On Sun, 16 Sep 2001, Andre Pang wrote:
> On Thu, Sep 13, 2001 at 11:30:47PM +1000, Jeffrey Borg wrote:
>
> > anyway the problem tonight was that realplayer couldn't be killed off. I
> > suspect that the sound driver locked and wouldn't release realplayer and
> > thus any tools to kill realplayer wouldn't work at all. in fact cat
> > /proc/<pid of realplayer which was guessed>/cmdline would lock.
>
> try using the ALSA sound drivers. i had a few problems with the
> normal OSS drivers on my laptop (the drivers didn't like
> suspend/resume very much), and i had numerous apps floating
> around which refused to be killed becuase of this. ALSA fixed
> it all up perfectly.
This isn't a laptop, although on my laptop I am using ext3 so crashes
don't hurt as much, I am but worried about my other machine with ext3
because it also has software raid mirroring on it. Although I don't like
patching the kernel too much as so far 2.4 I have needed no patches to
make it work. my 2.2 kernels were patched so much usually.
> > My 2nd and it's happened quite a few times is that the user schedulder
> > dies and the only resolution is just to cold reboot. THe funny thing is
> > that it still works as a router :-) But that's all in the kernel
> > schedulder.
>
> what kinda symptoms?
Exactly as it says machine locks but will still route packets/ act as a
firewall etc.. connecting to a tcp port which is open will accept the
connection and hang. I.E. say the kernel knows to open the port but no
data can be transmitted. But it will still route packets as this dosen't
involve any user processes
> > My experience with 2.2 was that it's far more stable. But I don't think I
> > will go back.
>
> nod, i agree. i hope 2.5 comes out _really_ soon so 2.4 really
> does get a proper chance to stabilise.
I agree too many changes to 2.4 at the moment.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
