Re: panic on heavy read/writes (5.1 + vinum)
There are two files in /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum One is vinum.ko and the other is vinum.ko.debug (Both are not stripped) I have tried the gdb dump with vinum.paths pointing to either one of them and it still gives the error mentioned below (Attempt to extract..) -- Hari On Mon, Aug 18, 2003 at 10:15:32PM -0500, Hari Bhaskaran wrote: ok, here is it, trace for kernel panic NOTE: There seems to a problem in the .gdbinit files (I may need your help on that). panic: free locked buf panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02d15f9 stack pointer = 0x10:0xd257d858 frame pointer = 0x10:0xd257d88c 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 = 94137 (genattrtab) trap number = 12 panic: page fault syncing disks, buffers remaining... 2220 2220 panic: free locked buf Uptime: 5h12m33s Dumping 256 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- And here is the output on gdb f bt commands (kgdb) f 1 #1 0xc0303b9a in boot () (kgdb) bt #0 0xc030366b in doadump () #1 0xc0303b9a in boot () #2 0xc0303e53 in panic () #3 0xc2758926 in freerq (rq=0xc2ebc8c0) at /usr/src/sys/dev/vinum/vinuminterrupt.c:252 #4 0xc275882a in complete_rqe (bp=0xc2633024) at /usr/src/sys/dev/vinum/vinuminterrupt.c: 230 #5 0xc0346451 in bufdone () #6 0xc0346354 in bufdonebio () #7 0xc03461b2 in biodone () #8 0xc02d159e in g_dev_done () #9 0xc03461b2 in biodone () #10 0xc02d3d42 in g_io_schedule_up () #11 0xc02d3f38 in g_up_procbody () #12 0xc02f109e in fork_exit () Now this trace may be wrong because gdb gave this error when it loaded. Reading symbols from /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum/vinum.ko .debug...done. Loaded symbols for /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum/vinum.ko.d ebug #0 0xc030366b in doadump () .gdbinit:4: Error in sourced command file: Attempt to extract a component of a value that is not a structure. I have all these in separate files (output, gdbinit files etc) in a zip. BTW, I was doing a make buildworld while the machine crashed. And yes, both kernel and vinum.ko have debugging info. ettukaali# file /boot/kernel/kernel /boot/kernel/kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped ettukaali# ls -al /boot/kernel/kernel -r-xr-xr-x 1 root wheel 5455085 Aug 17 23:07 /boot/kernel/kernel ettukaali# file /boot/kernel/vinum.ko /boot/kernel/vinum.ko: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped ettukaali# ls -al /boot/kernel/vinum.ko -r-xr-xr-x 1 root wheel 96588 Aug 18 07:34 /boot/kernel/vinum.ko ettukaali# (Aug 17 23:07 is approx when I made the debug kernel) (Aug 18 07:34 is approx when I did make installkernel - although I would have expected the last-mod-time on vinum.ko to match that of kernel) Either-way the make buildworld wouldn't have affected any of these files since I did it in the afternoon. -- Hari On Mon, Aug 18, 2003 at 09:21:59AM +0930, Greg 'groggy' Lehey wrote: Follow the steps at http://www.vinumvm.org/vinum/how-to-debug.html#panic. I can't help you if you don't tell me what's wrong. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic on heavy read/writes (5.1 + vinum)
Prev trace was not using kernel.debug, I found kernel.debug file that matched the running kernel and here is the trace with it (no errors from gdb now). BTW, I will be moving back to 4.8+vinum tonight ettukaali# gdb -k kernel.debug vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... panic: free locked buf panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02d15f9 stack pointer = 0x10:0xd257d858 frame pointer = 0x10:0xd257d88c 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 = 94137 (genattrtab) trap number = 12 panic: page fault syncing disks, buffers remaining... 2220 2220 panic: free locked buf Uptime: 5h12m33s Dumping 256 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- Reading symbols from /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum/vinum.ko.debug...done. Loaded symbols for /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum/vinum.ko.debug #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:238 238 dumping++; add symbol table from file /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum/vinum.ko.debug at .text_addr = 0x0 (kgdb) f 1 #1 0xc0303b9a in boot (howto=0x104) at /usr/src/sys/kern/kern_shutdown.c:370 370 doadump(); (kgdb) bt #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:238 #1 0xc0303b9a in boot (howto=0x104) at /usr/src/sys/kern/kern_shutdown.c:370 #2 0xc0303e53 in panic () at /usr/src/sys/kern/kern_shutdown.c:543 #3 0xc2758926 in freerq (rq=0xc2ebc8c0) at /usr/src/sys/dev/vinum/vinuminterrupt.c:252 #4 0xc275882a in complete_rqe (bp=0xc2633024) at /usr/src/sys/dev/vinum/vinuminterrupt.c:230 #5 0xc0346451 in bufdone (bp=0xc2633024) at /usr/src/sys/kern/vfs_bio.c:3086 #6 0xc0346354 in bufdonebio (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:3034 #7 0xc03461b2 in biodone (bp=0xc2633024) at /usr/src/sys/kern/vfs_bio.c:2961 #8 0xc02d159e in g_dev_done (bp2=0xc2634090) at /usr/src/sys/geom/geom_dev.c:391 #9 0xc03461b2 in biodone (bp=0xc2634090) at /usr/src/sys/kern/vfs_bio.c:2961 #10 0xc02d3d42 in g_io_schedule_up (tp=0xc0ecbe40) at /usr/src/sys/geom/geom_io.c:365 #11 0xc02d3f38 in g_up_procbody () at /usr/src/sys/geom/geom_kern.c:91 #12 0xc02f109e in fork_exit (callout=0xc02d3f10 g_up_procbody, arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:768 (kgdb) On Tue, Aug 19, 2003 at 08:52:26AM -0500, Hari Bhaskaran wrote: There are two files in /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum One is vinum.ko and the other is vinum.ko.debug (Both are not stripped) I have tried the gdb dump with vinum.paths pointing to either one of them and it still gives the error mentioned below (Attempt to extract..) -- Hari On Mon, Aug 18, 2003 at 10:15:32PM -0500, Hari Bhaskaran wrote: ok, here is it, trace for kernel panic NOTE: There seems to a problem in the .gdbinit files (I may need your help on that). panic: free locked buf panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02d15f9 stack pointer = 0x10:0xd257d858 frame pointer = 0x10:0xd257d88c 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 = 94137 (genattrtab) trap number = 12 panic: page fault syncing disks, buffers remaining... 2220 2220 panic: free locked buf Uptime: 5h12m33s Dumping 256 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- And here is the output on gdb f bt commands (kgdb) f 1 #1 0xc0303b9a in boot () (kgdb) bt #0 0xc030366b in doadump () #1 0xc0303b9a in boot () #2 0xc0303e53 in panic () #3 0xc2758926 in freerq (rq=0xc2ebc8c0) at /usr/src/sys/dev/vinum/vinuminterrupt.c:252 #4 0xc275882a in complete_rqe (bp=0xc2633024) at /usr/src/sys/dev/vinum/vinuminterrupt.c: 230 #5 0xc0346451 in bufdone () #6 0xc0346354 in bufdonebio () #7 0xc03461b2 in biodone () #8 0xc02d159e in g_dev_done () #9 0xc03461b2 in biodone () #10 0xc02d3d42 in
Re: panic on heavy read/writes (5.1 + vinum)
ok, here is it, trace for kernel panic NOTE: There seems to a problem in the .gdbinit files (I may need your help on that). panic: free locked buf panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02d15f9 stack pointer = 0x10:0xd257d858 frame pointer = 0x10:0xd257d88c 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 = 94137 (genattrtab) trap number = 12 panic: page fault syncing disks, buffers remaining... 2220 2220 panic: free locked buf Uptime: 5h12m33s Dumping 256 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- And here is the output on gdb f bt commands (kgdb) f 1 #1 0xc0303b9a in boot () (kgdb) bt #0 0xc030366b in doadump () #1 0xc0303b9a in boot () #2 0xc0303e53 in panic () #3 0xc2758926 in freerq (rq=0xc2ebc8c0) at /usr/src/sys/dev/vinum/vinuminterrupt.c:252 #4 0xc275882a in complete_rqe (bp=0xc2633024) at /usr/src/sys/dev/vinum/vinuminterrupt.c: 230 #5 0xc0346451 in bufdone () #6 0xc0346354 in bufdonebio () #7 0xc03461b2 in biodone () #8 0xc02d159e in g_dev_done () #9 0xc03461b2 in biodone () #10 0xc02d3d42 in g_io_schedule_up () #11 0xc02d3f38 in g_up_procbody () #12 0xc02f109e in fork_exit () Now this trace may be wrong because gdb gave this error when it loaded. Reading symbols from /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum/vinum.ko .debug...done. Loaded symbols for /usr/obj/usr/src/sys/DEBUG/modules/usr/src/sys/modules/vinum/vinum.ko.d ebug #0 0xc030366b in doadump () .gdbinit:4: Error in sourced command file: Attempt to extract a component of a value that is not a structure. I have all these in separate files (output, gdbinit files etc) in a zip. BTW, I was doing a make buildworld while the machine crashed. And yes, both kernel and vinum.ko have debugging info. ettukaali# file /boot/kernel/kernel /boot/kernel/kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped ettukaali# ls -al /boot/kernel/kernel -r-xr-xr-x 1 root wheel 5455085 Aug 17 23:07 /boot/kernel/kernel ettukaali# file /boot/kernel/vinum.ko /boot/kernel/vinum.ko: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped ettukaali# ls -al /boot/kernel/vinum.ko -r-xr-xr-x 1 root wheel 96588 Aug 18 07:34 /boot/kernel/vinum.ko ettukaali# (Aug 17 23:07 is approx when I made the debug kernel) (Aug 18 07:34 is approx when I did make installkernel - although I would have expected the last-mod-time on vinum.ko to match that of kernel) Either-way the make buildworld wouldn't have affected any of these files since I did it in the afternoon. -- Hari On Mon, Aug 18, 2003 at 09:21:59AM +0930, Greg 'groggy' Lehey wrote: Follow the steps at http://www.vinumvm.org/vinum/how-to-debug.html#panic. I can't help you if you don't tell me what's wrong. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
panic on heavy read/writes (5.1 + vinum)
Hi, I recently installed 5.1 RELEASE on a PII (old!) machine. I am using vinum on everything except '/' ( I am not using the new vinum-root setup possible with 5.1 ) (Versions are straight out of the 5.1 RELEASE, no cvsup) I got a panic during a make distclean on cvsup-without-gui (which includes a dozen other packages - meaning heavy read/write) Unfortunately I couldn't get the dump/log anywhere - it cleared the screen too fast before i could write anything down - the panic message was some vinum, that's all I could read. /var/crash is empty - no trace of any other problem in /var/log/messages This had happened once before - When I did a make on cvsup-without-gui and since it takes a while I decided to come back after a while. When I came back the machine was in the login prompt again. I couldn't remember if I had intentionally rebooted it or not - I went back to /var/log/messages and realized there is no trace of a corresponding signal 15 or shutdown. That when I decided to do a make distclean and I got the second panic. NOTE: I wish the 'panic' just stopped the system (and let me see the console) rather than reseting the system automatically. I know I haven't followed the steps at http://www.vinumvm.org/vinum/how-to-debug.html#panic, but I will try to do it as soon as possible. 2 drives: D formosa State: up /dev/ad1s1e A: 0/11022 MB (0%) D regalis State: up /dev/ad0s1e A: 0/36122 MB (0%) 5 volumes: V var State: up Plexes: 2 Size: 1024 MB V usrbase State: up Plexes: 2 Size: 3072 MB V usrhome State: up Plexes: 2 Size: 6144 MB V tmp State: up Plexes: 1 Size:782 MB V fs1 State: up Plexes: 1 Size: 25 GB 8 plexes: P var.p0 C State: up Subdisks: 1 Size: 1024 MB P var.p1 C State: up Subdisks: 1 Size: 1024 MB P usrbase.p0 C State: up Subdisks: 1 Size: 3072 MB P usrbase.p1 C State: up Subdisks: 1 Size: 3072 MB P usrhome.p0 C State: up Subdisks: 1 Size: 6144 MB P usrhome.p1 C State: up Subdisks: 1 Size: 6144 MB P tmp.p0 C State: up Subdisks: 1 Size:782 MB P fs1.p0 C State: up Subdisks: 1 Size: 25 GB 8 subdisks: S var.p0.s0 State: up D: regalis Size: 1024 MB S var.p1.s0 State: up D: formosa Size: 1024 MB S usrbase.p0.s0 State: up D: regalis Size: 3072 MB S usrbase.p1.s0 State: up D: formosa Size: 3072 MB S usrhome.p0.s0 State: up D: regalis Size: 6144 MB S usrhome.p1.s0 State: up D: formosa Size: 6144 MB S tmp.p0.s0 State: up D: formosa Size:782 MB S fs1.p0.s0 State: up D: regalis Size: 25 GB dmesg of my system is given below - Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0689000. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 233864991 Hz CPU: Pentium II/Pentium II Xeon/Celeron (233.86-MHz 686-class CPU) Origin = GenuineIntel Id = 0x634 Stepping = 4 Features=0x80f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX real memory = 268435456 (256 MB) avail memory = 253681664 (241 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdca0 pcib0: Intel 82443LX (440 LX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82443LX (440 LX) host to PCI bridge mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 11 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 7.3 (no driver attached) pci0: display, VGA at device 9.0 (no driver attached) rl0: Accton MPX 5030/5038 10/100BaseTX port 0xe400-0xe4ff mem
Re: panic on heavy read/writes (5.1 + vinum)
On Sunday, 17 August 2003 at 15:01:41 -0500, Hari Bhaskaran wrote: Hi, I recently installed 5.1 RELEASE on a PII (old!) machine. I am using vinum on everything except '/' ( I am not using the new vinum-root setup possible with 5.1 ) (Versions are straight out of the 5.1 RELEASE, no cvsup) ... I know I haven't followed the steps at http://www.vinumvm.org/vinum/how-to-debug.html#panic, but I will try to do it as soon as possible. You've also included information which this page specifically asked you not to send. Any help is appreciated. Follow the steps at http://www.vinumvm.org/vinum/how-to-debug.html#panic. I can't help you if you don't tell me what's wrong. NOTE: I wish the 'panic' just stopped the system (and let me see the console) rather than reseting the system automatically. It does. It sounds like there's something wrong with your system. But that's why I need the information. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
