On Mon, 17 Feb 2020, Michael van Elst wrote:
p...@whooppee.com (Paul Goyette) writes:
So, sounds like "something somewhere isn't quite right (tm)". I would
have expected a memory allocation failure to automatically trigger some
mechanism to reclaim some of the file cache...
It's not the
Updating src tree:
P src/share/misc/acronyms
P src/sys/arch/amd64/amd64/genassym.cf
P src/sys/arch/amd64/conf/GENERIC
P src/sys/arch/amiga/amiga/genassym.cf
P src/sys/arch/atari/atari/genassym.cf
P src/sys/arch/cesfic/cesfic/genassym.cf
P src/sys/arch/hp300/hp300/genassym.cf
P
On 18.02.2020 00:09, Chavdar Ivanov wrote:
> Mono-6.6 - the previous build from 28th of January on the same machine
> running -current of the time - works fine.
>
>
>
Please update your pkgsrc tree as there were runtime fixes.
signature.asc
Description: OpenPGP digital signature
mlel...@serpens.de (Michael van Elst) writes:
> g...@lexort.com (Greg Troxel) writes:
>
>>My impression is that something, perhaps more umass than *hci, needs a
>>very large chunk of memory.
>
> umass allocates two 64k (MAXPHYS sized) DMA buffers and a few smaller ones.
> For all drivers but ehci
Hi,
I am getting:
Core was generated by `mono'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7e60351860ca in ?? ()
[Current thread is 1 (process 10)]
(gdb) bt
#0 0x7e60351860ca in ?? ()
#1 0x7e603518646a in ?? ()
#2 0xffdf in ?? ()
#3 0x
g...@lexort.com (Greg Troxel) writes:
>My impression is that something, perhaps more umass than *hci, needs a
>very large chunk of memory.
umass allocates two 64k (MAXPHYS sized) DMA buffers and a few smaller ones.
For all drivers but ehci each buffer must use contigous physical pages.
ehci
p...@whooppee.com (Paul Goyette) writes:
>available. The concensus on IRC is that this is a bug in the xhci(4)
>driver.
xhci could support scatter/gather transfers to multiple smaller buffers
to mitigate the problem, so far only ehci(4) does this. But some hardware
wouldn't support it unless
p...@whooppee.com (Paul Goyette) writes:
>So, sounds like "something somewhere isn't quite right (tm)". I would
>have expected a memory allocation failure to automatically trigger some
>mechanism to reclaim some of the file cache...
It's not the file cache. Freeing the file cache however also
On 17/02/2020 16:23, Paul Goyette wrote:
[...]
More info...
First, this is on a amd64 system, witwh 8core/16thread and 128GB of RAM.
On IRC it was suggested (thanks, maya!) that the error message might be
related to memory fragmentation. I didn't believe it (given how much
RAM I have), but a
Paul Goyette writes:
> First, this is on a amd64 system, witwh 8core/16thread and 128GB of RAM.
>
> On IRC it was suggested (thanks, maya!) that the error message might be
> related to memory fragmentation. I didn't believe it (given how much
> RAM I have), but a quick check with top(1) showed
This is now PR kern/54997
On Mon, 17 Feb 2020, Paul Goyette wrote:
With a 9.99.46 kernel built from sources dated 2020-02-07 16:26:35 UTC
I get the following errors when plugging in a USB hard drive:
umass0 at uhub1 port 2 configuration 1 interface 0
umass0: Western Digital (0x1058) Ext HDD
With a 9.99.46 kernel built from sources dated 2020-02-07 16:26:35 UTC
I get the following errors when plugging in a USB hard drive:
umass0 at uhub1 port 2 configuration 1 interface 0
umass0: Western Digital (0x1058) Ext HDD 1021 (0x1021), rev 2.00/20.02,
addr 32
umass0: using SCSI over
On Mon, 17 Feb 2020, Paul Goyette wrote:
On Mon, 17 Feb 2020, Paul Goyette wrote:
With a 9.99.46 kernel built from sources dated 2020-02-07 16:26:35 UTC
I get the following errors when plugging in a USB hard drive:
umass0 at uhub1 port 2 configuration 1 interface 0
umass0: Western Digital
On Mon, 17 Feb 2020, Paul Goyette wrote:
With a 9.99.46 kernel built from sources dated 2020-02-07 16:26:35 UTC
I get the following errors when plugging in a USB hard drive:
umass0 at uhub1 port 2 configuration 1 interface 0
umass0: Western Digital (0x1058) Ext HDD 1021 (0x1021), rev
With a 9.99.46 kernel built from sources dated 2020-02-07 16:26:35 UTC
I get the following errors when plugging in a USB hard drive:
umass0 at uhub1 port 2 configuration 1 interface 0
umass0: Western Digital (0x1058) Ext HDD 1021 (0x1021), rev 2.00/20.02, addr 32
umass0: using SCSI over
15 matches
Mail list logo
