amd64/81602: SATA crashes with parallel pcm access

Klaus-J.Wolf fbsdbug at
Sat May 28 14:30:02 PDT 2005

>Number:         81602
>Category:       amd64
>Synopsis:       SATA crashes with parallel pcm access
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 28 21:30:01 GMT 2005
>Originator:     Klaus-J. Wolf
>Release:        FreeBSD 5.4-RELEASE amd64
System: FreeBSD daywalker.logelhorst.xy 5.4-RELEASE FreeBSD 5.4-RELEASE #4: Sat May 28 23:07:33 CEST 2005 root@:/usr/src/sys/amd64/compile/DAYWALKER amd64

Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3000+ (1802.31-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x10ff0  Stepping = 0
  AMD Features=0xe2500800<SYSCALL,NX,MMX+,<b25>,LM,3DNow+,3DNow>
real memory  = 1073414144 (1023 MB)
avail memory = 1026969600 (979 MB)
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 0.3> irqs 0-23 on motherboard
acpi0: <A M I OEMXSDT> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
atapci0: <Promise PDC20378 SATA150 controller> port 0x9800-0x987f,0xa000-0xa00f,
0xa400-0xa43f mem 0xfa700000-0xfa71ffff,0xfa800000-0xfa800fff irq 18 at device 8
.0 on pci0
atapci0: failed: rid 0x20 is memory, requested 4
ata2: channel #0 on atapci0
ata3: channel #1 on atapci0
ata4: channel #2 on atapci0
pcm0: <CMedia CMI8738> port 0xb400-0xb4ff irq 19 at device 14.0 on pci0
atapci1: <VIA 6420 SATA150 controller> port 0xb800-0xb8ff,0xc000-0xc00f,0xc400-0
xc403,0xc800-0xc807,0xd000-0xd003,0xd400-0xd407 irq 20 at device 15.0 on pci0
ata5: channel #0 on atapci1
ata6: channel #1 on atapci1
atapci2: <VIA 8237 UDMA133 controller> port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f
6,0x1f0-0x1f7 at device 15.1 on pci0
ata0: channel #0 on atapci2
ata1: channel #1 on atapci2
ad4: 239372MB <Maxtor 7Y250M0/YAR51HW0> [486344/16/63] at ata2-master SATA150
ad6: 239372MB <Maxtor 7Y250M0/YAR51HW0> [486344/16/63] at ata3-master SATA150

A few accesses to the sound device are sufficient to make the system stall.
This often happens after boot, when someone logs into KDE and the welcome
melody is played.

In a simulated environment, the following messages could be read on the
ad4: TIMEOUT - READ_DMA retrying (2 tries left) LBA=369695071
ad4: FAILURE - ATA_IDENTIFY timed out
ad4: FAILURE - ATA_IDENTIFY timed out
ad4: WARNING - removed from configuration
ata2-master: FAILURE - READ_DMA timed out

Combine vivid disk access (e.g. find /) with some sound output (e.g.
ogg123 /somewhere/*.ogg).



More information about the freebsd-amd64 mailing list