Arch Linux

charli3

Member

Registered: 2015-06-01

Posts: 45

Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

My boot is broken after running

# pacman -Syu

.  My system was relatively up to date as I just ran a system wide upgrade a few days ago.  It appears to be just the Linux 4.3.3-2 Kernel package since I was able to boot into the system with my install usb and downgrade the package to the previous Kernal 4.2.1-4 and boot works as normal.  My hunch is it has something to do with the video drivers and the new kernal since the screen goes blank after the GRUB boot loader.  I'm running the core i7 with the Sky Lake chipset and have configured the kernel parameters per the wiki: https://wiki.archlinux.org/index.php/In … lake_chips. Here's a snippet of my

# journalctl -e -n4000

from before the reboot:

Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0: can't access the RSA semaphore it is write pro
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0: can't access the RSA semaphore it is write pro
Dec 31 23:59:10 charlie_cpu kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Dec 31 23:59:10 charlie_cpu kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Dec 31 23:59:10 charlie_cpu kernel: psmouse serio2: synaptics: queried max coordinates: x [..5712], y [.
Dec 31 23:59:10 charlie_cpu kernel: psmouse serio2: synaptics: queried min coordinates: x [1336..], y [1
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp_aux_ch not done status 0x2c0
Dec 31 23:59:10 charlie_cpu kernel: psmouse serio2: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, 
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeou
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_aux_ch [i915]] *ERROR* dp_aux_ch not done status 0xad4
Dec 31 23:59:10 charlie_cpu kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/
Dec 31 23:59:10 charlie_cpu kernel: mousedev: PS/2 mouse device common for all mice
Dec 31 23:59:10 charlie_cpu kernel: [drm] RC6 on
Dec 31 23:59:10 charlie_cpu kernel: ------------[ cut here ]------------
Dec 31 23:59:10 charlie_cpu kernel: WARNING: CPU: 2 PID: 121 at drivers/gpu/drm/i915/intel_dp.c:854 inte
Dec 31 23:59:10 charlie_cpu kernel: dp_aux_ch not started status 0xad40001f
Dec 31 23:59:10 charlie_cpu kernel: Modules linked in: joydev mousedev arc4 bnep iwlmvm mac80211 intel_r
Dec 31 23:59:10 charlie_cpu kernel:  ip_tables x_tables btrfs xor raid6_pq jitterentropy_rng sha256_ssse
Dec 31 23:59:10 charlie_cpu kernel: CPU: 2 PID: 121 Comm: kworker/u8:3 Not tainted 4.3.3-2-ARCH #1
Dec 31 23:59:10 charlie_cpu kernel: Hardware name: System76, Inc.                     Lemur             
Dec 31 23:59:10 charlie_cpu kernel: Workqueue: events_unbound async_run_entry_fn
Dec 31 23:59:10 charlie_cpu kernel:  0000000000000000 00000000efc1850a ffff88016bbab588 ffffffff812c0dc9
Dec 31 23:59:10 charlie_cpu kernel:  ffff88016bbab5d0 ffff88016bbab5c0 ffffffff81074f42 00000000ad40001f
Dec 31 23:59:10 charlie_cpu kernel:  0000000000064010 0000000000064014 ffff88016d5b0000 0000000000000006
Dec 31 23:59:10 charlie_cpu kernel: Call Trace:
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff812c0dc9>] dump_stack+0x4b/0x72
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81074f42>] warn_slowpath_common+0x82/0xc0
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81074fdc>] warn_slowpath_fmt+0x5c/0x80
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07cb5c4>] intel_dp_aux_ch+0x114/0x690 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff810b5dc0>] ? wake_atomic_t_function+0x60/0x60
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07cbc15>] intel_dp_aux_transfer+0xd5/0x1e0 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa055acf4>] drm_dp_dpcd_access+0x64/0x110 [drm_kms_helper]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa055aebb>] drm_dp_dpcd_write+0x1b/0x20 [drm_kms_helper]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07cdb3f>] intel_dp_start_link_train+0x7f/0x2e0 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07c248d>] intel_ddi_pre_enable+0x10d/0x320 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07a922b>] haswell_crtc_enable+0x40b/0xb70 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07a4931>] ? intel_display_port_power_domain+0x61/0xa0 [i
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07a4e8b>] intel_atomic_commit+0x39b/0x13d0 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa04827a5>] ? drm_atomic_check_only+0x215/0x540 [drm]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa0482b07>] drm_atomic_commit+0x37/0x60 [drm]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa05639af>] drm_atomic_helper_set_config+0x1bf/0x420 [drm_
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa0471642>] drm_mode_set_config_internal+0x62/0x100 [drm]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa0565a23>] restore_fbdev_mode+0xb3/0x110 [drm_kms_helper]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa05679b5>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa0567a2d>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helpe
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07bb58a>] intel_fbdev_set_par+0x1a/0x60 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8132a1d0>] fbcon_init+0x570/0x5f0
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff813a36ea>] visual_init+0xca/0x130
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff813a520e>] do_bind_con_driver+0x1be/0x3e0
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff813a5769>] do_take_over_console+0x149/0x1a0
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8132a2a7>] do_fbcon_takeover+0x57/0xb0
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8132e418>] fbcon_event_notify+0x658/0x750
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81093b2a>] notifier_call_chain+0x4a/0x70
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81093ed7>] __blocking_notifier_call_chain+0x47/0x60
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81093f06>] blocking_notifier_call_chain+0x16/0x20
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8133419b>] fb_notifier_call_chain+0x1b/0x20
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8133632f>] register_framebuffer+0x20f/0x350
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa0567caf>] drm_fb_helper_initial_config+0x25f/0x5b0 [drm_
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffffa07bc00b>] intel_fbdev_initial_config+0x1b/0x20 [i915]
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81095598>] async_run_entry_fn+0x48/0x150
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8108cfeb>] process_one_work+0x14b/0x440
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8108d328>] worker_thread+0x48/0x4a0
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8108d2e0>] ? process_one_work+0x440/0x440
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81092e68>] kthread+0xd8/0xf0
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81092d90>] ? kthread_worker_fn+0x170/0x170
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff8158409f>] ret_from_fork+0x3f/0x70
Dec 31 23:59:10 charlie_cpu kernel:  [<ffffffff81092d90>] ? kthread_worker_fn+0x170/0x170
Dec 31 23:59:10 charlie_cpu kernel: ---[ end trace d55f36cd15a5f4b6 ]---
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link
Dec 31 23:59:10 charlie_cpu kernel: wlp2s0: authenticate with a8:54:b2:5b:8d:5d
Dec 31 23:59:10 charlie_cpu kernel: wlp2s0: send auth to a8:54:b2:5b:8d:5d (try 1/3)
Dec 31 23:59:10 charlie_cpu kernel: wlp2s0: authenticated
Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supporte
Dec 31 23:59:10 charlie_cpu kernel: iwlwifi 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not support
Dec 31 23:59:10 charlie_cpu kernel: wlp2s0: associate with a8:54:b2:5b:8d:5d (try 1/3)
Dec 31 23:59:10 charlie_cpu kernel: wlp2s0: RX AssocResp from a8:54:b2:5b:8d:5d (capab=0x411 status=0 ai
Dec 31 23:59:10 charlie_cpu kernel: wlp2s0: associated
Dec 31 23:59:10 charlie_cpu kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Dec 31 23:59:10 charlie_cpu kernel: [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to start ch
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_compo
Dec 31 23:59:10 charlie_cpu kernel: Console: switching to colour frame buffer device 240x67
Dec 31 23:59:10 charlie_cpu kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VC: line_out
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
Dec 31 23:59:10 charlie_cpu kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12

Thanks in advance for the help!

Last edited by charli3 (2016-01-05 00:09:21)

fdservices

Member

From: France

Registered: 2012-02-06

Posts: 413

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

Do you have an Nvidia GPU? I had to downgrade on my desktop because of that. In my case it was mainly the compositing that no longer worked. I have not looked into it further yet.

Andrew

leuchtturm

Member

Registered: 2015-11-30

Posts: 9

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

Same problem here with skylake and HD 520 graphics. no nvidia card.

Have you tried it with an external monitor (assuming you have a laptop)? If i plug in an external monitor the external one works at least. Then I tried some more or random xrandr command until it worked:

xrandr --output eDP1 --off
xrandr --output eDP1 --auto

I put that in a script and have it run as session-starter-script with lightdm greeter. After logging in, everything works alright at least. The funny thing, it sort of works when not having an external monitor connected as well. You just need to know how to login without seeing anything, because the greeter doesn't show up at all and even after logging in, I need to force my laptop into sleep and turn it back one and suddenly it works. I am using kernel 4.3.3-2.

I hope I could helo you to get it at least working to some extend, it's not satisfying though.

charli3

Member

Registered: 2015-06-01

Posts: 45

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

Do you have an Nvidia GPU?

Nope, it's the Intel Core i7-6500U with integrated graphics. 

Have you tried it with an external monitor (assuming you have a laptop)?

I haven't tried that yet, but I will give it a try, thanks!

pressman57

Member

Registered: 2011-12-18

Posts: 26

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

nvidia-304xx is broken as well with the new kernel. I downgraded both to get x running again.

---

An ignorant man is one who doesn't know what I just found out.

loqs

Member

Registered: 2014-03-06

Posts: 18,426

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

@charli3,  leuchtturm have either of you tried the 4.4-rc7 kernel to see if that improves the situation?
As a note i915.preliminary_hw_support=1 should not be needed with the 4.3 kernel or above for skylake GPU support.

leuchtturm

Member

Registered: 2015-11-30

Posts: 9

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

Not yet, due to the circumstance that this is my only computer and I need it at the moment and don't  really have time to fix any major issues . Might try it this weekend

charli3

Member

Registered: 2015-06-01

Posts: 45

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

@leuchtturm, I am able to see the login screen when connected to a monitor and running

xrandr --output eDP1 --off && xrandr --output eDP1 --auto

seems to have done the trick.  However, it would be nice to be able to boot without the monitor since I am on a laptop.

leuchtturm

Member

Registered: 2015-11-30

Posts: 9

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

Can you see it on the laptop monitor, too or only on the external one?

I can login without extra monitor, however, I don't see what I am doing. I just have to press tab twice, enter password and press enter which logs me in with my greeter. After that, I close the lid or press the power button to have the laptop suspend and wake it up again. Then it "works".

I have installed the linux-mailine package from the AUR and it works just fine.

Last edited by leuchtturm (2016-01-02 12:11:46)

charli3

Member

Registered: 2015-06-01

Posts: 45

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

@leuchtturm, I haven't tried loging in without the monitor to give me a login prompt. I'm guessing that would work (sames as yours 'blind'...), but I didn't bother to set up a script to run at login with the 'xrandr' commands since the linux-lts kernel works just fine for me.  I'm ideally looking for a more permanent less hacker-ish solution...

Last edited by charli3 (2016-01-04 20:29:42)

loqs

Member

Registered: 2014-03-06

Posts: 18,426

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

@charli3

I have installed the linux-mailine package from the AUR and it works just fine.

See also https://bbs.archlinux.org/viewtopic.php?id=206979

charli3

Member

Registered: 2015-06-01

Posts: 45

Re: Boot broken after upgrading to Linux Kernel 4.3.3 [Solved]

Just finished installing the linux-mainline kernel from the AUR.  Additionally I had to remove the 'i915.preliminary_hw_support=1' kernal perameter from the boot-loader in order for the monitor to work after boot.  Monitor works as expected now. Marking this as [Solved].

Last edited by charli3 (2016-01-05 00:10:25)