MCE Kernel Panic with 1394 Firewire Enabled on Z7S MB

Bug #1016556 reported by Brendan McLearie on 2012-06-22
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
linux (Ubuntu)
High
Unassigned

Bug Description

System crashes with catatrophic MCE Kernel Panic on all versions of Ubuntu and mainline kernels since 2.6.38. 2.6.35-xx works fine. Bisects would not compile after second round.

Please see https://launchpadlibrarian.net/74062894/Panic.jpg for call trace.

Related bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/801840 shows history.

WORKAROUND:
Thanks to Tomasz Kusmierz who accidently found that disabling 1394 in BIOS stops the crashes. Also thanks to Daniel Manrique for his extensive assitance on the bug. (https://launchpad.net/~roadmr)

Regards
Brendan

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: upstart 1.5-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 22 23:32:46 2012
ExecutablePath: /sbin/init
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SourcePackage: upstart
UpgradeStatus: Upgraded to precise on 2012-06-19 (3 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: brendan 3423 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9bf4000 irq 93'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,104382cb,00100001'
   Controls : 43
   Simple ctrls : 20
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=abdf656c-e2c8-49fd-8cac-3cea7fac4cc8
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: root=UUID=dc5cb730-74c6-4caf-854f-5b5a1ee508af ro
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-25-generic N/A
 linux-backports-modules-3.2.0-25-generic N/A
 linux-firmware 1.79
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-25-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-06-19 (3 days ago)
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 07/22/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Z7S WS
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.:bvr0401:bd07/22/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnZ7SWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

affects: ubuntu → linux (Ubuntu)
tags: added: mce panic
Joseph Salisbury (jsalisbury) wrote :

@Brendan,

The v3.5 kernel is now in development. I see that you tested v3.3 when it was mainline. Would it be possible for you to test the latest version of v3.5? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc3-quantal/

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1016556

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

affects: linux (Ubuntu) → linux-meta (Ubuntu)
description: updated
affects: linux-meta (Ubuntu) → linux (Ubuntu)

apport information

description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

@joseph

I have tested the 3.5 release candidte and can confirm that the same problem exists. the problem definitiely started between 2.6.35 and 2.6.38 and has been present in all Ubuntu and mainline kerels since.

The occurence of the panic is random, however always within the first minute or so of linux boot. Sometimes I get a panic screen, at other times its a reset with no panic, and I also get straight system freezes. I imagine it depends what code is running at the time as to whether the exception handler can acutally run and report the panic.

In the case of the 3.5 kernel, I am yet to receive a panic message - it alwyas simply freezes. This is currently occuring just after initialising USB drivers aqnd may be simply coincident on the fact that the USB initialisation takes an extended time before giving up on talking to my apple keyboard or logitech bluetooth mouse. I imagine installation of the rest of the architecture driver files would resolve this.

If 1394 is diabled in BIOS then 3.5 boots sucessfully through to the gnome login screen and seems happy (although no mouse, keyboard or network functional so I havent been able to test further).

I woud tend to just write the problem off and not use 1394, except however for the fact that it was totally rock solid up until 2.6.38 and having pursued this bug now for some time, I have a gut feel that there is some MB/kernel timing issue interacting with the problem. If that is indeed the case and it can be identified and fixed would be a good thing to have sorted out for the Ubuntu and linux projects generally.

Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
status: Confirmed → Triaged
description: updated
tags: added: natty needs-upstream-testing regression-release
removed: mce panic
tags: added: kernel-bug-exists-upstream-v3.5-rc3-quantal

Brandon McLearie, could you please test the latest upstream kernel available (v3.7-rc1-quantal) 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

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

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

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

Duplicates of this bug

Other bug subscribers

Related questions