Hi folks,
Ok, I had made some tests yesterday evening and I will go on this evening. I tried the magic key and the insert (actually now I get what it is doing and this is very nice!). But I did those things in the wrong order and I have to start again the 'get ready and freeze' session this evening. Anyway, my conclusions are the following: When I run two alsamixer and that I change the volume of one of them, according to Alt+Sys_Rq+t the current process is the alsamixer that I just tried to modify. And it's stuck. I mean REALLY stuck. There is no more other process running but this one which seems to wait something. What is suprising me is that the kernel should take care of the liveness of the system and it seems to not detect this problem (I mean the distribution of cpu time should be fair among processes). I can add that I noticed that even if there is no more ssh, no more inetd, and so on, the ping is responding. Which means that the very low level kernel features are still active. So, this problem *could* be also related to a Linux kernel problem in the SMP part... (I mean, you can blow the system like this only with sound driver, do you?). Anyway, the facts are that one of the alsamixer (the one which ask for a modification) is hanging to death and making the other process starving. And moreover, I can't kill it by Alt+Sys_Rq+k... So, just for now, wait for the correct trace of the problem that I will try to get this evening. And if you have any idea, feel free to ask for some other tests. I love to freeze my computer, it makes my thanks giving more delightful. :-) -- Emmanuel `My doctor says that I have a malformed public-duty gland and a natural deficiency in moral fibre, and that I am therefore excused from saving Universes.' -- Ford last attempt to get out of the story (Douglas Adams) _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
