Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Mar 2003 03:42:43 -0500 (EST)
From:      Jeff Roberson <jroberson@chesapeake.net>
To:        Julian Elischer <julian@elischer.org>
Cc:        FreeBSD current users <current@FreeBSD.ORG>
Subject:   Re: stacktrace of recent panic..(bremfree)
Message-ID:  <20030313034131.S43514-100000@mail.chesapeake.net>
In-Reply-To: <Pine.BSF.4.21.0303130033580.30228-100000@InterJet.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Mar 2003, Julian Elischer wrote:

>
> I got this today on a kernel checked out on the 10th.

Can you please disable sync on panic and get a dump from the first panic?
Then print out the contents of the buf in that stack for me?  A couple of
people have seen this now but I have not been able to repro it.

Thanks,
Jeff

>
> 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: 46m53s
> Dumping 255 MB
> ata0: resetting devices ..
> done
>  16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
> ---
> #0  doadump () at ../../../kern/kern_shutdown.c:239
> 239  dumping++;
> (kgdb)
> (kgdb) bt
> #0  doadump () at ../../../kern/kern_shutdown.c:239
> #1  0xc020e1ba in boot (howto=260) at ../../../kern/kern_shutdown.c:371
> #2  0xc020e423 in panic () at ../../../kern/kern_shutdown.c:542
> #3  0xc024d130 in bremfreel (bp=0xc6920078) at
> ../../../kern/vfs_bio.c:630
> #4  0xc024d042 in bremfree (bp=0x0) at ../../../kern/vfs_bio.c:612
> #5  0xc024f0e0 in vfs_bio_awrite (bp=0x0) at
> ../../../kern/vfs_bio.c:1682
> #6  0xc02dfe5a in ffs_fsync (ap=0xcc06b8b8) at
> ../../../ufs/ffs/ffs_vnops.c:257
> #7  0xc02def67 in ffs_sync (mp=0xc17e7400, waitfor=2, cred=0xc0eb5e00,
>     td=0xc03b31e0) at vnode_if.h:612
> #8  0xc0263f1b in sync (td=0xc03b31e0, uap=0x0)
>     at ../../../kern/vfs_syscalls.c:138
> #9  0xc020dd7c in boot (howto=256) at ../../../kern/kern_shutdown.c:280
> #10 0xc020e423 in panic () at ../../../kern/kern_shutdown.c:542
> #11 0xc024d5b2 in bwrite (bp=0xc68839f8) at ../../../kern/vfs_bio.c:795
> #12 0xc024df2c in bawrite (bp=0x0) at ../../../kern/vfs_bio.c:1138
> #13 0xc0255f0f in cluster_wbuild (vp=0xc1c206d8, size=8192, start_lbn=2,
> len=4)
>     at ../../../kern/vfs_cluster.c:996
> #14 0xc025550f in cluster_write (bp=0xc6920078, filesize=49152,
> seqcount=10)
>     at ../../../kern/vfs_cluster.c:596
> #15 0xc02e0a7c in ffs_write (ap=0xcc06bbc4) at
> ../../../ufs/ffs/ffs_vnops.c:728
> #16 0xc026c1e1 in vn_write (fp=0xc1b4f078, uio=0xcc06bc70,
>     active_cred=0xc1bc0e00, flags=0, td=0xc17d0a50) at vnode_if.h:417
> #17 0xc02312c8 in dofilewrite (td=0xc17d0a50, fp=0xc1b4f078, fd=0,
>     buf=0x896fc00, nbyte=0, offset=0, flags=0) at file.h:239
> #18 0xc0231109 in write (td=0xc17d0a50, uap=0xcc06bd10)
>     at ../../../kern/sys_generic.c:329
> #19 0xc033c46a in syscall (frame=
>       {tf_fs = 677314607, tf_es = 47, tf_ds = -1078001617, tf_edi =
> 677351712, tf_esi = 0, tf_ebp = -1077941192, tf_isp = -871973516, tf_ebx
> = 677363940, tf_edx = 20, tf_ecx = 0, tf_eax = 4, tf_trapno = 0, tf_err
> = 2, tf_eip = 677698275, tf_cs = 31, tf_eflags = 518, tf_esp =
> -1077941252, tf_ss = 47})
>     at ../../../i386/i386/trap.c:1030
> #20 0xc032bafd in Xint0x80_syscall () at {standard input}:138
> ---Can't read userspace from dump, or kernel process---
>
> I still have the kernel.debug and the coredump if anyone wants to look
> further..
>
> (am recompiling new kernel now. will see if it happens again)
> (ata disk, ufs1 filesystem)
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030313034131.S43514-100000>