When creating this driver, I left this debugging output in the module for a while so I'd find odd problems like this. There are several versions of each of these chips (the driver supports two different chips in general). Due to this hardware being rare nowadays, it hasn't received a great amount of testing. However, it works fine on the hardware it was tested on.
Anyway...the debugging output has been turned off on the latest versions of this code. However, kernel 2.6.17 is over a year old. The debugging output has been turned off as of alsa-driver 1.0.14 (www.alsa- project.org) and won't be available in kernel until 2.6.23. The output should indeed be annoying, but the output alone shouldn't really cause the machine to hang :s My concern is the fact that your system seems to be constantly preparing the sound stream for playback instead of preparing it once and then utilising it. Which part of the startup process is this? Is the machine trying to play a startup sound? I don't know why the playback_prepare function is being repeatedly called. Are you sure that all this scrolling output is the same? Anyway, to at least get rid of the messages to try and rule that out, you will need to get alsa-driver 1.0.14 running. At glance, I can't see a reason for the driver to crash a machine, although, it has received minimal testing on the ALS300+ chip, which your laptop most likely posesses. I was only able to attain the programming information for the ALS300 chip. The ALS300+ support was added by reverse engineering. Ash -- module kernel snd_als300 endless loop https://bugs.launchpad.net/bugs/119083 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
