Le 2003-03-12, Jeff Roberson écrivait :
Can you please print bp? I'd like to know what all of the members are. A
cluster buf should NEVER have BX_BKGRDWRITE set. This is totally bogus.
Got that crash again, with sync-on-panic disabled. The interesting thing
is that the stack trace might
Le 2003-03-12, Jeff Roberson écrivait :
Can you disable sync on panic to make sure that something has not come
along and cleaned this buffer? I suspect that it has been modified after
the first panic. Do you know when this first started to happen? Do you
have any more clues into what
Le 2003-03-12, Jeff Roberson écrivait :
Can you please print bp? I'd like to know what all of the members are. A
cluster buf should NEVER have BX_BKGRDWRITE set. This is totally bogus.
(kgdb) fr
#11 0xc0232072 in bwrite (bp=0xce5313e0) at
/usr/src/sys/kern/vfs_bio.c:795
795
On Wed, 12 Mar 2003, Thomas Quinot wrote:
Le 2003-03-12, Jeff Roberson écrivait :
Can you please print bp? I'd like to know what all of the members are. A
cluster buf should NEVER have BX_BKGRDWRITE set. This is totally bogus.
(kgdb) fr
#11 0xc0232072 in bwrite (bp=0xce5313e0) at
-CURRENT as of this week-end on a Dell Inspiron 8200 laptop.
During desktop use :
panic: bremfree: removing a buffer not on a queue
panic messages:
---
panic: bwrite: buffer is not busy???
syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue
Uptime: 9h18m39s
I've trimmed to the relavent part of the stack.
On Tue, 11 Mar 2003, Thomas Quinot wrote:
#11 0xc0232072 in bwrite (bp=0xce5313e0) at /usr/src/sys/kern/vfs_bio.c:795
#12 0xc0232a7c in bawrite (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:1138
#13 0xc023a02b in cluster_wbuild (vp=0xc4a21124,
