Bug 686451

Summary:	System failed to boot / start after installing.
Product:	[openSUSE] openSUSE 11.4	Reporter:	Ferdinand Thiessen <rpm>
Component:	Basesystem	Assignee:	E-mail List <kernel-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P2 - High	CC:	cobexer, Creationn, jeffm, lorne_shantz, novell, thorsten
Version:	Final
Target Milestone:	Final
Hardware:	32bit
OS:	openSUSE 11.4
See Also:	https://bugzilla.novell.com/show_bug.cgi?id=688714
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Output of dmesg and content of messages file

Description Ferdinand Thiessen 2011-04-09 15:23:16 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-de; rv:1.9.2.16) Gecko/20110319 SUSE/3.6.16-0.2.1 Firefox/3.6.16

After installing openSUSE 11.4 on my 3000 Lenovo N200, the system doesn't boot.
So it shows GRUB, and started to boot, but then it hang. I mean i doesn't go forward.
If I press "Esc" fast enough on star I can see the message:
"Doing fast Boot [3.820012] failed to resume link (scontrd 0) Creating nodes with uDev"
Or like this.
After two minutes this message appears too:
"Bug: soft look up CPU #0 stuck for 63 s! (modprobe 150)"
But sometimes (one of thirty trials) it still starts. The only way to start the system in the normal case is to boot into the failsave mode.

But I make out that the problem is the Kernel (default), if I change to Desktop-Kernel I have not this problem, so there must a bug in the default Kernel.
If it would help you, I add the content of the messages file and the output of dmesg to this report.

Reproducible: Sometimes

Steps to Reproduce:
1.install openSUSE 11.4 on the Laptop
2.Tray to boot
3.select normal start in GRUB (not failsave)
Actual Results:  
only shows the loading-screen all the time.

Expected Results:  
Boot the system.

I found a work-around: boot in failsave mode and change Kernel from default to desktop.

Comment 1 Ferdinand Thiessen 2011-04-09 15:25:04 UTC

Created attachment 424118 [details]
Output of dmesg and content of messages file

Comment 2 Thorsten W. Schmidt 2011-04-10 18:41:39 UTC

I have the same problem on my Samsung NC10 with an Atom CPU

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 28
model name      : Intel(R) Atom(TM) CPU N270   @ 1.60GHz
stepping        : 2
cpu MHz         : 800.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 1
apicid          : 1
initial apicid  : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm movbe lahf_lm dts
bogomips        : 3191.92
clflush size    : 64
cache_alignment : 64
address sizes   : 32 bits physical, 32 bits virtual
power management:


When I boot with the kernel option "maxcpus=0" then the system boots normally.

The problem can also be avoided by installing the vanilla kernel but then the display brightness cannot be changed anymore. Not automatically or by hardware keys.

> xbacklight -dec +10.0
No outputs have backlight property

Maybe this helps

Comment 3 Christoph Obexer 2011-05-08 08:26:21 UTC

do both of you use an intel garphics card? if so this might be related to: https://bugzilla.novell.com/show_bug.cgi?id=688714

Comment 4 Ferdinand Thiessen 2011-05-18 16:23:14 UTC

I think it is an Intel graphics card.

Comment 5 Lorne Shantz 2011-05-20 16:20:30 UTC

I believe this is a bug introduced with the new kernel. I have a i7 with an intel mb and it hangs on me. If you look at your listing above:
core id         : 0
cpu cores       : 1

Do you really only have 1 cpu, or is it a multi core chip? I have found if you disable CPUID to legacy OS it will work. This has been introduced with 11.4. 11.3 kernels did not cause this issue. I am just now researching why my SMP kernel is not working and or hanging. This is what I just discovered. Try disabling the CPUID in CMOS. I have an NVIDIA card with the same problems as above.

Comment 6 Ursan Marius Bogdan 2012-01-14 11:49:06 UTC

I have openSUSE 12.1 installed under VBox with kernel-default and the machine did rebooted fine after install. 

Probably this bug is fixed in openSUSE 12.1 while using kernel-default.

Comment 7 Ferdinand Thiessen 2012-01-14 15:12:25 UTC

I do not have tested it, but I think installing in a virtual box is senseless, because if it is a problem with the hardware, you can not reproduce the error in a virtual machine.

Comment 8 Ursan Marius Bogdan 2012-01-14 17:46:06 UTC

Ferdinand, if you could test it on real hardware that will bring some informations for your bug report and for the assignee.

Comment 9 Jeff Mahoney 2012-08-02 16:04:37 UTC

With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained.

Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue.

We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users.  We're working hard to make openSUSE 12.2 the best openSUSE release yet!