From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: radeon in dom0/ivtv in domU: irq 16 nobody cared Date: Mon, 19 Apr 2010 10:08:49 -0400 Message-ID: <20100419140849.GA20776@phenom.dumpdata.com> References: <20100413125741.GA16475@phenom.dumpdata.com> <504848C9-52F2-46C5-BD0E-1C2B35BA1A02@xs4all.nl> <201004170238.31591.mark.hurenkamp@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <201004170238.31591.mark.hurenkamp@xs4all.nl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Hurenkamp Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, Apr 17, 2010 at 02:38:31AM +0200, Mark Hurenkamp wrote: > > > Anyhow, what I would like you test is to provide 'noirqdebug' flag = on > > > your Linux kernel command line. That should take care of the 'nobod= y > > > cared IRQ'. Please test and see if you your machine is more or less > > > sluggish. > I have had my system up and running for several days now, and indeed > the IRQ nobody cared has not occured. I do not see my system behave > any more sluggish than before. All the scheduled recordings seem to hav= e > been recorded correctly (sometimes up to 3 in parallel). Excellent. Then the patch I am working on will make your machine work fine. >=20 > > > Also, please do run this: > > > while (true) > > > do > > > sleep 10 > > > cat /proc/interrupts | grep 16 > > > done > > > > > > during the lifecycle of the whole machine. I am curious to see whet= her > > > you also get an IRQ storm (or if it is just a trickle - which is OK= ) > > > after launching the DomU guest. > Having done so, i notice that the count in dom0 and domU is identical, > and seems to increase with about ~100 or so per second while domU is > recording from /dev/video0. To me that does not seem unusual. >=20 >=20 > Probably unrelated, but although i do have compiz running, and quite so= me eye- > candy enabled in my dom0 Kde environement, the radeon driver still does= n't=20 > seem to generate any interupts.=20 >=20 >=20 > And probably also unrelated, dmesg in the domU shows a lot of these mes= sages: Ugh. No idea. > xennet: skb rides the rocket: 20 frags = = =20 > Pid: 0, comm: swapper Not tainted 2.6.32mh25 #6 = = =20 > Call Trace: = = =20 > [] xennet_start_xmit+0x7d/0x680 [xen_netfront= ] = =20 > [] ? xen_force_evtchn_callback+0xd/0xf = = =20 > [] ? check_events+0x12/0x20 = = =20 > [] ? lock_acquired+0x255/0x264 = = =20 > [] dev_hard_start_xmit+0x23b/0x2e6 = = =20 > [] sch_direct_xmit+0x6a/0x178 = = =20 > [] dev_queue_xmit+0x279/0x3e2 = = =20 > [] ? dev_queue_xmit+0x169/0x3e2 = = =20 > [] ? rcu_read_unlock+0x2b/0x46 = = =20 > [] ? nf_hook_slow+0xcf/0xe0 = = =20 > [] ? ip_finish_output+0x0/0x71 = = =20 > [] ip_finish_output2+0x238/0x281 = = =20 > [] ip_finish_output+0x6f/0x71 = = =20 > [] ip_output+0xcc/0xd5 = = =20 > [] dst_output+0x10/0x12 = = =20 > [] ip_local_out+0x23/0x27 = = =20 > [] ip_queue_xmit+0x30e/0x3a4 = = =20 > [] ? xen_force_evtchn_callback+0xd/0xf = = =20 > [] ? check_events+0x12/0x20 = = =20 > [] tcp_transmit_skb+0x672/0x6b0 = = =20 > [] ? mark_lock+0x27/0x21e = = =20 > [] tcp_write_xmit+0x7cd/0x8bd = = =20 > [] ? tcp_established_options+0x33/0xae = = =20 > [] __tcp_push_pending_frames+0x2f/0x5c = = =20 > [] tcp_data_snd_check+0x29/0xef = = =20 > [] tcp_rcv_established+0xd2/0x6a9 = = =20 > [] ? check_events+0x12/0x20 = = =20 > [] tcp_v4_do_rcv+0x1bf/0x367 = = =20 > [] ? tcp_v4_rcv+0x2b8/0x66d = = =20 > [] ? tcp_v4_rcv+0x2b8/0x66d = = =20 > [] tcp_v4_rcv+0x45b/0x66d = = =20 > [] ip_local_deliver_finish+0x154/0x200 = = =20 > [] ip_local_deliver+0x77/0x7e = = =20 > [] ip_rcv_finish+0x3a9/0x3d5 = = =20 > [] ip_rcv+0x289/0x2c9 = = =20 > [] netif_receive_skb+0x415/0x43f = = =20 > [] xennet_poll+0xaf9/0xca4 [xen_netfront] = = =20 > [] net_rx_action+0xc8/0x21a = = =20 > [] __do_softirq+0x11c/0x1fd = = =20 > [] ? _raw_spin_unlock+0x8f/0x98 = = =20 > [] call_softirq+0x1c/0x30 = = =20 > [] do_softirq+0x4b/0xa6 = = =20 > [] irq_exit+0x4a/0x99 = = =20 > [] xen_evtchn_do_upcall+0x1af/0x1ec = = =20 > [] xen_do_hypervisor_callback+0x1e/0x30 = = =20 > [] ? hypercall_page+0x3aa/0x100b = = =20 > [] ? hypercall_page+0x3aa/0x100b = = =20 > [] ? xen_safe_halt+0x10/0x1a = = =20 > [] ? xen_idle+0x51/0x5c = = =20 > [] ? cpu_idle+0xb0/0x107 = = =20 > [] ? rest_init+0x7f/0x81 = = =20 > [] ? start_kernel+0x417/0x422 = = =20 > [] ? x86_64_start_reservations+0xac/0xb0 = = =20 > [] ? xen_start_kernel+0x648/0x64f >=20 > And dmesg in dom0 (seems related to a chrome crash): This is not good. Can you describe how to reproduce this. > FIX bio-0: Marking all objects used > chrome[12644]: segfault at 7f6cc3b5ad0c ip 0000000000c10c47 sp 00007fff= 88da2a80=20 > error 4 in chrome[400000+262f000] > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D =20 > BUG bio-0: Poison overwritten = =20 > -----------------------------------------------------------------------= ------ =20 >=20 > INFO: 0xffff88002fcfe58b-0xffff88002fcfe58b. First byte 0xeb instead of= 0x6b > INFO: Allocated in mempool_alloc_slab+0x15/0x17 age=3D611 cpu=3D0 pid=3D= 10074 =20 > INFO: Freed in mempool_free_slab+0x17/0x19 age=3D609 cpu=3D0 pid=3D0 = =20 > INFO: Slab 0xffffea000136c730 objects=3D32 used=3D31 fp=3D0xffff88002fc= fe500=20 > flags=3D0x200000000040c3 > INFO: Object 0xffff88002fcfe500 @offset=3D1280 fp=3D0x(null) = =20 >=20 > Bytes b4 0xffff88002fcfe4f0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a= 5a 5a=20 > ZZZZZZZZZZZZZZZZ > Object 0xffff88002fcfe500: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe510: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe520: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe530: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe540: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe550: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe560: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe570: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe580: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b eb 6b 6b= 6b 6b=20 > kkkkkkkkkkk=EBkkkk > Object 0xffff88002fcfe590: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b 6b=20 > kkkkkkkkkkkkkkkk > Object 0xffff88002fcfe5a0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b= 6b a5=20 > kkkkkkkkkkkkkkk=A5 > Redzone 0xffff88002fcfe5b0: bb bb bb bb bb bb bb bb = =20 > =BB=BB=BB=BB=BB=BB=BB=BB =20 > Padding 0xffff88002fcfe5f0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a= 5a 5a=20 > ZZZZZZZZZZZZZZZZ > Pid: 914, comm: kjournald Tainted: G B W 2.6.32mh25 #6 = =20 > Call Trace: > [] print_trailer+0x140/0x149 > [] check_bytes_and_report+0xba/0xeb > [] check_object+0xca/0x1ae > [] __slab_alloc+0x3a6/0x454 > [] ? mempool_alloc_slab+0x15/0x17 > [] ? mempool_alloc_slab+0x15/0x17 > [] kmem_cache_alloc+0xb4/0x173 > [] mempool_alloc_slab+0x15/0x17 > [] mempool_alloc+0x6c/0x11e > [] ? xen_force_evtchn_callback+0xd/0xf > [] ? xen_force_evtchn_callback+0xd/0xf > [] bio_alloc_bioset+0x35/0xc2 > [] bio_clone+0x2a/0x7c > [] make_request+0x51b/0x697 [raid1] > [] md_make_request+0xcf/0x10d > [] ? up_read+0x2b/0x2f > [] generic_make_request+0x2ca/0x323 > [] ? sub_preempt_count+0x9/0x83 > [] submit_bio+0xcd/0xea > [] submit_bh+0xf4/0x117 > [] journal_commit_transaction+0x95b/0xeea > [] ? _spin_unlock_irqrestore+0x70/0x7e > [] ? try_to_del_timer_sync+0x73/0x81 > [] ? del_timer_sync+0x0/0xa6 > [] kjournald+0xf0/0x23c > [] ? autoremove_wake_function+0x0/0x39 > [] ? kjournald+0x0/0x23c > [] kthread+0x7f/0x87 > [] child_rip+0xa/0x20 > [] ? restore_args+0x0/0x30 > [] ? check_events+0x12/0x20 > [] ? check_events+0x12/0x20 > [] ? child_rip+0x0/0x20 > FIX bio-0: Restoring 0xffff88002fcfe58b-0xffff88002fcfe58b=3D0x6b >=20 >=20 > Regards, > Mark. >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel