> These messages should still be copied to /var/log/messages. However if > you're using sysvinit, they might go into /var/log/dmesg instead. > Please check there. > > Ben.
Hi Ben, you are correct, I found these messages in /var/log/messages. I send them below, maybe they are useful: ------- snip ----------- Aug 14 16:20:50 localhost kernel: [ 22.342509] ------------[ cut here ]------------ Aug 14 16:20:50 localhost kernel: [ 22.342534] WARNING: CPU: 1 PID: 102 at / build/linux-J4LMtv/linux-4.11.6/drivers/gpu/drm/drm_atomic_helper.c:796 drm_atomic_helper_update_legacy_modeset_state+0x232/0x260 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.342536] Modules linked in: snd_hda_codec_realtek snd_hda_codec_generic sg ath9k(+) ath9k_common snd_hda_intel ath9k_hw ath snd_hda_codec snd_hda_core snd_hwdep lpc_ich snd_pcm_oss mfd_core mac80211 snd_mixer_oss i915 snd_pcm rng_core snd_timer cfg80211 drm_kms_helper snd soundcore shpchp drm i2c_algo_bit eeepc_laptop(+) sparse_keymap rfkill battery ac video button wmi acpi_cpufreq gspca_sn9c20x gspca_main v4l2_common videodev media loop atl1 mii parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto mbcache ecb lrw gf128mul algif_skcipher af_alg uas usb_storage dm_crypt dm_mod crypto_simd cryptd aes_i586 sd_mod ahci libahci libata psmouse scsi_mod uhci_hcd ehci_pci ehci_hcd usbcore usb_common atl1c thermal Aug 14 16:20:50 localhost kernel: [ 22.342665] CPU: 1 PID: 102 Comm: kworker/u4:2 Not tainted 4.11.0-1-686-pae #1 Debian 4.11.6-1 Aug 14 16:20:50 localhost kernel: [ 22.342668] Hardware name: ASUSTeK Computer INC. \x931005HAG\x94/1005HAG, BIOS 0401 03/02/2010 Aug 14 16:20:50 localhost kernel: [ 22.342678] Workqueue: events_unbound async_run_entry_fn Aug 14 16:20:50 localhost kernel: [ 22.342682] Call Trace: Aug 14 16:20:50 localhost kernel: [ 22.342695] ? dump_stack+0x55/0x73 Aug 14 16:20:50 localhost kernel: [ 22.342701] ? __warn+0xea/0x110 Aug 14 16:20:50 localhost kernel: [ 22.342716] ? drm_atomic_helper_update_legacy_modeset_state+0x232/0x260 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.342729] ? drm_atomic_helper_update_legacy_modeset_state+0x232/0x260 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.342735] ? warn_slowpath_null+0x2a/ 0x30 Aug 14 16:20:50 localhost kernel: [ 22.342748] ? drm_atomic_helper_update_legacy_modeset_state+0x232/0x260 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.342890] ? intel_atomic_commit_tail +0x945/0xee0 [i915] Aug 14 16:20:50 localhost kernel: [ 22.342899] ? __switch_to+0xa1/0x3a0 Aug 14 16:20:50 localhost kernel: [ 22.343031] ? intel_atomic_commit +0x388/0x460 [i915] Aug 14 16:20:50 localhost kernel: [ 22.343061] ? drm_mode_object_reference +0x3e/0x60 [drm] Aug 14 16:20:50 localhost kernel: [ 22.343089] ? drm_atomic_set_crtc_for_connector+0xb1/0x100 [drm] Aug 14 16:20:50 localhost kernel: [ 22.343116] ? drm_atomic_commit+0x4b/ 0x60 [drm] Aug 14 16:20:50 localhost kernel: [ 22.343130] ? restore_fbdev_mode +0x153/0x2c0 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.343157] ? drm_modeset_lock_all_ctx +0xa4/0xb0 [drm] Aug 14 16:20:50 localhost kernel: [ 22.343171] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.343184] ? drm_fb_helper_set_par +0x2d/0x63 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.343316] ? intel_fbdev_set_par +0x15/0x70 [i915] Aug 14 16:20:50 localhost kernel: [ 22.343329] ? fbcon_init+0x53d/0x590 Aug 14 16:20:50 localhost kernel: [ 22.343338] ? visual_init+0xbb/0x120 Aug 14 16:20:50 localhost kernel: [ 22.343344] ? do_bind_con_driver +0x174/0x360 Aug 14 16:20:50 localhost kernel: [ 22.343351] ? do_take_over_console +0x11b/0x190 Aug 14 16:20:50 localhost kernel: [ 22.343358] ? do_fbcon_takeover+0x5f/ 0xc0 Aug 14 16:20:50 localhost kernel: [ 22.343366] ? notifier_call_chain+0x4e/ 0x70 Aug 14 16:20:50 localhost kernel: [ 22.343374] ? __blocking_notifier_call_chain+0x39/0x60 Aug 14 16:20:50 localhost kernel: [ 22.343381] ? blocking_notifier_call_chain+0x1f/0x30 Aug 14 16:20:50 localhost kernel: [ 22.343387] ? register_framebuffer +0x1f6/0x340 Aug 14 16:20:50 localhost kernel: [ 22.343406] ? drm_fb_helper_initial_config+0x23a/0x3f0 [drm_kms_helper] Aug 14 16:20:50 localhost kernel: [ 22.343541] ? intel_fbdev_initial_config +0x16/0x30 [i915] Aug 14 16:20:50 localhost kernel: [ 22.343551] ? async_run_entry_fn +0x35/0x190 Aug 14 16:20:50 localhost kernel: [ 22.343558] ? __schedule+0x2d7/0x8e0 Aug 14 16:20:50 localhost kernel: [ 22.343564] ? process_one_work +0x150/0x380 Aug 14 16:20:50 localhost kernel: [ 22.343570] ? process_one_work +0x150/0x380 Aug 14 16:20:50 localhost kernel: [ 22.343576] ? worker_thread+0x41/0x480 Aug 14 16:20:50 localhost kernel: [ 22.343582] ? kthread+0xdb/0x110 Aug 14 16:20:50 localhost kernel: [ 22.343587] ? process_one_work +0x380/0x380 Aug 14 16:20:50 localhost kernel: [ 22.343592] ? kthread_create_on_node +0x30/0x30 Aug 14 16:20:50 localhost kernel: [ 22.343596] ? ret_from_fork+0x1c/0x28 Aug 14 16:20:50 localhost kernel: [ 22.343603] ---[ end trace e3014e12a8add248 ]--- ---------- snap ------------------ You may right, it looks like the framebuffer module is involved. However, as I told before, it is not harmful and everything is working fine, also graphics looks good. Hope it helps either. Best Hans
