From owner-freebsd-usb@FreeBSD.ORG Thu Oct 30 20:54:28 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 9B3F01065670 for ; Thu, 30 Oct 2008 20:54:28 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172]) by mx1.freebsd.org (Postfix) with ESMTP id 6B79A8FC08 for ; Thu, 30 Oct 2008 20:54:28 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so795764wfg.7 for ; Thu, 30 Oct 2008 13:54:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :sender:to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=YTZJZ/y0RomqXZxiQHPPVAIF995L+bL6wnsvApY2thw=; b=SoYK+iBbzVKMZ+KfA0RSmSjuWAX0ePARPqOjhsi8Oc4bVXtPSP/SadpEF8YfFEK+DQ MVeMPTbiIueD7KrorfNaF/jiLbSE+poWRWxh6YzuhndtLEKueH9VfG+5YQSUfO8CD4S3 DaGhfuRGrd7sGGw7dKV1DutIB/egZeo5ArATw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references:x-google-sender-auth; b=mABg2TrJOJ46Pyxx6qqe48I/R8clfwO6zBPL5FQpOmaOv91BEiUw6JhMUpeBihZGWl oGT6rsHu66aQaFqRkkPtohN63oDvZQuO1DN/xK6WzsLXIpnEivfCkoR03Ml2avLQS5zO zjUt4SBcHhjDsKN3ccI0LjHKd2aqIdEGRGKqA= Received: by 10.142.223.20 with SMTP id v20mr4959710wfg.81.1225400067903; Thu, 30 Oct 2008 13:54:27 -0700 (PDT) Received: by 10.142.141.5 with HTTP; Thu, 30 Oct 2008 13:54:27 -0700 (PDT) Message-ID: <539c60b90810301354h10c9a411tdbad75880a8448@mail.gmail.com> Date: Thu, 30 Oct 2008 13:54:27 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: "M. Warner Losh" In-Reply-To: <20081029.183134.1650439445.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <539c60b90810291648l7567b974h8e0999a66971495b@mail.gmail.com> <20081029.183134.1650439445.imp@bsdimp.com> X-Google-Sender-Auth: 6fe21dfa47d0cf75 Cc: freebsd-usb@freebsd.org Subject: Re: ucom panic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stevefranks@ieee.org List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2008 20:54:28 -0000 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