OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[kano]

As per the README file as it says:
 cgminer -o http://pool:port -u username -p password -I 9 --auto-fan --auto-gpu
where username and password are of course your worker username and password at the pool
and http://pool:port are whatever the pools is
 e.g. http://pool.abcpool.co:8332

Intensity should be "-I 9,9", because otherwise the second would be on dynamic. Or at least as I understand it (correct me if I'm wrong).

And the --auto-fan and --auto-gpu are completely optional. I'd say keep those out and overclock manually (but that's just my opinion).

Nope if you specify -I 9 on it's own it covers all cards. (well it does on my dual 6950

[Fiyasko]

./facepalm
I need help.
alright so i get as far as
it telling me that i cannot connect to the pool....

I havent the Slightest idea how to configure ANYTHING for this miner.

Could someone.. Like.. Hand me a command line that i can add onto cgminer.exe

I want to run Two 6870's deticated.. I just have no idea the syntax or format, I've read the readme and the example.conf, And im just an example.confused user!

As per the README file as it says:
 cgminer -o http://pool:port -u username -p password -I 9 --auto-fan --auto-gpu
where username and password are of course your worker username and password at the pool
and http://pool:port are whatever the pools is
 e.g. http://pool.abcpool.co:8332

If you want to actually use the computer at the same time, then use a much lower number for -I (e.g. -I 5) or leave it out altogether (no -I 9)

Yeah... Thankyou for helping, So far your help has brought me to this:

[2011-12-30 23:48:32] Pool 0 slow/down or URL or credentials invalid
[2011-12-30 23:48:32] Unable to get work from pool 0 http://pit.deepbit.net:8332

[2011-12-30 23:48:32] No servers were found that could be used to get work from.

[2011-12-30 23:48:32] Please check the details from the list below of the server
s you have input
[2011-12-30 23:48:32] Most likely you have input the wrong URL, forgotten to add
 a port, or have not set up workers
[2011-12-30 23:48:32] Pool: 0  URL: http://pit.deepbit.net:8332  User: *****@
****  Password: ********
[2011-12-30 23:48:32] Press any key to exit, or cgminer will try again in 15s.

Any insight as to whats going wrong? Ports are good... Tried Many different Deepbit addrs, Aswell as btcguild's servers, All give same message..

[P4man]

Username  is usually in the form
username.workername

You probably forgot the worker name.

[Queelis]

On the topic of my fluctuating hash rate, downgrading to 11.6+2.4 didn't help - again dropped to 60 Mhash from 80. I'll just stop trying.

[-ck]

I'll just stop trying.

That's the spirit 

[kano]

Username  is usually in the form
username.workername

You probably forgot the worker name.

Also the username and password are of course the worker user name and password.
Not the account username and password
Of course JackRabiit if you have ever mined before you will know that

[Queelis]

That's the spirit 

That made me giggle

Well, my point is, it doesn't have a reason - one restart it's faster, the other - slower, doesn't seem to have any pattern at all, since I've had the same behaviour through different driver and miner versions. Otherwise there were no software or hardware changes.

[ancow]

That's the spirit 

That made me giggle

Well, my point is, it doesn't have a reason - one restart it's faster, the other - slower, doesn't seem to have any pattern at all, since I've had the same behaviour through different driver and miner versions. Otherwise there were no software or hardware changes.

It couldn't be that PP thingy (http://en.wikipedia.org/wiki/ATI_PowerPlay) that changes card clocks and all whenever it feels like it?

[mmortal03]

I'm seeing something broken in 2.1.0 that I wasn't seeing in 2.0.8. When I hit 'Q' to quit the program, it actually doesn't quit and instead keeps running. What it does, however, is start adding odd lines of information at the bottom of the command window, line by line. For context, I'm running cgminer with a command line that looks like this:

cgminer.exe -o http://us.eclipsemc.com:8337/ -u [username] -p [password] -o http://bitcoinpool.com:8334/ -u [username] -p [password] -k phatk -I 9 --submit-stale --auto-fan --auto-gpu --gpu-engine 999 --gpu-memclock 150 -q --donation 1.0

[Queelis]

It couldn't be that PP thingy (http://en.wikipedia.org/wiki/ATI_PowerPlay) that changes card clocks and all whenever it feels like it?

No, at mining load it's constantly at full frequencies (only at idle drops down completely and at something like 10% load it sits in between).

[Proofer]

If you want to actually use the computer at the same time, then use a much lower number for -I (e.g. -I 5) or leave it out altogether (no -I 9)

