* [Xenomai-help] I-pipe: Detected illicit call from domain 'Xenomai'
@ 2007-08-17 11:09 Yeoh Chun Yeow
2007-08-17 12:07 ` Gilles Chanteperdrix
0 siblings, 1 reply; 5+ messages in thread
From: Yeoh Chun Yeow @ 2007-08-17 11:09 UTC (permalink / raw)
To: Xenomai-help@domain.hid
[-- Attachment #1: Type: text/plain, Size: 2893 bytes --]
Dear all,
I have encounter the following problem when migrating a Linux driver to RTDM
driver:
I-pipe: Detected illicit call from domain 'Xenomai'
into a service reserved for domain 'Linux' and below.
[<c002a474>] (show_stack+0x0/0x58) from [<c00736a4>]
(ipipe_check_context+0x98/0xe4)
[<c007360c>] (ipipe_check_context+0x0/0xe4) from [<c00d4ca4>]
(cache_alloc_refill+0x7c/0x78c)
r8 = 00000020 r7 = C04A3360 r6 = 00000000 r5 = 0000001B
r4 = 00000000
[<c00d4c28>] (cache_alloc_refill+0x0/0x78c) from [<c00d54dc>]
(__kmalloc+0x128/0x138)
[<c00d53b4>] (__kmalloc+0x0/0x138) from [<c027ede8>] (__alloc_skb+0x58/0xf8)
r8 = 00000000 r7 = C04A8B00 r6 = 00000060 r5 = 00000020
r4 = C065C940
[<c027ed90>] (__alloc_skb+0x0/0xf8) from [<c0222b94>]
(at91ether_interrupt+0x250/0x350)
r8 = FFC00000 r7 = C0768A60 r6 = C0768B20 r5 = 00000046
r4 = C03E4C60
<snip>
| # end 0x80000000 -44 __ipipe_unstall_root+0x4c
(__ipipe_restore_root+0x70)
| # *func -50 __ipipe_unstall_root+0x10
(__ipipe_restore_root+0x70)
| # *func -56 __ipipe_restore_root+0x10
(kmem_cache_alloc+0x84)
| # *func -63 debug_smp_processor_id+0x10
(kmem_cache_alloc+0x50)
| # *end 0x80000001 -70 kmem_cache_alloc+0xd8 (__alloc_skb+0x3c)
| # begin 0x80000001 -76 kmem_cache_alloc+0xc4 (__alloc_skb+0x3c)
| # func -83 kmem_cache_alloc+0x14 (__alloc_skb+0x3c)
| # func -91 __alloc_skb+0x14 (at91ether_interrupt+0x250)
| # func -100 at91ether_interrupt+0x14
(xnintr_irq_handler+0x48)
| # func -107 xnintr_irq_handler+0x14
(__ipipe_dispatch_wired+0xf8)
| +func -113 __ipipe_dispatch_wired+0x14
(__ipipe_handle_irq+0x1b0)
| +func -119 at91_aic_mask_irq+0x10
(__ipipe_ack_level_irq+0x4c)
| +func -125 at91_aic_mask_irq+0x10
(__ipipe_ack_level_irq+0x3c)
| +func -130 __ipipe_ack_level_irq+0x10
(__ipipe_ack_irq+0x24)
| +func -137 __ipipe_ack_irq+0x10
(__ipipe_handle_irq+0x1a4)
| +func -143 __ipipe_handle_irq+0x14
(__ipipe_grab_irq+0xa0)
| +begin 0xffffffff -150 __ipipe_grab_irq+0x34 (__irq_svc+0x30)
| +func -156 __ipipe_grab_irq+0x14 (__irq_svc+0x30)
| +end 0x80000000 -164 __ipipe_unstall_root+0x4c
(__do_softirq+0x4c)
| #begin 0x80000000 -171 __ipipe_unstall_root+0x70
(__do_softirq+0x4c)
#func -177 __ipipe_unstall_root+0x10
(__do_softirq+0x4c)
#func -183 debug_smp_processor_id+0x10
(__do_softirq+0x38)
#func -190 debug_smp_processor_id+0x10
(__do_softirq+0x30)
#func -196 add_preempt_count+0x10 (__do_softirq+0x2c)
Is this the problem coming from the alloc_skb function call? {
Please advice. Thanks
Regards,
Chun Yeow
[-- Attachment #2: Type: text/html, Size: 5195 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Xenomai-help] I-pipe: Detected illicit call from domain 'Xenomai'
2007-08-17 11:09 [Xenomai-help] I-pipe: Detected illicit call from domain 'Xenomai' Yeoh Chun Yeow
@ 2007-08-17 12:07 ` Gilles Chanteperdrix
2007-08-17 12:45 ` Jan Kiszka
0 siblings, 1 reply; 5+ messages in thread
From: Gilles Chanteperdrix @ 2007-08-17 12:07 UTC (permalink / raw)
To: Yeoh Chun Yeow; +Cc: Xenomai-help@domain.hid
On 8/17/07, Yeoh Chun Yeow <yeohchunyeow@domain.hid> wrote:
> Dear all,
>
> I have encounter the following problem when migrating a Linux driver to RTDM
> driver:
>
> I-pipe: Detected illicit call from domain 'Xenomai'
> into a service reserved for domain 'Linux' and below.
> [<c002a474>] (show_stack+0x0/0x58) from [<c00736a4>]
> (ipipe_check_context+0x98/0xe4)
> [<c007360c>] (ipipe_check_context+0x0/0xe4) from [<c00d4ca4>]
> (cache_alloc_refill+0x7c/0x78c)
> r8 = 00000020 r7 = C04A3360 r6 = 00000000 r5 = 0000001B
> r4 = 00000000
> [<c00d4c28>] (cache_alloc_refill+0x0/0x78c) from [<c00d54dc>]
> (__kmalloc+0x128/0x138)
> [<c00d53b4>] (__kmalloc+0x0/0x138) from [<c027ede8>] (__alloc_skb+0x58/0xf8)
> r8 = 00000000 r7 = C04A8B00 r6 = 00000060 r5 = 00000020
> r4 = C065C940
> [<c027ed90>] (__alloc_skb+0x0/0xf8) from [<c0222b94>]
> (at91ether_interrupt+0x250/0x350)
> r8 = FFC00000 r7 = C0768A60 r6 = C0768B20 r5 = 00000046
> r4 = C03E4C60
>
> <snip>
>
> | # end 0x80000000 -44 __ipipe_unstall_root+0x4c
> (__ipipe_restore_root+0x70)
> | # *func -50 __ipipe_unstall_root+0x10
> (__ipipe_restore_root+0x70)
> | # *func -56 __ipipe_restore_root+0x10
> (kmem_cache_alloc+0x84)
> | # *func -63 debug_smp_processor_id+0x10
> (kmem_cache_alloc+0x50)
> | # *end 0x80000001 -70 kmem_cache_alloc+0xd8 (__alloc_skb+0x3c)
> | # begin 0x80000001 -76 kmem_cache_alloc+0xc4 (__alloc_skb+0x3c)
> | # func -83 kmem_cache_alloc+0x14 (__alloc_skb+0x3c)
> | # func -91 __alloc_skb+0x14 (at91ether_interrupt+0x250)
> | # func -100 at91ether_interrupt+0x14
> (xnintr_irq_handler+0x48)
> | # func -107 xnintr_irq_handler+0x14
> (__ipipe_dispatch_wired+0xf8)
> | +func -113 __ipipe_dispatch_wired+0x14
> (__ipipe_handle_irq+0x1b0)
> | +func -119 at91_aic_mask_irq+0x10
> (__ipipe_ack_level_irq+0x4c)
> | +func -125 at91_aic_mask_irq+0x10
> (__ipipe_ack_level_irq+0x3c)
> | +func -130 __ipipe_ack_level_irq+0x10
> (__ipipe_ack_irq+0x24)
> | +func -137 __ipipe_ack_irq+0x10
> (__ipipe_handle_irq+0x1a4)
> | +func -143 __ipipe_handle_irq+0x14
> (__ipipe_grab_irq+0xa0)
> | +begin 0xffffffff -150 __ipipe_grab_irq+0x34 (__irq_svc+0x30)
> | +func -156 __ipipe_grab_irq+0x14 (__irq_svc+0x30)
> | +end 0x80000000 -164 __ipipe_unstall_root+0x4c
> (__do_softirq+0x4c)
> | #begin 0x80000000 -171 __ipipe_unstall_root+0x70
> (__do_softirq+0x4c)
> #func -177 __ipipe_unstall_root+0x10
> (__do_softirq+0x4c)
> #func -183 debug_smp_processor_id+0x10
> (__do_softirq+0x38)
> #func -190 debug_smp_processor_id+0x10
> (__do_softirq+0x30)
> #func -196 add_preempt_count+0x10 (__do_softirq+0x2c)
>
> Is this the problem coming from the alloc_skb function call? {
Yes, you can not call alloc_skb from Xenomai domain, as you can not
call most Linux functions. Note that if you are porting a network
driver, you should consider using rtnet.
--
Gilles Chanteperdrix
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Xenomai-help] I-pipe: Detected illicit call from domain 'Xenomai'
2007-08-17 12:07 ` Gilles Chanteperdrix
@ 2007-08-17 12:45 ` Jan Kiszka
2007-08-23 8:00 ` Yeoh Chun Yeow
0 siblings, 1 reply; 5+ messages in thread
From: Jan Kiszka @ 2007-08-17 12:45 UTC (permalink / raw)
To: Gilles Chanteperdrix, Yeoh Chun Yeow; +Cc: Xenomai-help@domain.hid
[-- Attachment #1: Type: text/plain, Size: 3966 bytes --]
Gilles Chanteperdrix wrote:
> On 8/17/07, Yeoh Chun Yeow <yeohchunyeow@domain.hid> wrote:
>> Dear all,
>>
>> I have encounter the following problem when migrating a Linux driver to RTDM
>> driver:
>>
>> I-pipe: Detected illicit call from domain 'Xenomai'
>> into a service reserved for domain 'Linux' and below.
[Nice example for how to validate new RTDM drivers or Xenomai skins
against accidental Linux calls! => CONFIG_IPIPE_DEBUG_CONTEXT]
>> [<c002a474>] (show_stack+0x0/0x58) from [<c00736a4>]
>> (ipipe_check_context+0x98/0xe4)
>> [<c007360c>] (ipipe_check_context+0x0/0xe4) from [<c00d4ca4>]
>> (cache_alloc_refill+0x7c/0x78c)
>> r8 = 00000020 r7 = C04A3360 r6 = 00000000 r5 = 0000001B
>> r4 = 00000000
>> [<c00d4c28>] (cache_alloc_refill+0x0/0x78c) from [<c00d54dc>]
>> (__kmalloc+0x128/0x138)
>> [<c00d53b4>] (__kmalloc+0x0/0x138) from [<c027ede8>] (__alloc_skb+0x58/0xf8)
>> r8 = 00000000 r7 = C04A8B00 r6 = 00000060 r5 = 00000020
>> r4 = C065C940
>> [<c027ed90>] (__alloc_skb+0x0/0xf8) from [<c0222b94>]
>> (at91ether_interrupt+0x250/0x350)
>> r8 = FFC00000 r7 = C0768A60 r6 = C0768B20 r5 = 00000046
>> r4 = C03E4C60
>>
>> <snip>
>>
>> | # end 0x80000000 -44 __ipipe_unstall_root+0x4c
>> (__ipipe_restore_root+0x70)
>> | # *func -50 __ipipe_unstall_root+0x10
>> (__ipipe_restore_root+0x70)
>> | # *func -56 __ipipe_restore_root+0x10
>> (kmem_cache_alloc+0x84)
>> | # *func -63 debug_smp_processor_id+0x10
>> (kmem_cache_alloc+0x50)
>> | # *end 0x80000001 -70 kmem_cache_alloc+0xd8 (__alloc_skb+0x3c)
>> | # begin 0x80000001 -76 kmem_cache_alloc+0xc4 (__alloc_skb+0x3c)
>> | # func -83 kmem_cache_alloc+0x14 (__alloc_skb+0x3c)
>> | # func -91 __alloc_skb+0x14 (at91ether_interrupt+0x250)
>> | # func -100 at91ether_interrupt+0x14
>> (xnintr_irq_handler+0x48)
>> | # func -107 xnintr_irq_handler+0x14
>> (__ipipe_dispatch_wired+0xf8)
>> | +func -113 __ipipe_dispatch_wired+0x14
>> (__ipipe_handle_irq+0x1b0)
>> | +func -119 at91_aic_mask_irq+0x10
>> (__ipipe_ack_level_irq+0x4c)
>> | +func -125 at91_aic_mask_irq+0x10
>> (__ipipe_ack_level_irq+0x3c)
>> | +func -130 __ipipe_ack_level_irq+0x10
>> (__ipipe_ack_irq+0x24)
>> | +func -137 __ipipe_ack_irq+0x10
>> (__ipipe_handle_irq+0x1a4)
>> | +func -143 __ipipe_handle_irq+0x14
>> (__ipipe_grab_irq+0xa0)
>> | +begin 0xffffffff -150 __ipipe_grab_irq+0x34 (__irq_svc+0x30)
>> | +func -156 __ipipe_grab_irq+0x14 (__irq_svc+0x30)
>> | +end 0x80000000 -164 __ipipe_unstall_root+0x4c
>> (__do_softirq+0x4c)
>> | #begin 0x80000000 -171 __ipipe_unstall_root+0x70
>> (__do_softirq+0x4c)
>> #func -177 __ipipe_unstall_root+0x10
>> (__do_softirq+0x4c)
>> #func -183 debug_smp_processor_id+0x10
>> (__do_softirq+0x38)
>> #func -190 debug_smp_processor_id+0x10
>> (__do_softirq+0x30)
>> #func -196 add_preempt_count+0x10 (__do_softirq+0x2c)
>>
>> Is this the problem coming from the alloc_skb function call? {
>
> Yes, you can not call alloc_skb from Xenomai domain, as you can not
> call most Linux functions. Note that if you are porting a network
> driver, you should consider using rtnet.
The point here is specifically that even if Linux itself provides
deterministic execution of your IRQ handler, it cannot guarantee that
there is always memory available for alloc_skb. That's why RTnet uses
preallocated pools for precisely this scenario. But, to avoid potential
misunderstandings right from the start, it is _not_ intended as a
performance or latency "booster" for standard networking applications.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Xenomai-help] I-pipe: Detected illicit call from domain 'Xenomai'
2007-08-17 12:45 ` Jan Kiszka
@ 2007-08-23 8:00 ` Yeoh Chun Yeow
2007-08-23 20:33 ` Jan Kiszka
0 siblings, 1 reply; 5+ messages in thread
From: Yeoh Chun Yeow @ 2007-08-23 8:00 UTC (permalink / raw)
To: Jan Kiszka; +Cc: Xenomai-help@domain.hid
[-- Attachment #1: Type: text/plain, Size: 5321 bytes --]
Dear all,
I have ported the at91ether and it now works under RTnet. I would like to
use the networking stack in Linux, instead of RTnet stack. However, I have
problem configure the VNIC with following errors:
[root@domain.hid] ./rtping 172.16.6.174
Real-time PING 172.16.6.174 56(84) bytes of data.
64 bytes from 172.16.6.174: icmp_seq=1 time=1186.7 us
64 bytes from 172.16.6.174: icmp_seq=2 time=1218.7 us
64 bytes from 172.16.6.174: icmp_seq=3 time=1178.7 us
64 bytes from 172.16.6.174: icmp_seq=4 time=1210.1 us
64 bytes from 172.16.6.174: icmp_seq=5 time=1182.4 us
--- 172.16.6.174 rtping statistics ---
5 packets transmitted, 5 received, 0% packet loss
worst case rtt = 1218.7 us
[root@domain.hid] ./rtifconfig
rtlo Medium: Local Loopback
IP address: 127.0.0.1
UP LOOPBACK RUNNING MTU: 1500
rteth0 Medium: Ethernet Hardware address: 14:09:07:05:05:02
IP address: 172.16.6.203 Broadcast address: 172.16.6.255
UP BROADCAST RUNNING MTU: 1500
[root@domain.hid] ifconfig vnic0 up 172.16.6.203
SIOCGIFFLAGS: No such device
SIOCSIFADDR: No such device
Please help. Thanks.
Regards,
Chun Yeow
P.S: Sorry for posting the RTnet issue here.
On 8/17/07, Jan Kiszka < jan.kiszka@domain.hid> wrote:
>
> Gilles Chanteperdrix wrote:
> > On 8/17/07, Yeoh Chun Yeow < yeohchunyeow@domain.hid> wrote:
> >> Dear all,
> >>
> >> I have encounter the following problem when migrating a Linux driver to
> RTDM
> >> driver:
> >>
> >> I-pipe: Detected illicit call from domain 'Xenomai'
> >> into a service reserved for domain 'Linux' and below.
>
> [Nice example for how to validate new RTDM drivers or Xenomai skins
> against accidental Linux calls! => CONFIG_IPIPE_DEBUG_CONTEXT]
>
> >> [<c002a474>] (show_stack+0x0/0x58) from [<c00736a4>]
> >> (ipipe_check_context+0x98/0xe4)
> >> [<c007360c>] (ipipe_check_context+0x0/0xe4) from [<c00d4ca4>]
> >> (cache_alloc_refill+0x7c/0x78c)
> >> r8 = 00000020 r7 = C04A3360 r6 = 00000000 r5 = 0000001B
> >> r4 = 00000000
> >> [<c00d4c28>] (cache_alloc_refill+0x0/0x78c) from [<c00d54dc>]
> >> (__kmalloc+0x128/0x138)
> >> [<c00d53b4>] (__kmalloc+0x0/0x138) from [<c027ede8>]
> (__alloc_skb+0x58/0xf8)
> >> r8 = 00000000 r7 = C04A8B00 r6 = 00000060 r5 = 00000020
> >> r4 = C065C940
> >> [<c027ed90>] (__alloc_skb+0x0/0xf8) from [<c0222b94>]
> >> (at91ether_interrupt+0x250/0x350)
> >> r8 = FFC00000 r7 = C0768A60 r6 = C0768B20 r5 = 00000046
> >> r4 = C03E4C60
> >>
> >> <snip>
> >>
> >> | # end 0x80000000 -44 __ipipe_unstall_root+0x4c
> >> (__ipipe_restore_root+0x70)
> >> | # *func -50 __ipipe_unstall_root+0x10
> >> (__ipipe_restore_root+0x70)
> >> | # *func -56 __ipipe_restore_root+0x10
> >> (kmem_cache_alloc+0x84)
> >> | # *func -63 debug_smp_processor_id+0x10
> >> (kmem_cache_alloc+0x50)
> >> | # *end 0x80000001 -70 kmem_cache_alloc+0xd8
> (__alloc_skb+0x3c)
> >> | # begin 0x80000001 -76 kmem_cache_alloc+0xc4
> (__alloc_skb+0x3c)
> >> | # func -83 kmem_cache_alloc+0x14
> (__alloc_skb+0x3c)
> >> | # func -91 __alloc_skb+0x14
> (at91ether_interrupt+0x250)
> >> | # func -100 at91ether_interrupt+0x14
> >> (xnintr_irq_handler+0x48)
> >> | # func -107 xnintr_irq_handler+0x14
> >> (__ipipe_dispatch_wired+0xf8)
> >> | +func -113 __ipipe_dispatch_wired+0x14
> >> (__ipipe_handle_irq+0x1b0)
> >> | +func -119 at91_aic_mask_irq+0x10
> >> (__ipipe_ack_level_irq+0x4c)
> >> | +func -125 at91_aic_mask_irq+0x10
> >> (__ipipe_ack_level_irq+0x3c)
> >> | +func -130 __ipipe_ack_level_irq+0x10
> >> (__ipipe_ack_irq+0x24)
> >> | +func -137 __ipipe_ack_irq+0x10
> >> (__ipipe_handle_irq+0x1a4)
> >> | +func -143 __ipipe_handle_irq+0x14
> >> (__ipipe_grab_irq+0xa0)
> >> | +begin 0xffffffff -150 __ipipe_grab_irq+0x34 (__irq_svc+0x30)
> >> | +func -156 __ipipe_grab_irq+0x14 (__irq_svc+0x30)
> >> | +end 0x80000000 -164 __ipipe_unstall_root+0x4c
> >> (__do_softirq+0x4c)
> >> | #begin 0x80000000 -171 __ipipe_unstall_root+0x70
> >> (__do_softirq+0x4c)
> >> #func -177 __ipipe_unstall_root+0x10
> >> (__do_softirq+0x4c)
> >> #func -183 debug_smp_processor_id+0x10
> >> (__do_softirq+0x38)
> >> #func -190 debug_smp_processor_id+0x10
> >> (__do_softirq+0x30)
> >> #func -196 add_preempt_count+0x10
> (__do_softirq+0x2c)
> >>
> >> Is this the problem coming from the alloc_skb function call? {
> >
> > Yes, you can not call alloc_skb from Xenomai domain, as you can not
> > call most Linux functions. Note that if you are porting a network
> > driver, you should consider using rtnet.
>
> The point here is specifically that even if Linux itself provides
> deterministic execution of your IRQ handler, it cannot guarantee that
> there is always memory available for alloc_skb. That's why RTnet uses
> preallocated pools for precisely this scenario. But, to avoid potential
> misunderstandings right from the start, it is _not_ intended as a
> performance or latency "booster" for standard networking applications.
>
> Jan
>
>
>
[-- Attachment #2: Type: text/html, Size: 9738 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [Xenomai-help] I-pipe: Detected illicit call from domain 'Xenomai'
2007-08-23 8:00 ` Yeoh Chun Yeow
@ 2007-08-23 20:33 ` Jan Kiszka
0 siblings, 0 replies; 5+ messages in thread
From: Jan Kiszka @ 2007-08-23 20:33 UTC (permalink / raw)
To: Yeoh Chun Yeow; +Cc: Xenomai-help@domain.hid, rtnet-users
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]
Yeoh Chun Yeow wrote:
> Dear all,
>
> I have ported the at91ether and it now works under RTnet. I would like to
Do you plan to post your changes? Would be great.
> use the networking stack in Linux, instead of RTnet stack. However, I have
> problem configure the VNIC with following errors:
>
> [root@domain.hid] ./rtping 172.16.6.174
> Real-time PING 172.16.6.174 56(84) bytes of data.
> 64 bytes from 172.16.6.174: icmp_seq=1 time=1186.7 us
> 64 bytes from 172.16.6.174: icmp_seq=2 time=1218.7 us
> 64 bytes from 172.16.6.174: icmp_seq=3 time=1178.7 us
> 64 bytes from 172.16.6.174: icmp_seq=4 time=1210.1 us
> 64 bytes from 172.16.6.174: icmp_seq=5 time=1182.4 us
Are these numbers over plain RTnet or with RTmac/TDMA active?
>
> --- 172.16.6.174 rtping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss
> worst case rtt = 1218.7 us
> [root@domain.hid] ./rtifconfig
> rtlo Medium: Local Loopback
> IP address: 127.0.0.1
> UP LOOPBACK RUNNING MTU: 1500
>
> rteth0 Medium: Ethernet Hardware address: 14:09:07:05:05:02
> IP address: 172.16.6.203 Broadcast address: 172.16.6.255
> UP BROADCAST RUNNING MTU: 1500
>
> [root@domain.hid] ifconfig vnic0 up 172.16.6.203
> SIOCGIFFLAGS: No such device
> SIOCSIFADDR: No such device
See question above. How did you configure RTnet, only manually?
>
> Please help. Thanks.
>
> Regards,
> Chun Yeow
> P.S: Sorry for posting the RTnet issue here.
I added rtnet-users to CC. Please drop Xenomai on reply unless there is
some Xenomai-specific topic covered.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-08-23 20:33 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-17 11:09 [Xenomai-help] I-pipe: Detected illicit call from domain 'Xenomai' Yeoh Chun Yeow
2007-08-17 12:07 ` Gilles Chanteperdrix
2007-08-17 12:45 ` Jan Kiszka
2007-08-23 8:00 ` Yeoh Chun Yeow
2007-08-23 20:33 ` Jan Kiszka
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.