* PROBLEM: Serial error
@ 2008-05-26 21:14 Noel (Sourceforge)
2008-05-26 22:36 ` Jiri Slaby
0 siblings, 1 reply; 7+ messages in thread
From: Noel (Sourceforge) @ 2008-05-26 21:14 UTC (permalink / raw)
To: linux-kernel
serial comms error with smsclient >2.6.25 , worked fine up until and
including 2.6.24.7
smsclient a command line client for sending sms's, worked fine for all
previous versions but as of 2.6.25, I get errors "waiting for ACK" this
has been confirmed as a kernel related error, smsmclient worked fine for
years, carrier (Telstra) has been very helpful with assisting in
debugging, confirms no change, error kernel related verified by rolling
back to kernel 2.6.24.7, as of 2.6.25 something in the serial comms area
was altered and broke smsclient ability to send SMS's, it will connect
but not login to send, with timeout waiting for ID, been working on this
for weeks and again its confirmed to some change in the kernel versions
mentioned. Only changes made were kernel upgrades.
Slackware 12.0, kernel from kernel.org, same .config file copied
through all upgrades, GCC version 4.1.2
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and
Memory
Controller Hub (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort+ >SERR- <PERR-
Latency: 0
Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [88] Vendor Specific Information
Capabilities: [a0] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=<none>
00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev
02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fda00000-feafffff
Prefetchable memory behind bridge: f3700000-f57fffff
Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR+
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02) (prog-if
00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fd900000-fd9fffff
Prefetchable memory behind bridge: f3600000-f36fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller
(rev 02) (prog-if 80 [Master])
Subsystem: Intel Corporation Unknown device 4541
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: [virtual] Memory at 000001f0 (32-bit,
non-prefetchable) [disabled] [size=8]
Region 1: [virtual] Memory at 000003f0 (type 3,
non-prefetchable) [disabled] [size=1]
Region 2: [virtual] Memory at 00000170 (32-bit,
non-prefetchable) [disabled] [size=8]
Region 3: [virtual] Memory at 00000370 (type 3,
non-prefetchable) [disabled] [size=1]
Region 4: I/O ports at ffa0 [size=16]
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1
(rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 4541
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin D routed to IRQ 10
Region 4: I/O ports at ef40 [size=32]
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 02)
Subsystem: Intel Corporation Unknown device 4541
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 6
Region 4: I/O ports at efa0 [size=16]
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1
(rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation Unknown device 4541
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin C routed to IRQ 9
Region 4: I/O ports at ef80 [size=32]
00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97
Audio Controller (rev 02)
Subsystem: Intel Corporation Unknown device 4541
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 6
Region 0: I/O ports at e800 [size=256]
Region 1: I/O ports at ef00 [size=64]
01:08.0 Ethernet controller: Intel Corporation 82801BA/BAM/CA/CAM
Ethernet Controller (rev 01)
Subsystem: Intel Corporation EtherExpress PRO/100 VE
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fd9fe000 (32-bit, non-prefetchable)
[size=4K]
Region 1: I/O ports at df00 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
01:0a.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
20)
Subsystem: Netgear FA310TX
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at d400 [size=256]
Region 1: Memory at fd9ff800 (32-bit, non-prefetchable)
[size=256]
Expansion ROM at f3600000 [disabled] [size=256K]
01:0c.0 Serial controller: PLX Technology, Inc. PCI <-> IOBus Bridge
(rev 01) (prog-if 00 [8250])
Subsystem: Stallion Technologies, Inc. Unknown device f010
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 6
Region 0: Memory at fd9ffc00 (32-bit, non-prefetchable)
[size=128]
Region 1: I/O ports at dc00 [size=128]
Region 2: I/O ports at d880 [size=128]
02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2164W
[Millennium II] AGP (prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc. Unknown device 1000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Region 0: Memory at fd9ffc00 (32-bit, non-prefetchable)
[size=128]
Region 1: I/O ports at dc00 [size=128]
Region 2: I/O ports at d880 [size=128]
02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2164W
[Millennium II] AGP (prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc. Unknown device 1000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 11
Region 0: Memory at f4000000 (32-bit, prefetchable) [size=16M]
Region 1: Memory at feafc000 (32-bit, non-prefetchable)
[size=16K]
Region 2: Memory at fe000000 (32-bit, non-prefetchable)
[size=8M]
Expansion ROM at feae0000 [disabled] [size=64K]
Capabilities: [f0] AGP version 1.0
Status: RQ=1 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64-
HTrans- 64bit- FW- AGP3- Rate=<none>
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=<none>
Stallion Multiport Serial Driver: version 5.6.0
Stallion Intelligent Multiport Serial Driver: version 5.6.0
0000:01:0c.0: ttyS4 at I/O 0xd880 (irq = 6) is a ST16654
0000:01:0c.0: ttyS5 at I/O 0xd888 (irq = 6) is a ST16654
0000:01:0c.0: ttyS6 at I/O 0xd890 (irq = 6) is a ST16654
0000:01:0c.0: ttyS7 at I/O 0xd898 (irq = 6) is a ST16654
0000:01:0c.0: ttyS8 at I/O 0xd8a0 (irq = 6) is a ST16654
0000:01:0c.0: ttyS9 at I/O 0xd8a8 (irq = 6) is a ST16654
0000:01:0c.0: ttyS10 at I/O 0xd8b0 (irq = 6) is a ST16654
0000:01:0c.0: ttyS11 at I/O 0xd8b8 (irq = 6) is a ST16654 <-- phone line
in this port
suggestions or assistance appreciated.
Noel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: PROBLEM: Serial error
2008-05-26 21:14 PROBLEM: Serial error Noel (Sourceforge)
@ 2008-05-26 22:36 ` Jiri Slaby
2008-05-27 13:30 ` Jiri Slaby
0 siblings, 1 reply; 7+ messages in thread
From: Jiri Slaby @ 2008-05-26 22:36 UTC (permalink / raw)
To: Noel (Sourceforge); +Cc: linux-kernel
On 05/26/2008 11:14 PM, Noel (Sourceforge) wrote:
> serial comms error with smsclient >2.6.25 , worked fine up until and
> including 2.6.24.7
[...]
> 01:0c.0 Serial controller: PLX Technology, Inc. PCI <-> IOBus Bridge
> (rev 01) (prog-if 00 [8250])
> Subsystem: Stallion Technologies, Inc. Unknown device f010
Do you have some patched driver or whatever, that this binds?
[...]
> Stallion Multiport Serial Driver: version 5.6.0
> Stallion Intelligent Multiport Serial Driver: version 5.6.0
> 0000:01:0c.0: ttyS4 at I/O 0xd880 (irq = 6) is a ST16654
> 0000:01:0c.0: ttyS5 at I/O 0xd888 (irq = 6) is a ST16654
> 0000:01:0c.0: ttyS6 at I/O 0xd890 (irq = 6) is a ST16654
> 0000:01:0c.0: ttyS7 at I/O 0xd898 (irq = 6) is a ST16654
> 0000:01:0c.0: ttyS8 at I/O 0xd8a0 (irq = 6) is a ST16654
> 0000:01:0c.0: ttyS9 at I/O 0xd8a8 (irq = 6) is a ST16654
> 0000:01:0c.0: ttyS10 at I/O 0xd8b0 (irq = 6) is a ST16654
> 0000:01:0c.0: ttyS11 at I/O 0xd8b8 (irq = 6) is a ST16654 <-- phone line
> in this port
>
>
> suggestions or assistance appreciated.
The only significant change is
ccfea3c98a10b9d4d49b899616a06594ec976d7d
could you try to revert it and re-test?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Serial error
2008-05-26 22:36 ` Jiri Slaby
@ 2008-05-27 13:30 ` Jiri Slaby
2008-05-27 13:33 ` Jiri Slaby
2008-05-27 13:41 ` Noel (Sourceforge)
0 siblings, 2 replies; 7+ messages in thread
From: Jiri Slaby @ 2008-05-27 13:30 UTC (permalink / raw)
To: Noel (Sourceforge); +Cc: linux-kernel, Alan Cox
Jiri Slaby napsal(a):
> On 05/26/2008 11:14 PM, Noel (Sourceforge) wrote:
>> serial comms error with smsclient >2.6.25 , worked fine up until and
>> including 2.6.24.7
There is >2.6.25. It means post 2.6.26-rc1 inclusively?
> [...]
>> 01:0c.0 Serial controller: PLX Technology, Inc. PCI <-> IOBus Bridge
>> (rev 01) (prog-if 00 [8250])
>> Subsystem: Stallion Technologies, Inc. Unknown device f010
>
> Do you have some patched driver or whatever, that this binds?
>
> [...]
>> Stallion Multiport Serial Driver: version 5.6.0
>> Stallion Intelligent Multiport Serial Driver: version 5.6.0
>> 0000:01:0c.0: ttyS4 at I/O 0xd880 (irq = 6) is a ST16654
>> 0000:01:0c.0: ttyS5 at I/O 0xd888 (irq = 6) is a ST16654
>> 0000:01:0c.0: ttyS6 at I/O 0xd890 (irq = 6) is a ST16654
>> 0000:01:0c.0: ttyS7 at I/O 0xd898 (irq = 6) is a ST16654
>> 0000:01:0c.0: ttyS8 at I/O 0xd8a0 (irq = 6) is a ST16654
>> 0000:01:0c.0: ttyS9 at I/O 0xd8a8 (irq = 6) is a ST16654
>> 0000:01:0c.0: ttyS10 at I/O 0xd8b0 (irq = 6) is a ST16654
>> 0000:01:0c.0: ttyS11 at I/O 0xd8b8 (irq = 6) is a ST16654 <-- phone line
>> in this port
>>
>>
>> suggestions or assistance appreciated.
>
> The only significant change is
> ccfea3c98a10b9d4d49b899616a06594ec976d7d
> could you try to revert it and re-test?
> Thanks
> Reverted, but problem remains.
If you double checked this, trying to CC Alan if he doesn't have a clue.
For reference:
http://lkml.org/lkml/2008/5/26/260
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Serial error
2008-05-27 13:30 ` Jiri Slaby
@ 2008-05-27 13:33 ` Jiri Slaby
2008-05-27 13:42 ` Noel (Sourceforge)
2008-05-27 13:41 ` Noel (Sourceforge)
1 sibling, 1 reply; 7+ messages in thread
From: Jiri Slaby @ 2008-05-27 13:33 UTC (permalink / raw)
To: Noel (Sourceforge); +Cc: linux-kernel, Alan Cox
Jiri Slaby napsal(a):
>>> 01:0c.0 Serial controller: PLX Technology, Inc. PCI <-> IOBus Bridge
>>> (rev 01) (prog-if 00 [8250])
>>> Subsystem: Stallion Technologies, Inc. Unknown device f010
>>
>> Do you have some patched driver or whatever, that this binds?
And please post
lspci -vvxxs 01:0c.0
I didn't get how this binds to *stallion drivers.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Serial error
2008-05-27 13:33 ` Jiri Slaby
@ 2008-05-27 13:42 ` Noel (Sourceforge)
0 siblings, 0 replies; 7+ messages in thread
From: Noel (Sourceforge) @ 2008-05-27 13:42 UTC (permalink / raw)
To: Jiri Slaby; +Cc: linux-kernel, Alan Cox
On Tue, 2008-05-27 at 23:33, Jiri Slaby wrote:
> Jiri Slaby napsal(a):
> >>> 01:0c.0 Serial controller: PLX Technology, Inc. PCI <-> IOBus Bridge
> >>> (rev 01) (prog-if 00 [8250])
> >>> Subsystem: Stallion Technologies, Inc. Unknown device f010
> >>
> >> Do you have some patched driver or whatever, that this binds?
>
> And please post
> lspci -vvxxs 01:0c.0
>
> I didn't get how this binds to *stallion drivers.
lspci -vvxxs 01:0c.0
01:0c.0 Serial controller: PLX Technology, Inc. PCI <-> IOBus Bridge
(rev 01) (prog-if 00 [8250])
Subsystem: Stallion Technologies, Inc. Unknown device f010
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 6
Region 0: Memory at fd9ffc00 (32-bit, non-prefetchable)
[size=128]
Region 1: I/O ports at dc00 [size=128]
Region 2: I/O ports at d880 [size=128]
00: b5 10 50 90 03 01 80 02 01 00 00 07 08 00 00 00
10: 00 fc 9f fd 01 dc 00 00 81 d8 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 4d 12 10 f0
30: 00 00 00 00 00 00 00 00 00 00 00 00 06 01 00 00
Thanks
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Serial error
2008-05-27 13:30 ` Jiri Slaby
2008-05-27 13:33 ` Jiri Slaby
@ 2008-05-27 13:41 ` Noel (Sourceforge)
2008-05-27 14:14 ` Jiri Slaby
1 sibling, 1 reply; 7+ messages in thread
From: Noel (Sourceforge) @ 2008-05-27 13:41 UTC (permalink / raw)
To: Jiri Slaby; +Cc: linux-kernel, Alan Cox
On Tue, 2008-05-27 at 23:30, Jiri Slaby wrote:
> Jiri Slaby napsal(a):
> > On 05/26/2008 11:14 PM, Noel (Sourceforge) wrote:
> >> serial comms error with smsclient >2.6.25 , worked fine up until and
> >> including 2.6.24.7
>
> There is >2.6.25. It means post 2.6.26-rc1 inclusively?
>
Yes, it broke as of 2.6.25 , I also obtained .1 through .4 and still
broken in each, I have not tried 2.6.26-rc1 as I assume the code
breaking this is still in the tree
>
> If you double checked this, trying to CC Alan if he doesn't have a clue.
> For reference:
> http://lkml.org/lkml/2008/5/26/260
Yes, checked.
Thanks
Noel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Serial error
2008-05-27 13:41 ` Noel (Sourceforge)
@ 2008-05-27 14:14 ` Jiri Slaby
0 siblings, 0 replies; 7+ messages in thread
From: Jiri Slaby @ 2008-05-27 14:14 UTC (permalink / raw)
To: Noel (Sourceforge); +Cc: linux-kernel, Alan Cox, linux-serial
Noel (Sourceforge) napsal(a):
> On Tue, 2008-05-27 at 23:30, Jiri Slaby wrote:
>> Jiri Slaby napsal(a):
>>> On 05/26/2008 11:14 PM, Noel (Sourceforge) wrote:
>>>> serial comms error with smsclient >2.6.25 , worked fine up until and
>>>> including 2.6.24.7
>> There is >2.6.25. It means post 2.6.26-rc1 inclusively?
>>
>
> Yes, it broke as of 2.6.25 , I also obtained .1 through .4 and still
> broken in each, I have not tried 2.6.26-rc1 as I assume the code
> breaking this is still in the tree
>
>
>
>> If you double checked this, trying to CC Alan if he doesn't have a clue.
>> For reference:
>> http://lkml.org/lkml/2008/5/26/260
>
> Yes, checked.
Ah, this one goes through platform driver (why do you load istallion and
stallion drivers?).
8250.c driver changes:
Alan Cox (3):
serial: Coding style
serial8250: coding style
8250: enable rate reporting via termios
Will Newton (1):
8250.c: support specifying DW APB UARTs in device platform_data
Nothing seems intrusive, but whatever changes in the rest of the serial
might have caused it. Could you bisect it? I think it would be fast.
git-bisect v2.6.25 v2.6.24 -- drivers/char/ drivers/serial/
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2008-05-27 14:14 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-26 21:14 PROBLEM: Serial error Noel (Sourceforge)
2008-05-26 22:36 ` Jiri Slaby
2008-05-27 13:30 ` Jiri Slaby
2008-05-27 13:33 ` Jiri Slaby
2008-05-27 13:42 ` Noel (Sourceforge)
2008-05-27 13:41 ` Noel (Sourceforge)
2008-05-27 14:14 ` Jiri Slaby
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.