From: Gerd Knorr <kraxel@suse.de>
To: xen-devel@lists.xensource.com
Subject: network (irq?) problems in unstable
Date: Mon, 30 May 2005 14:52:47 +0200 [thread overview]
Message-ID: <20050530125247.GA12140@bytesex> (raw)
Hi,
With xen unstable I have the problem that the network stops
working after a while. Heavy network traffic seems to make it
more likely, it triggers almost every time I try to untar a
kernel source tree, where the tarball comes from a NFS-mounted
volume.
The network card doesn't receive interrupts any more according
to /proc/interrupts. It works fine in native linux and also
with xen 2.0. It's a tulip card. Anyone has an idea what this
might be or where to look?
Gerd
/proc/interrupts in native linux:
CPU0
0: 613024 XT-PIC timer
1: 673 XT-PIC i8042
2: 0 XT-PIC cascade
5: 3460 XT-PIC sym53c8xx
7: 1 XT-PIC parport0
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi, uhci_hcd
10: 0 XT-PIC Ensoniq AudioPCI
11: 1131 XT-PIC eth0
12: 446 XT-PIC i8042
14: 313 XT-PIC ide0
15: 9492 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
/proc/interrupts in domain0, unstable:
CPU0
1: 113 Phys-irq i8042
5: 2521 Phys-irq sym53c8xx
9: 0 Phys-irq acpi
11: 779 Phys-irq hw-eth0
256: 0 Dynamic-irq ctrl-if
257: 15736 Dynamic-irq timer0
258: 0 Dynamic-irq console
259: 0 Dynamic-irq net-be-dbg
NMI: 0
LOC: 0
ERR: 0
MIS: 0
next reply other threads:[~2005-05-30 12:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 12:52 Gerd Knorr [this message]
2005-05-30 13:36 ` network (irq?) problems in unstable Keir Fraser
2005-05-31 10:18 ` Gerd Knorr
2005-05-31 10:59 ` Keir Fraser
2005-05-31 11:36 ` Gerd Knorr
2005-05-31 18:21 ` Hypercall interface changes for PAE Keir Fraser
2005-05-31 18:26 ` Keir Fraser
2005-05-31 19:02 ` Gerd Knorr
2005-05-31 19:23 ` Keir Fraser
2005-05-31 20:38 ` Gerd Knorr
2005-05-31 21:18 ` Keir Fraser
2005-05-31 21:40 ` Keir Fraser
2005-05-31 22:25 ` David Hopwood
2005-05-31 18:32 ` Jonathan S. Shapiro
2005-05-31 18:37 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050530125247.GA12140@bytesex \
--to=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.