From owner-freebsd-current@FreeBSD.ORG Wed Nov 27 18:50:30 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B5CFB3A; Wed, 27 Nov 2013 18:50:30 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94296211F; Wed, 27 Nov 2013 18:50:28 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id rARIoH8V053231; Wed, 27 Nov 2013 20:50:17 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua rARIoH8V053231 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id rARIoHDv053229; Wed, 27 Nov 2013 20:50:17 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 27 Nov 2013 20:50:17 +0200 From: Konstantin Belousov To: Don Lewis Subject: Re: panic: double fault with 11.0-CURRENT r258504 Message-ID: <20131127185017.GC59496@kib.kiev.ua> References: <20131127175743.GA59496@kib.kiev.ua> <201311271833.rARIXU8S042240@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PFevkc5XKN5n4o6D" Content-Disposition: inline In-Reply-To: <201311271833.rARIXU8S042240@gw.catspoiler.org> User-Agent: Mutt/1.5.22 (2013-10-16) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 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: Wed, 27 Nov 2013 18:50:30 -0000 --PFevkc5XKN5n4o6D Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote: > On 27 Nov, Konstantin Belousov wrote: > > On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote: > >> On 27 Nov, Konstantin Belousov wrote: > >> > On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote: > >> >> > >> >=20 > >> > What is the instruction at cpu_switch+0x9b ? > >>=20 > >> movl 0x8(%edx),%eax > > So it is line 176 in swtch.s. Is machine still in ddb, or did you > > obtained the core ? If yes, please print out the content of words at > > 0xe4f62bb0 + 4, +8 (*), +16. Please print the content of the word at > > address (*) + 8. >=20 > It is still in ddb. >=20 > , though not in > the above order. Uhm, sorry, I mistyped the last part of the instructions. The new thread pointer is 0xd2f4e000, there is nothing incriminating. Please print the word at 0xd2f4e000+0x254 =3D=3D 0xd2f4e254, which would be the address of the new thread pcb. It is load from the pcb + 8 which faults. --PFevkc5XKN5n4o6D Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJSlj7oAAoJEJDCuSvBvK1BCkAP/AjbBoO9DPS/MIy5guLp1pKk xypBN2YzI5qil79ZZBG8FRG+IKgYPub/SjhYDJ6WUaRQ1gKeLeU2NqmDwZja2Lq1 Jkd3EHTvxddyWOWLxg0OEUDwxiQ7x9viXg1DZJ9ulsl2QG99yUWCy+FPTcqrhd8P LJVJhe0p1pVaHv7WpVdJrpApt74VmT3SQsmFaeNOPDyf1L0LcACWAmks51V29vJQ TEvqo6Xz35h9UnyscDSpb1+MQaXkQS4iweWpE1tJaHVFzHEwfvJom/qJ2etQ6bRH phKxRsbUNId9LIdqpDgSgPCXV2ZG5KNfn/4QfCathA9beLmCyIKmmtTQmfq9QZJ2 LvLtO+QxH7gGDI4Pu+zU3xmXnPfw3SizFUr48fFK2b2X7ghSbQSJ5taj0CgIG2eT xERdmwVoCgSEYPYG5OemPAjIVWSoEDJsGn+ckVc6qnabGVJyy89fJ7rePFFJl6A0 g9puDwRy7ybUkf3ux8T9P6OZfVIMJuBKsKjQ2pm/F7J0ZSr9HtVoRUPO5tz1j+iU bADxTs+Rh1I2Tze58qAZ449TRxBVYQRrlggKxMHMTv1au2qgjytDV+daV2UexudE nh8BMnNGJxYQNn3w3cRw58Jdet8ZS5bqxGD6fUFUS5HWPht9/wN943/NhI9z56ZX 7FJAhTB8NFVG6yq2JiWl =nw7y -----END PGP SIGNATURE----- --PFevkc5XKN5n4o6D--