Date: Tue, 20 Jun 2006 19:31:48 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-alpha@freebsd.org, linimon@freebsd.org Subject: Re: alpha/67626: X crashes an alpha machine, resulting reboot Message-ID: <20060620173147.GB14871@cicely12.cicely.de> In-Reply-To: <200606201249.25983.jhb@freebsd.org> References: <200510231839.j9NIdHnj002910@freefall.freebsd.org> <200606190856.55473.jhb@freebsd.org> <20060620.233256.345485143.furutaka@jb3.so-net.ne.jp> <200606201249.25983.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 20, 2006 at 12:49:25PM -0400, John Baldwin wrote: > On Tuesday 20 June 2006 10:32, Kazuyoshi Furutaka wrote: > > Dear John, Mark and all others, > > > > From: John Baldwin <jhb@freebsd.org> > > Subject: Re: alpha/67626: X crashes an alpha machine, resulting reboot > > Date: Mon, 19 Jun 2006 08:56:55 -0400 > > > > > We'd really need a stacktrace to help. It would also be useful to know > > > if more recent versions of the OS (such as 6.1) exhibit the same problems. > > > > > > As far as getting serial console working, you don't need to create a > > > /boot.config file (that is i386-specific). However, you need to get SRM > > > to use the serial console and then the loader and kernel will use it. > It's > > > been a while since I set it up, but I would look at your SRM variables and > > > see if there's a CONSOLE variable you can set to SERIAL instead of VIDEO > > > (IIRC). You can then try running 'init' from SRM to restart SRM which > > > should then show up on your serial console. You might be able to find > more > > > definitive instructions on using SRM with a serial console via a web > search. > > > > Well, could you tell me how I can collect more information from > > the current installation, in addition to the attached ? > > > > Later I'll test more recent versions... > > A 0x670 vector machine check indicates a hardware failure specific to the > CPU such as a cache failure. On some machine modells it could also be accessing non exiting memory, which can point to a broken memory mapped videocard driver. If the video card is on a secondary bus it can also be a sparse initialisation problem related to PCI-PCI bridges. Moving slots may help in that case. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060620173147.GB14871>