iwlagn: Random "Time out reading EEPROM".

netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* iwlagn: Random "Time out reading EEPROM".
@ 2011-06-04 13:14 Nicolas de Pesloüan
  2011-06-05 14:31 ` wwguy
  0 siblings, 1 reply; 6+ messages in thread
From: Nicolas de Pesloüan @ 2011-06-04 13:14 UTC (permalink / raw)
  To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, wireless

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iwlagn: Random "Time out reading EEPROM".
  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
  0 siblings, 1 reply; 6+ messages in thread
From: wwguy @ 2011-06-05 14:31 UTC (permalink / raw)
  To: Nicolas de Pesloüan; +Cc: netdev@vger.kernel.org, wireless

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?
 

Wey


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iwlagn: Random "Time out reading EEPROM".
  2011-06-05 14:31 ` wwguy
@ 2011-07-15  8:22   ` Nicolas de Pesloüan
       [not found]     ` <4E1FF8B8.9020005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
  0 siblings, 1 reply; 6+ messages in thread
From: Nicolas de Pesloüan @ 2011-07-15  8:22 UTC (permalink / raw)
  To: wwguy, dhalperi; +Cc: netdev@vger.kernel.org, wireless

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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

[parent not found: <4E1FF8B8.9020005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

* Re: iwlagn: Random "Time out reading EEPROM".
       [not found]     ` <4E1FF8B8.9020005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
@ 2011-07-15 14:28       ` wwguy
  2011-08-25 13:50         ` Nicolas de Pesloüan
  0 siblings, 1 reply; 6+ messages in thread
From: wwguy @ 2011-07-15 14:28 UTC (permalink / raw)
  To: Nicolas de Pesloüan
  Cc: dhalperi-GmWTxIRN22iJaUV4rX00uodd74u8MsAO@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, wireless,
	wey-yi.w.guy-ral2JQCrhuEAvxtiuMwx3w

On Fri, 2011-07-15 at 01:22 -0700, Nicolas de Pesloüan wrote:
> 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.
> 
the error indicate fail to read data from EEPROM, your 2nd report is
even more strange, the number at the end the error message indicate the
index of DWORD driver trying to read from EEPROM. 

"Time out reading EEPROM[2]" telling me the first 2 DWORD is reading ok
but not the 3rd read.

How many PCI-E slots you have in your system, could it possible for you
to switch to another PCI-E slot, or pull out and re-insert the NIC.

Also, it is possible to put the NIC into different system and see if you
are seeing the similar problem?

Thanks
Wey


--
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iwlagn: Random "Time out reading EEPROM".
  2011-07-15 14:28       ` wwguy
@ 2011-08-25 13:50         ` Nicolas de Pesloüan
       [not found]           ` <4E565333.3080007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
  0 siblings, 1 reply; 6+ messages in thread
From: Nicolas de Pesloüan @ 2011-08-25 13:50 UTC (permalink / raw)
  To: wwguy
  Cc: dhalperi-GmWTxIRN22iJaUV4rX00uodd74u8MsAO@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, wireless

Le 15/07/2011 16:28, wwguy a écrit :

> the error indicate fail to read data from EEPROM, your 2nd report is
> even more strange, the number at the end the error message indicate the
> index of DWORD driver trying to read from EEPROM.
>
> "Time out reading EEPROM[2]" telling me the first 2 DWORD is reading ok
> but not the 3rd read.
>
> How many PCI-E slots you have in your system, could it possible for you
> to switch to another PCI-E slot, or pull out and re-insert the NIC.

Unfortunately, not. On this laptop, the NIC is not reachable without disassembling the laptop, and I 
don't want to... I will double check again, but...

> Also, it is possible to put the NIC into different system and see if you
> are seeing the similar problem?

No, for the exact same reason.

Not that it still happens with 3.0.0-1 from Debian.

[   15.086244] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[   15.086247] iwlagn: Copyright(c) 2003-2011 Intel Corporation
[   15.086404] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   15.086412] iwlagn 0000:05:00.0: setting latency timer to 64
[   15.086438] iwlagn 0000:05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
[   15.095859] iwlagn 0000:05:00.0: Time out reading EEPROM[6]
[   15.095945] iwlagn 0000:05:00.0: Unable to init EEPROM
[   15.096030] iwlagn 0000:05:00.0: PCI INT A disabled
[   15.096039] iwlagn: probe of 0000:05:00.0 failed with error -110

modprobe -r iwlagn ; modprobe iwlagn

[  231.822492] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[  231.822495] iwlagn: Copyright(c) 2003-2011 Intel Corporation
[  231.822581] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[  231.822591] iwlagn 0000:05:00.0: setting latency timer to 64
[  231.822621] iwlagn 0000:05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
[  231.843544] iwlagn 0000:05:00.0: device EEPROM VER=0x11f, CALIB=0x4
[  231.843546] iwlagn 0000:05:00.0: Device SKU: 0Xb
[  231.844889] iwlagn 0000:05:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[  231.844961] iwlagn 0000:05:00.0: irq 50 for MSI/MSI-X
[  231.989424] iwlagn 0000:05:00.0: loaded firmware version 8.83.5.1 build 33692
[  232.037456] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'

