Re: uhub_reattach_port:413: could not allocate new device!
- From: Hans Petter Selasky <hselasky@xxxxxxx>
- Date: Fri, 30 Jan 2009 10:44:21 +0100
On Friday 30 January 2009, Chris Ruiz wrote:
Jan 29 19:34:39 attack kernel: usb2_pc_common_mem_cb:429: Page offset
was not preserved!
Hi,
First of all thanks for reporting!
The issue you are experiencing is a known problem with busdma, because you are
using a 64-bit platform.
See "http://wiki.freebsd.org/USB" for a resolution.
--HPS
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: uhub_reattach_port:413: could not allocate new device!
- From: Chris Ruiz
- Re: uhub_reattach_port:413: could not allocate new device!
- References:
- uhub_reattach_port:413: could not allocate new device!
- From: Chris Ruiz
- uhub_reattach_port:413: could not allocate new device!
- Prev by Date: RFC: Change mtree nsec handling?
- Next by Date: Re: RFC: Change mtree nsec handling?
- Previous by thread: uhub_reattach_port:413: could not allocate new device!
- Next by thread: Re: uhub_reattach_port:413: could not allocate new device!
- Index(es):
Relevant Pages
|