linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: George Kadianakis <asn@woodpecker.gentoo.org>
Cc: linux-wireless@vger.kernel.org, rt2400-devel@lists.sourceforge.net
Subject: Re: kernel panic with rt61pci
Date: Mon, 13 Apr 2009 23:41:18 +0200	[thread overview]
Message-ID: <200904132341.18679.IvDoorn@gmail.com> (raw)
In-Reply-To: <20090413211131.GA11257@woodpecker.gentoo.org>

Hi,

> this mail is the result of:
> http://bugs.gentoo.org/show_bug.cgi?id=262862
> 
> The problem is a 2.6.28 regression (which is fixed in 2.6.29) that
> causes a kernel panic when rt61pci tries to connect to a router.
> 
> You can find a screenshot of the panic over here:
> http://bugs.gentoo.org/attachment.cgi?id=185431
> For more info, visit the Gentoo bug entry page.
> 
> Any ideas on the patch that fixes the crash?

Yes, a very simple one actually.

As mentioned in the bugreport, going through all patches
is unfeasable. There are way too many patches and when you
do get the patch there are probably a lot of dependencies on earlier
patches.

However the bug occurs within Hardware crypto functionality,
this means that the best workaround is to disable the HW crypto itself.
Below is the patch which disables HW crypto by default. Note that it still
allows it to be enabled by using the nohwcrypt=0 module parameter.

If indeed the bug is not present in 2.6.29, I think below patch is the one
most worthwhile. :)

Ivo

---
diff --git a/drivers/net/wireless/rt2x00/rt2500usb.c b/drivers/net/wireless/rt2x00/rt2500usb.c
index 9e630e7..e1ba2e8 100644
--- a/drivers/net/wireless/rt2x00/rt2500usb.c
+++ b/drivers/net/wireless/rt2x00/rt2500usb.c
@@ -38,7 +38,7 @@
 /*
  * Allow hardware encryption to be disabled.
  */
-static int modparam_nohwcrypt = 0;
+static int modparam_nohwcrypt = 1;
 module_param_named(nohwcrypt, modparam_nohwcrypt, bool, S_IRUGO);
 MODULE_PARM_DESC(nohwcrypt, "Disable hardware encryption.");
 
diff --git a/drivers/net/wireless/rt2x00/rt61pci.c b/drivers/net/wireless/rt2x00/rt61pci.c
index 4346cd1..1e1bf5c 100644
--- a/drivers/net/wireless/rt2x00/rt61pci.c
+++ b/drivers/net/wireless/rt2x00/rt61pci.c
@@ -40,7 +40,7 @@
 /*
  * Allow hardware encryption to be disabled.
  */
-static int modparam_nohwcrypt = 0;
+static int modparam_nohwcrypt = 1;
 module_param_named(nohwcrypt, modparam_nohwcrypt, bool, S_IRUGO);
 MODULE_PARM_DESC(nohwcrypt, "Disable hardware encryption.");
 
diff --git a/drivers/net/wireless/rt2x00/rt73usb.c b/drivers/net/wireless/rt2x00/rt73usb.c
index 853b2b2..48a109a 100644
--- a/drivers/net/wireless/rt2x00/rt73usb.c
+++ b/drivers/net/wireless/rt2x00/rt73usb.c
@@ -39,7 +39,7 @@
 /*
  * Allow hardware encryption to be disabled.
  */
-static int modparam_nohwcrypt = 0;
+static int modparam_nohwcrypt = 1;
 module_param_named(nohwcrypt, modparam_nohwcrypt, bool, S_IRUGO);
 MODULE_PARM_DESC(nohwcrypt, "Disable hardware encryption.");
 

      reply	other threads:[~2009-04-13 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 21:11 kernel panic with rt61pci George Kadianakis
2009-04-13 21:41 ` Ivo van Doorn [this message]

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=200904132341.18679.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=asn@woodpecker.gentoo.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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).