From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 5 07:56:32 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 D74D9551 for ; Mon, 5 Nov 2012 07:56:32 +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 637088FC12 for ; Mon, 5 Nov 2012 07:56:31 +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 qA57uTkk097155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Nov 2012 18:56: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 qA57uNsY052398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Nov 2012 18:56: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 qA57uMXT052397; Mon, 5 Nov 2012 18:56:22 +1100 (EST) (envelope-from peter) Date: Mon, 5 Nov 2012 18:56:22 +1100 From: Peter Jeremy To: nate keegan Subject: Re: SSD dropping off bus Message-ID: <20121105075622.GB37312@server.rulingia.com> References: <20121029104329.GA58203@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oLBj+sq0vYjzfsbl" 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: Mon, 05 Nov 2012 07:56:32 -0000 --oLBj+sq0vYjzfsbl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Oct-29 12:22:41 -0700, nate keegan wrote: >I tried all sorts of things and the solution for me was to ditch >Crucial SSD for straight SATA disks. > >http://lists.freebsd.org/pipermail/freebsd-hardware/2012-October/007135.ht= ml Yes, I saw that thread (and even provided input). You have different brand SSDs, attached to different SATA controllers and a different FreeBSD version (though I'm not sure if the ahci(4) driver is different). My suspicion is the SSD firmware, though it's possible there's an issue in the driver that is triggered by something unique to SSDs in general. --=20 Peter Jeremy --oLBj+sq0vYjzfsbl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCXcSYACgkQ/opHv/APuIdVYwCgqdOrq79iYQGl5mqxB7ibR0pE 83gAoKSuRf8q6Ar/NcizJAkP7lV5CF33 =T1m2 -----END PGP SIGNATURE----- --oLBj+sq0vYjzfsbl-- From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 5 11:06:34 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 05CE8CE4 for ; Mon, 5 Nov 2012 11:06:34 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id DE4318FC0A for ; Mon, 5 Nov 2012 11:06:33 +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 qA5B6XMi001158 for ; Mon, 5 Nov 2012 11:06:33 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA5B6XIP001156 for freebsd-hardware@FreeBSD.org; Mon, 5 Nov 2012 11:06:33 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Nov 2012 11:06:33 GMT Message-Id: <201211051106.qA5B6XIP001156@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, 05 Nov 2012 11:06:34 -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 Wed Nov 7 09:03: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 4CA20C04 for ; Wed, 7 Nov 2012 09:03:13 +0000 (UTC) (envelope-from linuxfreaker@gmail.com) Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 127188FC08 for ; Wed, 7 Nov 2012 09:03:12 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id k10so1246449iag.13 for ; Wed, 07 Nov 2012 01:03:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=/6UMgz5FMctLV8yobadFeu5UKAgRoMoE46p7GOt0pNk=; b=uwxEkGPlgOTuC9SGtx1JO1qarctDULMVuC9NFmioY8MXfmanHnkBX2Tg9d6tVPtDjy CoO65xhIZObZnTcv63LPBJ1Uo0QJs8Llyb7l6XTOtE+geyaTtTUOesmPMOc0kiZK/J+/ P/0++A3hJcYnxg+uUms8k0GM3IEU+pmeHxQMNLR+9UpJbjdR0sX7bg3/er9buj/qw/QN TNHPZ7pTXBOcLLmaI73TKC+YGv6XC00NA5DOdSgM1Ogkt3bovAHkoWM0iLzJ0OfQgPxg 76KbDkTtjVGd+/LW5BjLRxuNAvsNPJMtj1YDvo59QgL1pyHGVBBCBdQbHfxF8sWvlDb1 X6Ew== MIME-Version: 1.0 Received: by 10.50.77.230 with SMTP id v6mr15837730igw.11.1352278992236; Wed, 07 Nov 2012 01:03:12 -0800 (PST) Received: by 10.64.106.39 with HTTP; Wed, 7 Nov 2012 01:03:12 -0800 (PST) Date: Wed, 7 Nov 2012 01:03:12 -0800 Message-ID: Subject: From: linux freaker To: freebsd-hardware@freebsd.org, manick20@gmail.com, E32748172-WR@workroom.elance.com, robert.mtt@verizon.net, E34147723-WR@workroom.elance.com 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: Wed, 07 Nov 2012 09:03:13 -0000 http://geertdekoning.nl/wordpress3/wp-content/themes/fullscreen/ugoogle.html From owner-freebsd-hardware@FreeBSD.ORG Fri Nov 9 07:37: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 392BDED for ; Fri, 9 Nov 2012 07:37:35 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id CB5398FC13 for ; Fri, 9 Nov 2012 07:37:34 +0000 (UTC) Received: (qmail 6483 invoked by uid 0); 9 Nov 2012 07:30:52 -0000 Received: from 67.206.184.196 by rms-us009 with HTTP Content-Type: text/plain; charset="utf-8" Date: Fri, 09 Nov 2012 02:30:48 -0500 From: "Dieter BSD" Message-ID: <20121109073050.238960@gmx.com> MIME-Version: 1.0 Subject: Re: FreeBSD on RaspberryPi To: freebsd-hardware@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: fdTucDw83zOlNR3dAHAhold+IGRvb0Cw 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, 09 Nov 2012 07:37:35 -0000 > If someone knows how to get the video out > to work, I'm very interested! Technically, there is a fully open-source graphics stack. The bad news is that they moved the functionality into the binary-only firmware, which makes fixing bugs a bit more difficult. I haven't hunted down the actual code, much less looked at it, but if all the functionality is in the firmware, there shouldn't be much code that needs to be ported to BSD. The good news: http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDY The bad news: http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDk From owner-freebsd-hardware@FreeBSD.ORG Fri Nov 9 10:30:17 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 9C795AAC for ; Fri, 9 Nov 2012 10:30:17 +0000 (UTC) (envelope-from lnb@freebsdsystems.com) Received: from zmail.servaris.com (zmail.servaris.com [107.6.51.160]) by mx1.freebsd.org (Postfix) with ESMTP id 485608FC08 for ; Fri, 9 Nov 2012 10:30:16 +0000 (UTC) Received: (qmail 51444 invoked by uid 89); 9 Nov 2012 10:26:44 -0000 Received: by simscan 1.4.0 ppid: 51399, pid: 51440, t: 0.0640s scanners: attach: 1.4.0 clamav: 0.97.6/m:54/d:15557 Received: from unknown (HELO ?192.168.0.55?) (lnb@freebsdsystems.com@99.238.64.55) by zmail.servaris.com with ESMTPA; 9 Nov 2012 10:26:44 -0000 Message-ID: <509CDA3D.5090509@freebsdsystems.com> Date: Fri, 09 Nov 2012 05:26:05 -0500 From: Lanny Baron Organization: Freedom Technologies Corp. FreeBSD Systems User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: nate keegan Subject: Re: ahcich Timeouts SATA SSD References: <20121015203229.40280@gmx.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 09 Nov 2012 10:30:17 -0000 Hi, I don't know how far apart you added memory from the time you bought/built your server. I say that because the drams on the memory might be slightly different. When we build servers, we use a particular brand for certain reasons but one of those reason is the fact the dram specs do not change on a given sku. Here is what I recommend you try. Take out all the memory. Add one dimm only. See if problem persists. If problem stops, add second dimm. Still good, add 3rd dimm and keep adding another dimm one by one. When the problem comes back. Remove all dimms again and put the last dimm you added where the problem came back in first slot. If the problem persists, you found the winner. If not, add all dimms back except the one you just tested and use another dimm. If problem persists, you found a bad memory slot. It's a real PITA but that is the only way to find the issue if it is indeed memory or a bad memory slot. One more thing you should try. Did you enable IPMI? If so, #ipmitool -H x.x.x.x sel list Take a look at the output. If you did not enable IPMI (ipadd/netmask/gateway), the bios should have a place to do so. Sorry, we don't sell/build supermicro* so I am unfamiliar with those boards. If you are using both kingston/crucial, just use one of those, do not mix them. Hope this can help you out. Lanny Servaris Corporation http://www.servaris.com On 10/16/2012 3: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" > _______________________________________________ > 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" >