[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Kubilay Kocak changed: What|Removed |Added Resolution|FIXED |Not Enough

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #46 from Robert Watson --- I've opened a new #218270 for the sbsndptr() crash. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #45 from Mike Andrews --- As the guy that filed the original bug report almost 7 years ago, I'd tend to agree with Robert Watson here. I'll see if Bugzilla will let me close it. -- You are receiving this

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Mike Andrews changed: What|Removed |Added Resolution|--- |FIXED

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #44 from Robert Watson --- It's probably best to be clear: the bugs being described by various reporters over the years are *different* (and likely entirely *independent*) bugs that happen to have the same

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #43 from Kubilay Kocak --- @All For issues where the 'described problem' and the 'thing(s) that need to be changed' are not one and the same, to retain all history/contextual information and not cause

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #42 from Hiren Panchasara --- I've seen this happen on both em(4) which has only 1 queue and igb(4) which has 2. It'd be interesting to see if new iflib'd em(4) (which has both em/igb) drivers in -HEAD help

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #41 from e...@norma.perm.ru --- May be it will be better just to change a subject, rather to lose all the decent work here in comments ? Because closing such a bug will be really discouraging, even if it's subject is misleading.

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #40 from Ivan Klymenko --- (In reply to Robert Watson from comment #39) I am afraid, that I can not add to new ticket tacking is nothing more, than has been described in the above thread the mailing list. In the

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #39 from Robert Watson --- FYI, I feel that this bug report ought to be closed, and a new and more specific report opened on the IGB issue. The "sbdrop" panic is a generic debugging invariant that catches a

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Ivan Klymenko changed: What|Removed |Added CC||fi...@ukr.net ---

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Hiren Panchasara changed: What|Removed |Added CC|

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Greg Lund-Chaix changed: What|Removed |Added CC|

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #35 from s...@zxy.spb.ru --- (In reply to Hiren Panchasara from comment #34) > which value of 'm' should I trust? is it null in frame #22 or not? it seems > like null in the frames above it also. Зartially. ether_input call

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #34 from Hiren Panchasara --- (In reply to slw from comment #33) Thanks but I am little confused. which value of 'm' should I trust? is it null in frame #22 or not? it seems like null in the frames above it

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 s...@zxy.spb.ru changed: What|Removed |Added CC||s...@zxy.spb.ru --- Comment #33

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Daniel Bilik changed: What|Removed |Added CC|

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #31 from Hiren Panchasara --- (In reply to Robert Watson from comment #29) Robert, Thanks for your response. On a slightly modified (nothing in driver space) stable/11, I am seeing repeated panic in

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #30 from e...@norma.perm.ru --- Follow-up: RC3 was installed incorrectly (i.e. not installed at all). After proper RC3 downgrade (r305786) seems like server is at least more stable - it runs for more than an hour. On 11.0-PRE

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #29 from Robert Watson --- Just a quick comment in light of recent notes on this PR: the panic being seen is as a result of a kernel self-check that occurs on socket close, and likely reports on a bug that

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 e...@norma.perm.ru changed: What|Removed |Added CC||e...@norma.perm.ru ---

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #27 from Mike Andrews --- For what it's worth, the original problem I reported in this PR from 6 years ago is (for me anyway) long-ago solved... but then we're on 10.3 these days and are slowly rolling

[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable9?,