l4-hackers September 2006

l4-hackers@os.inf.tu-dresden.de

12 participants
18 discussions

L4Linux on Xscale
by 조완근 01 Oct '06

01 Oct '06

Hi, Sorry, I forgot to say that I tried arm-linux-gcc version 2.95.3, 3.3.1, 3.4.4.. but all the results are same...   Thank you..

2 1

L4Linux on Xscale
by Wan-Keun Jo 30 Sep '06

30 Sep '06

Hi, I tried to install Fiasco-L4Linux on Xscale-PXA255. I saw a "hello message" with fiasco kernel, sigma0, roottask, hello programs yesterday. When I start to compile L4linux, I got the following errors... ================================================================== /l4linux-2.6$ make CHK include/linux/version.h CC arch/l4/kernel/asm-offsets.s cc1: error: invalid option `abi=apcs-gnu' (1) cc1: error: bad value (armv4) for -march= switch … [View More]

1 0

L4Linux and USB mass storage
by Andreas Niederl 26 Sep '06

26 Sep '06

Hi, I'm having problems using a USB connected mass storage device with L4Linux. On device detection an out of memory error happens when the cache is allocated: NET: Registered protocol family 1 NET: Registered protocol family 17 Waiting 15sec before mounting root device... l4lx | l4lx_thread_create: Created thread 0e.0c (IRQ1) input: AT Translated Set 2 keyboard as /class/input/input0 logips2pp: Detected unknown logitech mouse model 1 input: PS/2 Logitech Mouse as /class/input/input1 … [View More]

2 2

IO address acess on L4linux for ARM
by 김광식 23 Sep '06

23 Sep '06

   IO peripheral Address region in my platform is 0xfffb0000 - 0xfffeffff    I want to add device driver in L4linux.    in L4linux device driver  ...  *(volatile unsigned char *)0xfffb0000 = 'c';  ...    following case made error result error e0 l4lx    | Invalid source for request: 2f.3f result error e0 l4lx    | … [View More]

2 1

Re: Maybe it is a bug of L4/Fiasco or L4Linux
by chenggh 19 Sep '06

19 Sep '06

On Tuesday 19 September 2006 04:17, Adam Lackorzynski wrote: > Hi, > > On Mon Sep 18, 2006 at 11:19:27 +0800, chenggh wrote: > > When I use netpipe to test the performance of L4Linux based on top of > > L4/Fiasco there is something as following: > > > > kernel BUG at include/linux/netdevice.h:886! > > Trap: 6: 0000 [#1] > > Modules linked in: > > CPU: 0 > > EIP: f032:[<0056f317>] Not tainted VLI > > EFLAGS: 00013246 … [View More] (2.6.17-l4 #1) > > EIP is at rtl8139_poll+0xd7/0xf0 > > eax: 00000006 ebx: 0001d43c ecx: 0000c07f edx: 0000d43c > > esi: 01331400 edi: b09fff10 ebp: b09fff00 esp: b09ffedc > > ds: 4000 es: ea0c ss: 0000 > > Process swapper (pid: 0, threadinfo=b09fe000 task=0066b940) > > Stack: 01331400 01331660 00000040 00000001 0001d400 01331660 013314c0 > > 01331400 00003e13 b09fff20 005a8262 01331400 b09fff10 0000012c 00000001 > > 007207d8 0000000a b09fff38 0041a7a9 007207d8 00000000 0000000c 00000000 > > b09fff48 Call Trace: > > <0040bec0> show_stack_log_lvl+0x90/0xc0 <0040c08b> > > show_registers+0x14b/0x1c0 > > <0040c2bd> die+0xfd/0x200 <00000000> _start+0xffc00000/0x50 > > <005a8262> net_rx_action+0x72/0x110 <0041a7a9> __do_softirq+0x49/0xb0 > > <00407bc8> do_softirq+0x48/0x50 <0041a8c5> irq_exit+0x35/0x40 > > <00407993> do_IRQ+0x23/0x30 <0050b052> irq_thread_hw+0x1f2/0x330 > > <a00a8a4c> 0xa00a8a4c <a00abc76> 0xa00abc76 > > Code: 41 04 00 02 20 00 c7 86 c0 00 00 00 00 01 10 00 0f ba 76 2c 05 e8 > > 4a 4a e9 ff 31 c0 83 7d e8 00 0f 94 c0 83 c4 18 5b 5e 5f c9 c3 <0f> 0 > > b 76 03 e0 03 64 00 eb b6 eb 0d 90 90 90 90 90 90 90 90 90 > > EIP: [<0056f317>] rtl8139_poll+0xd7/0xf0 SS:ESP 0023:b09ffed4 > > <0>Kernel panic - not syncing: Fatal exception in interrupt > > panic: going to sleep forever, bye > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 107084 dirty entry 107080. > > eth1: Tx descriptor 0 is 0008a042. (queue head) > > eth1: Tx descriptor 1 is 0008a042. > > eth1: Tx descriptor 2 is 0008a5ea. > > eth1: Tx descriptor 3 is 0008a5ea. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 4 dirty entry 0. > > eth1: Tx descriptor 0 is 0008a4ef. (queue head) > > eth1: Tx descriptor 1 is 0008a5ea. > > eth1: Tx descriptor 2 is 0008a5ea. > > eth1: Tx descriptor 3 is 0008a5ea. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 4 dirty entry 0. > > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > > eth1: Tx descriptor 1 is 0008a5ea. > > eth1: Tx descriptor 2 is 0008a5ea. > > eth1: Tx descriptor 3 is 0008a5ea. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > eth1: Transmit timeout, status 0c 0005 c07f media 10. > > eth1: Tx queue start entry 4 dirty entry 0. > > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > > eth1: Tx descriptor 1 is 0008a03c. > > eth1: Tx descriptor 2 is 0008a03c. > > eth1: Tx descriptor 3 is 0008a03c. > > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > > NETDEV WATCHDOG: eth1: transmit timed out > > > > And every time the netpipe program don't exit normally and the L4Linux > > is dead so that I must reboot it again. Maybe it is a bug but I am not > > sure. Thank you. > > Hard to tell what's going wrong here, I guess I need to reproduce this > to say anything about this. This is some Realtek 100Mbit NIC, right? Do > you give any special options to NPtcp? > Are both sides L4Linux or just one, if the latter, which side? > > > > Adam In the sender I use command as "./NPtcp -h receive_ip -o mylog" and in the receiver I only use "./NPtcp". Oh, I use two different types netcard, Realtek 100Mbit and Intel 1000M. When I use Realtek or Intel anyway as the sender port the error information is same. I only use one L4Linux as a bridge and the structure is like this: Slackware 10.2 <-------------> L4Linux/Fiasco <-------------> Slackware 10.1 192.168.1.2(sender) <------->192.168.1.1 192.168.0.1<------------------->192.168.0.2(receiver) 192.168.1.2(receiver) <------->192.168.1.1 192.168.0.1<------------------->192.168.0.2(sender) In the L4Linux/Fiasco I use two different ethernet card as Realtek 100M and Intel 1000M. The error information is from the minicom log. And in this test the NPtcp application doesn't exit normally and I have to reboot when the minicom has the error information. Thank you. chenggh [View Less]

1 0

Re: Maybe it is a bug of L4/Fiasco or L4Linux
by Adam Lackorzynski 18 Sep '06

18 Sep '06

Hi, On Mon Sep 18, 2006 at 11:19:27 +0800, chenggh wrote: > When I use netpipe to test the performance of L4Linux based on top of > L4/Fiasco there is something as following: > > kernel BUG at include/linux/netdevice.h:886! > Trap: 6: 0000 [#1] > Modules linked in: > CPU: 0 > EIP: f032:[<0056f317>] Not tainted VLI > EFLAGS: 00013246 (2.6.17-l4 #1) > EIP is at rtl8139_poll+0xd7/0xf0 > eax: 00000006 ebx: 0001d43c ecx: 0000c07f edx: … [View More]0000d43c > esi: 01331400 edi: b09fff10 ebp: b09fff00 esp: b09ffedc > ds: 4000 es: ea0c ss: 0000 > Process swapper (pid: 0, threadinfo=b09fe000 task=0066b940) > Stack: 01331400 01331660 00000040 00000001 0001d400 01331660 013314c0 01331400 > 00003e13 b09fff20 005a8262 01331400 b09fff10 0000012c 00000001 007207d8 > 0000000a b09fff38 0041a7a9 007207d8 00000000 0000000c 00000000 b09fff48 > Call Trace: > <0040bec0> show_stack_log_lvl+0x90/0xc0 <0040c08b> > show_registers+0x14b/0x1c0 > <0040c2bd> die+0xfd/0x200 <00000000> _start+0xffc00000/0x50 > <005a8262> net_rx_action+0x72/0x110 <0041a7a9> __do_softirq+0x49/0xb0 > <00407bc8> do_softirq+0x48/0x50 <0041a8c5> irq_exit+0x35/0x40 > <00407993> do_IRQ+0x23/0x30 <0050b052> irq_thread_hw+0x1f2/0x330 > <a00a8a4c> 0xa00a8a4c <a00abc76> 0xa00abc76 > Code: 41 04 00 02 20 00 c7 86 c0 00 00 00 00 01 10 00 0f ba 76 2c 05 e8 4a 4a > e9 ff 31 c0 83 7d e8 00 0f 94 c0 83 c4 18 5b 5e 5f c9 c3 <0f> 0 > b 76 03 e0 03 64 00 eb b6 eb 0d 90 90 90 90 90 90 90 90 90 > EIP: [<0056f317>] rtl8139_poll+0xd7/0xf0 SS:ESP 0023:b09ffed4 > <0>Kernel panic - not syncing: Fatal exception in interrupt > panic: going to sleep forever, bye > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 107084 dirty entry 107080. > eth1: Tx descriptor 0 is 0008a042. (queue head) > eth1: Tx descriptor 1 is 0008a042. > eth1: Tx descriptor 2 is 0008a5ea. > eth1: Tx descriptor 3 is 0008a5ea. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 4 dirty entry 0. > eth1: Tx descriptor 0 is 0008a4ef. (queue head) > eth1: Tx descriptor 1 is 0008a5ea. > eth1: Tx descriptor 2 is 0008a5ea. > eth1: Tx descriptor 3 is 0008a5ea. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 4 dirty entry 0. > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > eth1: Tx descriptor 1 is 0008a5ea. > eth1: Tx descriptor 2 is 0008a5ea. > eth1: Tx descriptor 3 is 0008a5ea. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > eth1: Transmit timeout, status 0c 0005 c07f media 10. > eth1: Tx queue start entry 4 dirty entry 0. > eth1: Tx descriptor 0 is 0008a5ea. (queue head) > eth1: Tx descriptor 1 is 0008a03c. > eth1: Tx descriptor 2 is 0008a03c. > eth1: Tx descriptor 3 is 0008a03c. > eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 > NETDEV WATCHDOG: eth1: transmit timed out > > And every time the netpipe program don't exit normally and the L4Linux is > dead so that I must reboot it again. Maybe it is a bug but I am not sure. > Thank you. Hard to tell what's going wrong here, I guess I need to reproduce this to say anything about this. This is some Realtek 100Mbit NIC, right? Do you give any special options to NPtcp? Are both sides L4Linux or just one, if the latter, which side? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ [View Less]

1 0

L4 Bootimage tools
by Spring, Ryan C 18 Sep '06

18 Sep '06

Which tools are available to generate monolithic bootimages for l4 on platforms that don't support elf? I have seen the dite tool from NICTA; are there also other options? Thanks, Ryan Spring --- Ryan Spring Doctoral Student University of Texas at El Paso (UTEP) Cell: +1 915-539-7311 (when in USA) Alt Cell: +49 179-9624406 (when in Germany) http://www.spring-west.net/ryan Auch aus Steinen, die einem in den Weg gelegt werden, kann man Schönes bauen. J.W. Goethe

2 1

Maybe it is a bug of L4/Fiasco or L4Linux
by chenggh 18 Sep '06

18 Sep '06

Hi, everyone: When I use netpipe to test the performance of L4Linux based on top of L4/Fiasco there is something as following: kernel BUG at include/linux/netdevice.h:886! Trap: 6: 0000 [#1] Modules linked in: CPU: 0 EIP: f032:[<0056f317>] Not tainted VLI EFLAGS: 00013246 (2.6.17-l4 #1) EIP is at rtl8139_poll+0xd7/0xf0 eax: 00000006 ebx: 0001d43c ecx: 0000c07f edx: 0000d43c esi: 01331400 edi: b09fff10 ebp: b09fff00 esp: b09ffedc ds: 4000 es: ea0c ss: 0000 … [View More]Process swapper (pid: 0, threadinfo=b09fe000 task=0066b940) Stack: 01331400 01331660 00000040 00000001 0001d400 01331660 013314c0 01331400 00003e13 b09fff20 005a8262 01331400 b09fff10 0000012c 00000001 007207d8 0000000a b09fff38 0041a7a9 007207d8 00000000 0000000c 00000000 b09fff48 Call Trace: <0040bec0> show_stack_log_lvl+0x90/0xc0 <0040c08b> show_registers+0x14b/0x1c0 <0040c2bd> die+0xfd/0x200 <00000000> _start+0xffc00000/0x50 <005a8262> net_rx_action+0x72/0x110 <0041a7a9> __do_softirq+0x49/0xb0 <00407bc8> do_softirq+0x48/0x50 <0041a8c5> irq_exit+0x35/0x40 <00407993> do_IRQ+0x23/0x30 <0050b052> irq_thread_hw+0x1f2/0x330 <a00a8a4c> 0xa00a8a4c <a00abc76> 0xa00abc76 Code: 41 04 00 02 20 00 c7 86 c0 00 00 00 00 01 10 00 0f ba 76 2c 05 e8 4a 4a e9 ff 31 c0 83 7d e8 00 0f 94 c0 83 c4 18 5b 5e 5f c9 c3 <0f> 0 b 76 03 e0 03 64 00 eb b6 eb 0d 90 90 90 90 90 90 90 90 90 EIP: [<0056f317>] rtl8139_poll+0xd7/0xf0 SS:ESP 0023:b09ffed4 <0>Kernel panic - not syncing: Fatal exception in interrupt panic: going to sleep forever, bye NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 107084 dirty entry 107080. eth1: Tx descriptor 0 is 0008a042. (queue head) eth1: Tx descriptor 1 is 0008a042. eth1: Tx descriptor 2 is 0008a5ea. eth1: Tx descriptor 3 is 0008a5ea. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 4 dirty entry 0. eth1: Tx descriptor 0 is 0008a4ef. (queue head) eth1: Tx descriptor 1 is 0008a5ea. eth1: Tx descriptor 2 is 0008a5ea. eth1: Tx descriptor 3 is 0008a5ea. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 4 dirty entry 0. eth1: Tx descriptor 0 is 0008a5ea. (queue head) eth1: Tx descriptor 1 is 0008a5ea. eth1: Tx descriptor 2 is 0008a5ea. eth1: Tx descriptor 3 is 0008a5ea. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out eth1: Transmit timeout, status 0c 0005 c07f media 10. eth1: Tx queue start entry 4 dirty entry 0. eth1: Tx descriptor 0 is 0008a5ea. (queue head) eth1: Tx descriptor 1 is 0008a03c. eth1: Tx descriptor 2 is 0008a03c. eth1: Tx descriptor 3 is 0008a03c. eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 NETDEV WATCHDOG: eth1: transmit timed out And every time the netpipe program don't exit normally and the L4Linux is dead so that I must reboot it again. Maybe it is a bug but I am not sure. Thank you. chenggh [View Less]

1 0

The fiasco kernel and roottask I build are too large to put in the floppy.
by Zheng Da 17 Sep '06

17 Sep '06

I found the two files in drops-demo-floppydisk-current.img are quite small. -rwxr-xr-x 1 root root 166060 2005-08-15 15:53 fiasco -rwxr-xr-x 1 root root 61545 2005-08-15 15:41 roottask But the ones I build are so large that there are on enough space for them in the floppy. -rwxr-xr-x 1 zhengda zhengda 639K 2006-09-16 00:25 bin/x86_586/l4v2/roottask -rwxr-xr-x 1 zhengda zhengda 358K 2006-09-16 00:08 l4/kernel/fiasco/build/main I got fiasco from CVS, and followed the steps showed in http://os.… [View More]

2 1

PXE enabled GRUB
by Adam Lackorzynski 15 Sep '06

15 Sep '06

Hi, this might be of interest to you. I have added PXE network driver support for my GRUB patch set recently. This enables GRUB to load files via the network using any PXE capable NIC, including latest e1000, Broadcom, e100, 3coms, etc. cards. The patch, README and binary are at the usual place at: http://os.inf.tu-dresden.de/~adam/grub/0.97/ Refer to the README file for details. If you have a NIC that has PXE and does not work, please let me know. Adam -- Adam adam(a)os.… [View More]

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers September 2006