On Tue, Jul 21, 2015 at 04:39:07PM +0300, Konstantin Belousov wrote:
On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
My laptop had no problems, but the build machine has a panic that
appears quite reproducible (4 successes out of 4 tries); here's a bit
from the core.txt
On Tue, Jul 21, 2015 at 09:19:27AM -0700, David Wolfskill wrote:
On Tue, Jul 21, 2015 at 04:39:07PM +0300, Konstantin Belousov wrote:
On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
My laptop had no problems, but the build machine has a panic that
appears quite
On Tue, Jul 21, 2015 at 07:17:43PM +, Mark Johnston wrote:
On Tue, Jul 21, 2015 at 09:19:27AM -0700, David Wolfskill wrote:
On Tue, Jul 21, 2015 at 04:39:07PM +0300, Konstantin Belousov wrote:
On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
My laptop had no problems,
On Tue, Jul 21, 2015 at 03:21:16PM -0500, Eric van Gyzen wrote:
...
So it looks like net swi, leaking some udp6 lock.
Curiouser and curiouser... While I'm not taking any special pains to
avoid building IPv6, I'm not actively actually doing anything with it
(IPv6), either (for both the
On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote:
...
Indeed, thank you.
ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70
fork_exit() at fork_exit+0x84/frame 0xfe083b9c0ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe083b9c0ab0
--- trap 0, rip =
On 07/21/2015 15:05, David Wolfskill wrote:
On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote:
...
Indeed, thank you.
ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70
fork_exit() at fork_exit+0x84/frame 0xfe083b9c0ab0
fork_trampoline() at
On 07/21/2015 15:21, Eric van Gyzen wrote:
On 07/21/2015 15:05, David Wolfskill wrote:
On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote:
...
Indeed, thank you.
ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70
fork_exit() at fork_exit+0x84/frame
On Tue, Jul 21, 2015 at 05:57:34AM -0700, David Wolfskill wrote:
My laptop had no problems, but the build machine has a panic that
appears quite reproducible (4 successes out of 4 tries); here's a bit
from the core.txt file:
There must be kernel messages before the panic string. They are
