[lkml]   [2001]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Hardware testing [was Re: VIA Southbridge bug (Was: Crash on boot (2.4.5))]
Rob Landley writes:

> The third thing (which started this thread) was memory bus. The new 3DNow
> optimizations drove a memory bus into failure, and that IS processor
> specific...
> memtest86 is great becuase it ONLY tests memory. CPUburn is similarly
> specific. A memory bus buster would be a good tool to add to the mix. (DMA
> is another common problem, but the more I look into it, the more it seems to
> be dependent on whatever peripheral you're talking to, which is more
> complication than I'm looking to bite off...)

DMA could be done in a sane manner. Let drivers register a function
to excercise DMA. When you want to test, tell all registered drivers
to start wild excessive DMA. Use a timer to stop this, because you
might end up pretty well locked out of your system while the bus is
busy moving test data.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:56    [W:0.085 / U:0.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site