From owner-freebsd-current@FreeBSD.ORG Sat Dec 14 08:44:43 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 E2A35550; Sat, 14 Dec 2013 08:44:43 +0000 (UTC) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 58225125B; Sat, 14 Dec 2013 08:44:42 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 96D683EB5F; Sat, 14 Dec 2013 08:44:40 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.7/8.14.7) with ESMTP id rBE8idjL055351; Sat, 14 Dec 2013 08:44:40 GMT (envelope-from phk@phk.freebsd.dk) To: John Baldwin Subject: Re: r259072 is not a happy camper... In-reply-to: <201312131620.25107.jhb@freebsd.org> From: "Poul-Henning Kamp" References: <27325.1386444776@critter.freebsd.dk> <201312091216.04052.jhb@freebsd.org> <44591.1386966997@critter.freebsd.dk> <201312131620.25107.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Date: Sat, 14 Dec 2013 08:44:39 +0000 Message-ID: <55350.1387010679@critter.freebsd.dk> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 08:44:44 -0000 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). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.