Kernel panics after 6-20 hours regurlarly with same stack dump

[Erik Sornes]

Kernel panics after 6-20 hours regurlarly with same stack dump
We have tried 3.13.0-43 and 3.13.0-40. The problem was not there on 3.2
The system is fully patched as of 17. des. 2014 and running "Ubuntu 12.04.5 LTS"
It works as a nfs fileserver with iscsiattached xfs and ext4 disks.
8 G memory and quadcore xeon 2.53GHz, hardware is Supermicro.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.13.0-43-generic 3.13.0-43.72~precise1
ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Dec 18 14:31 seq
 crw-rw---T 1 root audio 116, 33 Dec 18 14:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Thu Dec 18 15:01:06 2014
HibernationDevice: RESUME=UUID=2b3ce18a-e78a-4166-8cc2-136db857de71
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: Supermicro X8SIE
MarkForUpload: True
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=33e8af07-dbcf-4233-a097-ac4e1ae0501c ro crashkernel=384M-2G:64M,2G-:128M quiet
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-43-generic N/A
 linux-backports-modules-3.13.0-43-generic N/A
 linux-firmware 1.79.18
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux-lts-trusty
UpgradeStatus: Upgraded to precise on 2013-01-31 (685 days ago)
dmi.bios.date: 02/25/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0b
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X8SIE
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 24
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd02/25/2010:svnSupermicro:pnX8SIE:pvr0123456789:rvnSupermicro:rnX8SIE:rvr0123456789:cvnSupermicro:ct24:cvr0123456789:
dmi.product.name: X8SIE
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

[penalvch (penalvch)]

Erik Sornes, thank you for reporting this and helping make Ubuntu better.

As per http://www.supermicro.com/support/resources/results.aspx an update to your computer's buggy and outdated BIOS is available (1.2a). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed. If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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