Date: Sun, 24 Mar 2002 22:55:14 -0600 (CST) From: David LaCroix <dlacroix@poit.suddendeceleration.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/36274: 75GXP drive ATA tagging failure makes df bus error? Message-ID: <200203250455.g2P4tEs01009@poit.suddendeceleration.com>
next in thread | raw e-mail | index | archive | help
>Number: 36274
>Category: kern
>Synopsis: 75GXP drive ATA tagging failure makes df bus error?
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Mar 24 21:00:08 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: David LaCroix
>Release: FreeBSD 4.5-RELEASE-p1 i386
>Organization:
>Environment:
System: FreeBSD poit.suddendeceleration.com 4.5-RELEASE-p1 FreeBSD 4.5-RELEASE-p1 #2: Wed Feb 27 00:06:44 CST 2002 dlacroix@poit.suddendeceleration.com:/usr/obj/usr/src/sys/POIT i386
> sysctl -a |grep ata
kern.ipc.max_datalen: 156
hw.ata.ata_dma: 1
hw.ata.wc: 1
hw.ata.tags: 1
hw.ata.atapi_dma: 1
hw.atamodes: pio,---,dma,---,---,---,---,---,
> df
Bus error
> dmesg
Copyright (c) 1992-2002 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 4.5-RELEASE-p1 #2: Wed Feb 27 00:06:44 CST 2002
dlacroix@poit.suddendeceleration.com:/usr/obj/usr/src/sys/POIT
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 756744639 Hz
CPU: AMD Athlon(tm) Processor (756.74-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x642 Stepping = 2
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
AMD Features=0xc0440000<<b18>,AMIE,DSP,3DNow!>
real memory = 536788992 (524208K bytes)
avail memory = 519172096 (507004K bytes)
Preloaded elf kernel "kernel" at 0xc034e000.
Pentium Pro MTRR support enabled
Using $PIR table, 9 entries at 0xc00f1720
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <VIA 8363 (Apollo KT133) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
pci1: <NVidia model 0110 graphics accelerator> at 0.0 irq 11
isab0: <VIA 82C686 PCI-ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686 ATA100 controller> port 0xd800-0xd80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 5 at device 4.2 on pci0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ugen0: OmniVision OV511+ Camera, rev 1.00/1.00, addr 2
ums0: Microsoft Microsoft IntelliMouse\M-. Optical, rev 1.10/1.21, addr 3, iclass 3/1
ums0: 5 buttons and Z dir.
uhci1: <VIA 83C572 USB controller> port 0xd000-0xd01f irq 5 at device 4.3 on pci0
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
pcm0: <VIA VT82C686A> port 0xb000-0xb003,0xb400-0xb403,0xb800-0xb8ff irq 3 at device 4.5 on pci0
bktr0: <BrookTree 878> mem 0xd7000000-0xd7000fff irq 5 at device 9.0 on pci0
iicbb0: <I2C generic bit-banging driver> on bti2c0
iicbus0: <Philips I2C bus> on iicbb0 master-only
smbus0: <System Management Bus> on bti2c0
bktr0: AVer Media TV/FM, Philips FR1236 NTSC FM tuner.
pci0: <unknown card> (vendor=0x109e, dev=0x0878) at 9.1 irq 5
sym0: <875> port 0xa400-0xa4ff mem 0xd4000000-0xd4000fff,0xd4800000-0xd48000ff irq 3 at device 10.0 on pci0
sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware.
rl0: <RealTek 8139 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38000ff irq 11 at device 12.0 on pci0
rl0: Ethernet address: 00:e0:4c:39:0d:1c
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
atapci1: <Promise ATA100 controller> port 0x8400-0x843f,0x8800-0x8803,0x9000-0x9007,0x9400-0x9403,0x9800-0x9807 mem 0xd3000000-0xd301ffff irq 10 at device 17.0 on pci0
ata2: at 0x9800 on atapci1
ata3: at 0x9000 on atapci1
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
orm0: <Option ROMs> at iomem 0xc0000-0xcbfff,0xcc000-0xcffff,0xd0000-0xd07ff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 43979MB <IBM-DTLA-307045> [89355/16/63] at ata0-master tagged UDMA100
acd0: DVD-ROM <SAMSUNG DVD-ROM SD-608> at ata1-master using WDMA2
Waiting 5 seconds for SCSI devices to settle
(noperiph:sym0:0:-1:-1): SCSI BUS reset delivered.
Mounting root from ufs:/dev/ad0s1a
cd0 at sym0 bus 0 target 5 lun 0
cd0: <YAMAHA CRW2100S 1.0H> Removable CD-ROM SCSI-2 device
cd0: 20.000MB/s transfers (20.000MHz, offset 7)
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
ASUS A7V133 M.B. with IBM 45Gig 75GXP type drive on the VIA
chipset based controller, a Symbios Logic 875 based SCSI card with
a Yamaha 16x10x40 CD-RW installed.
>Description:
While ripping a stack of audio CDs, I was running several rips concurrently
(as soon as the disk cdda2wav portion was through I would start a new
ripit.pl process in a separate window. At the time the symptoms stared,
there were approx 5 lame processes running in the background.
While ripping a particularly noisy audio CD, the disk usage dropped to zero,
the rip that was in process failed with a write error, and momentarily
the keyboard/mouse would not respond. The following errors appeared
on the console.
ad0: READ command timeout tag=0 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: no request for this tag=0??
ad0: invalidating queued requests
ad0: timeout waiting for READY
ad0: invalidating queued requests
- resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=0 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=31 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=30 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=29 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=7 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=6 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=5 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=4 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=3 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=2 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=1 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: no request for this tag=1??
ad0: invalidating queued requests
ad0: READ command timeout tag=0 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: timeout waiting for READY
ad0: invalidating queued requests
ata0-master: timeout waiting to give command=00 s=d0 e=04
ad0: flushing queue failed
- resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=31 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=30 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=29 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=7 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=6 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=5 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=4 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=3 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=2 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=1 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=0 serv=0 - resetting
ad0: invalidating queued requests
ad0: trying fallback to PIO mode
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=0 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=31 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=30 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=29 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=7 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=6 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=5 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=4 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=3 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=2 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=1 serv=0 - resetting
ad0: invalidating queued requests
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=31 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=30 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=7 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: WRITE command timeout tag=6 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=5 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: read interrupt arrived earlyad0: read error detected (too) latead0: READ command timeout tag=4 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=3 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: timeout waiting for DRQad0: invalidating queued requests
- resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: timeout waiting for DRQad0: invalidating queued requests
- resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: timeout waiting for DRQad0: invalidating queued requests
- resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: timeout waiting for DRQad0: invalidating queued requests
- resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
ad0: READ command timeout tag=2 serv=0 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
Mar 24 22:32:45 poit /kernel: pid 715 (df), uid 0: exited on signal 10
Mar 24 22:32:52 poit /kernel: pid 720 (df), uid 0: exited on signal 10
Mar 24 22:32:53 poit /kernel: pid 721 (df), uid 0: exited on signal 10
Mar 24 22:33:18 poit /kernel: pid 722 (df), uid 0: exited on signal 10
Mar 24 22:35:27 poit /kernel: pid 739 (df), uid 0: exited on signal 10
Mar 24 22:35:38 poit /kernel: pid 742 (df), uid 1001: exited on signal 10
Mar 24 22:36:07 poit /kernel: pid 753 (df), uid 0: exited on signal 10
After a brief period of unresponsiveness, control seemed to return to normal,
however it seems impossible to get output from the df command. It seems
to be giving a bus error on every invocation.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203250455.g2P4tEs01009>