Duncan Brown wrote: > On 03/12/2015 17:00, m.roth at 5-cent.us wrote: >> Duncan Brown wrote: >>> On 03/12/2015 14:29, Leon Fauster wrote: >>>> Am 03.12.2015 um 15:06 schrieb Duncan Brown <centos2 at duncb.co.uk>: >>>>> On 03/12/2015 13:54, Jonathan Billings wrote: >>>>>> On Thu, Dec 03, 2015 at 01:44:47PM +0000, Duncan Brown wrote: >>>>>>> The last message before it is "switching to clocksource hpet" >>>>>>> >>>>>>> Then the panic scrolls by >>>>>>> >>>>>>> I've no idea if that counts as later or not >>>>>> It's unlikely to be a panic related to your hardware clock (HPET = High Precision Event Timer), so it's probably when the kernel is touching something else on your system. >>>>>> >>>>>> The content of the panic is really the only thing that can help. >>>>>> >>>>> That's what I figured, but how do I go about getting a copy of it? >>>>> >>>>> Most of it has scrolled by when it's finished >>>> start for example with a photo (or video and grab the frame where the panic occurs) and - disable grub options like rhgb or quit ... >>> Here is a couple of pictures, >> ^^ should be are.* >>> http://i.imgur.com/Vqvqn1H.jpg >>> http://i.imgur.com/WQaz1j9.png >>> >>> Any use? >> I'm just guessing here, but it looks to me as though it's looking at inodes - so filesystem, and kernel modules, maybe video - notice the blacklist. >> >> Wonder if this is a grub2 issue, and it's not finding the filesystem. This isn't, by chance, a secure boot, not BIOS, system? >> > No nothing that exciting, BIOS, and xfs on lvm2. Pretty much the standard options anaconda gives you > > And it boots fine in 3.10.0-229.20.1.el7.x86_64 A thought: did you say you'd rebuilt the ramfs, making sure both xfs and lvm drivers were included? mark
