[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
If it help, I've done another change (against git hash 786235ee): diff --git a/kernel/kthread.c b/kernel/kthread.c index b5ae3ee..25a4780 100644 --- a/kernel/kthread.c +++ b/kernel/kthread.c @@ -298,7 +298,7 @@ struct task_struct *kthread_create_on_node(int (*threadfn)(void *data), * that thread. */ if (xchg(create-done, NULL)) - return ERR_PTR(-ENOMEM); + return ERR_PTR(-42); /* * kthreadd (or new kernel thread) will call complete() * shortly. So, depending on error (-12 / -ENOMEM or -42) we could know which return triggered the bug. Result is: [ 37.607981] scsi4: error handler thread failed to spawn, error = -42 To make sure the race condition do not affect which error is returned, I've booted 5 times that kernel. Each time I get error = -42. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
With few hopes, I've tried the latest kernel from: * trusty: linux 3.13.0-16.36 (linux-image-3.13.0-16-generic) * trusty-proposed (downloaded from launchpad directly) : linux 3.13.0-17.37 Both still have the bug. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I've tested the following: * v3.14-rc6-trusty from comment #38 : still fail with same error. * Kernel 786235eeba0e1e85e5cbbb9f97d1087ad03dfa21 with patch check-sigkill : still got the fail to spawn thread. I will attach full output from serial console. * Kernel 786235eeba0e1e85e5cbbb9f97d1087ad03dfa21 with patch kthread-defer-leaving.patch : also fail, but this time their is no error about failure to spawn thread. Only systemd-udevd blocked for more that 120 seconds. Also ouput of serial console attached. Note: on second console output, command result from ps is not complet, serial console seem to discard output when we generate it too fast. ** Attachment added: Console output with check-sigkill patch applied on 786235ee https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026608/+files/serial-ouput-patch-check-sigkill.txt -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
** Attachment added: Console output with kthread-defer-leaving patch applied on 786235ee https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026609/+files/serial-ouput-patch-kthread-defer-leaving.txt -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Yes, it is working! With this new patch applied (on 786235ee), server boot without any issue. I've attached the console ouput (which show no error). As for other test, I've booter 5 times on this kernel to be sure it was not by luck that it work. Thanks for this fix. ** Attachment added: Console output with kthread-defer-leaving v2 patch applied on 786235ee https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026655/+files/serial-ouput-patch-kthread-defer-leaving2.txt -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I've tested the final patch againt both 786235ee and tag v3.14-rc6 (fa389e22). It still works. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Applied patch on tag v3.14-rc6 (fa389e2), run kernel 4 four times, all worked. We seen on output (full output attached): [5.537193] mousedev: PS/2 mouse device common for all mice [ [9.776032] floppy0: no floppy controllers found [ 36.823538] Ignored SIGKILL by systemd-udevd [ 38.356082] scsi4 : ioc0: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16 [ 38.408276] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 9, phy 0, sas_addr 0x5000cca00f2e18fd [...] ** Attachment added: serial-output-patch-comment51.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4031962/+files/serial-output-patch-comment51.txt -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I've tested with kernel from comment #56. The kernel generated too much logs for IPMI serial console (which generated too much garbage), so I switched to a real serial console (and at 115kbauds). I've attached a archive with 3 runs (the last run it the most interesting I think): First run with serial console and a bigger kernel log buffer (log_buf_len=8M). The hope with larger log buffer was to catch full kernel message with dmesg once server is running. Sadly, after about 30 minutes, server was still printing stacks. Serial console capture attached under name 01-serial-capture-large-buffer.txt Second run, still with serial console but with default kernel log (no log_buf_len) This time, kernel booted fine (with exception to disk beeing discovered after rootdelay, but a ctrl+d resumed the boot process). Note: this boot generated WAY less message and booted. The only change is the log_buf_len=8M present or not. Serial console capture attached under name 02-serial-capture-default-buffer.txt Third run, this time with serial console disabled and very large kernel log buffer (log_buf_len=32M). Probably the most interesting one, dmesg was complete (include very first messages). It is 12 MB large ! Server booted without any issue (disk detected before the end of rootdelay). ** Attachment added: Logs when running kernel from comment #56 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4033864/+files/logs-3.14.0-031400rc7.201403191557.tar.xz -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Joseph, kernel freeze is planed in 7 days, which will arrive very fast. Do you think we could have a fix committed before this deadline ? I still didn't tested the firmware upgrade. I didn't tested it to keep a machine which exhibit the bug... upgrading firmware is okay with a local machine, but always trickier with remote server :( If their is something I can do for this issue, please tell me. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I've tested this new kernel, it boot without issue on the server (as usual, I booted three time the kernel to make it always works well). -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I see that trusty has now a kernel with the fix included: $ cat changelog.Debian linux (3.13.0-21.43) trusty; urgency=low [...] [ Tetsuo Handa ] * SAUCE: kthread: Do not leave kthread_create() immediately upon SIGKILL. [...] After a apt-get dist-upgrade to this kernel, I've successfully booted the server 5 times. So this kernel fix the issue. Thanks all for your work. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
** Attachment added: dmesg from a running system (no rootdelay, press control-d in initramfs) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/3970066/+files/dmesg.txt -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: New Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
** Attachment added: lspci -vnn on the server https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/3970067/+files/lspci.txt -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: New Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] [NEW] Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Public bug reported: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: console output (initramfs) when error occure https://bugs.launchpad.net/bugs/1276705/+attachment/3970065/+files/console.log -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: New Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I booted kernel with following common option : ro console=tty0 console=ttyS1,57600. When booted with rootdelay, it's rootdelay=45. The result are the following: * 3.13.0-7-generic, rootdelay = error * 3.13.0-7-generic, no rootdelay = Ok * 3.6, rootdelay = Ok * 3.12, rootdelay = Ok, tested twice. * 3.13.0-6-generic, rootdelay = error * 3.13.0-6-generic, no rootdelay = Error... then on next try Ok. The error is due to some race condition ? * Tested once more time 3.12 with rootdelay = Ok. * 3.13.0-7-generic, no rootdelay = Ok So the issue is between 3.12 and 3.13. Also on 3.13 with same condition (console=tty0 console=ttyS1,57600), sometime we got the error, sometime we didn't get the error. We always got the error with rootdelay set. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
None of them worked. All had the same issue. Tested: * v3.13-rc3 * v3.13-rc2 * v3.13-rc1 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc1-trusty/) -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Yes, I confirm that 3.12-saucy works. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Tested this kernel. It is NOT working, it has the issue. Extract of console log: [...] Linux version 3.12.0-031200-generic (jsalisbury@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402101715 SMP Thu Feb 13 14:58:01 UTC 2014 [...] [ 42.455969] scsi4: error handler thread failed to spawn, error = -12 [ 42.541170] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem [ 42.630361] BUG: unable to handle kernel NULL pointer dereference at 0060 [...] -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
This one is good, it is working: [...] Linux version 3.12.0-031200rc5-generic (jsalisbury@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402131150 SMP Thu Feb 13 16:54:49 UTC 2014 [...] -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
This kernel version is also good: Linux version 3.12.0-031200rc5-generic (jsalisbury@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402131403 SMP Thu Feb 13 19:04:57 UTC 2014 -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I can not test this kernel, it was only build for i386. The server is installed with amd64 :( Because of timezone difference we can only test one kernel per day, to speed up the bisect, I've done one by myself, the result is the following: $ git bisect log # bad: [6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae] Linux 3.13-rc1 # good: [5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52] Linux 3.12 git bisect start 'v3.13-rc1' 'v3.12' '--' 'drivers/scsi' # good: [53151bbb83f11b358ac94eddd81347c581dc51ea] [SCSI] lpfc 8.3.43: Fixed not processing task management IOCB response status git bisect good 53151bbb83f11b358ac94eddd81347c581dc51ea # good: [323f6226a816f0b01514d25fba5529e0e68636c3] Merge tag 'fcoe-3.13' into for-linus git bisect good 323f6226a816f0b01514d25fba5529e0e68636c3 [Above this point, I didn't build kernel. It was the result from your kernel. Bellow the result are from kernel compiled by myself] # bad: [2f466d33f5f60542d3d82c0477de5863b22c94b9] Merge tag 'pci-v3.13-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci git bisect bad 2f466d33f5f60542d3d82c0477de5863b22c94b9 # bad: [0910c0bdf7c291a41bc21e40a97389c9d4c1960d] Merge branch 'for-3.13/core' of git://git.kernel.dk/linux-block git bisect bad 0910c0bdf7c291a41bc21e40a97389c9d4c1960d # good: [0324e74534241f3f00910ec04ef67de1fe1542f4] Merge tag 'driver-core-3.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core git bisect good 0324e74534241f3f00910ec04ef67de1fe1542f4 # good: [e37459b8e2c7db6735e39e019e448b76e5e77647] Merge branch 'blk-mq/core' into for-3.13/core git bisect good e37459b8e2c7db6735e39e019e448b76e5e77647 # bad: [8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587] Merge branch 'for-linus-dma-masks' of git://git.linaro.org/people/rmk/linux-arm git bisect bad 8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587 # good: [7d35496dd98229cdf923238367fd3b3833fbde52] ARM: 7796/1: scsi: Use dma_max_pfn(dev) helper for bounce_limit calculations git bisect good 7d35496dd98229cdf923238367fd3b3833fbde52 # first bad commit: [8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587] Merge branch 'for-linus-dma-masks' of git://git.linaro.org/people/rmk/linux-arm From my bisect, the commit which introduced the error is 8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587. For information, to build the kernel I did the following: git remote add ubuntu-trusty git://kernel.ubuntu.com/ubuntu/ubuntu- trusty.git git checkout ubuntu-trusty/master -- debian git checkout ubuntu-trusty/master -- debian.master fakeroot debian/rules clean defaultconfigs fakeroot debian/rules binary-generic skipmodule=true Build area was cleaned after each build. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Ok, I've restarted a bisect without limitation on driver/scsi (git bisect start v3.13-rc1 v3.12). Git tell me it's 13 steps, will took some time, but during middle of next week we should have the bad commit. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Bisect finished. The first bad commit is 786235eeba0e1e85e5cbbb9f97d1087ad03dfa21. It seem more likely as this commit concerne kthread (and the first error is scsi4: error handler thread failed to spawn, error = -12). I also attach my bisect log if needed. ** Attachment added: bisect.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/3994538/+files/bisect.log -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Yes, this version is working: Linux version 3.13.0-12-generic (root@gomeisa) (gcc version 4.8.2 (Ubuntu 4.8.2-15ubuntu3) ) #32 SMP Mon Feb 24 18:50:37 UTC 2014 (Ubuntu 3.13.0-12.32-generic 3.13.4) -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Any update ? If i can help for something tell me, but I don't know kernel and can't do debuging of it by myself. I've tried to identify which ENOMEM cause the issue by added the printk (one before the first ENOMEM, one before the second ENOMEM, one after both ENOMEM)... but with just this change bug no longer occure ! I've already suspected that this bug is due to some race-condition because it seems to occure nearly everytime with rootdelay + serial console, and seems to sometime success when using neither rootdelay nor serial console. I've attached the diff of printk I've added. ** Patch added: printk.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4005322/+files/printk.patch -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
By more testing, you just mean reboot several time on this kernel to check that the isssue do not appear sometime ? During my bisect, I always booted 3 times on good kernel to make sure it was not by luck that the kernel worked. I also booted three time the kernel from comment #28. To double check, I just booted 5 times with this kernel and all 5 times worked. -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I've attached the debdiff patch for trusty. I'm building a backport for precise to test if slapd can start with this patch applied (the server on which the issue occure is running precise). -- 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/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more informations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
I have null pointer exception on a XPS 13 (9343) which trigger a kernel panic when I suspend the laptop. I can reproduce the issue nearly all times (3 / 4 tries), for this I need to generate network traffic (looking a video on Internet seem to be enough). After applying the patch mentioned above, I not longer have such kernel panic (done 6 tries without any kernel panic). So that patch seems to solve my kernel panic issue when suspending laptop. I will attach the debdiff I used to apply the patch. Without the patch (with bcmwl-kernel-source 6.30.223.248+bdcom- 0ubuntu2), I could product a kernel panic by doing: * Have network load (watching video on internet, downloading something, ...) * Suspend the laptop. On my test I did it with systemctl suspend from tty1 to capture the Call trace. System information: * Hardware : Dell XPS 13 (9343) * Ubuntu 15.04 amd64 * Bios A03 03/25/2015 * bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 (so wifi is using module wl) * lspci : 02:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) I will also attach picture of the screen after a crash + partial transcript the of kernel panic (see picture for the full information). ** Patch added: Patch to fix suspend kernel panic https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401631/+files/lp1415880.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: In Progress Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]=0014-null-pointer-crash.patch * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Attachment added: Kernel panic when suspending https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401634/+files/pierref-crash.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: In Progress Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]=0014-null-pointer-crash.patch * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Attachment added: lspci + software version https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401636/+files/pierref-system-info.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: In Progress Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]=0014-null-pointer-crash.patch * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Attachment added: Kernel panic when suspending https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401633/+files/pierref-crash.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: In Progress Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]=0014-null-pointer-crash.patch * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+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 1518457] Re: kswapd0 100% CPU usage
If the verification apply also on 16.04, it does fix the issue. We had a server that triggered the bug at least once a day (I suspect unattended-upgrade run every morning to trigger it). Since the upgrade - 2 days and half ago - the server had no issue. -- 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/1518457 Title: kswapd0 100% CPU usage Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Invalid Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+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
