From: Larry Finger <Larry.Finger@lwfinger.net>
To: Richard Farina <sidhayn@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
Hin-Tak Leung <hintak.leung@gmail.com>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Subject: Possible fix for rtl8187: kernel oops when leds enabled
Date: Tue, 03 Nov 2009 17:22:45 -0600 [thread overview]
Message-ID: <4AF0BB45.5000402@lwfinger.net> (raw)
In-Reply-To: <4AE5CDCB.8090400@gmail.com>
Rick,
Does this patch fix your problem? I tried to bisect this problem as it
looked like a regression; however, the problem was sometimes a little
flakey. On one boot of a given kernel, it might run for 3-400 cycles
without failing, then fail immediately after rebooting. I suspect that
the random contents of some memory location would control that.
This patch was inspired by the code in p54usb, which does not have the
problem.
Index: wireless-testing/drivers/net/wireless/rtl818x/rtl8187_leds.c
===================================================================
--- wireless-testing.orig/drivers/net/wireless/rtl818x/rtl8187_leds.c
+++ wireless-testing/drivers/net/wireless/rtl818x/rtl8187_leds.c
@@ -210,10 +210,10 @@ void rtl8187_leds_exit(struct ieee80211_
/* turn the LED off before exiting */
ieee80211_queue_delayed_work(dev, &priv->led_off, 0);
- cancel_delayed_work_sync(&priv->led_off);
- cancel_delayed_work_sync(&priv->led_on);
rtl8187_unregister_led(&priv->led_rx);
rtl8187_unregister_led(&priv->led_tx);
+ cancel_delayed_work_sync(&priv->led_off);
+ cancel_delayed_work_sync(&priv->led_on);
}
#endif /* def CONFIG_RTL8187_LED */
Thanks for testing,
Larry
next prev parent reply other threads:[~2009-11-03 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 15:17 rtl8187: kernel oops when leds enabled Richard Farina
2009-10-26 15:50 ` Larry Finger
[not found] ` <4AE5CDCB.8090400@gmail.com>
2009-10-26 18:27 ` Larry Finger
2009-11-03 23:22 ` Larry Finger [this message]
2009-11-04 5:50 ` Possible fix for " Richard Farina
2009-10-26 18:20 ` Hin-Tak Leung
2009-10-27 16:56 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF0BB45.5000402@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sidhayn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).