Bug 36274

Summary:	75GXP drive ATA tagging failure makes df bus error?
Product:	Base System	Reporter:	David LaCroix <dlacroix>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.5-RELEASE
Hardware:	Any
OS:	Any

Description David LaCroix 2002-03-25 05:00:08 UTC

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.

Comment 1 Søren Schmidt freebsd_committer

2003-05-05 11:12:40 UTC

State Changed
From-To: open->closed

I think this was fixed around 4.7 time, if not please get back to me.