Bug 119572 - [sbp] PowerBook not accessable when in target mode
Summary: [sbp] PowerBook not accessable when in target mode
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: Bugmeister
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-11 21:00 UTC by Sean Bruno
Modified: 2025-01-28 12:01 UTC (History)
0 users

See Also:


Attachments
fwdebug.out (54.30 KB, application/octet-stream)
2013-05-04 20:46 UTC, Justin Hibbits
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Bruno 2008-01-11 21:00:02 UTC
When attempting to access an Apple Powerbook when it is placed into
target mode, I am unable to access the drive, but it is detected as
an SBP-2 device.

I cannot read the drive in any way, tried diskinfo, fdisk and dd.


Output when sbp is compiled with debugging on:

source # ls -la /dev/da*
crw-r-----  1 root  operator    0,  94 Jan 10 11:24 /dev/da0
source # fdisk /dev/da0
sbp0:0:0 ORB status src:1 resp:0 dead:1 len:2 stat:0 orb:0002ce634
sbp0:0:0 No additional information to report
sbp0:0:0 XPT_SCSI_IO: cmd: 25 00 00 00 00 00 00 00 00 00, flags: 0x40, 10b cmd/8b data/32b sense
sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 2 code 3a qlfr 0 len 2
sbp0:0:0 sbp_agent_reset
(da0:sbp0:0:0:0): error 6
(da0:sbp0:0:0:0): Unretryable Error
Opened disk da0 -> 6
fdisk: cannot open disk /dev/da0: Device not configured
source # fwohci0: BUS reset
sbp_post_busreset
fwohci0: node_id=0xc800ffc0, gen=5, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
sbp_post_explore (sbp_cold=0)
sbp_post_explore: EUI:001d4ffffe78600c not attached, state=3.
target 0 lun 0 found
target 0 lun 0 found
sbp0:0:0 lost target
fwohci0: BUS reset
sbp_post_busreset
fwohci0: node_id=0x8800ffc0, gen=6, non CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me)
firewire0: root node is not cycle master capable
firewire0: bus manager 0 (me)
fwohci0: too many cycle lost, no cycle master presents?
sbp_post_explore (sbp_cold=0)
sbp_post_explore: EUI:001d4ffffe78600c attached
target 0 lun 0 found
target 0 lun 0 found
sbp0:0:0 ordered:0 type:14 EUI:001d4ffffe78600c node:1 speed:2 maxrec:0
sbp0:0:0 'AAPL' '' ''
sbp0:0:0 RECONNECT
sbp0:0:0 mgm orb: 002ce76c
sbp0:0:0 reconnect failed
sbp_login: sec = 0 usec = 679651 ticks = 679
sbp0:0:0 LOGIN
sbp0:0:0 mgm orb: 002ce8a4
sbp0:0:0 login: len 16, ID 1, cmd 0000fffff0ef1020, recon_hold 0
sbp0:0:0 sbp_busy_timeout
sbp0:0:0 sbp_agent_reset
sbp0:0:0 sbp_do_attach
sbp0:0:0 sbp_cam_scan_target
sbp0:0:0 ORB status src:1 resp:0 dead:1 len:2 stat:0 orb:0002ce9dc
sbp0:0:0 No additional information to report
sbp0:0:0 XPT_SCSI_IO: cmd: 00 00 00 00 00 00 00 00 00 00, flags: 0xc0, 6b cmd/0b data/32b sense
sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 2 code 3a qlfr 0 len 2
sbp0:0:0 sbp_agent_reset
(probe0:sbp0:0:0:0): error 6
(probe0:sbp0:0:0:0): Unretryable Error
sbp0:0:0 ORB status src:1 resp:0 dead:1 len:2 stat:0 orb:0002ced84
sbp0:0:0 No additional information to report
sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense
sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 24 qlfr 0 len 2
sbp0:0:0 sbp_agent_reset
(probe0:sbp0:0:0:0): error 22
(probe0:sbp0:0:0:0): Unretryable Error
sbp0:0:0 sbp_cam_scan_lun

How-To-Repeat: Connect a Powerbook in target mode to a FreeBSD machine.

Run camcontrol rescan all

Attempt to fdisk the new disk
Comment 1 Jaakko Heinonen freebsd_committer freebsd_triage 2011-11-12 20:16:02 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-firewire

Reassign.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:22 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2025-01-28 12:01:44 UTC
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.