From: Dan Williams <dcbw@redhat.com>
To: Marcus Furlong <furlongm@hotmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: RE: iwl3945 problem with 2.6.25-rc9
Date: Wed, 16 Apr 2008 16:04:52 -0400 [thread overview]
Message-ID: <1208376292.27708.3.camel@localhost.localdomain> (raw)
In-Reply-To: <fu5l5r$pm8$1@ger.gmane.org>
On Wed, 2008-04-16 at 20:48 +0100, Marcus Furlong wrote:
> On Wednesday 16 April 2008 20:01 in <fu5iel$c45$1@ger.gmane.org>, Marcus
> Furlong wrote:
>
> > On Wednesday 16 April 2008 19:28 in
> >
> <D936D925018D154694D8A362EEB08920043535A1@orsmsx416.amr.corp.intel.com>,
> > Chatre, Reinette wrote:
> >
> >> Looks like the device is being brought up and down a lot ... are you
> >> perhaps running wpa_supplicant or some other user application that is
> >> doing this? Could you please give more information about what you were
> >> doing when these errors started to appear?
> >
> > Yes, wpa_supplicant is running as part of the boot process. Should I use
> > some other application? (Do wireless-tools support WPA?) Or should I just
> > load the module on it's own and give the dmesg output from that?
>
> Here is the output from the module loading without wpa_supplicant, then me
> reloading it with debug flags, and running ifconfig wlan0 and iwlist
> scanning. Still some Microcode SW and FW errors in there, but there's a lot
> less noise.
>
> https://www.cs.tcd.ie/~furlongm/iwlwifi/iwl3945-output-no-wpasupplicant.bz2
Interesting; can you run wpa_supplicant again but dump it's detailed
output using "-dddt" for us so we can see what it's doing and if it's
causing the restarts?
Dan
next prev parent reply other threads:[~2008-04-16 20:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 22:24 iwl3945 problem with 2.6.25-rc9 Marcus Furlong
2008-04-16 18:28 ` Chatre, Reinette
2008-04-16 19:01 ` Marcus Furlong
2008-04-16 19:26 ` Dan Williams
2008-04-16 19:48 ` Marcus Furlong
2008-04-16 20:04 ` Dan Williams [this message]
2008-04-16 21:22 ` Chatre, Reinette
2008-04-16 22:05 ` Marcus Furlong
2008-04-16 22:55 ` Chatre, Reinette
2008-04-17 0:06 ` Marcus Furlong
2008-04-18 3:03 ` Marcus Furlong
2008-04-18 21:46 ` Chatre, Reinette
2008-04-18 21:57 ` Johannes Berg
2008-04-18 22:12 ` Chatre, Reinette
2008-04-18 22:23 ` Brian Morrison
2008-04-18 22:35 ` Chatre, Reinette
2008-04-18 22:38 ` Brian Morrison
2008-04-18 22:37 ` Johannes Berg
2008-04-18 22:39 ` Johannes Berg
2008-04-19 0:28 ` Tomas Winkler
2008-04-19 8:32 ` Johannes Berg
2008-04-19 12:39 ` Vincent C Jones
2008-04-19 13:09 ` Johannes Berg
2008-04-19 13:44 ` Vincent C Jones
2008-04-19 13:48 ` Johannes Berg
2008-04-19 13:51 ` Johannes Berg
2008-04-20 15:33 ` Dan Williams
2008-04-20 15:24 ` Dan Williams
2008-04-20 20:39 ` Tomas Winkler
2008-04-21 0:14 ` Dan Williams
2008-04-21 18:39 ` Tomas Winkler
2008-04-21 19:20 ` Dan Williams
2008-04-21 20:47 ` Tomas Winkler
2008-04-20 15:28 ` Dan Williams
2008-04-19 2:32 ` Marcus Furlong
2008-04-22 23:02 ` Chatre, Reinette
2008-04-23 13:23 ` Marcus Furlong
2008-04-16 23:01 ` Marcus Furlong
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=1208376292.27708.3.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=furlongm@hotmail.com \
--cc=linux-wireless@vger.kernel.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).