Bug 231056 - Installation hangs on bootup
Summary: Installation hangs on bootup
Status: RESOLVED DUPLICATE of bug 231205
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Installation (show other bugs)
Version: Final
Hardware: x86-64 SUSE Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Kay Sievers
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-29 06:15 UTC by Joseph Comfort
Modified: 2007-01-12 07:06 UTC (History)
1 user (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Comfort 2006-12-29 06:15:43 UTC
Computer: HP Pavilion a1520n.  Motherboard: Asus A8N-LA (Nagami2-GL8E). 1 GB memory.  2 SATA disks (one added for Linux).

SuSE 10.2 x86_64 DVD iso (and CD1 also) downloaded and burned.  All mdsums OK.
When "Installation" starts, computer freezes with ~22 lines of text on the console.  No log files can be obtained.  A (hand) copy of the screen display is attached.  A workaround is to use ACPI disabled.  However, no hard disks are found in probing the system (a separate bugzilla report).

This bug is similar to #229217, which is waiting for information.  The only information available is attached here.

Sorry, I can't see how to make an attacment, or to get it to work.  The information is here:
[openSUSE icon]

[About 40% of the screen is blank.]

Console: switching to colour frame buffer device 156x60
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.01 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
RAMDISK drive initialized: 16 RAM disks of 128000K size 1024 blocksize
serio: 18042 AUX port at 0x60,0x64 irq 12
serio: 18042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input0
input: AT Translated Set 2 keyboard as /class/input/input1
input: ImPS/2 Logitech Wheel Mouse as /class/input/input2
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
ACPI: (supports S0 S1 S3 S4 S5)
Freeing unused kernel memory" 188k freed
Moving into tmpfs... done.

>>> openSUSE installation program v2.1.17 (c) 1996-2006 SUSE Linux Products GmbH <<<
Starting udev...
Comment 1 Joseph Comfort 2006-12-30 18:13:15 UTC
(In reply to comment #0)
Additional notes.

The cpu is a dual core AMD X2 3800+.

I discovered that a i386 installation DVD does not have any of the problems mentioned here (or in bug 231059).  The kernel messages do not show anything, to me, that seems unusual or troublesome.  (A thumb usb drive can be seen.  If someone can tell me how to get the messages copied to the drive, I'll forward them.)  All devices are detected and both cpu processors are recognized.  But I want to install 64-bit rpms and applications.

The problems did not occur with SuSE 10.1.  They are new to 10.2.
Comment 2 Kay Sievers 2006-12-31 15:46:36 UTC
Likely the loading of a kernel-module crashes the box. Steffen, any idea how to debug this?
Comment 3 Joseph Comfort 2007-01-07 01:11:34 UTC
My bug 231059 was marked as a duplicate of a more recent bug 232013.  I have attached some files there that might be useful.  They include the output of a semi-successful install (with 1 cpu processor lost), a recent boot.msg file, a hwinfo log file, and the output of the firmware check program (latest version). I hope that, with more people looking at it, the problems I (and others) are having will be rectified.  Thank you.
Comment 4 Joseph Comfort 2007-01-12 04:54:58 UTC
(In reply to comment #2)
All of my problems are resolved by installing the latest kotd.  See bug 232013 for 2 successful reports, and also lots of information.  In bug 231205, it was found that the bug apparently originates in a SuSE kernel patch, not known which one. The people who are working on these bugs all need to coordinate.
Comment 5 Kay Sievers 2007-01-12 07:06:21 UTC

*** This bug has been marked as a duplicate of bug 231205 ***