Bug 12324
Summary: | using emu10k1 hardware synth freezes computer | ||
---|---|---|---|
Product: | Drivers | Reporter: | Guillaume Radde (guillaumeradde) |
Component: | Sound(ALSA) | Assignee: | Jaroslav Kysela (perex) |
Status: | CLOSED OBSOLETE | ||
Severity: | normal | CC: | alan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.28 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | lsmod |
Description
Guillaume Radde
2008-12-29 13:44:59 UTC
Same bug happens with a freshly compiled 2.6.28 kernel. What sequencer timer module is being used? If snd-rtctimer driver is loaded, try to unload / disable it. The emu10k1 synth itself seems working fine on my test machine, and I don't think it's an audigy2-specific issue. Created attachment 19727 [details]
lsmod
snd-rtctimer doesn't seem to be loaded. I attached the output of lsmod. Also, this bug report in ubuntu bugtracker seems to be related: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/34831 Does the hang up occur also when you play MIDI on emu10k1, not from MIDI input? For example, aplaymidi -p $EMUPORT somefile.mid causes the same lock-up? Yes, I ran the following commands and the computer played a few notes and froze: guignome@alphonse:~$ asfxload ADC-TranceKit.sf2 guignome@alphonse:~$ aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 16: 'Audigy 2 [Unknown]' [type=kernel] 0 'Audigy MPU-401 (UART)' 32 'Audigy MPU-401 #2' client 17: 'Emu10k1 WaveTable' [type=kernel] 0 'Emu10k1 Port 0 ' 1 'Emu10k1 Port 1 ' 2 'Emu10k1 Port 2 ' 3 'Emu10k1 Port 3 ' client 20: 'Keystation 49e' [type=kernel] 0 'Keystation 49e MIDI 1' guignome@alphonse:~$ aplaymidi --port=17:0 HitTheLights.mid OK, what about other output ports? For example, aplaymidi --port=20:0 HitTheLights.mid I haven't tried that for a while but if I remember correctly, it was giving the exact same result. I will double check on that tonight. Thanks for following up on this bug! Oh wait, you mean routing aplaymidi to something else than the emu10k1 wavetable. I had tried to route aplaymidi to timidity and it was working OK (slow but working). I will try again tonight to make sure. Confirmed. If I run timidity -iA -Os, and then aplaymidi -p 129:0 myfile.mid (where 129:0 is timidity's port), I can hear my song playing and everything works fine. If I run aplaymidi -p 17:0 (where 17:0 is the emu10k1 wavetable port), the computer hangs up. OK. One more test: try to play MIDI notes without sequencer queuing. That is, run a program like vkeybd, connect to emu10k1 wavetable port, and play notes there. If this causes the lock-up, it means that only the emu10k1 wavetable part (and/or the event-delivering part) is the culprit. If it doesn't cause the problem, the combination of queue and emu10k1 is the key. Here is what I did: -Ran vkeybd -Loaded a soundfont in the card with asfxload -connected vkeybd output to the emu10k1 wavetable with acconect -clicked on 3 keys on vkeybd's virtual keyboard. None of the 3 notes played and the computer hung up. OK, then it's very likely emu10k1-specific. Does this "vkeybd -> emu10k1" hang occurs even if you don't load soundfonts? No, the computer doesn't hang if there is no soundfont loaded in the soundcard. Here is what I did: -Ran vkeybd -connected vkeybd to the emu10k1 wavetable port with aconnect -played 300 notes with vkeybd ...Nothing happened.... -loaded a font in the soundcard with asfxload -played a few notes on vkeybd ....Computer hang..... Note that I tried to load several different soundfonts and the computer hang each time. Thanks. How much RAM do your machine have? If it's over 2GB, try to limit to 2GB via boot option. I only have 1GB of RAM. |