Bug 431800 - repeatable hang of rmmod of rtl8187
repeatable hang of rmmod of rtl8187
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-02-06 19:28 EST by David Mansfield
Modified: 2014-06-16 09:11 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 00:56:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
sysrq-t after hang (186.18 KB, text/plain)
2008-02-06 19:28 EST, David Mansfield
no flags Details

  None (edit)
Description David Mansfield 2008-02-06 19:28:28 EST
Description of problem:
rmmod of rtl8187 hangs and rmmod and ksoftirqd go to 100% CPU in top.  this
happens after the network 'goes dead' which happens after about 15-30 minutes of

Version-Release number of selected component (if applicable):

kernel-, x86_64. dual core processor

How reproducible:
every time i use the card it dies within 15 minutes, and after this rmmod hangs
every time

Steps to Reproduce:
1. ifup
2. let nytimes.com reload for a while by itself until the network dies
Actual results:
rmmod hangs, ksoftirqd and rmmod go to 100%

Expected results:

Additional info:

i have dmesg and output from sysrq-t available, but it doesn't seem to include a
stack trace of rmmod or ksoftirqd.  in fact, the capture of sysrq-t is almost
definitely truncated (see beginning of attached file)

i'm going to attach the syslog capture of the sysrq-t
Comment 1 David Mansfield 2008-02-06 19:28:28 EST
Created attachment 294174 [details]
sysrq-t after hang
Comment 2 Hin-Tak Leung 2008-10-31 19:37:11 EDT
A lot of work has gone into the rtl8187 driver recently because of the rtl8187b work in 2.6.26.x/2.6.27.x. Is this still an issue?
Comment 3 Bug Zapper 2008-11-26 04:43:37 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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: 
Comment 4 Bug Zapper 2009-01-09 00:56:13 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.
Comment 5 Hin-Tak Leung 2009-01-09 06:48:43 EST
Recently one of us specifically made some changes to address this issue in the rtl8187 code. This should no longer be the issue with a sufficiently new driver code - the change will likely land in 2.6.29. People can't wait should get compat-wireless today.
Comment 6 David Mansfield 2014-06-16 09:11:30 EDT
I'm a "needinfo" but this is a dead issue.

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