Re: next-20151207 - crash in IPv6 code

From: valdis.kletni...@vt.edu Date: Tue, 08 Dec 2015 16:54:17 -0500 > On Tue, 08 Dec 2015 12:34:09 +0100, Florian Westphal said: >> Valdis Kletnieks wrote: >> >> [ CC Pablo ] >> >> > Seen this in 2 boots out of two on next-20151207 when IPV6 networking >> > was available. It was stable when no

Re: next-20151207 - crash in IPv6 code

On Tue, 08 Dec 2015 12:34:09 +0100, Florian Westphal said: > Valdis Kletnieks wrote: > > [ CC Pablo ] > > > Seen this in 2 boots out of two on next-20151207 when IPV6 networking > > was available. It was stable when no net was available. Also, > > next-20161127 is OK. > > Haven't bisected it

Re: next-20151207 - crash in IPv6 code

Valdis Kletnieks wrote: [ CC Pablo ] > Seen this in 2 boots out of two on next-20151207 when IPV6 networking > was available. It was stable when no net was available. Also, next-20161127 > is OK. > Haven't bisected it yet - this ring any bells? Thanks for the report, my fault -- its caused

Re: next-20151207 - crash in IPv6 code

Valdis Kletnieks wrote: [ CC Pablo ] > Seen this in 2 boots out of two on next-20151207 when IPV6 networking > was available. It was stable when no net was available. Also, next-20161127 > is OK. > Haven't bisected it yet - this ring any bells? Thanks for the report,

Re: next-20151207 - crash in IPv6 code

From: valdis.kletni...@vt.edu Date: Tue, 08 Dec 2015 16:54:17 -0500 > On Tue, 08 Dec 2015 12:34:09 +0100, Florian Westphal said: >> Valdis Kletnieks wrote: >> >> [ CC Pablo ] >> >> > Seen this in 2 boots out of two on next-20151207 when IPV6 networking >> > was

Re: next-20151207 - crash in IPv6 code

On Tue, 08 Dec 2015 12:34:09 +0100, Florian Westphal said: > Valdis Kletnieks wrote: > > [ CC Pablo ] > > > Seen this in 2 boots out of two on next-20151207 when IPV6 networking > > was available. It was stable when no net was available. Also, > > next-20161127 is OK. >

next-20151207 - crash in IPv6 code

Seen this in 2 boots out of two on next-20151207 when IPV6 networking was available. It was stable when no net was available. Also, next-20161127 is OK. Haven't bisected it yet - this ring any bells? [ 92.231022] BUG: unable to handle kernel NULL pointer dereference at (null) [

next-20151207 - crash in IPv6 code

Seen this in 2 boots out of two on next-20151207 when IPV6 networking was available. It was stable when no net was available. Also, next-20161127 is OK. Haven't bisected it yet - this ring any bells? [ 92.231022] BUG: unable to handle kernel NULL pointer dereference at (null) [