Fatal error during gpu init amdgpu

Диагностика проблем с видеокартой AMD Radeon Доброго дня, ЛОРчане! Есть уже достаточно древняя видео карточка AMD Radeon R9 270X, от ASUS (R9270X-DC2T-4GD5) c 4-мя ГиБ GDDR5 памяти. На днях произошла некая поломка, которую я пытаюсь идентифицировать. Хоть карточка и древняя, но время сейчас не самое удачное для покупки новой. Да и в любом случае […]

Содержание

  1. Диагностика проблем с видеокартой AMD Radeon
  2. amdgpu fatal error during GPU init (Polaris, powerpc64) #237
  3. Comments
  4. Thread: Fatal error — GPU Init
  5. Fatal error — GPU Init
  6. Re: Fatal error — GPU Init
  7. Re: Fatal error — GPU Init
  8. Re: Fatal error — GPU Init
  9. Re: Fatal error — GPU Init
  10. Arch Linux
  11. #1 2015-09-06 13:26:06
  12. Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  13. #2 2015-09-06 16:03:10
  14. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  15. #3 2015-09-06 17:53:24
  16. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  17. #4 2015-09-06 18:07:46
  18. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  19. #5 2015-09-07 07:40:04
  20. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  21. #6 2015-09-07 11:16:26
  22. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  23. #7 2015-09-07 13:06:44
  24. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  25. #8 2015-09-07 16:02:15
  26. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  27. #9 2015-09-07 16:07:34
  28. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init
  29. #10 2015-09-07 16:15:22
  30. Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Диагностика проблем с видеокартой AMD Radeon

Доброго дня, ЛОРчане!

Есть уже достаточно древняя видео карточка AMD Radeon R9 270X, от ASUS (R9270X-DC2T-4GD5) c 4-мя ГиБ GDDR5 памяти. На днях произошла некая поломка, которую я пытаюсь идентифицировать. Хоть карточка и древняя, но время сейчас не самое удачное для покупки новой. Да и в любом случае было бы интересно разобраться в причинах.

Система работала нормально, просто рабочий стол и зависла совершенно полностью, помог только Reset. После включения на экране появились надписи POST вперемешку с красными горизонтальными линиями высотой в символ (на экране текстовый режим) и шириной в половину экрана. Дальше появился GRUB так же в текстовом режиме. Хотя до этого всегда работал в графическом. Между буквами меню отображались артефакты похожие на символы псевдографики (но не они) зелёного цвета. В UEFI (BIOS) setup войти не удалось, вероятно из-за того, что он работает в графическом режиме. А может быть и удалось. Непонятно, после нажатия Delete просто чёрный экран.

Карточку извлёк, разобрал, почистил от пыли. Поменял термопасту (оригинальная совсем высохла). Собрал. В процессе никаких видимых повреждений, вроде проблемных конденсаторов или следов явного перегрева, я не обнаружил. Естественно разборка и сборка не помогла.

В UEFI (BIOS) setup выставил встроенную в процессор, после этого система стала загружаться нормально. Но R9 279X, естественно, от этого работать не начала. Драйвер ядра её определяет, но выдаёт жалобы:

После загрузки карточка в системе никак не задействуется.

По совету я попробовал её перепрошить на ту же версию VBIOS и это даже помогло один раз. Я прошил, перезагрузил комп, посмотрел dmesg , указанных ошибок там больше не было. Я запустил DRI_PRIME=1 glxgears (DRI_PRIME, т.к. основной была выставлена встроенная), шестерёнки отображались корректно. Проверил glxinfo — информация корректная. Я запустил ещё штук 5 glxgears чтобы немного нагрузить карточку. И система опять намертво зависла, пришлось использовать Reset. После перезагрузки карточка опять оказалась не задействованной, и в dmesg я обнаружил такие же ошибки, как и были (как и написаны выше). Попробовал прошить ещё раз, но это уже не помогло. Сначала я упёрся в ошибку утилиты amdvbflash * сообщающую, что прошивка уже была проведена. Обойти эту проблему помог ключ -fa и прошивка прошла. Однако в этот раз пробема никуда не делась и карточка осталась в нерабочем состоянии. Я попробовал и другую версию VBIOS — ничего. Правда я не уверен, что прошивка действительно в эти разы работала нормально. Несмотря на то, что утилита для прошивки писала

,
при явной проверке контрольной суммы она отличалась от контрольной суммы файла с прошивкой.

Пробовал в этом же слоте другую карточку от NVIDIA — работает нормально. Т.е. с большой вероятностью, это не проблема слота или материнской платы. Карточку AMD пока не пробовал в другом системнике, надо его ещё собрать.

Поскольку одна перепрошивка всё же помогла, у меня есть мысль заменить микросхему памяти. Однако я не уверен, что дело всё таки в микросхеме памяти с прошивкой, ведь работа карточки нарушалась уже после загрузки. Хотя я не знаю, используется ли VBIOS после того как карточка была инициализирована или он нужен только в самом начале после включения.

Что ещё можно попробовать с ней сделать кроме как выбросить?

Примечания:
* — Почему-то amdvbflash_linux_4.69 карточку не видит вообще, что с загруженным драйвером, что без него. Поэтому все манипуляции с прошивкой пришлось проводить из FreeDOS.

Источник

amdgpu fatal error during GPU init (Polaris, powerpc64) #237

Observed using drm-devel-kmod and gpu-firmware-kmod from ports on FreeBSD 13-CURRENT r360353, on a Raptor Blackbird w/ DD2.3 POWER9 8-core and Radeon Pro WX 3200 GPU.

I’m going to have to read up on how the DRM system works. but in the meantime, here’s the console log:

