From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 08:41:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D02816A4CE for ; Thu, 4 Mar 2004 08:41:43 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1A6543D1D for ; Thu, 4 Mar 2004 08:41:41 -0800 (PST) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i24Gek4I048921; Thu, 4 Mar 2004 17:41:01 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <40475C28.4050106@DeepCore.dk> Date: Thu, 04 Mar 2004 17:41:12 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040126 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: tnelson@alcyon.ltd.uk References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 X-Mailman-Approved-At: Fri, 05 Mar 2004 04:55:08 -0800 cc: freebsd-current@freebsd.org Subject: Re: CURRENT panics: Fatal trap 12 on atapci1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 04 Mar 2004 16:41:43 -0000 Trent Nelson wrote: > I'm getting fatal trap 12 panics as soon as my 5.2-CURRENT kernel comes > across my SiI0680 card (atapci1). For the life of me, I can't seem to > capture dmesg output anymore. Normally, just 'set console=comconsole' at > the loader prompt and tying it up to a 'tip com1' on the other end was > sufficient. That doesn't work, and I've tried -D, -Dh, and -h which don't > work either, kernel output still goes to the video console. I just committed a fix for this, the sii_reset function is only for the SATA chips, not the '680. -- -Søren