Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Thu, Oct 23, 2008 at 4:08 AM, Stephane Lapie [EMAIL PROTECTED] wrote: On Oct 22, 2008, at 4:49 PM, Alexey Suslikov wrote: On Wed, Oct 22, 2008 at 9:15 AM, Stephane Lapie [EMAIL PROTECTED] wrote: On Oct 21, 2008, at 8:01 PM, Alexey Suslikov wrote: Stephane Lapie wrote: Hello, I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. You definitely should try to install recent snapshot on a CF card and boot GENERIC.MP with APM disabled since that box may mis-behave on interrupts without APCI. Issue bsd.mp -c in UKC than disable apm and exit. Since the Intel controller got two modes (Enhanced, which successfully activates, but provokes issues with wd0 being recognized as UDMA5 ; Compatible, which can't allocate properly an IRQ, probably due to an ACPI issue), I tried booting with both modes : Here is the dmesg trace for a bsd.mp kernel (I'll build a full fledged MP based ramdisk once I confirm this works) in Enhanced mode : You need to sendbug about this (including your researches) if you want this to be fixed in tree. FYI, I filed the bug under kernel/5961. On another note, simply detecting proper mode for the disk doesn't fix all of the issues ; it still seems there is a problem with the pciide driver, as I have confirmed the following error : wd0(pciide0:0:0): timeout type: ata c_bcount: 16384 c_skip: 0 pciide0:0:0: bus-master DMA error: status=0x22 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x22 Check if that still true for GENERIC.MP from -current. Alexey
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Oct 21, 2008, at 8:01 PM, Alexey Suslikov wrote: Stephane Lapie wrote: Hello, I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. You definitely should try to install recent snapshot on a CF card and boot GENERIC.MP with APM disabled since that box may mis-behave on interrupts without APCI. Issue bsd.mp -c in UKC than disable apm and exit. Since the Intel controller got two modes (Enhanced, which successfully activates, but provokes issues with wd0 being recognized as UDMA5 ; Compatible, which can't allocate properly an IRQ, probably due to an ACPI issue), I tried booting with both modes : Here is the dmesg trace for a bsd.mp kernel (I'll build a full fledged MP based ramdisk once I confirm this works) in Enhanced mode : OpenBSD 4.4-current (GENERIC.MP) #937: Sat Oct 18 21:14:41 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR real mem = 2138324992 (2039MB) avail mem = 2059100160 (1963MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/15/07, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.4 @ 0xfbc30 (27 entries) bios0: vendor American Megatrends Inc. version 080014 date 03/15/2007 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC MCFG OEMB GSCI acpi0: wakeup devices P0P2(S4) P0P1(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) EUSB(S4) USB4(S4) USB5(S4) USBE(S4) GBE_(S4) P0P4(S4) P0P5 (S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu2: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu3: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 7 (P0P1) acpiprt2 at acpi0: bus 1 (P0P4) acpiprt3 at acpi0: bus 2 (P0P5) acpiprt4 at acpi0: bus 3 (P0P6) acpiprt5 at acpi0: bus 4 (P0P7) acpiprt6 at acpi0: bus 5 (P0P8) acpiprt7 at acpi0: bus 6 (P0P9) acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB bios0: ROM list: 0xc/0xb000! 0xcb000/0x1000 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82Q965 Host rev 0x02 vga1 at pci0 dev 2 function 0 Intel 82Q965 Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 Intel i965Q(0), 1.6.0 20080312 ppb0 at pci0 dev 28 function 0 Intel 82801H PCIE rev 0x02: apic 4 int 16 (irq 10) pci1 at ppb0 bus 1 em0 at pci1 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: apic 4 int 16 (irq 10), address 00:90:fb:12:b4:6d ppb1 at pci0 dev 28 function 1 Intel 82801H PCIE rev 0x02: apic 4 int 17 (irq 11) pci2 at ppb1 bus 2 em1 at pci2 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: apic 4 int 17 (irq 11), address 00:90:fb:12:b4:6e ppb2 at pci0 dev 28 function 2 Intel 82801H PCIE rev 0x02: apic 4 int 18 (irq 5) pci3 at ppb2 bus 3 em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: apic 4 int 18 (irq 5), address 00:90:fb:12:b4:6f ppb3 at pci0 dev 28 function 3 Intel 82801H PCIE rev 0x02: apic 4 int 19 (irq 15) pci4 at ppb3 bus 4 em3 at pci4 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: apic 4 int 19 (irq 15), address 00:90:fb:12:b4:70 ppb4 at pci0 dev 28 function 4 Intel 82801H PCIE rev 0x02: apic 4 int 16 (irq 10) pci5 at ppb4 bus 5 em4 at pci5 dev 0 function 0 Intel PRO/1000MT (82573L) rev
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Wed, Oct 22, 2008 at 9:15 AM, Stephane Lapie [EMAIL PROTECTED] wrote: On Oct 21, 2008, at 8:01 PM, Alexey Suslikov wrote: Stephane Lapie wrote: Hello, I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. You definitely should try to install recent snapshot on a CF card and boot GENERIC.MP with APM disabled since that box may mis-behave on interrupts without APCI. Issue bsd.mp -c in UKC than disable apm and exit. Since the Intel controller got two modes (Enhanced, which successfully activates, but provokes issues with wd0 being recognized as UDMA5 ; Compatible, which can't allocate properly an IRQ, probably due to an ACPI issue), I tried booting with both modes : Here is the dmesg trace for a bsd.mp kernel (I'll build a full fledged MP based ramdisk once I confirm this works) in Enhanced mode : You need to sendbug about this (including your researches) if you want this to be fixed in tree. Alexey
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Oct 22, 2008, at 4:49 PM, Alexey Suslikov wrote: On Wed, Oct 22, 2008 at 9:15 AM, Stephane Lapie [EMAIL PROTECTED] is.co.jp wrote: On Oct 21, 2008, at 8:01 PM, Alexey Suslikov wrote: Stephane Lapie wrote: Hello, I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. You definitely should try to install recent snapshot on a CF card and boot GENERIC.MP with APM disabled since that box may mis-behave on interrupts without APCI. Issue bsd.mp -c in UKC than disable apm and exit. Since the Intel controller got two modes (Enhanced, which successfully activates, but provokes issues with wd0 being recognized as UDMA5 ; Compatible, which can't allocate properly an IRQ, probably due to an ACPI issue), I tried booting with both modes : Here is the dmesg trace for a bsd.mp kernel (I'll build a full fledged MP based ramdisk once I confirm this works) in Enhanced mode : You need to sendbug about this (including your researches) if you want this to be fixed in tree. FYI, I filed the bug under kernel/5961. On another note, simply detecting proper mode for the disk doesn't fix all of the issues ; it still seems there is a problem with the pciide driver, as I have confirmed the following error : wd0(pciide0:0:0): timeout type: ata c_bcount: 16384 c_skip: 0 pciide0:0:0: bus-master DMA error: status=0x22 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x22 wd0a: device timeout reading fsbn 1244032 of 1244032-1244063 (wd0 bn 1244095; cn 308 tn 35 sn 34), retrying wd0(pciide0:0:0): timeout type: ata c_bcount: 16384 c_skip: 0 pciide0:0:0: bus-master DMA error: status=0x22 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x22 wd0: transfer error, downgrading to PIO mode 4 wd0(pciide0:0:0): using PIO mode 4 wd0a: device timeout reading fsbn 1244032 of 1244032-1244063 (wd0 bn 1244095; cn 308 tn 35 sn 34), retrying wd0: soft error (corrected) Here is the preceding dmesg trace (kernel has apm disabled) : OpenBSD 4.3 (RAMDISK_CD.MP) #1: Wed Oct 22 16:05:57 JST 2008 [EMAIL PROTECTED]:/var/work/src-portwell/sys/ arch/i386/compile/RAMDISK_CD.MP cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR real mem = 2138324992 (2039MB) avail mem = 2061094912 (1965MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/15/07, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.4 @ 0xfbc30 (27 entries) bios0: vendor American Megatrends Inc. version 080014 date 03/15/2007 acpi0 at bios0: rev 2, can't enable ACPI bios0: ROM list: 0xc/0xb000! 0xcb000/0x1000 mainbus0: Intel MP Specification (Version 1.4) cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu2: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu3: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPR mainbus0: bus 0 is type PCI mainbus0: bus 1 is type PCI mainbus0: bus 2 is type PCI mainbus0: bus 3 is type PCI mainbus0: bus 4 is type PCI mainbus0: bus 5 is type PCI mainbus0: bus 6 is type PCI mainbus0: bus 7 is type PCI mainbus0: bus 8 is type ISA ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82Q965 Host rev 0x02 agp at pchb0 not configured vga1 at pci0 dev 2 function 0 Intel 82Q965 Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) ppb0 at pci0 dev 28 function 0 Intel 82801H PCIE rev 0x02: apic 4 int 16 (irq 10) pci1 at ppb0 bus 1 em0 at pci1 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: apic 4 int 16 (irq 10), address 00:90:fb:12:b4:6d ppb1 at pci0 dev 28 function 1 Intel 82801H PCIE rev 0x02:
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Oct 21 18:11:07, Stephane Lapie wrote: Hello, I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. This results in error messages while installing OpenBSD 4.3 (via PXE), as seen in the following dmesg trace retrieved from the serial interface : OpenBSD 4.3 (RAMDISK_CD) #645: Wed Mar 12 11:31:03 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686- class) 2.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,VMX,EST,TM2,CX16,xTPRPXEBOOT 2.02 real mem = 2138324992 (2039MB) avail mem = 2061471744 (1965MB) mainbus0 at roote to com0 bios0 at mainbus0: AT/286+ BIOS, date 03/15/07, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.4 @ 0xfbc30 (27 entries) bios0: vendor American Megatrends Inc. version 080014 date 03/15/2007 apm at bios0 function 0x15 not configured acpi0 at bios0: rev 2, can't enable ACPI bios0: ROM list: 0xc/0xb000! 0xcb000/0x1000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82Q965 Host rev 0x02 agp at pchb0 not configured vga1 at pci0 dev 2 function 0 Intel 82Q965 Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) ppb0 at pci0 dev 28 function 0 Intel 82801H PCIE rev 0x02: irq 10 pci1 at ppb0 bus 1 em0 at pci1 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: irq 10, address 00:90:fb:12:b4:6d ppb1 at pci0 dev 28 function 1 Intel 82801H PCIE rev 0x02: irq 11 pci2 at ppb1 bus 2 em1 at pci2 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: irq 11, address 00:90:fb:12:b4:6e ppb2 at pci0 dev 28 function 2 Intel 82801H PCIE rev 0x02: irq 5 pci3 at ppb2 bus 3 em2 at pci3 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: irq 5, address 00:90:fb:12:b4:6f ppb3 at pci0 dev 28 function 3 Intel 82801H PCIE rev 0x02: irq 15 pci4 at ppb3 bus 4 em3 at pci4 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: irq 15, address 00:90:fb:12:b4:70 ppb4 at pci0 dev 28 function 4 Intel 82801H PCIE rev 0x02: irq 10 pci5 at ppb4 bus 5 em4 at pci5 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: irq 10, address 00:90:fb:12:b4:71 ppb5 at pci0 dev 28 function 5 Intel 82801H PCIE rev 0x02: irq 11 pci6 at ppb5 bus 6 em5 at pci6 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: irq 11, address 00:90:fb:12:b4:72 uhci0 at pci0 dev 29 function 0 Intel 82801H USB rev 0x02: irq 14 uhci1 at pci0 dev 29 function 1 Intel 82801H USB rev 0x02: irq 15 ehci0 at pci0 dev 29 function 7 Intel 82801H USB rev 0x02: irq 14 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb6 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xf2 pci7 at ppb6 bus 7 em6 at pci7 dev 12 function 0 Intel PRO/1000MT (82541GI) rev 0x05: irq 10, address 00:90:fb:12:b4:73 em7 at pci7 dev 13 function 0 Intel PRO/1000MT (82541GI) rev 0x05: irq 11, address 00:90:fb:12:b4:74 em8 at pci7 dev 14 function 0 Intel PRO/1000MT (82541GI) rev 0x05: irq 5, address 00:90:fb:12:b4:75 ichpcib0 at pci0 dev 31 function 0 Intel 82801H LPC rev 0x02: PM disabled pciide0 at pci0 dev 31 function 2 Intel 82801H SATA rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using irq 15 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: SanDisk SDCFH2-002G wd0: 4-sector PIO, LBA, 1953MB, 4001760 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 Intel 82801H SMBus rev 0x02 at pci0 dev 31 function 3 not configured pciide1 at pci0 dev 31 function 5 Intel 82801H SATA rev 0x02: DMA, channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide1: using irq 15 for native-PCI interrupt usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo biomask f3c5 netmask ffe5 ttymask ffe7 rd0: fixed, 3800 blocks uhub3 at uhub1 port 2 Mitsumi Electric Hub in Apple Extended USB Keyboard rev 1.10/4.10 addr 2 uhidev0 at uhub3 port 3 configuration 1 interface 0 Mitsumi Electric
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Tue, Oct 21, 2008 at 06:11:07PM +0900, Stephane Lapie wrote: I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. I had the same problem with an early Soekris 4801 which was not wired to support DMA or U-DMA on the CF slot. The solution was to disable both with the 0x0ff0 flag to wd (see the wd man page): *--* frisco# config -o new -e bsd.rd OpenBSD 4.4 (RAMDISK_CD) #857: Tue Aug 12 17:31:49 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD Enter 'help' for information ukc change wd 32 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0x0 change [n] y channel [-1] ? flags [0] ? 0x0ff0 32 wd* changed 32 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0xff0 ukc q Saving modified kernel. frisco# mv new bsd.rd frisco# *--* Do the same with bsd and it should install fine. Once you have it working properly you might be able to fine tune it to use a DMA mode it supports, but this will get you going.
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On 2008-10-21, Emilio Perea [EMAIL PROTECTED] wrote: On Tue, Oct 21, 2008 at 06:11:07PM +0900, Stephane Lapie wrote: I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. I had the same problem with an early Soekris 4801 which was not wired to support DMA or U-DMA on the CF slot. The solution was to disable both with the 0x0ff0 flag to wd (see the wd man page): *--* frisco# config -o new -e bsd.rd OpenBSD 4.4 (RAMDISK_CD) #857: Tue Aug 12 17:31:49 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD Enter 'help' for information ukc change wd 32 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0x0 change [n] y channel [-1] ? flags [0] ? 0x0ff0 32 wd* changed 32 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0xff0 ukc q Saving modified kernel. frisco# mv new bsd.rd frisco# *--* Do the same with bsd and it should install fine. Once you have it working properly you might be able to fine tune it to use a DMA mode it supports, but this will get you going. You missed the part lower down in Stephane's email (read down past the dmesg), showing exactly what's happening in the source code and why changing flags does not have an effect.
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Wed, Oct 22, 2008 at 12:10:40AM +, Stuart Henderson wrote: You missed the part lower down in Stephane's email (read down past the dmesg), showing exactly what's happening in the source code and why changing flags does not have an effect. Not to mention the other two replies... Sorry about that!
