Ask Your Question
1

correct way to report when new release hangs on boot

asked 2016-04-16 19:28:15 -0500

scottf gravatar image

updated 2016-04-17 15:25:05 -0500

Hi All, from a Fedora newbie:

I installed Fedora 4.2.3-300 Desktop on an Intel NUC NUC5CPYH computer, and that version works great.

A little later, I get a message automagically that says I should upgrade to 4.4.6-301, so I do that.

Now, when I try to start 4.4.6, it hangs during boot. Fortunately I can load 4.2.3, so I'm not totally stuck.

Two questions:

  1. What's the right way to report the hang back to the community so that someone smarter than me can look at the issue and possibly fix it?
  2. Is there a simple way to get Fedora to show a verbose boot instead of the Fedora icon, so that I can get some information about exactly where it hangs?

Thank you.


Update, info on video sliced 2 ways:

 1.
$ lspci -vnn | grep VGA -A 12
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
    DeviceName:  CPU
    Subsystem: Intel Corporation Device [8086:2060]
    Flags: bus master, fast devsel, latency 0, IRQ 118
    Memory at 80000000 (64-bit, non-prefetchable) [size=16M]
    Memory at 88000000 (64-bit, prefetchable) [size=128M]
    I/O ports at f000 [size=64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: <access denied>
    Kernel driver in use: i915
    Kernel modules: i915

2.
$ sudo lshw -numeric -C display
  *-display               
       description: VGA compatible controller
       product: Intel Corporation [8086:22B1]
       vendor: Intel Corporation [8086]
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 21
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:118 memory:80000000-80ffffff memory:88000000-8fffffff ioport:f000(size=64)

Here are the last lines of the bootlog for the hanging 4.4.6 release:

Apr 17 15:37:34 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 17 15:37:34 localhost.localdomain systemd[1]: Started Create Static Device Nodes in /dev.
Apr 17 15:37:34 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 17 15:37:34 localhost.localdomain kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Apr 17 15:37:34 localhost.localdomain systemd[1]: Mounted NFSD configuration filesystem.
Apr 17 15:37:34 localhost.localdomain systemd[1]: Started Configure read-only root support.
Apr 17 15:37:34 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fedora-readonly comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 17 15:37:34 localhost.localdomain systemd[1]: Starting Load/Save Random Seed...
Apr 17 15:37:34 localhost.localdomain systemd[1]: Starting udev Kernel Device Manager...
Apr 17 15:37 ...
(more)
edit retag flag offensive close merge delete

Comments

2.) boot the crashing kernel, then boot the good kernel, and run 'journalctl -b-1', which gives you the boot log of the boot prior to the actual boot.

What graphics adapter you have?

florian gravatar imageflorian ( 2016-04-16 22:28:28 -0500 )edit

Thanks heis2201 ... video info, see above. As for the bootlog, it's 948 lines and I'm not exactly sure what I'm looking for -- would posting it here help?

scottf gravatar imagescottf ( 2016-04-17 14:56:45 -0500 )edit

genodeftest, I will pursue this, thank you for your answer.

scottf gravatar imagescottf ( 2016-04-17 15:16:52 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-04-17 08:15:01 -0500

genodeftest gravatar image

1.) I'd report it on bugzilla. Look here for duplicates first, then press the "+" to enter a new bug report. You'll need a bugzilla account for that. There is a mailing list and the #fedora-kernel IRC channel on that. The wiki has a list of commonly known issues and a general help page with links on how to build your own kernel. If you have spare time, bisecting the issue would probably help finding the code causing the issue.

2.) Have a look at the comment above. Additionally you may want to change kernel boot parameters. As far as I know they default to "rhgb quiet". If you remove "quiet", you get more verbose logging. This document has a long list of possible parameters. "debug" might be of interest to you.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-04-16 19:28:15 -0500

Seen: 146 times

Last updated: Apr 17 '16