Bug 598171
Summary: | Network Manager drops PAN connections after succesfully establishing them with errors btusb_intr_complete and btusb_bulk_complete | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | jesus |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | anton, dcbw, dougsland, gansalmon, itamar, jonathan, kernel-maint, psvbugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-17 16:34:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
jesus
2010-05-31 16:28:36 UTC
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 *** |