i've discovered this bug from the test9 version of kernel.. but i was waiting for see this fixed... until now :) so.. the bug completely hangs the system. you need a shutdown or a reboot for continue using your pc steps to reproduce: 1) rfcomm bind 2 11:22:33:44:55:66 1 # 11:22:33:44:55:66 is the bluetooth ID of your gprs cellularphone 2) pppd file /etc/ppp/nokia-3650 /dev/rfcomm2 etc ... etcc. etc.. #IF THE PHONE is turned off... the rfcomm hangs, and u need to kill manually the pppd process (or with CTRL+C) - you now have your rfcomm2 blocked. there are 2 variables of this bug. A) the rfcomm is blocked so, you turn on your phone, then write "pppd file /etc/ppp/nokia-3650 /dev/rfcomm2" and it will print: "Failed to open /dev/rfcomm2: Device or resource busy" B) you turn on the phone, try to connect... and you get a error similar to: /dev/rfcomm2 is used by pid xxxx the pid xxxx is the previous pppd instance... and he becomes inkillable! (i tried killall pppd or kill -9 xxxx) in this two cases if you shutdown the phone, remove the bluetooth adapter or try to close the rfcomm device with "rfcomm release 2" the pc hangs completely :
i've discovered this bug from the test9 version of kernel.. but i was waiting for see this fixed... until now :) so.. the bug completely hangs the system. you need a shutdown or a reboot for continue using your pc steps to reproduce: 1) rfcomm bind 2 11:22:33:44:55:66 1 # 11:22:33:44:55:66 is the bluetooth ID of your gprs cellularphone 2) pppd file /etc/ppp/nokia-3650 /dev/rfcomm2 etc ... etcc. etc.. #IF THE PHONE is turned off... the rfcomm hangs, and u need to kill manually the pppd process (or with CTRL+C) - you now have your rfcomm2 blocked. there are 2 variables of this bug. A) the rfcomm is blocked so, you turn on your phone, then write "pppd file /etc/ppp/nokia-3650 /dev/rfcomm2" and it will print: "Failed to open /dev/rfcomm2: Device or resource busy" B) you turn on the phone, try to connect... and you get a error similar to: /dev/rfcomm2 is used by pid xxxx the pid xxxx is the previous pppd instance... and he becomes inkillable! (i tried killall pppd or kill -9 xxxx) in this two cases if you shutdown the phone, remove the bluetooth adapter or try to close the rfcomm device with "rfcomm release 2" the pc hangs completely :° i will include a syslog of the problem.. but... there is nothing interesting
Created attachment 25762 [details] log of my pc from the turn on to the hang
improvement with the 2.6.[1234] releases ? not sure how we can help here, seemsl ike a kernel problem to me.
did a newer release of the kernel or ppp fix this?
Closing due to lack of feedback.
