Date:Thu, 18 Oct 2018 02:45:35 +0200
From:m...@netbsd.org (Emmanuel Dreyfus)
Message-ID: <1nwuhrv.17wehqe12fccjvm%m...@netbsd.org>
| --- sys/dev/usb/uhub.c 27 Sep 2018 14:52:26 - 1.136.2.2
| +++ sys/dev/usb/uhub.c 18 Oct 2018 00:32:58 -
| @@
> On Oct 16, 2018, at 1:00 PM, Mindaugas Rasiukevicius wrote:
>
> Hi,
>
> I recently implemented thmap [1] -- a concurrent trie-hash map, combining
> the elements of hashing and radix trie. It is supports lock-free lookups
> and concurrent inserts/deletes. It is designed to be optimal as a
Hello
While working with USB code, I noticed the port numbering was
inconsistent: A device would be detected on port 5 during boot, but if I
detached and reattached it with drvctl, the kernel would tell about port
4.
This happens because attaching and reattaching do not go through the
same
On Wed, Oct 17, 2018 at 09:27:43PM +0900, Rin Okuyama wrote:
> Both kernels were built with no local patches. I still have
> not distinguished what difference triggers the crash...
I wonder if it is something stupid like DIAGNOSTIC (second bet would be
on one of the file systems not in your
-20181017
Both kernels were built with no local patches. I still have
not distinguished what difference triggers the crash...
Thanks,
rin
I have a crash on my mac68k machine when trying to boot a -current
kernel:
[ 5.4087986] trap(2bfe50,8,485,66c000) + 708
[ 5.4087986] copypage(?)
[ 5.4087986]
sleepq_block(0,0,242d5c,230c80,242d50,1de974,2308d4,72d09c,72d480) + 10
[ 5.4087986] cv_wait(242d50,242d5c) + 78
[ 5.4087986]
Hi,
On 2018/10/17 5:00, Mindaugas Rasiukevicius wrote:
> Hi,
>
> I recently implemented thmap [1] -- a concurrent trie-hash map, combining
> the elements of hashing and radix trie. It is supports lock-free lookups
> and concurrent inserts/deletes. It is designed to be optimal as a general
>
On Wed, Oct 17, 2018 at 06:03:16AM +0100, Nick Hudson wrote:
> Can you make the trace available somewhere, please?
The traces are what happen with my fake descriptors patch.
Trying nfc-list -t 1 but the device stopped responding:
https://ftp.espci.fr:shadow/manu/timeout.trace
Reboot trace:
