current-users: 1.5 and adw driver.

Subject: 1.5 and adw driver.
To: None <current-users@netbsd.org>
From: Herb Peyerl <hpeyerl@beer.org>
List: current-users
Date: 12/16/2000 10:43:47

Somewhere between 1.4K and 1.5, the adw driver or its related bits suffered
a bad change.

I have a 1.4K production web-server that's been running just wonderfully with
uptimes of 180+ days.

I rebooted it with a 1.5 GENERIC kernel and proceeded to untar base.tgz
and am getting this on the console:

	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	adw0: DMA Error. Reseting bus
	First bad, reclen=6e72, DIRSIZ=92, namlen=80, flags=5000 entryoffsetinblock=0
	adw0: DMA Error. Reseting bus
	/: bad dir ino 163072 at offset 0: mangled entry
	panic: bad dir
	Stopped in sh at        cpu_Debugger+0x4:       leave
	db>  

Obviously, the stack-trace is uninteresting.


Anyone have any ideas?