All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: irq 17: nobody cared (try booting with the "irqpoll" option)
@ 2008-01-27 20:07 Gunnar Zarncke
  0 siblings, 0 replies; 5+ messages in thread
From: Gunnar Zarncke @ 2008-01-27 20:07 UTC (permalink / raw)
  To: xen-devel

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

^ permalink raw reply	[flat|nested] 5+ messages in thread
* irq 17: nobody cared (try booting with the "irqpoll" option)
@ 2008-10-18  0:02 Justin Mattock
  0 siblings, 0 replies; 5+ messages in thread
From: Justin Mattock @ 2008-10-18  0:02 UTC (permalink / raw)
  To: Linux Kernel Mailing List

I'm not sure if this is to blame, or something else
I've applied a patch for 2.6.27 from:
http://bugzilla.kernel.org/show_bug.cgi?id=10724
and later atheros gave a response like this:

[  433.706892] irq 17: nobody cared (try booting with the "irqpoll" option)
[  433.706909] Pid: 0, comm: swapper Not tainted 2.6.27-04845-g742a691 #41
[  433.706912] Call Trace:
[  433.706919]  [<c0153f94>] __report_bad_irq+0x2e/0x6f
[  433.706922]  [<c015419a>] note_interrupt+0x1c5/0x217
[  433.706926]  [<c01536fc>] ? handle_IRQ_event+0x2a/0x5a
[  433.706929]  [<c015474e>] handle_fasteoi_irq+0x91/0xb6
[  433.706933]  [<c0104ca1>] do_IRQ+0x6c/0x87
[  433.706936]  [<c0103c2b>] common_interrupt+0x23/0x28
[  433.706954]  [<f803769f>] ? acpi_idle_enter_bm+0x306/0x392 [processor]
[  433.706959]  [<c02f5d02>] cpuidle_idle_call+0x62/0x92
[  433.706962]  [<c010227d>] cpu_idle+0x74/0x8f
[  433.706966]  [<c039fde2>] rest_init+0x4e/0x50
[  433.706968] handlers:
[  433.706969] [<f83de780>] (ath_isr+0x0/0x13a [ath9k])
[  433.706985] Disabling IRQ #17

I've seen this twice usually If I let NetworkManager
connect, and not google or stream the radio.


-- 
Justin P. Mattock

^ permalink raw reply	[flat|nested] 5+ messages in thread
* irq 17: nobody cared (try booting with the "irqpoll" option)
@ 2006-06-03 12:51 Hans-Christian Armingeon
  2006-06-04  0:48 ` Hans-Christian Armingeon
  2006-06-04  8:03 ` Keir Fraser
  0 siblings, 2 replies; 5+ messages in thread
From: Hans-Christian Armingeon @ 2006-06-03 12:51 UTC (permalink / raw)
  To: xen-devel; +Cc: xen-users

Hi,

I am running
xen unstable hg from 2006-06-03
2.6.16.19 pathced with xen unstable hg from 2006-06-02

I get this error message.

[ 1199.028108] irq 17: nobody cared (try booting with the "irqpoll" option)
[ 1199.031054]
[ 1199.031055] Call Trace: <IRQ> <ffffffff8014d754>{__report_bad_irq+48}
[ 1199.034294]        <ffffffff8014d9bc>{note_interrupt+539} <ffffffff8014d2ab>{__do_IRQ+190}
[ 1199.040504]        <ffffffff8010c934>{do_IRQ+62} <ffffffff802d0034>{evtchn_do_upcall+132}
[ 1199.046403]        <ffffffff8010b152>{do_hypervisor_callback+30} <EOI>
[ 1199.052363] handlers:
[ 1199.055141] [<ffffffff880354ab>] (ata_interrupt+0x0/0x166 [libata])
[ 1199.058267] Disabling IRQ #17

So I rebooted with irqpoll option.

Is this a bug, or what's the cause of this error message?


Johnny

^ permalink raw reply	[flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-10-18  0:02 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-27 20:07 irq 17: nobody cared (try booting with the "irqpoll" option) Gunnar Zarncke
  -- strict thread matches above, loose matches on Subject: below --
2008-10-18  0:02 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

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.