Public bug reported: I am tentatively reporting this here since the bug appears to be specific to my Audigy 4, and does not appear when on-board sound is used instead.
Ubuntuforums threads: http://ubuntuforums.org/showthread.php?t=617777 http://ubuntuforums.org/showthread.php?t=622389 To summarise what is in the above two threads, my system will hard lock when the Audigy 4 is in use for playback, the software raid is being accessed, and any ethernet port is connected to the network (though not necessarily in use). Version numbers: alsa-base: 1.0.14-1ubuntu2 mdadm: 2.6.2-1ubuntu2 Ubuntu: Gutsy (7.10) [EMAIL PROTECTED]:~$ uname -a Linux tokaygecko 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux Motherboard is a VIA chipset, specifically an Abit AX8-V Ethernet problems discovered using both on-board gigabit controller and PCI-based Belkin Gigabit Ethernet Controller. Sound card is a Creative Audigy 4, OEM edition (so no breakout box or remote control). To reproduce (method 1): Boot system Wait for network to connect Start playing an audio file directly off raid filesystem - machine crashes, usually before first sound output is heard (method 2): Boot system Wait for network to connect Start playing an audio file on a non-raided filesystem Access the raided filesystem (sometimes small operations aren't enough, block transfers seem to consistently work for this) - machine crashes, apparently instantly (method 3): Boot system Ensure network devices are disconnected (e.g. with sudo ifdown eth0) Start playing an audio file directly off raid filesystem Bring up network connection (e.g. sudo ifup eth0) - brief pause for DHCP, if applicable, then full lock as soon as IP address is registered. ------------------------------------------------------ If you need more information, give me a hint on where to find it and I will do my best. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- Conflict between Audigy 4, mdadm software raid and networking https://bugs.launchpad.net/bugs/172458 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
