Date: Fri, 20 Mar 2020 15:37:19 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 206567] [msk] msk0: watchdog timeout - 88E8053 on i386 Message-ID: <bug-206567-7501-7WSj7YkcFm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206567-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-206567-7501@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=3D206567 --- Comment #12 from Chris Hutchinson <portmaster@bsdforge.com> --- (In reply to Tom Lane from comment #11) OK. I only see one MSI-X message in dmesg(8) It's related to your (msk) card -- Found 1 of 1 interrupts. I ran into the same error you're reporting. But it was on a dual port re (realtek) card. The most proposed solution was to disable MSI-X on the card. Blamed on a poor implementation. I wasn't satisfied with that, as doing so would reduce performance, and I work that card pretty hard. So I performed some additional investigation into exactly *why* this problem occurs, and ultimately decided to investigate the kernel tunable kern.ipc.nmbjumbop and kern.ipc.nmbclusters After tweaking them for awhile. I found thresholds that eliminated the error, and have been running the card blissfully for about 9 months now. If I were you, I might be inclined to increase those numbers until the errors cease. There is no magic number I can provide. As it differs from card to card, and load to load. But it's enough to say that the *default* number is inadequate (too small). HTH --Chris --=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-206567-7501-7WSj7YkcFm>