Ubuntu
linux-meta package

i915 driver in kernel 6.2.0-39

Asked by Eric Fafet

Hi

I just updated my kernel to the 6.2.0-39 version and the i915 [drm] raised an *ERROR* Failed to setup region(-19) type=3
The previous version 6.2.0-37 is running fine (22.04.3 LTS Jammy Jellyfish)

I would like to know what could have been changed in the kernel that could make the i915 driver behaving differently.

For information, I ran into the same issue with the 6.5 kernel (23.10 release). The initialization fail the same way during a cold boot and freeze the kernel while both kernel 6.2.0-39 or 6.5 run apparently ok if it is a hot reboot, except that the nvme devices are renamed : nmve0 become nvme1 and vice et versa, randomly.

I know that a new DRM driver is due mid 2024 from intel to replace the i915 driver, but any information on what could be the root cause of such a strange behavior is more than welcome.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu linux-meta Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Is the error:

Failed to setup region(-19) type=3

?

Is that the exact error, please?

Revision history for this message
Eric Fafet (ericoder-f) said : 		#2

Please find below the trace in the boot log (journalctl -b):
boot_log_trace_i915_Linux_version_620-39-generic_buildd@lcy02-amd64-045

déc. 16 13:06:55 eric-NUC12 kernel: ------------[ cut here ]------------
déc. 16 13:06:55 eric-NUC12 kernel: WARNING: CPU: 4 PID: 259 at
drivers/gpu/drm/i915/gem/i915_gem_stolen.c:914
i915_gem_stolen_lmem_setup+0x2cc/0x310 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: Modules linked in: hid_logitech_dj(+)
hid_generic usbhid hid i915(+) drm_buddy i2c_algo_bit ttm
drm_display_helper cec rc_core drm_kms_helper sy>
déc. 16 13:06:55 eric-NUC12 kernel: CPU: 4 PID: 259 Comm: systemd-udevd
Tainted: G W 6.2.0-39-generic #40~22.04.1-Ubuntu
déc. 16 13:06:55 eric-NUC12 kernel: Hardware name: Intel(R) Client Systems
NUC12SNKi72/NUC12SNKi72, BIOS SNADL357.0058.2023.0711.1531 07/11/2023
déc. 16 13:06:55 eric-NUC12 kernel: RIP:
0010:i915_gem_stolen_lmem_setup+0x2cc/0x310 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: Code: ff ff ff e9 bb fe ff ff 41 c1 e5
05 e9 5e ff ff ff 4d 63 ed 49 8b 7c 24 08 48 c7 c6 50 21 d9 c0 e8 99 9f ed
dc e9 99 fe ff ff <0f> 0b 49 c>
déc. 16 13:06:55 eric-NUC12 kernel: RSP: 0018:ffffa9a8c0f7f8c0 EFLAGS:
00010207
déc. 16 13:06:55 eric-NUC12 kernel: RAX: fffffffffff00000 RBX:
0000000000000003 RCX: 0000000000000000
déc. 16 13:06:55 eric-NUC12 kernel: RDX: 0000003fc0100000 RSI:
fffffffffff00000 RDI: 0000000000000000
déc. 16 13:06:55 eric-NUC12 kernel: RBP: ffffa9a8c0f7f8e8 R08:
0000000000000000 R09: 0000000000000000
déc. 16 13:06:55 eric-NUC12 kernel: R10: 0000000000000000 R11:
0000000000000000 R12: ffff8953a5768000
déc. 16 13:06:55 eric-NUC12 kernel: R13: ffff8953a5769ca8 R14:
0000003fc0000000 R15: ffff89538320f0d0
déc. 16 13:06:55 eric-NUC12 kernel: FS: 00007f71226838c0(0000)
GS:ffff8962f0300000(0000) knlGS:0000000000000000
déc. 16 13:06:55 eric-NUC12 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
déc. 16 13:06:55 eric-NUC12 kernel: CR2: 0000564dec9cb648 CR3:
00000001014c4000 CR4: 0000000000750ee0
déc. 16 13:06:55 eric-NUC12 kernel: PKRU: 55555554
déc. 16 13:06:55 eric-NUC12 kernel: Call Trace:
déc. 16 13:06:55 eric-NUC12 kernel: <TASK>
déc. 16 13:06:55 eric-NUC12 kernel: ? show_regs+0x72/0x90
déc. 16 13:06:55 eric-NUC12 kernel: ?
i915_gem_stolen_lmem_setup+0x2cc/0x310 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: ? __warn+0x8d/0x160
déc. 16 13:06:55 eric-NUC12 kernel: ?
i915_gem_stolen_lmem_setup+0x2cc/0x310 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: ? report_bug+0x1bb/0x1d0
déc. 16 13:06:55 eric-NUC12 kernel: ? handle_bug+0x46/0x90
déc. 16 13:06:55 eric-NUC12 kernel: ? exc_invalid_op+0x19/0x80
déc. 16 13:06:55 eric-NUC12 kernel: ? asm_exc_invalid_op+0x1b/0x20
déc. 16 13:06:55 eric-NUC12 kernel: ?
i915_gem_stolen_lmem_setup+0x2cc/0x310 [i915]
déc. 16 13:06:55 eric-NUC12 kernel:
 intel_memory_regions_hw_probe+0x90/0x200 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: i915_driver_hw_probe+0x264/0x340 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: i915_driver_probe+0xfa/0x450 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: ? acpi_dev_found+0x66/0x80
