From owner-freebsd-mobile Sat Jan 24 10:19:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00977 for freebsd-mobile-outgoing; Sat, 24 Jan 1998 10:19:12 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00972 for ; Sat, 24 Jan 1998 10:19:11 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA27949; Sat, 24 Jan 1998 11:19:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA25873; Sat, 24 Jan 1998 11:19:06 -0700 Date: Sat, 24 Jan 1998 11:19:06 -0700 Message-Id: <199801241819.LAA25873@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ugo Paternostro Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: Cirrus Logic PD6729 In-Reply-To: References: <199801230503.WAA19888@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On 23-Jan-98 Nate Williams wrote about "Re: Cirrus Logic PD6729": > > The error would probably occur even if you didn't compile DDB. Also, > > No, this behavior first showed up when I added "options DDB" in the kernel > config. Did you re-install the includes? I'm compiling stuff with DDB and I don't have any problems. > >> debugger. Almost any command (but help) prints something like "Panic... blah > >> blah blah". I tried a trace, but it gives no useful information. What should > > > > *grin* Read the handbook on kernel debugging, that should be a big help > > and can give you more information than I can provide in email. > > Well, if I enter the debugger by pressing CTRL-ALT-ESC and then I give a > "Trace" command, I can see the stack trace (it starts form _Debugger(...) and > so on), but if I wait the panic and ask for a trace, I simply see something > like this (I marked with "==>" my commands) (WARNING: hand copied from the > console, may contain errors): Hmm, not good. It should give you a back-trace of the system. You may want to post this kind of information to -stable and see if they know of bugs in the current system. (Note, I'm also having problems getting a back-trace as well when it crashes mounting my DOS partition...) > without any stack trace: it seems that the debugger itself is panicing, right > after accessing location 0x10. Please note that the IP points to that location. Something is hosed up. > Reading the edx value, I could guess it just did or it is going to do and I/O > to that port, and, from the reference to r_hook, I could guess it is something > related to APM (this would also explain why somethimes the machine goes in > sleep mode when I remove the PCMCIA card). Ahh, can you disable APM just for kicks to see if that makes things any better? Nate