The error is not easy to reproduce, but the fix is perfectly stable. A single unload/reload of 
iwlagn is always enough to solve the problem, when it happens. For this reason, it sounds difficult 
to consider this a hardware slot problem. Can't this be related to some other PCI components?

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation G98 [GeForce 9300M GS] (rev a1)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller 
(rev 14)
05:00.0 Network controller: Intel Corporation WiFi Link 5100
09:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
09:03.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
09:03.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)

I'm quite sure I can fix this problem by loading, unloading and reloading iwlagn on every startup... 
but I don't really consider this a fix :-/

	Nicolas.
--
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

[parent not found: <4E565333.3080007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

* Re: iwlagn: Random "Time out reading EEPROM".
       [not found]           ` <4E565333.3080007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
@ 2011-08-25 13:37             ` Guy, Wey-Yi
  0 siblings, 0 replies; 6+ messages in thread
From: Guy, Wey-Yi @ 2011-08-25 13:37 UTC (permalink / raw)
  To: Nicolas de Pesloüan
  Cc: dhalperi-GmWTxIRN22iJaUV4rX00uodd74u8MsAO@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, wireless

On Thu, 2011-08-25 at 06:50 -0700, Nicolas de Pesloüan wrote:
> Le 15/07/2011 16:28, wwguy a écrit :
> 
> > the error indicate fail to read data from EEPROM, your 2nd report is
> > even more strange, the number at the end the error message indicate the
> > index of DWORD driver trying to read from EEPROM.
> >
> > "Time out reading EEPROM[2]" telling me the first 2 DWORD is reading ok
> > but not the 3rd read.
> >
> > How many PCI-E slots you have in your system, could it possible for you
> > to switch to another PCI-E slot, or pull out and re-insert the NIC.
> 
> Unfortunately, not. On this laptop, the NIC is not reachable without disassembling the laptop, and I 
> don't want to... I will double check again, but...
> 
> > Also, it is possible to put the NIC into different system and see if you
> > are seeing the similar problem?
> 
> No, for the exact same reason.
> 
> Not that it still happens with 3.0.0-1 from Debian.
> 
> [   15.086244] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
> [   15.086247] iwlagn: Copyright(c) 2003-2011 Intel Corporation
> [   15.086404] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [   15.086412] iwlagn 0000:05:00.0: setting latency timer to 64
> [   15.086438] iwlagn 0000:05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
> [   15.095859] iwlagn 0000:05:00.0: Time out reading EEPROM[6]
> [   15.095945] iwlagn 0000:05:00.0: Unable to init EEPROM
> [   15.096030] iwlagn 0000:05:00.0: PCI INT A disabled
> [   15.096039] iwlagn: probe of 0000:05:00.0 failed with error -110
> 
> modprobe -r iwlagn ; modprobe iwlagn
> 
> [  231.822492] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
> [  231.822495] iwlagn: Copyright(c) 2003-2011 Intel Corporation
> [  231.822581] iwlagn 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [  231.822591] iwlagn 0000:05:00.0: setting latency timer to 64
> [  231.822621] iwlagn 0000:05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
> [  231.843544] iwlagn 0000:05:00.0: device EEPROM VER=0x11f, CALIB=0x4
> [  231.843546] iwlagn 0000:05:00.0: Device SKU: 0Xb
> [  231.844889] iwlagn 0000:05:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
> [  231.844961] iwlagn 0000:05:00.0: irq 50 for MSI/MSI-X
> [  231.989424] iwlagn 0000:05:00.0: loaded firmware version 8.83.5.1 build 33692
> [  232.037456] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
> 
> The error is not easy to reproduce, but the fix is perfectly stable. A single unload/reload of 
> iwlagn is always enough to solve the problem, when it happens. For this reason, it sounds difficult 
> to consider this a hardware slot problem. Can't this be related to some other PCI components?
> 
> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
> 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
> 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
> 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
> 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
> 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
> 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
> 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
> 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
> 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
> 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
> 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
> 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
> 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
> 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
> 01:00.0 VGA compatible controller: nVidia Corporation G98 [GeForce 9300M GS] (rev a1)
> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller 
> (rev 14)
> 05:00.0 Network controller: Intel Corporation WiFi Link 5100
> 09:03.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
> 09:03.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
> 09:03.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
> 
> I'm quite sure I can fix this problem by loading, unloading and reloading iwlagn on every startup... 
> but I don't really consider this a fix :

not sure how to help since it is not easy to re-produce and it is EEPROM
reading problem, I only can guess it might related to the physical
device.

Thanks
Wey


--
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-08-25 13:50 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
     [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

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).