1 |
Mark Knecht posted <5bdc1c8b05091914554f0c7360@××××××××××.com>, excerpted |
2 |
below, on Mon, 19 Sep 2005 14:55:59 -0700: |
3 |
|
4 |
> It seems right now that a simple emerge sync is causing xruns on this |
5 |
> system implying to me some underlying problem with either hard drive |
6 |
> activity or networking. since the hard drive is SATA and the networking |
7 |
> option in the kernel marks the NIC driver as 'Reverse engineered - |
8 |
> experimental' I'm not confident of fixing this problem in the immediate |
9 |
> short term anyway. |
10 |
> |
11 |
> My thoughts right now: |
12 |
> |
13 |
> 1) kernel.org + rt patches |
14 |
> 2) ck-sources |
15 |
> 3) gentoo-sources-amd64 + rt patches not cleanly applied |
16 |
> |
17 |
> I may also investigate a different NIC. I have a email friend that |
18 |
> runs a studio in Sydney. I helped him move from FC2 to Gentoo. We had |
19 |
> xruns using some of the NIC stuff for his motherboard. When we found that |
20 |
> was the problem he never had another problem. |
21 |
|
22 |
I'm not familiar with the term "xrun", so this may be entirely off the |
23 |
wall, but have you confirmed the hard drive is running DMA? If your |
24 |
chipset or SATA drivers are wrong, and your hard drive is having to run in |
25 |
legacy interrupt mode instead of DMA mode, it *WILL* destroy latency and |
26 |
generally make the system unusable for any sort of real-time work at all, |
27 |
regardless of the other kernel patches applied. So... in addition to |
28 |
checking the network drivers, investigate the hard drive and chipset I/O |
29 |
drivers as well, and confirm you ARE running DMA mode. |
30 |
|
31 |
-- |
32 |
Duncan - List replies preferred. No HTML msgs. |
33 |
"Every nonfree program has a lord, a master -- |
34 |
and if you use the program, he is your master." Richard Stallman in |
35 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
36 |
|
37 |
|
38 |
-- |
39 |
gentoo-amd64@g.o mailing list |