archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <>
To: Inaky Perez-Gonzalez <>
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card
Date: Wed, 28 Jul 2010 14:14:05 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1280341422.26204.307.camel@localhost.localdomain>

On Wed, 2010-07-28 at 11:23 -0700, Inaky Perez-Gonzalez wrote:
> On Wed, 2010-07-28 at 11:09 -0700, Inaky Perez-Gonzalez wrote: 
> > Hi Alexey
> > 
> > On Wed, 2010-07-28 at 21:53 +0400, Alexey Shvetsov wrote: 
> > > Updated relevant part of logs for this bug
> > > 
> On the other side, I just went through the huge log file you sent me --
> thx for that.
> I don't see any i2400m errors in there -- the driver seems to at least
> be able to initialize right. WiFi's iwlagn gets toasted, but i2400m is
> not really complaining about anything -- except when NetworkManager
> seemingly tries to turn on/off the radio and a message about it being
> done while the device is not in the right state is popping up:

Stock NM actually doesn't poke rfkill for any device type yet.  It
listens for killswitch changes, but it doesn't modify the switch state
at all.  It will set the wifi device !IFF_UP though.  At some point
we'll hook up rfkill to the "Wireless Enabled" checkbox, but rfkill is
such a tangled mess that it takes a bit of work to get the user
interaction right.

(there are platform and hardware switches, and sometimes the platform
switches control the hard/soft block on the hardware switches.
sometimes they don't.  and you can't really tell.  so you have to loop
through all switches, try turning them all off, and if any one fails to
turn off then you go through again until all of them turn off or until
it fails.  but you can't tell it might fail before you try...)

> ... 
> kernel: iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio.
> NetworkManager: <info>  WiFi now disabled by radio killswitch
> kernel: i2400m_usb 2-1.3:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
> NetworkManager: <info>  (wlan0): bringing up device.
> kernel: iwlagn 0000:02:00.0: Microcode SW error detected.  Restarting
> ...
> I say seemingly because I don't remember NetworkManager actually doing
> that on WiMAX devices, but I could be wrong, as they expose an RFKILL
> interface.

NM doesn't do anything yet with wimax devices, though it'll look for
wimax killswitches.  But nothing is done with them yet upstream.

So I guess my question here is whether Alexey is using a stock NM or a
distro-patched one.  Ubuntu used to patch NM to actually poke the rfkill
bits, not sure if they still do that or not.  Fedora does not, and I
don't think Novell/SUSE does either.


> So I am the more puzzled here, I guess I need to re-establish a baseline
> to curb confusion, please help me here:
> -- let's be in peace with the fact that wifi is not working at this
> point --
> (1) Does WiMAX work ok when iwlagn is unloaded? can you get to turn on
> the radio and scan?
> (2) Apparently the driver is up and running when iwlagn is loaded
> (according to your logs). Can you get the daemon to start? turn the
> radio on? scan?
> (3) when and how do you actually get that -22 error from the i2400m
> probe?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to
> More majordomo info at

  reply	other threads:[~2010-07-28 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2010-07-27 22:38 ` [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card Inaky Perez-Gonzalez
2010-07-28  0:04   ` Guy, Wey-Yi
2010-07-28 17:53   ` Alexey Shvetsov
2010-07-28 18:09     ` Inaky Perez-Gonzalez
2010-07-28 18:23       ` Inaky Perez-Gonzalez
2010-07-28 21:14         ` Dan Williams [this message]
2010-07-28 20:21           ` Inaky Perez-Gonzalez
2010-07-30 14:48             ` Alexey Shvetsov
2010-08-04 16:36               ` Inaky Perez-Gonzalez

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).