Fedora 22 continuously rebooting

[Armelius Cameron]

Hello,

After the latest upgrade over the weekend, my laptop (Dell Latitute
E6540) continuously rebooting after restart. Before the restart (after
upgrade) everything seemed to be working OK.

Sometime the boot sequence wont even get as far as starting X before
rebooting. Sometime it starts X then sit for a few seconds, then
reboot automatically. I cannot make sense of what's going on.

I tried booting to the oldest kernel I have (4.2.6) and it's giving me
the same results.

Any help is appreciated. Thanks.

AC

[Sylvia Sánchez]

Hi!
Did you try to boot with previous kernel?  I find very likely there 
lies your problem. 
Just pick another kernel from the list in GRUB and see what 
happens.
Also, you can try booting a live pendrive/DVD to see if there's any 
hardware issue.

Cheers,
Sylvia

[Armelius Cameron]

Hello,
Yes, I tried all version of kernels I still have, and still getting
the same thing.

If I boot with "Rescue kernel" though, it stopped the infinite looping
reboot. So I can get into the system with Rescue, but then I am not
sure what to do from there.

I wondered if one of the services or one of the kernel module causes
this, but then I am confused as to why this also affects older kernel.

Thanks,
AC

On Tue, Jan 19, 2016 at 10:12 AM, Sylvia  wrote:
> Hi!
>
> Did you try to boot with previous kernel? I find very likely there lies your
> problem.
>
> Just pick another kernel from the list in GRUB and see what happens.
>
> Also, you can try booting a live pendrive/DVD to see if there's any hardware
> issue.
>
> Cheers,
>
> Sylvia
>
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Richard Shaw]

On Tue, Jan 19, 2016 at 9:17 AM, Armelius Cameron 
wrote:
> Hello,
> If I boot with "Rescue kernel" though, it stopped the infinite looping
> reboot. So I can get into the system with Rescue, but then I am not
> sure what to do from there.
>
> I wondered if one of the services or one of the kernel module causes
> this, but then I am confused as to why this also affects older kernel.

I would start looking through your logs, if the previous log was one that
rebooted soemthing like:

journalctl -b -1

should do the trick.

Richard

[Sylvia Sánchez]

Maybe a drivers issue? Looking through the logs as Richard said would be
useful ye.

Cheers,
Sylvia

On Tuesday, 19 January 2016, Richard Shaw  wrote:
> On Tue, Jan 19, 2016 at 9:17 AM, Armelius Cameron <[e-mail]
> > wrote:
> > Hello,
> > If I boot with "Rescue kernel" though, it stopped the infinite looping
> > reboot. So I can get into the system with Rescue, but then I am not
> > sure what to do from there.
> >
> > I wondered if one of the services or one of the kernel module causes
> > this, but then I am confused as to why this also affects older kernel.
>
> I would start looking through your logs, if the previous log was one that
> rebooted soemthing like:
>
> journalctl -b -1
>
> should do the trick.
>
> Richard

[Armelius Cameron]

Sorry for my lag in response, in between work meetings with
non-working laptop has made this an onerous day!

So I've tried the following kernel options, all to no-avail:
"systemd.unit=multi-user.target", still reboot after a few seconds, so
does this option remove video driver issue (radeon) ?
"acpi=off" or "noapic", kernel won't boot at all

Scrolling through the journal the only thing that caught my eyes is
the message "watchdog1 watchdog did not step". Searching on the web,
this caught my attention
(https://www.kernel.org/doc/Documentation/watchdog/watchdog-api.txt):
"A Watchdog Timer (WDT) is a hardware circuit that can reset the
computer system in case of a software fault.", which makes me go
"hm... does the kernel think it needs reboot all the time"

So I tried modifying the timeout in /etc/systemd/system.conf, but that
doesn't seem to have any effect either.

Thanks,
AC

On Tue, Jan 19, 2016 at 11:43 AM, Sylvia Sánchez  wrote:
> Maybe a drivers issue? Looking through the logs as Richard said would be
> useful ye.
>
> Cheers,
> Sylvia
>
> On Tuesday, 19 January 2016, Richard Shaw  wrote:
> > On Tue, Jan 19, 2016 at 9:17 AM, Armelius Cameron 
> > wrote:
> > > Hello,
> > > If I boot with "Rescue kernel" though, it stopped the infinite looping
> > > reboot. So I can get into the system with Rescue, but then I am not
> > > sure what to do from there.
> > >
> > > I wondered if one of the services or one of the kernel module causes
> > > this, but then I am confused as to why this also affects older kernel.
> >
> > I would start looking through your logs, if the previous log was one that
> > rebooted soemthing like:
> >
> > journalctl -b -1
> >
> > should do the trick.
> >
> > Richard
>
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Ed Greshko]

On 01/20/16 02:48, Armelius Cameron wrote:
> Sorry for my lag in response, in between work meetings with
> non-working laptop has made this an onerous day!
>
> So I've tried the following kernel options, all to no-avail:
> "systemd.unit=multi-user.target", still reboot after a few seconds, so
> does this option remove video driver issue (radeon) ?
> "acpi=off" or "noapic", kernel won't boot at all
>
> Scrolling through the journal the only thing that caught my eyes is
> the message "watchdog1 watchdog did not step". Searching on the web,
> this caught my attention
> (https://www.kernel.org/doc/Documentation/watchdog/watchdog-api.txt):
> "A Watchdog Timer (WDT) is a hardware circuit that can reset the
> computer system in case of a software fault.", which makes me go
> "hm... does the kernel think it needs reboot all the time"
>
> So I tried modifying the timeout in /etc/systemd/system.conf, but that
> doesn't seem to have any effect either.

You may be suffering from a series of unfortunate coincidences.

I had a similar scenario a few years back.  The frequency wasn't as great as yours, but
the system would reboot at random times.  Turned out to be a power supply issue.

I'd be looking at hardware since you've said the reboot happens at random points in the
boot process.

[Richard Shaw]

You could try booting into multi-user.target instead of graphical.target
and see if that helps since it doesn't appear to be releated to which
kernel you boot.

Add "systemd.unit=multi-user.target" to your kernel options or perhaps the
traditional "3" on the end still works?

Thanks,
Richard