Bug 20122
Summary: | 2.6.36 fails to recover networking after microcode error | ||
---|---|---|---|
Product: | Networking | Reporter: | rocko (rockorequin) |
Component: | Wireless | Assignee: | networking_wireless (networking_wireless) |
Status: | CLOSED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | linville, wey-yi.w.guy |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.36-rc7 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
rocko
2010-10-12 03:48:25 UTC
Note that connections formed after DHCP succeeds but before the microcode error occurs continue to work after the error occurs - eg if Skype connects in time, it will continue to work after the error - but attempts to form any new connection after the error always fail. This is still a problem with 2.6.36-rc8. In my ad-hoc test, it succeeded in keeping the connection after the microcode error on the first time and the sixteenth time that I tried. Since it does work occasionally, it appears that there is a timing issue that causes the regression. Does this problem persist with 2.6.37 or later? I haven't been back to the site where the problem occurs since October so I haven't been able to try 2.6.37 yet. I hope to be onsite in the coming weeks and be able to report back. Any word on this issue? Does the problem persist with current kernels? Closed due to lack of response... Sorry, I haven't been back to that site since, so I can't test it. |