Date: Wed, 09 Feb 2005 22:40:03 -0600 From: Eric Anderson <anderson@centtech.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-current@freebsd.org Subject: Re: Panic - FFS background buffer bla bla Message-ID: <420AE5A3.3040406@centtech.com> In-Reply-To: <20050210043710.GA26601@xor.obsecurity.org> References: <420ADAFC.40504@centtech.com> <20050210040102.GA11457@xor.obsecurity.org> <420ADEF7.30003@centtech.com> <20050210042321.GA26438@xor.obsecurity.org> <420AE1E1.5030403@centtech.com> <20050210043710.GA26601@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: >On Wed, Feb 09, 2005 at 10:24:01PM -0600, Eric Anderson wrote: > > >>Kris Kennaway wrote: >> >> >> >>>On Wed, Feb 09, 2005 at 10:11:35PM -0600, Eric Anderson wrote: >>> >>> >>> >>> >>> >>>>After rebooting (with a console plugged in), I get this: >>>>Fast boot: skipping disk checks. >>>>panic: panic: thread 100079(cp):2 holds Giant but isn't blocked on a lock >>>> >>>>cpuid = 0 >>>>KDB: enter: panic >>>>[thread pid 27 tid 100001 ] >>>>Stopped at kdb_enter+0x30: leave >>>> >>>>Backtrace: >>>> >>>> >>>> >>[..snip..] >> >> >> >>>>Hope that helps.. Anything else I can give you? >>>> >>>> >>>> >>>> >>>That's actually not the real panic. Look at the backtraces of other >>>processes to find the first panic. If you can examine the core in gdb >>>to obtain source code line numbers, that would help too. >>> >>> >>> >>> >>Oh.. Ok, well, how do I find the real panic? I can do any debugging >>needed - but I'm not sure what to do here as far as examining the core >>in gdb.. >> >> > >I already said..look at the backtraces of the other processes. You'll >find another one that has panicked. > > Sorry - after going through a few, I found this one: Tracing pid 127 tid 100079 td 0xc255ecf0 0 0 0000204 [SLPQ - 0xc0a9a568] sched_switch(c255ecf0,0,2,118,810afe45) at sched_switch+0x1a0 mi_switch(2,0,c097b6e6,252,0) at mi_switch+0x2d6 critical_exit(c0a24d00,0,0,0,0) at critical_exit+0xb2 intr_execute_handlers(c0a24d00,e7dec324,0,0,c255ecf0) at intr_execute_handlers+0 xd4 atpic_handle_intr(0) at atpic_handle_intr+0xcf Xatpic_intr0() at Xatpic_intr0+0x20 --- interrupt, eip = 0xc06f10d2, esp = 0xe7dec368, ebp = 0xe7dec37c --- critical_exit(c0aad0a0,1,c09793e7,18a) at critical_exit+0xf2 _mtx_unlock_spin_flags(c0aad0a0,0,c0998294,a23,30f000c) at _mtx_unlock_spin_flag s+0xbd siocnputc(c0a1ffa0,20,5,e7dec4f0,20) at siocnputc+0xe9 cnputc(20,ffffffff,0,1,c097a1d0) at cnputc+0x6a putchar(20,e7dec4f0,38,e7dec4f8,0) at putchar+0x5c kvprintf(c097a1c9,c06fc0c0,e7dec4f0,a,e7dec510) at kvprintf+0x8d printf(c097a1c9,c0a45040,c09811a1,e7dec540,c255ecf0) at printf+0x55 panic(c09811a1,d19f4fc8,c0730c71,c0a92ec0,0) at panic+0xe8 bufwrite(d19f4fc8,0,c0991b40,652,0) at bufwrite+0x84 ffs_bufwrite(d19f4fc8,0,c09907be,1407,c097d9cd) at ffs_bufwrite+0x2f8 flush_pagedep_deps(c254dcf0,c251fc00,c254ae74,129b,2) at flush_pagedep_deps+0x2d d softdep_sync_metadata(c254dcf0,0,c0991de3,129,1) at softdep_sync_metadata+0x501 ffs_syncvnode(c254dcf0,1,e7dec688,c0706f33,c0a760c0) at ffs_syncvnode+0x3a5 ffs_truncate(c254dcf0,200,0,880,c220e780) at ffs_truncate+0x5be ufs_direnter(c254dcf0,c25d4450,e7dec8e8,e7decbfc,0) at ufs_direnter+0x980 ufs_makeinode(81a4,c254dcf0,e7decbe8,e7decbfc,e7deca64) at ufs_makeinode+0x4e7 ufs_create(e7deca64,e7decd14,e7decbd4,e7decd14,e7decb20) at ufs_create+0x37 VOP_CREATE_APV(c0a17b80,e7deca64,2,2,1) at VOP_CREATE_APV+0xbc vn_open_cred(e7decbd4,e7deccd4,1a4,c220e780,4) at vn_open_cred+0x1fb vn_open(e7decbd4,e7deccd4,1a4,4,c0a927d8) at vn_open+0x33 kern_open(c255ecf0,804b048,0,602,21b6) at kern_open+0xc8 open(c255ecf0,e7decd14,c,3ff,3) at open+0x36 syscall(2f,2f,2f,805f100,bfbfeea4) at syscall+0x2a0 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x280cad6f, esp = 0xbfbfec5c, ebp = 0xbfbfeca8 --- Sorry for any wrapping - I'm using a windows pc to grab this using hyperterminal (eek!).. Does that help? Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?420AE5A3.3040406>