Date: Sat, 1 Jan 2000 23:03:39 -0500 (EST) From: Bosko Milekic <bmilekic@dsuper.net> To: Jun Kuriyama <kuriyama@sky.rim.or.jp> Cc: current@FreeBSD.ORG Subject: Re: panic at kern/uipc_socket2.c Message-ID: <Pine.OSF.4.05.10001012256280.28369-100000@oracle.dsuper.net> In-Reply-To: <14446.48302.292419.80479F@localhost.sky.rim.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2 Jan 2000, Jun Kuriyama wrote: !> !>I don't know what I did at that time, but my box is panic'ed with this !>message. !> !>----- !>Jan 1 16:19:21 leda kernel: panic: sbflush: cc 0 || mb 0xc05a7400 || mbcnt 256 !>----- !> !>It seems that this message is created by sbflush() in !>kern/uipc_socket2.c. !> !>Should I add some hooks into this function to display details !>preparing for when I get this panic()? !> !> !>Jun Kuriyama // kuriyama@sky.rim.or.jp !> // kuriyama@FreeBSD.org !> You don't happen to have a backtrace? Was anything particular happening at the time of the crash? Do you have any way to not necessarily directly reproduce the panic but rather "force" it to happen (e.g. as a consequence of execution of something or, even as a result of some external "trigger")? -- Bosko Milekic Email: bmilekic@dsuper.net WWW: http://pages.infinit.net/bmilekic/ -- 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?Pine.OSF.4.05.10001012256280.28369-100000>