Re: Fatal Trap 12 in various processes always at address 0x3030313a
--- On Sun, 8/30/09, Gavin Atkinson ga...@freebsd.org wrote: From: Gavin Atkinson ga...@freebsd.org Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: Richard Mahlerwein mahle...@yahoo.com Cc: FreeBSD-Stable freebsd-stable@FreeBSD.org Date: Sunday, August 30, 2009, 3:47 PM On Sat, 29 Aug 2009, Richard Mahlerwein wrote: (Sorry, update to subject to be something) 3 weeks ago: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) [snip] Does anyone have a further recommendation on what to do, try, test or change? Firstly, please set up a dump partition by adding 'dumpdev=AUTO' to your rc.conf. Then, can you compile in the kernel debugger (options KGB / options DDB) and when this happens again, please obtain a backtrace from the debugger with the bt command. Then, give the show registers command so that we can establish which register is pointing to the odd address. Finally, issue the call doadump() command to hopefully save a copy of the kernel dump for later analysis. Thanks, Gavin No problem, but for future reference by others reading this thread, the handbook says KGB should be KDB, which is what I'm enabling in the kernel config. DDB is fine. http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fatal Trap 12 in various processes always at address 0x3030313a
From: Gavin Atkinson ga...@freebsd.org Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: Richard Mahlerwein mahle...@yahoo.com Cc: FreeBSD-Stable freebsd-stable@FreeBSD.org Date: Sunday, August 30, 2009, 3:47 PM On Sat, 29 Aug 2009, Richard Mahlerwein wrote: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) Does anyone have a further recommendation on what to do, try, test or change? Firstly, please set up a dump partition by adding 'dumpdev=AUTO' to your rc.conf. Then, can you compile in the kernel debugger (options KGB / options DDB) and when this happens again, please obtain a backtrace from the debugger with the bt command. Then, give the show registers command so that we can establish which register is pointing to the odd address. Finally, issue the call command to hopefully save a copy of the kernel dump for later analysis. Thanks, Gavin Error at virtual address 0x3030313a current process 352(sysctl) bt says (typing blind, but I think I got it): Tracing pid 352 tid 100044 td 0xc3378480 sysctl_devctl_disable(c0c80ac0,0,0,d82fcba4,d82fcba4...) at sysctl_devctl_disable+0xaa sysctl_root(d82fcba4,4,1,d82fcc60,0,...) at sysctl_root+0x187 userland_sysctl(c3378480,d82fcc14,3,0,0,...) at userland_sysctl+0x1c4 __sysctl(c3378480,d82fccfc,18,d82fcd38,d82fcd2c,...) at __sysctl_0x94 syscall(d82fcd38) at syscall_0x335 Xint0x80_syscall() at Xint0x80_syscall_0x20 --- syscall (202,FreeBSD ELF32, __sysctl, eip = 0x2815beaf, esp=0xbfbfe55c, epb = 0xbfbfe588 --- show registers : cs 0x20 ds 0xc1470028 es 0xc1470028 fs 0xc1460008 ss 0x28 eax 0xc0cea0cc devsoftc_0x4c ecx 0 edx 0x30303132 ebx 0xc3181350 esp 0xd82fcb34 ebp 0xd82fcb54 esi 0 edi 0 eip 0xc08218da sysctl_devctl_disable+0xaa efl 0x10202 sysctl_devctl_disable+0xaa: movl %eax,0x8(%edx) I hope that tells someone on the list way more than it tells me. Thanks again for all the help so far! -Rich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fatal Trap 12 in various processes always at address 0x3030313a
From: Richard Mahlerwein mahle...@yahoo.com Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: FreeBSD-Stable freebsd-stable@freebsd.org Date: Tuesday, September 1, 2009, 2:58 PM From: Gavin Atkinson ga...@freebsd.org Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: Richard Mahlerwein mahle...@yahoo.com Cc: FreeBSD-Stable freebsd-stable@FreeBSD.org Date: Sunday, August 30, 2009, 3:47 PM On Sat, 29 Aug 2009, Richard Mahlerwein wrote: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) Does anyone have a further recommendation on what to do, try, test or change? Firstly, please set up a dump partition by adding 'dumpdev=AUTO' to your rc.conf. Then, can you compile in the kernel debugger (options KGB / options DDB) and when this happens again, please obtain a backtrace from the debugger with the bt command. Then, give the show registers command so that we can establish which register is pointing to the odd address. Finally, issue the call command to hopefully save a copy of the kernel dump for later analysis. Thanks, Gavin Error at virtual address 0x3030313a current process 352(sysctl) bt says (typing blind, but I think I got it): Tracing pid 352 tid 100044 td 0xc3378480 sysctl_devctl_disable(c0c80ac0,0,0,d82fcba4,d82fcba4...) at sysctl_devctl_disable+0xaa sysctl_root(d82fcba4,4,1,d82fcc60,0,...) at sysctl_root+0x187 userland_sysctl(c3378480,d82fcc14,3,0,0,...) at userland_sysctl+0x1c4 __sysctl(c3378480,d82fccfc,18,d82fcd38,d82fcd2c,...) at __sysctl_0x94 syscall(d82fcd38) at syscall_0x335 Xint0x80_syscall() at Xint0x80_syscall_0x20 --- syscall (202,FreeBSD ELF32, __sysctl, eip = 0x2815beaf, esp=0xbfbfe55c, epb = 0xbfbfe588 --- show registers : cs 0x20 ds 0xc1470028 es 0xc1470028 fs 0xc1460008 ss 0x28 eax 0xc0cea0cc devsoftc_0x4c ecx 0 edx 0x30303132 ebx 0xc3181350 esp 0xd82fcb34 ebp 0xd82fcb54 esi 0 edi 0 eip 0xc08218da sysctl_devctl_disable+0xaa efl 0x10202 sysctl_devctl_disable+0xaa: movl %eax,0x8(%edx) I hope that tells someone on the list way more than it tells me. Thanks again for all the help so far! -Rich I hope changing back to non-text (to get around some messed-up-ed-ness I've been having in my Yahoo account) won't mess this up too bad. Please don't yell at me if it does - just a polite mention will do. :) I changed devd_enable=NO to devd_enable=YES in rc.conf, and get THIS error (which is back to being almost the same as the original one I got on the first attempt at a new kernel) vault virtual address 0x3030313a fault code = supervisor write, page not present instruction pointer = 0x20:0xc08216dc stack pointer = 0x28: 0xd8311b70 frame pointer = 0x28:0xd8300b8c code segment = base 0x0, limit 0xf, type 0x1b =DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process -= 255 (devd) [thread pid 355 tid 100045 ] stopped at devread+0x12c: movl %eax,0x8(%edx) bt says: Tracing pid 355 tid 100045 tc 0xc3378240 devread(c30df400,d8300c60,0,c3434564,d8300bd8,...) at devread+0x12c giant_read(c30df400,d8300c60,0,0,400,...) at giant_read+0x89 devfs_read_f(c33adb48,d8300c60,c3071300,0,c33adb48,...) at dofileread+0x96 kern_readv(c3378240,3,d8300c60,bfbfe9f7,400,...) at kern_readv+0x58 read(c3378240,d8300cfc,c,8000,369e99,...) at read+0x4f syscall(d8300d38) at syscall_0x335 Xint0x80_syscall() at Xint0x80_syscall_0x20 --- syscall (3, FreeBSD ELF32, read), eip - 0x8086c7f, esp = 0xbfbfe9bc, ebp = 0xbfbfee98 --- And show registers: cs=20,ds=d8300028, es=d8300028,fs= d838, ss=28, eax=c0cea0cc devsoftc_0x4c ecx=0x4,, edx=0x30303132, ebx=oxc3181350, esp=pxd8300b70, ebp=oxd8300b8c, esi=0xc30df400, edi=0x6, eip=oxc08216dc devread_0x12c, efl=0x10202 devread+0x12c: movl %eax, 0x8(%edx) I'm still not quite sure what that's telling me, but is it significant that it's the same virtual location with a different piece of code loaded there because of a change in options? No other change was made, just changing devd_enable. I'm going to check loader.conf, too, as someone else suggested (but at this point, I didn't want to muddy the waters by changing two things at once). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fatal Trap 12 in various processes always at address 0x3030313a
From: Richard Mahlerwein mahle...@yahoo.com Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: FreeBSD-Stable freebsd-stable@freebsd.org Date: Tuesday, September 1, 2009, 2:58 PM From: Gavin Atkinson ga...@freebsd.org Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: Richard Mahlerwein mahle...@yahoo.com Cc: FreeBSD-Stable freebsd-stable@FreeBSD.org Date: Sunday, August 30, 2009, 3:47 PM On Sat, 29 Aug 2009, Richard Mahlerwein wrote: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) Does anyone have a further recommendation on what to do, try, test or change? Firstly, please set up a dump partition by adding 'dumpdev=AUTO' to your rc.conf. Then, can you compile in the kernel debugger (options KGB / options DDB) and when this happens again, please obtain a backtrace from the debugger with the bt command. Then, give the show registers command so that we can establish which register is pointing to the odd address. Finally, issue the call command to hopefully save a copy of the kernel dump for later analysis. Thanks, Gavin TWO Pieces of information here, and please excuse the repost - darn mailer's making me look like such a noob (not like I need help at that!). Again, mention it if this screws up the formatting too badly. Now that I know certain stuff doesn't come across, I have not used it so hopefully this will turn out nicely. Error at virtual address 0x3030313a current process 352(sysctl) bt says (typing blind, but I think I got it): Tracing pid 352 tid 100044 td 0xc3378480 sysctl_devctl_disable(c0c80ac0,0,0,d82fcba4,d82fcba4...) at sysctl_devctl_disable+0xaa sysctl_root(d82fcba4,4,1,d82fcc60,0,...) at sysctl_root+0x187 userland_sysctl(c3378480,d82fcc14,3,0,0,...) at userland_sysctl+0x1c4 __sysctl(c3378480,d82fccfc,18,d82fcd38,d82fcd2c,...) at __sysctl_0x94 syscall(d82fcd38) at syscall_0x335 Xint0x80_syscall() at Xint0x80_syscall_0x20 --- syscall (202,FreeBSD ELF32, __sysctl, eip = 0x2815beaf, esp=0xbfbfe55c, epb = 0xbfbfe588 --- show registers : cs 0x20 ds 0xc1470028 es 0xc1470028 fs 0xc1460008 ss 0x28 eax 0xc0cea0cc devsoftc_0x4c ecx 0 edx 0x30303132 ebx 0xc3181350 esp 0xd82fcb34 ebp 0xd82fcb54 esi 0 edi 0 eip 0xc08218da sysctl_devctl_disable+0xaa efl 0x10202 sysctl_devctl_disable+0xaa: movl %eax,0x8(%edx) I hope that tells someone on the list way more than it tells me. On a hunch, I changed devd_enable=NO to devd_enable=YES in rc.conf, and get THIS error (which is back to being almost the same as the original one I got on the first attempt at a new kernel) vault virtual address 0x3030313a fault code = supervisor write, page not present instruction pointer = 0x20:0xc08216dc stack pointer = 0x28: 0xd8311b70 frame pointer = 0x28:0xd8300b8c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process -= 255 (devd) [thread pid 355 tid 100045 ] stopped at devread+0x12c: movl %eax,0x8(%edx) bt says: Tracing pid 355 tid 100045 tc 0xc3378240 devread(c30df400,d8300c60,0,c3434564,d8300bd8,...) at devread+0x12c giant_read(c30df400,d8300c60,0,0,400,...) at giant_read+0x89 devfs_read_f(c33adb48,d8300c60,c3071300,0,c33adb48,...) at dofileread+0x96 kern_readv(c3378240,3,d8300c60,bfbfe9f7,400,...) at kern_readv+0x58 read(c3378240,d8300cfc,c,8000,369e99,...) at read+0x4f syscall(d8300d38) at syscall_0x335 Xint0x80_syscall() at Xint0x80_syscall_0x20 --- syscall (3, FreeBSD ELF32, read), eip - 0x8086c7f, esp = 0xbfbfe9bc, ebp = 0xbfbfee98 --- And show registers: cs=20, ds=d8300028, es=d8300028, fs= d838, ss=28, eax=c0cea0cc devsoftc_0x4c ecx=0x4, edx=0x30303132, ebx=oxc3181350, esp=pxd8300b70, ebp=oxd8300b8c, esi=0xc30df400, edi=0x6, eip=oxc08216dc devread_0x12c, efl=0x10202 devread+0x12c: movl %eax, 0x8(%edx) I'm still not quite sure what that's telling me, but is it significant that it's the same virtual location with a different piece of code loaded there because of a change in options? No other change was made, just changing devd_enable. I'm going to check loader.conf, too, as someone else suggested (but at this point, I didn't want to muddy the waters by changing two things at once). Thanks again, Rich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fatal Trap 12 in various processes always at address 0x3030313a
In the last episode (Aug 29), Richard Mahlerwein said: (Sorry, update to subject to be something) 3 weeks ago: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) At this point you will want to get a kernel dump and post its stack trace. 0x3030313a in ASCII is 001:, so some string probably overflowed a buffer. http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html -- Dan Nelson dnel...@allantgroup.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fatal Trap 12 in various processes always at address 0x3030313a
Richard Mahlerwein wrote: --- On Sat, 8/29/09, Marat N.Afanasyev ama...@ksu.ru wrote: From: Marat N.Afanasyev ama...@ksu.ru Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: mahle...@yahoo.com Cc: FreeBSD-Stable freebsd-stable@freebsd.org Date: Saturday, August 29, 2009, 6:59 PM such trap could be triggered by 'floating' memory/cache error. and i think that you should try to suspect memory first. memtest helps to diagnose most of memory problems, but not all. -- SY, Marat How can I test that? If a buildworld will complete successfully several times (with mildly different source, even), and memtest86+ won't find it, how can I tell if that's the problem or not? I ususally do md5 of large tmpfs based file. make tmpfs as large as possible, create a big file in the tmpfs and calculate md5 of this file many times. -- SY, Marat smime.p7s Description: S/MIME Cryptographic Signature
Re: Fatal Trap 12 in various processes always at address 0x3030313a
On Sat, 29 Aug 2009, Richard Mahlerwein wrote: (Sorry, update to subject to be something) 3 weeks ago: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) [snip] Does anyone have a further recommendation on what to do, try, test or change? Firstly, please set up a dump partition by adding 'dumpdev=AUTO' to your rc.conf. Then, can you compile in the kernel debugger (options KGB / options DDB) and when this happens again, please obtain a backtrace from the debugger with the bt command. Then, give the show registers command so that we can establish which register is pointing to the odd address. Finally, issue the call doadump() command to hopefully save a copy of the kernel dump for later analysis. Thanks, Gavin___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fatal Trap 12 in various processes always at address 0x3030313a
Richard Mahlerwein wrote: (Sorry, update to subject to be something) 3 weeks ago: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) I redid the *whole* process in single user mode, yet no difference. I was out of town for 2.5 weeks after that, then busy for a few days, which brings me to now: TODAY: I booted to my memtest86+ CD, let it run through which it did with no issues noted. I blew away my /usr/src and resynced as of about noon today. After following through all steps to rebuild, I now get a fatal trap 12... Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 352 (sysctl) Same virtual address, different process. Umm. Interesting. I'm at a loss. Google's been of little help, and searching these lists hasn't turned up much either. Does anyone have a further recommendation on what to do, try, test or change? BTW, I'm GENERIC. Rich Mahlerwein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org such trap could be triggered by 'floating' memory/cache error. and i think that you should try to suspect memory first. memtest helps to diagnose most of memory problems, but not all. -- SY, Marat smime.p7s Description: S/MIME Cryptographic Signature
Re: Fatal Trap 12 in various processes always at address 0x3030313a
--- On Sat, 8/29/09, Marat N.Afanasyev ama...@ksu.ru wrote: From: Marat N.Afanasyev ama...@ksu.ru Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a To: mahle...@yahoo.com Cc: FreeBSD-Stable freebsd-stable@freebsd.org Date: Saturday, August 29, 2009, 6:59 PM Richard Mahlerwein wrote: (Sorry, update to subject to be something) 3 weeks ago: I upgraded from 7.1-PRELEASE to -stable and all seemed fine until I rebooted out of single user mode after doing make installworld and mergemaster. At that point, near the end of the boot sequence I got a core dump, apparently triggered by devd. Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 355 (devd) I redid the *whole* process in single user mode, yet no difference. I was out of town for 2.5 weeks after that, then busy for a few days, which brings me to now: TODAY: I booted to my memtest86+ CD, let it run through which it did with no issues noted. I blew away my /usr/src and resynced as of about noon today. After following through all steps to rebuild, I now get a fatal trap 12... Fatal trap 12: page fault while in kernel mode. cpu id = 0; apic id = 00 fault virtual address = 0x3030313a fault code = supervisor write, page not present [snip] current process = 352 (sysctl) Same virtual address, different process. Umm. Interesting. I'm at a loss. Google's been of little help, and searching these lists hasn't turned up much either. Does anyone have a further recommendation on what to do, try, test or change? BTW, I'm GENERIC. Rich Mahlerwein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org such trap could be triggered by 'floating' memory/cache error. and i think that you should try to suspect memory first. memtest helps to diagnose most of memory problems, but not all. -- SY, Marat How can I test that? If a buildworld will complete successfully several times (with mildly different source, even), and memtest86+ won't find it, how can I tell if that's the problem or not? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
