From: Gunnar Zarncke <gunnar@zarncke.de>
To: xen-devel@lists.xensource.com
Subject: Re: irq 17: nobody cared (try booting with the "irqpoll" option)
Date: Sun, 27 Jan 2008 21:07:35 +0100 [thread overview]
Message-ID: <479CE487.4040207@zarncke.de> (raw)
Hi,
I know it's a time since this question was posted and treated the last
time, but I have quite the same problem, only its IRQ #18 and some other
pci devices, but it's also a dom-u ("asterisk") with some devices moved
there 2xISDN and 1 soundcard. The problem halts the whole system (also
the dom-0 ("powerless")), hard reboot is needed. This happens some hours
after the dom-u (asterisk) is started. I'm right now trying the
noirqdebug workaround.
I think this occors since I move the soundcard into the asterisk
dom-u. I'd really be happy to keep it in the dom-0, but I don't see a
way to let the dom-u access it. I couldn't find a virtual sound card for
xen.
I would be grateful for any help.
Gunnar Zarncke
Debug data:
powerless:~# uname -a
Linux powerless 2.6.18-4-xen-686 #1 SMP Thu May 10 03:24:35 UTC 2007
i686 GNU/Li
powerless:~# cat /proc/interrupts
CPU0
1: 397 Phys-irq i8042
7: 0 Phys-irq parport0
8: 1 Phys-irq rtc
9: 0 Phys-irq acpi
14: 129799 Phys-irq ide0
18: 137 Phys-irq ohci_hcd:usb1
19: 36296 Phys-irq ohci_hcd:usb3, ohci_hcd:usb5, eth1
20: 39757 Phys-irq ehci_hcd:usb6, eth2
21: 229 Phys-irq libata
22: 0 Phys-irq ohci_hcd:usb2, ohci_hcd:usb4
256: 2114450 Dynamic-irq timer0
257: 0 Dynamic-irq resched0
258: 0 Dynamic-irq callfunc0
259: 4449 Dynamic-irq xenbus
260: 205 Dynamic-irq blkif-backend
261: 7596 Dynamic-irq blkif-backend
262: 30 Dynamic-irq blkif-backend
263: 22089 Dynamic-irq blkif-backend
264: 12909 Dynamic-irq vif2.0
265: 12000 Dynamic-irq vif2.1
266: 1 Dynamic-irq vif2.2
267: 423 Dynamic-irq pciback
268: 698 Dynamic-irq blkif-backend
269: 21 Dynamic-irq blkif-backend
270: 53 Dynamic-irq vif3.0
NMI: 0
LOC: 0
ERR: 0
MIS: 0
asterisk:~# cat /proc/interrupts
CPU0
16: 21 Phys-irq zaphfc
17: 1 Phys-irq zaphfc
18: 93 Phys-irq HDA Intel
256: 1779 Dynamic-irq timer0
257: 0 Dynamic-irq resched0
258: 0 Dynamic-irq callfunc0
259: 463 Dynamic-irq xenbus
260: 114 Dynamic-irq xencons
261: 1276 Dynamic-irq blkif
262: 20 Dynamic-irq blkif
263: 98 Dynamic-irq eth0
NMI: 0
LOC: 0
ERR: 0
MIS: 0
from dmesg:
pciback: vpci: 0000:04:05.0: assign to virtual slot 0
pciback: vpci: 0000:04:06.0: assign to virtual slot 1
pciback: vpci: 0000:00:14.2: assign to virtual slot 2
[...]
pciback 0000:00:14.2: Driver tried to write to a read-only configuration
space field at offset 0x54, size 2. This may be harmless, but if you
have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of
your device obtained from lspci.
PCI: Enabling device 0000:00:14.2 (0000 -> 0002)
ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 18
pciback 0000:04:05.0: Driver tried to write to a read-only configuration
space field at offset 0x44, size 2. This may be harmless, but if you
have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of
your device obtained from lspci.
PCI: Enabling device 0000:04:05.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:04:05.0[A] -> GSI 20 (level, low) -> IRQ 17
pciback 0000:04:06.0: Driver tried to write to a read-only configuration
space field at offset 0x44, size 2. This may be harmless, but if you
have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of
your device obtained from lspci.
PCI: Enabling device 0000:04:06.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:04:06.0[A] -> GSI 21 (level, low) -> IRQ 16
--
mailto:gunnar.zarncke@gmx.de
http://gunnar.zarncke.de
next reply other threads:[~2008-01-27 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 20:07 Gunnar Zarncke [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-18 0:02 irq 17: nobody cared (try booting with the "irqpoll" option) Justin Mattock
2006-06-03 12:51 Hans-Christian Armingeon
2006-06-04 0:48 ` Hans-Christian Armingeon
2006-06-04 8:03 ` 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=479CE487.4040207@zarncke.de \
--to=gunnar@zarncke.de \
--cc=gunnar.zarncke@gmx.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.