Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
22237 Discussions

A770 16 Gig, AMD cpu, realtime kernel 6.11 and 6.8, Ubuntu 24.04 Hangs on boot

MSab
Beginner
659 Views

Realtime kernel hangs on boot, but works with i915.modeset=0.

Has anyone had a similar issue? Is it somehow solvable so I can use SYCL or Vulkan for compute?

 

Thanks,

Mani

 

0 Kudos
11 Replies
Mike_Intel
Moderator
591 Views

Hello MSab,


Thank you for posting in Intel community Forum.


For me to further check this, please help provide the following details:


  1. Are you using an Intel brand Arc A770?
  2. Was it working fine before or this is the first time that you installed Ubuntu?
  3. Can you tell me which part of the boot up process does the system hangs?
  4. Did you already install a driver then the system hangs, or this is after the OS installation?
  5. What are the troubleshooting steps that you tried so far?


If you have questions, please let us know. Thank you.


Best regards,

Michael L.

Intel Customer Support Technician


0 Kudos
MSab
Beginner
567 Views

Hi,

The graphic card is ASRock brand. Regular kernel works fine. Just the realtime kernel crashes. Full kernel output is attached in the first message, but I think the relevant parts might be in the middle of these ones

 

Thank you,

Mani

 

Apr 26 13:07:55 system5 systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Apr 26 13:07:55 system5 systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Apr 26 13:07:55 system5 systemd[1]: systemd-update-done.service - Update is Completed was skipped because no trigger condition checks were met.
Apr 26 13:07:55 system5 systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
Apr 26 13:07:55 system5 systemd[1]: Started rpcbind.service - RPC bind portmap service.
Apr 26 13:07:55 system5 systemd[1]: Reached target rpcbind.target - RPC Port Mapper.
Apr 26 13:07:56 system5 systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
Apr 26 13:07:56 system5 kernel: snd_hda_intel 0000:0c:00.0: bound 0000:0b:00.0 (ops i915_audio_component_bind_ops [i915])
Apr 26 13:07:56 system5 kernel: snd_hda_intel 0000:0c:00.0: Unknown capability 0
Apr 26 13:07:56 system5 kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:09:00.0/0000:0a:04.0/0000:0c:00.0/sound/card1/input46
Apr 26 13:07:56 system5 kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:09:00.0/0000:0a:04.0/0000:0c:00.0/sound/card1/input47
Apr 26 13:07:56 system5 kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:09:00.0/0000:0a:04.0/0000:0c:00.0/sound/card1/input48
Apr 26 13:07:56 system5 kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:09:00.0/0000:0a:04.0/0000:0c:00.0/sound/card1/input49
Apr 26 13:07:56 system5 kernel: ------------[ cut here ]------------
Apr 26 13:07:56 system5 kernel: irq 120 handler mei_me_irq_quick_handler+0x0/0x130 [mei_me] enabled interrupts
Apr 26 13:07:56 system5 kernel: WARNING: CPU: 7 PID: 1477 at kernel/irq/handle.c:161 __handle_irq_event_percpu+0x1a8/0x1b0
Apr 26 13:07:56 system5 kernel: Modules linked in: mei_gsc(+) mei_me mei snd_hda_codec_hdmi xe drm_gpuvm drm_exec gpu_sched drm_suballoc_helper drm_ttm_helper nls_iso8859_1 gspca_ov534(+) gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_codec_realtek videodev snd_hda_codec_generic videobuf2_common ee1004 intel_rapl_msr snd_hda_scodec_component mc snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi amd_atl intel_rapl_common snd_hda_codec snd_hda_core i915 snd_hwdep asus_ec_sensors snd_pcm edac_mce_amd snd_seq_midi snd_seq_midi_event crct10dif_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel snd_rawmidi sha256_ssse3 sha1_ssse3 mfd_aaeon eeepc_wmi aesni_intel drm_buddy asus_wmi ttm crypto_simd sparse_keymap cryptd snd_seq platform_profile rapl drm_display_helper snd_seq_device wmi_bmof mxm_wmi btusb snd_timer cec btrtl btintel btbcm rc_core snd btmtk video k10temp i2c_piix4 soundcore ccp cdc_acm i2c_smbus bluetooth joydev input_leds hid_waltop mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore
Apr 26 13:07:56 system5 kernel: nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log hid_logitech_hidpp hid_logitech_dj hid_logitech ff_memless hid_generic usbhid hid igb ahci crc32_pclmul i2c_algo_bit dca libahci nvme xhci_pci xhci_pci_renesas nvme_core nvme_auth wmi
Apr 26 13:07:56 system5 kernel: CPU: 7 UID: 0 PID: 1477 Comm: irq/119-i915 Not tainted 6.11.0-1008-realtime #8~24.04.1-Ubuntu
Apr 26 13:07:56 system5 kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 5003 10/07/2023
Apr 26 13:07:56 system5 kernel: RIP: 0010:__handle_irq_event_percpu+0x1a8/0x1b0
Apr 26 13:07:56 system5 kernel: Code: 5e 3b ff ff e9 a8 fe ff ff 45 31 ed e9 fc fe ff ff 48 8b 13 44 89 f6 48 c7 c7 f0 31 c4 a3 c6 05 3f a1 65 02 01 e8 18 58 f4 ff <0f> 0b eb ab 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90
Apr 26 13:07:56 system5 kernel: RSP: 0018:ffffb1ec01847c70 EFLAGS: 00010246
Apr 26 13:07:56 system5 kernel: RAX: 0000000000000000 RBX: ffff966ec1b90d80 RCX: 0000000000000000
Apr 26 13:07:56 system5 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Apr 26 13:07:56 system5 kernel: RBP: ffffb1ec01847ca0 R08: 0000000000000000 R09: 0000000000000000
Apr 26 13:07:56 system5 kernel: R10: 0000000000000000 R11: 0a73747075727265 R12: 0000000000000002
Apr 26 13:07:56 system5 kernel: R13: 0000000000000000 R14: 0000000000000078 R15: ffff966ec91e4200
Apr 26 13:07:56 system5 kernel: FS: 0000000000000000(0000) GS:ffff96858ed80000(0000) knlGS:0000000000000000
Apr 26 13:07:56 system5 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 26 13:07:56 system5 kernel: CR2: 000060ac3a9cbef3 CR3: 0000000107fc6000 CR4: 0000000000350ef0
Apr 26 13:07:56 system5 kernel: Call Trace:
Apr 26 13:07:56 system5 kernel: <TASK>
Apr 26 13:07:56 system5 kernel: ? show_regs+0x6c/0x80
Apr 26 13:07:56 system5 kernel: ? __warn+0x8d/0x150
Apr 26 13:07:56 system5 kernel: ? __handle_irq_event_percpu+0x1a8/0x1b0
Apr 26 13:07:56 system5 kernel: ? report_bug+0x182/0x1b0
Apr 26 13:07:56 system5 kernel: ? handle_bug+0x6e/0xb0
Apr 26 13:07:56 system5 kernel: ? exc_invalid_op+0x18/0x80
Apr 26 13:07:56 system5 kernel: ? asm_exc_invalid_op+0x1b/0x20
Apr 26 13:07:56 system5 kernel: ? __handle_irq_event_percpu+0x1a8/0x1b0
Apr 26 13:07:56 system5 kernel: ? mtree_load+0x275/0x2d0
Apr 26 13:07:56 system5 kernel: handle_irq_event+0x39/0x80
Apr 26 13:07:56 system5 kernel: handle_simple_irq+0x65/0xc0
Apr 26 13:07:56 system5 kernel: handle_irq_desc+0x3f/0x60
Apr 26 13:07:56 system5 kernel: generic_handle_irq+0x1f/0x30
Apr 26 13:07:56 system5 kernel: gsc_irq_handler+0x54/0x120 [i915]
Apr 26 13:07:56 system5 kernel: intel_gsc_irq_handler+0x2f/0x50 [i915]
Apr 26 13:07:56 system5 kernel: gen11_gt_bank_handler+0x401/0x4a0 [i915]
Apr 26 13:07:56 system5 kernel: ? srso_return_thunk+0x5/0x5f
Apr 26 13:07:56 system5 kernel: ? finish_task_switch.isra.0+0x9c/0x320
Apr 26 13:07:56 system5 kernel: gen11_gt_irq_handler+0x4d/0x70 [i915]
Apr 26 13:07:56 system5 kernel: dg1_irq_handler+0xa6/0x110 [i915]
Apr 26 13:07:56 system5 kernel: irq_forced_thread_fn+0x35/0x90
Apr 26 13:07:56 system5 kernel: irq_thread+0x1b9/0x2e0
Apr 26 13:07:56 system5 kernel: ? __pfx_irq_forced_thread_fn+0x10/0x10
Apr 26 13:07:56 system5 kernel: ? __pfx_irq_thread_dtor+0x10/0x10
Apr 26 13:07:56 system5 kernel: ? __pfx_irq_thread+0x10/0x10
Apr 26 13:07:56 system5 kernel: kthread+0xe4/0x110
Apr 26 13:07:56 system5 kernel: ? __pfx_kthread+0x10/0x10
Apr 26 13:07:56 system5 kernel: ret_from_fork+0x47/0x70
Apr 26 13:07:56 system5 kernel: ? __pfx_kthread+0x10/0x10
Apr 26 13:07:56 system5 kernel: ret_from_fork_asm+0x1a/0x30
Apr 26 13:07:56 system5 kernel: </TASK>
Apr 26 13:07:56 system5 kernel: ---[ end trace 0000000000000000 ]---
Apr 26 13:07:56 system5 kernel: ------------[ cut here ]------------
Apr 26 13:07:56 system5 kernel: Voluntary context switch within RCU read-side critical section!
Apr 26 13:07:56 system5 kernel: WARNING: CPU: 7 PID: 1477 at kernel/rcu/tree_plugin.h:330 rcu_note_context_switch+0x29f/0x2c0
Apr 26 13:07:56 system5 kernel: Modules linked in: mei_gsc(+) mei_me mei snd_hda_codec_hdmi xe drm_gpuvm drm_exec gpu_sched drm_suballoc_helper drm_ttm_helper nls_iso8859_1 gspca_ov534(+) gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_codec_realtek videodev snd_hda_codec_generic videobuf2_common ee1004 intel_rapl_msr snd_hda_scodec_component mc snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi amd_atl intel_rapl_common snd_hda_codec snd_hda_core i915 snd_hwdep asus_ec_sensors snd_pcm edac_mce_amd snd_seq_midi snd_seq_midi_event crct10dif_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel snd_rawmidi sha256_ssse3 sha1_ssse3 mfd_aaeon eeepc_wmi aesni_intel drm_buddy asus_wmi ttm crypto_simd sparse_keymap cryptd snd_seq platform_profile rapl drm_display_helper snd_seq_device wmi_bmof mxm_wmi btusb snd_timer cec btrtl btintel btbcm rc_core snd btmtk video k10temp i2c_piix4 soundcore ccp cdc_acm i2c_smbus bluetooth joydev input_leds hid_waltop mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore
Apr 26 13:07:56 system5 kernel: nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_mirror dm_region_hash dm_log hid_logitech_hidpp hid_logitech_dj hid_logitech ff_memless hid_generic usbhid hid igb ahci crc32_pclmul i2c_algo_bit dca libahci nvme xhci_pci xhci_pci_renesas nvme_core nvme_auth wmi
Apr 26 13:07:56 system5 kernel: CPU: 7 UID: 0 PID: 1477 Comm: irq/119-i915 Tainted: G W 6.11.0-1008-realtime #8~24.04.1-Ubuntu
Apr 26 13:07:56 system5 kernel: Tainted: [W]=WARN
Apr 26 13:07:56 system5 kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 5003 10/07/2023
Apr 26 13:07:56 system5 kernel: RIP: 0010:rcu_note_context_switch+0x29f/0x2c0
Apr 26 13:07:56 system5 kernel: Code: ba 02 00 00 00 be 01 00 00 00 48 89 df e8 29 c7 fe ff e9 62 fe ff ff 48 c7 c7 60 5d c4 a3 c6 05 14 2b 63 02 01 e8 e1 e1 f1 ff <0f> 0b e9 bb fd ff ff 0f 0b e9 31 ff ff ff 0f 0b e9 13 ff ff ff 66
Apr 26 13:07:56 system5 kernel: RSP: 0018:ffffb1ec01847d80 EFLAGS: 00010046
Apr 26 13:07:56 system5 kernel: RAX: 0000000000000000 RBX: ffff966ed2a4d100 RCX: 0000000000000000
Apr 26 13:07:56 system5 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Apr 26 13:07:56 system5 kernel: RBP: ffffb1ec01847da0 R08: 0000000000000000 R09: 0000000000000000
Apr 26 13:07:56 system5 kernel: R10: 0000000000000000 R11: 6e69687469772068 R12: ffff96858edb7ec0
Apr 26 13:07:56 system5 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000001
Apr 26 13:07:56 system5 kernel: FS: 0000000000000000(0000) GS:ffff96858ed80000(0000) knlGS:0000000000000000
Apr 26 13:07:56 system5 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 26 13:07:56 system5 kernel: CR2: 000060ac3a9cbef3 CR3: 0000000107fc6000 CR4: 0000000000350ef0
Apr 26 13:07:56 system5 kernel: Call Trace:
Apr 26 13:07:56 system5 kernel: <TASK>
Apr 26 13:07:56 system5 kernel: ? show_regs+0x6c/0x80
Apr 26 13:07:56 system5 kernel: ? __warn+0x8d/0x150
Apr 26 13:07:56 system5 kernel: ? rcu_note_context_switch+0x29f/0x2c0
Apr 26 13:07:56 system5 kernel: ? report_bug+0x182/0x1b0
Apr 26 13:07:56 system5 kernel: ? handle_bug+0x6e/0xb0
Apr 26 13:07:56 system5 kernel: ? exc_invalid_op+0x18/0x80
Apr 26 13:07:56 system5 kernel: ? asm_exc_invalid_op+0x1b/0x20
Apr 26 13:07:56 system5 kernel: ? rcu_note_context_switch+0x29f/0x2c0
Apr 26 13:07:56 system5 kernel: __schedule+0x88/0x6b0
Apr 26 13:07:56 system5 kernel: schedule+0x29/0xd0
Apr 26 13:07:56 system5 kernel: irq_thread+0xde/0x2e0
Apr 26 13:07:56 system5 kernel: ? __pfx_irq_forced_thread_fn+0x10/0x10
Apr 26 13:07:56 system5 kernel: ? __pfx_irq_thread_dtor+0x10/0x10
Apr 26 13:07:56 system5 kernel: ? __pfx_irq_thread+0x10/0x10
Apr 26 13:07:56 system5 kernel: kthread+0xe4/0x110
Apr 26 13:07:56 system5 kernel: ? __pfx_kthread+0x10/0x10
Apr 26 13:07:56 system5 kernel: ret_from_fork+0x47/0x70
Apr 26 13:07:56 system5 kernel: ? __pfx_kthread+0x10/0x10
Apr 26 13:07:56 system5 kernel: ret_from_fork_asm+0x1a/0x30
Apr 26 13:07:56 system5 kernel: </TASK>
Apr 26 13:07:56 system5 kernel: ---[ end trace 0000000000000000 ]---
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 kernel: NOHZ tick-stop error: local softirq work is pending, handler #80!!!
Apr 26 13:07:56 system5 systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
Apr 26 13:07:56 system5 systemd[1]: ldconfig.service - Rebuild Dynamic Linker Cache was skipped because no trigger condition checks were met.
Apr 26 13:07:57 system5 kernel: mei_gsc i915.mei-gsc.2816: waiting for mei start failed
Apr 26 13:07:57 system5 kernel: mei_gsc i915.mei-gsc.2816: HBM haven't started
Apr 26 13:07:57 system5 kernel: mei_gsc i915.mei-gsc.2816: link layer initialization failed.
Apr 26 13:07:57 system5 kernel: mei_gsc i915.mei-gsc.2816: init hw failure.
Apr 26 13:07:57 system5 kernel: usbcore: registered new interface driver ov534
Apr 26 13:07:57 system5 kernel: usb 1-3.1.2: current rate 1764332 is different from the runtime rate 16000
Apr 26 13:07:57 system5 kernel: usb 1-3.1.2: 3:1: cannot get min/max values for control 2 (id 3)
Apr 26 13:07:57 system5 kernel: usbcore: registered new interface driver snd-usb-audio
Apr 26 13:07:57 system5 (udev-worker)[1027]: controlC2: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 2' failed with exit code 99.
Apr 26 13:07:59 system5 kernel: mei_gsc i915.mei-gscfi.2816: wait hw ready failed
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: hw_start failed ret = -62 fw status = 00000345 80210400 00000000 00000000 C0020002 00000000
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: H_RST is set = 0x80000031
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: wait hw ready failed
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: hw_start failed ret = -62 fw status = 00000345 80210400 00000000 00000000 C0020002 00000000
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: H_RST is set = 0x80000031
Apr 26 13:08:03 system5 kernel: i915 0000:0b:00.0: [drm] GT0: HuC: timed out waiting for MEI PXP
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: wait hw ready failed
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: hw_start failed ret = -62 fw status = 00000345 80210400 00000000 00000000 C0020002 00000000
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: reset: reached maximal consecutive resets: disabling the device
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: reset failed ret = -19
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: link layer initialization failed.
Apr 26 13:08:03 system5 kernel: mei_gsc i915.mei-gscfi.2816: init hw failure.
Apr 26 13:08:06 system5 kernel: i915 0000:0b:00.0: [drm] *ERROR* [CRTC:82:pipe A] flip_done timed out

