Date: Fri, 19 Aug 2005 08:44:29 -0600 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: Marian Hettwer <MH@kernel32.de>, "Justin T. Gibbs" <gibbs@scsiguy.com> Cc: freebsd-current@freebsd.org Subject: Re: Adaptec AIC-7901 (ahd) broken with 6.0-BETA2 Message-ID: <3F5D63052EDC670D1C98312F@[10.0.0.90]> In-Reply-To: <4305E4A3.6040902@kernel32.de> References: <4305967B.8010909@kernel32.de> <435838B88932CE9C36A18199@aslan.scsiguy.com> <4305E4A3.6040902@kernel32.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>> It looks like the system was able to talk to the controller and your >> drive just fine, but hung later. Can you break into the debugger >> and get a stack trace of where the system is hung? >> > Pardon me, but how do I break into the debugger ? :) > I know, if I'm using -CURRENT I should know how to do it... could you > point me at the right direction anyway ? :-) http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html > Even if I could break into debugger, I would need to get a serial console > working, otherwise a stack trace could be quite hard to get. I don't > think I want to type this by hand... The top few functions are likely all that are important. <Scroll-Lock> followed by PgUp is your friend. -- Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F5D63052EDC670D1C98312F>