On Sat, Mar 04, 2006 at 02:06:45PM +0200, Martin Schlemmer wrote:
> On Fri, 2006-03-03 at 18:43 -0500, Bill Rugolsky Jr. wrote:
> > On Fri, Mar 03, 2006 at 05:09:57PM -0500, Jeff Garzik wrote:
> > > Or sata_nv/libata is to blame.
> >  
> > In case you are coming late to the thread:
> > 
> > The lost ticks are closely correlated with sata_nv disk activity on
> > multiple disks, and the problem is easily reproducable with "find /usr |
> > cpio -o >/dev/null" on an MD RAID1 -- but not on a single disk.
> > 
> > Andi suggested:
> > 
> >    Yes, I bet something forgets to turn on interrupts again and it's
> >    picked up by (and blamed on) the next guy who does an unconditional
> >    sti, which happens to be __do_sofitrq or idle.
> > 
> > That sounds right to me.
> > 
> > I built 2.6.16-rc5-git6 yesterday, and it still suffers from the same
> > issue.
> > 
> 
> Not sure this will help in anyway, but anyhow.

Hi

just to throw my 2c, I have a shuttle sn25p with a amd 2x 4400+, under
normal conditions I don't see any mising tick, but when I hammer the
network and the raid5 lvm I start to see missing ticks and the same
error message mentioned before. I am using debian 2.6.15 amd64


> 
> I have had this system for about 6-8 months (maybe 10) now.  It was
> originally a Asus A8N-SLI Deluxe with a 3200+ Athlon64.  In November I
> changed to a Asus A8N-SLI Premium, and added another 1GB memory (now
> have 2GB memory).  In all that time I have not had any issues with lost
> ticks, but I was hesitant to get a X2 processor due to the issue that
> some people had.
 snip ..

> 
> If anything might be of relevance, or you want me to try something, just
> say it.  Same with extra info that might be needed.
> 
> 
> Regards,
> 
> -- 
> Martin Schlemmer
>