[drm] add ip block number 6 [drm] add ip block number 7 [drm] add ip block number 8 [drm] UVD is enabled in VM mode [drm] UVD ENC is enabled in VM mode [drm] VCE enabled in VM mode [drm] vm size is 256 GB, 2 levels, block size is 10-bit, fragment size is 9-bit May 3 02:35:47 clancy kernel: pci_is_thunderbolt_attached not implemented — see your local kernel hacker drmn0: successfully loaded firmware image with name: amdgpu/polaris12_k_mc.bin drmn0: VRAM: 4096M 0x000000F400000000 — 0x000000F4FFFFFFFF (4096M used) drmn0: GART: 256M 0x000000FF00000000 — 0x000000FF0FFFFFFF [drm] Detected VRAM RAM=4096M, BAR=256M [drm] RAM width 128bits GDDR5 [drm] amdgpu: 4096M of VRAM memory ready [drm] amdgpu: 4096M of GTT memory ready. [drm] GART: num cpu pages 65536, num gpu pages 65536May 3 02:35:48 clancy kernel: amdgpu_device_resize_fb_bar not implemented — see your local kernel hacker May 3 02:35:48 clancy kernel: Successfully added WC MTRR for [0x6000000000000-0x600000fffffff]: 0; [drmMay 3 02:35:48 clancy kernel: i_size_write not implemented — see your local kernel hacker ] PCIE GART of 256M enabled (table at 0x000000F400000000). May 3 02:35:48 clancy kernel: get_nr_swap_pages not implemented — see your local kernel hacker drmn0: successfully loaded firmware image with name: amdgpu/polaris12_pfp_2.bin drmn0: successfully loaded firmware image with name: amdgpu/polaris12_me_2.bin drmn0: successfully loaded firmware image with name: amdgpu/polaris12_ce_2.bin [drm] Chained IB support enabled! drmn0: successfully loaded firmware image with name: amdgpu/polaris12_rlc.bin drmn0: successfully loaded firmware image with name: amdgpu/polaris12_mec_2.bin drmn0: successfully loaded firmware image with name: amdgpu/polaris12_mec2_2.bin May 3 02:35:51 clancy kernel: sched_setscheduler not implemented — see your local kernel hacker May 3 02:35:51 clancy kernel: i_size_write not implemented — see your local kernel hacker drmn0: successfully loaded firmware image with name: amdgpu/polaris12_sdma.bin drmn0: successfully loaded firmware image with name: amdgpu/polaris12_sdma1.bin drmn0: successfully loaded firmware image with name: amdgpu/polaris12_uvd.bin [drm] Found UVD firmware Version: 1.130 Family ID: 16 drmn0: successfully loaded firmware image with name: amdgpu/polaris12_vce.bin [drm] Found VCE firmware Version: 53.26 Binary ID: 3 drmn0: successfully loaded firmware image with name: amdgpu/polaris12_k_smc.bin drmn0: amdgpu_device_ip_init failed drmn0: Fatal error during GPU init [drm] amdgpu: finishing device. May 3 02:35:55 clancy kernel: amdgpu: [powerplay] SMU Firmware start failed! May 3 02:35:55 clancy kernel: amdgpu: [powerplay] Failed to load SMU ucode. May 3 02:35:55 clancy kernel: amdgpu: [powerplay] fw load failed May 3 02:35:55 clancy kernel: firmware loading failed WARNING !bo->pin_count failed at /wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-2ccbcda/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c:915 drmn0: 0xc00000023a894800 unpin not necessary ttm_bo_global_kobj_release: START kobj = 0xe0000000dfdd59a0 [drm] amdgpu: ttm finalized device_attach: drmn0 attach returned 22″>

The text was updated successfully, but these errors were encountered:

Источник

Thread: Fatal error — GPU Init

Thread Tools
Display

Fatal error — GPU Init

Hello,
when I try to run a live DVD of 17.04 the following error appears. It can’t detect the correct resolution of my monitor.

I’ve got a AMD Radeon™ HD 7610M Graphics (1GB dedicated memory). Where should I report this bug (if it can be considered a bug)?

Re: Fatal error — GPU Init

Perhaps you can still use ‘nomodeset’ during live/install

and see what happens.

Re: Fatal error — GPU Init

Perhaps you can still use ‘nomodeset’ during live/install

and see what happens.

Is it an option that I should add at boot?

Re: Fatal error — GPU Init

