From owner-freebsd-firewire@FreeBSD.ORG Thu Feb 19 05:01:21 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA8FC106564A for ; Thu, 19 Feb 2009 05:01:21 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id B4A068FC13 for ; Thu, 19 Feb 2009 05:01:21 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: (qmail 29768 invoked from network); 18 Feb 2009 21:00:19 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.51?) (69.64.235.60) by iron2.pdx.net with SMTP; 18 Feb 2009 21:00:18 -0800 From: Sean Bruno To: Boris Kotzev In-Reply-To: <1235019152.24031.0.camel@localhost.localdomain> References: <200902150012.49329.boris.kotzev@gmail.com> <200902151727.38421.boris.kotzev@gmail.com> <1234985191.20261.22.camel@localhost.localdomain> <200902190312.24163.boris.kotzev@gmail.com> <1235019152.24031.0.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Wed, 18 Feb 2009 21:01:20 -0800 Message-Id: <1235019680.24031.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) Content-Transfer-Encoding: 8bit Cc: freebsd-firewire@freebsd.org Subject: Re: firewire disk stopped working X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 05:01:22 -0000 On Wed, 2009-02-18 at 20:52 -0800, Sean Bruno wrote: > On Thu, 2009-02-19 at 03:12 +0200, Boris Kotzev wrote: > > On сряда 18 февруари 2009 21:26:31 you wrote: > > > On Sun, 2009-02-15 at 17:27 +0200, Boris Kotzev wrote: > > > > On неделя 15 февруари 2009 01:12:40 you wrote: > > > > > If you haven't already, boot back into the previous kernel environment > > > > > and let me know what revision of CURRENT it was that worked. > > > > > > > > > > Then I'll need to know what version you were using that broke. > > > > > > > > > > I'm trying to get my AMD64 system built this weekend to test things. > > > > > > > > > > Sean > > > > > > > > Verbose dmesg from the working system: > > > > > > > > http://host7.net62.hdsl-213-169.fastbg.net/dmesg.working.txt > > > > > > > > Verbose dmesg from the broken system: > > > > > > > > http://host7.net62.hdsl-213-169.fastbg.net/dmesg.broken.txt > > > > > > > > (The cable was plugged in after the system had had already booted - the > > > > output from the disk is found at the end.) > > > > > > > > Please, feel free to ask for more details, if necessary. > > > > > > > > Thanks, > > > > > > > > Boris Kotzev > > > > > > Looking over your logs, I can't quite see what the failure is. There > > > seems to be a format error, I'm just not sure what is being requested. > > > > > > Can you update to -current, and set: > > > debug.sbp_debug = 1 > > > debug.firewire_debug = 1 > > > > > > Then repost your dmesg. > > > > > > Sean > > > > Hi, > > > > The dmesg output after plugging the cable are as follows (full verbose dmesg can be > > found at http://host7.net62.hdsl-213-169.fastbg.net/dmesg.debug.txt ): > > I went over everything and came up with the following patch. Let me > apply this to -current and let me know if it makes any difference. > > Sean Ok, this didn't break anything for me. Let me know if this works for you. Sean