[Bug 222987] ARM64 panic in iflib.c:2944

2018-06-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222987 Sean Bruno changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 222987] ARM64 panic in iflib.c:2944

2018-01-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222987 --- Comment #3 from Sean Bruno --- Panic this morning: Tracing pid 0 tid 100236 td 0xfd000b986540 db_trace_self() at db_stack_trace+0xec pc = 0x005fb138 lr = 0x000898a8 sp = 0x00013230c1a0 fp = 0

[Bug 222987] ARM64 panic in iflib.c:2944

2018-01-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222987 --- Comment #4 from Sean Bruno --- (In reply to Sean Bruno from comment #3) ACtually, looking at scrollback, its actually this: Jan 28 08:31:55 thunderx1 smartd[53576]: In the system's table of devices NO devices found to scan panic: deadl

[Bug 222987] ARM64 panic in iflib.c:2944

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222987 --- Comment #2 from Antoine Brodin --- Another panic from yesterday: KDB: reentering KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+40 pc = 0x005e72e8 lr = 0x00086ad4 sp = 0x000b96c218

[Bug 222987] ARM64 panic in iflib.c:2944

2017-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222987 --- Comment #1 from Sean Bruno --- I think I need to run a specific patch to get a valid crash dump here on thunderx1. I wanted to start a ticket on this so that it doesn't get lost. -- You are receiving this mail because: You are the as

[Bug 222987] ARM64 panic in iflib.c:2944

2017-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222987 Bug ID: 222987 Summary: ARM64 panic in iflib.c:2944 Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Some