[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
https://bugzilla.novell.com/show_bug.cgi?id=666793
https://bugzilla.novell.com/show_bug.cgi?id=666793#c2
--- Comment #2 from Aaron Burgemeister
https://bugzilla.novell.com/show_bug.cgi?id=666793
https://bugzilla.novell.com/show_bug.cgi?id=666793#c3
Aaron Burgemeister
https://bugzilla.novell.com/show_bug.cgi?id=666793
https://bugzilla.novell.com/show_bug.cgi?id=666793#c
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=666793
https://bugzilla.novell.com/show_bug.cgi?id=666793#c4
--- Comment #4 from Thomas Renninger
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
https://bugzilla.novell.com/show_bug.cgi?id=666793
https://bugzilla.novell.com/show_bug.cgi?id=666793#c6
--- Comment #6 from Jiri Slaby
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
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
https://bugzilla.novell.com/show_bug.cgi?id=666793
https://bugzilla.novell.com/show_bug.cgi?id=666793#c9
Jiri Slaby
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