Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Aug 2005 17:19:44 +0800
From:      Rong-En Fan <grafan@gmail.com>
To:        freebsd-stable@freebsd.org
Subject:   Re: panic: sbflush_locked on 5.4-p5/i386
Message-ID:  <6eb82e050801021948bb3cf0@mail.gmail.com>
In-Reply-To: <dcjavk$3g5$1@sea.gmane.org>
References:  <6eb82e0507241001615f7490@mail.gmail.com> <dc0m7k$enm$1@sea.gmane.org> <20050729002138.X60522@fledge.watson.org> <dcd588$tkf$1@sea.gmane.org> <20050729125525.D74149@fledge.watson.org> <dcjavk$3g5$1@sea.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 8/1/05, Alexander S. Usov <A.S.Usov@kvi.nl> wrote:
> In just 2 days of waiting I got it, however it looks that it has fired in=
 a
> bit different place.
>=20
> (kgdb) bt
> #0  doadump () at pcpu.h:159
> #1  0xc0513899 in boot (howto=3D260) at ../../../kern/kern_shutdown.c:410
> #2  0xc0513ede in panic (fmt=3D0xc06ac87f "sbdrop")
> at ../../../kern/kern_shutdown.c:566
> #3  0xc05556f4 in sbdrop_locked (sb=3D0xc2285ad8, len=3D112)
> at ../../../kern/uipc_socket2.c:1149
> #4  0xc05b27f2 in tcp_input (m=3D0xc1e31800, off0=3D152)
> at ../../../netinet/tcp_input.c:2209
> #5  0xc05a9b13 in ip_input (m=3D0xc1e31800) at ../../../netinet/ip_input.=
c:776
> #6  0xc059215e in netisr_processqueue (ni=3D0xc070b0f8)
> at ../../../net/netisr.c:233
> #7  0xc059241d in swi_net (dummy=3D0x0) at ../../../net/netisr.c:346
> #8  0xc04fb9a1 in ithread_loop (arg=3D0xc1979500)
> at ../../../kern/kern_intr.c:547
> #9  0xc04fa9dc in fork_exit (callout=3D0xc04fb8ea <ithread_loop>, arg=3D0=
x0,
> frame=3D0x0)    at ../../../kern/kern_fork.c:791
> #10 0xc0656a8c in fork_trampoline () at ../../../i386/i386/exception.s:20=
9

I also got a panic:sbdrop, but a bit different on path:
http://www.rafan.org/FreeBSD/5.4-so/panic-sbdrop
(but no dump)

And, another one with trap 12
http://www.rafan.org/FreeBSD/5.4-so/panic-trap12
I have dump for this, but kgdb cant read it :-(
It says "cannot read PTD".

This machine is our main www server,  so I have to make it as stable
as possible. I might be able to switch mpsafenet at night.

By the way, I have accf_http(4) and accf_data(4) compiled in. But
with or without them, I can easily get panic with mpsafenet in less
half day.



>=20
> I am going to keep it around for some time, so I can easisy do a full bt =
or
> variables.
>=20
>=20
> Corresponding dmesg & sysctl output can be found at
> https://kvip88.kvi.nl/~usov
>=20
>=20
> --
> Best regards,
>   Alexander.
>=20
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e050801021948bb3cf0>