From owner-freebsd-current@FreeBSD.ORG  Wed Dec 18 22:38:43 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D79C1573
 for <freebsd-current@freebsd.org>; Wed, 18 Dec 2013 22:38:43 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id AECD21E22
 for <freebsd-current@freebsd.org>; Wed, 18 Dec 2013 22:38:43 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id B4AADB948;
 Wed, 18 Dec 2013 17:38:41 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Subject: Re: r259072 is not a happy camper...
Date: Wed, 18 Dec 2013 14:58:20 -0500
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; )
References: <27325.1386444776@critter.freebsd.dk>
 <201312131620.25107.jhb@freebsd.org> <55350.1387010679@critter.freebsd.dk>
In-Reply-To: <55350.1387010679@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201312181458.20649.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Wed, 18 Dec 2013 17:38:41 -0500 (EST)
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2013 22:38:43 -0000

On Saturday, December 14, 2013 3:44:39 am Poul-Henning Kamp wrote:
> In message <201312131620.25107.jhb@freebsd.org>, John Baldwin writes:
> 
> >> >Hmmm.  Maybe do 'show lapic' and 'show apic' in ddb and paste that here?
> >> 
> >> sorry about the delay...
> >> 
> >> db> show lapic
> >> lapic ID = 2
> >> version  = 1.0
> >> max LVT  = 5
> >> SVR      = ff (enabled)
> >> TPR      = 00
> >> In-service Interrupts:
> >
> >Hmm, this is empty.  It should not be empty. :(
> >
> >Never the less, the panic is further down than I thought it was.  The system 
> >thinks it had a valid IRQ that required an ithread to be scheduled, but when
> >it went to schedule the ithread, there was no thread to schedule:
> 
> >Does it get a crashdump if you try?
> 
> No :-(
> 
> There may be a connection to unclean UFS filesystems (SU + TRIM, no J).

Is this reproducible?  If so, build with KTR enabled and KTR_INTR set in
KTR_COMPILE and KTR_MASK.  That should at least let us see which interrupt
it thinks it is triggering.  'show irqs' from DDB combined with 'show ktr'
would then be useful.

-- 
John Baldwin