> Le 29 déc. 2018 à 20:50, Michael van Elst a écrit :
>
> nage...@sdf.org (Bruce Nagel) writes:
>
>> I'm guessing there isn't a simple means to use USB2 drivers and avoid this
>> issue? Nothing in the case is newer than 2012 so I don't need USB3
>> support.
>
> The USB3 case is worse. The
nage...@sdf.org (Bruce Nagel) writes:
>I'm guessing there isn't a simple means to use USB2 drivers and avoid this
>issue? Nothing in the case is newer than 2012 so I don't need USB3
>support.
The USB3 case is worse. The only driver that better handles fragmented
memory by allowing multi-segmen
Michael van Elst writes:
> On Fri, Dec 28, 2018 at 09:19:39AM -0500, Brad Spencer wrote:
>> mlel...@serpens.de (Michael van Elst) writes:
>> > It should only happen after some larger uptime when kernel memory
>> > might be too fragmented.
>>
>> I see this with a USB CDROM drive on a Xen DOM0 wit
Bruce Nagel writes:
> On Fri, 28 Dec 2018, Michael van Elst wrote:
>
>> Date: Fri, 28 Dec 2018 08:45:15 - (UTC)
>> From: Michael van Elst
>> To: netbsd-users@netbsd.org
>> Newsgroups: lists.netbsd.users
>> Subject: Re: Issue mounting USB mass-storage dri
On Fri, 28 Dec 2018, Michael van Elst wrote:
Date: Fri, 28 Dec 2018 08:45:15 - (UTC)
From: Michael van Elst
To: netbsd-users@netbsd.org
Newsgroups: lists.netbsd.users
Subject: Re: Issue mounting USB mass-storage drive
nage...@sdf.org (Bruce Nagel) writes:
umass0: failed to create
On Fri, Dec 28, 2018 at 09:19:39AM -0500, Brad Spencer wrote:
> mlel...@serpens.de (Michael van Elst) writes:
> > It should only happen after some larger uptime when kernel memory
> > might be too fragmented.
>
> I see this with a USB CDROM drive on a Xen DOM0 with no USB3 involved.
> I have to ta
mlel...@serpens.de (Michael van Elst) writes:
> nage...@sdf.org (Bruce Nagel) writes:
>
>>umass0: failed to create xfers
>
> Usually means the kernel ran out of (contigous) memory. This can be
> a consequence of using USB3, the xhci driver does not support
> multi-segment DMA yet.
>
> It should on
nage...@sdf.org (Bruce Nagel) writes:
>umass0: failed to create xfers
Usually means the kernel ran out of (contigous) memory. This can be
a consequence of using USB3, the xhci driver does not support
multi-segment DMA yet.
It should only happen after some larger uptime when kernel memory
might b
I am now having an issue with mounting a mass-storage 1TB drive that in the
past I was able to mount. I'm having the same issue with mounting USB flash
drives (8GB and 16GB).
When I attach the drive and attempt to run disklabel I get this output:
# disklabel sd0
disklabel: /dev/rsd0d: Device n
