On 2014-11-19 21:48, vixsomnis wrote: > On November 19, 2014 3:40:38 PM EST, Mark Lee <mark@xxxxxxxxxxxx> wrote: > >On 11/19/2014 12:15 PM, Rasmus Liland wrote: > >> On 2014-11-17 00:19, Rasmus Liland wrote: > >>> 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. > >> > >> A breakthrough in this thread has happened. > >> > >> I ended up taking a backup of the disk to an external hdd using > >> > >>> # dd if=/dev/sda of=/mnt/angrist-sda-18nov14.img > >> > >> then I booted FreeBSD 10.1 memstick, entered shell and entered some > >> commands: > >> > >>> [ ... cut, see previously archived message for output ... ] > >> > >> Then I rebooted into ArchLinux iso memstick to install Arch on the > >> 20G partition and using the other one as /home. So now Syslinux > >> works, unfortunately I don't know why. And I was able to install > >> all new packages including linux 3.17.3-1 and intel-ucode > >> 20140913-1, loading it in Syslinux according to the wiki. > >> > >> I got a new mce after exactly three hours: > >> > >>> [ ... cut, see previously archived message for output ... ] > >> > >> I am also making this output an attachment. There is a lot of more > >> information in this new mce compared to the other one I sent. > >> > >> Perhaps some of you got some new suggestions. > >> > >> Meanwhile, I am downgrading back to 3.11.5-1. > >> > > > >To Rasmus, > > > >Can you run the parts where it says "run the abvoe through mcelog > >- --ascii" and post the contents? > > > >Regards, > >Mark > > I may have had a similar error, but I can't remember the details. Have you > checked if your hardware clock is synchronized? It fixed my kernel panic > issues. > -- > vixsomnis This is interesting. Do you mean synchronizing via NTP protocol? My experience from this laptop is that the RTC quickly becomes desynchronized at times when I am not able to sync via OpenNTPd, i.e. when I am not connected to the internet. -- Rasmus Liland, jrl@xxxxxxxxxxxxx, jens.rasmus.liland@xxxxxxx
Attachment:
pgpKLWkBCxpma.pgp
Description: PGP signature
