https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231441
Warner Losh changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #33 from Lev A. Serebryakov ---
And igb + !AESNI + INVARIANTS — looks very similar to em!
panic: Assertion (staterr & E1000_RXD_STAT_DD) != 0 failed at
/data/src/sys/dev/e1000/igb_txrx.c:451
cpuid = 2
time = 1539129723
KDB: sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #32 from Lev A. Serebryakov ---
I've removed KDB_UNATTENDED from kernel and got dump! Looks like kernel memory
is complete mess at this moment, as it panics on all 4 cores!
Unread portion of the kernel message buffer:
kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #31 from Lev A. Serebryakov ---
Ok, system with igb0 CAN NOT crash dumps in automatic mode at all, even if it
is local dump. It goes to panic loop and print on console this again and again
and again, forever:
Fatal trap 9: gene
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #30 from Mark Johnston ---
(In reply to Lev A. Serebryakov from comment #29)
Are you able grab a backtrace or at least a panic message in this case?
netdump does have a lot of failure modes when used on a busy interface. It
wo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #29 from Lev A. Serebryakov ---
netdump(8) via same igb0 as test itself leads to loop of panics :-)
--
You are receiving this mail because:
You are the assignee for the bug.
___
free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #28 from Lev A. Serebryakov ---
It still a issue for ALPHA8, r339259.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing li
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
Lev A. Serebryakov changed:
What|Removed |Added
Summary|[em] 12-ALPHA7 r338900 |[em][igb][softcrypto]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #27 from Lev A. Serebryakov ---
igb0 + !AESNI + !INVARIANTS — crash.
But I can not provide dumps or stacks yet :-(
Looks like it is combination of Intel NICs and soft crypto.
--
You are receiving this mail because:
You are t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #26 from Lev A. Serebryakov ---
I could report, that
vtent0 + AESNI + INVARIANTS — no crash.
vtnet0 + !AESNI + INVARIANTS — no crash.
vtent0 + AESNI + !INVARIANTS — no crash.
vtent0 + !AESNI + !INVARIANTS — no crash.
I'll
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #25 from Lev A. Serebryakov ---
(In reply to Conrad Meyer from comment #23)
Now I have:
igb + AESNI + bpf — one crash on older revision, no crashes for several hours
of testing on newer revisions. It is very first stack trace,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
Conrad Meyer changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #24 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #23 from Conrad Meyer ---
Ok, let me try and understand what has been tested. Please correct me if I am
mistaken:
- igb + ??? + bpf = crash (initial description)?
- igb + AESNI + no bpf = no crash
- em + !AESNI + no bpf = cras
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #22 from Lev A. Serebryakov ---
(In reply to Conrad Meyer from comment #21)
It gives me idea to test on AES-NI capable hardware with other NICs (igb
instead of em) but without AES-NI loaded, to force it use soft crypto.
Also, I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #21 from Conrad Meyer ---
Ok, I think it's probably not an OCF bug then. Plenty of room for a NIC or
IPsec bug, though.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230858
Mark Linimon changed:
What|Removed |Added
CC||lini...@freebsd.org
--- Comment #9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #20 from Lev A. Serebryakov ---
(In reply to Conrad Meyer from comment #19)
It is r339021.
aesni is useless here, as this hardware doesn't have support for it.
--
You are receiving this mail because:
You are the assignee for
17 matches
Mail list logo
