Date: Tue, 15 Jul 2008 11:23:09 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: freebsd-usb@freebsd.org Subject: Re: Crash when booting with umass device connected Message-ID: <3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com> In-Reply-To: <3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com> References: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu> <3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/14/08, Paul Schmehl <pschmehl_lists@tx.rr.com> wrote: > I'd like to work with someone to provide useful information about this > problem. > Ever since upgrading my workstation to 7.0 STABLE, I cannot boot with my > umass > device connected. Once the system is up and running, I can mount the > device > with no problems. > > During the boot process, the device is detected, but then it causes a > kernel > panic. I'm logging the console to console.log, but there is no useful > information there. I've enabled USB_DEBUG and rebuilt the kernel, but I > have > no idea how to capture the information printed to the console when this > failure > occurs. (I'm seriously considering taking a photograph of the screen > since > I > can't do a screenshot and I can't find the information in any logs.) > > I'd post a bug, but without some trace information, it's kind of > worthless. > If > I can get help from someone knowledgeable, I'll provide whatever > information > is > needed to track this problem down. Look in Developers handbook for more info /usr/share/doc/en/books/developers-handbook/index.html I think that textdumps are MFCed to STABLE. Textdumps provide easy way for gathering backtraces.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750807150223w6f264048wd9e13ae8846b593c>