LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Boot hangs intermittently Fedora 22 (https://www.linuxquestions.org/questions/linux-newbie-8/boot-hangs-intermittently-fedora-22-a-4175545676/)

lujate 06-17-2015 07:01 PM

Boot hangs intermittently Fedora 22
 
I did a clean install of Fedora 22 on my laptop. It will intermittently hang on boot. It gets as far as the Fedora logo and stops. I have to do a hard boot and try again. It usually takes several tries before it boots successfully.

I've checked boot.log but didn't see anything clues there. I wanted to turn of verbose messages during startup, but I can't find my grub.conf (I'm guessing that file no longer exists).

Once it hangs and I press the power button once, the Fedora logo goes away and these two messages appear.
Code:

[drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR uncleared pch fifo underrun on pch transcoder A

[drm:interl_pch_fifo_underrun_irq_handler [i915]] *ERROR PCH transcoder A FIFO underrun


Any suggestions as to what to try/check?

TIA

syg00 06-17-2015 07:55 PM

The file you're looking for is /boot/grub2/grub.cfg - not a good idea to update it directly though as it gets rebuilt automatically.
Better to update the actual boot entry for just that boot - at the boot menu, highlight the entry you want and hit "e" to edit it. Go down and remove the "rhgb" and "quiet" from the linux line and hit F10 to boot it. That way you'll get to see all the messages without the dopey splash screen. Post the last few lines.

John VV 06-17-2015 08:09 PM

the "quite" part in the RHGB should be able to be canceled during boot

just hit < esc >

but you WILL want to read the boot.log to see what is the issue

lujate 06-17-2015 08:35 PM

I checked boot.log and everything in there showed OK.

lujate 06-17-2015 09:08 PM

Here the last messages in the verbose startup:
Code:

Starting GNOME Display Manager...
[OK] Started Command Scheduler.
Starting Command Scheduler...
Starting Wait for Plymouth Boot Screen to Quit...
[OK] Started GNOME Display Manager.
[OK] Created slice user-42.slice.
Starting User Manager for UID 42...
[OK] Started Virtualization daemon.
[OK] Started User Manager for UID 42.


syg00 06-17-2015 10:09 PM

GDM - but who knows with systemd; it's designed to start services in parallel.
Guess you'll have to plough through journalctl looking for differences. You can limit the boot(s) you look at - and you'll need to if it's big.
Code:

jounalctl --list-boots | tail
journalctl -x -b

-b (-b 0) gets you the current boot; -b -1 the prior one ...

jefro 06-18-2015 07:33 PM

https://bbs.archlinux.org/viewtopic.php?id=183094 seems to suggest kernel issue.

Do any virtual screens still exist? (that main display wrong)

Guess you could fool with any bios settings if they exist. Look at any setting for video.

May have to put in different kernel to try the link's ideas.

lujate 06-18-2015 07:40 PM

Quote:

Originally Posted by syg00 (Post 5379066)
GDM - but who knows with systemd; it's designed to start services in parallel.
Guess you'll have to plough through journalctl looking for differences. You can limit the boot(s) you look at - and you'll need to if it's big.
Code:

jounalctl --list-boots | tail
journalctl -x -b

-b (-b 0) gets you the current boot; -b -1 the prior one ...

Here's the last page:
Code:

--
-- The start-up result is done.
Jun 18 17:39:30 aw15147 audit[1]: <audit-1130> pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=upower comm="sys
Jun 18 17:39:30 aw15147 kernel: snd_hda_intel 0000:01:00.1: Disabling via VGA-switcheroo
Jun 18 17:39:30 aw15147 kernel: sound hdaudioC1D0: HDMI: invalid ELD buf size -1
Jun 18 17:39:30 aw15147 kernel: sound hdaudioC1D0: HDMI: invalid ELD buf size -1
Jun 18 17:39:30 aw15147 kernel: snd_hda_intel 0000:01:00.1: Cannot lock devices!
Jun 18 17:39:30 aw15147 kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (2015020
Jun 18 17:39:30 aw15147 kernel: ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
Jun 18 17:39:30 aw15147 kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (2015020
Jun 18 17:39:31 aw15147 gnome-session[1287]: glamor: EGL version 1.4 (DRI2):
Jun 18 17:39:31 aw15147 kernel: sound hdaudioC1D0: HDMI: ELD buf size is 0, force 128
Jun 18 17:39:31 aw15147 kernel: sound hdaudioC1D0: HDMI: invalid ELD data byte 0
Jun 18 17:39:31 aw15147 kernel: sound hdaudioC1D0: HDMI: ELD buf size is 0, force 128
Jun 18 17:39:31 aw15147 kernel: sound hdaudioC1D0: HDMI: invalid ELD data byte 0
Jun 18 17:39:31 aw15147 kernel: sound hdaudioC1D0: HDMI: ELD buf size is 0, force 128
Jun 18 17:39:31 aw15147 kernel: sound hdaudioC1D0: HDMI: invalid ELD data byte 0
Jun 18 17:39:32 aw15147 /usr/libexec/gdm-wayland-session[1274]: Activating service name='org.a11y.Bus'
Jun 18 17:39:32 aw15147 /usr/libexec/gdm-wayland-session[1274]: Successfully activated service 'org.a11y.Bus'
Jun 18 17:39:32 aw15147 org.a11y.Bus[1276]: Activating service name='org.a11y.atspi.Registry'
Jun 18 17:39:32 aw15147 org.a11y.Bus[1276]: Successfully activated service 'org.a11y.atspi.Registry'
Jun 18 17:39:32 aw15147 org.a11y.atspi.Registry[1424]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jun 18 17:39:32 aw15147 org.a11y.atspi.Registry[1424]: Xlib:  extension "XEVIE" missing on display ":1024".
Jun 18 17:39:32 aw15147 rtkit-daemon[782]: Successfully made thread 1433 of process 1433 (/usr/bin/pulseaudio) owned by '42' high priority at nice le
Jun 18 17:39:32 aw15147 rtkit-daemon[782]: Supervising 1 threads of 1 processes of 1 users.
Jun 18 17:39:33 aw15147 NetworkManager[889]: <info>  (virbr0-nic): link disconnected (calling deferred action)
Jun 18 17:39:40 aw15147 audit[1]: <audit-1131> pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-d
Jun 18 17:40:28 aw15147 systemd-logind[786]: Power key pressed.
Jun 18 17:40:28 aw15147 systemd-logind[786]: Powering Off...
Jun 18 17:40:28 aw15147 systemd-logind[786]: System is powering down.
-- Subject: System shutdown initiated
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Systemd shutdown has been initiated. The shutdown has now begun and
-- all system services are terminated and all file systems unmounted.


lujate 06-18-2015 07:43 PM

Quote:

Originally Posted by jefro (Post 5379559)
https://bbs.archlinux.org/viewtopic.php?id=183094 seems to suggest kernel issue.

Do any virtual screens still exist? (that main display wrong)

Guess you could fool with any bios settings if they exist. Look at any setting for video.

May have to put in different kernel to try the link's ideas.

I'm not sure what "virtual screens" are. How can I check for them?


All times are GMT -5. The time now is 03:50 AM.