Description of problem: Network Manager drops PAN connections Version-Release number of selected component (if applicable): [root@localhost ~]# rpm -aq | grep Network NetworkManager-pptp-0.7.997-3.git20100120.fc12.i686 NetworkManager-openvpn-0.7.996-4.git20090923.fc12.i686 NetworkManager-0.8.0-6.git20100408.fc12.i686 NetworkManager-gnome-0.8.0-6.git20100408.fc12.i686 NetworkManager-vpnc-0.7.996-4.git20090921.fc12.i686 NetworkManager-glib-0.8.0-6.git20100408.fc12.i686 [root@localhost ~]# rpm -aq | grep blue bluez-4.58-1.fc12.i686 bluez-compat-4.58-1.fc12.i686 bluez-cups-4.58-1.fc12.i686 pulseaudio-module-bluetooth-0.9.21-5.fc12.i686 gnome-bluetooth-libs-2.28.6-2.fc12.i686 bluecurve-cursor-theme-8.0.2-5.fc12.noarch bluez-libs-4.58-1.fc12.i686 gnome-bluetooth-2.28.6-2.fc12.i686 How reproducible: Always Steps to Reproduce: 1.Pair with your iPhone 2.Connect to the PAN Network via Network Manager 3.Will work for 30 seconds and then drop with messages in /var/log/messages May 31 18:07:54 localhost kernel: btusb_intr_complete: hci0 urb f3b44a80 failed to resubmit (1) May 31 18:07:54 localhost kernel: btusb_bulk_complete: hci0 urb f3b44d00 failed to resubmit (1) May 31 18:07:54 localhost kernel: btusb_bulk_complete: hci0 urb f3b44880 failed to resubmit (1) Actual results: Works for a few seconds Expected results: Stays connected Additional info: Non Network Manager related components work as exprected: running the following gets the connection running flawlessly: pand --conncect BTADDRESS -n dhclient bnep0
This is a kernel driver and/or Bluez issue and possibly related to crappy hardware (which is still a kernel driver issue), not an NM issue.
(In reply to comment #1) > This is a kernel driver and/or Bluez issue and possibly related to crappy > hardware (which is still a kernel driver issue), not an NM issue. If you read the Additional info section, you will see that I already nailed it on NetworkManager.
I have the same issue on Fedora 13. Starting the network with "pand" works. If I start it from NetworkManager the network goes down after a few seconds with the same messages as in the inital report.
How is this a kernel bug when pand works and NetworkManager does not? If the hardware is "crappy" it should not work in either case.
This actually was a bug in NM, and was fixed in early May. *** This bug has been marked as a duplicate of bug 586961 ***