System freeze on Lemur UltraThin with Linux 3.1

Bug #891830 reported by Michael Terry
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Lots of things were going on on my system (thunderbird filtering mail, a couple ssh sessions, web browser with dozens of tabs, IRC, etc). But nothing obviously triggered it.

But my mouse froze, the screen stopped updating, and I couldn't switch to VT1. Hopefully the logs make sense of it.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.1.0-2-generic-pae 3.1.0-2.3
ProcVersionSignature: Ubuntu 3.1.0-2.3-generic-pae 3.1.0
Uname: Linux 3.1.0-2-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.26-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mike 1766 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0800000 irq 42'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:10ec0272,15583100,00100001 HDA:80862804,15584101,00100000'
   Controls : 30
   Simple ctrls : 14
CheckboxSubmission: 9a284f3f6b4f7829abbe27ad9573a709
CheckboxSystem: 3935143777c965daaa64b51f0134f712
Date: Thu Nov 17 16:27:09 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110422)
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:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
MachineType: System76, Inc. Lemur UltraThin
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.1.0-2-generic-pae root=UUID=0e585e80-16f1-404c-80cc-7d9805fcc3b0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.1.0-2-generic-pae N/A
 linux-backports-modules-3.1.0-2-generic-pae N/A
 linux-firmware 1.61
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2011-11-05 (11 days ago)
dmi.bios.date: 11/11/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: CALPELLACRB.86C.0000.X.0000000000
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur UltraThin
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu2
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: lemu2
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C.0000.X.0000000000:bd11/11/2010:svnSystem76,Inc.:pnLemurUltraThin:pvrlemu2:rvnSystem76,Inc.:rnLemurUltraThin:rvrlemu2:cvnSystem76,Inc.:ct10:cvrlemu2:
dmi.product.name: Lemur UltraThin
dmi.product.version: lemu2
dmi.sys.vendor: System76, Inc.

Revision history for this message
Michael Terry (mterry) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Michael,

Was this a one time event, or can you reproduce the freeze?

Revision history for this message
Michael Terry (mterry) wrote :

I can't invoke it at will, but it has happened at least three times.

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-1.1)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-1.1
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: System freeze

In addition to testing the latest development kernel, 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 others). 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'.

Thanks in advance.

tags: added: needs-upstream-testing
Revision history for this message
Michael Terry (mterry) wrote :

I just got this same freeze with 3.2.0.1.1.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

(Am trying the mainline kernel next)

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-1.3)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-1.3
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: System freeze

Have you run previous versions of Ubuntu on this machine? If so, did this issue happen with previous versions?

tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
Michael Terry (mterry) wrote :

I don't recall it happening on previous versions.

BTW, I've been running mainline 3.2-rc2 kernel for a while and haven't hit this bug. I'll switch to latest Ubuntu kernel again and see if it's been fixed.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

That would be great data to have. Thanks, Michael.

Revision history for this message
Reinhard Tartler (siretart) wrote :

I can confirm the issue on the following machine:

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: FUJITSU
        Product Name: ESPRIMO P7935

The system freeze does not happen with the oneiric (3.0) kernel.

summary: - System freeze
+ System freeze on Lemur UltraThin with Linux 3.1
Revision history for this message
Michael Terry (mterry) wrote :

Just an update. I accidentally never actually switched back to Ubuntu precise kernels. So I've been running the rc2 kernel ever since November. But I did eventually hit the bug several times on the mainline rc2 kernel as well.

I am now for realz back on Ubuntu precise kernels.

Revision history for this message
Brad Figg (brad-figg) wrote :

@mterry,

It's been a while since the last comment on this bug. Does this issue still exist with the latest Precise kernel?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michael Terry (mterry) wrote :

No, I haven't seen it for a long time. Marking Fixed! Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.