Longer response:
Boot the liveUSB;
At the purple splash screen (stick figure keyboard emblems at bottom of screen) [legacy boot >-> hit any key ->
Language screen -> escape key to accept the default ->
Booting options screen -> F6 key (other options) -> arrow down to the preset option(s) space or enter to accept and then the escape key to exit;
Try «nomodeset» at this time; for other additions the boot options kernel boot line are also now available, one may append «other» desired boot parameters to the end of the line that are not present in the «presets».
Enter key to continue the boot process to the GUI desk top; Degraded graphics is OK at this point.

Additional Drivers, location varies depending on the version, ->locate the Additional Drivers utility and install the recommended driver.

If this works to boot the liveUSB, once installed to the hard drive you might have to also implement «nomodeset» initially to get to the desktop to here also install a graphic’s driver .

Re: Fatal error — GPU Init

Longer response:
Boot the liveUSB;
At the purple splash screen (stick figure keyboard emblems at bottom of screen) [legacy boot >-> hit any key ->
Language screen -> escape key to accept the default ->
Booting options screen -> F6 key (other options) -> arrow down to the preset option(s) space or enter to accept and then the escape key to exit;
Try «nomodeset» at this time; for other additions the boot options kernel boot line are also now available, one may append «other» desired boot parameters to the end of the line that are not present in the «presets».
Enter key to continue the boot process to the GUI desk top; Degraded graphics is OK at this point.

Additional Drivers, location varies depending on the version, ->locate the Additional Drivers utility and install the recommended driver.

If this works to boot the liveUSB, once installed to the hard drive you might have to also implement «nomodeset» initially to get to the desktop to here also install a graphic’s driver .

Thank you very much. Unfortunately it didn’t work. I’ve tried with nomodeset first and with all the other options you can find in the F6 menu then, but no one worked. I’m still using 16.04 because all the newer versions have this problem on my PC.

Источник

Arch Linux

You are not logged in.

#1 2015-09-06 13:26:06

Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Hello ALL.
Please help to resolve (actually would like to update kernel) the following situation:

After upgrading from 3.19.2-pf to 4.1.4-pf or linux 4.2-3 I’ve got during booting via grube the following message on the screen: radeon 0000:01:00.0 Fatal error during GPU init
and no X (xf86-video-ati) and framebuffer in console.
With 3.19.2-pf everything is FINE!

Could someone help what was changed in 4.1.x kernel and what should be done additionally to make it working?

Some additional diagnostic information:
kernels details that were used

Last edited by niam (2015-09-06 17:46:03)

#2 2015-09-06 16:03:10

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Post the output of uname -a

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#3 2015-09-06 17:53:24

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Post the output of uname -a

added to the original post.
Actually my preconclusion — there is no init in kernel radeondrmfb.
Probably like it is described in Gentoo — conflict between vesafb and radeondrmfb.
BUT the strange thing is that there is such sitation on stock arch kernel (not pf) too.

#4 2015-09-06 18:07:46

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Based on my limited interaction with you, you seem to know what you are doing. I have no access to Radeon hardware, so I cannot be of much help beyond the generic.

When you boot from different kernels, I assume that all of the appropriate kernel modules are in place under /lib/modules for the various kernels.
Also, you have some method of ensuring each kernel gets the correct initrd during boot?

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#5 2015-09-07 07:40:04

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Yes initramfs is correct for each kernel and all of them have radeon.ko module.

Strange thing is that after simple pacman -Syy && pacman -Suy I’ve got situation when no X starting due described above problem. This is the reason why I am reporting here. My researching brings me to the kernel problems. I will try to recompile my own kernel but this is not normal for standard kernel!

#6 2015-09-07 11:16:26

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Please post the kernel command lines you use .
Some details about your bootloader and a FULL dmesg / journalctl log from a failed boot may also help.

For clarification : when you tried arch kernel 4.2-3 , you had whole testing repo enabled and it was first repo in pacman.conf ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

#7 2015-09-07 13:06:44

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

I’m using the same card here and generally I have no problems(1). Like Lone_Wolf says, post the full dmesg, and xorg log as it may provide more clues.

(1)
Are you using a compositing window manager? I’m asking because I can make things hang under certain conditions. I can manage to make the card hang if I use a compositing manager (in my case XFCE’s compositor) and if I’m using glamor either by specifying it on a xorg .conf file or if using the modesetting driver (which uses glamor).

Sometimes things go a bit wonky when watching videos with mplayer using vdpau but I have not seen the machine/card hang when this happens.

#8 2015-09-07 16:02:15

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

Please post the kernel command lines you use .
Some details about your bootloader and a FULL dmesg / journalctl log from a failed boot may also help.

For clarification : when you tried arch kernel 4.2-3 , you had whole testing repo enabled and it was first repo in pacman.conf ?

Yes, when I tried arch kernel 4.2-3 , I had whole testing repo enabled and it was first repo in pacman.conf.

For kernel command line -nothing special, all that grub automatically generates.
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-linux-pf root=UUID=a3693671-f526-4814-80ab-90d8d5ff633e rw quiet

#9 2015-09-07 16:07:34

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

#10 2015-09-07 16:15:22

Re: Linux kernel 4.1.x and Radeon Rv610 = fatal error during GPU init

I’m using the same card here and generally I have no problems(1). Like Lone_Wolf says, post the full dmesg, and xorg log as it may provide more clues.

(1)
Are you using a compositing window manager? I’m asking because I can make things hang under certain conditions. I can manage to make the card hang if I use a compositing manager (in my case XFCE’s compositor) and if I’m using glamor either by specifying it on a xorg .conf file or if using the modesetting driver (which uses glamor).

Sometimes things go a bit wonky when watching videos with mplayer using vdpau but I have not seen the machine/card hang when this happens.

I am using xfce too with built in compositor and vdpau and on 3.19.2 linux pf everything fine.
On any kernel from 4.1.x — I have a problem during kernel boot with drm initializing. Why? and what happens with 4.1.x and above kernels — still a question.

Have some guessing that early KMS in initramfs is not working, for the case I am publishing also initramfs for 4.2.03, in mkinitcpio.conf in MODULES radeon is added! (actually marked as explicit)

Last edited by niam (2015-09-07 16:50:05)

Источник

Источник

Description

My laptop with config system_details fails to boot up (not even tty) with any latest kernels not even LTS (including 5.1x and 6.x) . I tried different distributions but the result is always the same . Luckily I found old iso of manjaro with kernel 5.13.12-1-MANJARO which seems to work . other than that the only success I had was when I blacklisted both proprietary & opensource gpu drivers (similar to safe graphics mode) and I was able to login but system does not recognize any monitor and had lot of other bugs due to lack of drivers and is unusable.

I am a userspace developer I think problem is related to

amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
Nov 04 00:07:42.904254 Monarch kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -110
Nov 04 00:07:42.904270 Monarch kernel: amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_init failed
Nov 04 00:07:42.904375 Monarch kernel: amdgpu 0000:01:00.0: amdgpu: Fatal error during GPU init
Nov 04 00:07:42.904476 Monarch kernel: amdgpu 0000:01:00.0: amdgpu: amdgpu: finishing device.
Nov 04 00:07:42.904581 Monarch kernel: amdgpu: probe of 0000:01:00.0 failed with error -110

this error existed for more than year but it always recovered (5.13.1) but I can’t say exactly after which release but kernel doesnot seem to recover anymore . I tried all latest LTS releases,zen but error is always the same i.e page fault

I tried kernel 6.x releases but error is null pointer dereference and not page fault . my guess is that up until some bug fix there used to be a recovery mechanism but was removed after this fix and this fix was pushed to all LTS releases hence I can’t boot up .

Attachments:

  • actual_error.txt

  • successful_boot_log_using_kernel_5.13.12

  • failed_boot_log_using_kernel_5.15.76

Error on linux 6.1.0

[drm] Detected VRAM RAM=4096M, BAR=256M
Nov 04 01:39:58.930900 Monarch kernel: [drm] RAM width 128bits GDDR5
Nov 04 01:39:58.930940 Monarch kernel: [drm] amdgpu: 4096M of VRAM memory ready
Nov 04 01:39:58.930981 Monarch kernel: [drm] amdgpu: 7841M of GTT memory ready.
Nov 04 01:39:58.931023 Monarch kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536
Nov 04 01:39:58.931062 Monarch kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Nov 04 01:39:58.931101 Monarch kernel: [drm] Chained IB support enabled!
Nov 04 01:39:58.960289 Monarch kernel: audit: type=1130 audit(1667506195.498:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@leds:asus::kbd_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 04 01:39:58.960383 Monarch kernel: audit: type=1130 audit(1667506195.574:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 04 01:39:58.960436 Monarch kernel: amdgpu: hwmgr_sw_init smu backed is polaris10_smu
Nov 04 01:39:58.960478 Monarch kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
Nov 04 01:39:58.960516 Monarch kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Nov 04 01:39:58.960552 Monarch kernel: audit: type=1130 audit(1667506196.061:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-byx2duuid-2131x2d271E comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 04 01:39:58.960593 Monarch kernel: amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
Nov 04 01:39:58.960917 Monarch kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -110
Nov 04 01:39:58.960964 Monarch kernel: amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_init failed
Nov 04 01:39:58.961250 Monarch kernel: amdgpu 0000:01:00.0: amdgpu: Fatal error during GPU init
Nov 04 01:39:58.961518 Monarch kernel: amdgpu 0000:01:00.0: amdgpu: amdgpu: finishing device.
Nov 04 01:39:58.961816 Monarch kernel: amdgpu: probe of 0000:01:00.0 failed with error -110
Nov 04 01:39:58.961858 Monarch kernel: BUG: kernel NULL pointer dereference, address: 0000000000000090
Nov 04 01:39:58.961967 Monarch kernel: #PF: supervisor write access in kernel mode
Nov 04 01:39:58.962103 Monarch kernel: #PF: error_code(0x0002) - not-present page
Nov 04 01:39:58.962222 Monarch kernel: PGD 0 P4D 0 
Nov 04 01:39:59.129350 Monarch kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Nov 04 01:39:59.129484 Monarch kernel: CPU: 4 PID: 317 Comm: systemd-udevd Tainted: G           OE      6.1.0-1-MANJARO #1 dc22f7a720c32acf7691c378ceb7ed41eb713b14
Nov 04 01:39:59.129544 Monarch kernel: Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX705DY_FX705DY/FX705DY, BIOS FX705DY.315 03/09/2020
Nov 04 01:39:59.129592 Monarch kernel: RIP: 0010:drm_sched_fini+0x84/0xa0 [gpu_sched]
Nov 04 01:39:59.129638 Monarch kernel: Code: 02 c5 df c7 c6 85 8c 01 00 00 00 5b 5d 41 5c 41 5d e9 74 e3 d3 c8 4c 8d 63 f0 4c 89 e7 e8 f4 d3 96 c8 48 8b 03 48 39 d8 74 0f <c6> 80 90 00 00 00 01 48 8b 00 48 39 d8 75 f1 4c 89 e7 e8 65 d4 96
Nov 04 01:39:59.129684 Monarch kernel: RSP: 0018:ffffb30f405f3b08 EFLAGS: 00010217
Nov 04 01:39:59.129728 Monarch kernel: RAX: 0000000000000000 RBX: ffff8e6d06049ae8 RCX: ffff8e6d0e254000
Nov 04 01:39:59.129779 Monarch kernel: RDX: 0000000000000001 RSI: ffff8e6d0e254028 RDI: ffff8e6d06049ad8
Nov 04 01:39:59.129824 Monarch kernel: RBP: ffff8e6d06049a40 R08: ffffffff89c86ae1 R09: 0000000000000010
Nov 04 01:39:59.129867 Monarch kernel: R10: 0000000000000021 R11: ffff8e6d11137230 R12: ffff8e6d06049ad8
Nov 04 01:39:59.129912 Monarch kernel: R13: ffff8e6d06049a48 R14: ffff8e6d06046618 R15: ffffb30f405f3df0
Nov 04 01:39:59.129956 Monarch kernel: FS:  00007f5efeaeb200(0000) GS:ffff8e701ef00000(0000) knlGS:0000000000000000
Nov 04 01:39:59.130000 Monarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 04 01:39:59.130044 Monarch kernel: CR2: 0000000000000090 CR3: 0000000106834000 CR4: 00000000003506e0
Nov 04 01:39:59.130088 Monarch kernel: Call Trace:
Nov 04 01:39:59.130132 Monarch kernel:  <TASK>
Nov 04 01:39:59.130187 Monarch kernel:  amdgpu_fence_driver_sw_fini+0xc8/0xd0 [amdgpu cface1340c4651f89bc6225f605dac1195c103af]
Nov 04 01:39:59.130237 Monarch kernel:  amdgpu_device_fini_sw+0x33/0x3f0 [amdgpu cface1340c4651f89bc6225f605dac1195c103af]
Nov 04 01:39:59.130282 Monarch kernel:  amdgpu_driver_release_kms+0x16/0x30 [amdgpu cface1340c4651f89bc6225f605dac1195c103af]
Nov 04 01:39:59.130325 Monarch kernel:  devm_drm_dev_init_release+0x49/0x70
Nov 04 01:39:59.130373 Monarch kernel:  release_nodes+0x40/0xb0
Nov 04 01:39:59.130413 Monarch kernel:  devres_release_all+0x8c/0xc0
Nov 04 01:39:59.130447 Monarch kernel:  device_unbind_cleanup+0xe/0x70
Nov 04 01:39:59.130495 Monarch kernel:  really_probe+0x242/0x380
Nov 04 01:39:59.130538 Monarch kernel:  ? pm_runtime_barrier+0x54/0x90
Nov 04 01:39:59.130594 Monarch kernel:  __driver_probe_device+0x78/0x170
Nov 04 01:39:59.130660 Monarch kernel:  driver_probe_device+0x1f/0x90
Nov 04 01:39:59.130715 Monarch kernel:  __driver_attach+0xd5/0x1d0
Nov 04 01:39:59.130764 Monarch kernel:  ? __device_attach_driver+0x110/0x110
Nov 04 01:39:59.130812 Monarch kernel:  bus_for_each_dev+0x8b/0xd0
Nov 04 01:39:59.130883 Monarch kernel:  bus_add_driver+0x1b2/0x200
Nov 04 01:39:59.130954 Monarch kernel:  driver_register+0x8d/0xe0
Nov 04 01:39:59.131019 Monarch kernel:  ? 0xffffffffc184c000
Nov 04 01:39:59.131081 Monarch kernel:  do_one_initcall+0x5d/0x220
Nov 04 01:39:59.131148 Monarch kernel:  do_init_module+0x4a/0x1e0
Nov 04 01:39:59.131224 Monarch kernel:  __do_sys_init_module+0x17f/0x1b0
Nov 04 01:39:59.131293 Monarch kernel:  do_syscall_64+0x5f/0x90
Nov 04 01:39:59.131359 Monarch kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
Nov 04 01:39:59.131428 Monarch kernel:  ? do_syscall_64+0x6b/0x90
Nov 04 01:39:59.131498 Monarch kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
Nov 04 01:39:59.131579 Monarch kernel:  ? do_syscall_64+0x6b/0x90
Nov 04 01:39:59.131659 Monarch kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Nov 04 01:39:59.131724 Monarch kernel: RIP: 0033:0x7f5efef21eae

I hope this helps . Let me know if you need any more info . Currently I am using unsupported kernel (5.13.12). It fails on some other unsupported kernels I have tested

Источник
Attachments

dmesg lsmod lspci lsusb cpuinfo url


(59.30 KB,
application/x-xz)

2018-09-28 16:37 UTC,

quirin.blaeser

Details

dmesg old + new


(34.46 KB,
application/x-xz)

2018-10-09 21:44 UTC,

quirin.blaeser

Details

dmesg + amdgpu_pm_info


(17.41 KB,
application/x-xz)

2018-10-18 13:21 UTC,

quirin.blaeser

Details

config+dmesg for patched 4.19.1


(43.54 KB,
application/x-xz)

2018-11-09 17:24 UTC,

quirin.blaeser

Details

test fix


(562 bytes,
patch)

2018-11-23 21:34 UTC,

Alex Deucher

Details
| Diff

dmesg lsmod additional infos


(35.16 KB,
application/x-xz)

2018-12-13 06:36 UTC,

quirin.blaeser

Details

dmesg amd_gpu_firmware_info


(15.70 KB,
application/x-xz)

2018-12-14 07:59 UTC,

quirin.blaeser

Details

boot.omsg amdgpu_firmware_info messages.part Xorg.0.log.old


(32.48 KB,
application/x-xz)

2019-03-07 21:01 UTC,

quirin.blaeser

Details

Add an attachment
(proposed patch, testcase, etc.)

Источник

  • #1

Помыл карту RX584 бензином калоша, как в ролике на трубе.
Собрал, теперь пишет:
[ 3.641326] [drm:gfx_v8_0_kiq_resume [amdgpu]] *ERROR* KCQ enable failed (scratch(0xC040)=0xCAFEDEAD)
[ 3.642222] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
[ 3.643107] amdgpu 0000:02:00.0: amdgpu_init failed
[ 3.842495] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.843517] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.844529] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.845539] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.846532] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.847526] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.848581] [drm] amdgpu: ttm finalized
[ 3.849449] amdgpu 0000:02:00.0: Fatal error during GPU init
[ 3.850305] [drm] amdgpu: finishing device.
[ 3.851149] [TTM] Memory type 2 has not been initialized
[ 3.852307] amdgpu: probe of 0000:02:00.0 failed with error -22

