public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Gómez" <david@pleyades.net>
To: linux-kernel@vger.kernel.org
Subject: Re: events kthread gone crazy
Date: Fri, 7 May 2004 11:16:00 +0200	[thread overview]
Message-ID: <20040507091559.GA1166@fargo> (raw)
In-Reply-To: <20040506213450.GA11761@DervishD>

Hi ;),

> > I'm running kernel 2.6.5. I had running aMule and decided to preview
> > a file, using xine. Then, suddenly, xine opened but hanged and the
> > machine started to feel unresponsive and sluggish. I guessed that
> > the xine process was in D state, so i did a 'ps' and found this mess:
> [...]
> > 11569 ?        SW<    0:00  \_ [events/0]
> > 11570 ?        S<     0:00  |   \_ /sbin/modprobe -q -- char_major_116_0
> > 11571 ?        D<     0:00  |       \_ /usr/sbin/alsactl restore
> [Ad infinitum]
> 
>     It seems that ALSA is screwing something. Maybe you need to
> recompile ALSA binaries or something like that :???

I think i know the cause of the problem, i'll test it later. You had
to be careful with 'install' directives in modprobe.conf to not cause
circular dependencies, and i think maybe this is the problem. But this
shouldn't trash the kernel with a lot of processes in D state that 
cannot be killed...

> >    85 tty3     S      0:00 into           
> 
>     What the hell is that crap? X''DDDD

A init/login/getty clone programmed by some crazy bastard XDDD

>     Have you seen where xine is disk sleeping. It should not matter
> to the sound problem, but...

I was wrong, xine and aMule had nothing to do with the problem. Just a
'modprobe snd' triggers the problem.

bye

-- 
David Gómez

"The question of whether computers can think is just like the question of
 whether submarines can swim." -- Edsger W. Dijkstra

  reply	other threads:[~2004-05-07  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 21:19 events kthread gone crazy David Gómez
2004-05-06 21:34 ` DervishD
2004-05-07  9:16   ` David Gómez [this message]
2004-05-07 10:24     ` DervishD

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=20040507091559.GA1166@fargo \
    --to=david@pleyades.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox