From owner-freebsd-current@FreeBSD.ORG Mon Mar 10 15:52:45 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B9E3106566C for ; Mon, 10 Mar 2008 15:52:45 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 6F8588FC33 for ; Mon, 10 Mar 2008 15:52:45 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id BA3701CC44; Mon, 10 Mar 2008 16:52:44 +0100 (CET) Date: Mon, 10 Mar 2008 16:52:44 +0100 From: Ed Schouten To: David Wolfskill , current@freebsd.org Message-ID: <20080310155244.GV80576@hoeg.nl> References: <20080310154947.GB53010@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gpOboRovIPmaBszt" Content-Disposition: inline In-Reply-To: <20080310154947.GB53010@bunrab.catwhisker.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Subject: Re: panic: Invalid priority on timeshare runq X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Mar 2008 15:52:45 -0000 --gpOboRovIPmaBszt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * David Wolfskill wrote: > panic: Invalid priority 155 on timeshare runq > cpuid =3D 1 > KDB: enter: panic > [thread pid 718 tid 100068 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > db> bt > Tracing pid 718 tid 100068 td 0xc58208c0 > kdb_enter(c0af2a73,c0af2a73,c0af4976,e7a3c938,1,...) at kdb_enter+0x3a > panic(c0af4976,9b,c0af449e,183,c0c167c0,...) at panic+0x12c > sched_switch(c58208c0,0,6,184,6c4a2d63,...) at sched_switch+0x1d4 > mi_switch(6,0,c0af483e,b6,0,...) at mi_switch+0x223 > critical_exit(c4f20b00,0,728,c58208c0,c4f20b00,...) at critical_exit+0x99 > intr_execute_handlers(c4f08f34,e7a3c9fc,e7a3ca98,c0a46a74,32,...) at intr= _execute_handlers+0x14b > lapic_handle_intr(32,e7a3c9fc) at lapic_handle_intr+0x3f > Xapic_isr1() at Xapic_isr1+0x34 > --- interrupt, eip =3D 0xc0a5da09, esp =3D 0xe7a3ca3c, ebp =3D 0xe7a3ca98= --- Same problem here. Good to see I'm not the only one who has this problem; I am seeing this panic in my mpsafetty branch (in Perforce) and I was starting to suspect my own code... ;-) --=20 Ed Schouten WWW: http://g-rave.nl/ --gpOboRovIPmaBszt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkfVWUwACgkQ52SDGA2eCwVUBgCeLij4LpPeYf4NNYnT/v9ojqTN TFUAn0TiauX5Hanf7Zs/fe/ckHipgC3d =M8sx -----END PGP SIGNATURE----- --gpOboRovIPmaBszt--