[EMAIL PROTECTED]
Subject: Re: new panic under -current
On Mon, 14 Jan 2002, Alfred Perlstein wrote:
...
Can you cvsup and try to reproduce this?
Maybe.
Today I did:
- reducing my mainmem to 64M using hw.physmem=64M
- compiling and cleaning some packages garaphics/[mplayer|ogle] a few times
Hi,
a new panic while surfing under X:
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
On Mon, 14 Jan 2002 20:43:11 +0100, Michael Reifenberger wrote:
syncing disks... panic: bwrite: buffer is not busy???
Uptime: 4h47m36s
I can get these pretty easily by using modules that are out of sync with
the kernel.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On 14-Jan-02 Sheldon Hearn wrote:
On Mon, 14 Jan 2002 20:43:11 +0100, Michael Reifenberger wrote:
syncing disks... panic: bwrite: buffer is not busy???
Uptime: 4h47m36s
I can get these pretty easily by using modules that are out of sync with
the kernel.
That wasn't his real panic.
On Mon, 14 Jan 2002 12:37:16 PST, John Baldwin wrote:
I can get these pretty easily by using modules that are out of sync with
the kernel.
That wasn't his real panic. If you read teh whole log, a vrele() called from
fdrop_locked() did a vput(0x0), i.e. vput(NULL) which resulted in a
* Michael Reifenberger [EMAIL PROTECTED] [020114 11:47] wrote:
Hi,
a new panic while surfing under X:
Can you cvsup and try to reproduce this?
-Alfred
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, 14 Jan 2002, Alfred Perlstein wrote:
...
Can you cvsup and try to reproduce this?
Do you have some new -current patches in mind which could affect the problem?
My -current is as of today (with some local patches from bde regarding
slice-handling which shouldn't be related here).
I've