Bug#441206: linux-image-2.6.22-2-k7: Firewire 400 external HD fails to be recognized
On Fri, Sep 07, 2007 at 06:36:34PM +0200, maximilian attems wrote:
[...]
> can you be so kind and test tomorrow's build,
> just to know that git firewire doesn't rebork. ;)
I've just installed and rebooted today's kernel build
(2.6.23~rc5-1~experimental.1~snapshot.9473), and... FIREWIRE IS STILL
WORKING !!! Here are the syslog messages:
Sep 8 12:49:19 monk kernel: scsi0 : SBP-2 IEEE-1394
Sep 8 12:49:19 monk kernel: firewire_core: created new fw device fw1 (0 config rom retries, S400)
Sep 8 12:49:19 monk kernel: firewire_core: phy config: card 0, new root=ffc0, gap_count=5
Sep 8 12:49:21 monk kernel: firewire_sbp2: orb reply timed out, rcode=0x11
Sep 8 12:49:21 monk kernel: firewire_sbp2: logged in to fw1.1 LUN 0000 (1 retries)
Sep 8 12:49:27 monk kernel: firewire_sbp2: sbp2_scsi_abort
Sep 8 12:49:32 monk kernel: scsi 0:0:0:0: Direct-Access WD 5000AAKS Externa 107a PQ: 0 ANSI: 4
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Write Protect is off
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Write Protect is off
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Sep 8 12:49:32 monk kernel: sda: sda1 sda2
Sep 8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Attached SCSI disk
This snapshot of the firewire_sbp2 module still doesn't have the
'workaround' parameter. Here's the dmesg message:
firewire_sbp2: Unknown parameter `workaround'
I'm currently tracking unstable. When will this kernel snapshot hit
unstable ? May I bump into problems if I go on booting kernel snapshot
and continue to track unstable ?
Thanks a lot for fixing this, Maks !
Paulo
Reply to: