Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

Bug #1581326 reported by Chaitra P B on 2016-05-13
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Joseph Salisbury
Trusty
High
Joseph Salisbury
Xenial
High
Joseph Salisbury
Yakkety
High
Joseph Salisbury

Bug Description

Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver- v12.100.00.00,

Successfully discovered HBA and the devices connected to HBA.
>>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). volume successfully created and listed from SAS3IRCU utility.
>>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU utility.
Kernel crashed here while creating second volume.
>>tried with all possible combinations of RAID volumes.

Please find the attached kernel crash logs.

>>cat /proc/version_signature
Ubuntu 4.4.0-21.37-generic 4.4.6

HBA used : LSI SAS3(Fury)

Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
Expected : One should be able to create MAX 2 RAID volumes at any point of time successfully , without any kernel crash.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
InstallationDate: Installed on 2016-05-11 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
IwConfig:
 enp5s0f0 no wireless extensions.

 enp5s0f1 no wireless extensions.

 lo no wireless extensions.
MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 04/28/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0b
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DRH-7TF/7F/iTF/iF
dmi.board.vendor: Supermicro
dmi.board.version: 1234567890
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
dmi.product.name: X9DRH-7TF/7F/iTF/iF
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
InstallationDate: Installed on 2016-05-11 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
IwConfig:
 enp5s0f0 no wireless extensions.

 enp5s0f1 no wireless extensions.

 lo no wireless extensions.
MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 04/28/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0b
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DRH-7TF/7F/iTF/iF
dmi.board.vendor: Supermicro
dmi.board.version: 1234567890
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
dmi.product.name: X9DRH-7TF/7F/iTF/iF
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
InstallationDate: Installed on 2016-05-11 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
IwConfig:
 enp5s0f0 no wireless extensions.

 enp5s0f1 no wireless extensions.

 lo no wireless extensions.
MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 04/28/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0b
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DRH-7TF/7F/iTF/iF
dmi.board.vendor: Supermicro
dmi.board.version: 1234567890
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
dmi.product.name: X9DRH-7TF/7F/iTF/iF
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro

Chaitra P B (chaitra-basappa) wrote :

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

apport-collect 1581326

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 xenial
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

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

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

Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

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'.

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/v4.6-rc7-wily/

Changed in linux (Ubuntu):
importance: Undecided → High
Changed in linux (Ubuntu Xenial):
importance: Undecided → High
status: New → Incomplete
tags: added: kernel-da-key
Chaitra P B (chaitra-basappa) wrote :

Joseph,
 Tested with latest upstream kernel : http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
issue not observed and hence looks like this bug is fixed in mainline kernel 'kernel-fixed-upstream'

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Xenial):
status: Incomplete → Triaged
Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: needs-reverse-bisect
Changed in linux (Ubuntu):
status: Triaged → New
Brad Figg (brad-figg) on 2016-06-13
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Changed in linux (Ubuntu Xenial):
status: Triaged → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Changed in linux (Ubuntu Xenial):
status: Incomplete → Triaged
Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Xenial):
assignee: nobody → Joseph Salisbury (jsalisbury)
bugproxy (bugproxy) on 2016-12-08
tags: added: architecture-ppc64 bugnameltc-142479 severity-critical targetmilestone-inin16041
Changed in linux (Ubuntu):
status: Triaged → In Progress
Changed in linux (Ubuntu Xenial):
status: Triaged → In Progress
Changed in linux (Ubuntu Trusty):
status: New → In Progress
Changed in linux (Ubuntu Yakkety):
status: New → In Progress
Changed in linux (Ubuntu Trusty):
importance: Undecided → High
Changed in linux (Ubuntu Yakkety):
importance: Undecided → High
Changed in linux (Ubuntu Trusty):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Yakkety):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
status: In Progress → Incomplete
Changed in linux (Ubuntu Trusty):
status: In Progress → Incomplete
Changed in linux (Ubuntu Xenial):
status: In Progress → Incomplete
Changed in linux (Ubuntu Yakkety):
status: In Progress → Incomplete
bugproxy (bugproxy) on 2017-04-04
tags: removed: apport-collected bugnameltc-142479 kernel-da-key needs-reverse-bisect severity-critical xenial
78 comments hidden view all 158 comments

Default Comment by Bridge

tags: added: bugnameltc-142479 severity-critical
bugproxy (bugproxy) wrote : syslog

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

------- Comment From <email address hidden> 2017-06-07 09:35 EDT-------
(In reply to comment #106)
>
> Does this bug also happen with Yakkety(4.8 based) and Zesty(mainline based)?
> I wanted to see if I should SRU the patch to those releases as well?

We have seen two instances of this problem happening on Zesty this week. Both running 4.10.0-21-generic #23-Ubuntu kernels.

Joseph Salisbury (jsalisbury) wrote :

Has there been any additional activity on the patch upstream?

This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix.

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

Changed in linux (Ubuntu Yakkety):
status: Incomplete → Won't Fix

------- Comment From <email address hidden> 2017-10-07 23:22 EDT-------
There was never a patch provided here, this problem does not exist in current/newer Ubuntu releases. Closing.

Displaying first 40 and last 40 comments. View all 158 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments