Matt Rickard <mjr318@psu.edu> writes:
> I've built a generic + ieee1394 kernel in an attempt to get an external
> Maxtor firewire drive working on netbsd-current.  This is on a Dell
> Inspiron 8000 laptop.  I recall this setup working (although a bit
> buggy) several months ago with the ieee1394 code in current.  Now when I
> attach the device I get a kernel panic (on boot) of the following:

Our firewire support is pretty crappy. I've had similar problems of
all sorts with a couple of laptops. Sigh. :(

Really, I think we should dump our current firewire stuff and instead
slurp in the FreeBSD stuff, which seems to work much better.

Perry

>
> fw0 at fwochi0: 46:4f:c0:00:12:84:d4:01:0a:02:ff:ff:f0:01:00:00
> fwnode0 at fwohci0 Node 0: UID 00:00:00:00:00:00:00:00
> fwnode1 at fwohci0 Node 0: UID 00:10:b9:01:01:40:a5:6b
> fwnode0 detached
> atapibus0 at atabus0: 2 targets
> cd0 at atapibus0 drive 1: <TOSHIBA CD-RW/DVD-ROM SD-R2002, , 1E29> cdrom
> removable
> fwnode1: Link Speed: 100Mb/s, max_rec: 64 bytes
> uvm_fault(0xc07b0b00, 0x6010000, 0, 2) -> 0xe
> kernel: page fault trap, code=0
> Stopped in pid 3.1 (fwohci0) at netbsd: sbp2_abort+0x49: movl 
> %ebx,0xec(%edx)
>
> After being dropped to db, here is the backtrace:
>
> sbp2_abort(c11c8044,c1217a00,e33e8c9c,c0293488,c1218c80) at
> netbsd:sbp2_abort+0x49
> sbp2_free(c11c8000,c1218c80,c02d7830,733672de,e33e8cf4) at
> netbsd:sbp2_free+0x3c
> sbpscsi_match(c1217a00,c0746fac,c10d2640,c0762300,c0746fac) at
> netbsd:sbpscsi_match+0x5c
> mapply(e33e8cf4,c0746fac,0,1,0) at netbsd:mapply+0x36
> config_search(0,c1217a00,c10d2640,c1217a00,c10db004) at
> netbsd:config_search+0x8c
> config_found_sm(c1217a00,c10d2640,c0563b08,0,0) at
> netbsd:config_found_sm+0x1c
> p1212_match_units(c1217a00,c1218dc0,c0563b08,40,c10d2740) at netbsd:
> p1212_match_units+0x4e
> fwnode_configrom_input(c1218d00,0,e33e8dd4,3,2) at
> netbsd:fwnode_configrom_input+0x1e7
> fwohci_read_multi_resp(c11c1000,c10d2740,e33e8e94,6,6) at
> netbsd:fwohci_read_multi_resp+0x170
> fwohci_arrs_input(c11c1000,c11be200,0,380054f3,c11c11c8) at
> netbsd:fwohci_arrs_input+0x79
> fwohci_event_thread(c11c1000,c11c1000,2,c10d2810,c11c1000) at
> netbsd:fwohci_event_thread+0x25f
> fwohci_thread_init(c11c1000,876000,87f000,0,c010030c) at
> netbsd:fwohci_thread_init+0x1dc
>
>
> If more information is needed to determine the cause of this panic let
> me know and I'll do my best to provide it.
>
> Thanks.
>

-- 
Perry E. Metzger		perry@piermont.com