Re: unable to use gmirror on supermicro 5015b-mt
On Tuesday 22 July 2008 16:59:20 ian j hart wrote: These are new boxes. http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm core 2 Q6600 CPU 8Gb 667 RAM Boxes were memtested from Fri-Mon okay. 6.3-RELEASE (amd64) installs fine. Build cycle okay. Running (no load) for a week or so. However, when I try to configure gmirror they hang on boot. After some fiddling it appears issuing #kldload geom_mirror hangs the boxes very hard. Ping response stops (after 3), no CAD response, CDROM draw doesn't open! This may well be a foolish thing to do but another (different) amd64 box doesn't hang. I don't believe this to be amd64 specific, I suspect that there's something strange about this hardware. There are very many BIOS options and I feel like I've tried them all without getting anywhere. I'm on holiday this week and I've borrowed a box to test. Any suggestions would be welcome. I'll (re)try anything but I need help to stay focused. Before you ask, no I cannot try 7.0-RELEASE, but that's a whole other thread (which may bear fruit more quickly). I already dropped the RAM to 2Gb and disabled the memory remap in the BIOS. dmesg after sig [AHCI disabled, SATA legacy mode] Thanks As I suspected, no takers :) Fix. In /boot/loader.conf hw.ata.atapi_dma=0 This allows kldload without hang. I'm sure that this fix will allow me to configure a mirror. I'll post back if I'm wrong. -- ian j hart ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to use gmirror on supermicro 5015b-mt
On Wed, Jul 23, 2008 at 09:23:52PM +0100, ian j hart wrote: ... As I suspected, no takers :) Fix. In /boot/loader.conf hw.ata.atapi_dma=0 This allows kldload without hang. I'm sure that this fix will allow me to configure a mirror. I'll post back if I'm wrong. OK, but *probably* this is an indicator that you need to either replace the cable (think you said you've tried that) or replace the motherboard. If the cable is known-good and the other components are known-good, and it won't run with DMA on supported hardware, something is seriously wrong with this particular board and odds are too high that it will die horribly later. (Not to mention that you'll be hammering your CPU just to get lousy throughput out of it.) As you said in the other post, you've already spent hours of your life you won't get back - do you want to sign up for some more hours further down the road? -- Clifton (suddenly questioning why I'm spending hours on mailing lists today) -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to use gmirror on supermicro 5015b-mt
On Wednesday 23 July 2008 23:06:39 Clifton Royston wrote: On Wed, Jul 23, 2008 at 09:23:52PM +0100, ian j hart wrote: ... As I suspected, no takers :) Fix. In /boot/loader.conf hw.ata.atapi_dma=0 This allows kldload without hang. I'm sure that this fix will allow me to configure a mirror. I'll post back if I'm wrong. OK, but *probably* this is an indicator that you need to either replace the cable (think you said you've tried that) or replace the motherboard. I tried a 40 wire cable. That's a different test than trying a new (80 wire) cable. If the cable is known-good and the other components are known-good, and it won't run with DMA on supported hardware, something is seriously wrong with this particular board and odds are too high that it will die horribly later. What are the odds that I bought five systems with exactly the same fault? To avoid tempting fate I should say I only tried the fix one one box so far. I'm really not that worried tho'. (Not to mention that you'll be hammering your CPU just to get lousy throughput out of it.) Given that the CDROM (DVD if we're being pedantic) will probably get no use at all, ever, I'm not that worried about it's throughput. As you said in the other post, you've already spent hours of your life you won't get back - do you want to sign up for some more hours further down the road? -- Clifton (suddenly questioning why I'm spending hours on mailing lists today) -- ian j hart ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to use gmirror on supermicro 5015b-mt
Clifton Royston wrote: On Wed, Jul 23, 2008 at 09:23:52PM +0100, ian j hart wrote: ... As I suspected, no takers :) Fix. In /boot/loader.conf hw.ata.atapi_dma=0 This allows kldload without hang. I'm sure that this fix will allow me to configure a mirror. I'll post back if I'm wrong. OK, but *probably* this is an indicator that you need to either replace the cable (think you said you've tried that) or replace the motherboard. If the cable is known-good and the other components are known-good, and it won't run with DMA on supported hardware, something is seriously wrong with this particular board and odds are too high that it will die horribly later. (Not to mention that you'll be hammering your CPU just to get lousy throughput out of it.) This was the same issue I experienced with the NVidia board that I mentioned in the 'taskqueue timeout' thread last week. As I mentioned thereafter, I used my workstation board (Intel), and everything worked fine (ZFS). I tried then to set up my Windows workstation on the NVidia board, and thereafter found out that it would ONLY operate in PIO(4), no matter what I did. Needless to say, the board was RMA'd, and I have a new Intel board on its way to handle the ZFS file system. As you said in the other post, you've already spent hours of your life you won't get back - do you want to sign up for some more hours further down the road? IMHO, just replace the board. If you are not able to acquire DMA on the disk subsystem, you've lost already. -- Clifton (suddenly questioning why I'm spending hours on mailing lists today) ...because your systems are running so smoothly, you have to be typing something to justify your office space? ;) Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
unable to use gmirror on supermicro 5015b-mt
These are new boxes. http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm core 2 Q6600 CPU 8Gb 667 RAM Boxes were memtested from Fri-Mon okay. 6.3-RELEASE (amd64) installs fine. Build cycle okay. Running (no load) for a week or so. However, when I try to configure gmirror they hang on boot. After some fiddling it appears issuing #kldload geom_mirror hangs the boxes very hard. Ping response stops (after 3), no CAD response, CDROM draw doesn't open! This may well be a foolish thing to do but another (different) amd64 box doesn't hang. I don't believe this to be amd64 specific, I suspect that there's something strange about this hardware. There are very many BIOS options and I feel like I've tried them all without getting anywhere. I'm on holiday this week and I've borrowed a box to test. Any suggestions would be welcome. I'll (re)try anything but I need help to stay focused. Before you ask, no I cannot try 7.0-RELEASE, but that's a whole other thread (which may bear fruit more quickly). I already dropped the RAM to 2Gb and disabled the memory remap in the BIOS. dmesg after sig [AHCI disabled, SATA legacy mode] Thanks -- ian j hart %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 6.3-RELEASE #0: Wed Jan 16 01:43:02 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz (2394.02-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,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=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 2145845248 (2046 MB) avail memory = 2059509760 (1964 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Jan 16 2008 01:41:13) acpi0: PTLTDXSDT on motherboard 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: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 uhci0: UHCI (generic) USB controller port 0x1820-0x183f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) 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 uhci1: UHCI (generic) USB controller port 0x1840-0x185f irq 17 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: UHCI (generic) USB controller port 0x1860-0x187f irq 18 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] usb2: UHCI (generic) USB controller on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xd8601000-0xd86013ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: EHCI (generic) USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered pcib3: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci5: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci13: ACPI PCI bus on pcib4 em0: Intel(R) PRO/1000 Network Connection Version - 6.7.2 port 0x2000-0x201f mem 0xd800-0xd801 irq 16 at device 0.0 on pci13 em0: Ethernet address: 00:30:48:64:22:fa pcib5: ACPI PCI-PCI bridge irq 17 at device 28.5 on pci0 pci15: ACPI PCI bus on pcib5 em1: Intel(R) PRO/1000 Network Connection Version - 6.7.2 port 0x3000-0x301f mem 0xd820-0xd821 irq 17 at device 0.0 on pci15 em1: Ethernet address: 00:30:48:64:22:fb uhci3: UHCI (generic) USB controller port 0x1880-0x189f irq 23 at device 29.0 on pci0 uhci3:
