Re: Panic on connecting external harddrive
On Feb 13, 2008, at 10:26 AM, Ben Stuyts wrote: Hi, On 13 Feb 2008, at 18:36, Ben Stuyts wrote: I'm trying, but I can't get a crashdump. I have dumpdev in rc.conf set to my swap partition, and during booting it correctly says it will dump to that device. My swap is 4 GB and I have 4 GB memory, but doing the math it should fit. Here is something really odd: For debugging I had options KDB options DDB options GDB in my kernel conf. To find out why it would not dump, I removed DDB and GDB, and now it has gotten a lot harder to panic the system. If I plug or unplug the USB drive slowly, I get the usual connect/ disconnect messages and no panic. Only when I connect and then around 3 s later unplug, I get a panic. This is while the connect message comes by on the screen. (Ok, maybe I'm asking for it at that point.) How could the inclusion of DDB/GDB affect the USB subsystem? Some odd timing problem? (And still no way to create a crashdump...) Memory corruption: by adding or removing options, you change the kernel itself as well as its behaviour. This can change where in the kernel the corruption happens and what sub-systems are being affected. See if some other options have the same effect... -- Marcel Moolenaar [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on connecting external harddrive
Hi, On 13 Feb 2008, at 18:36, Ben Stuyts wrote: I'm trying, but I can't get a crashdump. I have dumpdev in rc.conf set to my swap partition, and during booting it correctly says it will dump to that device. My swap is 4 GB and I have 4 GB memory, but doing the math it should fit. Here is something really odd: For debugging I had options KDB options DDB options GDB in my kernel conf. To find out why it would not dump, I removed DDB and GDB, and now it has gotten a lot harder to panic the system. If I plug or unplug the USB drive slowly, I get the usual connect/ disconnect messages and no panic. Only when I connect and then around 3 s later unplug, I get a panic. This is while the connect message comes by on the screen. (Ok, maybe I'm asking for it at that point.) How could the inclusion of DDB/GDB affect the USB subsystem? Some odd timing problem? (And still no way to create a crashdump...) With kind regards, Ben ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on connecting external harddrive
Hi, On 13 Feb 2008, at 03:17, Gary Palmer wrote: You might get someone who knows the USB stack to spot a problem if you are able to supply a full backtrace with variables and line numbers for the functions. If you feel the need to file a PR, that level of information will be required. I'm trying, but I can't get a crashdump. I have dumpdev in rc.conf set to my swap partition, and during booting it correctly says it will dump to that device. My swap is 4 GB and I have 4 GB memory, but doing the math it should fit. I tried 'call doadump' from kdb, but that just hangs there indefinitely. No output, no disk activity. I have to hard-reset the machine. While searching the mailing lists I found this sometimes happens, but I found no solution. P.S. I am not a USB guru, just trying to help Thank you! With kind regards, Ben ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on connecting external harddrive
Ben Stuyts wrote: Hi Gary, On 12 Feb 2008, at 23:13, Gary Palmer wrote: On Tue, Feb 12, 2008 at 07:15:21PM +0100, Ben Stuyts wrote: I have a consistent panic when I connect a 2.5" LaCie 250 GB drive to a SuperMicro 6015P-TR. This server is running amd64 with ZFS. Not being able to connect external harddrives is kind of a show stopper for putting this server into production. Has anyone pointed you at http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html No, but I've read about it. I can supply a kernel dump if that helps. Ben, You might get someone who knows the USB stack to spot a problem if you are able to supply a full backtrace with variables and line numbers for the functions. If you feel the need to file a PR, that level of information will be required. Regards, Gary P.S. I am not a USB guru, just trying to help ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on connecting external harddrive
Hi Gary, On 12 Feb 2008, at 23:13, Gary Palmer wrote: On Tue, Feb 12, 2008 at 07:15:21PM +0100, Ben Stuyts wrote: I have a consistent panic when I connect a 2.5" LaCie 250 GB drive to a SuperMicro 6015P-TR. This server is running amd64 with ZFS. Not being able to connect external harddrives is kind of a show stopper for putting this server into production. Has anyone pointed you at http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html No, but I've read about it. I can supply a kernel dump if that helps. With kind regards, Ben ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on connecting external harddrive
On Tue, Feb 12, 2008 at 07:15:21PM +0100, Ben Stuyts wrote: > Hi, > > I posted this to amd64 and current mailing lists, but can't get any > help. I looked through this list's archive but no solution either. > Maybe somebody here can help me? > > I have a consistent panic when I connect a 2.5" LaCie 250 GB drive to > a SuperMicro 6015P-TR. This server is running amd64 with ZFS. Not > being able to connect external harddrives is kind of a show stopper > for putting this server into production. > > Here is the panic message: > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x290 > fault code= supervisor read data, page not present > instruction pointer = 0x8:0x803ff8aa > stack pointer = 0x10:0xd72eed70 > frame pointer = 0x10:0xd72eedb0 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 48 (usb3) > [thread pid 48 tid 100047 ] > Stopped at usb_transfer_complete+0x10a:movq0x290(%rax),%rax > db> tr > Tracing pid 48 tid 100047 td 0xff00034fe350 > usb_transfer_complete() at usb_transfer_complete+0x10a > usbd_start_transfer() at usbd_start_transfer+0x1a1 > bus_dmamap_load() at bus_dmamap_load+0x453 > usbd_transfer() at usbd_transfer+0xae > usbd_sync_transfer() at usbd_sync_transfer+0xe > usbd_do_request_flags_pipe() at usbd_do_request_flags_pipe+0x96 > usbd_do_request_flags() at usbd_do_request_flags+0x25 > usbd_get_string_desc() at usbd_get_string_desc+0x88 > usbd_get_string() at usbd_get_string+0xcd > usbd_devinfo_vp() at usbd_devinfo_vp+0x80 > usbd_devinfo() at usbd_devinfo+0x46 > usbd_new_device() at usbd_new_device+0x68b > uhub_explore() at uhub_explore+0x295 > usb_discover() at usb_discover+0x38 > usb_event_thread() at usb_event_thread+0x9f > fork_exit() at fork_exit+0x12b > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xd72efd30, rbp = 0 --- Has anyone pointed you at http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html ? Regards, Gary ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic on connecting external harddrive
Hi, I posted this to amd64 and current mailing lists, but can't get any help. I looked through this list's archive but no solution either. Maybe somebody here can help me? I have a consistent panic when I connect a 2.5" LaCie 250 GB drive to a SuperMicro 6015P-TR. This server is running amd64 with ZFS. Not being able to connect external harddrives is kind of a show stopper for putting this server into production. Here is the panic message: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x290 fault code = supervisor read data, page not present instruction pointer = 0x8:0x803ff8aa stack pointer = 0x10:0xd72eed70 frame pointer = 0x10:0xd72eedb0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 48 (usb3) [thread pid 48 tid 100047 ] Stopped at usb_transfer_complete+0x10a:movq0x290(%rax),%rax db> tr Tracing pid 48 tid 100047 td 0xff00034fe350 usb_transfer_complete() at usb_transfer_complete+0x10a usbd_start_transfer() at usbd_start_transfer+0x1a1 bus_dmamap_load() at bus_dmamap_load+0x453 usbd_transfer() at usbd_transfer+0xae usbd_sync_transfer() at usbd_sync_transfer+0xe usbd_do_request_flags_pipe() at usbd_do_request_flags_pipe+0x96 usbd_do_request_flags() at usbd_do_request_flags+0x25 usbd_get_string_desc() at usbd_get_string_desc+0x88 usbd_get_string() at usbd_get_string+0xcd usbd_devinfo_vp() at usbd_devinfo_vp+0x80 usbd_devinfo() at usbd_devinfo+0x46 usbd_new_device() at usbd_new_device+0x68b uhub_explore() at uhub_explore+0x295 usb_discover() at usb_discover+0x38 usb_event_thread() at usb_event_thread+0x9f fork_exit() at fork_exit+0x12b fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xd72efd30, rbp = 0 --- Here is the dmesg: Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-PRERELEASE #15: Wed Feb 6 16:07:55 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MARS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5335 @ 2.00GHz (2000.08-MHz K8- class CPU) Origin = "GenuineIntel" Id = 0x6f7 Stepping = 7 Features = 0xbfebfbff < FPU ,VME ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP ,MTRR ,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2 =0x4e33d AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 4 usable memory = 4280487936 (4082 MB) avail memory = 4117889024 (3927 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 p4tcc0: on cpu0 cpu1: on acpi0 p4tcc1: on cpu1 cpu2: on acpi0 p4tcc2: on cpu2 cpu3: on acpi0 p4tcc3: on cpu3 cpu4: on acpi0 p4tcc4: on cpu4 cpu5: on acpi0 p4tcc5: on cpu5 cpu6: on acpi0 p4tcc6: on cpu6 cpu7: on acpi0 p4tcc7: on cpu7 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci4: on pcib4 pcib5: irq 18 at device 2.0 on pci2 pci5: on pcib5 em0: port 0x2000-0x201f mem 0xd800-0xd801 irq 18 at device 0.0 on pci5 em0: Using MSI interrupt em0: Ethernet address: 00:30:48:7b:88:7e em0: [FILTER] em1: port 0x2020-0x203f mem 0xd802-0xd803 irq 19 at device 0.1 on pci5 em1: Using MSI interrupt em1: Ethernet address: 00:30:48:7b:88:7f em1: [FILTER] pcib6: at device 0.3 on pci1 pci6: on pcib6 puc0: port 0x3030-0x3037,0x3028-0x302f,0x3020-0x3027,0x3018-0x301f, 0x3010-0x3017,0x3000-0x300f irq 24 at device 1.0 on pci6 puc0: [FILTER] uart0: on puc0 uart0: [FILTER] uart1: on puc0 uart1: [FILTER] ppc0: on puc0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: cannot reserve interrupt, failed. lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 pcib7: at device 4.0 on pci0 pci7: on pcib7 pcib8: at device 6.0 on pci0 pci8: on pcib8 pci0: at device 8.0 (no driver attached) uhci0: port 0x1800-0x181f irq 17 at device
