Re: Freebsd 11.0 RELEASE - ZFS deadlock

2016-11-14 Thread Andriy Gapon
On 13/11/2016 15:28, Henri Hennebert wrote: > On 11/13/2016 11:06, Andriy Gapon wrote: >> On 12/11/2016 14:40, Henri Hennebert wrote: >>> I attatch it >> >> Thank you! >> So, these two threads are trying to get the lock in the exclusive mode: >> Thread 687 (Thread 101243): >> #0 sched_switch (td=0

Re: Freebsd 11.0 RELEASE - ZFS deadlock

2016-11-14 Thread Henri Hennebert
On 11/14/2016 10:07, Andriy Gapon wrote: On 13/11/2016 15:28, Henri Hennebert wrote: On 11/13/2016 11:06, Andriy Gapon wrote: On 12/11/2016 14:40, Henri Hennebert wrote: [snip] Could you please show 'info local' in frame 14? I expected that 'nd' variable would be defined there and it may

Re: Freebsd 11.0 RELEASE - ZFS deadlock

2016-11-14 Thread Andriy Gapon
On 14/11/2016 11:35, Henri Hennebert wrote: > > > On 11/14/2016 10:07, Andriy Gapon wrote: >> Hmm, I've just noticed another interesting thread: >> Thread 668 (Thread 101245): >> #0 sched_switch (td=0xf800b642aa00, newtd=0xf8000285f000, >> flags=> optimized out>) at /usr/src/sys/kern/sc

Re: Freebsd 11.0 RELEASE - ZFS deadlock

2016-11-14 Thread Henri Hennebert
On 11/14/2016 12:45, Andriy Gapon wrote: On 14/11/2016 11:35, Henri Hennebert wrote: On 11/14/2016 10:07, Andriy Gapon wrote: Hmm, I've just noticed another interesting thread: Thread 668 (Thread 101245): #0 sched_switch (td=0xf800b642aa00, newtd=0xf8000285f000, flags=) at /usr/src

Re: Problems with Dell external USB DVD drive

2016-11-14 Thread Felix Johnson
Hi Kevin, The drive was plugged in when I used usbconfig. When I plug the drive in, the drive makes a powering-up noise, as if it's trying to align with a disk that may be inside it. Unfortunately, there are no console messages. I've tried the USB 2 and USB 3 ports, with no change - the device po

Re: stable/11 -r308135 Build for RPI2 failed for: . . ./bcm2835_ft5406.c:65:10: fatal error: 'mbox_if.h' file not found [Fixed]

2016-11-14 Thread Mark Millard
On 2016-Nov-2, at 12:16 PM, Mark Millard wrote: > Quick top post reporting that a build-order-race for -j use seems likely: the > clean-then-build sequence > >> Command: env __MAKE_CONF=/root/src.configs/make.conf >> SRC_ENV_CONF=/root/src.configs/src.conf.rpi2-clang-bootstrap.amd64-host >> W