A NOTE has been added to this issue. ====================================================================== <https://bugtrack.alsa-project.org/alsa-bug/view.php?id=952> ====================================================================== Reported By: skunk Assigned To: ====================================================================== Project: ALSA - driver Issue ID: 952 Category: PCI - emu10k1 Reproducibility: random Severity: crash Priority: normal Status: new Distribution: Debian testing Kernel Version: 2.6.8-2-k7 ====================================================================== Date Submitted: 03-01-2005 06:28 CET Last Modified: 06-07-2006 19:50 CEST ====================================================================== Summary: System freeze at end of MIDI playback Description: Hardware: Sound Blaster Live! Value Software: sfxload (for patch loading) and drvmidi (playback) I often play a list of MIDI files. On a number of occasions---either at the end of a MIDI song, or when I hit STOP---the computer has frozen hard. The recurrence is rare enough to make this more an annoyance than a showstopper, but then, I haven't been too keen on ferreting out this bug. I am reporting this against ALSA from the 2.6.8 kernel, as that is what I'm using now (Debian official package) but the same problem arose with alsa-driver 1.0.8 (as compiled by me) on 2.4.29. I could probably rig up something to start/stop MIDI playback repeatedly, with a debug-compiled driver, but is there any way to get useful debugging output when the bug takes the whole system down? ====================================================================== ---------------------------------------------------------------------- pen - 06-07-06 19:45 ---------------------------------------------------------------------- I can't get it to happen when I want it to (typical!) :-) Would the panic be in any of the logs (if so, which one?) ---------------------------------------------------------------------- rlrevell - 06-07-06 19:50 ---------------------------------------------------------------------- Possibly in /var/log/kernel or /var/log/kern.log or whatever the hell your distro calls the kernel log. But if the bug kills the machine it's likely that the panic does not make it to any log. If you can't trigger the bug from a text console, try doing something in X that would cause the bug, then switch quickly to a text console - you may be able to see an Oops that way. Issue History Date Modified Username Field Change ====================================================================== 03-01-05 06:28 skunk New Issue 03-01-05 06:28 skunk Distribution => Debian testing 03-01-05 06:28 skunk Kernel Version => 2.6.8-2-k7 09-19-05 10:10 jdthood Note Added: 0006287 09-19-05 10:19 skunk Note Added: 0006290 04-23-06 07:57 skunk Note Added: 0009441 06-07-06 18:09 pen Note Added: 0010085 06-07-06 18:09 pen Issue Monitored: pen 06-07-06 18:23 rlrevell Note Added: 0010086 06-07-06 19:45 pen Note Added: 0010087 06-07-06 19:50 rlrevell Note Added: 0010088 ====================================================================== _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel
