HP 380 G4 - ciss kernel page fault.

[Giovanni Trematerra]

On Wed, Apr 28, 2010 at 5:41 PM, Giovanni Trematerra
<giovanni.trematerra at gmail.com> wrote:
> On Wed, Apr 28, 2010 at 4:07 PM, kama <kama at pvp.se> 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: <HP Smart Array 6400 EM> 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: <HP Smart Array 6400 EM> 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.

--
Gianni