On 2014-11-15 18:28, Mark Lee wrote:
On 11/15/2014 12:20 PM, Rasmus Liland wrote:
On 2014-11-15 15:21, LoneVVolf wrote:
On 15-11-14 06:57, Rasmus Liland wrote:
On 2014-11-15 06:10, Mark Lee wrote:
On 11/14/2014 10:29 PM, Rasmus Liland wrote:
On 2014-11-15 04:01, Mark Lee wrote: > Are you booting with the new intel u-code? Are you fairly sure this is a Intel microcode issue? I'm not completely certain; but it would make sense. I'd test it out. Thank you for your help thus far. I'll examine this further tomorrow, g'night. From rasmus first post: I'm experiencing machine check exceptions since every kernel after package linux-3.11.5-1 (Oct 14 2013) New intel microcode was only introduced with kernel 3.17 ... It's unlikely to have to do with this issue.
install mcelog, run it as the log tells you and post the result. [ ... output, see previous messages ... ] I never did use the mcelog tool before, but to me it looks like not much of an analysis, perhaps I'm doing it wrong. Looks like a microcode error, please try to add the intel-ucode to your kernel cmdline. Bah, just as I was finished enabling syslinux using syslinux-install_update and rebooted, the system did not respond, just a blank screen and lighting shutting off, then rebooting again.
Thus, this system needs an overhaul -- apparently some difficulty with the bootcode or the MBR, though I am able to mount the old partitions and chroot into them using arch-chroot. I tried installing grub using the standard method grub-install according to the wiki, with little success -- some good news at least relevant to previous topic in this thread is that grub recognized and added the intel-ucode file I had copied to the /boot directory, when running grub-mkconfig. The plan forward is to forget about generating new mbr using gpart and install Debian at the end of the disk to, hopefully, restore some boot related stuff that might have come crashing down after meddling with syslinux. I was able to jot down this at my remote terminal. -- Rasmus Liland, jrl@jrl.dyndns.dk