Re: INVARIANTS-related fs panic on alpha
On Fri, Feb 14, 2003 at 06:51:19PM -0800, Kris Kennaway wrote: On Fri, Feb 14, 2003 at 04:53:07PM -0800, Kirk McKusick wrote: 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. Hmm. The machines that have panicked are likely to have been under extreme disk load at the time they ran out of space (e.g. extracting several dozen large tarballs simultaneously) [1]. I'll have to see if I can trigger this. Kris [1] Due to the stupidity of the bento package build scheduler and various other contributing factors. Got this again when a filesystem filled up. Kris pgp0.pgp Description: PGP signature
Re: INVARIANTS-related fs panic on alpha
On Sun, Feb 23, 2003 at 01:37:24PM -0800, Kris Kennaway wrote: Hmm. The machines that have panicked are likely to have been under extreme disk load at the time they ran out of space (e.g. extracting several dozen large tarballs simultaneously) [1]. I'll have to see if I can trigger this. Kris [1] Due to the stupidity of the bento package build scheduler and various other contributing factors. Got this again when a filesystem filled up. I got a crashdump and gdb backtrace this time..let me know if you want it. Kris pgp0.pgp Description: PGP signature
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): fatal kernel trap: trap entry = 0x2 (memory management fault) faulting va= 0xdeadc0dedeadc0e6 type = access violation cause = store instruction pc = 0xfc53453c ra = 0xfc53b2a8 sp = 0xfe001da15b30 curthread = 0xfc003e33b930 pid = 3, comm = g_up Stopped at add_to_worklist+0xac: stq a0,0x8(t0) 0xdeadc0dedeadc0e6 a0=0xfc0035deb200,t0=0xdeadc0dedeadc0de 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 msg52364/pgp0.pgp Description: PGP signature
Re: INVARIANTS-related fs panic on alpha
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 [EMAIL PROTECTED] To: Kris Kennaway [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] 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 0xfc53453c ra =3D 0xfc53b2a8 sp =3D 0xfe001da15b30 curthread =3D 0xfc003e33b930 pid =3D 3, comm =3D g_up =20 Stopped at add_to_worklist+0xac: stq a0,0x8(t0) 0xdeadc0dedea= dc0e6 a0=3D0xfc0035deb200,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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: INVARIANTS-related fs panic on alpha
On Fri, Feb 14, 2003 at 04:53:07PM -0800, Kirk McKusick wrote: 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. Hmm. The machines that have panicked are likely to have been under extreme disk load at the time they ran out of space (e.g. extracting several dozen large tarballs simultaneously) [1]. I'll have to see if I can trigger this. Kris [1] Due to the stupidity of the bento package build scheduler and various other contributing factors. msg52372/pgp0.pgp Description: PGP signature
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): fatal kernel trap: trap entry = 0x2 (memory management fault) faulting va= 0xdeadc0dedeadc0e6 type = access violation cause = store instruction pc = 0xfc53453c ra = 0xfc53b2a8 sp = 0xfe001da15b30 curthread = 0xfc003e33b930 pid = 3, comm = g_up Stopped at add_to_worklist+0xac: stq a0,0x8(t0) 0xdeadc0dedeadc0e6 a0=0xfc0035deb200,t0=0xdeadc0dedeadc0de 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 Here it is again: fatal kernel trap: trap entry = 0x4 (unaligned access fault) faulting va= 0xdeadc0dedeadc0e6 opcode = 0x2d register = 0x10 pc = 0xfc534540 ra = 0xfc53b2a8 sp = 0xfe0006c0fb30 curthread = 0xfc0007ba7930 pid = 3, comm = g_up Stopped at add_to_worklist+0xb0: ldq t0,0x7c60(gp) 0xfc6581d0 t0=0xdeadc0dedeadc0de,gp=0xfc650570 db trace add_to_worklist() at add_to_worklist+0xb0 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 msg51086/pgp0.pgp Description: PGP signature