FWIW based on my experience I can use ssh for a variety of tasks while all three 5970s/six GPUs are I=9.  And as an experiment I just went to the rig's keyboard and monitor -- the latter attached to GPU 0 -- and opened a few GUI applications OK.  It was an abbreviated test, though.

[Proofer]

I'm not sure whether this is a cgminer topic or hardware topic -- maybe some of each.

In the current 24.5 hour session, I've had seven instances of GPUs being declared SICK and then being immediately released from the hospital and functioning normally.  Here's an example:

[2011-12-30 19:33:45] Thread 1 idle for more than 60 seconds, GPU 1 declared SICK!
[2011-12-30 19:33:45] Attempting to restart GPU
[2011-12-30 19:33:45] Thread 1 still exists, killing it off
[2011-12-30 19:33:45] Thread 7 still exists, killing it off
[2011-12-30 19:33:46] Thread 1 restarted
[2011-12-30 19:33:47] Thread 7 restarted

Here are the instances:

[2011-12-30 12:02:51] Thread 4 idle for more than 60 seconds, GPU 4 declared SICK!
[2011-12-30 12:07:41] Thread 0 idle for more than 60 seconds, GPU 0 declared SICK!
[2011-12-30 12:59:33] Thread 0 idle for more than 60 seconds, GPU 0 declared SICK!
[2011-12-30 13:20:44] Thread 2 idle for more than 60 seconds, GPU 2 declared SICK!
[2011-12-30 17:50:17] Thread 0 idle for more than 60 seconds, GPU 0 declared SICK!
[2011-12-30 19:33:45] Thread 1 idle for more than 60 seconds, GPU 1 declared SICK!
[2011-12-31 01:39:42] Thread 1 idle for more than 60 seconds, GPU 1 declared SICK!

I am overclocking.  I don't know whether these instances mean I should back down or whether, given the immediate recoveries, I've found the sweet spot w/r hash rate versus GPU health, or ... something else.

[P4man]

Do the cards really recover? I havent seen it work on my rig; once sick, they might as well be dead. Maybe I dont have as good doctors
Anyway, Id back down on the clocks if I where you. 

[Proofer]

Do the cards really recover? I havent seen it work on my rig; once sick, they might as well be dead. Maybe I dont have as good doctors
Anyway, Id back down on the clocks if I where you. 

Yes, their hash rate immediately returns to normal.  A few days ago one of them did NOT recover and I reduced its clock a little -- to 800 from 810.  That GPU is not among the seven instances I've seen recently.

[DeathAndTaxes]

Do the cards really recover? I havent seen it work on my rig; once sick, they might as well be dead. Maybe I dont have as good doctors
Anyway, Id back down on the clocks if I where you. 

Yes, their hash rate immediately returns to normal.  A few days ago one of them did NOT recover and I reduced its clock a little -- to 800 from 810.  That GPU is not among the seven instances I've seen recently.

If you are getting frequent sicks eventually you will be getting deads.  I would drop the cards back a little.  The difference between 800 and 810 is ~1%.  When a card goes dead if the downtime is greater than 1% compared to the prior uptime period you are coming out behind.

Example:  Running at 1% higher clock you get one GPU hard crash every week.  On average you are unable to reset it for 8 hours.  8/(24*7) = 4% downtime.  You are 3% behind by running 1% higher clock.

Still if you have a couple GPU you might be fine but in a large farm (20+ GPU) running the bleeding edge is foolish. 

[Proofer]

Thanks, P4man and DeathAndTaxes.  They're now all at 800.  This did reduce my power draw by 2.6%, so it's not all bad.

[gnar1ta$]

Is there anything in 2.1.0 that would be causing sick/dead GPU's more frequently? I thought it was just the clocks and intensity, but I've been dropping both and my GPU's still die in a few hours. I went back to 2.0.7 and the higher clocks I've been using for months and no sick or dead GPU's in 24 hrs so far. Here is the end of a 2.1.0 log:

Code:

