search for: panicstr

...s in advance :) ultraviolet@tulip:~ %> uname -a FreeBSD tulip.epweb.co.za 4.8-STABLE FreeBSD 4.8-STABLE #0: Wed Jun 11 10:09:55 SAST 2003 root@tulip.epweb.co.za:/usr/src/sys/compile/TULIP i386 Panic message: IdlePTD at phsyical address 0x0042a000 initial pcb at physical address 0x0036e460 panicstr: vm_map_entry_create: kernel resources exhausted initial pcb at physical address 0x0036e460 panicstr: vm_map_entry_create: kernel resources exhausted panic messages: --- panic: vm_map_entry_create: kernel resources exhausted syncing disks... 2 2 done Uptime: 7d7h13m45s (kgdb) where #0 0xc01682aa...

Hi all! I'm having problems no end on my 4.8-STABLE box, and I hope you can help me. My processes get lots of signals (mostly 6, 10 and 11), and my kernel dumps core very often. I have the core dumps from the 4 latest crashes. See attachment for more info. Notice the common values for IdlePTD and initial pcb. Does this mean anything? There are other problems as well: 1) Some time ago KDE

....panic > certainty = 0x64 > asru = > sw:///:path=/var/crash/bofh-sol/.4f6725c1-509f-eba4-8774-e627e1925461 > resource = > sw:///:path=/var/crash/bofh-sol/.4f6725c1-509f-eba4-8774-e627e1925461 > savecore-succcess = 0 > os-instance-uuid = 4f6725c1-509f-eba4-8774-e627e1925461 > panicstr = BAD TRAP: type=e (#pf Page fault) rp=ffffff0010a5e920 addr=30 > occurred in module "zfs" due to a NULL pointer dereference > panicstack = unix:die+dd () | unix:trap+1799 () | unix:cmntrap+e6 () | > zfs:ddt_phys_decref+c () | zfs:zio_ddt_free+5c () | zfs:zio_execute+8d > () |...

...bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x00352000 initial pcb at physical address 0x002bf8e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xaaae fault code = supervisor write, page not present instruction pointer = 0x8:0xc0193de9 stack pointer = 0x10:0xcf466c70 frame pointer = 0x10:0xcf466c74 c...

...copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x05332000 initial pcb at physical address 0x0029f980 panicstr: page fault panic messages: --- Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc023ceeb stack pointer = 0x10:0xcf7d9ea4 frame pointer = 0x10:0xcf7d9ec0 code segment = base 0x0, limit 0xfffff, type 0x1b...

...4MB <ST36531A> [13446/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ==================================================================================== IdlePTD at phsyical address 0x002b4000 initial pcb at physical address 0x00237ea0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xe37e0000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0142ffa stack pointer = 0x10:0xd0200d20 frame pointer = 0x10:0xe37e000...

...d then the system panic'd. According to the crashdump, p->p_leader is NULL but according to the code, this can never happen. This is a UP Athlon XP-1800 with the kernel built for a K7. Anyone got any ideas? IdlePTD at phsyical address 0x003a3000 initial pcb at physical address 0x00302ac0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x184 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015c0dd stack pointer = 0x10:0xe18ebeb4 frame pointer = 0x10:0xe18ebed8 cod...

...debuging information follows... # uname -a FreeBSD digitalpimp.princenet 4.8-STABLE FreeBSD 4.8-STABLE #1: Thu Jun 12 14:13:23 EDT 2003 root@digitalpimp.princenet:/usr/src/sys/compile/PIMPIN48 i386 panic message: IdlePTD at phsyical address 0x0040c000 initial pcb at physical address 0x00353c40 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffff000a fault code = supervisor read, page not present instruction pointer = 0x8:0xc02639dc stack pointer = 0x10:0xd7508c10 frame pointer = 0x10:0xd7508c10 code segment = b...

...bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x0040f000 initial pcb at physical address 0x003618e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x121a2673 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0283ad3 stack pointer = 0x10:0xdf65dc3c frame pointer = 0x10:0xdf65dc5...

We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few days. This started shortly after upgrade from 6.2-RELEASE to 6.3-RELEASE with freebsd-update. Other than switching to a debugging kernel, a little sysctl tuning, and patching with freebsd-update, they are stock. The debugging kernel was built from source that is also being patched with freebsd-update. These systems are

...up. Then the system coredumped. Below is more information. Is this a serious problem? Please help me, I'm an inexperienced programmer and I can't do this alone. Daniela # gdb -k kernel.debug vmcore.0 ... IdlePTD at phsyical address 0x005ba000 initial pcb at physical address 0x004d3100 panicstr: ufsdirhash_lookup: bad offset in hash array panic messages: --- panic: ufsdirhash_lookup: bad offset in hash array syncing disks... 80 2 1 done Uptime: 1d21h53m1s /dev/vmmon: Module vmmon: unloaded dumping to dev #ad/0x30001, offset 1048704 dump ata0: resetting devices .. done 511 ... 0 --- #0...

...which I had done for a number of other aggregate routes). The only other "strange" thing about the box is that ds0 is loaded via kld. I will see if I can reproduce it on a non production box. ---Mike IdlePTD at phsyical address 0x0032e000 initial pcb at physical address 0x002a3d80 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc019a569 stack pointer = 0x10:0xdf0b1d28 frame pointer = 0x10:0xdf0b1d34 code...

...bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x005bf000 initial pcb at physical address 0x004dbb00 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 145 111 102 41 37 31 31 31 31 31 31 31 panic: lockmgr: locking against myself Uptime: 2d9h18m37s dumping to dev #ad/0x30031, offset 4718752 dump ata3: resetting devices .. done 767 766 765 764...

I''ve been testing ZFS since it came out on b27 and this week I BFUed to b30. I''ve seen two problems, one I''ll call minor and the other major. The hardware is a Dell PowerEdge 2600 with 2 3.2GHz Xeons, 2GB memory and a perc3 controller. I have created a filesystem for over 1000 users on it and take hourly snapshots, which destroy the one from 24 hours ago, except the

G'day ... David Schultz, in his spare time, has been working through some of the issues I've been able to 'tweak' in the unionfs code ... as he is currently working on forward-patching it to -CURRENT right now, he can't commit the code to the -STABLE tree ... in order to allow others using unionfs to test the patch (I've been running it a few weeks now on a very heavily

......and I'd been using the chance of having the system case open to build out another drive (ad2). 8-sec# gdb -k gdb -k /usr/obj/usr/src/sys/NORMAL/kernel.debug /opt/crash/vmcore.0 GNU gdb 4.18 (FreeBSD) [ ... ] IdlePTD at phsyical address 0x00473000 initial pcb at physical address 0x003b3700 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x36 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01d1092 stack pointer = 0x10:0xd08d3ca0 frame pointer = 0x10:0xd08d3cac code...

As others have noted, Tor's patch appears to be a total solution to the recent instability the PAE patch introduced. So, if you're experiencing panics with a recent kernel, or are in a position to stress a machine, please cvsup and give it a test! Thanks, Mike "Silby" Silbersack ---------- Forwarded message ---------- Date: Sat, 30 Aug 2003 08:39:08 -0700 (PDT) From: Tor Egge

...db/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf SMP 2 cpus IdlePTD at phsyical address 0x00375000 initial pcb at physical address 0x002db900 panicstr: rslock: cpu: 1, addr: 0xc02f1660, lock: 0x01000001 panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 fault virtual address = 0x8974238 fault code = supervisor read, page not present instruction pointer = 0x8:0xc...

.../binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x003ad000 initial pcb at physical address 0x0030cb40 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc408b0c8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc025fa19 stack pointer = 0x10:0xe8ba6e24 frame pointer = 0x10:0xe8ba6e2...

...../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf SMP 2 cpus IdlePTD at phsyical address 0x0032c000 initial pcb at physical address 0x002a29e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x18 fault code = supervisor write, page not present instruction pointer = 0x8:0xc01e1725 stack pointer = 0x10:0xfd0...