В ремонт?

  • #2

Надо было поджечь в конце, чтобы бензин выгорел :D

У меня один вопрос, на кой хер ты её мыл в бензине, спирт не можешь купить технический?

  • #3

зачем мыл то ?
Эти руки не для скуки ))))

  • #5

надо было использовать фэйри )

  • #6

Грелась, 85 при внешнем обдуве.
На некоторых алго зависала

  • #8

Теперь в посудомойку и finish

  • #9

Калоша норм тема, но что-то пошло не так у ТС. Собрал скорее всего не так.

  • #10

Надо было поджечь в конце, чтобы бензин выгорел :D

У меня один вопрос, на кой хер ты её мыл в бензине, спирт не можешь купить технический?

Вот этот нехороший человек попутал : www.youtube.com/watch?v=7_E05atGpC0
Ночь сохла на батарее

  • #11

Помыл карту RX584 бензином калоша, как в ролике на трубе.
Собрал, теперь пишет:
[ 3.641326] [drm:gfx_v8_0_kiq_resume [amdgpu]] *ERROR* KCQ enable failed (scratch(0xC040)=0xCAFEDEAD)
[ 3.642222] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
[ 3.643107] amdgpu 0000:02:00.0: amdgpu_init failed
[ 3.842495] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.843517] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.844529] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.845539] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.846532] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.847526] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.848581] [drm] amdgpu: ttm finalized
[ 3.849449] amdgpu 0000:02:00.0: Fatal error during GPU init
[ 3.850305] [drm] amdgpu: finishing device.
[ 3.851149] [TTM] Memory type 2 has not been initialized
[ 3.852307] amdgpu: probe of 0000:02:00.0 failed with error -22

