Date: Mon, 27 Mar 2000 11:38:32 +1000 (EST) From: Andrew <acs@fl.net.au> To: freebsd-stable@freebsd.org Subject: DMA on a UDMA 33 drive Message-ID: <Pine.BSF.4.05.10003271126070.53046-100000@jander.fl.net.au>
next in thread | raw e-mail | index | archive | help
Hi, What is the current status of DMA support? I've always had trouble with it and just then I enabled it, caused a lot of disk activity and the machine paniced. On reboot It took me several goes to get fsck to get through all the errors with out complaining it couldn't find an inode. My lost+found directy filled up and fsck had to extend it. Half the source tree ended up in lost+found. I'm not sure if any files were lost as I didnt bother putting them back, just rmed them and cvsupped again. This was with 3.4-STABLE asof yesterday. Extracts from dmesg: CPU: Cyrix 6x86MX (250.57-MHz 686-class CPU) Origin = "CyrixInstead" Id = 0x600 Stepping = 0 DIR=0x0853 Features=0x80a135<FPU,DE,TSC,MSR,CX8,PGE,CMOV,MMX> real memory = 67108864 (65536K bytes) config> en wdc1 config> po wdc1 0x170 config> ir wdc1 15 config> f wdc1 0xa0ff config> en wdc0 config> po wdc0 0x1f0 config> ir wdc0 14 config> f wdc0 0x80ff config> q Probing for devices on PCI bus 0: chip0: <VIA 82C597 (Apollo VP3) system controller> rev 0x04 on pci0.0.0 chip1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI bridge> rev 0x00 on pci0.1.0 chip2: <VIA 82C586 PCI-ISA bridge> rev 0x47 on pci0.7.0 ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1 chip3: <VIA 82C586B ACPI interface> rev 0x10 on pci0.7.3 <I have turned off DMA here> wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa wdc0: unit 0 (wd0): <Maxtor 90845D4>, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x80ff on isa wdc1: unit 0 (wd2): <FUJITSU MPC3043AT>, 32-bit, multi-block-16 wd2: 4125MB (8448300 sectors), 8940 cyls, 15 heads, 63 S/T, 512 B/S It was the fujitsu that I ahd DMA turend on, the Maxtor wasn't mounted. Just before the panic I got DMA failure, DMA status 5<active>. Anyway what I wanted to know is is DMA known to be broken or am I just cursed? Does it depend on the motherboard or the drive? Does anyone want me to collect debugging output for them? Would I have more luck with 4.0? Thanks, Andrew (who has had almost every hard drive he owns fail in the past week...:-( ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10003271126070.53046-100000>