search for: wdma2

hi, latest changes in dev/ata broke this, on older -stable ... ata0-master: pio=PIO4 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 wire ad0: success setting PIO4 on National chip ad0: 977MB <SanDisk SDCFB-1024 Rev 0.00> at ata0-master PIO4 on latest -stable: ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire and no disk. cheers, danny

Hi there colleagues, atapci3: <nVidia nForce MCP55 SATA300 controller> port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f mem 0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0 atacontrol detach ata7 - insert ATA disk (ad14) atacontrol attach ata7 pinics with Fatal trap 12: page fault while in kernel mode (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc0533227

...or and gjournal running on a 7.0-RELEASE #p2 amd64 (built from latest CVS source), the box hung a couple of times when on high disk load. Finally, while building some port it won't boot for no reason obvious to me. This is what I get with kernel.geom.mirror.debug=2: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB <SAMSUNG HD501LJ CR100-13> at ata2-master SATA300 ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ad4: nVidia check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed GEOM_MIRROR[2]: Tasting ad...

...BSD 4.8 I use "hw.ata.atapi_dma=1" at boot. This then tells me it is using UDMA33. Unfortunately, I then often get this: acd0: READ_BIG - HARDWARE ERROR asc=0x08 ascq=0x03 error=0x00 I think this means a DMA error. (PS why not say what it is?) If I use atacontrol to downgrade to WDMA2, it works flawlessly (though somewhat slower than it does in UDMA33 mode). So, was 4.5 setting my hardware to WDMA2 when I thought it was doing UDMA33? Has 4.8 introduced bugs that weren't in 4.5? Is there another setting I've missed? Cheers, Stephen.

I have a couple of DVD drives (one drive, one burner) that used to play DVDs quite fine from 5.3 to somewhere in the 6.x branch. Nowadays I have to send them to PIO4 to play DVDs, because they'll just throw DMA not aligned errors around in UDMA33 or WDMA2 mode. Should someone be interested in this I'm willing to supply all necessary information, such as the exact drives, firmware versions, kernel traces... whatever comes to your mind. I'm also willing to test patches.

...C1 dmesg gives the following error lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 ed1: <Realtek Plug & Play Ethernet Card> at port 0x220-0x23f irq 5 on isa0 ed1: address 52:54:40:28:83:9a, type NE2000 (16 bit) ad0: 4112MB <WDC AC24300L> [8912/15/63] at ata0-master WDMA2 Mounting root from ufs:/dev/ad0s1a module_register: module miibus/ukphy already exists! linker_file_sysinit "miibus.ko" failed to register! 17 module_register: module pci/ed already exists! linker_file_sysinit "if_ed.ko" failed to register! 17 /root/kernel/HEAVEN have the follo...

...2008 19:59:27) cpu0 on motherboard pcib0: <Host to PCI bridge> pcibus 0 on motherboard pir0: <PCI Interrupt Routing Table: 6 Entries> on motherboard pci0: <PCI bus> on pcib0 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 1.1 on pci0 ata0: <ATA channel 0> on atapci0 ata0: [ITHREAD] ata1: <ATA channel 1> on atapci0 ata1: [ITHREAD] vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf2000000-0xf2000fff at devi...

...;Host to PCI bridge> pcibus 0 on motherboard > pir0: <PCI Interrupt Routing Table: 6 Entries> on motherboard > pci0: <PCI bus> on pcib0 > isab0: <PCI-ISA bridge> at device 1.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <Intel PIIX3 WDMA2 controller> port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 1.1 on pci0 > ata0: <ATA channel 0> on atapci0 > ata0: [ITHREAD] > ata1: <ATA channel 1> on atapci0 > ata1: [ITHREAD] > vgapci0: <VGA-compatible display> mem...

...5 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1f48-0x1f4b on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc300-0xc30f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ata1: <ATA channel> at channel 1 on atapci0 pci0: <bridge> at device 1.3 (no driver attached) vgapci0: <VGA-compatible display> mem 0xf0000...

...ug npx0: [FAST] npx0: <math processor> on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: <Host to PCI bridge> pcibus 0 on motherboard pci0: <PCI bus> on pcib0 isab0: <PCI-ISA bridge> at device 7.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 7.1 on pci0 ata0: <ATA channel 0> on atapci0 ata1: <ATA channel 1> on atapci0 ahc0: <Adaptec 2940 SCSI adapter> port 0x6000-0x60ff mem 0xe1000000-0xe1000fff irq 12 at device 19.0 on pci0 ahc0: [GIANT-L...

...at 3.579545MHz> port 0xb008-0xb00b on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pci_link4: Unable to route IRQs: AE_NOT_FOUND isab0: <PCI-ISA bridge> at device 1.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX3 WDMA2 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 1.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ata1: <ATA channel> at channel 1 on atapci0 uhci0: <Intel 82371SB (PIIX3) USB controller> port 0xc020-0xc03f irq 11 at device 1.2 on pci0 usbus0:...

I am having problems with silent data corruption on (some) drives connected to an MCP55 SATA controller. I have two servers, both running RELENG_7_0/amd64. One has the 570 Ultra chipset, the other has 570 SLI. Both chipsets have the MCP55 SATA controller. The server with 570 Ultra chipset has a bunch of older 250GB SATA-150 drives hooked up to the MCP55 controller and it is working just fine.

Hello, I've got a (P)ATA disk in a special frame. The disk itself supports UDMA-100 (and has an 80-ribbon cable), but the frame isn't compatible with that. By default, FreeBSD negotiates UDMA-100, and the console starts to fill with ICRC errors. In the past, I used a patch to ata-all.c that enabled the following entry in loader.conf to force the disk to UDMA-33, so it worked fine:

...re initialization) stops. Referring to this portion of the dmesg -v output, of a successful boot, where i have marked ">>>HERE<<<" is where the boot freezes on an unsuccessful boot. This is a constnat problem, on 6.2 as well as 6.3 unchanged. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on 63XXESB2 chip acd0: setting UDMA33 on 63XXESB2 chip acd0: <TSSTcorpCD-RW/DVD-ROM TSL462D/DE01> CDRW drive at ata0 as master acd0: read 4134KB/s (4134KB/s) write 4134KB/s (4134KB/s), 1536KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDR...

...50026b7223027059 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 234441648 sectors LBA48 supported 234441648 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM non-rotating Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queui...

...lt;Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% ad0: 9671MB <IBM-DTTA-351010> [19650/16/63] at ata0-master UDMA33 acd0: CD-RW <PLEXTOR CD-R PX-W1210A> at ata1-master WDMA2 Mounting root from ufs:/dev/ad0s1a cd0 at ata1 bus 0 target 0 lun 0 cd0: <PLEXTOR CD-R PX-W1210A 1.08> Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [87508 x 2048 byte records]

...5000c50011db1e03 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 976773168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM 7200 Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ)...

Thomas, Have spoken to Soren, from my bootlog he believes that the problem is in atapicam causing the system to lock up. He is happy to answer some questions but doesnt have time to delve into atapicam himself. Did you author atapicam, I have seen your name on the sourcecode, can you help me further? Whats next? Thanks Adam. -------------- next part -------------- An embedded message was

...obe_children: probing PnP devices Device configuration finished. procfs registered lapic: Divisor 2, Frequency 100457581 hz Timecounter "TSC" frequency 1607326403 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached rr232x: no controller detected. ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 152627MB <WDC WD1600JD-00HBB0 08.02D08> at ata2-master SATA150 ad4: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue ad4: nVidia check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD...