Date: Thu, 30 Oct 2008 13:54:27 -0700 From: "Steve Franks" <stevefranks@ieee.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-usb@freebsd.org Subject: Re: ucom panic Message-ID: <539c60b90810301354h10c9a411tdbad75880a8448@mail.gmail.com> In-Reply-To: <20081029.183134.1650439445.imp@bsdimp.com> References: <539c60b90810291648l7567b974h8e0999a66971495b@mail.gmail.com> <20081029.183134.1650439445.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 29, 2008 at 5:31 PM, M. Warner Losh <imp@bsdimp.com> wrote: > In message: <539c60b90810291648l7567b974h8e0999a66971495b@mail.gmail.com> > "Steve Franks" <stevefranks@ieee.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539c60b90810301354h10c9a411tdbad75880a8448>