From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 19:55:23 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5D581065672 for ; Tue, 4 Nov 2008 19:55:23 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe14.swipnet.se [212.247.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id 4DA358FC14 for ; Tue, 4 Nov 2008 19:55:22 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=d6BVkb5LuPPVEe4iNQMLyA==:17 a=ekFrb3239OE0hOTvgD0A:9 a=kEPXseiqTXpooPsuFl6v2YNaiTgA:4 a=ZrMMMnaxNC4A:10 a=cvZW9r6VXHAA:10 a=LY0hPdMaydYA:10 Received: from [62.113.135.6] (account mc467741@c2i.net [62.113.135.6] verified) by mailfe14.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 397588094; Tue, 04 Nov 2008 20:55:21 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org, stevefranks@ieee.org Date: Tue, 4 Nov 2008 20:57:25 +0100 User-Agent: KMail/1.9.7 References: <539c60b90810291648l7567b974h8e0999a66971495b@mail.gmail.com> <539c60b90810301354h10c9a411tdbad75880a8448@mail.gmail.com> <539c60b90811041131h5a45ab8ev397e84cf3a0cf489@mail.gmail.com> In-Reply-To: <539c60b90811041131h5a45ab8ev397e84cf3a0cf489@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811042057.27556.hselasky@c2i.net> Cc: Subject: Re: ucom panic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2008 19:55:24 -0000 On Tuesday 04 November 2008, Steve Franks wrote: > On Thu, Oct 30, 2008 at 1:54 PM, Steve Franks wrote: > > On Wed, Oct 29, 2008 at 5:31 PM, M. Warner Losh wrote: > >> In message: > >> <539c60b90810291648l7567b974h8e0999a66971495b@mail.gmail.com> > >> > >> "Steve Franks" writes: > >> : Perhaps someone can make sense of my backtrace, this is a ucom causes > >> : a panic, but only when I open it from one specific program. If I talk > >> : to the ucom with minicom, no issues. That aside, a panic when talking > >> : to any serial port with any program would be considered a bug, right? > >> > >> Is there any way you could boot a -current kernel? I think this is a > >> bug I fixed in -current, but maybe didn't back merge to 7... > >> > >> Warner > > > > I have a rather older amd64 kernel that didn't do it until I rebuilt > > the day before yesterday (now that's bad luck), and my internal umass > > drive seems to panic both (amd64 & i386) pretty reliably...is there a > > fresbie for current? I suppose the regular snapshot CD would be > > sufficient as well, right? > > > > How about the stability of the rest of current? This is my work > > desktop, and all my files are offsite, so I'm not too concerned about > > weekly reliability, if I get better hw support day-to-day...do you run > > current on any of your workstations? > > > > Alternatively, is there a patch for 7-stable? My work is as an OEM, > > and all our devices get programmed over a ucom bootloader. I'm pretty > > much stuck until this is fixed... > > > > Steve > > So, no real luck installing 8, I don't have an extra disk at the > moment to put it on. I'm really interested in this patch, however. > Is this the same as the new USB4BSD, or USB2 that I've been hearing > about? Can I patch my 7.1 with it? That would be easier for me to > test out. > > Steve Hi, If you compile a FreeBSD 8 kernel with: options COMPAT_FREEBSD7 It should pretty much work if you then copy the resulting kernel and modules to your FreeBSD 7 /boot/kernel directory. --HPS