В ремонт?

бензин непричем, смотри пайку,может что отлетело,калошей многие сц пользуются, моют материнки и всякую другую дичь

  • #12

За название-лайк :D
И потёр, вижу, от души

  • #13

Помыл карту RX584 бензином калоша, как в ролике на трубе.
Собрал, теперь пишет:
[ 3.641326] [drm:gfx_v8_0_kiq_resume [amdgpu]] *ERROR* KCQ enable failed (scratch(0xC040)=0xCAFEDEAD)
[ 3.642222] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
[ 3.643107] amdgpu 0000:02:00.0: amdgpu_init failed
[ 3.842495] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.843517] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.844529] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.845539] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.846532] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.847526] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.848581] [drm] amdgpu: ttm finalized
[ 3.849449] amdgpu 0000:02:00.0: Fatal error during GPU init
[ 3.850305] [drm] amdgpu: finishing device.
[ 3.851149] [TTM] Memory type 2 has not been initialized
[ 3.852307] amdgpu: probe of 0000:02:00.0 failed with error -22

В ремонт?

Ты ее сразу после мыться в компьютер вставил — правильно? Нужно было дать просохнуть.

  • #14

Вот этот нехороший человек попутал : www.youtube.com/watch?v=7_E05atGpC0
Ночь сохла на батарее

Зачем на батарее сушить карту, это не вода, бензин испаряется очень быстро, как и спирт. Причина скорее всего в том, что ты повредил какой-то элемент на плате, когда её тёр бензином.

  • #15

Про калошу не зная. Но мою собранную мной электронику от канифоли. Растворителем 646 и зубной щёткой.. Всё работает отлично. Когда просохнут платы. Даже SMD.

  • #16

Помыл карту RX584 бензином калоша, как в ролике на трубе.

А там еще ролик есть, где мужик огурец в жопу пихает. Не смотрел еще?

  • #17

Грелась, 85 при внешнем обдуве.
На некоторых алго зависала

Заменил бы термопасту и продуть радиатор
Зачем в бензин то сразу ? Или вся в потекла от термопрокладок ?

  • #18

Вот этот нехороший человек попутал : www.youtube.com/watch?v=7_E05atGpC0
Ночь сохла на батарее

[ 3.849449] amdgpu 0000:02:00.0: фатальная ошибка во время инициализации графического процессора [3.850305] [drm] amdgpu: финишное устройство. [ 3.851149] [TTM] Тип памяти 2 не был инициализирован [ 3.852307]

  • #19

Помыл карту RX584 бензином калоша, как в ролике на трубе.
Собрал, теперь пишет:
[ 3.641326] [drm:gfx_v8_0_kiq_resume [amdgpu]] *ERROR* KCQ enable failed (scratch(0xC040)=0xCAFEDEAD)
[ 3.642222] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -22
[ 3.643107] amdgpu 0000:02:00.0: amdgpu_init failed
[ 3.842495] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.843517] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.844529] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.845539] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.846532] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.847526] [drm:log_to_debug_console [amdgpu]] *ERROR* dal_irq_service_set: cannot find irq info table entry for 1280332957
[ 3.848581] [drm] amdgpu: ttm finalized
[ 3.849449] amdgpu 0000:02:00.0: Fatal error during GPU init
[ 3.850305] [drm] amdgpu: finishing device.
[ 3.851149] [TTM] Memory type 2 has not been initialized
[ 3.852307] amdgpu: probe of 0000:02:00.0 failed with error -22

В ремонт?

суши, если не чего не отлетело во время мойки

  • #20

Да при мойке какой то элемент монтажа снес. Инфа сотка!
Бенз ни при чем.
Автору в СЦ.

Источник

Update 2018-12-13: This has been resolved in 4.19.8, which was released to core on 2018-12-10.

Update 2018-11-15: The patch available here resolves this issue on 4.19.1. Thanks to /u/Xeno420 for pointing me towards this bug report referencing the patch.

The update from kernel 4.18.16.arch1-1 to 4.19.1.arch1-1 yesterday seems to have broken amdgpu on my PowerColor PCS+ R9 290X 4GB V2.

When attempting to boot using amdgpu, I get only a black screen. System journal (relevant attached below) indicates a fatal error during GPU init from amdgpu.

When attempting to boot using radeon (by excluding radeon.cik_support=0 amdgpu.cik_support=1), all other things equal, the system boots correctly.

Output of journalctl --boot=-1 | grep -n amdgpu:

