On 1 Dec, Stefan Ehmann wrote:
On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
Can you reproduce this problem without bktr?
snip
You are getting a double panic, with the second happening during the
file system sync. The code seems to be be tripping over the same mount
list entry each time.
This happens to me several times a day (cvsup from yesterday didn't
change anything). The panic message is always the same, the backtrace is
different though (but always seems to be file system related in some
way)
Here's one from today:
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software
On Sun, 2003-11-30 at 11:13, Stefan Ehmann wrote:
This happens to me several times a day (cvsup from yesterday didn't
change anything). The panic message is always the same, the backtrace is
different though (but always seems to be file system related in some
way)
Here's one from today:
As
On 30 Nov, Stefan Ehmann wrote:
On Sun, 2003-11-30 at 11:13, Stefan Ehmann wrote:
This happens to me several times a day (cvsup from yesterday didn't
change anything). The panic message is always the same, the backtrace is
different though (but always seems to be file system related in some
Can you reproduce this problem without bktr?
#6 0xc06743d8 in calltrap () at {standard input}:94
#7 0xc0505b53 in _mtx_lock_flags (m=0x0, opts=0,
file=0xc06bfc1d /usr/src/sys/kern/kern_lock.c, line=228)
at /usr/src/sys/kern/kern_mutex.c:214
#8 0xc0502b54 in lockmgr
On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
Can you reproduce this problem without bktr?
snip
You are getting a double panic, with the second happening during the
file system sync. The code seems to be be tripping over the same mount
list entry each time. Maybe the mount list is getting
On 1 Dec, Stefan Ehmann wrote:
On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
Can you reproduce this problem without bktr?
snip
You are getting a double panic, with the second happening during the
file system sync. The code seems to be be tripping over the same mount
list entry each time.
