From owner-freebsd-current@FreeBSD.ORG Mon May 18 05:36:39 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 0BC4F1065672 for ; Mon, 18 May 2009 05:36:39 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 82AF38FC23 for ; Mon, 18 May 2009 05:36:38 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 243034055; Mon, 18 May 2009 08:36:37 +0300 Message-ID: <4A10F3E3.40306@FreeBSD.org> Date: Mon, 18 May 2009 08:36:35 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: Magnus Kling References: <43b1bb350905150939s5d503f00x27116e7ffe79a37@mail.gmail.com> In-Reply-To: <43b1bb350905150939s5d503f00x27116e7ffe79a37@mail.gmail.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Kernel panic when reboot on server with a Promise SX4000 and two ATA disks RAID1. 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: Mon, 18 May 2009 05:36:39 -0000 Hi. Magnus Kling wrote: > After having some trouble with ACPI kernel in 7.1, regarding booting > with a Promise SX4000 card in a RAID1 setup, I tried to upgrade to > CURRENT to test the bits that John Baldwin wrote and had commited to head. > > Result: > Well, it boots ok but on reboot I get a kernel panic after the disks > have made the sync. > > Attached is a bt and panic message. According to backtrace, system tried to reference address 0xc while sending final flush command to the drive. ATA has no other shutdown actions except this, so any contexts and states should not be lost in any case. And as soon as your drive was detected, the controller is probably operable. Haven't you seen any other ATA error messages during boot or later? If my i386 kernel is more or less coherent to your's, ata_promise_sx4_command+0x39 address where it have crashed means caddr_t window = rman_get_virtual(ctlr->r_res1); line, and especially 'ctlr->r_res1' part. So looks like struct ata_pci_controller *ctlr = device_get_softc(gparent); returned NULL there. But the same technique used by many other ATA drivers without problems, so I am a bit surprised. Is the problem continuously repeatable? Does the controller operates well all other time before shutdown? Are you sure that you have rebuilt your kernel correctly? -- Alexander Motin