[Acer Aspire 5750] Complete hang, no response to SysRq magic keys

[shinyblue]

This bug comes and goes. Recently it's started up again after about 6 months of not doing it. It started again around

Linux reech 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

and has just happened again.

It's intermittant, perhaps once a day or less.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-37-generic 3.2.0-37.58
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rich 1851 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc0600000 irq 43'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10250513,00100100 HDA:80862805,80860101,00100000'
   Controls : 26
   Simple ctrls : 12
Date: Sat Feb 23 08:37:06 2013
HibernationDevice: RESUME=UUID=cdc83e00-ab58-4d15-8c00-1767e317ff39
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc.
MachineType: Acer Aspire 5750
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=UUID=72d863fd-0e78-4313-96b2-e194ebe1d127 ro crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-37-generic N/A
 linux-backports-modules-3.2.0-37-generic N/A
 linux-firmware 1.79.1
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.20
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV70_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.20
dmi.modalias: dmi:bvnAcer:bvrV1.20:bd03/16/2012:svnAcer:pnAspire5750:pvrV1.20:rvnAcer:rnSJV70_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.20:
dmi.product.name: Aspire 5750
dmi.product.version: V1.20
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/

[Launchpad Janitor (janitor)]

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

[shinyblue (shinyblue)]

Am trying new BIOS update. Thanks to <a href="http://www.linuxinsight.com/how-to-flash-motherboard-bios-from-linux-no-dos-windows-no-floppy-drive.html" >these instructions</a> for how to do this.

[shinyblue (shinyblue)]

OK, still get hangs after the BIOS update :-(

They mostly happen when running on battery, but had one lock up last week on AC power too. Currently on Ubuntu 12.04

Linux reech 3.2.0-53-generic #81-Ubuntu SMP Thu Aug 22 21:01:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[shinyblue (shinyblue)]

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V1.20
03/16/2012

[shinyblue (shinyblue)]

Aaaagh! I thought that flash routine ran fast. It hadn't worked. I've tried again:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V1.21
08/09/2012

No crashes yet (5 mins use so far), but promise to update this if/when it happens again. Sorry for wasting your time, let's hope the BIOS update fixed it!

[shinyblue (shinyblue)]

I can confirm it still happens with the latest BIOS.

[penalvch (penalvch)]

shinyblue, could you please capture the oops following https://help.ubuntu.com/community/DebuggingSystemCrash ?

[shinyblue (shinyblue)]

Installed linux-crashdump. Test with AltGr+SysRq+C. Crashes. Hangs with no disk activity 5+minutes. Does not reboot. Nothing in /var/crash, nothing apparently unusual in /var/log/kern.log I'll assume that linux-crashdump is crashing and ignore that - install linux-crashdump-crashdump? ;-)

Next time it happens I'll dump the whole of /var/log and /var/crash immediately after, JIC.

[shinyblue (shinyblue)]

In case it's helpful, here's a screenshot of the panic from /var/log/syslog (never gets written to disk), after doing a "test crash" as explained at https://wiki.ubuntu.com/Kernel/CrashdumpRecipe?action=show&redirect=KernelTeam%2FCrashdumpRecipe (n.b. as instructed, I've stripped back the APPEND options one by one - always get a hang)

http://i.imgur.com/6vkAuOA.jpg

[penalvch (penalvch)]

shinyblue, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this.

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 daily kernel 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. 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-rc6

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.

[Launchpad Janitor (janitor)]

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