Julien Reveillet
2007-Dec-06 18:34 UTC
[Xen-users] DomU (Centos 5) with dedicated e1000 (intel) device dropping packets
Hello everybody, I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i have a new problem, and a big one. My ethernet card is dropping packets but after some time (i can''t tell how) It can work for a day (not in production so not hard tested) and then all packets are dropped. Look at the ifconfig output : eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:192.168.9.52 Bcast:192.168.9.255 Mask:255.255.255.0 inet6 addr: fe80::213:72ff:fe0f:1c6a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10505 errors:0 dropped:352 overruns:0 frame:0 TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2223312 (2.1 MiB) TX bytes:555445 (542.4 KiB) Base address:0xcce0 Memory:fe3e0000-fe400000 Today, nothing was done on it but, a few minutes before, i realised that it was down. Dmesg output : ... Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI Copyright (c) 1999-2006 Intel Corporation. PCI: Enabling device 0000:00:01.0 (0000 -> 0003) PCI: Setting latency timer of device 0000:00:01.0 to 64 e1000: 0000:00:01.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) xx:xx:xx:xx:xx:xx e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver NET: Registered protocol family 5 eth0: no IPv6 routers present The interface is still up. I saw while googling that it could be an hardware problem but this was not in a xen environnement so... Anybody have seen this before? Thanks. Best Regards. Julien. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julien Reveillet
2007-Dec-06 19:15 UTC
Re: [Xen-users] DomU (Centos 5) with dedicated e1000 (intel) device dropping packets
Re, After ifdown, ifup my interface i see packet arriving in it but... while using tshark to catch packets, here is what i get when it runs : tshark -i eth0 No log handling enabled - turning on stderr logging Cannot find module (IP-MIB): At line 0 in (none) Cannot find module (IF-MIB): At line 0 in (none) Cannot find module (TCP-MIB): At line 0 in (none) Cannot find module (UDP-MIB): At line 0 in (none) Cannot find module (SNMPv2-MIB): At line 0 in (none) Cannot find module (SNMPv2-SMI): At line 0 in (none) Cannot find module (UCD-SNMP-MIB): At line 0 in (none) audit(1196968132.562:2): dev=eth0 prom=256 old_prom=0 auid=4294967295 Capturing on eth0 And nothing... To correct what i wrote earlier. Pci export from Dom0 (Debian Etch) to DomU (CentOs 5) works. I can transfer big files but after a moment, no response (while not using it) Could it be acpi that standby my card which do work correctly? Thanks in advance. Regards. Julien. Julien Reveillet a écrit : Hello everybody, I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i have a new problem, and a big one. My ethernet card is dropping packets but after some time (i can''t tell how) It can work for a day (not in production so not hard tested) and then all packets are dropped. Look at the ifconfig output : eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:192.168.9.52 Bcast:192.168.9.255 Mask:255.255.255.0 inet6 addr: fe80::213:72ff:fe0f:1c6a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10505 errors:0 dropped: 352 overruns:0 frame:0 TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2223312 (2.1 MiB) TX bytes:555445 (542.4 KiB) Base address:0xcce0 Memory:fe3e0000-fe400000 Today, nothing was done on it but, a few minutes before, i realised that it was down. Dmesg output : ... Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI Copyright (c) 1999-2006 Intel Corporation. PCI: Enabling device 0000:00:01.0 (0000 -> 0003) PCI: Setting latency timer of device 0000:00:01.0 to 64 e1000: 0000:00:01.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) xx:xx:xx:xx:xx:xx e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver NET: Registered protocol family 5 eth0: no IPv6 routers present The interface is still up. I saw while googling that it could be an hardware problem but this was not in a xen environnement so... Anybody have seen this before? Thanks. Best Regards. Julien. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Julien Reveillet
2007-Dec-12 15:25 UTC
[Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device dropping packets
Hi everyone, Here is what my Xen Dom0 syslog daemon reports after a freeze of my CentOs DomU network interface : xen kernel: Disabling IRQ #17 Dec 12 16:16:18 xen kernel: [] __report_bad_irq+0x2b/0x69 Dec 12 16:16:18 xen kernel: [] note_interrupt+0x1b3/0x1eb Dec 12 16:16:18 xen kernel: [] handle_IRQ_event+0x49/0x51 Dec 12 16:16:18 xen kernel: [] __do_IRQ+0xb3/0xe8 Dec 12 16:16:18 xen kernel: [] do_IRQ+0x43/0x53 Dec 12 16:16:18 xen kernel: [] evtchn_do_upcall+0x64/0x9b Dec 12 16:16:18 xen kernel: [] hypervisor_callback+0x3d/0x48 Dec 12 16:16:18 xen kernel: [] notify_remote_via_irq+0x27/0x5f Dec 12 16:16:18 xen kernel: [] blkif_notify_work+0x1b/0x1d Dec 12 16:16:18 xen kernel: [] make_response+0xeb/0x12f Dec 12 16:16:18 xen kernel: [] end_block_io_op+0x45/0x7e Dec 12 16:16:18 xen kernel: [] end_block_io_op+0x0/0x7e Dec 12 16:16:18 xen kernel: [] bio_endio+0x50/0x55 Dec 12 16:16:18 xen kernel: [] dec_pending+0x9b/0xb3 [dm_mod] Dec 12 16:16:18 xen kernel: [] clone_endio+0x7c/0x94 [dm_mod] Dec 12 16:16:18 xen kernel: [] clone_endio+0x0/0x94 [dm_mod] Dec 12 16:16:18 xen kernel: [] bio_endio+0x50/0x55 Dec 12 16:16:18 xen kernel: [] __end_that_request_first+0x11b/0x422 Dec 12 16:16:18 xen kernel: [] del_timer+0x41/0x47 Dec 12 16:16:18 xen kernel: [] scsi_end_request+0x1a/0xa9 [scsi_mod] Dec 12 16:16:18 xen kernel: [] mempool_free+0x5f/0x63 Dec 12 16:16:18 xen kernel: [] scsi_io_completion+0x143/0x2ed [scsi_mod] Dec 12 16:16:18 xen kernel: [] unmask_evtchn+0x26/0xba Dec 12 16:16:18 xen kernel: [] sd_rw_intr+0x1eb/0x215 [sd_mod] Dec 12 16:16:18 xen kernel: [] _spin_lock_irqsave+0x8/0x28 Dec 12 16:16:18 xen kernel: [] scsi_finish_command+0x73/0x77 [scsi_mod] Dec 12 16:16:18 xen kernel: [] blk_done_softirq+0x55/0x60 Dec 12 16:16:18 xen kernel: [] __do_softirq+0x5e/0xc3 Dec 12 16:16:18 xen kernel: [] do_softirq+0x3a/0x4a Dec 12 16:16:18 xen kernel: [] do_IRQ+0x48/0x53 Dec 12 16:16:18 xen kernel: [] evtchn_do_upcall+0x64/0x9b Dec 12 16:16:18 xen kernel: [] hypervisor_callback+0x3d/0x48 Dec 12 16:16:18 xen kernel: [] raw_safe_halt+0x8c/0xaf Dec 12 16:16:18 xen kernel: [] xen_idle+0x22/0x2e Dec 12 16:16:18 xen kernel: [] cpu_idle+0x91/0xab Dec 12 16:16:18 xen kernel: [] start_kernel+0x378/0x37f It''s apparently an Irq conflict but i don''t know why? Do someone have an idea? Thanks. Julien. Julien Reveillet a écrit : Hello everybody, I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i have a new problem, and a big one. My ethernet card is dropping packets but after some time (i can''t tell how) It can work for a day (not in production so not hard tested) and then all packets are dropped. Look at the ifconfig output : eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:192.168.9.52 Bcast:192.168.9.255 Mask:255.255.255.0 inet6 addr: fe80::213:72ff:fe0f:1c6a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10505 errors:0 dropped: 352 overruns:0 frame:0 TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2223312 (2.1 MiB) TX bytes:555445 (542.4 KiB) Base address:0xcce0 Memory:fe3e0000-fe400000 Today, nothing was done on it but, a few minutes before, i realised that it was down. Dmesg output : ... Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI Copyright (c) 1999-2006 Intel Corporation. PCI: Enabling device 0000:00:01.0 (0000 -> 0003) PCI: Setting latency timer of device 0000:00:01.0 to 64 e1000: 0000:00:01.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) xx:xx:xx:xx:xx:xx e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver NET: Registered protocol family 5 eth0: no IPv6 routers present The interface is still up. I saw while googling that it could be an hardware problem but this was not in a xen environnement so... Anybody have seen this before? Thanks. Best Regards. Julien. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Boudreau Luc
2007-Dec-12 18:12 UTC
RE: [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device dropping packets
I got this error lately. It turns out that I was passing a device through PCI
passthrough and this device was given an IRQ (from domU) which conflicted with a
IRQ number already used by dom0.
Take a look at your current attributed IRQs in dom0 and your domUs and try to
see if there might be any conflict.
De : xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] De la part de Julien Reveillet
Envoyé : 12 décembre 2007 10:26
À : xen-users@lists.xensource.com
Objet : [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device
dropping packets
Hi everyone,
Here is what my Xen Dom0 syslog daemon reports after a freeze of my CentOs DomU
network interface :
xen kernel: Disabling IRQ #17
Dec 12 16:16:18 xen kernel: [<c013af97>] __report_bad_irq+0x2b/0x69
Dec 12 16:16:18 xen kernel: [<c013b188>] note_interrupt+0x1b3/0x1eb
Dec 12 16:16:18 xen kernel: [<c013a7ed>] handle_IRQ_event+0x49/0x51
Dec 12 16:16:18 xen kernel: [<c013a8a8>] __do_IRQ+0xb3/0xe8
Dec 12 16:16:18 xen kernel: [<c010612c>] do_IRQ+0x43/0x53
Dec 12 16:16:18 xen kernel: [<c020c1cc>] evtchn_do_upcall+0x64/0x9b
Dec 12 16:16:18 xen kernel: [<c0104a51>] hypervisor_callback+0x3d/0x48
Dec 12 16:16:18 xen kernel: [<c020bbb1>] notify_remote_via_irq+0x27/0x5f
Dec 12 16:16:18 xen kernel: [<c021359b>] blkif_notify_work+0x1b/0x1d
Dec 12 16:16:18 xen kernel: [<c02137b3>] make_response+0xeb/0x12f
Dec 12 16:16:18 xen kernel: [<c021383c>] end_block_io_op+0x45/0x7e
Dec 12 16:16:18 xen kernel: [<c02137f7>] end_block_io_op+0x0/0x7e
Dec 12 16:16:18 xen kernel: [<c015d715>] bio_endio+0x50/0x55
Dec 12 16:16:18 xen kernel: [<ee1a62da>] dec_pending+0x9b/0xb3 [dm_mod]
Dec 12 16:16:18 xen kernel: [<ee1a63de>] clone_endio+0x7c/0x94 [dm_mod]
Dec 12 16:16:18 xen kernel: [<ee1a6362>] clone_endio+0x0/0x94 [dm_mod]
Dec 12 16:16:18 xen kernel: [<c015d715>] bio_endio+0x50/0x55
Dec 12 16:16:18 xen kernel: [<c01ad07b>]
__end_that_request_first+0x11b/0x422
Dec 12 16:16:18 xen kernel: [<c0123662>] del_timer+0x41/0x47
Dec 12 16:16:18 xen kernel: [<ee0e2055>] scsi_end_request+0x1a/0xa9
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c013ebec>] mempool_free+0x5f/0x63
Dec 12 16:16:18 xen kernel: [<ee0e2227>] scsi_io_completion+0x143/0x2ed
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c020bcf2>] unmask_evtchn+0x26/0xba
Dec 12 16:16:18 xen kernel: [<ee16f3b2>] sd_rw_intr+0x1eb/0x215 [sd_mod]
Dec 12 16:16:18 xen kernel: [<c0289aa0>] _spin_lock_irqsave+0x8/0x28
Dec 12 16:16:18 xen kernel: [<ee0de3bd>] scsi_finish_command+0x73/0x77
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c01af180>] blk_done_softirq+0x55/0x60
Dec 12 16:16:18 xen kernel: [<c011f41e>] __do_softirq+0x5e/0xc3
Dec 12 16:16:18 xen kernel: [<c011f4bd>] do_softirq+0x3a/0x4a
Dec 12 16:16:18 xen kernel: [<c0106131>] do_IRQ+0x48/0x53
Dec 12 16:16:18 xen kernel: [<c020c1cc>] evtchn_do_upcall+0x64/0x9b
Dec 12 16:16:18 xen kernel: [<c0104a51>] hypervisor_callback+0x3d/0x48
Dec 12 16:16:18 xen kernel: [<c0107342>] raw_safe_halt+0x8c/0xaf
Dec 12 16:16:18 xen kernel: [<c0102c5f>] xen_idle+0x22/0x2e
Dec 12 16:16:18 xen kernel: [<c0102d7e>] cpu_idle+0x91/0xab
Dec 12 16:16:18 xen kernel: [<c03236fc>] start_kernel+0x378/0x37f
It''s apparently an Irq conflict but i don''t know why?
Do someone have an idea?
Thanks.
Julien.
Julien Reveillet a écrit :
Hello everybody,
I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i
have a new problem, and a big one.
My ethernet card is dropping packets but after some time (i can''t tell
how)
It can work for a day (not in production so not hard tested) and then all
packets are dropped.
Look at the ifconfig output :
eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.9.52 Bcast:192.168.9.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fe0f:1c6a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10505 errors:0 dropped: 352 overruns:0 frame:0
TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2223312 (2.1 MiB) TX bytes:555445 (542.4 KiB)
Base address:0xcce0 Memory:fe3e0000-fe400000
Today, nothing was done on it but, a few minutes before, i realised that it was
down.
Dmesg output :
...
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
PCI: Enabling device 0000:00:01.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:00:01.0 to 64
e1000: 0000:00:01.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1)
xx:xx:xx:xx:xx:xx
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 5
eth0: no IPv6 routers present
The interface is still up.
I saw while googling that it could be an hardware problem but this was not in a
xen environnement so...
Anybody have seen this before?
Thanks.
Best Regards.
Julien.
________________________________
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Boudreau Luc
2007-Dec-12 18:21 UTC
RE: [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device dropping packets
BTW. The syntax to display currently assigned IRQs is
# cat /proc/interrupts
De : xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] De la part de Julien Reveillet
Envoyé : 12 décembre 2007 10:26
À : xen-users@lists.xensource.com
Objet : [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device
dropping packets
Hi everyone,
Here is what my Xen Dom0 syslog daemon reports after a freeze of my CentOs DomU
network interface :
xen kernel: Disabling IRQ #17
Dec 12 16:16:18 xen kernel: [<c013af97>] __report_bad_irq+0x2b/0x69
Dec 12 16:16:18 xen kernel: [<c013b188>] note_interrupt+0x1b3/0x1eb
Dec 12 16:16:18 xen kernel: [<c013a7ed>] handle_IRQ_event+0x49/0x51
Dec 12 16:16:18 xen kernel: [<c013a8a8>] __do_IRQ+0xb3/0xe8
Dec 12 16:16:18 xen kernel: [<c010612c>] do_IRQ+0x43/0x53
Dec 12 16:16:18 xen kernel: [<c020c1cc>] evtchn_do_upcall+0x64/0x9b
Dec 12 16:16:18 xen kernel: [<c0104a51>] hypervisor_callback+0x3d/0x48
Dec 12 16:16:18 xen kernel: [<c020bbb1>] notify_remote_via_irq+0x27/0x5f
Dec 12 16:16:18 xen kernel: [<c021359b>] blkif_notify_work+0x1b/0x1d
Dec 12 16:16:18 xen kernel: [<c02137b3>] make_response+0xeb/0x12f
Dec 12 16:16:18 xen kernel: [<c021383c>] end_block_io_op+0x45/0x7e
Dec 12 16:16:18 xen kernel: [<c02137f7>] end_block_io_op+0x0/0x7e
Dec 12 16:16:18 xen kernel: [<c015d715>] bio_endio+0x50/0x55
Dec 12 16:16:18 xen kernel: [<ee1a62da>] dec_pending+0x9b/0xb3 [dm_mod]
Dec 12 16:16:18 xen kernel: [<ee1a63de>] clone_endio+0x7c/0x94 [dm_mod]
Dec 12 16:16:18 xen kernel: [<ee1a6362>] clone_endio+0x0/0x94 [dm_mod]
Dec 12 16:16:18 xen kernel: [<c015d715>] bio_endio+0x50/0x55
Dec 12 16:16:18 xen kernel: [<c01ad07b>]
__end_that_request_first+0x11b/0x422
Dec 12 16:16:18 xen kernel: [<c0123662>] del_timer+0x41/0x47
Dec 12 16:16:18 xen kernel: [<ee0e2055>] scsi_end_request+0x1a/0xa9
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c013ebec>] mempool_free+0x5f/0x63
Dec 12 16:16:18 xen kernel: [<ee0e2227>] scsi_io_completion+0x143/0x2ed
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c020bcf2>] unmask_evtchn+0x26/0xba
Dec 12 16:16:18 xen kernel: [<ee16f3b2>] sd_rw_intr+0x1eb/0x215 [sd_mod]
Dec 12 16:16:18 xen kernel: [<c0289aa0>] _spin_lock_irqsave+0x8/0x28
Dec 12 16:16:18 xen kernel: [<ee0de3bd>] scsi_finish_command+0x73/0x77
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c01af180>] blk_done_softirq+0x55/0x60
Dec 12 16:16:18 xen kernel: [<c011f41e>] __do_softirq+0x5e/0xc3
Dec 12 16:16:18 xen kernel: [<c011f4bd>] do_softirq+0x3a/0x4a
Dec 12 16:16:18 xen kernel: [<c0106131>] do_IRQ+0x48/0x53
Dec 12 16:16:18 xen kernel: [<c020c1cc>] evtchn_do_upcall+0x64/0x9b
Dec 12 16:16:18 xen kernel: [<c0104a51>] hypervisor_callback+0x3d/0x48
Dec 12 16:16:18 xen kernel: [<c0107342>] raw_safe_halt+0x8c/0xaf
Dec 12 16:16:18 xen kernel: [<c0102c5f>] xen_idle+0x22/0x2e
Dec 12 16:16:18 xen kernel: [<c0102d7e>] cpu_idle+0x91/0xab
Dec 12 16:16:18 xen kernel: [<c03236fc>] start_kernel+0x378/0x37f
It''s apparently an Irq conflict but i don''t know why?
Do someone have an idea?
Thanks.
Julien.
Julien Reveillet a écrit :
Hello everybody,
I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i
have a new problem, and a big one.
My ethernet card is dropping packets but after some time (i can''t tell
how)
It can work for a day (not in production so not hard tested) and then all
packets are dropped.
Look at the ifconfig output :
eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.9.52 Bcast:192.168.9.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fe0f:1c6a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10505 errors:0 dropped: 352 overruns:0 frame:0
TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2223312 (2.1 MiB) TX bytes:555445 (542.4 KiB)
Base address:0xcce0 Memory:fe3e0000-fe400000
Today, nothing was done on it but, a few minutes before, i realised that it was
down.
Dmesg output :
...
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
PCI: Enabling device 0000:00:01.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:00:01.0 to 64
e1000: 0000:00:01.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1)
xx:xx:xx:xx:xx:xx
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 5
eth0: no IPv6 routers present
The interface is still up.
I saw while googling that it could be an hardware problem but this was not in a
xen environnement so...
Anybody have seen this before?
Thanks.
Best Regards.
Julien.
________________________________
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Boudreau Luc
2007-Dec-12 20:38 UTC
RE: [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device dropping packets
I strongly suggest avoiding shared IRQs between dom0 and domUs. As you can see,
your IRQ 17 is shared and it is this exact same IRQ that appears in your error
message.
One easy fix is to move your Ethernet card into another PCI slot. I
didn''t find how to explicitly define an IRQ number for a given device,
but I suspect it is within your BIOS config.
Cheers !
De : Julien Reveillet [mailto:j.reveillet@graphique-alliance.com]
Envoyé : 12 décembre 2007 15:29
À : Boudreau Luc
Objet : Re: [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel)
device dropping packets
Hi,
Thanks for your help.
Here are the interrupts used by my DomU (CentOs) with the dedicated e1000:
CPU0
17: 99997 Phys-irq eth0
18: 0 Phys-irq uhci_hcd:usb1
256: 293664 Dynamic-irq timer0
257: 0 Dynamic-irq resched0
258: 0 Dynamic-irq callfunc0
259: 558 Dynamic-irq xenbus
260: 834 Dynamic-irq xencons
261: 2666 Dynamic-irq blkif
262: 3 Dynamic-irq blkif
263: 18 Dynamic-irq blkif
264: 219 Dynamic-irq blkif
265: 814 Dynamic-irq blkif
266: 983 Dynamic-irq blkif
267: 39548 Dynamic-irq blkif
NMI: 0
LOC: 0
ERR: 0
MIS: 0
And here are the interrupts in the DomU :
8: 1 Phys-irq rtc
9: 0 Phys-irq acpi
14: 74 Phys-irq ide0
17: 100000 Phys-irq ohci1394
18: 279 Phys-irq ehci_hcd:usb1
19: 569 Phys-irq uhci_hcd:usb2
20: 191699 Phys-irq uhci_hcd:usb3, peth2
21: 0 Phys-irq uhci_hcd:usb4
22: 29277 Phys-irq libata
256: 1384176 Dynamic-irq timer0
257: 943 Dynamic-irq resched0
258: 36 Dynamic-irq callfunc0
259: 6834 Dynamic-irq blkif-backend
260: 38 Dynamic-irq blkif-backend
261: 75310 Dynamic-irq vif4.0
262: 8614 Dynamic-irq xenbus
263: 0 Dynamic-irq console
264: 355 Dynamic-irq pciback
265: 1928 Dynamic-irq blkif-backend
266: 4 Dynamic-irq blkif-backend
267: 16 Dynamic-irq blkif-backend
268: 180 Dynamic-irq blkif-backend
269: 535 Dynamic-irq blkif-backend
270: 530 Dynamic-irq blkif-backend
271: 359 Dynamic-irq blkif-backend
NMI: 0
LOC: 0
ERR: 0
MIS: 0
As i see, there is no conflicts in the same virtual machine.
Is there a need that Irqs are différents between DomU(s) and Dom0?
Thanks in advance.
Julien.
PS: Bien le bonjour à vous Canadien.
Boudreau Luc a écrit :
BTW. The syntax to display currently assigned IRQs is
# cat /proc/interrupts
De : xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] De la part de Julien Reveillet
Envoyé : 12 décembre 2007 10:26
À : xen-users@lists.xensource.com
Objet : [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device
dropping packets
Hi everyone,
Here is what my Xen Dom0 syslog daemon reports after a freeze of my CentOs DomU
network interface :
xen kernel: Disabling IRQ #17
Dec 12 16:16:18 xen kernel: [<c013af97>] __report_bad_irq+0x2b/0x69
Dec 12 16:16:18 xen kernel: [<c013b188>] note_interrupt+0x1b3/0x1eb
Dec 12 16:16:18 xen kernel: [<c013a7ed>] handle_IRQ_event+0x49/0x51
Dec 12 16:16:18 xen kernel: [<c013a8a8>] __do_IRQ+0xb3/0xe8
Dec 12 16:16:18 xen kernel: [<c010612c>] do_IRQ+0x43/0x53
Dec 12 16:16:18 xen kernel: [<c020c1cc>] evtchn_do_upcall+0x64/0x9b
Dec 12 16:16:18 xen kernel: [<c0104a51>] hypervisor_callback+0x3d/0x48
Dec 12 16:16:18 xen kernel: [<c020bbb1>] notify_remote_via_irq+0x27/0x5f
Dec 12 16:16:18 xen kernel: [<c021359b>] blkif_notify_work+0x1b/0x1d
Dec 12 16:16:18 xen kernel: [<c02137b3>] make_response+0xeb/0x12f
Dec 12 16:16:18 xen kernel: [<c021383c>] end_block_io_op+0x45/0x7e
Dec 12 16:16:18 xen kernel: [<c02137f7>] end_block_io_op+0x0/0x7e
Dec 12 16:16:18 xen kernel: [<c015d715>] bio_endio+0x50/0x55
Dec 12 16:16:18 xen kernel: [<ee1a62da>] dec_pending+0x9b/0xb3 [dm_mod]
Dec 12 16:16:18 xen kernel: [<ee1a63de>] clone_endio+0x7c/0x94 [dm_mod]
Dec 12 16:16:18 xen kernel: [<ee1a6362>] clone_endio+0x0/0x94 [dm_mod]
Dec 12 16:16:18 xen kernel: [<c015d715>] bio_endio+0x50/0x55
Dec 12 16:16:18 xen kernel: [<c01ad07b>]
__end_that_request_first+0x11b/0x422
Dec 12 16:16:18 xen kernel: [<c0123662>] del_timer+0x41/0x47
Dec 12 16:16:18 xen kernel: [<ee0e2055>] scsi_end_request+0x1a/0xa9
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c013ebec>] mempool_free+0x5f/0x63
Dec 12 16:16:18 xen kernel: [<ee0e2227>] scsi_io_completion+0x143/0x2ed
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c020bcf2>] unmask_evtchn+0x26/0xba
Dec 12 16:16:18 xen kernel: [<ee16f3b2>] sd_rw_intr+0x1eb/0x215 [sd_mod]
Dec 12 16:16:18 xen kernel: [<c0289aa0>] _spin_lock_irqsave+0x8/0x28
Dec 12 16:16:18 xen kernel: [<ee0de3bd>] scsi_finish_command+0x73/0x77
[scsi_mod]
Dec 12 16:16:18 xen kernel: [<c01af180>] blk_done_softirq+0x55/0x60
Dec 12 16:16:18 xen kernel: [<c011f41e>] __do_softirq+0x5e/0xc3
Dec 12 16:16:18 xen kernel: [<c011f4bd>] do_softirq+0x3a/0x4a
Dec 12 16:16:18 xen kernel: [<c0106131>] do_IRQ+0x48/0x53
Dec 12 16:16:18 xen kernel: [<c020c1cc>] evtchn_do_upcall+0x64/0x9b
Dec 12 16:16:18 xen kernel: [<c0104a51>] hypervisor_callback+0x3d/0x48
Dec 12 16:16:18 xen kernel: [<c0107342>] raw_safe_halt+0x8c/0xaf
Dec 12 16:16:18 xen kernel: [<c0102c5f>] xen_idle+0x22/0x2e
Dec 12 16:16:18 xen kernel: [<c0102d7e>] cpu_idle+0x91/0xab
Dec 12 16:16:18 xen kernel: [<c03236fc>] start_kernel+0x378/0x37f
It''s apparently an Irq conflict but i don''t know why?
Do someone have an idea?
Thanks.
Julien.
Julien Reveillet a écrit :
Hello everybody,
I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i
have a new problem, and a big one.
My ethernet card is dropping packets but after some time (i can''t tell
how)
It can work for a day (not in production so not hard tested) and then all
packets are dropped.
Look at the ifconfig output :
eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.9.52 Bcast:192.168.9.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fe0f:1c6a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10505 errors:0 dropped: 352 overruns:0 frame:0
TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2223312 (2.1 MiB) TX bytes:555445 (542.4 KiB)
Base address:0xcce0 Memory:fe3e0000-fe400000
Today, nothing was done on it but, a few minutes before, i realised that it was
down.
Dmesg output :
...
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
PCI: Enabling device 0000:00:01.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:00:01.0 to 64
e1000: 0000:00:01.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1)
xx:xx:xx:xx:xx:xx
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 5
eth0: no IPv6 routers present
The interface is still up.
I saw while googling that it could be an hardware problem but this was not in a
xen environnement so...
Anybody have seen this before?
Thanks.
Best Regards.
Julien.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
________________________________
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Julien Reveillet
2007-Dec-17 09:24 UTC
Re: [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device dropping packets
Hi, Just want to thanks you for your explanations. I saw while watching other posts that you had the same problem to me ;-) You were right but, as the ethernet was a built in one and the bios wasn''t configurable, i had to switch my firewire card (the other card sharing irq 17). It is a Dell computer with many good features but no way to configure Irq sharing, not pro... Well, now it works like a charm, and this is what i wanted. Thanks. Julien. Boudreau Luc a écrit : I strongly suggest avoiding shared IRQs between dom0 and domUs. As you can see, your IRQ 17 is shared and it is this exact same IRQ that appears in your error message. One easy fix is to move your Ethernet card into another PCI slot. I didn’t find how to explicitly define an IRQ number for a given device, but I suspect it is within your BIOS config. Cheers ! De : Julien Reveillet [mailto:j.reveillet@graphique-alliance.com] Envoyé : 12 décembre 2007 15:29 À : Boudreau Luc Objet : Re: [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device dropping packets Hi, Thanks for your help. Here are the interrupts used by my DomU (CentOs) with the dedicated e1000: CPU0 17: 99997 Phys-irq eth0 18: 0 Phys-irq uhci_hcd:usb1 256: 293664 Dynamic-irq timer0 257: 0 Dynamic-irq resched0 258: 0 Dynamic-irq callfunc0 259: 558 Dynamic-irq xenbus 260: 834 Dynamic-irq xencons 261: 2666 Dynamic-irq blkif 262: 3 Dynamic-irq blkif 263: 18 Dynamic-irq blkif 264: 219 Dynamic-irq blkif 265: 814 Dynamic-irq blkif 266: 983 Dynamic-irq blkif 267: 39548 Dynamic-irq blkif NMI: 0 LOC: 0 ERR: 0 MIS: 0 And here are the interrupts in the DomU : 8: 1 Phys-irq rtc 9: 0 Phys-irq acpi 14: 74 Phys-irq ide0 17: 100000 Phys-irq ohci1394 18: 279 Phys-irq ehci_hcd:usb1 19: 569 Phys-irq uhci_hcd:usb2 20: 191699 Phys-irq uhci_hcd:usb3, peth2 21: 0 Phys-irq uhci_hcd:usb4 22: 29277 Phys-irq libata 256: 1384176 Dynamic-irq timer0 257: 943 Dynamic-irq resched0 258: 36 Dynamic-irq callfunc0 259: 6834 Dynamic-irq blkif-backend 260: 38 Dynamic-irq blkif-backend 261: 75310 Dynamic-irq vif4.0 262: 8614 Dynamic-irq xenbus 263: 0 Dynamic-irq console 264: 355 Dynamic-irq pciback 265: 1928 Dynamic-irq blkif-backend 266: 4 Dynamic-irq blkif-backend 267: 16 Dynamic-irq blkif-backend 268: 180 Dynamic-irq blkif-backend 269: 535 Dynamic-irq blkif-backend 270: 530 Dynamic-irq blkif-backend 271: 359 Dynamic-irq blkif-backend NMI: 0 LOC: 0 ERR: 0 MIS: 0 As i see, there is no conflicts in the same virtual machine. Is there a need that Irqs are différents between DomU(s) and Dom0? Thanks in advance. Julien. PS: Bien le bonjour à vous Canadien. Boudreau Luc a écrit : BTW. The syntax to display currently assigned IRQs is # cat /proc/interrupts De : xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] De la part de Julien Reveillet Envoyé : 12 décembre 2007 10:26 À : xen-users@lists.xensource.com Objet : [Xen-users] Re: HELP DomU (Centos 5) with dedicated e1000 (intel) device dropping packets Hi everyone, Here is what my Xen Dom0 syslog daemon reports after a freeze of my CentOs DomU network interface : xen kernel: Disabling IRQ #17 Dec 12 16:16:18 xen kernel: [] __report_bad_irq+0x2b/0x69 Dec 12 16:16:18 xen kernel: [] note_interrupt+0x1b3/0x1eb Dec 12 16:16:18 xen kernel: [] handle_IRQ_event+0x49/0x51 Dec 12 16:16:18 xen kernel: [] __do_IRQ+0xb3/0xe8 Dec 12 16:16:18 xen kernel: [] do_IRQ+0x43/0x53 Dec 12 16:16:18 xen kernel: [] evtchn_do_upcall+0x64/0x9b Dec 12 16:16:18 xen kernel: [] hypervisor_callback+0x3d/0x48 Dec 12 16:16:18 xen kernel: [] notify_remote_via_irq+0x27/0x5f Dec 12 16:16:18 xen kernel: [] blkif_notify_work+0x1b/0x1d Dec 12 16:16:18 xen kernel: [] make_response+0xeb/0x12f Dec 12 16:16:18 xen kernel: [] end_block_io_op+0x45/0x7e Dec 12 16:16:18 xen kernel: [] end_block_io_op+0x0/0x7e Dec 12 16:16:18 xen kernel: [] bio_endio+0x50/0x55 Dec 12 16:16:18 xen kernel: [] dec_pending+0x9b/0xb3 [dm_mod] Dec 12 16:16:18 xen kernel: [] clone_endio+0x7c/0x94 [dm_mod] Dec 12 16:16:18 xen kernel: [] clone_endio+0x0/0x94 [dm_mod] Dec 12 16:16:18 xen kernel: [] bio_endio+0x50/0x55 Dec 12 16:16:18 xen kernel: [] __end_that_request_first+0x11b/0x422 Dec 12 16:16:18 xen kernel: [] del_timer+0x41/0x47 Dec 12 16:16:18 xen kernel: [] scsi_end_request+0x1a/0xa9 [scsi_mod] Dec 12 16:16:18 xen kernel: [] mempool_free+0x5f/0x63 Dec 12 16:16:18 xen kernel: [] scsi_io_completion+0x143/0x2ed [scsi_mod] Dec 12 16:16:18 xen kernel: [] unmask_evtchn+0x26/0xba Dec 12 16:16:18 xen kernel: [] sd_rw_intr+0x1eb/0x215 [sd_mod] Dec 12 16:16:18 xen kernel: [] _spin_lock_irqsave+0x8/0x28 Dec 12 16:16:18 xen kernel: [] scsi_finish_command+0x73/0x77 [scsi_mod] Dec 12 16:16:18 xen kernel: [] blk_done_softirq+0x55/0x60 Dec 12 16:16:18 xen kernel: [] __do_softirq+0x5e/0xc3 Dec 12 16:16:18 xen kernel: [] do_softirq+0x3a/0x4a Dec 12 16:16:18 xen kernel: [] do_IRQ+0x48/0x53 Dec 12 16:16:18 xen kernel: [] evtchn_do_upcall+0x64/0x9b Dec 12 16:16:18 xen kernel: [] hypervisor_callback+0x3d/0x48 Dec 12 16:16:18 xen kernel: [] raw_safe_halt+0x8c/0xaf Dec 12 16:16:18 xen kernel: [] xen_idle+0x22/0x2e Dec 12 16:16:18 xen kernel: [] cpu_idle+0x91/0xab Dec 12 16:16:18 xen kernel: [] start_kernel+0x378/0x37f It''s apparently an Irq conflict but i don''t know why? Do someone have an idea? Thanks. Julien. Julien Reveillet a écrit : Hello everybody, I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i have a new problem, and a big one. My ethernet card is dropping packets but after some time (i can''t tell how) It can work for a day (not in production so not hard tested) and then all packets are dropped. Look at the ifconfig output : eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:192.168.9.52 Bcast:192.168.9.255 Mask:255.255.255.0 inet6 addr: fe80::213:72ff:fe0f:1c6a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10505 errors:0 dropped: 352 overruns:0 frame:0 TX packets:2921 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2223312 (2.1 MiB) TX bytes:555445 (542.4 KiB) Base address:0xcce0 Memory:fe3e0000-fe400000 Today, nothing was done on it but, a few minutes before, i realised that it was down. Dmesg output : ... Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI Copyright (c) 1999-2006 Intel Corporation. PCI: Enabling device 0000:00:01.0 (0000 -> 0003) PCI: Setting latency timer of device 0000:00:01.0 to 64 e1000: 0000:00:01.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) xx:xx:xx:xx:xx:xx e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver NET: Registered protocol family 5 eth0: no IPv6 routers present The interface is still up. I saw while googling that it could be an hardware problem but this was not in a xen environnement so... Anybody have seen this before? Thanks. Best Regards. Julien. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users -- ____________________________________ Julien Reveillet j.reveillet@graphique-alliance.com GraphiqueAlliance Solution pré-presse et gestion de documents Centre Emeraude Cidex 3 61/69 Rue Camille Pelletan 33150 CENON Tél. 05 56 67 55 78 Fax. 05 57 54 12 77 www.graphique-alliance.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users