3:Nov 14 21:44:36 Desktop-Arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=91623e48-4a6c-424e-915c-8e126f4fed26 rw rootflags=subvol=sv_root zswap.enable quiet radeon.cik_support=0 amdgpu.cik_support=1
172:Nov 14 21:44:36 Desktop-Arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=91623e48-4a6c-424e-915c-8e126f4fed26 rw rootflags=subvol=sv_root zswap.enable quiet radeon.cik_support=0 amdgpu.cik_support=1
1239:Nov 14 21:44:38 Desktop-Arch kernel: [drm] amdgpu kernel modesetting enabled.
1261:Nov 14 21:44:38 Desktop-Arch kernel: amdgpu 0000:01:00.0: No more image in the PCI ROM
1264:Nov 14 21:44:38 Desktop-Arch kernel: amdgpu 0000:01:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
1265:Nov 14 21:44:38 Desktop-Arch kernel: amdgpu 0000:01:00.0: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
1268:Nov 14 21:44:38 Desktop-Arch kernel: [drm] amdgpu: 4096M of VRAM memory ready
1269:Nov 14 21:44:38 Desktop-Arch kernel: [drm] amdgpu: 4096M of GTT memory ready.
1274:Nov 14 21:44:38 Desktop-Arch kernel: [drm] enabling PCIE gen 3 link speeds, disable with amdgpu.pcie_gen2=0
1289:Nov 14 21:44:40 Desktop-Arch kernel: amdgpu: [powerplay] 
1314:Nov 14 21:44:40 Desktop-Arch kernel: amdgpu: [powerplay] 
1334:Nov 14 21:44:41 Desktop-Arch kernel: amdgpu: [powerplay] 
1381:Nov 14 21:44:41 Desktop-Arch kernel: amdgpu: [powerplay] 
1432:Nov 14 21:44:41 Desktop-Arch kernel: amdgpu: [powerplay] 
1434:Nov 14 21:44:42 Desktop-Arch kernel: amdgpu: [powerplay] 
1436:Nov 14 21:44:42 Desktop-Arch kernel: amdgpu: [powerplay] Failed to retrieve minimum clocks.
1437:Nov 14 21:44:42 Desktop-Arch kernel: amdgpu: [powerplay] Error in phm_get_clock_info 
1446:Nov 14 21:44:43 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1447:Nov 14 21:44:44 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1448:Nov 14 21:44:45 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1449:Nov 14 21:44:46 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1455:Nov 14 21:44:47 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1456:Nov 14 21:44:48 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1457:Nov 14 21:44:49 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1458:Nov 14 21:44:50 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1459:Nov 14 21:44:51 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1460:Nov 14 21:44:52 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, trying to reset the VCPU!!!
1461:Nov 14 21:44:52 Desktop-Arch kernel: [drm:uvd_v4_2_start [amdgpu]] *ERROR* UVD not responding, giving up!!!
1462:Nov 14 21:44:52 Desktop-Arch kernel: [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* set_powergating_state of IP block <uvd_v4_2> failed -1
1463:Nov 14 21:44:53 Desktop-Arch kernel: amdgpu: [powerplay] 
1465:Nov 14 21:44:53 Desktop-Arch kernel: amdgpu: [powerplay] 
1467:Nov 14 21:44:53 Desktop-Arch kernel: [drm:uvd_v4_2_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 11 test failed (0xCAFEDEAD)
1468:Nov 14 21:44:53 Desktop-Arch kernel: [drm:amdgpu_device_init.cold.14 [amdgpu]] *ERROR* hw_init of IP block <uvd_v4_2> failed -22
1469:Nov 14 21:44:53 Desktop-Arch kernel: amdgpu 0000:01:00.0: amdgpu_device_ip_init failed
1470:Nov 14 21:44:53 Desktop-Arch kernel: amdgpu 0000:01:00.0: Fatal error during GPU init
1471:Nov 14 21:44:53 Desktop-Arch kernel: [drm] amdgpu: finishing device.
1472:Nov 14 21:44:54 Desktop-Arch kernel: amdgpu: [powerplay] 
1474:Nov 14 21:44:54 Desktop-Arch kernel: amdgpu: [powerplay] 
1476:Nov 14 21:44:54 Desktop-Arch kernel: amdgpu: [powerplay] VI should always have 2 performance levels
1477:Nov 14 21:44:55 Desktop-Arch kernel: amdgpu: [powerplay] 
1479:Nov 14 21:44:55 Desktop-Arch kernel: amdgpu: [powerplay] 
1481:Nov 14 21:44:55 Desktop-Arch kernel: amdgpu: [powerplay] 
1483:Nov 14 21:44:56 Desktop-Arch kernel: amdgpu: [powerplay] 
1485:Nov 14 21:44:56 Desktop-Arch kernel: amdgpu: [powerplay] 
1487:Nov 14 21:44:57 Desktop-Arch kernel: amdgpu: [powerplay] 
1489:Nov 14 21:44:57 Desktop-Arch kernel: amdgpu: [powerplay] 
1491:Nov 14 21:44:57 Desktop-Arch kernel: amdgpu: [powerplay] 
1493:Nov 14 21:44:58 Desktop-Arch kernel: amdgpu: [powerplay] 
1495:Nov 14 21:44:58 Desktop-Arch kernel: amdgpu: [powerplay] 
1497:Nov 14 21:44:58 Desktop-Arch kernel: amdgpu: [powerplay] 
1499:Nov 14 21:44:59 Desktop-Arch kernel: amdgpu: [powerplay] 
1501:Nov 14 21:44:59 Desktop-Arch kernel: amdgpu: [powerplay]

Edit: Formatting

Edit 2: Report back with solution

Источник
  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Specialised Support
  • Ubuntu Development Version
  • [SOLVED] Fatal error — GPU Init

  1. Fatal error — GPU Init

    Hello,
    when I try to run a live DVD of 17.04 the following error appears. It can’t detect the correct resolution of my monitor.

    Code:

    [drm:radeon_get_bios [radeon]] *ERROR* unable to locate a BIOS RO [trunked row] 
radeon 0000:01:00.0: Fatal error during GPU init
[TTM] Memory type 2 has not been initialized

    I’ve got a AMD Radeon� HD 7610M Graphics (1GB dedicated memory). Where should I report this bug (if it can be considered a bug)?

  2. Re: Fatal error — GPU Init

    Perhaps you can still use ‘nomodeset’ during live/install

    and see what happens.

  3. Re: Fatal error — GPU Init

    Quote Originally Posted by ventrical
    View Post

    Perhaps you can still use ‘nomodeset’ during live/install

    and see what happens.

    Is it an option that I should add at boot?

  4. Re: Fatal error — GPU Init

    enricobe; Hello;

    short answer:

    Is it an option that I should add at boot?

    Yes;

    Longer response:
    Boot the liveUSB;
    At the purple splash screen (stick figure keyboard emblems at bottom of screen) [legacy boot }-> hit any key ->
    Language screen -> escape key to accept the default ->
    Booting options screen -> F6 key (other options) -> arrow down to the preset option(s) space or enter to accept and then the escape key to exit;
    Try «nomodeset» at this time; for other additions the boot options kernel boot line are also now available, one may append «other» desired boot parameters to the end of the line that are not present in the «presets».
    Enter key to continue the boot process to the GUI desk top; Degraded graphics is OK at this point.

    Additional Drivers, location varies depending on the version, ->locate the Additional Drivers utility and install the recommended driver.

    If this works to boot the liveUSB, once installed to the hard drive you might have to also implement «nomodeset» initially to get to the desktop to here also install a graphic’s driver .

  5. Re: Fatal error — GPU Init

    Quote Originally Posted by Bashing-om
    View Post

    enricobe; Hello;

    short answer:

    Yes;

    Longer response:
    Boot the liveUSB;
    At the purple splash screen (stick figure keyboard emblems at bottom of screen) [legacy boot }-> hit any key ->
    Language screen -> escape key to accept the default ->
    Booting options screen -> F6 key (other options) -> arrow down to the preset option(s) space or enter to accept and then the escape key to exit;
    Try «nomodeset» at this time; for other additions the boot options kernel boot line are also now available, one may append «other» desired boot parameters to the end of the line that are not present in the «presets».
    Enter key to continue the boot process to the GUI desk top; Degraded graphics is OK at this point.

    Additional Drivers, location varies depending on the version, ->locate the Additional Drivers utility and install the recommended driver.

    If this works to boot the liveUSB, once installed to the hard drive you might have to also implement «nomodeset» initially to get to the desktop to here also install a graphic’s driver .

    Thank you very much. Unfortunately it didn’t work. I’ve tried with nomodeset first and with all the other options you can find in the F6 menu then, but no one worked. I’m still using 16.04 because all the newer versions have this problem on my PC.

  6. Re: Fatal error — GPU Init

    enricobe; Well !

    In this case we back up another step or so .
    Did you verify the .iso file with md5sum ? How did you make the liveUSB ?

    Did you verify the copy to the USB ? ( in the liveUSB boot options is » check disk for defects» )

    As we must have a solid foundation before we look for other reasons why not .

  7. Re: Fatal error — GPU Init

    Quote Originally Posted by Bashing-om
    View Post

    enricobe; Well !

    In this case we back up another step or so .
    Did you verify the .iso file with md5sum ? How did you make the liveUSB ?

    Did you verify the copy to the USB ? ( in the liveUSB boot options is » check disk for defects» )

    As we must have a solid foundation before we look for other reasons why not .

    Hello, I didn’t checked this particular DVD but there are some reasons why.
    1) I was a beta tester of the 16.10 and it worked fine for months until an update I did about 1 month before the official release. This update (but unfortunately I haven’t checked which packages had been updated) broke my screen resolution. This happened with an installed and working Kubuntu system.
    2) In the following months I’ve downloaded and tried the stable DVD of 16.10 (both Xubuntu and Ubuntu) and at least 3 daily builds of 17.04. Everytime I got a 800*600 monitor resolution.

    So I could check the DVD I’m using in this moment but I’m pretty sure this is not the root of the problem with 16.04 I have no problems

  8. Re: Fatal error — GPU Init

    enricobe; Hey;

    Your knowledge and skills are the greater than I had «assumed»
    Maybe try a directed boot parameter ?
    radeon.modeset=0
    In 16.10 or 17.04 it does not make sense that the ATI HD 7610M Graphics card is not recognized and the system configures for that card.
    Depending on your exact graphics hardware, Ubuntu 16.04 and later will use either the open-source AMDGPU driver or the open-source Radeon driver, both of which are included in the default Ubuntu 16.04+ installation. The amdgpu driver, pre-installed in 16.04+, is used for AMD’s newest graphics cards. The radeon driver, also pre-installed in 16.04+, is used for older AMD graphics cards that the amdgpu driver doesn’t support.

    Looking now to see what I can find out about the 7610M card .

  9. Re: Fatal error — GPU Init

    With nomodeset or Radeon.modeset =0 I see a new error.

    ERROR no UMS support in Radeon module

    someone on another forums suggests to remove nomodeset to solve this problem

    Last edited by enricobe; December 18th, 2016 at 09:54 PM.

  10. Re: Fatal error — GPU Init

    Quote Originally Posted by enricobe
    View Post

    With nomodeset or Radeon.modeset =0 I see a new error.

    Code:

    ERROR no UMS support in Radeon module

    As You should since (for a quite some time) radeon needs modesetting i.e. UMS…

    Ignota nulla curatio morbi.
    Quod nocet saepe docet.

