Bug#441206: linux-image-2.6.22-2-k7: Firewire 400 external HD fails to be recognized

2007-09-07 Thread Paulo Marcel Coelho Aragão
Package: linux-image-2.6.22-2-k7
Version: 2.6.22-4
Severity: important

My Western Digital 500GB MyBook external HD fails to be recognized when
I plug it through the Firewire 400 port. The following errors appear on
the syslog:

Sep  7 09:41:18 monk kernel: scsi0 : SBP-2 IEEE-1394
Sep  7 09:41:18 monk kernel: firewire_core: created new fw device fw1 (0 config 
rom retries)
Sep  7 09:41:18 monk kernel: firewire_sbp2: logged in to sbp2 unit fw1.1 (0 
retries)
Sep  7 09:41:18 monk kernel: firewire_sbp2:  - management_agent_address:
0xf003
Sep  7 09:41:18 monk kernel: firewire_sbp2:  - command_block_agent_address: 
0xf010
Sep  7 09:41:18 monk kernel: firewire_sbp2:  - status write address:
0x0001
Sep  7 09:41:24 monk kernel: firewire_sbp2: sbp2_scsi_abort
Sep  7 09:41:29 monk kernel: scsi 0:0:0:0: Direct-Access WD   5000AAKS 
Externa 107a PQ: 0 ANSI: 4
Sep  7 09:41:29 monk kernel: firewire_core: phy config: card 0, new root=ffc0, 
gap_count=63
Sep  7 09:41:29 monk kernel: firewire_sbp2: management write failed, rcode 0x12
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] READ CAPACITY failed
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BUS_BUSY 
driverbyte=DRIVER_OK,SUGGEST_OK
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] Sense not available.
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] Write Protect is off
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] Asking for cache data failed
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write 
through
Sep  7 09:41:29 monk kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Sep  7 09:41:29 monk kernel: firewire_sbp2: reconnected to unit fw1.1 (1 
retries)

The same HD also failed to be recognized by previous kernel version
linux-image-2.6.22-1-k7, but the error messages were different. This is
filed under bug #435224.

It's correctly recognized if I plug it through the USB port.

Regards,
Paulo

-- Package-specific info:
** Version:
Linux version 2.6.22-2-k7 (Debian 2.6.22-4) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 01:02:37 UTC 
2007

** Not tainted

** Kernel log:
Real Time Clock Driver v1.12ac
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
input: PC Speaker as /class/input/input2
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED]
bcm43xx driver
Yenta: ISA IRQ mask 0x0ef8, PCI irq 16
Socket status: 3006
Yenta: Raising subordinate bus# of parent bus (#03) from #04 to #07
pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff
cs: IO port probe 0xa000-0xafff: clean.
pcmcia: parent PCI bridge Memory window: 0xb020 - 0xb02f
pcmcia: parent PCI bridge Memory window: 0x6000 - 0x63ff
sdhci: SDHCI controller found at :03:04.4 [104c:8034] (rev 0)
ACPI: PCI Interrupt :03:04.4[D] - GSI 23 (level, low) - IRQ 22
mmc0: SDHCI at 0xb020a000 irq 22 DMA
mmc1: SDHCI at 0xb0208c00 irq 22 DMA
mmc2: SDHCI at 0xb0208800 irq 22 DMA
ACPI: PCI Interrupt :00:14.6[B] - GSI 17 (level, low) - IRQ 17
MC'97 0 converters and GPIO not ready (0x1)
ACPI: PCI Interrupt :03:02.0[A] - GSI 21 (level, low) - IRQ 21
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
ACPI: PCI Interrupt :00:14.5[B] - GSI 17 (level, low) - IRQ 17
Synaptics Touchpad, model: 1, fw: 6.2, id: 0x23a0b1, caps: 0xa04713/0x20
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x3e0-0x4ff: clean.
cs: IO port probe 0x820-0x8ff: excluding 0x878-0x87f
input: SynPS/2 Synaptics TouchPad as /class/input/input3
cs: IO port probe 0xc00-0xcf7: excluding 0xc00-0xc07 0xc10-0xc17 0xc50-0xc57 
0xc68-0xc6f 0xcd0-0xcdf
cs: IO port probe 0xa00-0xaff: clean.
Adding 1951856k swap on /dev/hda5.  Priority:-1 extents:1 across:1951856k
EXT3 FS on hda3, internal journal
loop: module loaded
ACPI: Battery Slot [BAT1] (battery present)
fuse init (API version 7.8)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 

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

2007-07-30 Thread Paulo Marcel Coelho Aragão
Package: linux-image-2.6.22-1-k7
Version: 2.6.22-3
Severity: normal

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:
0xf003
Jul 30 03:18:43 monk kernel: firewire_sbp2:  - command_block_agent_address: 
0xf010
Jul 30 03:18:43 monk kernel: firewire_sbp2:  - status write address:
0x0001
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: