Date: Mon, 10 Nov 2003 19:05:38 +0200 From: John Hay <jhay@icomtek.csir.co.za> To: Marius Strobl <marius@alchemy.franken.de> Cc: current@freebsd.org Subject: Re: New interrupt stuff breaks ASUS 2 CPU system Message-ID: <20031110170538.GA44941@zibbi.icomtek.csir.co.za> In-Reply-To: <20031110172540.A29948@newtrinity.zeist.de> References: <20031106152721.J95465@beagle.fokus.fraunhofer.de> <XFMail.20031106122245.jhb@FreeBSD.org> <20031110172540.A29948@newtrinity.zeist.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > With the new interrupt code I get: > <...> > OK boot > cpuid = 0; apic id = 00 > instruction pointer = 0x0:0xa00 > stack pointer = 0x0:0xffe > frame pointer = 0x0:0x0 > code segment = base 0x0, limit 0x0, type 0x0 > = DPL 0, pres 0, def32 0, gran 0 > processor eflags = interrupt enabled, vm86, IOPL = 0 > current process = 0 () > kernel: type 30 trap, code=0 > Stopped at 0xa00: cli > db> tr > (null)(0,0,0,0,0) at 0xa00 > <...> > > However, if I enter 'continue' at the DDB prompt it continues to boot > and the system seems to runs fine: > > <...> > db> continue ... > Copyright (c) 1992-2003 The FreeBSD Project. > <...> > Now why didn't I think of trying 'continue'? Hey there my old dual Pentium I diskless machine is running in SMP mode. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031110170538.GA44941>