Re: USB4BSD release candidate number 3 - request for review

On Thursday 06 November 2008, Alexey Shuvaev wrote:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
> _witness_debugger() at _witness_debugger+0x49
> witness_checkorder() at witness_checkorder+0x7e6
> _sx_xlock() at _sx_xlock+0x44
> vm_map_lookup() at vm_map_lookup+0x47
> vm_fault() at vm_fault+0xfe
> trap_pfault() at trap_pfault+0x1fa
> trap() at trap+0x201
> calltrap() at calltrap+0x8
> --- trap 0xc, rip = 0xffffffff804b2466, rsp = 0xfffffffeba7f8ac0, rbp =
> 0xfffffffeba7f8b00 --- bcopy() at bcopy+0x16
> usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x35
> usb2_bdma_work_loop() at usb2_bdma_work_loop+0x29b
> usb2_command_wrapper() at usb2_command_wrapper+0x76
> usb2_callback_wrapper() at usb2_callback_wrapper+0xfd
> usb2_command_wrapper() at usb2_command_wrapper+0x76
> usb2_callback_proc() at usb2_callback_proc+0x68
> usb2_process() at usb2_process+0xc0

Hi Alexey,

This looks more like a busdma problem to me. "bcopy()" is called from 
within "bus_dmamap_sync()". Maybe you can figure out if it is the source or 
the destination address that fails?

Looks like your system has started bouncing data to the 32-bit address range.

--HPS