From owner-freebsd-hardware@FreeBSD.ORG Sun Jul 28 00:08:15 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B9B7DA56; Sun, 28 Jul 2013 00:08:15 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: from mail-ob0-x241.google.com (mail-ob0-x241.google.com [IPv6:2607:f8b0:4003:c01::241]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7A35029D9; Sun, 28 Jul 2013 00:08:15 +0000 (UTC) Received: by mail-ob0-f193.google.com with SMTP id xk17so1789259obc.0 for ; Sat, 27 Jul 2013 17:08:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=2dJibMV3Cbx/Gs4kytdDx0PsAhCRDtR2iIzaBDnitRk=; b=Il3FvSJpz0vG47re60xz2JUYLIfmuKu9C2nLiSUS3sMry7AmuBAfu1/m+NDl05tC5W rzuvGyIq4qSF4AYhqCv+FebwYSSoYv1/EqpGCRtZeu+0Q80INGbIaDE8N3EsKpeqEB0a arkg7mib1AhHhclT9PYY0mCL0F0MeLyuh2JuV9iwlBenjNGyiehBnQNOoWyRisNddN4r IwyH2ZjneHvkiodha0URYcC+LcwaTI3v8grhE+gL4cm9Z6tyTeQovJcX1z8+SOXfejYi cGwY+oOqkEP+8hKGzchXbNFeZDQee2v7AiK6JqHKWjujInqA5B0z47gL6YXlSDZr5qDv nuWw== MIME-Version: 1.0 X-Received: by 10.50.47.107 with SMTP id c11mr433587ign.52.1374970094726; Sat, 27 Jul 2013 17:08:14 -0700 (PDT) Received: by 10.64.238.97 with HTTP; Sat, 27 Jul 2013 17:08:14 -0700 (PDT) Date: Sat, 27 Jul 2013 17:08:14 -0700 Message-ID: Subject: Re: Reset Problem with SATA Port Multiplier From: Dieter BSD To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: mav@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: Sun, 28 Jul 2013 00:08:15 -0000 Bob writes: > After a few hours of a database-like workload A faster way to trigger the problem would be useful. > We're actually more interested in archive type workloads than this > database workload and we have not observed the problem with an archive > workload. So perhaps something about the timing triggers the bug? Sam writes > if you have a script or a way to build a kernel to help debug this I will > run it if you post it here... I have the same issue on a 3 port multiplier > using -HEAD Can you share the make and model of this 3 port multiplier? If it is happening with more than one model of pm, it is more likely some generic problem, rather than triggering some model-specific quirk/bug. Has anyone seen this problem with an older OS release? (say 7.x or 8.x?) If the problem was introduced recently, we might be able to find it by looking at what changed in the source code. I haven't seen the problem with 8.2 or earlier. Looks like a verbose boot will give a little more info. But I suspect that adding more log(9) statements will be needed. Unless mav has a better idea? From owner-freebsd-hardware@FreeBSD.ORG Sun Jul 28 10:23:49 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1F666AA5 for ; Sun, 28 Jul 2013 10:23:49 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A6E062837 for ; Sun, 28 Jul 2013 10:23:48 +0000 (UTC) Received: by mail-ea0-f171.google.com with SMTP id n15so2347666ead.16 for ; Sun, 28 Jul 2013 03:23:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hnim3pTSldtMBE3ZOhq627n+BeijAq1wG6sLBRa5GR0=; b=OxN4Ac+NwJqxy9Mc4VWYIY5d25vXwBslyI0v/zfym6M9p3CwouCZet3OVNBAP9WTg3 egfJADKI4Ld+FLGBiL8CBk1eAD4fa498T7F5dwrp/rrhlF7RReNxItbQSGqLdQMxLmOt WXy/1Fzl5eS078gQhzAAjmR37vtOZo4WQ6l/mnLjU3MzD36gVpc3puAXtNa0SrqiKSPd 4iy0+hm6dlZbk7DgLbMptQ0iT2gStRbn0OSguQyr+CCMnx2WZwzOO1hsssk66qoxU69d oJKDLQB4DQCAHp9pS/wiqxh0jJGnqPDYihj3u9kdVcvpvdgub+mApMJIv/FBNNd+EpTj x/GA== X-Received: by 10.14.47.73 with SMTP id s49mr55272339eeb.71.1375007026930; Sun, 28 Jul 2013 03:23:46 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPSA id a4sm94134825eez.0.2013.07.28.03.23.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Jul 2013 03:23:46 -0700 (PDT) Sender: Alexander Motin Message-ID: <51F4F12F.80003@FreeBSD.org> Date: Sun, 28 Jul 2013 13:23:43 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130616 Thunderbird/17.0.6 MIME-Version: 1.0 To: Dieter BSD Subject: Re: Reset Problem with SATA Port Multiplier References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; 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: Sun, 28 Jul 2013 10:23:49 -0000 On 28.07.2013 03:08, Dieter BSD wrote: > Bob writes: >> After a few hours of a database-like workload > > A faster way to trigger the problem would be useful. > >> We're actually more interested in archive type workloads than this >> database workload and we have not observed the problem with an archive >> workload. > > So perhaps something about the timing triggers the bug? > > Sam writes >> if you have a script or a way to build a kernel to help debug this I will >> run it if you post it here... I have the same issue on a 3 port multiplier >> using -HEAD > > Can you share the make and model of this 3 port multiplier? > If it is happening with more than one model of pm, it is more likely > some generic problem, rather than triggering some model-specific quirk/bug. > Has anyone seen this problem with an older OS release? (say 7.x or 8.x?) > If the problem was introduced recently, we might be able to find it > by looking at what changed in the source code. I haven't seen the > problem with 8.2 or earlier. > > Looks like a verbose boot will give a little more info. > But I suspect that adding more log(9) statements will be needed. > Unless mav has a better idea? There are two sides of this problem: original issue and imperfect error recovery. First one is a big question. I can't say what is actually going on there that causes the problem. Just recently I've made one more attempt to get some documentation on SATA controllers from Marvell. But even after signing NDA process again stopped since I am neither buying thousands of their chips as vendor nor they are supporting for end-users. The alike situation is with other vendors. What's about the recovery, problem is that neither CAM nor mvs driver now track faulty status of the devices. So if some disk's firmware stuck and start causing infinite timeouts, that will substantially interrupt operation of other devices sharing that SATA port. Probably the mechanism of dropping faulty device could be improved somehow. What is about SAS, mentioned here -- that is quite different more expensive market. And even while protocols are much more sophisticated and hardware, firmware and software there are much better tested, there also situations happen sometimes when single misbehaving device may put down whole fabric. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Sun Jul 28 11:23:26 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41D262A2; Sun, 28 Jul 2013 11:23:26 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 006592992; Sun, 28 Jul 2013 11:23:25 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id CA2E8153434; Sun, 28 Jul 2013 13:23:22 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1E6jdLdtNWg; Sun, 28 Jul 2013 13:23:22 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:921:5fd2:d0ea:b474] (unknown [IPv6:2001:4cb8:3:1:921:5fd2:d0ea:b474]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id CF7EE153433; Sun, 28 Jul 2013 13:23:21 +0200 (CEST) Message-ID: <51F4FF2A.2000500@digiware.nl> Date: Sun, 28 Jul 2013 13:23:22 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Alexander Motin Subject: Getting documentation. ( Was Re: Reset Problem with SATA Port Multiplier) References: <51F4F12F.80003@FreeBSD.org> In-Reply-To: <51F4F12F.80003@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dieter BSD , 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: Sun, 28 Jul 2013 11:23:26 -0000 On 28-7-2013 12:23, Alexander Motin wrote: > Just recently I've made one more > attempt to get some documentation on SATA controllers from Marvell. But > even after signing NDA process again stopped since I am neither buying > thousands of their chips as vendor nor they are supporting for > end-users. The alike situation is with other vendors. I heard from several board design houses and distributors that Marvell is among the hardest to get the stuff from. So your story is not unlike other stories I've heard. In our previous company we needed support from a rather big chip vendor as well... (Philips NXP) which sort of worked while they were still in Eindhoven. But once this division got sold, things got a lost worse. And in the end we had to got thru the designer/manufacturer of our boards, and a second tier distributor. And again everything under the original NDA. Perhaps this is somethings you could also do for this problem. Find a coorperative PM board manufacturer, and bigback on their support with the promise to "support" their PM boards in FreeBSD. Motivation for them would have to be that there could be a sales advantage in selling PM boards to FreeBSDers. And given that we advertise that ZFS does not need complex/expensive RAID controllers will increase the usage of more simple devices. Otehr way about it would be to involve the FreeBSD foundation, and get them to do the legal part of the stuff as a umbrella for the developers, and then delegate (again under NDA) work to developers that want to work on Marvell stuff. --WjW From owner-freebsd-hardware@FreeBSD.ORG Sun Jul 28 17:39:08 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5A88E668 for ; Sun, 28 Jul 2013 17:39:08 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: from mail-oa0-x244.google.com (mail-oa0-x244.google.com [IPv6:2607:f8b0:4003:c02::244]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 291CA231E for ; Sun, 28 Jul 2013 17:39:08 +0000 (UTC) Received: by mail-oa0-f68.google.com with SMTP id n12so1833173oag.3 for ; Sun, 28 Jul 2013 10:39:07 -0700 (PDT) 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=PYEvk8iTbPx+UlTv8FJ/gghAIDL1yD0M7jwqSoBq9s0=; b=TgQYJrH7XIc467f3t5dRNw7dQ5ShqnPVKeYSkPnWKIq9rJdoEc3G4M3nxwo2NxHj7V wKUYx4XBsJSeI2BUv6v2IypQYKT7aceXEjIFxg4eC/LOmmZibZHBvT1PMP9y9vrYFBXe rrQn6cSRpG2RU388lgowdO1qP+/Rnlg3mAA1eiQGJHjIYvGiSEVCWthwS10s/1NxKM+G 0VnOcVei67FN9morZiFYSwGEgDMAY7ORajhw8omdp1rhiukradqRYjFMg3UsFR4fs5xu u8jFS+A05MiedACPxW9q09PscWOrxguH8Fd9zraPa/nPkmv32RY16OdMb5GNr7ndERjS fLvA== MIME-Version: 1.0 X-Received: by 10.50.50.210 with SMTP id e18mr544730igo.9.1375033147467; Sun, 28 Jul 2013 10:39:07 -0700 (PDT) Received: by 10.64.238.97 with HTTP; Sun, 28 Jul 2013 10:39:07 -0700 (PDT) Date: Sun, 28 Jul 2013 10:39:07 -0700 Message-ID: Subject: Re: Getting documentation. ( Was [...] SATA Port Multiplier) From: Dieter BSD 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: Sun, 28 Jul 2013 17:39:08 -0000 Willem writes: > Marvell is among the hardest to get the stuff from. One wonders how they expect to sell parts? > Perhaps this is somethings you could also do for this problem. Find a > coorperative PM board manufacturer, and bigback on their support with > the promise to "support" their PM boards in FreeBSD. > > Motivation for them would have to be that there could be a sales > advantage in selling PM boards to FreeBSDers. And given that we > advertise that ZFS does not need complex/expensive RAID controllers > will increase the usage of more simple devices. IIUC we have software RAID, thus we don't "need" complex/expensive RAID controllers regardless of fs. Don't the various BSDs mostly use the same drivers? Perhaps we could promise sales for Dragon/Open/Net as well as FreeBSD? > Otehr way about it would be to involve the FreeBSD foundation, and get > them to do the legal part of the stuff as a umbrella for the developers, > and then delegate (again under NDA) work to developers that want to work > on Marvell stuff. Sounds promising. From owner-freebsd-hardware@FreeBSD.ORG Mon Jul 29 11:06:45 2013 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0B4941A4 for ; Mon, 29 Jul 2013 11:06:45 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D3A0C2DD0 for ; Mon, 29 Jul 2013 11:06:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6TB6ihp061764 for ; Mon, 29 Jul 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6TB6iVo061762 for freebsd-hardware@FreeBSD.org; Mon, 29 Jul 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Jul 2013 11:06:44 GMT Message-Id: <201307291106.r6TB6iVo061762@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, 29 Jul 2013 11:06:45 -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 -------------------------------------------------------------------------------- f kern/156241 hardware [mfi] 'zfs send' does not prevents disks to suspend if 1 problem total.