Bookmarks

Bookmarks


Posting Permissions

Источник
  • Index
  • » Kernel & Hardware
  • » suddenly «Fatal error during GPU init» during boot — radeon

Pages: 1

#1 2012-06-21 16:10:58

kilmister
Member
Registered: 2012-01-28
Posts: 22

suddenly «Fatal error during GPU init» during boot — radeon

Hi,

after a rather abrupt shutdown my system doesn’t boot correctly anymore.
I have an Asus laptop with an ATI radeon HD 2400 (so the sticker on the laptop says — I’m not really a hardware guy)

Before:
While booting, the kernel/console output had bigger, somewhat non-high-resolution letters. Halfway in, the letters changed into a smaller, higher-defined font which was more «beautiful».
Sorry, I don’t know what mechanism that is, so I had to describe it that way.

After:
This doesn’t happen anymore. Rather, I get this message during boot (this is a copy out of /var/log/errors.log):

Jun 21 17:59:55 localhost kernel: [    4.081919] radeon 0000:01:00.0: Fatal error during GPU init
Jun 21 17:59:55 localhost kernel: [    4.082998] radeon 0000:01:00.0: no bo for sa manager
Jun 21 17:59:55 localhost kernel: [    4.083059] [TTM] Trying to take down uninitialized memory manager type 1

I already tried the following:
— reinstall xorg and xf86-video-ati
— sections «Enable KMS» and «Troubleshoot KMS» from that wiki entry:
  https://wiki.archlinux.org/index.php/ATI
— scream and slightly hit the side of the laptop

Nothing worked. Could anyone tell me where to continue searching? I’d hate to reinstall a 1-week old system.

Thanks in advance,
Alex

#2 2012-06-21 18:48:17

Potomac
Member
Registered: 2011-12-25
Posts: 519

Re: suddenly «Fatal error during GPU init» during boot — radeon

you can try adding some kernel boot options in /boot/grub/menu.lst:

noacpi noapic ( and maybe nolapic )

these options will disable acpi and apic functions, sometimes it can help on laptop

Last edited by Potomac (2012-06-21 18:51:21)

#3 2012-06-21 21:12:30

ConnorBehan
Package Maintainer (PM)
From: Long Island NY
Registered: 2007-07-05
Posts: 1,359
Website

Re: suddenly «Fatal error during GPU init» during boot — radeon

1. You can find out what video card you have for sure with the «lspci» command.

2. Switching from low resolution to high resolution letters is what happens when the the radeon module with KMS support gets loaded. The vga console is replaced by a framebuffer console.

3. Before and after what? Did you upgrade something?

The issue is with KMS. I’m pretty sure you could avoid it by disabling KMS but this is not recommended because UMS support is being dropped. What happens if you blacklist the radeon module so that it does not load on boot and later load it yourself with «modprobe radeon»? Try older kernel versions. There is probably one that works and when you find out, you could report the bug on freedesktop.org.

#4 2012-06-22 00:34:41

rowdog
Member
From: East Texas
Registered: 2009-08-19
Posts: 116

Re: suddenly «Fatal error during GPU init» during boot — radeon

It sounds like your «abrupt shutdown» might have mangled your filesystem a bit. Maybe try reinstalling linux-firmware and rebuild the initrd as described on the ATI wiki page you linked to. Also, keep an eye out for other «strange errors» that may have to do with corrupted files.

#5 2012-06-23 16:32:30

stopka
Member
Registered: 2012-06-23
Posts: 6

Re: suddenly «Fatal error during GPU init» during boot — radeon

