[Kernel-packages] [Bug 1613925] Re: System locks up after issuing a sas3ircu storage management command during RAID rebuild
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613925 Title: System locks up after issuing a sas3ircu storage management command during RAID rebuild Status in linux package in Ubuntu: Expired Bug description: We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a display or status command to the RAID controller during RAID rebuild process. The HDDs where the Operating system resides will change to RO (Read Only) once we trigger the problem. This will only occur if the Operating System's HDDs are also connected to the RAID controller. We've tried this problem with the OS residing on a USB and this problem does not occur. Apport is not writing or reporting anything in the "/etc/apport/" directory "ubuntu-bug" is not accessible after the crash. Ubuntu 16.04.1 LTS 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le PPC64EL (Power8) RAID Controller: LSI SAS3008 - Driver: mpt3sas - Driver version: 12.100.00.00 HDDs: - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides) - 2x Seagate ST6000NM0034 (FW: E001) (RAID1) 1.) Ubuntu 16.04.1 LTS 2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le 3.) A driver update to prevent this from crashing the system. 4.) The system crashed. Please read the first paragraph above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el Date: Tue Aug 16 18:23:32 2016 InstallationDate: Installed on 2016-08-16 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416 ProcLocks: 1: FLOCK ADVISORY WRITE 7727 00:17:5 0 EOF 2: FLOCK ADVISORY WRITE 7723 00:14:631 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition394321280 -1 ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1613925] Re: System locks up after issuing a sas3ircu storage management command during RAID rebuild
Not sure if this Broadcom fix addresses this issue - in fact, I tried many ways to reproduce this and wasn't able. Perhaps this should be closed as non-reproducible if we have no more news from the reporter. If dexterb has more updated information, please let us know. Thanks, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613925 Title: System locks up after issuing a sas3ircu storage management command during RAID rebuild Status in linux package in Ubuntu: Incomplete Bug description: We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a display or status command to the RAID controller during RAID rebuild process. The HDDs where the Operating system resides will change to RO (Read Only) once we trigger the problem. This will only occur if the Operating System's HDDs are also connected to the RAID controller. We've tried this problem with the OS residing on a USB and this problem does not occur. Apport is not writing or reporting anything in the "/etc/apport/" directory "ubuntu-bug" is not accessible after the crash. Ubuntu 16.04.1 LTS 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le PPC64EL (Power8) RAID Controller: LSI SAS3008 - Driver: mpt3sas - Driver version: 12.100.00.00 HDDs: - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides) - 2x Seagate ST6000NM0034 (FW: E001) (RAID1) 1.) Ubuntu 16.04.1 LTS 2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le 3.) A driver update to prevent this from crashing the system. 4.) The system crashed. Please read the first paragraph above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el Date: Tue Aug 16 18:23:32 2016 InstallationDate: Installed on 2016-08-16 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416 ProcLocks: 1: FLOCK ADVISORY WRITE 7727 00:17:5 0 EOF 2: FLOCK ADVISORY WRITE 7723 00:14:631 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition394321280 -1 ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1613925] Re: System locks up after issuing a sas3ircu storage management command during RAID rebuild
Broadcom found root cause and proposed the following fix: https://marc.info/?l=linux-block=147731657127810=2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613925 Title: System locks up after issuing a sas3ircu storage management command during RAID rebuild Status in linux package in Ubuntu: Incomplete Bug description: We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a display or status command to the RAID controller during RAID rebuild process. The HDDs where the Operating system resides will change to RO (Read Only) once we trigger the problem. This will only occur if the Operating System's HDDs are also connected to the RAID controller. We've tried this problem with the OS residing on a USB and this problem does not occur. Apport is not writing or reporting anything in the "/etc/apport/" directory "ubuntu-bug" is not accessible after the crash. Ubuntu 16.04.1 LTS 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le PPC64EL (Power8) RAID Controller: LSI SAS3008 - Driver: mpt3sas - Driver version: 12.100.00.00 HDDs: - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides) - 2x Seagate ST6000NM0034 (FW: E001) (RAID1) 1.) Ubuntu 16.04.1 LTS 2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le 3.) A driver update to prevent this from crashing the system. 4.) The system crashed. Please read the first paragraph above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el Date: Tue Aug 16 18:23:32 2016 InstallationDate: Installed on 2016-08-16 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416 ProcLocks: 1: FLOCK ADVISORY WRITE 7727 00:17:5 0 EOF 2: FLOCK ADVISORY WRITE 7723 00:14:631 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition394321280 -1 ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1613925] Re: System locks up after issuing a sas3ircu storage management command during RAID rebuild
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.8 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.8 ** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613925 Title: System locks up after issuing a sas3ircu storage management command during RAID rebuild Status in linux package in Ubuntu: Incomplete Bug description: We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a display or status command to the RAID controller during RAID rebuild process. The HDDs where the Operating system resides will change to RO (Read Only) once we trigger the problem. This will only occur if the Operating System's HDDs are also connected to the RAID controller. We've tried this problem with the OS residing on a USB and this problem does not occur. Apport is not writing or reporting anything in the "/etc/apport/" directory "ubuntu-bug" is not accessible after the crash. Ubuntu 16.04.1 LTS 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le PPC64EL (Power8) RAID Controller: LSI SAS3008 - Driver: mpt3sas - Driver version: 12.100.00.00 HDDs: - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides) - 2x Seagate ST6000NM0034 (FW: E001) (RAID1) 1.) Ubuntu 16.04.1 LTS 2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le 3.) A driver update to prevent this from crashing the system. 4.) The system crashed. Please read the first paragraph above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el Date: Tue Aug 16 18:23:32 2016 InstallationDate: Installed on 2016-08-16 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416 ProcLocks: 1: FLOCK ADVISORY WRITE 7727 00:17:5 0 EOF 2: FLOCK ADVISORY WRITE 7723 00:14:631 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition394321280 -1 ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1613925] Re: System locks up after issuing a sas3ircu storage management command during RAID rebuild
** Summary changed: - PPC system locks up after sas3ircu command is issued during RAID rebuild + System locks up after issuing a sas3ircu storage management command during RAID rebuild ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613925 Title: System locks up after issuing a sas3ircu storage management command during RAID rebuild Status in linux package in Ubuntu: Confirmed Bug description: We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a display or status command to the RAID controller during RAID rebuild process. The HDDs where the Operating system resides will change to RO (Read Only) once we trigger the problem. This will only occur if the Operating System's HDDs are also connected to the RAID controller. We've tried this problem with the OS residing on a USB and this problem does not occur. Apport is not writing or reporting anything in the "/etc/apport/" directory "ubuntu-bug" is not accessible after the crash. Ubuntu 16.04.1 LTS 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le PPC64EL (Power8) RAID Controller: LSI SAS3008 - Driver: mpt3sas - Driver version: 12.100.00.00 HDDs: - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides) - 2x Seagate ST6000NM0034 (FW: E001) (RAID1) 1.) Ubuntu 16.04.1 LTS 2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le 3.) A driver update to prevent this from crashing the system. 4.) The system crashed. Please read the first paragraph above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el Date: Tue Aug 16 18:23:32 2016 InstallationDate: Installed on 2016-08-16 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416 ProcLocks: 1: FLOCK ADVISORY WRITE 7727 00:17:5 0 EOF 2: FLOCK ADVISORY WRITE 7723 00:14:631 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition394321280 -1 ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
