On 6 Mar 2003, Thomas Seck wrote:
> * Bruce Evans ([EMAIL PROTECTED]):
>
> > This is the usual panic from sync() in panic() tripping over a lock.
> > Calling sync() in panic was never safe and now usually fails.
>
> Should one set "kern.sync_on_panic" to zero then?
Not a bad idea. It depends on
* Bruce Evans ([EMAIL PROTECTED]):
> This is the usual panic from sync() in panic() tripping over a lock.
> Calling sync() in panic was never safe and now usually fails.
Should one set "kern.sync_on_panic" to zero then?
--Thomas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
On Thu, 6 Mar 2003, Maxim Konovalov wrote:
> Several identical kernel panics with today -current. I suspect recent
> commits to subr_witness.c. See an attachment for details.
This seems to be most from a double fault triggering a cascade of errors.
There is no frame for the double fault so the cr
Hello,
Several identical kernel panics with today -current. I suspect recent
commits to subr_witness.c. See an attachment for details.
--
Maxim Konovalov, [EMAIL PROTECTED], [EMAIL PROTECTED]Script started on Thu Mar 6 18:42:01 2003
golf# gdb /usr/obj/usr/src/sys/GOLF5/kernel.debug -k vmcore.2
