Bug 389221 - b44 resume stack trace.
Summary: b44 resume stack trace.
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-11-18 11:08 UTC by Simon Goodall
Modified: 2008-08-21 20:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-21 20:53:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
b44 stack trace (1.24 KB, text/plain)
2007-11-18 11:08 UTC, Simon Goodall
no flags Details
updated backtrace (2.52 KB, text/plain)
2008-03-02 21:10 UTC, Simon Goodall
no flags Details

Description Simon Goodall 2007-11-18 11:08:31 UTC
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):

How reproducible:

Steps to Reproduce:
1. Make sure b44 driver is loaded
2. Suspend/hibernate machine
3. Resume.
4. Look in logs.
Actual results:
Stack trace

Expected results:
No stack trace.

Additional info:

Comment 1 Simon Goodall 2007-11-18 11:08:31 UTC
Created attachment 262831 [details]
b44 stack trace

Comment 2 Christopher Brown 2008-02-13 23:08:26 UTC

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.

Comment 3 Simon Goodall 2008-02-19 14:49:49 UTC
I had not noticed this bug for a little while until today as NM died for some
reason. I am currently running kernel

I do not need to remove the module to make hibernate and resume work properly.

Comment 4 Christopher Brown 2008-02-24 15:46:19 UTC
(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

Did you get a stack trace in the logs when this happened?

Comment 5 Simon Goodall 2008-03-02 21:10:12 UTC
Created attachment 296523 [details]
updated backtrace

Yes, I got a similar backtrace, see attachment.

Comment 6 John W. Linville 2008-03-03 14:56:33 UTC
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?

Comment 7 David Nalley 2008-08-21 20:53:50 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.