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: wimax@linuxwimax.org, linux-wireless@vger.kernel.org
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card
Date: Wed, 28 Jul 2010 11:09:57 -0700	[thread overview]
Message-ID: <1280340597.26204.300.camel@localhost.localdomain> (raw)
In-Reply-To: <201007282154.06383.alexxy@gentoo.org>

Hi Alexey

On Wed, 2010-07-28 at 21:53 +0400, Alexey Shvetsov wrote: 
> Updated relevant part of logs for this bug
> 

My concern here is that I am not seeing why the i2400m is failing to
initialize; there are no i2400m relevant messages. If I remember
correctly, over IRC you said that a grep of messages for i2400m only
turned:

Jul 22 16:20:03 x201 kernel: i2400m_usb: probe of 2-1.3:1.0 failed with
error -22

It that's the case, I missed to make the code properly report an error
condition, and we need to find out which one is it.

Can you enable debugging?:

1. unload the i2400m and i2400m-usb modules
2. $ modprobe i2400m debug='driver:8 control:3'
3. $ modprobe i2400m-usb debug='usb:8'

that should be printing way more logs to the console



  reply	other threads:[~2010-07-28 18:10 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 [this message]
2010-07-28 18:23       ` Inaky Perez-Gonzalez
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=1280340597.26204.300.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).