I used gmplayer (from Christian Marillat's excellent archive) to play a video file this morning. Gmplayer froze, and I had to kill it. Now *no* sound will play, and this is in /var/log/messages:
Jul 19 07:41:30 nitpicking kernel: printing eip: Jul 19 07:41:30 nitpicking kernel: df935efb Jul 19 07:41:30 nitpicking kernel: Oops: 0000 Jul 19 07:41:30 nitpicking kernel: CPU: 0 Jul 19 07:41:30 nitpicking kernel: EIP: 0010:[<df935efb>] Not tainted Jul 19 07:41:30 nitpicking kernel: EFLAGS: 00010202 Jul 19 07:41:30 nitpicking kernel: eax: df935efb ebx: 00000002 ecx: ff7979ab edx: 12d90203 Jul 19 07:41:30 nitpicking kernel: esi: df97bff2 edi: ca08c850 ebp: df97dffe esp: c28e9e8c Jul 19 07:41:30 nitpicking kernel: ds: 0018 es: 0018 ss: 0018 Jul 19 07:41:30 nitpicking kernel: Process gmplayer (pid: 3809, stackpage=c28e9000) Jul 19 07:41:30 nitpicking kernel: Stack: df9331a2 ca08c7c0 ce2d7340 c28e9eb8 00000208 ffffffff 00000000 c0220bb0 Jul 19 07:41:30 nitpicking kernel: df935d21 df935e72 df935efb ca08c830 00000000 00000004 00000004 00000001 Jul 19 07:41:30 nitpicking kernel: 02030203 000002a9 00000bff 00000400 ca08c7c0 cf1fb640 df9363ec ca08c7c0 Jul 19 07:41:30 nitpicking kernel: Call Trace: [<df9331a2>] [<df935d21>] [<df935e72>] [<df935efb>] [<df9363ec>] Jul 19 07:41:30 nitpicking kernel: [<df933597>] [<df92f3af>] [<df92f55b>] [<df931483>] [<c013c443>] [<c0108e8f>] Jul 19 07:41:30 nitpicking kernel: Jul 19 07:41:30 nitpicking kernel: Code: 8b 45 00 eb ac 0f b6 45 00 c1 e0 08 eb a3 81 fa 00 80 00 00 And now, I can't unload the sound drivers. They all report being busy. I'm going to have to reboot to get sound back, I guess. I've never experienced a kernel oops on this system. It's disturbing. Should I report this as a bug in kernel-image-2.4.20-3-k7? There are currently no visible bugs against any of the 2.4.20 kernels that I could find. Or is it a bug in the sound modules? And: I sent essentially this message about 6 hours ago, and it was never posted. That's three messages sent to debian-user that just disappeared into the ether, neither posted nor bounced. That should never happen. I know lists.debian.org accepted them, because I'm running my own SMTP server. Is anyone else experiencing this? -- Carl Fink [EMAIL PROTECTED] Jabootu's Minister of Proofreading http://www.jabootu.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
