On Thu, Mar 05, 2009 at 12:26:22AM +0000, Roger Leigh wrote:
> On Wed, Mar 04, 2009 at 07:57:25PM +0100, Pol Bettinger wrote:
> > Ben Hutchings wrote:
> >> Can you confirm whether this boot failure matches the bug filed upstream
> >> as <http://bugzilla.kernel.org/show_bug.cgi?id=12520>? That bug has not
> >> yet been fixed in a stable release but is believed to be fixed in Linux
> >> 2.6.29.
> >>
> >> Ben.
> >>
> > I can confirm having hit
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=12520
> >
> > Changing the "Max CPUID Value Limit" to disabled fixed this booting
> > problem. There is a already a patch in mainline (kernel) See this
> > thread
> > http://groups.google.com/group/linux.kernel/browse_thread/thread/2f27b0fe76919496/3638e04e45c3824b?lnk=raot
> > Post from Ingo Molnar on 22.Jan
> > I will now try to use this patch on 2.6.28.
>
> I also see this. Disabling the "Max CPUID Value Limit" in the BIOS
> CPU configuration allows the kernel to boot.
>
> However, applying the patch in the link above did not allow the
> kernel to boot without this option being disabled. I applied
> directly to the current linux-2.6 source package, then built and
> installed it. I'll try again tomorrow with both patch1 and patch2
> (this was just patch1), and see if that makes a difference.
Did appyling these patches fix the issue for you? Alternatively
you could just test 2.6.30 from unstable.
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
