Subject: Re: 2.0_RC4 and -current instability, data corruption and system hang ups
To: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: port-cobalt
Date: 11/04/2004 19:10:43
On Thu, Nov 04, 2004 at 05:33:25PM +0100, Markus W Kilbinger wrote:
> >>>>> "Manuel" == Manuel Bouyer <bouyer@antioche.lip6.fr> writes:
> 
>     >> - Corrupted files/data streams mostly at 32 byte boundaries
>     >>   (and for 32 bytes length), quite randomly spread, for writing
>     >>   and reading files.
> 
>     Manuel> Could be a cache sync issue. What CPU is there in this box
>     Manuel> ? Also what devices do you use for disk and network I/O ?
> 
> dmesg excerpt:
> 
>   total memory = 256 MB
>   avail memory = 246 MB
>   mainbus0 (root)
>   com0 at mainbus0 addr 0x1c800000 level 3: st16650a, working fifo
>   com0: console
>   cpu0 at mainbus0: QED RM5200 CPU (0x28a0) Rev. 10.0 with built-in FPU Rev. 10.0
>   cpu0: 32KB/32B 2-way set-associative L1 Instruction cache, 48 TLB entries
>   cpu0: 32KB/32B 2-way set-associative write-back L1 Data cache

32B lines, this matchs what you've reported.

>   [...]
> 
> 'tlp0' and 'viaide0' are all onboard devices.

tlp0 should have bus_dma related bugs, as it's known to work on alpha,
sparc64, and others hardware where bus_dma_sync() isn't a NOP.
viaide doesn't use custom DMA callbacks, so it should be safe too.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--