[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#649304: <processor.nocst=1> / dmesg and acpidump



See attached dmesg-processor.nocst=1 acpidump

I haven't been able to capture the buffer from an incomplete boot,
but the kernel is still hanging at many different points when no
options are added to the kernel commandline.

I have found a few other kernel options that also work with varying
degrees of usefulness.
<nocrs>
<processor.max_cstate=hw>
<processor.max_cstate=acpi>
As well as a few options that work sometimes but also hang sometimes.

<no_acpi> 
worked twice but timed out populating dev, iirc,
and also hung after gdm3 started
with no keyboard and mouse input.
But I was able to ssh in and save dmesg and acpidump

<processor.max_cstate=0> 
also seems to work with a timeout somewhere
"probably populating dev"
I only tested this "undocumented" option once.

I've also captured dmesg and acpidump labeled with each of the above
options
dmesg-nocrs
acpi-nocrs

dmesg-no_acpi
apci-no_acpi
etc.

best regards,
Will


Attachment: dmesg-processor.nocst=1
Description: Binary data

Attachment: acpidump
Description: Binary data


Reply to: