All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	wireless <linux-wireless@vger.kernel.org>
Subject: iwlagn: Random "Time out reading EEPROM".
Date: Sat, 04 Jun 2011 15:14:41 +0200	[thread overview]
Message-ID: <4DEA2FC1.2030104@gmail.com> (raw)

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


WARNING: multiple messages have this Message-ID (diff)
From: "Nicolas de Pesloüan" <nicolas.2p.debian-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	wireless <linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: iwlagn: Random "Time out reading EEPROM".
Date: Sat, 04 Jun 2011 15:14:41 +0200	[thread overview]
Message-ID: <4DEA2FC1.2030104@gmail.com> (raw)

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

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2011-06-04 13:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04 13:14 Nicolas de Pesloüan [this message]
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
2011-07-15 14:28     ` wwguy
2011-07-15 14:28       ` wwguy
2011-08-25 13:50       ` Nicolas de Pesloüan
2011-08-25 13:50         ` Nicolas de Pesloüan
2011-08-25 13:37         ` Guy, Wey-Yi
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=4DEA2FC1.2030104@gmail.com \
    --to=nicolas.2p.debian@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.