kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Chun-Hung Chen, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (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-v3.13-rc6

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.

** Changed in: linux (Ubuntu)
       Status: Triaged => 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/1060760

Title:
  Hot plug and unplug causes system hangs

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  We are testing our hardware stability with hot plug and unplug several
  times and it causes our system hangs.

  The SAS Controller is Intel C600 with driver version 1.0.0. The syslog
  related to the issue listed below.

  Oct  2 16:10:41 MyTestBox kernel: : [354243.488743] sas: command 0xffff881016964900, task 0xffff881014781a40, timed out: BLK_EH_NOT_HANDLED
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488766] sas: Enter sas_scsi_recover_host
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488772] sas: trying to find task 0xffff881014781a40
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488776] sas: sas_scsi_find_task: aborting task 0xffff881014781a40
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488780] sas: sas_scsi_find_task: querying task 0xffff881014781a40
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488784] sas: sas_scsi_find_task: task 0xffff881014781a40 at LU
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488787] sas: task 0xffff881014781a40 is at LU: lu recover
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488791] sas: eh: device 1000000012345674 LUN 0 has the task
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488803] sas: task 0xffff881014781a40 is not at LU: I_T recover
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488806] sas: I_T nexus reset for dev 1000000012345674
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488891] isci 0000:03:00.0: sci_remote_node_context_event_handler: invalid state 5
  Oct  2 16:10:41 MyTestBox kernel: : [354243.488900] isci 0000:03:00.0: isci_host_completion_routine: Error - request/task = ffff881014506000/ffff881014781a40
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517338] isci 0000:03:00.0: isci_port_perform_hard_reset: iport = ffff881014412b38; hard reset failed (0x21) - driving explicit link fail for all phys
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517434] isci 0000:03:00.0: sci_port_remove_phy: in wrong state: 7
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517450] isci 0000:03:00.0: sci_remote_node_context_suspend: invalid state 3
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517455] isci 0000:03:00.0: sci_port_hard_reset: in wrong state: 7
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517459] isci 0000:03:00.0: isci_port_perform_hard_reset: iport = ffff881014412b38; sci_port_hard_reset call failed 0x8
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517536] isci 0000:03:00.0: isci_port_perform_hard_reset: iport = ffff881014412b38; hard reset failed (0x21) - driving explicit link fail for all phys
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517625] isci 0000:03:00.0: sci_port_remove_phy: in wrong state: 7
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517632] isci 0000:03:00.0: sci_remote_node_context_resume: invalid state 4
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517636] sas: clearing nexus for port:2
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517639] sas: clear nexus ha
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517641] sas: error from  device 1000000012345674, LUN 0 couldn't be recovered in any way
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517646] sas: sas_ata_task_done: SAS error 40
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517652] sas: --- Exit sas_eh_handle_sas_errors -- clear_q
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517658] ata8: sas eh calling libata port error handler
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517677] ata11: sas eh calling libata port error handler
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517685] ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517731] ata11.00: failed command: IDENTIFY DEVICE
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517778] ata11.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517780]          res 01/04:00:00:00:00/00:00:00:00:00/00 Emask 0x12 (ATA bus error)
  Oct  2 16:12:01 MyTestBox kernel: : [354268.517911] ata11.00: status: { ERR }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1060760/+subscriptions