On 03/12/2015 13:33, Jonathan Billings wrote:> On Thu, Dec 03, 2015 at 09:29:21AM +0000, Duncan Brown wrote: >> Hi All >> >> After upgrading to 7.2, I'm getting an immediate kernel panic on boot >> >> Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine >> >> How can I go about diagnosing the problem here? > It'd probably help if you could give us more details on the kernel > panic. > > Can you see where it is panicking? Does it happen during the > kernel/initrd stage or later during boot? > > I suggest installing the kdump service if it is panicking later in > boot, you might be able to capture a kernel dump which makes debugging > these things a lot easier. Otherwise, I suggest trying to capture the > panic message some other way. >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
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 notIt'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. -- Jonathan Billings <billings at negate.org>
On Thu, Dec 3, 2015 at 5:44 AM, Duncan Brown <centos2 at duncb.co.uk> wrote:> On 03/12/2015 13:33, Jonathan Billings wrote: >> >> On Thu, Dec 03, 2015 at 09:29:21AM +0000, Duncan Brown wrote: >>> >>> Hi All >>> >>> After upgrading to 7.2, I'm getting an immediate kernel panic on boot >>> >>> Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine >>> >>> How can I go about diagnosing the problem here? >> >> It'd probably help if you could give us more details on the kernel >> panic. >> >> Can you see where it is panicking? Does it happen during the >> kernel/initrd stage or later during boot? >> >> I suggest installing the kdump service if it is panicking later in >> boot, you might be able to capture a kernel dump which makes debugging >> these things a lot easier. Otherwise, I suggest trying to capture the >> panic message some other way. >> > The last message before it is "switching to clocksource hpet" > > Then the panic scrolls byMaybe an issue with X. Look into /var/log/Xorg.0.log for hints. Or, does it boot fine in single user mode? Akemi
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
On 03/12/2015 13:57, Akemi Yagi wrote:> On Thu, Dec 3, 2015 at 5:44 AM, Duncan Brown <centos2 at duncb.co.uk> wrote: >> On 03/12/2015 13:33, Jonathan Billings wrote: >>> On Thu, Dec 03, 2015 at 09:29:21AM +0000, Duncan Brown wrote: >>>> Hi All >>>> >>>> After upgrading to 7.2, I'm getting an immediate kernel panic on boot >>>> >>>> Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine >>>> >>>> How can I go about diagnosing the problem here? >>> It'd probably help if you could give us more details on the kernel >>> panic. >>> >>> Can you see where it is panicking? Does it happen during the >>> kernel/initrd stage or later during boot? >>> >>> I suggest installing the kdump service if it is panicking later in >>> boot, you might be able to capture a kernel dump which makes debugging >>> these things a lot easier. Otherwise, I suggest trying to capture the >>> panic message some other way. >>> >> The last message before it is "switching to clocksource hpet" >> >> Then the panic scrolls by > Maybe an issue with X. Look into /var/log/Xorg.0.log for hints. Or, > does it boot fine in single user mode? > > Akemi > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centosThe same thing happens in single user mode too