Bug#435224: linux-image-2.6.22-1-k7: I/O errors when plugging external hd via Firewire 400

To: Paulo Marcel Coelho Aragão <marcelpaulo@gmail.com>, 435224@bugs.debian.org
Subject: Bug#435224: linux-image-2.6.22-1-k7: I/O errors when plugging external hd via Firewire 400
From: maximilian attems <max@stro.at>
Date: Mon, 30 Jul 2007 10:22:38 +0200
Message-id: <[🔎] 20070730082238.GE13713@baikonur.stro.at>
Reply-to: maximilian attems <max@stro.at>, 435224@bugs.debian.org
In-reply-to: <[🔎] 20070730062937.15960.97656.reportbug@monk.cortazar>
References: <[🔎] 20070730062937.15960.97656.reportbug@monk.cortazar>

On Mon, Jul 30, 2007 at 03:29:37AM -0300, Paulo Marcel Coelho Aragão wrote:
> 
> When I plug a Western Digital 500GB MyBook external HD through the
> Firewire 400 interface, the following errors appear on the syslog:
> 
> Jul 30 03:18:31 monk kernel: firewire_sbp2: management write failed, rcode 0x13
> Jul 30 03:18:31 monk kernel: firewire_sbp2: removed sbp2 unit fw1.1
> Jul 30 03:18:43 monk kernel: scsi3 : SBP-2 IEEE-1394
> Jul 30 03:18:43 monk kernel: firewire_core: created new fw device fw1 (0 config rom retries)
> Jul 30 03:18:43 monk kernel: firewire_sbp2: logged in to sbp2 unit fw1.1 (0 retries)
> Jul 30 03:18:43 monk kernel: firewire_sbp2:  - management_agent_address:    0xfffff0030000
> Jul 30 03:18:43 monk kernel: firewire_sbp2:  - command_block_agent_address: 0xfffff0100000
> Jul 30 03:18:43 monk kernel: firewire_sbp2:  - status write address:        0x000100000000
> Jul 30 03:18:49 monk kernel: firewire_sbp2: sbp2_scsi_abort
> Jul 30 03:18:54 monk kernel: scsi 3:0:0:0: Direct-Access     WD       5000AAKS Externa 107a PQ: 0 ANSI: 4
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Write Protect is off
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Mode Sense: 11 00 00 00
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Cache data unavailable
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Write Protect is off
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Mode Sense: 11 00 00 00
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Cache data unavailable
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
> Jul 30 03:18:54 monk kernel:  sdb: sdb1 sdb2
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
> Jul 30 03:18:54 monk kernel: firewire_core: phy config: card 0, new root=ffc0, gap_count=63
> Jul 30 03:18:54 monk kernel: firewire_sbp2: management write failed, rcode 0x12
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976772992
> Jul 30 03:18:54 monk kernel: printk: 36 messages suppressed.
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 122096624
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976772992
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 122096624
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976772992
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 122096624
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 122096645
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 122096645
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 122096645
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: Buffer I/O error on device sdb, logical block 122096645
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773104
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773152
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 976773160
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: sd 3:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
> Jul 30 03:18:54 monk kernel: end_request: I/O error, dev sdb, sector 0
> Jul 30 03:18:54 monk kernel: firewire_sbp2: reconnected to unit fw1.1 (1 retries)
> 
> These error messages weren't generated with the previous kernel version.
> I did a dist-upgrade today and noticed them when I plugged my external
> HD.

hmm interesting
yeah they are due to the new firewire stack.
it be interesting if you could test latest -rc1 + git7
if they are still reproducible there and if yes holler upstream.

to bad we have no 2.6.23-rcX snapshots yet,
will come soon i hope..

regards

-- 
maks

Reply to:

Follow-Ups:
- Bug#435224: linux-image-2.6.22-1-k7: I/O errors when plugging external hd via Firewire 400
  - From: Paulo Marcel Coelho Aragao <marcelpaulo@gmail.com>

References:
- Bug#435224: linux-image-2.6.22-1-k7: I/O errors when plugging external hd via Firewire 400
  - From: Paulo Marcel Coelho Aragão <marcelpaulo@gmail.com>

Prev by Date: Bug#435227: linux-image-2.6.22-1-686: yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal)
Next by Date: Bug#433307: linux-image-2.6-k7: results of git bisect
Previous by thread: Bug#435224: linux-image-2.6.22-1-k7: I/O errors when plugging external hd via Firewire 400
Next by thread: Bug#435224: linux-image-2.6.22-1-k7: I/O errors when plugging external hd via Firewire 400
Index(es):
- Date
- Thread