Regression between 2.6.35-020635-rc1 and 2.6.35-020635 breaks acpi support on Asus X71 laptop

[Chereji Mihai]

Binary package hint: linux-image

I am using Ubuntu Lucid on 64bits.

When trying to upgrade my kernel via the kernel-ppa I've come across the following: No kernel past http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid/ will work with acpi activated on my laptop.
The next version, which is http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-maverick/ as far as I can tell, will not work with acpi on. (when booting with acpi on, the last message on screen is registered taskstats version 1 )

All other kernels give an error as nvidia-current refuses to upgrade properly.

I have also tried running maverick and natty alpha live-cds and both of them stop at the exact same spot.

I will by all means try to help in tracking down this bug even further.
---
Architecture: amd64
CheckboxSubmission: 4a6e7791f33f8f7d1f813e08933f8662
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
NonfreeKernelModules: nvidia
Package: linux-meta (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.35-020635-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom dialout fuse lpadmin netdev plugdev sambashare

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SIS966 [HDA SIS966], device 0: ALC663 Analog [ALC663 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cronco 1967 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SIS966'/'HDA SIS966 at 0xf9ff0000 irq 18'
   Mixer name : 'Realtek ALC663'
   Components : 'HDA:10ec0663,10431963,00100001'
   Controls : 16
   Simple ctrls : 8
CheckboxSubmission: 4a6e7791f33f8f7d1f813e08933f8662
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=94ae1e95-149f-4e0e-86c8-0de7cd49947a
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: ASUSTeK Computer Inc. X71SL
NonfreeKernelModules: nvidia
Package: linux-meta (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=80a4f099-6cd2-45fa-8964-3459f8c41b1c ro splash vga=795 quiet splash noacpi acpi=off
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.35~lucid1-generic 2.6.35.4
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: Yes
Tags: lucid kconfig regression-release needs-upstream-testing
Uname: Linux 2.6.35-22-generic x86_64
UserAsoundrc:

UserGroups: adm admin cdrom dialout fuse lpadmin netdev plugdev sambashare
dmi.bios.date: 09/24/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X71SL
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd09/24/2008:svnASUSTeKComputerInc.:pnX71SL:pvr1.0:rvnPEGATRONCORPORATION:rnX71SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: X71SL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Tim Gardner (timg-tpi)]

You need to attach your platform information using 'apport-collect 689796'

[Chereji Mihai (croncobaurul)]

I've tried doing that in the first place, but apport said that as this was not an ubuntu kernel it couldn't collect data (as seen above) - i downloaded the packages and ran dpkg. Would installing them via apt or synaptic help in that sense?

[Tim Gardner (timg-tpi)]

Well, boot your stock Lucid kernel and run apport-collect from there. Furthermore, you should be getting the Maverick backported kernels from the archive by installing linux-image-generic-lts-backport-maverick. If you're still having problems, then try adding 'pci=noacpi' to the grub boot command.

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Chereji Mihai (croncobaurul)]

apport information

[Tim Gardner (timg-tpi)]

Given that this is ACPI related, there are a number of things to try:
) Try the current Natty Live CD
) Wait for over 300 seconds to make sure its really hung. It could be a timer wrap around.
) Boot with nolapic_timer
) Boot with nolapic
) run the Firmware Test Suite from https://launchpad.net/~firmware-testing-team/+archive/ppa-firmware-test-suite-natty-stable

[Chereji Mihai (croncobaurul)]

The current Natty Live CD is still a no go.

From that point on, I wasn't sure if your instructions referred to the Natty Live Cd or 2.6.35.22 (the first variation of the kernel where I found the bug) so I tried your instructions on both:

Waiting was no good (for neither of them). Left the computer alone for about 8-10 minutes each time.
Booting with nolapic from the Natty Live cd gave me a kernel panic (I assume I should report this as a bug, no?) but I'm writing this from 2.6.35.22 with nolapic.

[Chereji Mihai (croncobaurul)]

nolapic_timer was also a no go.

[Tim Gardner (timg-tpi)]

Bummer. Well then, if 2.6.35-rc1 was functional, lets try subsequent RC candidates until it fails:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc2-maverick
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc3-maverick/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc4-maverick/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc5-maverick/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc6-maverick/

[Chereji Mihai (croncobaurul)]

RC2 gives the message "ERST: Table is not found!" and only continues with nolapic option.

[Chereji Mihai (croncobaurul)]

I have tried running the latest build of the alternate install cd today (20110116 build) and it gave me the current kernel panic. I'm sorry, it's just a photo taken with my telephone, didn't know how else to capture the errors signaled.

[Chereji Mihai (croncobaurul)]

Again, using the 'nolapic' boot option makes the kernel panic go away and lets ubuntu boot up with no problems.

[Jeremy Foshee (jeremyfoshee)]

Hi Chereji,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try 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 run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 689796

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]