From owner-freebsd-bugs@freebsd.org Tue Oct 13 15:35:43 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE84EA11C6C for ; Tue, 13 Oct 2015 15:35:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB1621CF2 for ; Tue, 13 Oct 2015 15:35:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9DFZhj4001939 for ; Tue, 13 Oct 2015 15:35:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 191348] [mps] LSI2308 with WD3000FYYZ drives disappears after hotswapping Date: Tue, 13 Oct 2015 15:35:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: patch-ready X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: slm@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2015 15:35:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191348 --- Comment #30 from Stephen McConnell --- > --- Comment #29 from Karli.Sjoberg@slu.se --- Look, if you rather want me= to > open up a new bug report, I can do that, but the end result is the same a= s in > this report; a disk gets kicked for whatever reason, you reinsert a new d= rive, > but it never shows up. I don't care if you open another bug or not. I'm just saying that this app= ears to be a different issue and it's best for both of us to be on the same page= I think. >=20 > OS timeout is: > dev.mps.[0-9].spinup_wait_time=3D5 This is a driver variable. It's not actually an OS timeout. This is a wait time between checking if a drive is finished spinning up. This was necessa= ry in order to work around the problem where disks took a long time to spin up (the actual original issue here). By the time they spun up, the driver had given up waiting. This is exactly what I mean by saying that we should try= to focus on the correct problem, and not mix it in with this original problem, which seems quite different to me. It confuses things. >=20 > We experience this problem on very different hardware. There are a couple > of different SuperMicro motherboards, X9SRH-F, X8SIL-F, X9DBU-F, an HP > DL180 G6, and a Sun Fire X4140. Most have one or several SuperMicro > SC837E26-RJBOD1 but the HP just have the internal bays and the X4140 has > two standard Sun JBOD's, can't remember their names right now. >=20 > So very varying in nature, except for the HBA's, that are all of the same > maker; LSI models 9200, 9201, 9211 and several SuperMicro AOC-USAS2-L8i > (LSI2008). >=20 > The hard drives have also been varying. It=C2=B4s happened with Samsung, > Western Digital and Seagate. >=20 > And yes, if you insert the "kicked out" drive somewhere else, it works. It > shows up and reports no SMART errors. >=20 > Why does the SAS drive show up while any other SATA drive doesn=C2=B4t, i= f it=C2=B4s > not firmware/driver related? Who do I blame?:) I'm not sure why the SAS drive shows up or who to blame yet. But, from what I've seen in the logs, it doesn't look like it's the driver, although I'm n= ot completely sure yet. (In fact, if it was the driver I don't think a SAS dri= ve would show up either.) I hope you can get from my previous explanation why= I don't think it's the driver. The driver can only react to the firmware eve= nts that it receives. If the driver does not get a proper event to add a disk,= it can't do it. It looks like the driver is not getting the events that it ne= eds. It's possible that it's a Firmware problem, but I think we would have seen= a lot more complaints from customers if that were true. If you can give me s= ome exact, simple reproduction steps I can try to recreate it here. The less number of drives and smaller topology, the better for me since I don't have= a lot of equipment at hand. >=20 > /K --=20 You are receiving this mail because: You are the assignee for the bug.=