From: Bosko Milekic <[EMAIL PROTECTED]>
> 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
On Wed, 5 Jan 2000, Jun Kuriyama wrote:
>From: Bosko Milekic <[EMAIL PROTECTED]>
>> You don't happen to have a backtrace?
>
>I don't have it. When my box gives no reaction, I've hit some keys,
>keys, keys...and rebooted automatically. At that time, I could not
>switch to VT1 from X with
From: Bosko Milekic <[EMAIL PROTECTED]>
> You don't happen to have a backtrace?
I don't have it. When my box gives no reaction, I've hit some keys,
keys, keys...and rebooted automatically. At that time, I could not
switch to VT1 from X with [Ctrl]+[Alt]+[F1].
> Was anything partic
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/
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
