From: Marcus Furlong <furlongm@hotmail.com>
To: linux-wireless@vger.kernel.org
Subject: RE: iwl3945 problem with 2.6.25-rc9
Date: Wed, 16 Apr 2008 20:01:31 +0100 [thread overview]
Message-ID: <fu5iel$c45$1@ger.gmane.org> (raw)
In-Reply-To: D936D925018D154694D8A362EEB08920043535A1@orsmsx416.amr.corp.intel.com
On Wednesday 16 April 2008 19:28 in
<D936D925018D154694D8A362EEB08920043535A1@orsmsx416.amr.corp.intel.com>,
Chatre, Reinette wrote:
> On , Marcus Furlong wrote:
>
>> Hi,
>>
>> Have had a look through bugzilla and not sure if any of the
>> existing bugs
>> are exactly the same as mine, so thought I'd post here first
>> to make sure
>> I'm not missing anything obvious.
>>
>> Kernel 2.6.25-rc9 (although the same thing seems to happen on 2.6.24
>> kernels, so I stuck with the ipw driver and 2.6.23 til now)
>> Using iwl3945 firmware 2.14.1.5
>>
>> Machine doesn't associate with any AP (although it does seem to see
>> the closer ones) and I get lots of the following errors:
>>
>> iwl3945: Microcode SW error detected. Restarting 0x82000008.
>>
>> Also, and unsure if this is related or not, the mouse and
>> keyboard behave
>> erratically when the iwl3945 module is loaded. Both keyboard
>> and mouse lock
>> up, but store all input in a buffer and spurt it out after a
>> few seconds.
>> After between 1-10 minutes the machine hangs and the Caps Lock
>> and Scroll
>> Lock lights flash on and off (not the Num Lock one though).
>>
>> Dmesg log is available here using netconsole on a wired
>> connection, up to
>> the point where it crashes:
>>
>> https://www.cs.tcd.ie/~furlongm/iwlwifi/iwlwifi-output.bz2
>>
>> I also reloaded the module with debug=0x43ffb after booting,
>> so the output
>> becomes more verbose at that stage.
>
> 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?
Marcus.
next prev parent reply other threads:[~2008-04-16 19:01 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 [this message]
2008-04-16 19:26 ` Dan Williams
2008-04-16 19:48 ` Marcus Furlong
2008-04-16 20:04 ` Dan Williams
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='fu5iel$c45$1@ger.gmane.org' \
--to=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).