On Wed, 2006-03-15 at 22:15 -0500, Bill Rugolsky Jr. wrote: > > I'm heading home now (it's 22:00, and I've been here 16 hours > already), but I figured that I'd post what I have thus far, and > perhaps you can tell me what the problem is. > I think it would be better to try to identify the exact circumstances that trigger the large PIO delay, than to start over debugging a new and untested driver, especially if the SMM hypothesis has been ruled out. You mentioned before the bug only hits with writes to multiple drives - can you try to identify a pattern here - stress the drives one at a time, try RAID vs. stressing both drives independently, remove one from the bus. See if anything affects the duration of the latencies, etc. Lots of people have these boards and it seems like if the problem was widespread, I would have seen it on the Linux audio lists, as many of those users run Ingo's instrumented kernel and they all know to report latency traces when they get them. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: Gabor Gombas <gombasg@sztaki.hu>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: Ingo Molnar <mingo@elte.hu>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- References:
- Re: AMD64 X2 lost ticks on PM timer
- From: Jeff Garzik <jeff@garzik.org>
- Re: AMD64 X2 lost ticks on PM timer
- From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
- Re: AMD64 X2 lost ticks on PM timer
- From: Andi Kleen <ak@suse.de>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: Ingo Molnar <mingo@elte.hu>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: Ingo Molnar <mingo@elte.hu>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: Jeff Garzik <jeff@garzik.org>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: Ingo Molnar <mingo@elte.hu>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: Jeff Garzik <jeff@garzik.org>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
- Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
- Re: AMD64 X2 lost ticks on PM timer
- Prev by Date: Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- Next by Date: Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- Previous by thread: Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- Next by thread: Re: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
- Index(es):
![]() |