On Wed, Jan 12, 2000 at 09:06:50PM +0100, Manuel Bouyer wrote:
> On Wed, Jan 12, 2000 at 12:41:43PM +0000, Patrick Welche wrote:
> > Could this be an indication of failing hardware (i386)?
> 
> Yes, it could. Could be a lot of other things too ...

Indeed... Now each time I reboot (last 5 times in a row):

wd1: no disk label
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
kernel: privileged instruction fault trap, code=0
Stopped in sh at        _bus_dmamap_load_buffer+0x3a:   movl    0x24(%ebp),%esi

db> t
_bus_dmamap_load_buffer(f0252c60,f04dcb00,f5b5a000,1000,0) at _bus_dmamap_load_buffer+0x3a
_bus_dmamap_load(f0252c60,f04dcb00,f5b5a000,1000,0) at _bus_dmamap_load+0x4c
pciide_dma_init(f04d5c00,0,0,f5b5a000,1000) at pciide_dma_init+0x42
_wdc_ata_bio_start(f04d5c98,f04e3000,f04d5c98,f04e3000,f04d5c98) at _wdc_ata_bio_start+0x2b0
wdc_ata_bio_start(f04d5c98,f04e3000,f04e301c,f04d5c98,f638ebe4) at wdc_ata_bio_start+0x5a
wdcstart(f04d5c98,f04e490c,f04d5cc0,f638ec00,f01fcf08) at wdcstart+0x8f
wdc_exec_xfer(f04d5c98,f04e3000,f04e4800,ddc8,f04e4800) at wdc_exec_xfer+0x8a
wdc_ata_bio(f04d5cc0,f04e490c,f04e4800,f04e4894,f638ec30) at wdc_ata_bio+0x78
__wdstart(f04e4800,f0f188e0) at __wdstart+0x104
wdstart(f04e4800,f04e4894,f0f188e0) at wdstart+0x58
wdstrategy(f0f188e0,f0f188e0,f638ec98,f01e1a37,f638ece4) at wdstrategy+0x101
spec_strategy(f638ece4,0,4c,f0f188e0,f63794f8) at spec_strategy+0x47
ufs_strategy(f638ece4,0,f6378b28,1000,0) at ufs_strategy+0xcf
cluster_read(f6378b28,5331c,0,4c,1000) at cluster_read+0x417
ffs_read(f638edd0,f638eeb4,f6378b28,0,1000) at ffs_read+0x254
uvn_io(f6378b28,f638ee3c,1,2,0) at uvn_io+0x192
uvn_get(f6378b28,4c000,f638eeb4,f638eeb8,0) at uvn_get+0x190
uvm_fault(f63800b4,8095000,0,3,0) at uvm_fault+0xbfd
trap() at trap+0x405
--- trap (number 6) ---
0x8048143:


so I can't actually do anything with it... Something for tomorrow..

Cheers,

Patrick