Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Jul 2017 06:09:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 220358] panic in tcp_lro_flush_all
Message-ID:  <bug-220358-2472-GlKwnKcvdD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220358-2472@https.bugs.freebsd.org/bugzilla/>
References:  <bug-220358-2472@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220358

--- Comment #11 from iz-rpi03@hs-karlsruhe.de ---
I can add to this, that a 32-bit ARM (Raspberrr-PI) kernel r320571 panics
immediately when a ssh connect is attempted.
This behaviour is repeatable (3 panics out of 3 attempts).

Just for the record:

login: panic: Undefined instruction in kernel.

time =3D 1499024534
KDB: stack backtrace:
$a.6() at $a.6
         pc =3D 0xc05fe050  lr =3D 0xc01577b0 (db_trace_self_wrapper+0x30)
         sp =3D 0xdc65a818  fp =3D 0xdc65a930
db_trace_self_wrapper() at db_trace_self_wrapper+0x30
         pc =3D 0xc01577b0  lr =3D 0xc02f9130 (vpanic+0xc0)
         sp =3D 0xdc65a938  fp =3D 0xdc65a958
         r4 =3D 0x00000100  r5 =3D 0xdc65a96c
         r6 =3D 0xc061b004  r7 =3D 0x00000001
vpanic() at vpanic+0xc0
         pc =3D 0xc02f9130  lr =3D 0xc02f9070 (vpanic)
         sp =3D 0xdc65a960  fp =3D 0xdc65a964
         r4 =3D 0x00000000  r5 =3D 0x00000000
         r6 =3D 0x00000010  r7 =3D 0xffffff80
         r8 =3D 0xdc65a9f0  r9 =3D 0x00000001
        r10 =3D 0xc2caafdc
vpanic() at vpanic
         pc =3D 0xc02f9070  lr =3D 0xc061afec ($d.14)
         sp =3D 0xdc65a96c  fp =3D 0xdc65a9e8
         r4 =3D 0xffffff80  r5 =3D 0xdc65a9f0
         r6 =3D 0x00000001  r7 =3D 0xc2caafdc
         r8 =3D 0xdc65a964  r9 =3D 0xc02f9070
        r10 =3D 0xdc65a96c
$d.14() at $d.14
         pc =3D 0xc061afec  lr =3D 0xc0600b94 (exception_exit)
         sp =3D 0xdc65a9f0  fp =3D 0xdc65aa88
         r4 =3D 0xa0000013  r5 =3D 0xc2caaa78
         r6 =3D 0x00000010  r7 =3D 0xc2bd4700
         r8 =3D 0xc2c51824  r9 =3D 0xc2caa430
        r10 =3D 0x00000000
exception_exit() at exception_exit
         pc =3D 0xc0600b94  lr =3D 0xc0389544 (solisten_wakeup+0x28)
         sp =3D 0xdc65aa80  fp =3D 0xdc65aa88
         r0 =3D 0xc2caaa78  r1 =3D 0x00000000
         r2 =3D 0x00000001  r3 =3D 0xc2caaa90
         r4 =3D 0x00000001  r5 =3D 0xc2caaa78
         r6 =3D 0x00000010  r7 =3D 0xc2bd4700
         r8 =3D 0xc2c51824  r9 =3D 0xc2caa430
        r10 =3D 0x00000000 r12 =3D 0x00000000
_end() at 0xc2caafdc
         pc =3D 0xc2caafdc  lr =3D 0xc0389544 (solisten_wakeup+0x28)
         sp =3D 0xdc65aa80  fp =3D 0xdc65aa88
KDB: enter: panic
[ thread pid 13 tid 100033 ]
Stopped at      $d.12:  ldrb    r15, [r15, r15, ror r15]!
db>=20
db> show proc=20=20=20
Process 13 (usb) at 0xc288a398:
 state: NORMAL
 uid: 0  gids: 0
 parent: pid 0 at 0xc0783548
 ABI: null
 threads: 6
100031                   D       -       0xc291b02c  [usbus0]
100032                   D       -       0xc291b05c  [usbus0]
100033                   Run     CPU 0               [usbus0]
100034                   D       -       0xc291b0bc  [usbus0]
100035                   D       -       0xc291b0ec  [usbus0]
100069                   D       -       0xc2a9da28  [smsc0]
db> show thread=20
Thread 100033 at 0xc2936000:
 proc (pid 13): 0xc288a398
 name: usbus0
 stack: 0xdc659000-0xdc65afff
 flags: 0x1000004  pflags: 0x200000
 state: RUNNING (CPU 0)
 priority: 28
 container lock: sched lock (0xc07713c4)
 last voluntary switch: 1 ms ago
 last involuntary switch: 0 ms ago
db>

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220358-2472-GlKwnKcvdD>