Hello list,
I am running Ore on native HW and Intel(R) PRO/1000 Network Connection.
Ore seems to recognize the network card correctly but quits when I try to setup eth0.
L4Linux error message:
eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed.
Any hint highly appreciated.
Regards, Michael
Hi,
I am running Ore on native HW and Intel(R) PRO/1000 Network Connection.
Ore seems to recognize the network card correctly but quits when I try to setup eth0.
L4Linux error message:
eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed.
What do you mean by 'ORe quits when setting up eth0'? Is there an error message from the ORe server?
Please try to run ORe and the Arping-Test included in the ORe package. If you then can arping your test computer (the arping client's MAC is printed at startup) from another one, ORe should be working correctly and someone else (Adam ;)) needs to step in here.
Bjoern
Am Freitag 25 November 2005 18:20 schrieben Sie:
Hi,
I am running Ore on native HW and Intel(R) PRO/1000 Network Connection.
Ore seems to recognize the network card correctly but quits when I try to setup eth0.
L4Linux error message:
eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed.
What do you mean by 'ORe quits when setting up eth0'? Is there an error message from the ORe server?
ORe stops dumping the corresponding connection table and logs: thread/lib/src/exit.c:273:l4thread.shutdown() Error: thread 0 not active
Please try to run ORe and the Arping-Test included in the ORe package. If you then can arping your test computer (the arping client's MAC is printed at startup) from another one, ORe should be working correctly and someone else (Adam ;)) needs to step in here.
I've run ore_test_arping successfully. It seems to create a 'fresh' MAC which can then be arpinged by another host, but I still cannot setup the interface eth0 in L4Linux.
Running 'ifconfig eth0 <ip-adr>' causes the ORe stub to log
eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed
I have disabled "Network device support" in L4Linux and enabled "Network driver for ORe".
Regards, Michael
Hello Michael,
please post a complete log for:
* Fiasco kernel debugger messages * L4Linux boot messages
BTW: Switching "Network device support" on seems reasonable...
Cheers
Am Montag 28 November 2005 16:53 schrieb Christian Helmuth:
Hello Michael,
please post a complete log for:
- Fiasco kernel debugger messages
- L4Linux boot messages
BTW: Switching "Network device support" on seems reasonable...
Cheers
Hi,
here we are, better late than never :) We did not manage to arping ore_test_arping this time, but complete logs are attached.
Michael
Hello,
We did not manage to arping ore_test_arping this time, but complete logs are attached.
humm, ... please update your version of ORe from our public CVS and try to run some minimal setup with only the arping client and w/o L4Linux. See my example below and report us your experiences.
My menu.lst looks like this:
title ORe arping test kernel (nd)/tftpboot/doebel/l4v2/bootstrap -sigma0 -roottask -serial -comport=2 modaddr 0x02000000 module (nd)/tftpboot/doebel/kernel/fiasco -nowait -nokdb -comport 2 -tbuf_entries=32768 -serial_esc -esc module (nd)/tftpboot/doebel/l4v2/sigma0 module (nd)/tftpboot/doebel/l4v2/roottask module (nd)/tftpboot/doebel/l4v2/names --events module (nd)/tftpboot/doebel/l4v2/log module (nd)/tftpboot/doebel/l4v2/dm_phys --events module (nd)/tftpboot/doebel/l4v2/l4io --noirq --nolist module (nd)/tftpboot/doebel/l4v2/ore --events module (nd)/tftpboot/doebel/l4v2/events module (nd)/tftpboot/doebel/l4v2/ore_test_arping
With this setup I get a virtual MAC address (note that I have an Eepro100 NIC):
names | Starting thread listening for `exit' events io | do_args(): Disabling internal IRQ handling. io | do_args(): Disabling listing of PCI devices. arping | main(): Hello from the ORe arping shared memory client arping | main(): string ipc receive arping | main(): sending with string ipc arping | l4ore_open(): called io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | Applying VIA southbridge workaround. arping | ore_initialize(): dsi_init: 0 ore | l4dde_mm_init(): Using ... ore | 8192 kB at 0x00180000 (vmem) ore | 8192 kB in 1 regions (kmem) ore | eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/networ ore : k/eepro100.html ore | eepro100.c: $Revision: 1.2 $ 2000/11/17 Modified by Andrey V. Savochk ore : in saw@saw.sw.com.sg and others ore | eth0: Intel Corp. 82557/8/9 [Ethernet Pro 100], 00:02:B3:C1:E9:93, IR ore : Q 10. ore | Board assembly 751767-004, Physical connectors present: RJ45 ore | Primary interface chip i82555 PHY #1. ore | Secondary interface chip i82555. ore | General self-test: passed. ore | Serial sub-system self-test: passed. ore | Internal registers self-test: passed. ore | ROM checksum self-test: passed (0x3258698e). ore | device lo entered promiscuous mode ore | device eth0 entered promiscuous mode ore | main(): Initialized 2 network devices. ore | main(): Registering at names... ore | main(): Ready for service. arping | ore_lookup_server(): ORe = 9.02 arping | l4ore_open(): descriptor: 0 arping | l4ore_open(): sending via string ipc arping | l4ore_open(): receiving via string IPC arping | ore_do_open(): called arping | ore_do_open(): opened. worker = 9.08 arping | main(): opened eth0: 0 for 04:EA:F3:02:50:13 arping | main(): handle = 0 arping | main(): got send area: 0x00200008
Now I can arping this MAC from my workstation:
$>arping 04:EA:F3:02:50:13 -c 5 ARPING 04:EA:F3:02:50:13 80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 time=503.063 usec 80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 time=128.984 usec 80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 time=133.991 usec 80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 time=157.118 usec 80 bytes from 255.255.255.255 (04:ea:f3:02:50:13): icmp_seq=0 time=128.984 usec
--- 04:EA:F3:02:50:13 statistics --- 5 packets transmitted, 5 packets received, 0% unanswered
Bjoern
Am Dienstag 07 Februar 2006 16:42 schrieb Bjoern Doebel:
Hello,
We did not manage to arping ore_test_arping this time, but complete logs are attached.
humm, ... please update your version of ORe from our public CVS and try to run some minimal setup with only the arping client and w/o L4Linux. See my example below and report us your experiences.
Thank you! Arping now works again, but configuring eth0 in L4Linux fails with
ore | [B.2] thread/lib/src/exit.c:273:l4thread_shutdown(): ore | Error: thread 0 not active ore | [B.2] thread/lib/src/exit.c:273:l4thread_shutdown(): ore | Error: thread 0 not active ore | [B.2] thread/lib/src/exit.c:273:l4thread_shutdown(): ore | Error: thread 0 not active
Additionally dmesg says:
eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed. eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed. eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed.
My menu.lst:
title = ORe Gentoo kernel (hd0,3)/boot/tcb/svpn/bootstrap -sigma0 -roottask -serial -comport=1 modaddr 0x02000000 module (hd0,3)/boot/tcb/svpn/fiasco -nokdb -comport 1 -serial -nowait module (hd0,3)/boot/tcb/svpn/sigma0 module (hd0,3)/boot/tcb/svpn/roottask -sigma0 task modname "bmodfs" module module module module module (hd0,3)/boot/tcb/svpn/names module (hd0,3)/boot/tcb/svpn/dmon module (hd0,3)/boot/tcb/svpn/dm_phys module (hd0,3)/boot/tcb/svpn/simple_ts -t 380 module (hd0,3)/boot/tcb/svpn/rtc module (hd0,3)/boot/tcb/svpn/l4io module (hd0,3)/boot/tcb/bench/ore "--debug" module (hd0,3)/boot/tcb/bench/ore_test_arping
module (hd0,3)/boot/tcb/svpn/bmodfs module (hd0,3)/boot/tcb/svpn/run module (hd0,3)/boot/tcb/svpn/libloader.s.so module (hd0,3)/boot/tcb/bench/vmlinuz26-ore module (hd0,3)/boot/tcb/bench/l4linux26ramdisk-ore.cfg
module (hd0,3)/boot/tcb/svpn/l4exec module (hd0,3)/boot/tcb/svpn/l4dope --l4io module (hd0,3)/boot/tcb/svpn/loader --fprov=BMODFS l4linux26ramdisk-ore.cfg vbeset 0x117
Regards, Michael
l4-hackers@os.inf.tu-dresden.de
-
Bjoern Doebel -
Christian Helmuth -
Michael Scheibel