Red Hat Bugzilla – Bug 389221
b44 resume stack trace.
Last modified: 2008-08-21 16:53:50 EDT
Description of problem:
When resuming from suspend or hibernate, the b44 driver dumps a stacktrace in m
y log file.
See attached file for the relevant log message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make sure b44 driver is loaded
2. Suspend/hibernate machine
4. Look in logs.
No stack trace.
Created attachment 262831 [details]
b44 stack trace
Possible dupe: bug #242234
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel? You may also wish to to
test with a 2.6.24-based kernel.
If the problem no longer exists then please close this bug or I'll do so in a
few weeks if there is no additional information lodged.
I had not noticed this bug for a little while until today as NM died for some
reason. I am currently running kernel 220.127.116.11-137.fc8.
I do not need to remove the module to make hibernate and resume work properly.
(In reply to comment #3)
> I had not noticed this bug for a little while until today as NM died for some
> reason. I am currently running kernel 18.104.22.168-137.fc8.
Did you get a stack trace in the logs when this happened?
Created attachment 296523 [details]
Yes, I got a similar backtrace, see attachment.
Please try a later F8 kernel:
That one in particular has some recent SSB patches that may relate to the
stacktrace from comment 5. Can you recreate the problem using those kernels?
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.