A syzkaller regression test triggered a panic

2023-09-09 Thread Peter Holm
Fatal trap 9: general protection fault while in kernel mode cpuid = 1; apic id = 01 instruction pointer = 0x20:0x80d21330 stack pointer = 0x28:0xfe01d39b9b20 frame pointer = 0x28:0xfe01d39b9b40 code segment= base 0x0, limit 0xf, type 0x1b

Re: epoch callback panic

2022-04-01 Thread Peter Holm
On Fri, Apr 01, 2022 at 10:33:15PM +0200, Hans Petter Selasky wrote: > On 4/1/22 19:07, Peter Holm wrote: > > markj@ asked me to post this one: > > > > panic: rw lock 0xf801bccb1410 not unlocked > > cpuid = 4 > > time = 1648770125 > > KDB: stack ba

epoch callback panic

2022-04-01 Thread Peter Holm
markj@ asked me to post this one: panic: rw lock 0xf801bccb1410 not unlocked cpuid = 4 time = 1648770125 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00e48a3d10 vpanic() at vpanic+0x17f/frame 0xfe00e48a3d60 panic() at panic+0x43/frame 0xfe00

panic: general protection fault in if_vlan.c:1877, vmcore.280

2021-02-17 Thread Peter Holm
Fatal trap 9: general protection fault while in kernel mode cpuid = 8; apic id = 08 instruction pointer = 0x20:0x80d455d4 stack pointer = 0x28:0xfe06facde760 frame pointer = 0x28:0xfe06facde7b0 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, lo

Re: panic: SACK scoreboard must not be empty

2016-09-23 Thread Peter Holm
On Thu, Apr 23, 2015 at 08:33:00AM +1000, Lawrence Stewart wrote: > On 04/22/15 19:19, Peter Holm wrote: > > On Wed, Apr 22, 2015 at 11:45:21AM +1000, Lawrence Stewart wrote: > >> Hi Peter, > >> > >> On 04/15/15 21:04, Peter Holm wrote:

Re: panic: SACK scoreboard must not be empty

2015-04-22 Thread Peter Holm
On Wed, Apr 22, 2015 at 11:45:21AM +1000, Lawrence Stewart wrote: > Hi Peter, > > On 04/15/15 21:04, Peter Holm wrote: > > Seen during i386 stress tests. > > > > db_trace_self_wrapper(c11e20fc,0,c11b79d4,1eb,e47578e0,...) at > > db_trace_self_wrapper+0x2a/f

panic: SACK scoreboard must not be empty

2015-04-15 Thread Peter Holm
Seen during i386 stress tests. db_trace_self_wrapper(c11e20fc,0,c11b79d4,1eb,e47578e0,...) at db_trace_self_wrapper+0x2a/frame 0xe47578b0 kdb_backtrace(c139e637,2,c120851d,e4757984,e4757940,...) at kdb_backtrace+0x2d/frame 0xe4757918 vpanic(c155b86a,100,c120851d,e4757984,e4757984,...) at vpanic+

Re: panic in tcp_do_segment()

2013-04-12 Thread Peter Holm
ue, Apr 9, 2013 at 2:44 PM, Peter Holm <[1]pe...@holm.cc> wrote: > >On Tue, Apr 09, 2013 at 10:35:30AM +0200, Andre Oppermann wrote: > > On 09.04.2013 10:16, Peter Holm wrote: >> > On Mon, Apr 08, 2013 at 02:13:40PM +0200, Andre Oppermann wrote: &

Re: panic in tcp_do_segment()

2013-04-09 Thread Peter Holm
On Tue, Apr 09, 2013 at 10:35:30AM +0200, Andre Oppermann wrote: > On 09.04.2013 10:16, Peter Holm wrote: > > On Mon, Apr 08, 2013 at 02:13:40PM +0200, Andre Oppermann wrote: > >> On 05.04.2013 13:09, Matt Miller wrote: > >>> Hey Rick, > >>> > >>

Re: panic in tcp_do_segment()

2013-04-09 Thread Peter Holm
On Mon, Apr 08, 2013 at 02:13:40PM +0200, Andre Oppermann wrote: > On 05.04.2013 13:09, Matt Miller wrote: > > Hey Rick, > > > > I believe Juan and I have root caused this crash recently. The t_state = > > 0x1, TCPS_LISTEN, in the link provided at the time of the assertion. > > > > In tcp_input(),