Mike Cherba wrote:
> I noticed this when I was booting a system attached to a USB serial
> device, but eventually localized the issue to xterm itself. Basically
> when you put a lot of text through an xterm the cpu usage on gutsy goes
> way up. like 100%. I've tried the same thing with the gene
It is quite alright. I remembered to bring home a new drive for
my system finally. It's been giving me fits for a couple months
now. The computer didn't actually hard lock for another few
minutes after killing the process.
That be all,
Mr O.
P.S. That's not all! There is still a lot of soda and p
Neil,
I still think that profiling xterm will tell me a lot. I can run
oprofile on Xorg too once I get that far. I'd like to see what function
in xterm is making the call into Xorg. and where Xorg is spending its
time when this occurs.
-Mike
On Mon, 2007-12-10
Sorry Mike. I thought I mentioned that I found this while running the
DU command on another system. It is definately some oddness. I've just
switched over to gnome-terminals for the moment while I try and sort
this out.
-Mike
On Mon, 2007-12-10 at 18:33 -0800, Mr O wrote
Mike Cherba wrote,
>I noticed this when I was booting a system attached to a USB serial
>device, but eventually localized the issue to xterm itself. Basically
>when you put a lot of text through an xterm the cpu usage on gutsy goes
>way up. like 100%. I've tried the same thing with the generic t
Uh oh, damn it. Heavy thrashing does that every time. Thanks
Mike. CPU never got near loaded but my hard drive locked again.
Hopefully since my message sends while everything is still in
RAM. Guess I need to break down and get that new drive I've been
putting off.
That be all,
Mr O.
--- Mike Cher
On Dec 10, 2007 12:14 PM, Mike Cherba <[EMAIL PROTECTED]>
wrote:
> I'm curious if anyone else has run across this issue before.
>
> I noticed this when I was booting a system attached to a USB serial
> device, but eventually localized the issue to xterm itself. Basically
> when you put a lot of t
I'm curious if anyone else has run across this issue before.
I noticed this when I was booting a system attached to a USB serial
device, but eventually localized the issue to xterm itself. Basically
when you put a lot of text through an xterm the cpu usage on gutsy goes
way up. like 100%. I've
