Date: Mon, 10 Jan 2000 14:46:36 +0900 From: Jun Kuriyama <kuriyama@sky.rim.or.jp> To: bmilekic@dsuper.net Cc: current@FreeBSD.ORG Subject: Re: panic at kern/uipc_socket2.c Message-ID: <14457.29244.643560.68187Y@localhost.sky.rim.or.jp> In-Reply-To: In your message of "Fri, 7 Jan 2000 13:42:37 -0500 (EST)" <Pine.OSF.4.05.10001071336570.13191-100000@oracle.dsuper.net> References: <14450.6126.709759.19547O@localhost.sky.rim.or.jp> <Pine.OSF.4.05.10001071336570.13191-100000@oracle.dsuper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Bosko Milekic <bmilekic@dsuper.net>
> Can you look at kern/10872 and see if your hardware matches Bob's?
> (e.g. The infamous fxp and ncr combo.) and regardless, attempt executing
> the script that is provided and note whether or not you can reproduce the
> panic in sbdrop()? If so, a backtrace and a `print *sb' would be helpful,
> certainly. It looks as though some mbufs are literally being `zapped' off
> of sb_mb while sb_cc and sb_mbcnt are still greater than zero. Either
> that, or something's not adjusting sb_cc and/or sb_mbcnt under the proper
> spl which may lead to an interrupt eventually leading to the sbdrop
> with an sb_cc and sb_mb that just don't go together.
No. I'm using aue (USB ethernet adaptor) and no SCSI subsystem.
And I have another problem that I cannot clean re-mount root
filesystem everytime. So I cannot get kernel crash dump...
But it seems my panic is same as PR mentioned. I'll try with
INVARIANTS and activate KASSERT macro.
Jun Kuriyama // kuriyama@sky.rim.or.jp
// kuriyama@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14457.29244.643560.68187Y>