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 you provide data that better illustrate your
problem?
The problem is that when this happens, the system becomes unusable.
Videos stop playing, switching between windows takes more and more time,
mail client is painfully slow, etc. If I leave the system alone when
this starts happening the clock eventually consumes all CPU, the system
freezes, or it crashes. Since the last 2 require a full fsck to recover
from I tend to power down first. :)
BTW, something interesting happened the other day. I was having this
problem over and over with the same hulu video, so I finally switched to
windows in order to just finish watching it. After about 5 minutes
watching the same show in windows the video started to stall just like
it had in freebsd, but after about 5 seconds of that it "caught up" with
itself, and I was able to watch the last 20 or so minutes without any
problems.
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
