[Bug 666793] New: OpenSUSE 11.3 will not boot unless holding down key or using hpet=disable in Grub
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c0 Summary: OpenSUSE 11.3 will not boot unless holding down key or using hpet=disable in Grub Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: aburgemeister@novell.com QAContact: qa@suse.de Found By: Customer Services Priority: 300 Blocker: --- OpenSUSE 11.3 x86_64 or x86_32 Linux laptop 2.6.34.7-0.7-desktop #1 SMP PREEMPT 2010-12-13 11:13:53 +0100 i686 athlon i386 GNU/Linux All applicable patches as of a couple seconds ago. This kernel bug (?) has been mentioned online a few times before and it appears to also affect the OpenSUSE kernel. http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/fedora-1... http://www.linuxquestions.org/questions/linux-newbie-8/kubutnu-9-04-freezes-... My machine is using full disk encryption (all but /boot, courtesy of the installer's ability to encrypt the LVM setup) so the hang is persistent even before the passphrase for the system is requested. Pressing a key will get to the passphrase prompt and then holding down any key after it is entered for several seconds (ten to fifteen) is usually required to get the system to complete its boot process. Once running all is well. Adding the hpet=disable option to Grub completely resolves the issue. I have tried both x86_32 and x86_64 'desktop' kernels and seen this happen. Searching Novell's BugZilla I found perhaps twenty bugs referencing 'hpet' but none seemed to match this issue. Expected Results: Boot normally. Actual Results: Boot stalls unless constantly receiving some kind of input from the keyboard (or maybe some other unknown device). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c1 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jslaby@novell.com InfoProvider| |aburgemeister@novell.com --- Comment #1 from Jiri Slaby <jslaby@novell.com> 2011-01-31 12:02:43 UTC --- Does processor.max_cstate=1 kernel parameter fix the issue too? Could you provide full dmesg? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c2 --- Comment #2 from Aaron Burgemeister <aburgemeister@novell.com> 2011-01-31 15:15:49 UTC --- Created an attachment (id=411282) --> (http://bugzilla.novell.com/attachment.cgi?id=411282) dmesg from bootup without the hpet option. Haven't checked processor.max_cstate=1 yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c3 Aaron Burgemeister <aburgemeister@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|aburgemeister@novell.com | --- Comment #3 from Aaron Burgemeister <aburgemeister@novell.com> 2011-01-31 20:03:43 UTC --- The processor.max_cstate=1 option seemed to work too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.pr |trenn@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c4 --- Comment #4 from Thomas Renninger <trenn@novell.com> 2011-02-09 19:44:37 UTC ---
Does processor.max_cstate=1 kernel parameter fix the issue too? Is this known or even fixed already?
If not, this sounds like machine/cpu specific issue, can you please also attach: dmidecode and /proc/cpuinfo then. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c5 --- Comment #5 from Aaron Burgemeister <aburgemeister@novell.com> 2011-02-09 19:54:26 UTC --- Created an attachment (id=413116) --> (http://bugzilla.novell.com/attachment.cgi?id=413116) Files with requested data. Thomas, based on what you quoted I'm curious if you saw Comment #3. Assuming you did, see the attached files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c6 --- Comment #6 from Jiri Slaby <jslaby@novell.com> 2011-02-09 19:56:06 UTC --- (In reply to comment #4)
Does processor.max_cstate=1 kernel parameter fix the issue too? Is this known or even fixed already?
Ah, it's probably a dup of bug 579932. Thomas Gleixner commented on my lkml post here: http://lkml.indiana.edu/hypermail/linux/kernel/1010.0/00958.html But there is no fix known I think. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c7 --- Comment #7 from Jiri Slaby <jslaby@novell.com> 2011-02-09 19:59:08 UTC --- (In reply to comment #6)
But there is no fix known I think.
Kernel bugzilla BTW: https://bugzilla.kernel.org/show_bug.cgi?id=15289 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c8 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@novell.com AssignedTo|trenn@novell.com |jslaby@novell.com --- Comment #8 from Thomas Renninger <trenn@novell.com> 2011-02-09 20:32:33 UTC --- Jiri, do you mind to take over, I am not aware of this story. It's interesting to know, though, thanks for the pointer. Let me know if you think I still can help. Hmm, as so much time was invested already: if we find an affected machine we could give it a bisect via pxe boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=666793 https://bugzilla.novell.com/show_bug.cgi?id=666793#c9 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #9 from Jiri Slaby <jslaby@novell.com> 2011-02-11 10:34:47 UTC --- (In reply to comment #8)
Hmm, as so much time was invested already: if we find an affected machine we could give it a bisect via pxe boot.
Unfortunately the bisection was not successful many times in this case. It always leads to an irrelevant commit... So probably it's some coherence with a merge or something. *** This bug has been marked as a duplicate of bug 579932 *** http://bugzilla.novell.com/show_bug.cgi?id=579932 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com