Folks, I upgrade my Linux from 3.4.0 to 3.6.2.
When I finish the call with Twinkle, in that moment entire system freeze. ping or ssh is not working, NumLock and SysRq as well. Only think I can do is the Power button.
In logs is nothing.
First I thought it is due to new graphic driver for Nvidia card, but if I just go back to 3.4.0 without any other changes, there is no problem. I tried also 3.6.3 but with the same result. It does not matter if I finish the call by clicking or other side hangs the call (I suspected GUI).

I have no clue how can I find the source of the trouble in such a case.

Can anybody help me to identify it?

thanks

Was the kernel the only item that was upgraded?


Dmesg, system, Twinkle, which logs?
If system logs, did you check your system logs errors at all?
If Twinkle, have you tried configuring it to do debug logging?

Originaly I upgraded kernel and Nvidia driver. Then I upgraded kernel from 3.6.2 to 3.6.3. Nothing has change. Then I wend to older kernel - 3.4 but I kept new Nvidia drivere. And everythig works again.


syslog, daemon, kernel. No changes in /var/log few minutes before freeze

I did not touch twinkle.

Easy, easy, no prosecutor will charge you ;-p

Have you tried configuring it to do debug logging? System Settings > Log > Log debug reports, then crash your machine yet again. Before you reboot it press ALT+PRINTSCREEN+S a couple of times to at least try and sync the file system, then press ALT+PRINTSCREEN+U a couple of times and then ALT+PRINTSCREEN+B. When rebooted check ~/.twinkle/twinkle.log.

I will try tomorrow, but as I wrote in my original post, the PRINTSCREEN did not work as well. Alt-SysRQ S-U-B .....

So today

Alt+SysRQ is not working. But I retried.

In the Twinkle log is:
*************Call-ID: znyhuzuwslnbxqe@opahapaka^M
CSeq: 322 REGISTER^M
Server: (Very nice Sip Registrar/Proxy Server)^M
Allow: ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE^M
Content-Length: 0^M
^M

---

+++ 24-10-2012 20:27:19.934305 DEBUG NORMAL t_phone::handle_response_out_of_dialog
Out of dialog matches phone user: Dodo
---

+++ 24-10-2012 20:27:19.937777 DEBUG NORMAL t_abstract_dialog::t_abstract_dialog
Created dialog, id=22
---

+++ 24-10
******************************************************
So it hangs during the logging.

Any other idea I can try? Thanks ...

...

No, best contact the developer.

O.K. So one step farther.Looks like it is usb_audio.

When I use different audio card, it is working. It's freezing only when I do the call via USB headset. So that's maybe more topic for alsa people then Twinkle ...

Cool. How did you find out? What was your clue? If usb_audio and related audio / USB / sound modules have debug options (man modinfo, man modprobe) then maybe you can learn something from enabling those?

Sometimes is better to be lucky then smart I just switch in Twinkle from USB head seat to onboard Intel audio. And then I finished my call to myself without any problem. When I then switched back to usb audio and .... freeze

I will look at Alsa debugging but also I am curious if someone can reproduce the problem, so going to find some Twinkle forum ...

See http://tech.groups.yahoo.com/group/twinklephone/