5 May
2004
5 May
'04
6:35 p.m.
On Wed, May 05, 2004 at 09:56:14PM +0200, mik wrote:
On Wed, 5 May 2004 15:17:13 -0400 someone called
Eric Dantan Rzewnicki wrote:
No, probably not. I'll double check when I get home. But I think I had
only used about 50-60G or so of my 160G audio data drive and around 2-3G
of my 12G / partition on a separate drive.
I suspect such things as futex()'s, preemptive kernel, shared memory
problems, SCHED_FIFO processes getting out of hand, other such realtime
issues, (maybe) mozilla ... not sure really.
As Jack O'Quin pointed out to me recently I really should have been
running that realtime monitoring tool ... forget what it's called now.
Jack, can you send a link to that again? I fear my saved mail will not
be available when I get my box working again ...
-Eric Rz.
Just a note for the archives. This probably has
nothing at all to do
with ecasound. My system is severly foobar. Shortly after I wrote that
it locked up completely resulting in widespread filesystem corruption.
Now when I boot it hangs at INIT.
I can get to a shell with alt-sysrq or passing init=/bin/bash at the
lilo prompt, but I haven't had time yet to fully survey the damage.
Anyway ... just wanted to say that the compile problem is most likely
not ecasound's fault in the least.
you hd isn't full, is it?