Jaroslav Kysela wrote: > On Wed, 28 Nov 2001, Steve Harris wrote: > > It's very much better to use the alsa-driver/utils/insert script, and look > to alsa-driver/snd.map file for the IP address, where driver crashed. We > can determine easily the function.
Ooops, I already got the Sys Rq key infos... I was currently trying to see how to compile alsamixer with the '-g' option to be able to follow the execution with gdb and find the functions involved in this... Ok, here are the results of the Sys Rq keys. Alt+Sys_Rq+t (tasks) ==================== alsamixer R 00000000 4728 373 314 (NOTLB) Call Trace: [<d083e8d0>] [<c014d5c7>] [<c010745b>] alsamixer R current 2440 374 315 (NOTLB) Call Trace: [<c0214f0c>] [<c01130df>] [<c0112fa4>] [<d0863174>] [<d084c57a>] [<d083e3f8>] [<d083e8df>] [<c014d5c7>] [<c010745b>] Alt+Sys_Rq+p (register of the current process) ============================================== SysRq : Show Regs Pid: 374, comm: alsamixer EIP: 0010:[<c0214f0f>] CPU: 0 EFLAGS: 00000286 Not tainted EAX: c15ce000 EBX: c0267c20 ECX: c027e000 EDX: c027e000 ESI: 00000000 EDI: c027e000 EBP: c15cfbfc DS: 0018 ES: 0018 CR0: 8005003b CR2: 4018f9d0 CR3: 0ecdd000 CR4: 000002d0 Call Trace: [<c01130df>] [<c0112fa4>] [<d0863174>] [<d084c57a>] [<d083e3f8>] [<d083e8df>] [<c014d5c7>] [<c010745b>] Where can I find more documentation on alsa-driver/utils/insert ? (I have to confess now that I am a little dumb and I didn't get all what is done in this script :-/). Regards -- Emmanuel I care about the fact that our internal design has to be robust. It doesn't have to make everybody happy, but it has to be clean both conceptually and from a pure implementation standpoint. I don't want a "hack that works." -- Linus Torvalds _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel