From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gregory Haskins Subject: Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang Date: Mon, 29 Sep 2008 14:13:41 -0400 Message-ID: <48E11AD5.8060508@novell.com> References: <20080925123235.GA27916@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig881914E056A300BD217DBD85" To: ghaskins@novell.com, linux-rt-users , LKML , Steven Rostedt Return-path: Received: from victor.provo.novell.com ([137.65.250.26]:33535 "EHLO victor.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755907AbYI2SJW (ORCPT ); Mon, 29 Sep 2008 14:09:22 -0400 In-Reply-To: <20080925123235.GA27916@linux.vnet.ibm.com> Sender: linux-rt-users-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig881914E056A300BD217DBD85 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Chirag Chirag Jog wrote: > Hi Gregory, > We see the following BUG followed by a hang on the latest kernel 2.6.26= =2E5-rt9 on a Power6 blade (PPC64) > It is easily recreated by running the async_handler or sbrk_mutex (real= time tests from ltp) tests. > =20 FYI I am looking at this now. I suspect a dequeue_pushable_task() probably found its way inside a conditional for GROUP_SCHED and inadventently gets compiled away if you disable the feature.=20 Investigating now.. -Greg > login: cpu 0x2: Vector: 700 (Program Check) at [c0000000e8e875d0] > pc: c00000000005110c: .pick_next_pushable_task+0x54/0x9c > lr: c000000000059f50: .push_rt_task+0x44/0x2b4 > sp: c0000000e8e87850 > msr: 8000000000021032 > current =3D 0xc0000000ea5bb2e0 > paca =3D 0xc000000000608700 > pid =3D 2811, comm =3D async_handler > kernel BUG at kernel/sched_rt.c:1041! <--------------------- > enter ? for help > [link register ] c000000000059f50 .push_rt_task+0x44/0x2b4 > [c0000000e8e87850] c0000000e8e878f0 (unreliable) > [c0000000e8e87900] c00000000005a1dc .push_rt_tasks+0x1c/0x38 > [c0000000e8e87980] c00000000005a21c .post_schedule_rt+0x24/0x44 > [c0000000e8e87a10] c000000000057cbc .finish_task_switch+0xd0/0x180 > [c0000000e8e87ab0] c0000000003b6e88 .__schedule+0x6e0/0x798 > [c0000000e8e87b90] c0000000003b7148 .schedule+0xec/0x11c > [c0000000e8e87c10] c0000000003b7a40 .do_nanosleep+0x6c/0xcc > [c0000000e8e87c90] c000000000080738 .hrtimer_nanosleep+0x7c/0x100 > [c0000000e8e87d90] c000000000080830 .sys_nanosleep+0x74/0x94 > [c0000000e8e87e30] c0000000000086ac syscall_exit+0x0/0x40 > --- Exception: c00 (System Call) at 0000008026449844 > SP (400014185f0) is in userspace > > > This is generated by the BUG_ON lines in the pick_next_pushable functio= n > introduced by the sched-only-push-once-per-queue.patch . > > The -rt kernel prior to this patch didnot give such BUGes. > > All this was tried with > CONFIG_GROUP_SCHED=3DN > CONFIG_RT_GROUP_SCHED=3DN > > > Setting the options > CONFIG_GROUP_SCHED=3Dy > CONFIG_RT_GROUP_SCHED=3DY, > seems to solve the problem. > > > > =20 --------------enig881914E056A300BD217DBD85 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkjhGtUACgkQlOSOBdgZUxkCVgCffaEoDeJs6xpk6hMTxms94vYQ 9YUAn0Mcc78HvOozpckeG+tfE4OIbTmS =ZbVA -----END PGP SIGNATURE----- --------------enig881914E056A300BD217DBD85--