From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: wwguy <wey-yi.w.guy@intel.com>, dhalperi@cs.washington.edu
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: Random "Time out reading EEPROM".
Date: Fri, 15 Jul 2011 10:22:16 +0200 [thread overview]
Message-ID: <4E1FF8B8.9020005@gmail.com> (raw)
In-Reply-To: <1307284276.6918.17.camel@wwguy-ubuntu>
Le 05/06/2011 16:31, wwguy a écrit :
> On Sat, 2011-06-04 at 06:14 -0700, Nicolas de Pesloüan wrote:
>> Hi,
>>
>> From time to time, my Intel Wifi adapter fail on cold boot, with the following in dmesg:
>>
>> [ 7.442634] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
>> [ 7.442636] iwlagn: Copyright(c) 2003-2009 Intel Corporation
>> [ 7.442701] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
>> [ 7.442708] iwlagn 0000:05:00.0: setting latency timer to 64
>> [ 7.442788] iwlagn 0000:05:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54
>> [ 7.455547] iwlagn 0000:05:00.0: Time out reading EEPROM[0]
>> [ 7.455611] iwlagn 0000:05:00.0: Unable to init EEPROM
>> [ 7.455678] iwlagn 0000:05:00.0: PCI INT A disabled
>> [ 7.455685] iwlagn: probe of 0000:05:00.0 failed with error -110
>>
>> After "modprobe -r iwlagn ; modprobe iwlagn" or after a reboot, everything work fine:
>>
>> [ 346.332166] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
>> [ 346.332169] iwlagn: Copyright(c) 2003-2009 Intel Corporation
>> [ 346.332225] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
>> [ 346.332234] iwlagn 0000:05:00.0: setting latency timer to 64
>> [ 346.332277] iwlagn 0000:05:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54
>> [ 346.365739] iwlagn 0000:05:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
>> [ 346.365787] alloc irq_desc for 33 on node -1
>> [ 346.365788] alloc kstat_irqs on node -1
>> [ 346.365804] iwlagn 0000:05:00.0: irq 33 for MSI/MSI-X
>> [ 346.449989] phy0: Selected rate control algorithm 'iwl-agn-rs'
>>
>> This happens using 2.6.32-5 from Debian. I didn't had the opportunity to reproduce it using recent
>> kernel, but it occurs too rarely to conclude anything.
>>
>> I had a look at the git log, without finding something that seems related to this problem. Does this
>> ring a bell for someone?
>>
>> Nicolas.
>>
>> 05:00.0 Network controller: Intel Corporation WiFi Link 5100
>> Subsystem: Intel Corporation WiFi Link 5100 AGN
>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
>> FastB2B- DisINTx-
>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast>TAbort-<TAbort-<MAbort->SERR-
>> <PERR- INTx-
>> Latency: 0, Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 33
>> Region 0: Memory at d6d00000 (64-bit, non-prefetchable) [size=8K]
>> Capabilities: [c8] Power Management version 3
>> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>> Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>> Address: 00000000fee0300c Data: 41c9
>> Capabilities: [e0] Express (v1) Endpoint, MSI 00
>> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s<512ns, L1 unlimited
>> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
>> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
>> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
>> MaxPayload 128 bytes, MaxReadReq 128 bytes
>> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
>> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0<128ns, L1<32us
>> ClockPM+ Surprise- LLActRep- BwNot-
>> LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
>> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
>> Capabilities: [100 v1] Advanced Error Reporting
>> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC-
>> UnsupReq- ACSViol-
>> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC-
>> UnsupReq- ACSViol-
>> UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC-
>> UnsupReq- ACSViol-
>> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
>> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
>> AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
>> Capabilities: [140 v1] Device Serial Number 00-22-fb-ff-ff-28-46-c8
>> Kernel driver in use: iwlagn
>>
>
> no sure, you are the ONLY one report this issue, since the device works
> after you reload the module, the HW/SW is ok. maybe the timing/sequence
> have problem on the kernel you are using on your system. The bus is not
> ready when you boot the system and access the EEPROM.
>
> What model of the laptop you have? could you try to upgrade to newer
> kernel?
This problem also happens using 2.6.39-2-amd64 from Debian.
[ 8.507426] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 8.507429] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[ 8.507521] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 8.507529] iwlagn 0000:05:00.0: setting latency timer to 64
[ 8.507556] iwlagn 0000:05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
[ 8.516687] iwlagn 0000:05:00.0: Time out reading EEPROM[2]
[ 8.516724] iwlagn 0000:05:00.0: Unable to init EEPROM
[ 8.516739] iwlagn 0000:05:00.0: PCI INT A disabled
[ 8.516745] iwlagn: probe of 0000:05:00.0 failed with error -110
modprobe -r iwlagn ; modprobe iwlagn
[ 208.948664] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 208.948666] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[ 208.948743] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 208.948753] iwlagn 0000:05:00.0: setting latency timer to 64
[ 208.948817] iwlagn 0000:05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
[ 208.969659] iwlagn 0000:05:00.0: device EEPROM VER=0x11f, CALIB=0x4
[ 208.969661] iwlagn 0000:05:00.0: Device SKU: 0Xb
[ 208.969701] iwlagn 0000:05:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[ 208.969766] iwlagn 0000:05:00.0: irq 50 for MSI/MSI-X
[ 209.048366] iwlagn 0000:05:00.0: loaded firmware version 8.83.5.1 build 33692
Because it happens not very often, I still didn't had the opportunity to reproduce it with up to
date kernel.
The laptop is a two years old Sony Vaio VGN-AW21M.
Nicolas.
next prev parent reply other threads:[~2011-07-15 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 13:14 iwlagn: Random "Time out reading EEPROM" Nicolas de Pesloüan
2011-06-05 14:31 ` wwguy
2011-07-15 8:22 ` Nicolas de Pesloüan [this message]
[not found] ` <4E1FF8B8.9020005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-07-15 14:28 ` wwguy
2011-08-25 13:50 ` Nicolas de Pesloüan
[not found] ` <4E565333.3080007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-08-25 13:37 ` Guy, Wey-Yi
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=4E1FF8B8.9020005@gmail.com \
--to=nicolas.2p.debian@gmail.com \
--cc=dhalperi@cs.washington.edu \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wey-yi.w.guy@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).