Date: Wed, 29 Mar 2000 19:32:10 +0200 (CEST) From: Bart van Leeuwen <bart@ixori.demon.nl> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Dave Boers <djb@wit389306.student.utwente.nl>, Tommy Hallgren <thallgren@yahoo.com>, Jeremiah Gowdy <jgowdy@home.com>, freebsd-smp@freebsd.org Subject: Re: SMP and vn Message-ID: <Pine.BSF.4.21.0003291921510.359-100000@isengard.ixori.demon.nl> In-Reply-To: <200003291604.IAA63016@apollo.backplane.com>
index | next in thread | previous in thread | raw e-mail
I agree that that is what should happen, but it doesn't. Even when trying to break into DDB from a serial port connected terminal (with that serial port as my console) does not work in my case, besides, when it does panic, I do get the panic on my console, reardless of X running on anothr tty. Just for the record, during normal operation I can break into DDB from my console, so that functionality DOES work. Also, when the system panics, it will auto reboot after a timeout (unless configured with DDB and not configured as unatended). When the system panics, and I have a dumpdev defined, I would also expect to get a dump which will be saved by savecore, however, I don't. So... I'm inclined to say that the system is frozen and tho it might very well be that it should have paniced here, instead it locks up completely. Only 2 things that do still function are the power and reset buttons. But eh, I agree, getting into DDB in this case is one of the things tha would be very helpfull in resolving this. If anyone has suggestions how I could acomplish that I would be interested. Things I tried that did not work: - build a kernel with DDB support - try to get it into DDB on a panic (so.. not unatended) - break into DDB from the console when it is 'frozen', both from serial port as from 'built in' console Bart van Leeuwen ----------------------------------------------------------- mailto:bart@ixori.demon.nl - http://www.ixori.demon.nl/ ----------------------------------------------------------- On Wed, 29 Mar 2000, Matthew Dillon wrote: > > :That may be, but though I've got most of my lockups when X was running, in > :most cases X was doing the screen saver (blank screen) and I was logged in > :remote (or the system hang occurred during the night). > : > :Anyway, the system hangs don't seem to be related to heavy memory usage. > :(Even people with Asus dual pentium boards get smp related system hangs.) > :Also, my Abit BP6 board was just fine (uptimes of 20+ days or so ;- between > :-current updates) up and until last christmas or so. > : > :So, I'm not inclined to thinking it's a hardware problem at all. > : > : Regards, > : > : Dave. > > I suspect you are getting a panic, but due to X running you can't > see it. The goal should be to get to a DDB prompt on the console > to be able to see the panic and 'trace' and 'ps', and then to > (if possible) get a kernel core by typing 'panic' from the DDB prompt. > > What you want to do is compile the DDB kernel config option into the > kernel, then switch out of the X session (typically with ctl-alt-F1 or > F2) before you leave for the day. If it crunches while you are > accessing it remotely, when you come in the next day you should see a > DDB prompt and a panic message and be able to 'trace', 'ps', and then > 'panic' the system. > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003291921510.359-100000>