From owner-freebsd-current@FreeBSD.ORG Tue May 19 02:41:14 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 0CA761065695 for ; Tue, 19 May 2009 02:41:14 +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 7CAB28FC16 for ; Tue, 19 May 2009 02:41:13 +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 243148055; Tue, 19 May 2009 05:41:12 +0300 Message-ID: <4A121C40.7040201@FreeBSD.org> Date: Tue, 19 May 2009 05:41:04 +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> <4A10F3E3.40306@FreeBSD.org> <43b1bb350905180025g682d3764qba5a450d85d8f961@mail.gmail.com> <43b1bb350905181331r44b35b13i22aa1ba6a18103ed@mail.gmail.com> In-Reply-To: <43b1bb350905181331r44b35b13i22aa1ba6a18103ed@mail.gmail.com> Content-Type: multipart/mixed; boundary="------------030500010006020409010308" 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: Tue, 19 May 2009 02:41:15 -0000 This is a multi-part message in MIME format. --------------030500010006020409010308 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Magnus Kling wrote: > Compiled once again. No change. The kernel panics. I don't see obvious problems there. I think something else may erase that controller softc pointer. Can you try to apply attached patch. It may give us some more clues about what is actually become wrong there. May be it is somehow related to the RAID array built on controller. ata-raid part is quite complicated and historically was buggy quite often. Can you instead of your array drives try to attach some other one without any array built or just disable ata-raid module? Are you booting from some other device now? -- Alexander Motin --------------030500010006020409010308 Content-Type: text/plain; name="ata-promise.c.debug.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ata-promise.c.debug.patch" --- ata-promise.c.prev 2009-05-14 17:57:13.000000000 +0300 +++ ata-promise.c 2009-05-19 05:20:13.000000000 +0300 @@ -1053,6 +1053,15 @@ ata_promise_sx4_command(struct ata_reque { device_t gparent = GRANDPARENT(request->dev); struct ata_pci_controller *ctlr = device_get_softc(gparent); + +if (ctlr == NULL) { + printf("ctlr IS NULL!!!\n"); + device_printf(request->dev, "request->dev\n"); + device_printf(request->parent, "request->parent\n"); + device_printf(device_get_parent(request->dev), "device_get_parent(request->dev)\n"); + device_printf(gparent, "gparent\n"); +} + struct ata_channel *ch = device_get_softc(request->parent); struct ata_dma_prdentry *prd = request->dma->sg; caddr_t window = rman_get_virtual(ctlr->r_res1); --------------030500010006020409010308--