[2011-12-29 08:48:14] Accepted 00000000.6e536473.6599f992 GPU 1 thread 7 pool 0
[2011-12-29 08:48:14] Thread 0 idle for more than 60 seconds, GPU 0 declared SICK!
[2011-12-29 08:48:14] GPU still showing activity suggesting a hard hang.
[2011-12-29 08:48:14] Will not attempt to auto-restart it.
[2011-12-29 08:48:15] Accepted 00000000.2a013f6d.de1d9fbf GPU 3 thread 3 pool 0
[2011-12-29 08:48:18] Accepted 00000000.a4db64c2.4b582f61 GPU 1 thread 7 pool 0
[2011-12-29 08:48:19] Accepted 00000000.0684b36b.2a963168 GPU 2 thread 2 pool 0
[2011-12-29 08:48:20] Accepted 00000000.068d9bb2.08b9a638 GPU 2 thread 2 pool 0
[2011-12-29 08:48:27] Accepted 00000000.9eb90870.06baaa9f GPU 4 thread 4 pool 0
[2011-12-29 08:48:28] Accepted 00000000.4dc0370a.3cdee4ff GPU 5 thread 5 pool 0
[2011-12-29 08:48:30] Accepted 00000000.fb825502.12283a26 GPU 1 thread 1 pool 0
[2011-12-29 08:48:44] Accepted 00000000.a3e517b4.c377cc54 GPU 2 thread 2 pool 0
[2011-12-29 08:48:47] Accepted 00000000.a74c2f00.e0714890 GPU 1 thread 1 pool 0
[2011-12-29 08:48:47] Accepted 00000000.85eaf5c9.8d0f9b43 GPU 3 thread 9 pool 0
[2011-12-29 08:48:49] Accepted 00000000.45e2d6b6.6d7cd73a GPU 2 thread 8 pool 0
[2011-12-29 08:48:52] Accepted 00000000.773ad5ca.d59b4c13 GPU 3 thread 3 pool 0
[2011-12-29 08:48:52] Accepted 00000000.fc66bc11.db1c8b97 GPU 1 thread 1 pool 0
[2011-12-29 08:48:53] Accepted 00000000.be4fb6cc.81639e39 GPU 1 thread 7 pool 0
[2011-12-29 08:48:55] Accepted 00000000.f29f74dd.09e3596f GPU 2 thread 2 pool 0
[2011-12-29 08:48:55] Accepted 00000000.39ec5009.b448e45b GPU 4 thread 10 pool 0
[2011-12-29 08:48:57] Accepted 00000000.1dad93e6.54448214 GPU 5 thread 5 pool 0
[2011-12-29 08:48:59] Accepted 00000000.4ab61b1a.e4411342 GPU 2 thread 2 pool 0
[2011-12-29 08:49:00] Accepted 00000000.636a7c6c.1e5278e7 GPU 5 thread 5 pool 0
[2011-12-29 08:49:01] Accepted 00000000.f1984dca.e2d8049a GPU 2 thread 2 pool 0
[2011-12-29 08:49:01] Accepted 00000000.32a172a4.97e19e04 GPU 1 thread 1 pool 0
[2011-12-29 08:49:06] Accepted 00000000.884dec2d.b5b02fa5 GPU 4 thread 4 pool 0
[2011-12-29 08:49:07] Accepted 00000000.a8caaa9e.e3eec3a0 GPU 1 thread 7 pool 0
[2011-12-29 08:49:10] Accepted 00000000.ad0c16a2.6e20abb4 GPU 1 thread 1 pool 0
[2011-12-29 08:49:11] Accepted 00000000.ab2a6ce2.5a9a03c1 GPU 4 thread 4 pool 0
[2011-12-29 08:49:12] Accepted 00000000.210b2150.af906ee3 GPU 5 thread 5 pool 0
[2011-12-29 08:49:12] Accepted 00000000.a6bb201c.65febe17 GPU 5 thread 11 pool 0
[2011-12-29 08:49:15] Thread 0 still exists, killing it off
[2011-12-29 08:49:15] Thread 6 still exists, killing it off
[2011-12-29 08:52:15] LONGPOLL detected new block on network, waiting on fresh work
[2011-12-29 09:10:32] LONGPOLL detected new block on network, waiting on fresh work

[-ck]

Is there anything in 2.1.0 that would be causing sick/dead GPU's more frequently?

No.

[Proofer]

