[Pkg-alsa-devel] Bug#406677: alsa-utils: Alsaconf as a forkbomb

Steve Langasek vorlon at debian.org
Mon Jan 15 11:02:13 UTC 2007


severity 406677 important
tags 406677 moreinfo unreproducible
thanks

On Fri, Jan 12, 2007 at 10:41:45PM +0100, Robert Gomułka wrote:

> On my system alsaconf acts as a forkbomb. It is therefore unusable.
> Steps to reproduce:
> 1. Login as root.
> 2. Run alsaconf.
> 3. Press enter on welcome screen.
> 4. On lower part of the screen one can see "unloading snd-emu10k-synth"
> or sth. similar.
> 5. After a few seconds mouse starts lagging, then keyboard stops
> reacting. Hard disk drive LED blinks as hell (swapping?).
> 6. If one has good luck, can see multitude processes of modprobe/sh -c
> pairs. I don't know full command line, because had chance to execute ps
> aux (without w) and after two repetitions I didn't want to reproduce it
> further.

Sorry, this is not reproducible at all for me here.  I doubt this is
going to be possible to debug this without at least knowing the full
modprobe commandline that's being respawned, as a starting point.

> Looking at /proc/config.gz reveals that I have modules unloading
> enabled.

What is /proc/config.gz?  There's no such file here.  I do notice that you
seem to have a custom kernel on your system, so it's possible that
contributes to being able to reproduce this error.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/




More information about the Pkg-alsa-devel mailing list