Date: Tue, 09 Oct 2007 07:01:18 -0400 From: Randall Stewart <rrs@cisco.com> To: freebsd-current@freebsd.org Cc: Michael Tuexen <tuexen@fh-muenster.de> Subject: Re: AMD64 panic on boot Message-ID: <470B5F7E.9040307@cisco.com> In-Reply-To: <470AE40D.7090006@cisco.com> References: <470AE33B.7000806@cisco.com> <470AE40D.7090006@cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok... after a bit of poking around and recompiling.. and yet another sync to current.. its a no-op.. Turns out I had some modified files that I did not realize on my machine .. that were actually old .. not new.. So, with the proper update to current.. all is well both my 8 core AMD's are back up again (Michael, you should be able to access these now). R Randall Stewart wrote: > Randall Stewart wrote: > >> Hi all: >> >> I just updated to the latest.. and I am seeing a crash on >> boot up of my 8-core Xeon machines (running in AMD mode). >> >> its a >> >> pagefault UA= 0x2b >> >> sysctl_handle_int+0x27 >> syscall+0x254 >> Xfast_syscall+0xab >> >> IP= 0xffffffff8048e7d7 >> >> >> I can't get a core unfortunately.. I get a core device >> unavailable.. >> >> I have one of the machines sitting in a DDB> prompt >> and its twin sitting on the old kernel.. >> >> Let me know how I can help.. and in the mean time I will poke >> around in kgdb on the running machine :-) >> >> R > > Hmm.. it appears to be in.. > 0xffffffff8048e2e7 is in sysctl_handle_int > (../../../kern/kern_sysctl.c:816). > 811 */ > 812 if (arg1) > 813 tmpout = *(int *)arg1; > 814 else > 815 tmpout = arg2; > 816 error = SYSCTL_OUT(req, &tmpout, sizeof(int)); > 817 > 818 if (error || !req->newptr) > 819 return (error); > > > So its trying to copy out and faulting.. not sure what.. > > Let me know if there is some info I can poke out of DDB > > R > > -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 <or> 803-317-4952 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?470B5F7E.9040307>