On Fri, Jun 16, 2017 at 2:03 AM, Jia-Ju Bai wrote:
> The alc driver may sleep under a mutex, and the function call paths in file
> "sys/dev/alc/if_alc.c" in FreeBSD 11.0 is:
> alc_resume [line 2648: acquire the mutex]
> alc_init_locked [line 2664]
> alc_init_rx_ring [line 3911]
> alc_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428
--- Comment #7 from gitdev ---
Created attachment 183588
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=183588&action=edit
boot msg, panic and backtrace
FreeBSD 12.0-CURRENT #0 r319859 generates panic:
em1: Using MSIX interrupt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220073
Sean Bruno changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220073
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: sbruno
Date: Sat Jun 17 17:42:53 UTC 2017
New revision: 320059
URL: https://svnweb.freebsd.org/changeset/base/320059
Log:
Revert r319989 "bnxt(4) Enabl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220073
Diane Bruce changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #71 from Eugene Grosbein ---
IFYI2: another reason for this task to break and new set of patches here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220078
--
You are receiving this mail because:
You are on the CC list for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220073
Dmitry Chagin changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114
--- Comment #70 from Eugene Grosbein ---
JFYI: these patches made my mpd server side pretty stable, so my stress test
can run long enough to hit another problem that produces repeatable kernel
panics at client side. I've digged that problem