déc. 16 13:06:55 eric-NUC12 kernel: i915_pci_probe+0x111/0x1f0 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: local_pci_probe+0x48/0xb0
déc. 16 13:06:55 eric-NUC12 kernel: pci_call_probe+0x55/0x190
déc. 16 13:06:55 eric-NUC12 kernel: pci_device_probe+0x84/0x120
déc. 16 13:06:55 eric-NUC12 kernel: really_probe+0x1ea/0x450
déc. 16 13:06:55 eric-NUC12 kernel: __driver_probe_device+0x8a/0x190
déc. 16 13:06:55 eric-NUC12 kernel: driver_probe_device+0x23/0xd0
déc. 16 13:06:55 eric-NUC12 kernel: __driver_attach+0x10f/0x220
déc. 16 13:06:55 eric-NUC12 kernel: ? __pfx___driver_attach+0x10/0x10
déc. 16 13:06:55 eric-NUC12 kernel: bus_for_each_dev+0x80/0xe0
déc. 16 13:06:55 eric-NUC12 kernel: driver_attach+0x1e/0x30
déc. 16 13:06:55 eric-NUC12 kernel: bus_add_driver+0x152/0x250
déc. 16 13:06:55 eric-NUC12 kernel: driver_register+0x83/0x160
déc. 16 13:06:55 eric-NUC12 kernel: __pci_register_driver+0x68/0x80
déc. 16 13:06:55 eric-NUC12 kernel: i915_pci_register_driver+0x23/0x30
[i915]
déc. 16 13:06:55 eric-NUC12 kernel: i915_init+0x34/0x120 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: ? __pfx_init_module+0x10/0x10 [i915]
déc. 16 13:06:55 eric-NUC12 kernel: do_one_initcall+0x46/0x240
déc. 16 13:06:55 eric-NUC12 kernel: ? kmalloc_trace+0x2a/0xb0
déc. 16 13:06:55 eric-NUC12 kernel: do_init_module+0x52/0x240
déc. 16 13:06:55 eric-NUC12 kernel: load_module+0xb96/0xd60
déc. 16 13:06:55 eric-NUC12 kernel: ?
security_kernel_post_read_file+0x5c/0x80
déc. 16 13:06:55 eric-NUC12 kernel: __do_sys_finit_module+0xcc/0x150
déc. 16 13:06:55 eric-NUC12 kernel: ? __do_sys_finit_module+0xcc/0x150
déc. 16 13:06:55 eric-NUC12 kernel: __x64_sys_finit_module+0x18/0x30
déc. 16 13:06:55 eric-NUC12 kernel: do_syscall_64+0x59/0x90
déc. 16 13:06:55 eric-NUC12 kernel: ? exit_to_user_mode_prepare+0x3b/0xd0
déc. 16 13:06:55 eric-NUC12 kernel: ? syscall_exit_to_user_mode+0x38/0x60
déc. 16 13:06:55 eric-NUC12 kernel: ? do_syscall_64+0x69/0x90
déc. 16 13:06:55 eric-NUC12 kernel: ? do_syscall_64+0x69/0x90
déc. 16 13:06:55 eric-NUC12 kernel: ? do_syscall_64+0x69/0x90
déc. 16 13:06:55 eric-NUC12 kernel:
 entry_SYSCALL_64_after_hwframe+0x73/0xdd
déc. 16 13:06:55 eric-NUC12 kernel: RIP: 0033:0x7f7122d7c69d
déc. 16 13:06:55 eric-NUC12 kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00
00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c
8b 4c 24 08 0f 05 <48> 3d 01 f>
déc. 16 13:06:55 eric-NUC12 kernel: RSP: 002b:00007ffe86481af8 EFLAGS:
00000246 ORIG_RAX: 0000000000000139
déc. 16 13:06:55 eric-NUC12 kernel: RAX: ffffffffffffffda RBX:
0000564dec9bedb0 RCX: 00007f7122d7c69d
déc. 16 13:06:55 eric-NUC12 kernel: RDX: 0000000000000000 RSI:
00007f7122f13441 RDI: 0000000000000015
déc. 16 13:06:55 eric-NUC12 kernel: RBP: 0000000000020000 R08:
0000000000000000 R09: 0000000000000002
déc. 16 13:06:55 eric-NUC12 kernel: R10: 0000000000000015 R11:
0000000000000246 R12: 00007f7122f13441
déc. 16 13:06:55 eric-NUC12 kernel: R13: 0000564dec950d70 R14:
0000564dec9b0d30 R15: 0000564dec9b57a0
déc. 16 13:06:55 eric-NUC12 kernel: </TASK>
déc. 16 13:06:55 eric-NUC12 kernel: ---[ end trace 0000000000000000 ]---
déc. 16 13:06:55 eric-NUC12 kernel: i915 0000:03:00.0: [drm] *ERROR* Failed
to setup region(-19) type=3
déc. 16 13:06:55 eric-NUC12 kernel: i915 0000:03:00.0: Device
initialization failed (-19)
déc. 16 13:06:55 eric-NUC12 kernel: i915 0000:03:00.0: Please file a bug on
drm/i915; see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for
details.

Le mar. 19 déc. 2023 à 10:36, actionparsnip <
<email address hidden>> a écrit :

> Your question #708734 on linux-meta in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/linux-meta/+question/708734
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Is the error:
>
> Failed to setup region(-19) type=3
>
> ?
>
> Is that the exact error, please?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/linux-meta/+question/708734
>
> You received this question notification because you asked the question.
>

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Did you use the link and log the bug?

Can you help with this problem?

Provide an answer of your own, or ask Eric Fafet for more information if necessary.

To post a message you must log in.