- l4-hackers - example.com Site

TFTP does not work with QEMU
by Daniel Vandersee 05 Oct '06

05 Oct '06

Hello, when I try to run tftp under QEMU 0.8.2 with an emulated pcnet or ne2k-pci network card I get the following error. However, tftp under VMWare works just fine. Any help would be appreciated. Kind regards, Daniel > names | Starting thread listening for `exit' events > simplets| Configured for 30 tasks. > rtc | Date:02.10.2006 Time:14:42:15 > io | do_args(): Disabling internal IRQ handling. > tftp | NICs supported: E1000, EEPRO100, NE2000/PCI, PCNET32/PCI, RTL8139, > tftp | Tulip, VIA 86C100 > io | PCI: Using configuration type 1 > io | PCI: Probing PCI hardware > io | PCI: Probing PCI hardware (bus 00) > > KERNEL: d.3 (tcb=c0341800) killed: > Unhandled trap > > EAX 12378000 EBX 000f0000 ECX 00000000 EDX 00009fa0 > ESI 00000000 EDI 01044e30 EBP 0102ff8c ESP 0102ff7c > EIP 000f9f9b EFLAGS 00013206 > CS 001b SS 0023 DS 0023 ES 0023 FS 0023 GS 0043 > trap 13 (General Protection), error 00000018, from user mode > (internal event regarding GDT entry no. 0x03) > io | PCI: PIIX3: Enabling Passive Release on 00:01.0 > io | Limiting direct PCI/PCI transfers. > io | Activating ISA DMA hang workarounds. > io | 00000000-ffffffff : PCI mem > io | e0000000-e07fffff : PCI device 1234:1111 (Technical Corp.) > io | e1000000-e100001f : Advanced Micro Devices [AMD] 79c970 [PCnet32 LA > io : NCE] > io | 0000-ffff : PCI IO > io | 0cf8-0cff : PCI conf1 > io | b000-b03f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI > io | c000-c00f : Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] > io | c020-c03f : Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]

3 4

Difference between Fiasco and L4Linux...
by Dustin Oprea 02 Oct '06

02 Oct '06

I think I'm missing something really obvious, but what's the difference between Fiasco and L4Linux... It appears they're made by the same group. I use QNX RTOS at work, and I'm interested in using the microkernel instead of the full-on monolothic kernel at home with my Fedora installation. What goes in first: Fiasco, or L4Linux? Dustin Oprea

2 1

Re: Difference between Fiasco and L4Linux...
by chenggh 02 Oct '06

02 Oct '06

On Monday 02 October 2006 10:46, Dustin Oprea wrote: > I think I'm missing something really obvious, but what's the difference > between Fiasco and L4Linux... It appears they're made by the same group. Fiasco is the microkernel but L4Linux is not. L4Linux is the variation of Linux kernel running on top of Fiasco and it is loaded as the module of Fiasco when running. They made the L4Linux in order to have a good portability of Linux application into the L4/Fiasco. > I use QNX RTOS at work, and I'm interested in using the microkernel > instead of the full-on monolothic kernel at home with my Fedora > installation. What goes in first: Fiasco, or L4Linux? First you must compile the Fiasco and L4Linux of course you need a modified grub version to boot the Fiasco successfully. I think you should download all the souce code of L4 and L4Linux and try to compile. :) chenggh

1 0

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 (2) cc1: error: bad value (armv4) for -mcpu= switch make[1]: *** [arch/l4/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 ================================================================== >> Question 01: Error (1): I solved by fixing the following code arch/l4/Makefile:77: CFLAGS_ABI :=$(call cc-option,-mapcs-32,-mabi=apcs-gnu) $(call cc-option,-mno-thumb- interwork,) [change to] CFLAGS += $(call cc-option,-mapcs-32,$(call cc-option,-mabi=apcs-gnu),) $(call cc-option, -mno-thumb-interwork,) Error (1) is solved, but what is the difference between them?? (I just fix it, I don't know why...) >> Question 02: Error (2): I read what "-march" option is on gcc manual, and found the permissible values for it are armv2, armv2a, armv3, armv3m, armv4, armv4t, armv5, armv5t, armv5te, armv6, armv6j, iwmmxt, ep9312 In the file "arch/l4/Makefile:82 CFLAGS += -D__LINUX_ARM_ARCH__=4 -march=armv4" I just tried each values one by one for -march option, but all failed. How can I fix it and compile well??? Thank you!!

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 Vendor: ST325082 Model: 3AS Rev: Type: Direct-Access ANSI SCSI revision: 02 oom-killer: gfp_mask=0xd1, order=0 <0040a605> show_trace+0x15/0x20 <0040a6f7> dump_stack+0x17/0x20 <0043227b> out_of_memory+0x6b/0x90 <0043336c> __alloc_pages+0x26c/0x2a0 <004469d4> kmem_getpages+0x34/0xa0 <00447689> cache_grow+0x99/0x180 <004478ed> cache_alloc_refill+0x17d/0x1c0 <00447af8> kmem_cache_alloc+0x48/0x5 0 <00571fbc> sd_revalidate_disk+0x2c/0x100 <005722ad> sd_probe+0x21d/0x310 <00512244> driver_probe_device+0x54/0xb0 <005122b0> __device_attach+0x10/0x20 <005118db> bus_for_each_drv+0x4b/0x70 <00512314> device_attach+0x54/0x60 <00511a05> bus_add_device+0x25/0x90 <00510a5a> device_add+0xda/0x160 <0056da33> scsi_sysfs_add_sdev+0x33/0x180 <0056bef9> scsi_add_lun+0x199/0x360 <0056c1db> scsi_probe_and_add_lun+0x11b/0x200 <0056c9b1> __scsi_scan_target+0xa1/0xe0 <0056caec> scsi_scan_channel+0x6c/0x90 <0056cb76> scsi_scan_host_selected+0x66/0xb0 <0056cbd4> scsi_scan_host+0x14/0x20 <00594dee> usb_stor_scan_thread+0x4e/0x150 <00424994> kthread+0x94/0xc0 <00407619> kernel_thread_start+0x29/0x30 <004075ee> ret_kernel_thread_start+0x6/0x8 I'm using L4Linux-2.6.17 and tried it on a machine with 512MB memory with 256MB reserved for L4Linux as well as on a machine with 1GB memory and 768MB for L4Linux. Delaying the device detection by booting into a Ramdisk and then loading the respective modules and udev resulted in the same behaviour. Has anybody else experienced such problems when using USB disks with L4Linux? Regards, Andi

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    | Invalid source for request: 2f.3f result error e0 l4lx    | Invalid source for request: 2f.3f result error e0 l4lx    | Invalid source for request: 2f.3f result error e0 l4lx    | Invalid source for request: 2f.3f 0000003600000037 failed CLI: 0000000c.00000004    How can I access IO Address?

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

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

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