From owner-freebsd-current@FreeBSD.ORG Sat Feb 21 16:34:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD832106564A; Sat, 21 Feb 2009 16:34:50 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (brucec-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:c09::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7C79D8FC0C; Sat, 21 Feb 2009 16:34:50 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id BA6A719014; Sat, 21 Feb 2009 16:34:48 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muon X-Spam-Level: X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 Received: from [IPv6:2a01:348:10f:0:71a4:e1a:d4b6:59ab] (unknown [IPv6:2a01:348:10f:0:71a4:e1a:d4b6:59ab]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Sat, 21 Feb 2009 16:34:48 +0000 (GMT) Message-ID: <49A02D23.5080406@cran.org.uk> Date: Sat, 21 Feb 2009 16:34:43 +0000 From: Bruce Cran User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Alexander Motin References: <49A00130.9070105@FreeBSD.org> In-Reply-To: <49A00130.9070105@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Fatal trap 30: reserved (unknown) fault 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: Sat, 21 Feb 2009 16:34:51 -0000 Alexander Motin wrote: > About month ago after one of my amd64 8-CURRENT upgrade I have started > to see crashes with very strange message: > Fatal trap 30: reserved (unknown) fault while in kernel mode > > Crash usually happens during some driver loading or unloading, for > example, snd_hda, which always worked fine before, or during ata > channel detach/attach which also causes device destruction/creation. > Backtrace of this state shows nothing interesting, for example idling > in acpi_cpu_c1() or just DELAY(). > > Does anybody knows, for whom is this fault "reserved" and what does it > mean? > There was a recent thread about this - see also "r187880 causes fatal trap 30 when unloading drivers" -- Bruce Cran