Another data point on (what I'll call) the networking problem:

Code:

[2011-12-31 14:24:21] Accepted 00000000.a44e07fe.f3a7d653 GPU 1 thread 7 pool 0
[2011-12-31 14:25:22] Pool 0 http://us.eclipsemc.com:9009 not responding!
[2011-12-31 14:25:22] Switching to http://mint.bitminter.com:8332
[2011-12-31 14:26:22] Pool 1 http://mint.bitminter.com:8332 not responding!
[2011-12-31 14:26:22] Switching to http://us.eclipsemc.com:8337
[2011-12-31 14:26:24] Pool 0 http://us.eclipsemc.com:9009 recovered
[2011-12-31 14:26:24] Switching to http://us.eclipsemc.com:9009
[2011-12-31 14:26:25] Accepted 00000000.44992abd.5e945b36 GPU 0 thread 6 pool 0
[2011-12-31 14:26:29] Accepted 00000000.5bacb287.897ca7ac GPU 0 thread 0 pool 0
[2011-12-31 14:26:37] Accepted 00000000.c28a0041.2e45738c GPU 4 thread 4 pool 0
[2011-12-31 14:26:37] Accepted 00000000.fb811fb0.7d26dc10 GPU 2 thread 8 pool 0
[2011-12-31 14:26:37] Accepted 00000000.70b55434.0309010f GPU 0 thread 6 pool 0
[2011-12-31 14:26:38] Accepted 00000000.97428da9.4cdd94c2 GPU 3 thread 9 pool 0
[2011-12-31 14:26:38] Accepted 00000000.b783c19f.ee7e9245 GPU 3 thread 3 pool 0
[2011-12-31 14:26:41] Accepted 00000000.b7ec07c0.2f7a7963 GPU 4 thread 4 pool 0
[2011-12-31 14:26:43] Accepted 00000000.7b28072f.d7fb3df2 GPU 2 thread 2 pool 0
[2011-12-31 14:26:43] Accepted 00000000.77a991ef.bebf22df GPU 4 thread 4 pool 0
[2011-12-31 14:26:43] Accepted 00000000.34568bb5.2967afc7 GPU 1 thread 7 pool 0
[2011-12-31 14:26:44] Accepted 00000000.013c49fa.f08ca98f GPU 4 thread 10 pool 0
[2011-12-31 14:26:47] Pool 0 not providing work fast enough
[2011-12-31 14:27:26] Pool 1 http://mint.bitminter.com:8332 recovered
[2011-12-31 14:27:28] Accepted 00000000.bff2c936.34604cc5 GPU 2 thread 8 pool 1
[2011-12-31 14:27:47] Pool 0 http://us.eclipsemc.com:9009 not responding!
[2011-12-31 14:27:47] Switching to http://mint.bitminter.com:8332
[2011-12-31 14:28:47] Pool 1 http://mint.bitminter.com:8332 not responding!
[2011-12-31 14:28:47] Switching to http://us.eclipsemc.com:8337
[2011-12-31 14:28:48] Pool 0 http://us.eclipsemc.com:9009 recovered
[2011-12-31 14:28:48] Switching to http://us.eclipsemc.com:9009
[2011-12-31 14:28:51] Accepted 00000000.d2f50f5e.539e7944 GPU 5 thread 11 pool 0
[2011-12-31 14:28:53] Accepted 00000000.7bbc2161.34d248cb GPU 3 thread 9 pool 0
[2011-12-31 14:28:53] Accepted 00000000.36d0b4c0.33aa697f GPU 3 thread 3 pool 0
[2011-12-31 14:28:53] Accepted 00000000.95523d65.b05d2dad GPU 1 thread 1 pool 0
[2011-12-31 14:28:53] Accepted 00000000.12c1ef2b.715404b5 GPU 5 thread 5 pool 0
[2011-12-31 14:28:53] Accepted 00000000.e8713e0c.81a77f2a GPU 4 thread 10 pool 0
[2011-12-31 14:28:54] Accepted 00000000.75723c62.1486cf41 GPU 0 thread 0 pool 0
[2011-12-31 14:28:54] Accepted 00000000.d4db5195.a73b0e7e GPU 3 thread 3 pool 0
[2011-12-31 14:28:56] Accepted 00000000.5c8f445d.56141347 GPU 3 thread 9 pool 0
[2011-12-31 14:28:57] Accepted 00000000.caab04a5.9c9aa9d0 GPU 0 thread 6 pool 0
[2011-12-31 14:28:58] Accepted 00000000.04b0eaff.75ea35ba GPU 5 thread 5 pool 0
[2011-12-31 14:29:01] Accepted 00000000.e77d4d93.e0ee3434 GPU 0 thread 6 pool 0
[2011-12-31 14:29:03] Accepted 00000000.bffa684d.9cf265dd GPU 3 thread 9 pool 0
[2011-12-31 14:29:06] Accepted 00000000.56ab73f8.e920821d GPU 5 thread 11 pool 0
[2011-12-31 14:29:08] Accepted 00000000.90b91f92.e91f93db GPU 0 thread 0 pool 0
[2011-12-31 14:29:11] Pool 0 not providing work fast enough
[2011-12-31 14:29:49] Pool 1 http://mint.bitminter.com:8332 recovered
[2011-12-31 14:30:00] Accepted 00000000.c9686afd.83ab0cc1 GPU 1 thread 7 pool 1
[2011-12-31 14:30:11] Pool 0 http://us.eclipsemc.com:9009 not responding!
[2011-12-31 14:30:11] Switching to http://mint.bitminter.com:8332
[2011-12-31 14:31:11] Pool 1 http://mint.bitminter.com:8332 not responding!
[2011-12-31 14:31:11] Switching to http://us.eclipsemc.com:8337
[2011-12-31 14:31:15] Pool 0 http://us.eclipsemc.com:9009 recovered
[2011-12-31 14:31:15] Switching to http://us.eclipsemc.com:9009
[2011-12-31 14:31:16] Accepted 00000000.5afb7775.170f484d GPU 1 thread 7 pool 0
[2011-12-31 14:31:16] Accepted 00000000.c4587e7b.c761cbf8 GPU 0 thread 0 pool 0
[2011-12-31 14:31:17] Accepted 00000000.a6d797cc.43654f64 GPU 0 thread 0 pool 0
[2011-12-31 14:31:19] Accepted 00000000.a23f09d8.d6deb907 GPU 0 thread 6 pool 0
[2011-12-31 14:31:20] Accepted 00000000.b096e542.7eebbf2f GPU 1 thread 1 pool 0
[2011-12-31 14:31:24] Accepted 00000000.852bf25c.e4193971 GPU 1 thread 7 pool 0
[2011-12-31 14:31:24] Accepted 00000000.77aa4bd9.a9bade90 GPU 3 thread 9 pool 0
[2011-12-31 14:31:34] Accepted 00000000.8de2075d.306e1532 GPU 5 thread 11 pool 0
[2011-12-31 14:31:35] Accepted 00000000.b0011b74.263f24ce GPU 1 thread 1 pool 0
[2011-12-31 14:31:38] Pool 0 not providing work fast enough
[2011-12-31 14:32:13] Pool 1 http://mint.bitminter.com:8332 recovered
[2011-12-31 14:32:38] Pool 0 http://us.eclipsemc.com:9009 not responding!
[2011-12-31 14:32:38] Switching to http://mint.bitminter.com:8332
[2011-12-31 14:33:38] Pool 1 http://mint.bitminter.com:8332 not responding!
[2011-12-31 14:33:38] Switching to http://us.eclipsemc.com:8337
[2011-12-31 14:33:41] Pool 0 http://us.eclipsemc.com:9009 recovered
[2011-12-31 14:33:41] Switching to http://us.eclipsemc.com:9009
[2011-12-31 14:33:42] Accepted 00000000.ac9af786.2c8cad4c GPU 1 thread 1 pool 0
[2011-12-31 14:33:45] Accepted 00000000.731d5d0a.bc077ec4 GPU 4 thread 10 pool 0
[2011-12-31 14:33:46] Accepted 00000000.ba187561.35405119 GPU 4 thread 4 pool 0
[2011-12-31 14:33:47] Accepted 00000000.dcbc6894.136b499b GPU 3 thread 9 pool 0
[2011-12-31 14:33:49] Accepted 00000000.33cf321c.caf4b88b GPU 2 thread 8 pool 0
[2011-12-31 14:33:50] Accepted 00000000.a66c8423.7286022e GPU 4 thread 10 pool 0
[2011-12-31 14:33:51] Accepted 00000000.62f19e3c.0b82d805 GPU 1 thread 7 pool 0
[2011-12-31 14:33:57] Accepted 00000000.0badc91b.227b9b64 GPU 0 thread 0 pool 0
[2011-12-31 14:33:58] Accepted 00000000.592bce37.6961f2e8 GPU 0 thread 6 pool 0
[2011-12-31 14:33:59] Accepted 00000000.56f38f12.2a5e1bba GPU 3 thread 3 pool 0
[2011-12-31 14:34:00] Accepted 00000000.0ef2bbf7.e53fda1d GPU 0 thread 0 pool 0
[2011-12-31 14:34:00] Accepted 00000000.f8839832.a2cd64a2 GPU 4 thread 4 pool 0
[2011-12-31 14:34:01] Accepted 00000000.453eab0f.f9cec6fa GPU 5 thread 11 pool 0
[2011-12-31 14:34:03] Accepted 00000000.cce0b099.f329f24a GPU 4 thread 10 pool 0
[2011-12-31 14:34:04] Accepted 00000000.9e458df1.11525433 GPU 5 thread 11 pool 0
[2011-12-31 14:34:04] Pool 0 not providing work fast enough
[2011-12-31 14:34:05] Accepted 00000000.400abdfa.7d895b75 GPU 2 thread 2 pool 0
[2011-12-31 14:34:39] Pool 1 http://mint.bitminter.com:8332 recovered
[2011-12-31 14:34:41] Accepted 00000000.2f3304cb.f9b59632 GPU 0 thread 6 pool 1
[2011-12-31 14:35:04] Pool 0 http://us.eclipsemc.com:9009 not responding!
[2011-12-31 14:35:04] Switching to http://mint.bitminter.com:8332
[2011-12-31 14:36:04] Pool 1 http://mint.bitminter.com:8332 not responding!
[2011-12-31 14:36:04] Switching to http://us.eclipsemc.com:8337
[2011-12-31 14:36:08] Pool 0 http://us.eclipsemc.com:9009 recovered
[2011-12-31 14:36:08] Switching to http://us.eclipsemc.com:9009
[2011-12-31 14:36:11] Accepted 00000000.f0800ced.839900de GPU 2 thread 2 pool 0
[2011-12-31 14:36:15] Accepted 00000000.f0c0a439.a4e03185 GPU 0 thread 6 pool 0
[2011-12-31 14:36:15] Accepted 00000000.3e5b7f6f.d7cc2901 GPU 5 thread 11 pool 0
[2011-12-31 14:36:21] Accepted 00000000.2bb7cf61.43b70039 GPU 5 thread 11 pool 0
[2011-12-31 14:36:25] Accepted 00000000.b30f21bb.fcc5035c GPU 2 thread 2 pool 0
[2011-12-31 14:36:30] Pool 0 not providing work fast enough
[2011-12-31 14:37:06] Pool 1 http://mint.bitminter.com:8332 recovered
[2011-12-31 14:37:31] Pool 0 http://us.eclipsemc.com:9009 not responding!
[2011-12-31 14:37:31] Switching to http://mint.bitminter.com:8332
[2011-12-31 14:38:31] Pool 1 http://mint.bitminter.com:8332 not responding!
[2011-12-31 14:38:31] Switching to http://us.eclipsemc.com:8337
[2011-12-31 14:38:34] Pool 0 http://us.eclipsemc.com:9009 recovered
[2011-12-31 14:38:34] Switching to http://us.eclipsemc.com:9009
[2011-12-31 14:38:35] Accepted 00000000.69ab29f9.ed74fbc6 GPU 0 thread 0 pool 0
[2011-12-31 14:38:40] Accepted 00000000.491e9c55.036c19e3 GPU 1 thread 7 pool 0
[2011-12-31 14:38:43] Accepted 00000000.d14ac4ab.eba539d1 GPU 2 thread 8 pool 0
[2011-12-31 14:38:48] Accepted 00000000.64b82745.65baa79b GPU 3 thread 9 pool 0
[2011-12-31 14:38:49] Accepted 00000000.6a63db41.f82952d1 GPU 3 thread 9 pool 0
[2011-12-31 14:38:51] Accepted 00000000.b54fbebb.664fabca GPU 4 thread 4 pool 0
[2011-12-31 14:38:51] Accepted 00000000.bbab2dc0.5eae9294 GPU 4 thread 10 pool 0
[2011-12-31 14:38:53] Accepted 00000000.dd82a704.3436152e GPU 1 thread 1 pool 0
[2011-12-31 14:38:53] Accepted 00000000.e59ed0b7.b80db98e GPU 4 thread 4 pool 0
[2011-12-31 14:38:55] Accepted 00000000.84c0b220.32255517 GPU 2 thread 8 pool 0
[2011-12-31 14:38:57] Pool 0 not providing work fast enough
[2011-12-31 14:39:11] 
Summary of runtime statistics:
[..normal quit output...]

After quitting and immediately restarting cgminer, no problem for the next 20 minutes, after which this post was made.  This is not definitive; could be coincidence, but with more like instances it will become more indicative.

[P4man]

Another data point on (what I'll call) the networking problem:

After quitting and immediately restarting cgminer, no problem for the next 20 minutes, after which this post was made.  This is not definitive; could be coincidence, but with more like instances it will become more indicative.

Seems to be the exact same thing I had. I wonder if there could possibly be a correlation with the fact we both use bitminter pool? Is that your n1 pool?
edit: it isnt. So its not bitminter doing the long polling for you. It is for me.