Date: Thu, 21 Aug 2014 13:47:11 -0700 From: Garrett Cooper <yaneurabeya@gmail.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: r270287: crash Message-ID: <CAGHfRMBESJuuWqwEqvSCgZjW1eXbUqvaFnQLjKAQGyWh144ciw@mail.gmail.com> In-Reply-To: <D87D8356-7D66-4696-AA0E-F4DFDD41C0A3@gmail.com> References: <20140821212619.6bdffad0@munin.walstatt.dyndns.org> <D87D8356-7D66-4696-AA0E-F4DFDD41C0A3@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 21, 2014 at 12:32 PM, <yaneurabeya@gmail.com> wrote: > On Aug 21, 2014, at 12:26 PM, O. Hartmann <ohartman@zedat.fu-berlin.de> w= rote: > >> FreeBSD r270287 crashes/reboots instantanously on loading the kernel. I >> can not see at what point (on modern systems like Ivy Bridge). On older >> Core2Duo systems I get a trap 12 in APIC or similar. >> >> While I was able to start kernel.old on the modern systems, I fail on >> both kernel and kernel.old on the C2D system. >> >> I'd like to know whether there is a way to save the system I can not >> reboot the on-disk kernels snce they are, woderfull, compromised. >> >> Is there a possible scenario like: >> >> a) boot from DVD ROM or USB most recent snapshot >> b) establish network with on-disk config, svn checkout recent sources >> into on-disk file hierarchy >> c) build repaired/patched kernel and install on on-disk (not on the >> emergency boot media). > > I would grab a snapshot ISO or USB disk image: ftp://ftp.freebsd.org/pub/= FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/11.0/ . After that you can mount y= our filesystems, revert to an earlier SVN revision, and repair your system = that way. You could also copy over the /boot/kernel as long as you didn=E2= =80=99t have/need any customizations. > >> Thanks, help appreciated and what is about this crash affecting recent >> CURRENT r270287, what has corrupted the system? > > That=E2=80=99s a better question. Booting off newer sources worked on my = VM at least, but it=E2=80=99s not real hardware. Maybe something dealing wi= th vt(4)/xen? One important note is that my CURRENT VM on my Macbook runs i386, not a= md64. Cheers, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGHfRMBESJuuWqwEqvSCgZjW1eXbUqvaFnQLjKAQGyWh144ciw>