Kernel freeze on Acer Aspire 1510 since Maverick

[Karl-Felix Glatzer]

On every boot all Kernels newer than 2.6.33-02063306 completely freeze on my Acer Aspire 1510 notebook. When the kernel freezes the fan gets louder and i can't switch ttys anymore nor use the magic sysrq combinations for a safe reboot so i have to hard reset the laptop by pressing the power key for a while.

This happens regardless of the installed ubuntu version. At the moment i have a dual boot of lucid and precise and the bug is still present with the 3.2 linux kernel on precise although it works fine when i boot it with the current lucid kernel.

I've made a picture of the freeze using the 3.2 linux kernel booting it with the --debug and without the quiet and splash kernel parameters. I'll upload it as soon as possible.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-37-generic 2.6.32-37.81
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21
Uname: Linux 2.6.32-37-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: k1ll 1583 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'nForce3'/'NVidia nForce3 with ALC250 at irq 22'
   Mixer name : 'Realtek ALC250 rev 2'
   Components : 'AC97a:414c4752'
   Controls : 33
   Simple ctrls : 21
Date: Tue Jan 3 12:50:59 2012
HibernationDevice: RESUME=UUID=39897aa7-39bf-45f3-8dbe-732bf198cbbf
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 0483:0321 SGS Thomson Microelectronics
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer,Inc. Aspire 1510
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-37-generic root=UUID=c0efd683-5f06-4a82-80e1-b23fdf8806c5 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 05/10/04
dmi.bios.vendor: Acer
dmi.bios.version: 3A29
dmi.board.name: Aspire 1510
dmi.board.vendor: Acer,Inc.
dmi.board.version: Rev.A
dmi.chassis.asset.tag: No Asset Tag XXX
dmi.chassis.type: 1
dmi.chassis.vendor: Acer,Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvr3A29:bd05/10/04:svnAcer,Inc.:pnAspire1510:pvrAspire1510:rvnAcer,Inc.:rnAspire1510:rvrRev.A:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 1510
dmi.product.version: Aspire 1510
dmi.sys.vendor: Acer,Inc.
---
ApportVersion: 2.12.6-0ubuntu1
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 14.04
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 0483:0321 STMicroelectronics
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer,Inc. Aspire 1510
MarkForUpload: True
Package: linux 3.12.0.2.4
PackageArchitecture: i386
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic root=UUID=1605d023-943a-4512-8b73-3c32fc059a68 ro quiet splash
ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-2-generic N/A
 linux-backports-modules-3.12.0-2-generic N/A
 linux-firmware 1.117
RfKill:

Tags: trusty
Uname: Linux 3.12.0-2-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/10/04
dmi.bios.vendor: Acer
dmi.bios.version: 3A29
dmi.board.name: Aspire 1510
dmi.board.vendor: Acer,Inc.
dmi.board.version: Rev.A
dmi.chassis.asset.tag: No Asset Tag XXX
dmi.chassis.type: 1
dmi.chassis.vendor: Acer,Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvr3A29:bd05/10/04:svnAcer,Inc.:pnAspire1510:pvrAspire1510:rvnAcer,Inc.:rnAspire1510:rvrRev.A:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 1510
dmi.product.version: Aspire 1510
dmi.sys.vendor: Acer,Inc.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to try and boot the Lucid kernel on your Precise partition? I assume it would boot just fine, but it would be a good data point to know if there is an issue with the Precise partition.

[Karl-Felix Glatzer (k1ll)]

I've used my latest Lucid kernel to install Precise and of course can boot it fine with this kernel. I tested the latest upstream kernel on both Lucid and Precise.

[Reinhard Tartler (siretart)]

This report looks pretty much like #891830. Maybe it should be marked as duplicate?

[Karl-Felix Glatzer (k1ll)]

I don't think this is a duplicate of #891830 since the kernel freezes while booting.

Also the bug seems to be an older regression since it's already present in the Maverick kernels but according to you bug #891830 was introduced in a kernel newer than 3.0. In addition that bug seems to be fixed in upstream kernel versions while this bug is not.

[Reinhard Tartler (siretart)]

I've filed bug #914161, which looks similar, albit with different hardware.

[Karl-Felix Glatzer (k1ll)]

I've tested both the current 3.2.0-20 precise kernel and the current 3.3-rc7 mainline kernel. They both freeze with similar output.

The attached picture shows the freeze of the 3.3-rc7 mainline kernel.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Karl-Felix Glatzer (k1ll)]

I've filed an upstream bug report at bugzilla.kernel.org. It's bug number is 43014.

[penalvch (penalvch)]

Karl-Felix Glatzer, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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 (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. 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. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

apport information

[Karl-Felix Glatzer (k1ll)]

I tried installing 14.04 via netboot but could not run the ""Detect Disks" step so i was not able to create a root partition. The "Detect Network Configuration" step also tried to load yenta_socket but i was able to skip it and still had a working network connection.

I resorted to installing 14.04 from my working 10.04 install via debootstrap and tested both the stock 14.04 kernel (3.12.0-2-generic) and the latest trusty mainline kernel (3.12.0-031200-generic). On both kernels i get the freeze when either yenta_socket is loaded on boot or from a terminal via modprobe.

[penalvch (penalvch)]

Karl-Felix Glatzer, the next step is to fully commit bisect from Lucid to Maverick, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?