From: Gustavo Guillermo <gustavo@compunauta.com>
To: "Börkur Ingi Jónsson" <bugsy@isl.is>, linux-kernel@vger.kernel.org
Subject: Re: cpu 100% constantly..
Date: Sat, 27 Sep 2003 05:18:38 GMT [thread overview]
Message-ID: <20030927.5183800.688813666@linux.local> (raw)
In-Reply-To: <200309260157.30018.bugsy@isl.is>
I Have the same problem too but with 2.4.23-pre4
System, reach to hang up about 2 or 3 seconds and puts sound server down.
I doubt that is or not kernel issue, because sometimes it never happens.
With my old kernel 2.4.21-pre5 works fine.
This is not related to sound server (arts) because is a time issue on
arts (you can reproduce it putting back your system clock), but kernel
doesn't said anything at respect.
I trying to find out which driver or process is guilty.
>>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
El 26/09/03, 7:57:29, Börkur Ingi Jónsson <bugsy@isl.is> escribió sobre el
tema cpu 100% constantly..:
> I just installed kernel 2.6-beta 5 and I noticed my kde was kinda slow. I
then
> saw that cpu was in 100% usage while doing nothing. I never reported any
bug
> to the linux kernel before. What kind of info should I put in such a
report
> and more importantly how do I get that info :). Should I post the bug
here or
> in some bug database?
> Regards, Börkur Ingi Jónsson
> -
> 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/
prev parent reply other threads:[~2003-09-27 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 1:57 cpu 100% constantly Börkur Ingi Jónsson
2003-09-27 5:18 ` Gustavo Guillermo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030927.5183800.688813666@linux.local \
--to=gustavo@compunauta.com \
--cc=bugsy@isl.is \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.