All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	wireless <linux-wireless@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Regression in 2.6.30-rc1 since commit acae0515 - wireless broken
Date: Tue, 07 Apr 2009 23:54:13 -0500	[thread overview]
Message-ID: <49DC2DF5.3010603@lwfinger.net> (raw)

The most recent pulls of the Linux-2.6 git tree has broken wireless. The problem
was bisected with commit acae05156551fd7528fbb616271e672789388e3c, entitled
"module: create a request_module_nowait()", indicated as the faulty change. This
is seen with driver b43 on my system, and 2 reports for driver iwlagn:
http://marc.info/?l=linux-wireless&m=123916157630571&w=2 and
http://marc.info/?l=linux-wireless&m=123913015021457&w=2.

For b43, the logged error messages are:

phy0: Failed to initialize wep: -2
b43: probe of ssb0:0 failed with error -2

With this driver, module ssb is selected from the PCI ID. It then loads b43,
which triggers the loading of rfkill, mac80211, cfg80211, led-class, and
input-polldev. It appears that the nowait method is killing the chain somewhere.
If I unload and reload b43, then all these modules load correctly and wireless
works.

If this commit is reverted, wireless works OK.

I will be happy to try any patches to make request_module_nowait() work with
wireless networking.

Larry



             reply	other threads:[~2009-04-08  4:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  4:54 Larry Finger [this message]
2009-04-08  5:11 ` Regression in 2.6.30-rc1 since commit acae0515 - wireless broken Arjan van de Ven
2009-04-08  7:01   ` Rusty Russell
2009-04-08 13:46     ` Sedat Dilek
2009-04-08 13:46       ` Sedat Dilek
2009-04-08 14:49     ` Larry Finger
2009-04-08 17:06       ` Alan Jenkins
2009-04-08 17:32         ` Larry Finger
2009-04-08 23:49           ` Randy Dunlap
2009-04-09  0:02             ` Larry Finger
2009-04-08 20:05         ` Andreas Schwab
2009-04-08 21:13           ` Larry Finger
2009-04-09  0:06           ` Rusty Russell

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=49DC2DF5.3010603@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rusty@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.