On Sun, 13 Oct 2002, Kris Kennaway wrote:
Date: Sun, 13 Oct 2002 17:47:17 -0700
From: Kris Kennaway [EMAIL PROTECTED]
To: Michael Reifenberger [EMAIL PROTECTED]
Cc: FreeBSD-Current [EMAIL PROTECTED]
Subject: Re: Still under -current: bwrite: buffer is not busy???
On Mon, Oct 14, 2002
Hi,
Oha!
Is the attached backtrace from the bwrite or the vm_fault panic then?
If from the wrong panic, how to get the real one?
kern.sync_on_panic=0 in /etc/sysctl.conf
Martin
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
On Mon, 14 Oct 2002, Martin Blapp wrote:
...
kern.sync_on_panic=0 in /etc/sysctl.conf
Thanks!
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Oct 14, 2002 at 11:08:36AM +0200, Michael Reifenberger wrote:
FYI, the above line is the real panic message..the bwrite panic is
secondary and occurs when trying to sync disks.
?ha!
Is the attached backtrace from the bwrite or the vm_fault panic then?
If from the wrong panic,
Michael Reifenberger schrieb:
Hi,
I still get the following panic (2 are attached) under -current
on my notebook when doing a 'portupgrade -R -f kdebase'.
Anyone else sees this?
Yes, I also do get these type of panics during heavy FS activity (vm
fault, double fault, etc.)
I can panic my
Hi,
I still get the following panic (2 are attached) under -current
on my notebook when doing a 'portupgrade -R -f kdebase'.
Anyone else sees this?
### crash1 ###
GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General
On Mon, Oct 14, 2002 at 12:42:52AM +0200, Michael Reifenberger wrote:
panic: bwrite: buffer is not busy???
panic messages:
---
panic: vm_fault: fault on nofault entry, addr: cd36f000
FYI, the above line is the real panic message..the bwrite panic is
secondary and occurs when trying to sync
