From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Re: [BUG] iwlwifi 3945 works only with disable_hw_scan=1
Date: Thu, 12 Jun 2008 15:13:40 +0300 [thread overview]
Message-ID: <485112F4.7020207@gmail.com> (raw)
In-Reply-To: <1213241315.7814.696.camel@debian.sh.intel.com>
Zhu Yi wrote:
> On Wed, 2008-06-11 at 18:07 +0300, Maxim Levitsky wrote:
>> [ 87.270433] wlan0: Initial auth_alg=0
>> [ 87.270433] wlan0: authenticate with AP 00:1b:9e:d8:77:02
>> [ 87.273477] wlan0: RX authentication from 00:1b:9e:d8:77:02 (alg=0
>> transaction=2 status=0)
>> [ 87.273477] wlan0: authenticated
>> [ 87.273477] wlan0: associate with AP 00:1b:9e:d8:77:02
>> [ 87.275823] wlan0: RX AssocResp from 00:1b:9e:d8:77:02 (capab=0x411
>> status=0 aid=1)
>> [ 87.275823] wlan0: associated
>> [ 87.275823] wlan0: switched to short barker preamble
>> (BSSID=00:1b:9e:d8:77:02)
>> [ 87.276185] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
>> [ 92.713277] APIC error on CPU0: 40(40)
>> [ 97.885625] wlan0: no IPv6 routers present
>> [ 111.766658] wlan0: no IPv6 routers present
>> [ 112.121332] APIC error on CPU0: 40(40)
>> [ 144.876825] APIC error on CPU0: 40(40)
>> [ 158.676958] APIC error on CPU0: 40(40)
>> [ 212.915533] APIC error on CPU0: 40(40)
>> [ 290.079923] APIC error on CPU0: 40(40)
>> [ 290.632507] APIC error on CPU0: 40(40)
>> [ 296.557068] APIC error on CPU0: 40(40)
>> [ 303.989147] APIC error on CPU0: 40(40)
>> [ 305.782793] APIC error on CPU0: 40(40)
>> [ 307.150566] APIC error on CPU0: 40(40)
>> [ 310.248346] APIC error on CPU0: 40(40)
>> [ 310.657006] APIC error on CPU0: 40(40)
>> [ 311.453595] APIC error on CPU0: 40(40)
>> [ 317.468024] APIC error on CPU0: 40(40)
>> [ 321.284080] APIC error on CPU0: 40(40)
>> [ 328.179853] APIC error on CPU0: 40(40)
>> [ 330.127038] APIC error on CPU0: 40(40)
>> [ 332.437435] APIC error on CPU0: 40(40)
>> [ 335.326931] APIC error on CPU0: 40(40)
>> [ 335.881538] APIC error on CPU0: 40(40)
>> [ 337.790227] APIC error on CPU0: 40(40)
>> [ 368.373446] APIC error on CPU0: 40(40)
>> [ 369.809138] APIC error on CPU0: 40(40)
>> [ 374.289855] APIC error on CPU0: 40(40)
>> [ 375.768238] APIC error on CPU0: 40(40)
>> [ 382.440748] APIC error on CPU0: 40(40)
>> [ 383.159443] APIC error on CPU0: 40(40)
>> [ 383.529522] APIC error on CPU0: 40(40)
>> [ 383.906913] APIC error on CPU0: 40(40)
>> [ 384.356990] APIC error on CPU0: 40(40)
>> [ 384.610941] APIC error on CPU0: 40(40)
>> [ 386.305185] APIC error on CPU0: 40(40)
>> [ 386.935949] APIC error on CPU0: 40(40)
>> [ 390.071741] APIC error on CPU0: 40(40)
>> [ 390.403979] APIC error on CPU0: 40(40)
>> [ 391.114519] APIC error on CPU0: 40(40)
>> [ 391.528138] APIC error on CPU0: 40(40)
>> [ 403.677688] APIC error on CPU0: 40(40)
>> [ 404.140181] APIC error on CPU0: 40(40)
>> [ 406.270920] APIC error on CPU0: 40(40)
>> [ 406.927867] APIC error on CPU0: 40(40)
>> [ 418.880757] APIC error on CPU0: 40(40)
>> [ 419.235211] APIC error on CPU0: 40(40)
>> [ 437.974455] APIC error on CPU0: 40(40)
>> [ 438.193878] APIC error on CPU0: 40(40)
>> [ 443.974790] APIC error on CPU0: 40(40)
>> [ 444.177027] APIC error on CPU0: 40(40)
>> [ 479.469645] APIC error on CPU0: 40(40)
>> [ 479.720979] APIC error on CPU0: 40(40)
>> [ 497.925734] APIC error on CPU0: 40(40)
>> [ 498.202985] APIC error on CPU0: 40(40)
>> [ 526.922424] APIC error on CPU0: 40(40)
>> [ 527.607409] APIC error on CPU0: 40(40)
>> [ 715.960235] APIC error on CPU0: 40(40)
>> [ 716.232556] APIC error on CPU0: 40(40)
>> [ 753.480442] APIC error on CPU0: 40(40)
>> [ 753.820830] APIC error on CPU0: 40(40)
>> [ 774.693756] APIC error on CPU0: 40(40)
>> [ 774.867494] APIC error on CPU0: 40(40)
>> [ 815.787137] APIC error on CPU0: 40(40)
>> [ 816.308363] APIC error on CPU0: 40(40)
>> [ 841.546917] APIC error on CPU0: 40(40)
>> [ 842.082173] APIC error on CPU0: 40(40)
>> [ 847.758887] ACPI: PCI interrupt for device 0000:06:00.0 disabled
>
> It looks the association is succeeded. But 5 minutes later it got an
> APIC error. Then I found this error is with lot of devices in your
> system. Not sure about what caused this. Can you please try disable MSI
> with boot param pci=nomsi?
>
> I don't understand why "disable_hw_scan=1" works for you. Can you also
> attach the dmesg for it?
>
> Thanks,
> -yi
>
Forgot to tell you that you can ignore the APIC error.
I tested and I know that this error happens always, when CPU fan speed
change, so I guess this is unrelated)
Best regards,
Maxim levitsky
next prev parent reply other threads:[~2008-06-12 12:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 15:07 [BUG] iwlwifi 3945 works only with disable_hw_scan=1 Maxim Levitsky
2008-06-12 3:28 ` Zhu Yi
2008-06-12 12:13 ` Maxim Levitsky [this message]
2008-06-12 13:59 ` [ipw3945-devel] " John W. Linville
2008-06-12 14:19 ` Maxim Levitsky
2008-06-12 20:25 ` Stephen Clark
2008-06-13 7:35 ` Zhu Yi
2008-06-13 8:48 ` Filippo Zangheri
2008-06-13 12:37 ` Tor Håkon Haugen
2008-06-13 13:03 ` John W. Linville
2008-06-13 14:59 ` Tor Håkon Haugen
2008-06-13 15:06 ` Maxim Levitsky
2008-06-13 15:09 ` Tor Håkon Haugen
2008-06-13 20:04 ` Tomas Winkler
2008-06-14 10:00 ` Maxim Levitsky
2008-06-14 16:50 ` Luis R. Rodriguez
2008-06-15 13:42 ` Maxim Levitsky
2008-06-15 13:47 ` Tomas Winkler
2008-06-15 14:12 ` Maxim Levitsky
2008-06-15 15:09 ` Tomas Winkler
2008-06-15 16:47 ` Tomas Winkler
2008-06-16 5:50 ` Maxim Levitsky
2008-06-16 5:52 ` Tomas Winkler
2008-06-16 6:08 ` Maxim Levitsky
2008-06-16 6:46 ` Maxim Levitsky
2008-06-16 7:11 ` Maxim Levitsky
2008-06-16 14:35 ` Dan Williams
2008-06-16 21:41 ` Tomas Winkler
2008-06-18 8:28 ` drago01
2008-06-24 19:47 ` John W. Linville
2008-06-24 20:32 ` Maxim Levitsky
2008-06-25 5:43 ` Tomas Winkler
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 15:47 Maxim Levitsky
2008-06-06 19:34 Maxim Levitsky
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=485112F4.7020207@gmail.com \
--to=maximlevitsky@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@intel.com \
/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).