ieee1394: Error parsing configrom for node 0-00:1023

From: Justin Mattock
Date: Mon Jul 14 2008 - 01:35:29 EST


Hello;
I'm seeing this: ieee1394: Error parsing configrom for node 0-00:1023
and sd 4:0:0:0: [sdb] Missing header in MODE_SENSE response
when mounting a firelite hardisk with mac osx installed on it.
Keep in mind I don't know if disabling Journal on that
partition is what is causing this or not. irregardless of
these messages I am able to mount the drive and
view and change all of my mac osx files no problem.(clip of dmesg)

[ 4165.705384] ieee1394: Error parsing configrom for node 0-00:1023
[ 4165.705847] ieee1394: Node changed: 0-00:1023 -> 0-01:1023
[ 4170.577205] ieee1394: Node added: ID:BUS[0-00:1023] GUID[00d0010d0001eaa9]
[ 4170.759138] scsi4 : SBP-2 IEEE-1394
[ 4171.773840] ieee1394: sbp2: Logged into SBP-2 device
[ 4171.773865] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max
payload [2048]
[ 4171.775022] scsi 4:0:0:0: Direct-Access SmartDsk FireLite
4.70 PQ: 0 ANSI: 0
[ 4171.775614] sd 4:0:0:0: [sdb] 117210240 512-byte hardware sectors (60012 MB)
[ 4171.776654] sd 4:0:0:0: [sdb] Write Protect is off
[ 4171.776654] sd 4:0:0:0: [sdb] Mode Sense: 86 0b 00 02
[ 4171.777580] sd 4:0:0:0: [sdb] Missing header in MODE_SENSE response
[ 4171.778870] sd 4:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 4171.785750] sd 4:0:0:0: [sdb] 117210240 512-byte hardware sectors (60012 MB)
[ 4171.785750] sd 4:0:0:0: [sdb] Write Protect is off
[ 4171.785750] sd 4:0:0:0: [sdb] Mode Sense: 86 0b 00 02
[ 4171.785750] sd 4:0:0:0: [sdb] Missing header in MODE_SENSE response
[ 4171.785750] sd 4:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 4171.785750] sdb: sdb1 sdb2
[ 4171.898425] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 4171.898425] sd 4:0:0:0: Attached scsi generic sg2 type 0

kernel = latest git(torvalds)
regards;

--
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/