Re: radeon in dom0/ivtv in domU: irq 16 nobody cared

[Mark Hurenkamp <mark.hurenkamp@xs4all.nl>]

On Apr 9, 2010, at 1:47 AM, Mark Hurenkamp wrote:

> Hi,
>
>>> With a fairly recent (~march 29th) xen/next kernel and a recent
>>> xen-4.0.rc9-pre build, i still get occasional 'nobody cared'  
>>> messages on a
>>> IRQ which is shared between dom0 radeon driver, and domU ivtv  
>>> driver.
> Meanwhile i moved to an even more recent xen/stable-2.6.32 (.11)  
> kernel,
> and a xen-4.0.0 release, the problem still shows.
>
>>> Is there something i can do about this?
>>
>> Yes,
>>
>> Please e-mail your full serial log output, your cat /proc/interrupts,
>> and 'lspci -vvv' output. This is to say, for both Dom0 and DomU.
> I've attached the requested information, although it was collected  
> after a fresh boot
> (thus the problem has not occurred yet), with the same xen & kernel  
> as were in use
> when the problem last exposed itself.
>
> Note that during boot, there are a lot of warnings about slowpath  
> and schedule_bug,
> most of these occur when starting xen-domains.

The bug just triggered again, since boot, the following extra info was  
printed on the serial
console:
md: md12: resync done.
md: resync of RAID array md10
md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than  
200000 KB/sec) for resync.
md: using 128k window, over a total of 62508800 blocks.
RAID1 conf printout:
  --- wd:2 rd:2
  disk 0, wo:0, o:1, dev:sda12
  disk 1, wo:0, o:1, dev:sdb12
irq 16: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: G        W  2.6.32.11mh18 #10
Call Trace:
  <IRQ>  [<ffffffff810bcdfd>] __report_bad_irq+0x3d/0x8c
  [<ffffffff810bcf64>] note_interrupt+0x118/0x17c
  [<ffffffff810bd721>] handle_level_irq+0x8e/0xda
  [<ffffffff812c2349>] xen_evtchn_do_upcall+0x123/0x1ec
  [<ffffffff8101406e>] xen_do_hypervisor_callback+0x1e/0x30
  <EOI>  [<ffffffff810093aa>] ? hypercall_page+0x3aa/0x100b
  [<ffffffff810093aa>] ? hypercall_page+0x3aa/0x100b
  [<ffffffff8100eb7c>] ? xen_safe_halt+0x10/0x1a
  [<ffffffff8100c141>] ? xen_idle+0x51/0x5c
  [<ffffffff81011d4c>] ? cpu_idle+0xb0/0x107
  [<ffffffff8146975b>] ? rest_init+0x7f/0x81
  [<ffffffff8198ad71>] ? start_kernel+0x423/0x42e
  [<ffffffff8198a2c1>] ? x86_64_start_reservations+0xac/0xb0
  [<ffffffff8198df0d>] ? xen_start_kernel+0x659/0x660
handlers:
[<ffffffffa036649b>] (radeon_driver_irq_handler+0x0/0x141 [radeon])
[<ffffffffa036649b>] (radeon_driver_irq_handler+0x0/0x141 [radeon])
Disabling IRQ #16