2.6.35-28-generic amd64 kernel crash @ boottime

[Dlizzz]

The kernel crashes not long after it has booted. It's always the case when I boot in X mode (no time to login), but it isn't always the case when I boot in text mode.
The previous version of Ubuntu (10.04) is running fine on the same machine. I'm able to boot the 10.10 version, without any problem, with the mainline kernel 2.6.34-02063407-generic amd64

WORKAROUND: So I've rebooted the 2.6.35-28 kernel with the "intel_idle.max_cstate=0" parameter on the command line and everything went fine.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-28-generic 2.6.35-28.49
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: matou 2065 F.... pulseaudio
 /dev/snd/pcmC0D0c: matou 2065 F...m pulseaudio
 /dev/snd/pcmC0D0p: matou 2065 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7ff8000 irq 73'
   Mixer name : 'Realtek ALC1200'
   Components : 'HDA:10ec0888,104383c0,00100101'
   Controls : 35
   Simple ctrls : 20
Date: Sat Apr 2 18:21:44 2011
HibernationDevice: RESUME=UUID=bef0dc46-f93c-4db8-9233-99fa48f6e4b0
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=4c1c9b0d-cb44-4703-830d-381af17ec332 ro text
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38.5
RfKill:

SourcePackage: linux
dmi.bios.date: 03/08/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1303
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1303:bd03/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Dlizzz (denis-lambolez)]

I've checked the bug list for the 10.10 and found that this bug is similar to the #634702 bug.
So I've rebooted the 2.6.35-28 kernel with the "intel_idle.max_cstate=0" parameter on the command line and everything went fine.
My PC is based on an Asus P6T (X58 Chipset) with a CoreI7 CPU. But because my system is overclocked, I have disabled all the power/frequency control function in the BIOS: C1E Support, SpeedStep Tech and C-State Tech are disabled to be sure that the CPU frequency is as stable as possible.
When I boot without the parameter on the command line, I have the following report from the intel_idle driver in dmesg:
[ 2.050129] intel_idle: MWAIT substates: 0x1120
[ 2.050130] intel_idle: v0.4 model 0x1A
[ 2.050131] intel_idle: lapic_timer_reliable_states 0x2
[ 2.053740] ACPI: acpi_idle yielding to intel_idle
So, the driver is loaded and runs even if C-State is disabled in the bios ! It could be the cause of the kernel crash.

[penalvch (penalvch)]

Dlizzz, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs