linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: alexxy@gentoo.org
Cc: linux-wireless@vger.kernel.org, wimax@linuxwimax.org
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card
Date: Wed, 28 Jul 2010 11:23:42 -0700	[thread overview]
Message-ID: <1280341422.26204.307.camel@localhost.localdomain> (raw)
In-Reply-To: <1280340597.26204.300.camel@localhost.localdomain>

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:

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

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?



  reply	other threads:[~2010-07-28 18:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201007280028.48674.alexxy@gentoo.org>
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 [this message]
2010-07-28 21:14         ` Dan Williams
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:
  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=1280341422.26204.307.camel@localhost.localdomain \
    --to=inaky@linux.intel.com \
    --cc=alexxy@gentoo.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wimax@linuxwimax.org \
    /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).