r270287: crash
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). Thanks, help appreciated and what is about this crash affecting recent CURRENT r270287, what has corrupted the system? Regards, Oliver signature.asc Description: PGP signature
Re: r270287: crash
On Aug 21, 2014, at 12:26 PM, O. Hartmann wrote: > 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 your 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’t have/need any customizations. > Thanks, help appreciated and what is about this crash affecting recent > CURRENT r270287, what has corrupted the system? That’s a better question. Booting off newer sources worked on my VM at least, but it’s not real hardware. Maybe something dealing with vt(4)/xen? HTH! -Garrett signature.asc Description: Message signed with OpenPGP using GPGMail
Re: r270287: crash
On Thu, Aug 21, 2014 at 12:32 PM, wrote: > On Aug 21, 2014, at 12:26 PM, O. Hartmann wrote: > >> 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 your 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’t have/need any customizations. > >> Thanks, help appreciated and what is about this crash affecting recent >> CURRENT r270287, what has corrupted the system? > > That’s a better question. Booting off newer sources worked on my VM at least, > but it’s not real hardware. Maybe something dealing with vt(4)/xen? One important note is that my CURRENT VM on my Macbook runs i386, not amd64. Cheers, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r270287: crash
On Thu, Aug 21, 2014 at 09:26:19PM +0200, O. Hartmann wrote: > 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. Are you using VirtualBox? I just fixed a crash that fits your description by recompiling virtualbox-ose-kmod. Marcus ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r270287: crash
On Fri, 22 Aug 2014 15:02:46 -0400 Marcus Reid wrote: > On Thu, Aug 21, 2014 at 09:26:19PM +0200, O. Hartmann wrote: > > 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. > > Are you using VirtualBox? I just fixed a crash that fits your > description by recompiling virtualbox-ose-kmod. > > Marcus I indeed use VirtualBox, but as of this moment, I have disabled the loading of the kernel module. The box still gets stuck and for unknown reason, ALL() CURRENT systems (different generatins of hardware, with or without integrated GPU) show question marks on the screen and no usefull screen when vt is enabled and in backward vga compatible mode. This also happens with nVidia dedicated PCIe GPUs as well as with Ivy Bridge integrated IGP 2500. The port virtualbox-ose-kmod is compiled everytime I compile a kernel/kernel mods via PORTS_MODULES="emulators/virtualbox-ose-kmod" in /etc/src.conf. This unmature vt stuff starts to bother. signature.asc Description: PGP signature
