Machine must have been under heavy CPU load at the time, but I don't
think that it would have been doing a particularly large amount of
networking or I/O.. can't really say anything more useful about it
Mar 7 14:07:48 wolfgang kernel: eth0: DMAing conflict in ne_block_output.[DMAstat:1][irqlock:1][intr:0]
Mar 7 14:07:49 wolfgang last message repeated 4 times
Mar 7 14:07:49 wolfgang kernel: eth0: DMAing conflict in ne_get_8390_hdr [DMAstat:1][irqlock:0][intr:1].
Mar 7 14:07:49 wolfgang kernel: eth0: DMAing conflict in ne_block_output.[DMAstat:1][irqlock:1][intr:0]
Mar 7 14:07:51 wolfgang kernel: eth0: DMAing conflict in ne_block_output.[DMAstat:1][irqlock:1][intr:0]
Mar 7 14:07:52 wolfgang kernel: eth0: DMAing conflict in ne_get_8390_hdr [DMAstat:1][irqlock:0][intr:1].
Mar 7 14:07:54 wolfgang kernel: eth0: DMAing conflict in ne_block_output.[DMAstat:1][irqlock:1][intr:0]
Mar 7 14:07:55 wolfgang kernel: eth0: DMAing conflict in ne_get_8390_hdr [DMAstat:1][irqlock:0][intr:1].
Mar 7 14:07:59 wolfgang last message repeated 29 times
Mar 7 14:08:01 wolfgang kernel: eth0: DMAing conflict in ne_block_output.[DMAstat:1][irqlock:1][intr:0]
Mar 7 14:08:03 wolfgang kernel: eth0: DMAing conflict in ne_get_8390_hdr [DMAstat:1][irqlock:0][intr:1].
Mar 7 14:08:13 wolfgang last message repeated 29 times
Mar 7 14:08:13 wolfgang kernel: eth0: DMAing conflict in ne_block_output.[DMAstat:1][irqlock:1][intr:0]
Mar 7 14:08:14 wolfgang kernel: eth0: DMAing conflict in ne_get_8390_hdr [DMAstat:1][irqlock:0][intr:1].
Mar 7 14:08:34 wolfgang last message repeated 42 times
Mar 7 14:08:35 wolfgang kernel: eth0: DMAing conflict in ne_block_output.[DMAstat:1][irqlock:1][intr:0]
Mar 7 14:13:39 wolfgang syslogd: restart
<http://www.tardis.ed.ac.uk/~mikedlr/biography.html>
Scottish Climbing Archive: <http://www.tardis.ed.ac.uk/~mikedlr/climbing/>
Linux/Unix clone@ftp://src.doc.ic.ac.uk/packages/linux/sunsite.unc-mirror/docs/