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?