Date: Mon, 11 Aug 2014 14:54:06 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Bengt Ahlgren" <bengta@sics.se>, "Garrett Wollman" <wollman@bimajority.org> Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers Message-ID: <4950FD3896C0468D83A599AC104E4D7A@multiplay.co.uk> References: <21474.34330.572142.206098@hergotha.csail.mit.edu> <uh7ha1jryjg.fsf@P142s.sics.se>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "Bengt Ahlgren" <bengta@sics.se>
> Garrett Wollman <wollman@bimajority.org> writes:
>
>> Remember about six months ago when I tested 9-stable on one of my big
>> NFS servers, and had it panic in the middle of the USB probe, but
>> ultimately bisected the problem to an update to the mps(4) driver? I
>> had to stop investigating and get the server working (which I did, by
>> installing 9.2 instead of something newer and presumably faster).
>> I'm
>> at the point now where I'd like to upgrade my file servers to 9.3,
>> and
>> I can't, because of this issue, so it's time to start tracking down
>> the bug again.
>>
>> I have two test servers now. 9.3 works just fine on one of them, and
>> panics on the other. The one it works on is slightly older, and has
>> an mpt(4) controller for the boot drives, as opposed to the system
>> where the panic happens, which is mps(4)-only. Both systems have two
>> SAS2116 controllers for external drives; the ones on the working
>> system have drives attached, and the ones on the non-working system
>> are not connected to anything (and in fact disabled in the BIOS for
>> now).
>>
>> Any experts want to suggest where to start (besides, obviously,
>> attaching a serial console, which I haven't done yet)? I saw one
>> change in the svn logs for 9.3 prior to the release which looked like
>> it might be a relevant fix, but it clearly hasn't improved anything
>> for my servers.
>
> I have a dual-mps (one Dell H200 and one LSI 9207) system now running
> 9.1 (w patched sys/kern/kern_intr.c) that I intend to upgrade to 9.3
> shortly. Is it enough to boot a 9.3 memstick to provoke the issue?
I would take this thread with a pinch of salt until it can be proved
its not a hardware issue.
Regards
Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4950FD3896C0468D83A599AC104E4D7A>