From owner-freebsd-stable@FreeBSD.ORG Wed Apr 28 16:06:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E859C106566C; Wed, 28 Apr 2010 16:06:27 +0000 (UTC) (envelope-from kama@pvp.se) Received: from ms1.as.pvp.se (mail.pvp.se [213.64.187.227]) by mx1.freebsd.org (Postfix) with ESMTP id 761C08FC24; Wed, 28 Apr 2010 16:06:27 +0000 (UTC) Received: by ms1.as.pvp.se (Postfix, from userid 1001) id 11C4675; Wed, 28 Apr 2010 18:06:26 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ms1.as.pvp.se (Postfix) with ESMTP id 1035074; Wed, 28 Apr 2010 18:06:26 +0200 (CEST) Date: Wed, 28 Apr 2010 18:06:26 +0200 (CEST) From: kama X-X-Sender: kama@ns1.as.pvp.se To: Giovanni Trematerra In-Reply-To: Message-ID: <20100428180600.V4522@ns1.as.pvp.se> References: <20100427150736.A4522@ns1.as.pvp.se> <201004271721.34248.jhb@freebsd.org> <20100428091758.F4522@ns1.as.pvp.se> <201004280802.26267.jhb@freebsd.org> <20100428160428.R4522@ns1.as.pvp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: HP 380 G4 - ciss kernel page fault. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2010 16:06:28 -0000 On Wed, 28 Apr 2010, Giovanni Trematerra wrote: > On Wed, Apr 28, 2010 at 5:41 PM, Giovanni Trematerra > wrote: > > On Wed, Apr 28, 2010 at 4:07 PM, kama wrote: > >> > >> > >> On Wed, 28 Apr 2010, John Baldwin wrote: > >> > >>> On Wednesday 28 April 2010 3:22:44 am kama wrote: > >>> > > >>> > On Tue, 27 Apr 2010, John Baldwin wrote: > >>> > > >>> > > On Tuesday 27 April 2010 9:30:12 am kama wrote: > >>> > > > > >>> > > > Hi. > >>> > > > > >>> > > > I have problem when probing the ciss device. Causing a kernel panic. > >>> This > >>> > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel > >>> > > > works. So something has changed. I am also getting the error on both the > >>> > > > 7.3 and the 8.0 install cd's. > >>> > > > > >>> > > > The ciss that causing the problem is a Smart Array 6404 and its the > >>> addon > >>> > > > card that it faults at. The server disconnect it due to an error. But > >>> > > > since it works on 6.3 it is something that have changed. FreeBSD should > >>> > > > not panic, it should just disable it. > >>> > > > > >>> > > > Also I tried to disable the card in the BIOS, but FreeBSD try to probe > >>> it > >>> > > > anyway and panic. > >>> > > > > >>> > > > This whats comes up on a verbose boot through the ILO remote console. > >>> > > > (typed in manually from a screenshot) > >>> > > > > >>> > > > ciss2: port 0x6400-0x64ff mem > >>> > > > 0xfdf70000-0xfdf71fff irq 98 at device 5.0 on pcill > >>> > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf70000 > >>> > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > >>> > > > ioport > >>> > > > ciss2: can't allocate config window > >>> > > > kernel trap 12 with interupts disabled > >>> > > > >>> > > Can you get the ciss2 boot messages from a working 6.x kernel? > >>> > > >>> > This is the verbose boot on 6.3. > >>> > > >>> > FreeBSD 6.3-STABLE #3: Thu Mar  6 14:29:33 CET 2008 > >>> > > >>> > ciss1: 10 physical devices > >>> > ciss1: 4 logical drives > >>> > ciss1: logical drive (b0t0): RAID 1, 69120MB online > >>> > ciss1: logical drive (b0t1): RAID 1, 69120MB online > >>> > ciss1: logical drive (b0t2): RAID 1, 139776MB online > >>> > ciss1: logical drive (b0t3): RAID 1, 139776MB online > >>> > > >>> > ciss2: port 0x6400-0x64ff mem > >>> > 0xfdf70000-0xfdf71fff,0xfdf00000-0xfdf3ffff irq 98 at device 5.0 on pci11 > >>> > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf70000 > >>> > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > >>> > ioport > >>> > ciss2: can't allocate config window > >>> > device_attach: ciss2 attach returned 6 > >>> > >>> Oh, so it didn't work in 6.x either, it just handles failure less gracefully > >>> in 7.0+? > >> > >> No, ciss2 is disabled. The difference is that 6.x continue to boot instead > >> of a kernel panic as in 7.x and 8.x. > >> > >> I dont have any disks attached to ciss2, so I dont really need it. But > >> ciss1 and ciss2 is on the same physical card, so I cant just remove it. > >> > > > > Could you try this one if you are looking for a patch to 7-STABLE. > > > > Thank you > > > > [snip patch] > > I think it's worth to have > > mtx_assert(&sc->ciss_mtx, MA_OWNED); > > in ciss_free just to be on safe side. Where in ciss_free()? /Bjorn