Date: Fri, 14 Feb 2003 16:53:07 -0800 From: Kirk McKusick <mckusick@beastie.mckusick.com> To: Kris Kennaway <kris@obsecurity.org> Cc: current@FreeBSD.ORG, fs@FreeBSD.ORG, iedowse@FreeBSD.ORG Subject: Re: INVARIANTS-related fs panic on alpha Message-ID: <200302150053.h1F0r7FL044055@beastie.mckusick.com> In-Reply-To: Your message of "Fri, 14 Feb 2003 15:54:13 PST." <20030214235413.GA4079@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I have tried running my test machine out of filesystem space (repeatedly) and have not been able to get this panic. I will keep running that test in the hopes that it will show up. In the meantime, if you can come up with an example that reliably triggers it, that would be most helpful. Kirk McKusick =-=-=-=-=-= Date: Fri, 14 Feb 2003 15:54:13 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Kris Kennaway <kris@obsecurity.org> Cc: current@FreeBSD.ORG, fs@FreeBSD.ORG, kirk@mckusick.com, iedowse@FreeBSD.ORG Subject: Re: INVARIANTS-related fs panic on alpha On Sat, Jan 25, 2003 at 12:12:34AM -0800, Kris Kennaway wrote: > One of the alpha package clients panicked with this. It was under > very high load at the time (25 simultaneous package builds): >=20 > fatal kernel trap: >=20 > trap entry =3D 0x2 (memory management fault) > faulting va =3D 0xdeadc0dedeadc0e6 > type =3D access violation > cause =3D store instruction > pc =3D 0xfffffc000053453c > ra =3D 0xfffffc000053b2a8 > sp =3D 0xfffffe001da15b30 > curthread =3D 0xfffffc003e33b930 > pid =3D 3, comm =3D g_up >=20 > Stopped at add_to_worklist+0xac: stq a0,0x8(t0) <0xdeadc0dedea= dc0e6> <a0=3D0xfffffc0035deb200,t0=3D0xdeadc0dedeadc0de> > db> trace > add_to_worklist() at add_to_worklist+0xac > handle_written_inodeblock() at handle_written_inodeblock+0x5e8 > softdep_disk_write_complete() at softdep_disk_write_complete+0xac > bufdone() at bufdone+0x19c > bufdonebio() at bufdonebio+0x1c > biodone() at biodone+0x28 > g_dev_done() at g_dev_done+0xd8 > biodone() at biodone+0x28 > g_io_schedule_up() at g_io_schedule_up+0x4c > g_up_procbody() at g_up_procbody+0x9c > fork_exit() at fork_exit+0x100 > exception_return() at exception_return > --- root of call graph --- > db> I'm still getting this (on i386 and alpha). I believe it is related to a filesystem becoming full. Can someone please investigate? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302150053.h1F0r7FL044055>