Hi Andrew!

On Sat, Jun 09, 2007 at 12:38:29PM +0100, Andrew Doran wrote:
> Where is ffffffff804f5610 according to nm?

Seems to be firmly in the hand of USB:
nm /netbsd | sort | grep ffffffff804f5
ffffffff804f5000 T usbd_interface2device_handle
ffffffff804f5010 T usbd_device2interface_handle
ffffffff804f5050 T usbd_pipe2device_handle
ffffffff804f5060 T usbd_get_no_alts
ffffffff804f50c0 T usbd_get_interface_altindex
ffffffff804f50d0 t usbd_do_request_async_cb
ffffffff804f50e0 T usbd_get_quirks
ffffffff804f50f0 T usbd_dopoll
ffffffff804f5110 T usbd_set_polling
ffffffff804f5150 T usbd_get_endpoint_descriptor
ffffffff804f5190 T usb_match_device
ffffffff804f51d0 T usb_desc_iter_init
ffffffff804f5200 T usbd_get_string0
ffffffff804f5420 T usbd_get_string
ffffffff804f5430 T usb_desc_iter_next
ffffffff804f54b0 T usbd_ratecheck
ffffffff804f54c0 T usb_transfer_complete
ffffffff804f56e0 T usbd_close_pipe
ffffffff804f5750 T usbd_alloc_xfer
ffffffff804f57a0 T usbd_transfer
ffffffff804f5950 T usbd_do_request_async
ffffffff804f5a00 T usbd_clear_endpoint_stall_async
ffffffff804f5a60 T usbd_sync_transfer
ffffffff804f5a70 T usbd_do_request_flags_pipe
ffffffff804f5c40 T usbd_do_request_flags
ffffffff804f5c70 T usbd_do_request
ffffffff804f5c80 T usbd_get_interface
ffffffff804f5cd0 T usbd_set_interface
ffffffff804f5d70 T usbd_clear_endpoint_stall
ffffffff804f5dd0 t usbd_open_pipe_ival
ffffffff804f5ec0 T usbd_open_pipe_intr
ffffffff804f5fe0 T usbd_open_pipe

Which reminds me of my other mail from yesterday, that my USB scanner
doesn't work...

> Can you compile with ddb and
> -fno-omit-frame-pointer so that you can get a backtrace if it happens
> again?

Trouble is, I have no serial console set up, and I'm usually in X (and
my keyboard is USB). I should probably set up a serial console :|
 Thomas