From owner-freebsd-current@freebsd.org Wed Jul 15 15:44:28 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB1E99A1211 for ; Wed, 15 Jul 2015 15:44:28 +0000 (UTC) (envelope-from pawelbsd@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AB491AF4 for ; Wed, 15 Jul 2015 15:44:28 +0000 (UTC) (envelope-from pawelbsd@gmail.com) Received: by wicmv11 with SMTP id mv11so1654253wic.1 for ; Wed, 15 Jul 2015 08:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=2QWZReeAGUcqLXgpURWwOuula+a+wEJs+emBbHmc+Jo=; b=TEf46LyE/c2t9pwbF7M+p8KroJkQEUoQYDdsgj+5BvX0ptw7/B4DOVsjBPcwrbGQq9 O34tLFuPjsWss96RNR1SipbZqRuJyLsDUN0ONhCX4nVfy4tgj6+HsG8ar17qJgDDdG4u v23kTloqAkAsh6U2h+GByDOc8fY21+/pxzYQ04ZDegPHnzlU+p5thmtfGWlg1nutdZqN xH19WGA2em7MUzw5ZEXoKfzkTJoH6RHMHsLKng2zR/b363FzeOEOFhJEHIL3ae5I/ufE Vhv8d4mV/5+kji43gPR8G5oM9cQLYg2ttr4ypEtCMrU1Vk3ojwlT7wpzUHl4woGknlyU TOyw== X-Received: by 10.180.9.7 with SMTP id v7mr279892wia.60.1436975067063; Wed, 15 Jul 2015 08:44:27 -0700 (PDT) Received: from localhost ([176.221.120.130]) by smtp.gmail.com with ESMTPSA id i6sm8489039wjf.29.2015.07.15.08.44.25 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Jul 2015 08:44:26 -0700 (PDT) Sender: =?UTF-8?B?UGF3ZcWCIFDEmWthbGE=?= Date: Wed, 15 Jul 2015 17:40:27 +0200 From: Pawel Pekala To: John-Mark Gurney Cc: Mateusz Guzik , freebsd-current@FreeBSD.org Subject: Re: Instant panic while trying run ports-mgmt/poudriere Message-ID: <20150715174027.5c61e658@FreeBSD.org> In-Reply-To: <20150714222702.GX8523@funkthat.com> References: <20150713231205.627bab36@FreeBSD.org> <20150713212820.GA21313@dft-labs.eu> <20150714224743.0927db44@FreeBSD.org> <20150714222702.GX8523@funkthat.com> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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, 15 Jul 2015 15:44:29 -0000 Hi John-Mark, On 2015-07-14 15:27 -0700, John-Mark Gurney wrote: >Pawel Pekala wrote this message on Tue, Jul 14, 2015 at 22:47 +0200: >> On 2015-07-13 23:28 +0200, Mateusz Guzik wrote: >> >On Mon, Jul 13, 2015 at 11:12:05PM +0200, Pawel Pekala wrote: >> >> Hi >> >>=20 >> >> I'm getting 100% reproducible kernel crash while trying build >> >> ports with poudriere on my system. This started to show up about >> >> 2-3 weeks ago. I upgrade my system on weekly basis usually on >> >> saturday. Here's backtrace: >> >>=20 >> >> (kgdb) bt >> >[..] >> >> at /hdd/src/sys/amd64/amd64/trap.c:201 >> >> #25 0xffffffff80dace32 in calltrap () >> >> at /hdd/src/sys/amd64/amd64/exception.S:235 #26 0xffffffff80941430 >> >> in knote (list=3D0xfffff801a2589408, hint=3D2147483648, >> >> lockflags=3D) >> >> at /hdd/src/sys/kern/kern_event.c:1920 #27 0xffffffff80946a51 in >> >> exit1 (td=3D0xfffff801b84014d0, rv=3D) >> >> at /hdd/src/sys/kern/kern_exit.c:560 #28 0xffffffff80945f1e in >> >> sys_sys_exit (td=3D0x0, uap=3D> >> out>) at /hdd/src/sys/kern/kern_exit.c:178 #29 0xffffffff80dcdaa2 >> >> out>in amd64_syscall (td=3D0xfffff801b84014d0, traced=3D0) >> >> at subr_syscall.c:133 >> >> #30 0xffffffff80dad11b in Xfast_syscall () >> >> at /hdd/src/sys/amd64/amd64/exception.S:395 #31 0x0000000800922eea >> >> in ?? () Previous frame inner to this frame (corrupt stack?) >> >> Current language: auto; currently minimal >> >>=20 >> >> Let me know if you need more details. >> > >> > >> >Well, if the problem is really that reproducible it would be best if >> >you narrowed it down to the exact commit. >> > >> >However, quick look suggests you may be a "victim" of r284861. >>=20 >> After further testing I can confirm that this panic was introduced in >> r284861, thanks for the hint! > >Can you tell me what your line 1920 of kern_event.c is? (and the >context around it? Or at least the $FreeBSD$ line from >kern_event.c? Because in HEAD, the line is: > } else if ((lockflags & KNF_NOKQLOCK) !=3D 0) { > >and there isn't a way to fault on that code... Yes, this is strange. if ((kn->kn_status & (KN_INFLUX | KN_SCAN)) =3D=3D KN_INFLU= X) { /* * Do not process the influx notes, except for * the influx coming from the kq unlock in the * kqueue_scan(). In the later case, we do * not interfere with the scan, since the code * fragment in kqueue_scan() locks the knlist, * and cannot proceed until we finished. */ KQ_UNLOCK(kq); =3D=3D=3D> line 1920 } else if ((lockflags & KNF_NOKQLOCK) !=3D 0) { kn->kn_status |=3D KN_INFLUX; KQ_UNLOCK(kq); error =3D kn->kn_fop->f_event(kn, hint); KQ_LOCK(kq); kn->kn_status &=3D ~KN_INFLUX; if (error) KNOTE_ACTIVATE(kn, 1); KQ_UNLOCK_FLUX(kq); } else { Id line: __FBSDID("$FreeBSD: head/sys/kern/kern_event.c 284215 2015-06-10 10:48:12Z = mjg $"); --=20 pozdrawiam / with regards Pawe=C5=82 P=C4=99kala