Bug#627019: several kernel hangs before geting to login
Will Set wrote:
> Jonathan Nieder wrote
>> but the boot fails in some way unless you
>> add processor.nocst=1 to the kernel command line.
>
> Yes,
> Adding processor.nocst=1 has always worked for me on all effected kernels I've tested so far.
[...]
>> This is on the machine with a D865GBF motherboard.
>
> No,
> This report is and always will be Intel D865GRH mobo.
Sorry for the typo, and thanks for the corrections.
Excellent --- I suspect that udev is actually a red herring and that
_any_ code executed during the early boot process is likely to
misbehave or segfault on this machine unless processor.nocst=1 is
passed.
In other words, this looks like incorrect execution or memory
corruption during boot. Which is consistent with a broken _CST table.
Unfortunately the acpidump you sent does not include a _CST table.
The log you sent does not include any complaints about lack of a _CST
table, though. Puzzling.
I recommend keeping processor.nocst=1 on the kernel command line for
now. We should report this upstream to Len Brown and the
linux-acpi@vger.kernel.org list, but I would like to delay that until
after the holidays to avoid overwhelming them.
> There is another Debian user that has an Intel D865GBF mobo
> with a "very" similar debian bug report filed.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631597
Does disabling hyperthreading in the BIOS avoid trouble for you, too?
Reply to: