From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 22 11:06:35 2012 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ABB94250 for ; Mon, 22 Oct 2012 11:06:35 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 788178FC1E for ; Mon, 22 Oct 2012 11:06:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9MB6ZUI044416 for ; Mon, 22 Oct 2012 11:06:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9MB6Zbw044414 for freebsd-hardware@FreeBSD.org; Mon, 22 Oct 2012 11:06:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Oct 2012 11:06:35 GMT Message-Id: <201210221106.q9MB6Zbw044414@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-hardware@FreeBSD.org Subject: Current problem reports assigned to freebsd-hardware@FreeBSD.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 11:06:35 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/156241 hardware [mfi] 'zfs send' does not prevents disks to suspend if 1 problem total. From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 23 19:45:13 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0920DB5 for ; Tue, 23 Oct 2012 19:45:13 +0000 (UTC) (envelope-from nate.keegan@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8F58FC19 for ; Tue, 23 Oct 2012 19:45:13 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id v11so5887990vbm.13 for ; Tue, 23 Oct 2012 12:45:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=npRg0R0PYckWZZONA6BaXH2i37L/bxDIokPuP6RMgmQ=; b=tjIWas0w10XiUQ0F9faWzSrHKuJknBbyka9Mb8mXp6FOpQRQF17EuTAUGLBrD7UeZu m61UvpImtlfM8rXr7XLMCY+lnDwOT0Qv+CTEzz83L8UrNXaVONmB0KHDUAfmAdaBUhKc 87XICxE7teULXOyboo8ceZh0Hny9wWYfwjY1zAMULcIXcSXgDrofTiYCKx5cLmbq2uOA 49lN2tMKAGUA5Cww8fF3Hskb0xOcNHlE+N/fhTnAABg3kVyXlJMcivJwiJ9PukS2g+Kj CB+u9wyE5qBoACOg/BY6GxFhpsXBPerdQHidvId3j5NVV1IwsItARU6lzgDSSpGnJ0gY R0Dw== MIME-Version: 1.0 Received: by 10.52.89.146 with SMTP id bo18mr18021542vdb.33.1351021512558; Tue, 23 Oct 2012 12:45:12 -0700 (PDT) Received: by 10.58.240.42 with HTTP; Tue, 23 Oct 2012 12:45:12 -0700 (PDT) In-Reply-To: References: <20121015203229.40280@gmx.com> Date: Tue, 23 Oct 2012 12:45:12 -0700 Message-ID: Subject: Re: ahcich Timeouts SATA SSD From: nate keegan To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 19:45:14 -0000 Since replacing the SSD disks with good old plain SATA in external enclosures I have not experienced a single issue. I can only surmise that something is wonky with the Crucial M4 firmware with FreeBSD 8.2/9.0 under certain circumstances. Thanks to everyone who contributed on this as the information about debugging kernels, etc was very helpful from a procedural point of view. On Tue, Oct 16, 2012 at 12:48 PM, nate keegan wrote: > I'm only seeing gstat output of a few percentage points for the OS disks. > > I am using ECC memory (both the Kingston and the new Crucial memory) > and went ahead and swapped out the SSD for SATA disks this morning. > > Since both SSD were the same firmware and type/manufacturer I figured > it was a good time to address this variable. > > I also went ahead and put in a serial console server this morning so I > have proper console access instead of relying on the Supermicro iLO > utility. > > Will keep an eye on the pure SATA setup to see if it barfs or not. > Will try to gather some ddb(4) information if it does barf again. > > > On Mon, Oct 15, 2012 at 1:32 PM, Dieter BSD wrote: >>> SSD are connected to on-board SATA port on motherboard >> >> Presumably to controllers provided by the Intel Tylersburg 5520 chipset. >> >>> This system was commissioned in February of 2012 and ran without issue >>> as a ZFS backup system on our network until about 3 weeks ago. >> >>> The system is dual PSU behind a UPS so I don't think that this is an issue. >> >> No changes? e.g. no added hardware to increase power load. >> Overloading the power supply and/or the wiring (with too many splitters) >> can result in flaky problems like this. >> >>> OS will respond to ping requests after the issue and if you have an >>> active SSH session you will remain connected to the system until you >>> attempt to do something like 'ls', 'ps', etc. >> >>> I am not able to drop into DDB when the issue happens as the system is >>> locked up completely. Could be a failure on my part to >>> understand/engage in how to do this, will try if the issue happens >>> again (should on Wednesday AM unless setting camcontrol apm to off for >>> the disks somehow fixes the issue). >> >> If the system is alive enough to respond to ping, I'd expect you >> should be able to get into DDB? Can you get into DDB when the system >> is working normally? >> >>> 2 x Crucial M4 64 Gb SATA SSD for FreeBSD OS (zroot) >>> 2 x Intel 320 MLC 80 Gb SATA SSD for L2ARC and swap >> >>> I ran the Crucial firmware update ISO and it did not see any firmware >>> updates as necessary on the SSD disks. >> >> Does the problem happen with both the Crucial and the Intel SSDs? >> >>> If software I agree that it would not make sense that this would >>> suddenly pop-up after months of operation with no issues. >> >> If something causes the software/firmware to take a different >> path, new issues can appear. E.g. error handling or even timing. >> Infrequently used code paths might not have been tested sufficiently. >> >> Does the controller have firmware? Part of the BIOS I suppose. >> Is there a BIOS update available? Have you considered connecting the >> SSDs to a different controller? >> >>> the on-board AHCI portion of the BIOS does >>> not always see the disks after the event without a hard system power >>> reset. >> >> That's at least one bug somewhere, probably the hardware isn't getting reset >> properly. Does Supermicro know about this bug? >> >>> I have 48 Gb of Crucial memory that I will put in this system today to >>> replace the 24 Gb or so of Kingston memory I have in the system. >> >> Which in addition to being different memory, should reduce swap activity. >> >> Suggestion: move everything to conventional drives. Keep at least one >> SSD connected to system, but normally unused. Now you can beat on the >> SSD in a controlled manner to debug the problem. Does reading trigger >> the problem? Writing? Try dd with different blocksizes, accessing >> multiple SSDs at once, etc. I have to wonder if there is a timing problem, >> or missing interrupt, or... >> >>> * Ditch FreeBSD for Solaris so I can keep ZFS lovin for the intended >>> purpose of this system >> >> If it fails with FreeBSD but works with Solaris on the same hardware, >> then it is almost certainly a problem with the device driver. (Or >> at least a problem that Solaris has a workaround for.) >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 23 19:46:00 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 65579E07 for ; Tue, 23 Oct 2012 19:46:00 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id E0E0D8FC16 for ; Tue, 23 Oct 2012 19:45:59 +0000 (UTC) Received: from server.rulingia.com (c220-239-241-202.belrs5.nsw.optusnet.com.au [220.239.241.202]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q9NJjoZQ026044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 24 Oct 2012 06:45:51 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q9NJjig4003374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Oct 2012 06:45:45 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q9NJjipP003373; Wed, 24 Oct 2012 06:45:44 +1100 (EST) (envelope-from peter) Date: Wed, 24 Oct 2012 06:45:44 +1100 From: Peter Jeremy To: nate keegan Subject: Re: ahcich Timeouts SATA SSD Message-ID: <20121023194544.GA95769@server.rulingia.com> References: <20121015203229.40280@gmx.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 19:46:00 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Oct-16 12:48:16 -0700, nate keegan wrote: >Will keep an eye on the pure SATA setup to see if it barfs or not. >Will try to gather some ddb(4) information if it does barf again. Any news on this? --=20 Peter Jeremy --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCG8+gACgkQ/opHv/APuIfMNACfZlH7O5TCxzTzL5l1gSc1eHgu fngAn3jOWDO0v+1C+iWGosr+Wb/j1O91 =uVSY -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 26 23:15:38 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 81E3CFB5 for ; Fri, 26 Oct 2012 23:15:38 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 0B7A68FC12 for ; Fri, 26 Oct 2012 23:15:37 +0000 (UTC) Received: from server.rulingia.com (c220-239-241-202.belrs5.nsw.optusnet.com.au [220.239.241.202]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q9QNFToP071569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 27 Oct 2012 10:15:30 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q9QNFNa5075776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 27 Oct 2012 10:15:23 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q9QNFNKC075775 for freebsd-hardware@freebsd.org; Sat, 27 Oct 2012 10:15:23 +1100 (EST) (envelope-from peter) Date: Sat, 27 Oct 2012 10:15:23 +1100 From: Peter Jeremy To: freebsd-hardware@freebsd.org Subject: Any digi(4) users out there? Message-ID: <20121026231523.GA68167@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 23:15:38 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Does anyone use the DigiBoard multiport serial expanders? I have a couple of PRs (kern/152253 and kern/158086) to make digi(4) campatible with TTYng but I no longer have access to the hardware. --=20 Peter Jeremy --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCLGYsACgkQ/opHv/APuIc9TQCeI8cc4BSsQMy8uBt0pO1wsAHW GNYAn1DdvauhCszUof49NbHOg1jpyMN8 =P1r9 -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn--