Re: panics in network stack in 12-current

From: Andrey V. Elsukov <bu7cher_at_yandex.ru>
Date: Wed, 26 Apr 2017 05:17:26 +0300
On 26.04.2017 04:03, Tom Uffner wrote:
> Since updating my -current box to 12 several months ago, I have been
> trying to pin down several elusive and probably related panics.
> 
> they always manifest a a trap out of rw_wlock_hard()
> 
> i am fairly certain that r302409 was stable, revs up through r306792 may be
> stable, or perhaps I just didn't wait long enough for my system to panic. I
> don't know of anything that I can reproducably poke at to trigger this.
> r306807 is definitely bad, as is everything up through r309124. I
> haven't seen anything on the mailing lists or in the SVN logs that looks
> like it is related to my problem.
> 
> my hardware is an Asus M4A77TD MB, AMD Phenom 2 X6 1100T CPU (for some of
> this time I had an Athlon 2 X2, but upgraded recently), and RealTek 8168
> PCIe Gigabit NIC.
> 
> FreeBSD discordia.uffner.com 12.0-CURRENT FreeBSD 12.0-CURRENT #33
> r306807M: Tue Apr 18 17:09:55 EDT 2017
> tom_at_discordia.uffner.com:/usr/obj/usr/src/sys/DISCORDIA  amd64
> 
> in revs between 306807-307125, the panics have been in flowcleaner, in
> more recent ones, they happen in arbitrary userspace processes that make
> heavy use
> of the network.
> 
> I know I should try the latest rev to see if it went away. aside from
> that, any thoughts on how I should proceed?
I think the most of these panics should be fixed in r315956.

-- 
WBR, Andrey V. Elsukov


Received on Wed Apr 26 2017 - 00:18:30 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:11 UTC