Date: Thu, 13 Oct 2016 08:37:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Message-ID: <bug-148807-2472-eMjIImatQD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-148807-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-148807-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=3D148807 Daniel Bilik <ddb@neosystem.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddb@neosystem.org --- Comment #32 from Daniel Bilik <ddb@neosystem.org> --- (In reply to Robert Watson from comment #29) > On the whole, my intuition is towards a device-driver bug based > on past experience. We've been also struggling this in past weeks, and I can confirm Robert's intuition. In our case, the bug affects two hosts running recent 10-STABLE, connected = to each other via igb(4) using a dedicated 100Mb switch. When trying to transf= er directory structure holding several gigabytes of data with rsync protocol, either sender or receiver panics in less then a minute with: Panic String: sbsndptr: sockbuf 0xfffff8000ccc76f8 and mbuf 0xfffff802a0145= 800 clashing Interestingly, scp(1)ing data between the hosts doesn't seem to trigger this panic such easily, but sometimes it does, mostly when copying larger (>1GB) files. We've fixed this just yesterday by limiting number of igb(4) txrx queues, i= e. adding this into loader.conf: hw.igb.num_queues=3D1 Now the hosts run stable, periodically rsyncing data in both directions. --=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-148807-2472-eMjIImatQD>