|
|
|
|
Freitag, Januar 25, 2008
Again I got a little hardware problem :)
This time it's the new shiny firewire harddisk i bought recently to do backups.
If you connect your external firewire harddisk and get something like the following in your linux kernel message log then my patch could be something for you.
firewire_core: created new fw device fw1 (5 config rom retries, S400)
firewire_core: phy config: card 0, new root=ffc0, gap_count=5
scsi5 : SBP-2 IEEE-1394
scsi6 : SBP-2 IEEE-1394
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: status write for unknown orb
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: status write for unknown orb
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_core: Unsolicited response (source ffc0, tlabel 3)
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: status write for unknown orb
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: status write for unknown orb
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_core: Unsolicited response (source ffc0, tlabel 6)
firewire_sbp2: status write for unknown orb
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: status write for unknown orb
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: failed to login to fw1.0 LUN 0000
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: failed to login to fw1.1 LUN 0001
firewire_sbp2: status write for unknown orb
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: released fw1.1
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: released fw1.0
The problem with my disk (it's a Western Digital MyBook Studio Edition disk) is the spinup time. The disk needs some time to recover from suspend mode and the disk controller seems to block communication while this happens. The simple idea to get this sorted out is to increase the timeout the driver waits for the drive to answer. I increased the timeout from 2000ms to 5000ms and just get one error message at the beginning, but it works good after that first timeout. The patch is against Linux 2.6.24 (yes this time I am pretty up to date :) ).
Download the Firewire timeout patch here. You need to rebuild your kernel though. It looks like that then:
irewire_ohci: Added fw-ohci device 0000:05:04.0, OHCI version 1.10
firewire_core: created new fw device fw0 (0 config rom retries, S400)
scsi7 : SBP-2 IEEE-1394
scsi8 : SBP-2 IEEE-1394
firewire_core: created new fw device fw1 (0 config rom retries, S400)
firewire_core: phy config: card 0, new root=ffc0, gap_count=5
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: orb reply timed out, rcode=0x11
firewire_sbp2: status write for unknown orb
firewire_sbp2: logged in to fw1.0 LUN 0000 (1 retries)
scsi 7:0:0:0: Direct-Access WD My Book 1025 PQ: 0 ANSI: 4
sd 7:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdh] Write Protect is off
sd 7:0:0:0: [sdh] Mode Sense: 10 00 00 00
sd 7:0:0:0: [sdh] Cache data unavailable
sd 7:0:0:0: [sdh] Assuming drive cache: write through
sd 7:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdh] Write Protect is off
sd 7:0:0:0: [sdh] Mode Sense: 10 00 00 00
sd 7:0:0:0: [sdh] Cache data unavailable
sd 7:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 7:0:0:0: [sdh] Attached SCSI disk
sd 7:0:0:0: Attached scsi generic sg8 type 0
firewire_sbp2: error status: 0:4
firewire_sbp2: error status: 0:4
SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem sdh1
Ending clean XFS mount for filesystem: sdh1
firewire_sbp2: error status: 0:4
firewire_core: Unsolicited response (source ffc0, tlabel 9)
firewire_core: Unsolicited response (source ffc0, tlabel a)
firewire_core: Unsolicited response (source ffc0, tlabel b)
firewire_core: Unsolicited response (source ffc0, tlabel c)
firewire_sbp2: status write for unknown orb
firewire_sbp2: status write for unknown orb
firewire_sbp2: error status: 0:4
firewire_sbp2: error status: 0:4
firewire_sbp2: failed to login to fw1.1 LUN 0001
firewire_sbp2: sbp2_scsi_abort
XFS mounting filesystem sdh1
Ending clean XFS mount for filesystem: sdh1
The message that the driver cannot log into fw1.1 seems logical, since I've only one device connected but the disk has 2 ports to allow extending the bus with other devices
Eingestellt von
dunkelstern
|
|
|
Labels:
archlinux
,
computer
,
geekig
,
linux
,
programmieren
,
technisch
|
|
0 Kommentare:
Kommentar veröffentlichen