[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
Maciej Puzio, it's strongly preferred one reports on a per hardware basis, as it's cheap to mark something a duplicate of another if determined as such. -- 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/1328984 Title: [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: Incomplete Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv input:b0019vp0001e-r0,1,k74,ramlsfw' [771] udevd[699]: timeout: killing '/sbin/modprobe -bv dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:' [708] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k71,72,73,74,77,80,82,83,85,86,87,88,89,8A,8B,8C,8E,8F,90,96,98,9B,9C,9E,9F,A1,A3,A4,A5,A6,A7,A8,A9,AB,AC,AD,AE,B1,B2,B5,CE,CF,D0,D1,D2,D4,D8,D9,DB,E4,EA,EB,F1,100,161,162,166,16A,16E,172,174,176,178,179,17A,17B,17C,17D,17F,180,182,182,185,188,189,18C,18D,18E,18F,190,191,192,193,195,198,199,19A,1A9,1A1,1A2,1A3,1A4,1A5,1A6,1A7,1A8,1A9,1AA,1AB,1AC,1AD,1AE,1B0,1B1,1B7,1BA,r6,a20,m4,lsfw' [1678]
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
Maciej Puzio, could you please test the latest upstream kernel available from the first line at the top page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-3.15 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: kernel udev usb ** Tags added: 1.12.0 latest-bios- needs-bisect regression-update ** Summary changed: - Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card + [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card -- 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/1328984 Title: [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: Incomplete Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
I'm attaching the file generated by command: apport-cli -f -p linux --save bug1328984.apport This was done with the machine running 12.04 Server with kernel 3.2.0-63. May I ask for the reply to my question about the results of testing the problem on a different hardware? (The regression has been reproduced, but symptoms are somewhat different, and I worry about confusion which may result from mixing discussion about two hardware configurations. On the other hand, I am reluctant to start a new bug report, as this appears to be a single bug.) ** Attachment added: Result of apport-cli https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328984/+attachment/4130995/+files/bug1328984.apport -- 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/1328984 Title: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: Incomplete Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv input:b0019vp0001e-r0,1,k74,ramlsfw' [771] udevd[699]: timeout: killing '/sbin/modprobe -bv
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
Maciej Puzio: 1) The purpose of the apport-collect is to gather the necessary debug information about your hardware, not provide logs about the crash. 2) One may utilize https://help.ubuntu.com/community/ReportingBugs #Filing_bugs_when_off-line to attach the file to this report. ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1328984 Title: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: Incomplete Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv input:b0019vp0001e-r0,1,k74,ramlsfw' [771] udevd[699]: timeout: killing '/sbin/modprobe -bv dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:' [708] udevd[529]: timeout: killing '/sbin/modprobe -bv
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
I am unable to submit apport-collected data due to what appears to be numerous bugs in apport tools: 1. Submitting data directly from the affected machine is not possible due to apport not being able to connect through a proxy. 2. Following instructions on referenced page to submit previously created .apport file using ubuntu-bug does not work, because ubuntu-bug ignores file specified in -c or --crash-file parameter, and proceeds to gather system information from the machine on which it is running. As this is a wrong machine, I had no choice but to cancel the submission. 3. In addition, ubuntu-bug generates the following error: No packages found matching linux. ERROR: hook /usr/share/apport/general-hooks/cloud_archive.py crashed At this point debugging apport is not my priority. I would be grateful if you indicate an alternative way to proceed. -- 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/1328984 Title: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: Incomplete Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
Maciej Puzio, could you please boot into 14.04 Server via http://releases.ubuntu.com/trusty/ (or 10.04/other release if that doesn't work), gather the apport-collect file, use a USB stick to move the data to another computer, and attach the file manually to this report? -- 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/1328984 Title: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: Incomplete Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv input:b0019vp0001e-r0,1,k74,ramlsfw' [771] udevd[699]: timeout: killing '/sbin/modprobe -bv dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:' [708] udevd[529]: timeout: killing '/sbin/modprobe -bv
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
** Project changed: software-center = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1328984 Title: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux-meta” package in Ubuntu: New Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv input:b0019vp0001e-r0,1,k74,ramlsfw' [771] udevd[699]: timeout: killing '/sbin/modprobe -bv dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:' [708] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k71,72,73,74,77,80,82,83,85,86,87,88,89,8A,8B,8C,8E,8F,90,96,98,9B,9C,9E,9F,A1,A3,A4,A5,A6,A7,A8,A9,AB,AC,AD,AE,B1,B2,B5,CE,CF,D0,D1,D2,D4,D8,D9,DB,E4,EA,EB,F1,100,161,162,166,16A,16E,172,174,176,178,179,17A,17B,17C,17D,17F,180,182,182,185,188,189,18C,18D,18E,18F,190,191,192,193,195,198,199,19A,1A9,1A1,1A2,1A3,1A4,1A5,1A6,1A7,1A8,1A9,1AA,1AB,1AC,1AD,1AE,1B0,1B1,1B7,1BA,r6,a20,m4,lsfw' [1678] After pressing Ctrl-Alt-Delete, the above messages continue to appear for a few seconds, and after that the
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu) -- 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/1328984 Title: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: New Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv input:b0019vp0001e-r0,1,k74,ramlsfw' [771] udevd[699]: timeout: killing '/sbin/modprobe -bv dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:' [708] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k71,72,73,74,77,80,82,83,85,86,87,88,89,8A,8B,8C,8E,8F,90,96,98,9B,9C,9E,9F,A1,A3,A4,A5,A6,A7,A8,A9,AB,AC,AD,AE,B1,B2,B5,CE,CF,D0,D1,D2,D4,D8,D9,DB,E4,EA,EB,F1,100,161,162,166,16A,16E,172,174,176,178,179,17A,17B,17C,17D,17F,180,182,182,185,188,189,18C,18D,18E,18F,190,191,192,193,195,198,199,19A,1A9,1A1,1A2,1A3,1A4,1A5,1A6,1A7,1A8,1A9,1AA,1AB,1AC,1AD,1AE,1B0,1B1,1B7,1BA,r6,a20,m4,lsfw' [1678] After pressing Ctrl-Alt-Delete, the above messages continue to appear for a few seconds, and after that the following
[Kernel-packages] [Bug 1328984] Re: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card
I am unable to run the apport-collect command for two reasons: 1. The bug in question renders the machine unbootable. To boot the machine and run apport-collect, it is necessary to change either the software or hardware configuration. This would create an environment in which bug is not reproducible. 2. Two affected machines are servers located behind a corporate proxy. Apport-collect does not allow transmission through a proxy. As instructed, I am changing the status to 'Confirmed'. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/1328984 Title: Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card Status in “linux” package in Ubuntu: Confirmed Bug description: A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64 resulted in unbootable system on two machines. Further testing revealed that kernel fails while initializing HighPoint RocketU 1144C USB 3.0 controller. This is a PCIe x4 add-in card that contains four USB 3.0 ports, each equipped with its own controller. The card did and does work without any problems with kernel 3.2.0-63 and earlier. Prior to installing kernel 3.2.0-64 there were neither hardware nor software problems with either of the machines. Steps to reproduce: apt-get dist-upgrade sync reboot Result: system fails to boot. The workaround is to revert to kernel 3.2.0-63 or to remove the RocketU card. Hardware description (same on both machines): Dell PowerEdge R510 PERC6/i RAID controller 64GB RAM DDR3 ECC registered Dual CPU: Intel Xeon X5660 2.80GHz HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA Operating system (identical on both machines): Ubuntu 12.04.4 LTS Linux 3.2.0-64-generic x86_64 Drives: sda - logical drive on PERC6/i, OS sdb - logical drive on PERC6/i, data sdc - Areca 5040 external RAID connected by USB3 to RocketU card sdd - Areca 5040 external RAID connected by USB3 to RocketU card sde - Areca 5040 external RAID connected by USB3 to RocketU card Symptoms: System boots normally until initialization of Areca drives connected to the RocketU card. The following messages are displayed on screen when booting without quiet and with debug options. These are last messages of a typical part of the boot sequence. Following it is a ~2 minute lag when no messages are displayed. [Please note that no trace of the boot progress gets recorded in system logs, and messages on screen scroll very fast. I had to record the boot progress with a high framerate camera, and even so some messages scrolled too fast and were not recorded. The following is a manual transcript of fragments of these videos; please forgive inevitable typos.] [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5 PQ: 0 ANSI: 5 [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0 [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16). [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3 PQ: 0 ANSI: 5 [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0 [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16). [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 TB/19.0 TiB) [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7 PQ: 0 ANSI: 5 [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0 [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16). [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 TB/16.3 TiB) [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 46874620k After a two minute delay, the following messages appear in an infinite loop. Please note that these messages appear in a somewhat random sequence, and not all messages appear on every boot. The only thing that works at this point is Ctrl-Alt-Delete. udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774] udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776] udevd[529]: timeout: killing '/sbin/modprobe -bv input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642] udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655] udevd[508]: timeout: killing '/sbin/modprobe -bv pci:v80864342Esvsdbc00sc00i00' [512] udevd[494]: timeout: killing '/sbin/modprobe -bv input:b0019vp0001e-r0,1,k74,ramlsfw' [771] udevd[699]: timeout: killing '/sbin/modprobe -bv dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:' [708] udevd[529]: timeout: killing '/sbin/modprobe -bv
