From owner-freebsd-current@FreeBSD.ORG Sat Feb 21 15:44:22 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 06C2E1065672 for ; Sat, 21 Feb 2009 15:44:22 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 32A938FC14 for ; Sat, 21 Feb 2009 15:44:20 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 21 Feb 2009 15:44:19 -0000 Received: from p54A3E156.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.225.86] by mail.gmx.net (mp022) with SMTP; 21 Feb 2009 16:44:19 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX187b3xIjqs7E6KzAOt6jubgwbha/G5exGb9VdQwZU m2B1W2Sxsxg7Rq Message-ID: <49A02152.8050209@gmx.de> Date: Sat, 21 Feb 2009 16:44:18 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) 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 X-Y-GMX-Trusted: 0 X-FuHaFi: 0.61 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 15:44:22 -0000 Alexander Motin schrieb: > Hi. > > 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? Intel: 20-31 -- Intel reserved. Do not use. This exception really should not happen. Maybe int 0x30 is executed, but this should not be the case either.