`

0 Kudos
Mike_Intel
Moderator
527 Views

Hello MSab,


Thank you for the update.


Just to clarify, this issue happened after OS installation right? No drivers yet?


If you have questions, please let us know. Thank you.


Best regards,

Michael L.

Intel Customer Support Technician


0 Kudos
MSab
Beginner
483 Views

Um. No I installed the drivers according to this guide https://dgpu-docs.intel.com/driver/client/overview.html  (which works fine with the regular kernel) then installed the realtime kernel after.

0 Kudos
Mike_Intel
Moderator
452 Views

Hello MSab,


Thank you for the update.


Kindly check if you can still generate the SSU logs of your system for me to further investigate this issue.


https://www.intel.com/content/www/us/en/download/18895/intel-system-support-utility-for-the-linux-operating-system.html


If you have questions, please let us know. Thank you.


Best regards,

Michael L.

Intel Customer Support Technician


0 Kudos
MSab
Beginner
420 Views

Of course. Here it is. Thank you.

0 Kudos
Mike_Intel
Moderator
337 Views

Hello MSab,


Thank you for the information provided.  


I will do further research on this matter and post the response on this thread once it is available.


If you have questions, please let us know. Thank you.


Best regards,

Michael L.

Intel Customer Support Technician


0 Kudos
Mike_Intel
Moderator
274 Views

Hello MSab,


I hope this message finds you well.


Upon further checking, kindly refer to the link below:


https://dgpu-docs.intel.com/driver/client/overview.html

 

You should use the General Availability (GA) Kernel for ACM/MTL and older GPUs; or the Hardware Enablement (HWE) Kernel for BMG/LNL.

 

RT-kernel is not supported.


If you have questions, please let us know. Thank you.


Best regards,

Michael L.

Intel Customer Support Technician


0 Kudos
Mike_Intel
Moderator
176 Views

Hello MSab,

 

I hope this message finds you well. 


Were you able to check the previous post?


Please let us know if you still need assistance.

 

Best regards,

Michael L.

Intel Customer Support Technician


0 Kudos
MSab
Beginner
131 Views

Hi

RT kernels not being supported I need to think of something else for doing the realtime stuff.

Thank you,
Mani

0 Kudos
Mike_Intel
Moderator
84 Views

Hello MSab,


Thank you for the update and understanding.


Please tell me if you still have clarifications regarding this inquiry.


If you have questions, please let us know. Thank you.


Best regards,

Michael L.

Intel Customer Support Technician


0 Kudos
Reply