From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: [pv_ops] e1000e: "Detected Tx Unit Hang"
Date: Fri, 21 May 2010 01:22:19 +0200 [thread overview]
Message-ID: <4BF5C42B.3050706@access.denied> (raw)
In-Reply-To: <4BF5BF3E.2010708@goop.org>
[-- Attachment #1.1: Type: text/plain, Size: 4324 bytes --]
Am 21.05.2010 01:01, schrieb Jeremy Fitzhardinge:
Hello Jeremy,
> OK, definitely different problem. Does it happen immediately, or after
> a while? Under load? Can you provide the full boot output, and cat
> /proc/interrupts?
>
It happen under copy from domU to physical PC.
Boot output from dom0 (dmesg)?
root@Overmind:~# cat /proc/interrupts
CPU0 CPU1
1: 8 0 xen-pirq-ioapic-edge i8042
8: 0 0 xen-pirq-ioapic-edge rtc0
9: 926014 0 xen-pirq-ioapic-level acpi
12: 22 0 xen-pirq-ioapic-edge i8042
14: 129 0 xen-pirq-ioapic-edge ide0
16: 887 0 xen-pirq-ioapic-level uhci_hcd:usb5,
firewire_ohci
17: 0 0 xen-pirq-ioapic-level mmc0
18: 0 0 xen-pirq-ioapic-level uhci_hcd:usb4
19: 0 0 xen-pirq-ioapic-level uhci_hcd:usb3
22: 72 0 xen-pirq-ioapic-level HDA Intel
23: 31 0 xen-pirq-ioapic-level ehci_hcd:usb1,
uhci_hcd:usb2
381: 15770007 0 xen-dyn-event vif6.0
382: 85431 0 xen-dyn-event blkif-backend
383: 386 0 xen-dyn-event evtchn:xenconsoled
384: 139 0 xen-dyn-event evtchn:xenstored
385: 42592 0 xen-dyn-event vif5.0
386: 65335 0 xen-dyn-event blkif-backend
387: 315 0 xen-dyn-event evtchn:xenconsoled
388: 139 0 xen-dyn-event evtchn:xenstored
389: 43 0 xen-dyn-event vif4.0
390: 1306 0 xen-dyn-event blkif-backend
391: 123 0 xen-dyn-event evtchn:xenconsoled
392: 135 0 xen-dyn-event evtchn:xenstored
393: 6588 0 xen-dyn-event vif3.0
394: 6723 0 xen-dyn-event blkif-backend
395: 319 0 xen-dyn-event evtchn:xenconsoled
396: 265 0 xen-dyn-event evtchn:xenstored
397: 108544 0 xen-dyn-event vif2.0
398: 315 0 xen-dyn-event blkif-backend
399: 87 0 xen-dyn-event evtchn:xenconsoled
400: 128 0 xen-dyn-event evtchn:xenstored
401: 13477877 0 xen-dyn-event vif1.0
402: 866835 0 xen-dyn-event blkif-backend
403: 28802 0 xen-dyn-event blkif-backend
404: 300 0 xen-dyn-event evtchn:xenconsoled
405: 220 0 xen-dyn-event evtchn:xenstored
406: 0 0 xen-dyn-event evtchn:xenstored
407: 2460 0 xen-dyn-event evtchn:xenstored
408: 2953808 0 xen-pirq-msi ahci
409: 8689919 0 xen-pirq-msi peth0
412: 0 0 xen-dyn-virq pcpu
413: 4550 0 xen-dyn-event xenbus
414: 0 403 xen-dyn-ipi callfuncsingle1
415: 0 0 xen-dyn-virq debug1
416: 0 0 xen-dyn-ipi callfunc1
417: 0 104331 xen-dyn-ipi resched1
418: 0 53769606 xen-dyn-virq timer1
419: 221 0 xen-dyn-ipi callfuncsingle0
420: 0 0 xen-dyn-virq debug0
421: 0 0 xen-dyn-ipi callfunc0
422: 264761 0 xen-dyn-ipi resched0
423: 53761166 0 xen-dyn-virq timer0
NMI: 0 0 Non-maskable interrupts
LOC: 0 0 Local timer interrupts
SPU: 0 0 Spurious interrupts
CNT: 0 0 Performance counter interrupts
PND: 0 0 Performance pending work
RES: 264761 104331 Rescheduling interrupts
CAL: 221 403 Function call interrupts
TLB: 0 0 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 180 180 Machine check polls
ERR: 0
MIS: 0
root@Overmind:~#
I've no PCI device forwarded.
Regards,
Stefan Kuhne
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-20 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 21:45 [pv_ops] e1000e: "Detected Tx Unit Hang" Stefan Kuhne
2010-05-20 22:18 ` Jeremy Fitzhardinge
2010-05-20 22:58 ` Stefan Kuhne
2010-05-20 23:01 ` Jeremy Fitzhardinge
2010-05-20 23:21 ` AW: " Heiko Wundram
2010-05-23 0:16 ` Stefan Kuhne
2010-05-20 23:22 ` Stefan Kuhne [this message]
2010-05-22 15:32 ` Thomas Goirand
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=4BF5C42B.3050706@access.denied \
--to=stefan.kuhne@gmx.net \
--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.