I have now exactly the same problem. During boot it shows this:
radeon 0000:01:00.0: Fatal error during GPU init
radeon 0000:01:00.0: no bo for sa manager
[TTM] Trying to take down uninitialized memory manager type 1

After boot the X server does not start. There is a message «No screens found» in Xorg log.
Please, what helped you with this problem?

When i uninstall xf86-video-ati, gnome starts, but it blinks a lot (i don’t know what driver it is using instead, but not a proper one)
It stopped working after ordinary system update.

#6 2012-06-24 00:29:24

ConnorBehan
Package Maintainer (PM)
From: Long Island NY
Registered: 2007-07-05
Posts: 1,359
Website

Re: suddenly «Fatal error during GPU init» during boot — radeon

I thought I had damaged my video card recently, but it turns out that I just had to unplug my computer and take the battery out for a few hours. Have you tried this? Also: code tags would be great.

#7 2012-06-25 22:23:13

stopka
Member
Registered: 2012-06-23
Posts: 6

Re: suddenly «Fatal error during GPU init» during boot — radeon

Please help, still have no solution. Graphic card is OK, i can normaly boot windows from another partition. But it looks like open driver problem. I have no idea what to try next. I tryed to reinstal xf86-video-ati with all packages on which it depends on. No result. Only when i completely uninstal xf86-video-ati, system runs X in a very strage way (do not know what drivers it is using instead). I this state is everything blinking and is unusable.

#8 2012-06-25 23:27:25

Terminator
Member
From: Belgium
Registered: 2012-05-07
Posts: 265

Re: suddenly «Fatal error during GPU init» during boot — radeon

If you remove the ati drivers, the mesa-drivers are used I think.

Since the open source drivers don’t work, you should try the closed source drivers (ATI Catalyst) from the AUR. Installing this is a bit of a hassle. The catalyst driver does not support Xorg 1.12, so you have to add a repository for Xorg1.11 and downgrade (see the wiki page). Then, you should install either catalyst-utils and catalyst-hook from AUR (as described in the wiki) or catalyst-total (which combines both and is also mentioned in the wiki).

See the Catalyst Wiki for all information.

Catalyst Utils in AUR
Catalyst Hook
Catalyst Total

edit: I just read the wiki. It seems like there is an easier way to install things now: https://wiki.archlinux.org/index.php/AT … repository

Last edited by Terminator (2012-06-25 23:32:39)

#9 2012-06-27 07:22:46

stopka
Member
Registered: 2012-06-23
Posts: 6

Re: suddenly «Fatal error during GPU init» during boot — radeon

Thanks for advice.
Yes, I know about posibility of instaling catalyst. I would rather use open drivers. The problem is: i am using gnome 3. Will gnome 3 be working on Xorg 1.11?Everything was working fine until the update came. So my graphic car is (or was) supported with open driver. Why it stopped to work suddenly? Do you thing, this is a bug in the driver, or the update has broken some configuration in my computer? Should i report it as a bug?

#10 2012-06-27 19:12:55

ConnorBehan
Package Maintainer (PM)
From: Long Island NY
Registered: 2007-07-05
Posts: 1,359
Website

Re: suddenly «Fatal error during GPU init» during boot — radeon

Stopka, your error has nothing to do with Gnome or X server versions. It’s because of the «Fatal error» you see during boot and probably in your «dmesg» output.

If it was ever working before, you can probably make it work again by downgrading the kernel. Find a kernel version that doesn’t give you this «Fatal error». Then graphics will work and you can report a bug to the radeon developers.

Источник


Description


Carl George



2018-12-16 17:21:16 UTC

Description of problem:
With the latest kernel from updates testing (4.19.9-300), my computer boots but the screen stays black (no visible gdm).  When I ssh in from another machine, gdm says it's running.  In the journal I found this error message:

    Dec 16 11:12:36 zeratul kernel: amdgpu 0000:01:00.0: Direct firmware load for amdgpu/polaris11_k_mc.bin failed with error -2
    Dec 16 11:12:36 zeratul kernel: mc: Failed to load firmware "amdgpu/polaris11_k_mc.bin"
    Dec 16 11:12:36 zeratul kernel: [drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware!
    Dec 16 11:12:36 zeratul kernel: [drm:amdgpu_device_init.cold.28 [amdgpu]] *ERROR* sw_init of IP block <gmc_v8_0> failed -2
    Dec 16 11:12:36 zeratul kernel: amdgpu 0000:01:00.0: amdgpu_device_ip_init failed
    Dec 16 11:12:36 zeratul kernel: amdgpu 0000:01:00.0: Fatal error during GPU init
    Dec 16 11:12:36 zeratul kernel: [drm] amdgpu: finishing device.
    Dec 16 11:12:36 zeratul kernel: amdgpu: probe of 0000:01:00.0 failed with error -2

The previous 4.19.8-300 kernel did not have this issue.  The hardware is a custom PC with an ASUS H87I-PLUS motherboard and an ASUS Radeon RX 560 graphics card.

Version-Release number of selected component (if applicable):
kernel-4.19.9-300.fc29.x86_64

How reproducible:
always

Steps to Reproduce:
1. boot into 4.19.9-300 kernel

Actual results:
Black screen and aforementioned errors in the journal.

Expected results:
Normal boot with gdm showing so I can log in and use my computer.


Comment 1


Yanko Kaneti



2018-12-17 14:33:32 UTC

linux-firmware in Fedora is lagging behind upstream. It looks like the gpu firmware in question was added upstream on Dec 3


Comment 3


Yanko Kaneti



2018-12-18 13:41:26 UTC

*** Bug 1660507 has been marked as a duplicate of this bug. ***


Comment 4


Yanko Kaneti



2018-12-19 17:45:35 UTC

*** Bug 1660776 has been marked as a duplicate of this bug. ***


Comment 5


Yanko Kaneti



2018-12-19 17:50:04 UTC

*** Bug 1660674 has been marked as a duplicate of this bug. ***


Comment 11


Fedora Update System



2018-12-23 02:52:54 UTC

linux-firmware-20181219-89.git0f22c852.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Comment 12


Wade Berrier



2018-12-24 05:36:39 UTC

Thanks for the fix.

Just wanted to point out that even though I had the correct linux-firmware package, I still needed to update my initramfs manually ("dracut --regenerate-all --force").


Comment 13


Carl George



2018-12-26 20:59:42 UTC

I'm late to the party, but this does fix the issue for me.  Thanks!


Comment 14


Fedora Update System



2018-12-30 01:39:10 UTC

linux-firmware-20181219-89.git0f22c852.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


Comment 15


Jeremy Cline



2019-01-07 20:03:23 UTC

*** Bug 1660772 has been marked as a duplicate of this bug. ***


Comment 16


Jeremy Cline



2019-01-07 20:06:23 UTC

*** Bug 1661681 has been marked as a duplicate of this bug. ***

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Fatal error does not occur перевод
  • Fatal error dht h no such file or directory compilation terminated
  • Fatal error detected and logged sorry
  • Fatal error days gone
  • Fatal error data have sent to server dota 2

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии