← Back to team overview

kernel-packages team mailing list archive

[Bug 1394032] [NEW] Trusty isci module doesn't handle timeouts properly

 

Public bug reported:

I'm currently running linux 3.13.0-39 on trusty with a disks plugged
into an Intel C602 SATA/SAS controller.  Occasionally, a timeout and/or
SAS event (I'm not 100% sure which..) isn't handled properly ('Unhandled
error code') and  the kernel gets a bit upset.

I have 12 different hosts with this controller and disk combination and
all display the same behaviour (dmesg output):

[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff8808434fa600 timed out
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff880843673d00 timed out
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff88105081bc00 timed out
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff88084378e100 timed out
[Tue Nov 18 16:56:10 2014] sas: Enter sas_scsi_recover_host busy: 4 failed: 4
[Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: cmd error handler
[Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: dev error handler
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
[Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
[Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 9e 77 60 00 00 08 00
[Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 77494112
[Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 261733 (offset 0 size 0 starting block 5061868)
[Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 5061868
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
[Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
[Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 0f d0 e0 00 00 08 00
[Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 68145376
[Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 261710 (offset 0 size 0 starting block 3893276)
[Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 3893276
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
[Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
[Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 f8 00 00 08 00
[Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654520
[Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 1081919
[Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
[Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
[Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 58 00 00 08 00
[Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654360
[Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 1081899
[Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
[Tue Nov 18 16:56:10 2014] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "apport.linux-image-3.13.0-39-generic.n40iuzke.apport"
   https://bugs.launchpad.net/bugs/1394032/+attachment/4263386/+files/apport.linux-image-3.13.0-39-generic.n40iuzke.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/1394032

Title:
  Trusty isci module doesn't handle timeouts properly

Status in “linux” package in Ubuntu:
  New

Bug description:
  I'm currently running linux 3.13.0-39 on trusty with a disks plugged
  into an Intel C602 SATA/SAS controller.  Occasionally, a timeout
  and/or SAS event (I'm not 100% sure which..) isn't handled properly
  ('Unhandled error code') and  the kernel gets a bit upset.

  I have 12 different hosts with this controller and disk combination
  and all display the same behaviour (dmesg output):

  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff8808434fa600 timed out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff880843673d00 timed out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff88105081bc00 timed out
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] command ffff88084378e100 timed out
  [Tue Nov 18 16:56:10 2014] sas: Enter sas_scsi_recover_host busy: 4 failed: 4
  [Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: cmd error handler
  [Tue Nov 18 16:56:10 2014] sas: ata7: end_device-7:0: dev error handler
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 9e 77 60 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 77494112
  [Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 261733 (offset 0 size 0 starting block 5061868)
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 5061868
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 04 0f d0 e0 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 68145376
  [Tue Nov 18 16:56:10 2014] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -5 writing to inode 261710 (offset 0 size 0 starting block 3893276)
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 3893276
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 f8 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654520
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 1081919
  [Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] Unhandled error code
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg]
  [Tue Nov 18 16:56:10 2014] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
  [Tue Nov 18 16:56:10 2014] sd 7:0:0:0: [sdg] CDB:
  [Tue Nov 18 16:56:10 2014] Write(10): 2a 00 02 b8 a1 58 00 00 08 00
  [Tue Nov 18 16:56:10 2014] end_request: I/O error, dev sdg, sector 45654360
  [Tue Nov 18 16:56:10 2014] Buffer I/O error on device dm-2, logical block 1081899
  [Tue Nov 18 16:56:10 2014] lost page write due to I/O error on dm-2
  [Tue Nov 18 16:56:10 2014] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1

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


Follow ups

References