On 08/19/2010 10:43, Bjoern A. Zeeb wrote:
On Thu, 19 Aug 2010, Doug Barton wrote:
On 08/19/2010 08:24, Andriy Gapon wrote:
I am sorry, but I don't see anything dramatically wrong here. So
swi4: clock uses 5.76% of WCPU, is that such a big deal to be
called runaway intr?
That's the symptom.
on 12/08/2010 23:57 Doug Barton said the following:
My runaway intr problem with flash has been continuing all along, but
since no one has been interested in helping with it I haven't reported
it for a while. However, today, for the first time, it happened when I
had not run flash at all since
On 08/19/2010 08:24, Andriy Gapon wrote:
I am sorry, but I don't see anything dramatically wrong here. So
swi4: clock uses 5.76% of WCPU, is that such a big deal to be
called runaway intr?
That's the symptom.
A lot of CPU time is idle and a lot is used by userland processes
(e.g. Xorg). Can
on 19/08/2010 20:30 Doug Barton said the following:
On 08/19/2010 08:24, Andriy Gapon wrote:
I am sorry, but I don't see anything dramatically wrong here. So
swi4: clock uses 5.76% of WCPU, is that such a big deal to be
called runaway intr?
That's the symptom.
OK, I see.
Perhaps you will
On Thu, 19 Aug 2010, Doug Barton wrote:
On 08/19/2010 08:24, Andriy Gapon wrote:
I am sorry, but I don't see anything dramatically wrong here. So
swi4: clock uses 5.76% of WCPU, is that such a big deal to be
called runaway intr?
That's the symptom.
Have you ever posted a vmstat -i for when
On Mon, 16 Aug 2010, Peter Jeremy wrote:
- Have you tried running a uniprocessor kernel?
Ok I tried this, and got the same result early into the 3rd video. After
I ran the dtrace intr got up to a truly impressive 27% cpu before I shut
it down.
last pid: 4423; load averages: 2.07,
On 16 August 2010 13:09, Doug Barton do...@freebsd.org wrote:
Can you remember the revision number of the last
version of -CURRENT that didn't have these problems?
It was at least a year ago, so no; I can't remember specifically.
Have you tried running software build(s) from ~ 1.5 years ago
On 8/15/10, Doug Barton do...@freebsd.org wrote:
On 08/14/2010 09:54, b. f. wrote:
My runaway intr problem with flash has been continuing all
along, but since no one has been interested in helping with it I
haven't reported it for a while. However, today, for the first
time, it happened when
On 2010-Aug-14 20:30:44 -0700, Doug Barton do...@freebsd.org wrote:
It DOESN'T happen with loads that produce a lot more heat than my
typical desktop workloads (like say, make -j2 buildworld).
Whilst I also doubt it's hardware, it's worth noting that flash
(or other multimedia workload) is likely
On Sun, 15 Aug 2010, b. f. wrote:
What were you doing when you triggered the interrupt problem without
running X?
I'm afraid to say, lest I am once again labeled a bad programmer. :)
Was there a lot of network, audio device, or disk activity
at the time?
Disk, lots and lots of disk. No
On Mon, 16 Aug 2010, Peter Jeremy wrote:
On 2010-Aug-14 20:30:44 -0700, Doug Barton do...@freebsd.org wrote:
It DOESN'T happen with loads that produce a lot more heat than my
typical desktop workloads (like say, make -j2 buildworld).
Whilst I also doubt it's hardware, it's worth noting that
My runaway intr problem with flash has been continuing all along, but
since no one has been interested in helping with it I haven't reported
it for a while. However, today, for the first time, it happened when I
had not run flash at all since I booted.
My system:
Dell D620, C2D, i386, SMP,
On 08/14/2010 09:54, b. f. wrote:
My runaway intr problem with flash has been continuing all
along, but since no one has been interested in helping with it I
haven't reported it for a while. However, today, for the first
time, it happened when I had not run flash at all since I booted.
My
On 08/14/2010 20:30, Doug Barton wrote:
I'm still using powerd, and it seems to be working as expected.
Sorry, I should have added here that I've also tried running WITHOUT
powerd, and the runaway intr problem still happens.
Doug
--
Improve the effectiveness of your Internet
My runaway intr problem with flash has been continuing all along, but
since no one has been interested in helping with it I haven't reported
it for a while. However, today, for the first time, it happened when I
had not run flash at all since I booted.
My system:
Dell D620, C2D, i386, SMP,
15 matches
Mail list logo
