The officially official Devuan Forum!

You are not logged in.

#1 2019-05-19 02:57:41

Altoid
Member
Registered: 2017-05-07
Posts: 245  

dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages

Hello: 

Never ending surprises ...

Came across this new set of entries in my dmsg log.
It's new, had not seen it when I had just installed ASCII in my 1000HE.

The [ cut here ] sort of tells me it is something abnormal and meant to be sent somewhere.

[    9.424614] ------------[ cut here ]------------
[    9.424781] WARNING: CPU: 0 PID: 6 at /build/linux-6uB1fl/linux-4.9.168/drivers/gpu/drm/i915/intel_fbdev.c:414 intel_fb_initial_config+0x3fc/0x5f0 [i915]
[    9.424821] WARN_ON(!connector->state->crtc)
[    9.424831] Modules linked in:
[    9.424850]  i915 crc_ccitt coretemp rfkill psmouse pcspkr uhci_hcd ehci_pci ata_generic drm_kms_helper ehci_hcd snd_hda_codec_realtek snd_hda_codec_generic lpc_ich mfd_core atl1e ata_piix sg drm rng_core wmi usbcore snd_hda_intel usb_common battery i2c_algo_bit snd_hda_codec shpchp snd_hda_core video button ac snd_hwdep snd_pcm snd_timer snd soundcore acpi_cpufreq ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache sd_mod ahci libahci libata evdev serio_raw scsi_mod thermal
[    9.425099] CPU: 0 PID: 6 Comm: kworker/u4:0 Not tainted 4.9.0-9-686-pae #1 Debian 4.9.168-1+deb9u2
[    9.425131] Hardware name: ASUSTeK Computer INC. 1000HE/1000HE, BIOS 1104    10/14/2009
[    9.425170] Workqueue: events_unbound async_run_entry_fn
[    9.425193]  f5d19d40 c42ff602 f5d19d54 00000000 c406a30a f9029dc6 f5d19d74 00000006
[    9.425240]  f901d370 0000019e f8fcbf0c 0000019e 00000009 f8fcbf0c 00000001 f5e5f800
[    9.425285]  00000000 f5d19d60 c406a376 00000009 00000000 f5d19d54 f9029dc6 f5d19d74
[    9.425331] Call Trace:
[    9.425359]  [<c42ff602>] ? dump_stack+0x55/0x73
[    9.425384]  [<c406a30a>] ? __warn+0xea/0x110
[    9.425531]  [<f8fcbf0c>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[    9.425671]  [<f8fcbf0c>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[    9.425697]  [<c406a376>] ? warn_slowpath_fmt+0x46/0x60
[    9.425835]  [<f8fcbf0c>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[    9.425869]  [<c41c5dbf>] ? __kmalloc+0xef/0x500
[    9.425987]  [<f8fcbb10>] ? intelfb_create+0x4d0/0x4d0 [i915]
[    9.426012]  [<f8951946>] ? drm_setup_crtcs+0x1a6/0x950 [drm_kms_helper]
[    9.426032]  [<c40936f5>] ? try_to_wake_up+0x45/0x370
[    9.426049]  [<c4093a6e>] ? wake_up_q+0x2e/0x60
[    9.426071]  [<f89523e1>] ? drm_fb_helper_initial_config+0xc1/0x410 [drm_kms_helper]
[    9.426098]  [<c40a7420>] ? pick_next_task_fair+0x490/0x520
[    9.426202]  [<f8fcc6e0>] ? intel_fbdev_fini+0xd0/0xd0 [i915]
[    9.426307]  [<f8fcc6f6>] ? intel_fbdev_initial_config+0x16/0x30 [i915]
[    9.426325]  [<c408b20a>] ? async_run_entry_fn+0x3a/0x180
[    9.426342]  [<c4092900>] ? deactivate_task+0x20/0xf0
[    9.426360]  [<c45bd6f8>] ? __schedule+0x268/0x770
[    9.426377]  [<c4082df6>] ? process_one_work+0x146/0x390
[    9.426395]  [<c4083079>] ? worker_thread+0x39/0x480
[    9.426411]  [<c4088397>] ? kthread+0xb7/0xd0
[    9.426427]  [<c4083040>] ? process_one_work+0x390/0x390
[    9.426444]  [<c40882e0>] ? kthread_park+0x50/0x50
[    9.426461]  [<c45c1f67>] ? ret_from_fork+0x1b/0x3c
[    9.426478] ---[ end trace 280b97008804440b ]---
[    9.430341] fbcon: inteldrmfb (fb0) is primary device
[    9.431973] ------------[ cut here ]------------
[    9.431994] WARNING: CPU: 1 PID: 6 at /build/linux-6uB1fl/linux-4.9.168/drivers/gpu/drm/drm_atomic_helper.c:783 drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[    9.432106] Modules linked in: i915 crc_ccitt coretemp rfkill psmouse pcspkr uhci_hcd ehci_pci ata_generic drm_kms_helper ehci_hcd snd_hda_codec_realtek snd_hda_codec_generic lpc_ich mfd_core atl1e ata_piix sg drm rng_core wmi usbcore snd_hda_intel usb_common battery i2c_algo_bit snd_hda_codec shpchp snd_hda_core video button ac snd_hwdep snd_pcm snd_timer snd soundcore acpi_cpufreq ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache sd_mod ahci libahci libata evdev serio_raw scsi_mod thermal
[    9.432114] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G        W       4.9.0-9-686-pae #1 Debian 4.9.168-1+deb9u2
[    9.432116] Hardware name: ASUSTeK Computer INC. 1000HE/1000HE, BIOS 1104    10/14/2009
[    9.432125] Workqueue: events_unbound async_run_entry_fn
[    9.432135]  f5d19b00 c42ff602 00000000 00000000 c406a30a c46bb29c 00000001 00000006
[    9.432143]  f8954bb0 0000030f f894ac3a 0000030f 00000009 f894ac3a f5e5f800 00000000
[    9.432150]  f5689800 f5d19b14 c406a41a 00000009 00000000 00000000 f5d19b3c f894ac3a
[    9.432152] Call Trace:
[    9.432161]  [<c42ff602>] ? dump_stack+0x55/0x73
[    9.432167]  [<c406a30a>] ? __warn+0xea/0x110
[    9.432179]  [<f894ac3a>] ? drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[    9.432189]  [<f894ac3a>] ? drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[    9.432194]  [<c406a41a>] ? warn_slowpath_null+0x2a/0x30
[    9.432204]  [<f894ac3a>] ? drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[    9.432305]  [<f8fae7b5>] ? intel_pre_plane_update+0x55/0x140 [i915]
[    9.432398]  [<f8faf6f4>] ? intel_atomic_commit_tail+0x9a4/0xf60 [i915]
[    9.432490]  [<f8fb751c>] ? intel_prepare_plane_fb+0xdc/0x2a0 [i915]
[    9.432501]  [<f894b45c>] ? drm_atomic_helper_swap_state+0x1cc/0x2d0 [drm_kms_helper]
[    9.432593]  [<f8faffe5>] ? intel_atomic_commit+0x335/0x4c0 [i915]
[    9.432614]  [<f88223a4>] ? drm_atomic_check_only+0x324/0x6a0 [drm]
[    9.432633]  [<f8821dd1>] ? drm_atomic_set_crtc_for_connector+0xb1/0x100 [drm]
[    9.432725]  [<f8fafcb0>] ? intel_atomic_commit_tail+0xf60/0xf60 [i915]
[    9.432744]  [<f882276e>] ? drm_atomic_commit+0x4e/0x60 [drm]
[    9.432755]  [<f8950753>] ? restore_fbdev_mode+0x153/0x2a0 [drm_kms_helper]
[    9.432774]  [<f8821504>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm]
[    9.432784]  [<f8952267>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper]
[    9.432793]  [<f89522dd>] ? drm_fb_helper_set_par+0x2d/0x70 [drm_kms_helper]
[    9.432884]  [<f8fcb5e5>] ? intel_fbdev_set_par+0x15/0x70 [i915]
[    9.432891]  [<c4378730>] ? fbcon_init+0x540/0x590
[    9.432897]  [<c4400240>] ? visual_init+0xc0/0x120
[    9.432901]  [<c4401369>] ? do_bind_con_driver+0x179/0x370
[    9.432906]  [<c4401863>] ? do_take_over_console+0x123/0x1a0
[    9.432911]  [<c4378af0>] ? set_con2fb_map+0x370/0x370
[    9.432916]  [<c43746df>] ? do_fbcon_takeover+0x5f/0xc0
[    9.432921]  [<c4089851>] ? notifier_call_chain+0x51/0x70
[    9.432926]  [<c4089b79>] ? __blocking_notifier_call_chain+0x39/0x60
[    9.432931]  [<c4089bbf>] ? blocking_notifier_call_chain+0x1f/0x30
[    9.432935]  [<c43802c6>] ? register_framebuffer+0x1f6/0x340
[    9.432947]  [<f8952594>] ? drm_fb_helper_initial_config+0x274/0x410 [drm_kms_helper]
[    9.433039]  [<f8fcc6e0>] ? intel_fbdev_fini+0xd0/0xd0 [i915]
[    9.433130]  [<f8fcc6f6>] ? intel_fbdev_initial_config+0x16/0x30 [i915]
[    9.433135]  [<c408b20a>] ? async_run_entry_fn+0x3a/0x180
[    9.433139]  [<c4092900>] ? deactivate_task+0x20/0xf0
[    9.433145]  [<c45bd6f8>] ? __schedule+0x268/0x770
[    9.433150]  [<c4082df6>] ? process_one_work+0x146/0x390
[    9.433155]  [<c4083079>] ? worker_thread+0x39/0x480
[    9.433159]  [<c4088397>] ? kthread+0xb7/0xd0
[    9.433164]  [<c4083040>] ? process_one_work+0x390/0x390
[    9.433168]  [<c40882e0>] ? kthread_park+0x50/0x50
[    9.433173]  [<c45c1f67>] ? ret_from_fork+0x1b/0x3c
[    9.433177] ---[ end trace 280b97008804440c ]---

I've never seen this in four+ years of Linux distributions.

Can anyone shed a light on this and it's cause?

Thanks in advance.

A.

Offline

#2 2019-05-19 14:24:40

Dutch_Master
Member
Registered: 2018-05-31
Posts: 101  

Re: dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages

It's related to building the kernel module for the i915 GPU driver and it's a trace (as you've already noticed) for the developer(s) which shouldn't really be there. Do you have any related .dev package installed on your system? It may have 'escaped' from there. Report it as a bug to whomever is/are the dev's for the Intel i915 driver.

Offline

#3 2019-05-19 15:24:03

Altoid
Member
Registered: 2017-05-07
Posts: 245  

Re: dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages

Hello:

Dutch_Master wrote:

... related to building the kernel module for the i915 GPU driver
... it's a trace ...
... shouldn't really be there.

OK.
So it's just debugging information for the developer/maintainer?

Dutch_Master wrote:

... have any related .dev package installed ...

Related, none that I can see.

groucho@devuan:~$ dpkg -l | grep -i i9xx
ii  xserver-xorg-video-intel   2:2.99.917+git20161206-1   i386  X.Org X server -- Intel i8xx, i9xx display driver
groucho@devuan:~$ 

I've also had a thorough look in synaptic installed and no, none.

Dutch_Master wrote:

... may have 'escaped' from there.
Report it as a bug to whomever is/are the dev's for the Intel i915 ...

Would it still be a bug without there being an installed -dev package?

EDIT:

A search on the web for the last part of the initial string ie:

c:414 intel_fb_initial_config+0x3fc/0x5f0 [i915]

... got me this from 20 Feb 2017:

https://lists.debian.org/debian-kernel/ … 00265.html

Package: src:linux
Version: 4.9.6-3
Severity: important

The DRM driver for i915 hardware oopses in a systematic way during bootup on this Dell D430 using kernel 4.9 from testing/frozen.

Booting with kernel 3.16 from stable/updates doesn't produce these symptoms.

-- Package-specific info:
** Version:
Linux version 4.9.0-1-686-pae (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)

Should I file something more?
It's been more than two years and it's still there.
Severity: important?
 
Thank you for your input.

A.

Last edited by Altoid (2019-05-19 15:50:31)

Offline

#4 2019-05-19 16:19:13

Dutch_Master
Member
Registered: 2018-05-31
Posts: 101  

Re: dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages

Yes, it's still a bug if no .dev package is installed. Worse even, as there's no logical path for this info to be generated, in such case I'd rate the issue very serious indeed.

It's indeed worth putting in a bug report for this, even after 2 years, as it clearly isn't completely rooted out yet. Make sure you provide as much relevant info to the circumstances of the occurrence of the bug so the dev's can replicate it accurately.

Offline

#5 2019-05-19 17:13:05

Altoid
Member
Registered: 2017-05-07
Posts: 245  

Re: dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages

Hello:

Dutch_Master wrote:

... still a bug if no .dev package is installed.
... no logical path for this info to be generated ...
... rate the issue very serious indeed.

But the maintainers have to think so too ...    =-D

Dutch_Master wrote:

... worth putting in a bug report for this, even after 2 years ...

Done.

Dutch_Master wrote:

... clearly isn't completely rooted out ...

I have not seen any indication of its being assigned.

Dutch_Master wrote:

... provide as much relevant info to the circumstances ...

Yes ...
kern.log snippet, lshw, lspci, lsusb, lsmod and kernel-image information.

Being a bug with a number, I sent mail to the <bug_number>@bugs.debian.org address.
Hope it is enough and that I've done it properly.

Thanks for your input.

A.

Offline

#6 2019-10-06 14:31:26

Altoid
Member
Registered: 2017-05-07
Posts: 245  

Re: dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages

Hello:

Altoid wrote:

Hello:
I have not seen any indication of its being assigned.

I'm running the last available Devuan 4.9.0.11-686-pae SMP Debian 4.9.189-3+deb9u1 (2089-09-20) i686 and the problem subsists.

Will this ever get fixed or will it end up as part of the 'won't fix' crud that ends up accumulating inside the code because it is not considered worth correcting?


A.

Offline

Board footer