Date: Fri, 20 Jul 2001 20:35:38 -0500 From: mikea <mikea@mikea.ath.cx> To: stable@FreeBSD.ORG Subject: Re: system lookup Message-ID: <20010720203538.A61352@mikea.ath.cx> In-Reply-To: <42245809485.20010720194146@yahoo.com>; from pccb@yahoo.com on Fri, Jul 20, 2001 at 07:41:46PM -0400 References: <42245809485.20010720194146@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 20, 2001 at 07:41:46PM -0400, Peter Chiu wrote: > Under heavy disk read on my maxtor 40GB ata66 HD, freebsd locks up and > the following messages show up on the console. > > ad4: READ command timeout tag=0 serv=0 - resetting > ata2: resetting devices... > > At this point, the HD light is on, and the whole system locked up. I > have to do a hardware reset to reboot the system. This problem happen > several times and my system uptime is around 3 - 10 days because of > this. > > 1. Does anyone know what is wrong? > > 2. How to figure out where is the problem? > Harddisk (Maxtor), motherboard (Abit BP6), freebsd or whatever. > > > Info:- > zeus:opt$ sysctl -a | grep ata > kern.ipc.max_datalen: 136 > hw.ata.ata_dma: 1 > hw.ata.wc: 1 > hw.ata.tags: 0 > hw.ata.atapi_dma: 0 > hw.atamodes: dma,dma,dma,pio,dma,---,---,---, > > > dmesg output:- > > CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x665 Stepping = 5 > Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR> > real memory = 268435456 (262144K bytes) > avail memory = 258478080 (252420K bytes) > Programming 24 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xc02df000. > Pentium Pro MTRR support enabled > atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > atapci1: <HighPoint HPT366 ATA66 controller> port 0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 11 at device 19.0 on pci0 > ata2: at 0xcc00 on atapci1 > atapci2: <HighPoint HPT366 ATA66 controller> port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.1 on pci0 > ata3: at 0xd800 on atapci2 > ad0: 1625MB <ST31722A> [3303/16/63] at ata0-master UDMA33 > ad1: 39082MB <Maxtor 54098U8> [79406/16/63] at ata0-slave UDMA33 > ad2: 1033MB <WDC AC21000H> [2100/16/63] at ata1-master WDMA2 > SMP: AP CPU #1 Launched! > ad4: 39083MB <Maxtor 34098H4> [79408/16/63] at ata2-master UDMA66 > acd0: CDROM <TOSHIBA CD-ROM XM-5702B> at ata1-slave using PIO3 [I've trimmed away all except CPU, controller, and drives.] I gather that the lockup does not resolve after a reasonable time. It appears that something is terribly wrong in the path to the data on ad4. The message makes me think that ad4 itself failed to respond, but I suppose it's also possible that ata2 dropped an interrupt or other signal, and I think that would result in much the same symptom set. Have you tried setting ad4 to UDMA33 or PIO4 or PIO3, just to see if it makes a difference? Have you tried moving that disk to ata3, and leaving ata2 unused? Have you tried changing any other variables to see what effect the change(s) had? -- Mike Andrews mikea@mikea.ath.cx Tired old sysadmin since 1964 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?20010720203538.A61352>