Bug 539438
| Summary: | wpa_supplicant crashes on resume | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gordon Messmer <gordon.messmer> | ||||||
| Component: | wpa_supplicant | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 12 | CC: | bschueler, dcbw, skr, tore | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-12-04 03:07:00 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Gordon Messmer
2009-11-20 07:04:17 UTC
I'm also seeing this and can also provide more core files/debug info if necessary. See also bug #538717 for the NetworkManager counterpart. Tore *** Bug 540290 has been marked as a duplicate of this bug. *** Is there any chance you can get *another* backtrace from the supplicant and see if it dies in the same spot? The backtrace you were able to get (thanks!) is quite odd, and probably indicates heap corruption since the segfault inside glibc memory allocation functions. Also, if you're able to get the supplicant to die in gdb (start it under gdb initially using the arguments in /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service) and it dies at the same place, please print out the value of 'buflen' from whatever stack frame wpa_driver_wext_get_range() is. Thanks! Created attachment 405875 [details]
More complete backtrace
As requested I am able to generate a more complete backtrace (as generated by abrt). It appears to have failed in exactly the same way, and like the OP it happened on a resume after a suspend. As you can see, the value of 'buflen' in wpa_driver_wext_get_range() is 1068.
/var/log/wpa_supplicant.log doesn't show up anything of use.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |