Monday, December 26, 2011 5:24 PMWill Set wrote:
>Sunday, December 25, 2011 4:24 AM Jonathan Nieder wrote:
>>Will Set wrote:
>>> Jonathan Nieder wrote
>>
but the boot fails in some way unless you
add processor.nocst=1 to the kernel command line.
[...]
>I had to test using 3.1.0
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 mo
Friday, December 23, 2011 6:54 PMJonathan Nieder wrote
>Hi Will,
>
>Will Set wrote:
>
>> I was able to take three pictures of the boot messages by scrolling up the
>> boot buffer from the login prompt, while booting 3.2.0-rc4-686-pae
>> to illustrate what I did my best to explain yesterday.
>
Hi Will,
Will Set wrote:
> I was able to take three pictures of the boot messages by scrolling up the
> boot buffer from the login prompt, while booting 3.2.0-rc4-686-pae
> to illustrate what I did my best to explain yesterday.
>
> I'll also attach the dmesg.udev-2 and acpidump-udev-2
Thanks.
Tuesday, November 15, 2011 3:10AM Jonathan Nieder wrote:
>
>Hi,
>
>Will Set
wrote:
>
>- you have tested some 3.1.0-1-686-pae kernel (I assume
> 3.1.0-1~experimental.1 from experimental).
Yes, 3.1.0-1~experimental.1 from experimental
>- unless you add "processor.nocst=1", it reliably hangs at
Hi,
Will Set wrote:
> I see several segfaults and hangs during boot per each successfult login.
By private email, you said:
- you have tested some 3.1.0-1-686-pae kernel (I assume
3.1.0-1~experimental.1 from experimental).
- unless you add "processor.nocst=1", it reliably hangs at boot tim
6 matches
Mail list logo
