* Problem with kernel major than 4.15.x
@ 2019-07-24 12:11 Gilberto Nunes
2019-07-24 12:43 ` Gilberto Nunes
0 siblings, 1 reply; 5+ messages in thread
From: Gilberto Nunes @ 2019-07-24 12:11 UTC (permalink / raw)
To: kernelnewbies
[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]
Hi there
I am usging Linux mint here 19.1.
My laptop has the following configuration:
CPU - AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G
GPU - Wani [Radeon R5/R6/R7 Graphics] (amdgpu)
Network Interface card:
01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
When I install kernel 4.18.x or 5.x, the network doesn't work anymore...
I can loaded the modulo r8169 andr8168.
I saw enp1s0f1 as well but there's no link at all!
Even when I fixed the IP none link!
I cannot ping the network gateway or any other IP inside LAN!
Is there somebody with the same problem????
Thanks a lot.
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
[-- Attachment #1.2: Type: text/html, Size: 1592 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problem with kernel major than 4.15.x
2019-07-24 12:11 Problem with kernel major than 4.15.x Gilberto Nunes
@ 2019-07-24 12:43 ` Gilberto Nunes
2019-07-24 12:44 ` Gilberto Nunes
2019-07-24 14:58 ` amdgpu errors reported with kernel 5.2.2 (was Re: Problem with kernel major than 4.15.x) Yann Droneaud
0 siblings, 2 replies; 5+ messages in thread
From: Gilberto Nunes @ 2019-07-24 12:43 UTC (permalink / raw)
To: kernelnewbies
[-- Attachment #1.1: Type: text/plain, Size: 2036 bytes --]
Hello again!
Right now, I booted my laptop with kernel
Linux version 5.2.2-050202-generic (kernel@kathleen) (gcc version 9.1.0
(Ubuntu 9.1.0-9ubuntu2)) #201907231250 SMP Tue Jul 23 12:53:21 UTC 2019
The system boot slowly, and I have a SSD Samsung, which in kernel 4.15,
boot quickly.
And there's many errors in dmesg command, like you can see in this pastbin
https://paste.ubuntu.com/p/YhbjnzYYYh/
The system get stuck for 5 seconds and then the X login screen appears!
Also, I get this message:
dmesg | grep stuck
[ 40.231513] watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
[kworker/0:1:7]
[ 68.231511] watchdog: BUG: soft lockup - CPU#0 stuck for 21s!
[kworker/0:1:7]
[ 104.231513] watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
[kworker/0:0:5]
[ 176.239514] watchdog: BUG: soft lockup - CPU#3 stuck for 23s!
[kworker/3:3:593]
Which make the system freeze for a while and then return to normal!
Any help?
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
Em qua, 24 de jul de 2019 às 09:11, Gilberto Nunes <
gilberto.nunes32@gmail.com> escreveu:
> Hi there
>
> I am usging Linux mint here 19.1.
> My laptop has the following configuration:
>
> CPU - AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G
> GPU - Wani [Radeon R5/R6/R7 Graphics] (amdgpu)
> Network Interface card:
> 01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
>
> When I install kernel 4.18.x or 5.x, the network doesn't work anymore...
> I can loaded the modulo r8169 andr8168.
> I saw enp1s0f1 as well but there's no link at all!
> Even when I fixed the IP none link!
> I cannot ping the network gateway or any other IP inside LAN!
> Is there somebody with the same problem????
>
> Thanks a lot.
>
> ---
> Gilberto Nunes Ferreira
>
> (47) 3025-5907
> (47) 99676-7530 - Whatsapp / Telegram
>
> Skype: gilberto.nunes36
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 3933 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problem with kernel major than 4.15.x
2019-07-24 12:43 ` Gilberto Nunes
@ 2019-07-24 12:44 ` Gilberto Nunes
2019-07-24 14:58 ` amdgpu errors reported with kernel 5.2.2 (was Re: Problem with kernel major than 4.15.x) Yann Droneaud
1 sibling, 0 replies; 5+ messages in thread
From: Gilberto Nunes @ 2019-07-24 12:44 UTC (permalink / raw)
To: kernelnewbies
[-- Attachment #1.1: Type: text/plain, Size: 2420 bytes --]
Oh! By the way, the network card r8169 are work wonderful!
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
Em qua, 24 de jul de 2019 às 09:43, Gilberto Nunes <
gilberto.nunes32@gmail.com> escreveu:
> Hello again!
>
> Right now, I booted my laptop with kernel
> Linux version 5.2.2-050202-generic (kernel@kathleen) (gcc version 9.1.0
> (Ubuntu 9.1.0-9ubuntu2)) #201907231250 SMP Tue Jul 23 12:53:21 UTC 2019
>
> The system boot slowly, and I have a SSD Samsung, which in kernel 4.15,
> boot quickly.
> And there's many errors in dmesg command, like you can see in this pastbin
>
> https://paste.ubuntu.com/p/YhbjnzYYYh/
>
> The system get stuck for 5 seconds and then the X login screen appears!
> Also, I get this message:
> dmesg | grep stuck
> [ 40.231513] watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
> [kworker/0:1:7]
> [ 68.231511] watchdog: BUG: soft lockup - CPU#0 stuck for 21s!
> [kworker/0:1:7]
> [ 104.231513] watchdog: BUG: soft lockup - CPU#0 stuck for 23s!
> [kworker/0:0:5]
> [ 176.239514] watchdog: BUG: soft lockup - CPU#3 stuck for 23s!
> [kworker/3:3:593]
>
> Which make the system freeze for a while and then return to normal!
>
> Any help?
>
>
>
> ---
> Gilberto Nunes Ferreira
>
> (47) 3025-5907
> (47) 99676-7530 - Whatsapp / Telegram
>
> Skype: gilberto.nunes36
>
>
>
>
>
> Em qua, 24 de jul de 2019 às 09:11, Gilberto Nunes <
> gilberto.nunes32@gmail.com> escreveu:
>
>> Hi there
>>
>> I am usging Linux mint here 19.1.
>> My laptop has the following configuration:
>>
>> CPU - AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G
>> GPU - Wani [Radeon R5/R6/R7 Graphics] (amdgpu)
>> Network Interface card:
>> 01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
>>
>> When I install kernel 4.18.x or 5.x, the network doesn't work anymore...
>> I can loaded the modulo r8169 andr8168.
>> I saw enp1s0f1 as well but there's no link at all!
>> Even when I fixed the IP none link!
>> I cannot ping the network gateway or any other IP inside LAN!
>> Is there somebody with the same problem????
>>
>> Thanks a lot.
>>
>> ---
>> Gilberto Nunes Ferreira
>>
>> (47) 3025-5907
>> (47) 99676-7530 - Whatsapp / Telegram
>>
>> Skype: gilberto.nunes36
>>
>>
>>
>>
[-- Attachment #1.2: Type: text/html, Size: 5164 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 5+ messages in thread
* amdgpu errors reported with kernel 5.2.2 (was Re: Problem with kernel major than 4.15.x)
2019-07-24 12:43 ` Gilberto Nunes
2019-07-24 12:44 ` Gilberto Nunes
@ 2019-07-24 14:58 ` Yann Droneaud
2019-07-24 17:00 ` Gilberto Nunes
1 sibling, 1 reply; 5+ messages in thread
From: Yann Droneaud @ 2019-07-24 14:58 UTC (permalink / raw)
To: Gilberto Nunes, kernelnewbies; +Cc: dri-devel, amd-gfx
Hi,
Le mercredi 24 juillet 2019 à 09:43 -0300, Gilberto Nunes a écrit :
>
> Right now, I booted my laptop with kernel
> Linux version 5.2.2-050202-generic (kernel@kathleen) (gcc version
> 9.1.0 (Ubuntu 9.1.0-9ubuntu2)) #201907231250 SMP Tue Jul 23 12:53:21
> UTC 2019
>
> The system boot slowly, and I have a SSD Samsung, which in kernel
> 4.15, boot quickly.
> And there's many errors in dmesg command, like you can see in this
> pastbin
>
> https://paste.ubuntu.com/p/YhbjnzYYYh/
>
There surely something going on with amdgpu:
[ 1.998021] [drm] amdgpu kernel modesetting enabled.
[ 1.999415] amdgpu 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
[ 1.999417] amdgpu 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xd0800000 -> 0xd0ffffff
[ 1.999419] amdgpu 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 5: 0xd1600000 -> 0xd163ffff
[ 1.999422] fb0: switching to amdgpudrmfb from VESA VGA
[ 1.999606] amdgpu 0000:00:01.0: vgaarb: deactivate vga console
[ 2.000060] [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x1025:0x1201 0xC8).
...
[ 2.000342] [drm] UVD is enabled in physical mode
[ 2.000354] [drm] VCE enabled in physical mode
[ 2.015791] [drm] BIOS signature incorrect 0 0
[ 2.018947] [drm] RAS INFO: ras initialized successfully, hardware ability[0] ras_mask[0]
[ 2.018954] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
[ 2.018961] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
[ 2.018963] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
[ 2.018968] [drm] Detected VRAM RAM=512M, BAR=512M
[ 2.018969] [drm] RAM width 64bits UNKNOWN
[ 2.019323] [drm] amdgpu: 512M of VRAM memory ready
[ 2.019326] [drm] amdgpu: 3072M of GTT memory ready.
[ 2.019349] [drm] GART: num cpu pages 262144, num gpu pages 262144
[ 2.019406] [drm] PCIE GART of 1024M enabled (table at 0x000000F400401000).
[ 2.022066] [drm] Found UVD firmware Version: 1.87 Family ID: 11
[ 2.022077] [drm] UVD ENC is disabled
[ 2.023133] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
...
[ 2.030360] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
[ 2.051726] [drm] Display Core initialized with v3.2.27!
[ 2.059313] [drm] SADs count is: -2, don't need to read it
[ 2.086274] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.086276] [drm] Driver supports precise vblank timestamp query.
[ 2.112287] [drm] UVD initialized successfully.
[ 2.311516] [drm] VCE initialized successfully.
[ 2.315910] kfd kfd: Allocated 3969056 bytes on gart
[ 2.316132] kfd kfd: added device 1002:9874
...
[ 2.317580] fbcon: amdgpudrmfb (fb0) is primary device
[ 2.350513] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device
[ 2.371939] [drm] Initialized amdgpu 3.32.0 20150101 for 0000:00:01.0 on minor 0
[ 2.371999] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xc0000000 -> 0xcfffffff
[ 2.372000] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xd0000000 -> 0xd01fffff
[ 2.372002] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xd1400000 -> 0xd143ffff
[ 2.372213] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x699F 0x1025:0x1210 0xC3).
...
[ 2.372448] kfd kfd: skipped device 1002:699f, PCI rejects atomics
[ 2.372463] [drm] UVD is enabled in VM mode
[ 2.372463] [drm] UVD ENC is enabled in VM mode
[ 2.372467] [drm] VCE enabled in VM mode
[ 2.488633] [drm] GPU posting now...
[ 2.507783] [drm] RAS INFO: ras initialized successfully, hardware ability[0] ras_mask[0]
[ 2.507792] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
[ 2.507860] amdgpu 0000:03:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[ 2.507862] amdgpu 0000:03:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
[ 2.507876] [drm] Detected VRAM RAM=2048M, BAR=256M
[ 2.507876] [drm] RAM width 128bits GDDR5
[ 2.507899] [drm] amdgpu: 2048M of VRAM memory ready
[ 2.507902] [drm] amdgpu: 3072M of GTT memory ready.
[ 2.507934] [drm] GART: num cpu pages 65536, num gpu pages 65536
[ 2.508844] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[ 2.508992] [drm] Chained IB support enabled!
[ 2.511020] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[ 2.513477] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
[ 2.576488] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
[ 2.576521] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
[ 2.576542] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
[ 2.576563] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
[ 2.576584] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
[ 2.576604] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
[ 2.576625] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
...
[ 2.590298] [drm] Display Core initialized with v3.2.27!
[ 2.590367] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.590368] [drm] Driver supports precise vblank timestamp query.
[ 2.617310] [drm] UVD and UVD ENC initialized successfully.
[ 2.727249] [drm] VCE initialized successfully.
[ 2.734907] [drm] Initialized amdgpu 3.32.0 20150101 for 0000:03:00.0 on minor 1
[ 3.911826] amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on uvd (-110).
[ 4.239828] amdgpu: [powerplay]
failed to send message 15b ret is 0
[ 4.838072] amdgpu: [powerplay]
last message was failed ret is 0
[ 5.339761] amdgpu: [powerplay]
failed to send message 15a ret is 0
[ 5.883169] amdgpu: [powerplay]
last message was failed ret is 0
[ 6.420651] amdgpu: [powerplay]
failed to send message 155 ret is 0
[ 6.420775] amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on vce0 (-110).
[ 6.420862] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110).
[ 6.925748] amdgpu: [powerplay]
last message was failed ret is 0
[ 7.419539] amdgpu: [powerplay]
failed to send message 15b ret is 0
[ 11.724123] amdgpu: [powerplay]
last message was failed ret is 0
and so on ...
Regards.
--
Yann Droneaud
OPTEYA
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: amdgpu errors reported with kernel 5.2.2 (was Re: Problem with kernel major than 4.15.x)
2019-07-24 14:58 ` amdgpu errors reported with kernel 5.2.2 (was Re: Problem with kernel major than 4.15.x) Yann Droneaud
@ 2019-07-24 17:00 ` Gilberto Nunes
0 siblings, 0 replies; 5+ messages in thread
From: Gilberto Nunes @ 2019-07-24 17:00 UTC (permalink / raw)
To: Yann Droneaud; +Cc: dri-devel, amd-gfx, kernelnewbies
Thanks Yann to redirect to the proper lists!
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
Em qua, 24 de jul de 2019 às 11:59, Yann Droneaud
<ydroneaud@opteya.com> escreveu:
>
> Hi,
>
> Le mercredi 24 juillet 2019 à 09:43 -0300, Gilberto Nunes a écrit :
> >
> > Right now, I booted my laptop with kernel
> > Linux version 5.2.2-050202-generic (kernel@kathleen) (gcc version
> > 9.1.0 (Ubuntu 9.1.0-9ubuntu2)) #201907231250 SMP Tue Jul 23 12:53:21
> > UTC 2019
> >
> > The system boot slowly, and I have a SSD Samsung, which in kernel
> > 4.15, boot quickly.
> > And there's many errors in dmesg command, like you can see in this
> > pastbin
> >
> > https://paste.ubuntu.com/p/YhbjnzYYYh/
> >
>
> There surely something going on with amdgpu:
>
> [ 1.998021] [drm] amdgpu kernel modesetting enabled.
> [ 1.999415] amdgpu 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
> [ 1.999417] amdgpu 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xd0800000 -> 0xd0ffffff
> [ 1.999419] amdgpu 0000:00:01.0: remove_conflicting_pci_framebuffers: bar 5: 0xd1600000 -> 0xd163ffff
> [ 1.999422] fb0: switching to amdgpudrmfb from VESA VGA
> [ 1.999606] amdgpu 0000:00:01.0: vgaarb: deactivate vga console
> [ 2.000060] [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x1025:0x1201 0xC8).
> ...
> [ 2.000342] [drm] UVD is enabled in physical mode
> [ 2.000354] [drm] VCE enabled in physical mode
> [ 2.015791] [drm] BIOS signature incorrect 0 0
> [ 2.018947] [drm] RAS INFO: ras initialized successfully, hardware ability[0] ras_mask[0]
> [ 2.018954] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
> [ 2.018961] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
> [ 2.018963] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
> [ 2.018968] [drm] Detected VRAM RAM=512M, BAR=512M
> [ 2.018969] [drm] RAM width 64bits UNKNOWN
> [ 2.019323] [drm] amdgpu: 512M of VRAM memory ready
> [ 2.019326] [drm] amdgpu: 3072M of GTT memory ready.
> [ 2.019349] [drm] GART: num cpu pages 262144, num gpu pages 262144
> [ 2.019406] [drm] PCIE GART of 1024M enabled (table at 0x000000F400401000).
> [ 2.022066] [drm] Found UVD firmware Version: 1.87 Family ID: 11
> [ 2.022077] [drm] UVD ENC is disabled
> [ 2.023133] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
> ...
> [ 2.030360] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
> [ 2.051726] [drm] Display Core initialized with v3.2.27!
> [ 2.059313] [drm] SADs count is: -2, don't need to read it
> [ 2.086274] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [ 2.086276] [drm] Driver supports precise vblank timestamp query.
> [ 2.112287] [drm] UVD initialized successfully.
> [ 2.311516] [drm] VCE initialized successfully.
> [ 2.315910] kfd kfd: Allocated 3969056 bytes on gart
> [ 2.316132] kfd kfd: added device 1002:9874
> ...
> [ 2.317580] fbcon: amdgpudrmfb (fb0) is primary device
> [ 2.350513] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device
> [ 2.371939] [drm] Initialized amdgpu 3.32.0 20150101 for 0000:00:01.0 on minor 0
> [ 2.371999] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xc0000000 -> 0xcfffffff
> [ 2.372000] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xd0000000 -> 0xd01fffff
> [ 2.372002] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xd1400000 -> 0xd143ffff
> [ 2.372213] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x699F 0x1025:0x1210 0xC3).
> ...
> [ 2.372448] kfd kfd: skipped device 1002:699f, PCI rejects atomics
> [ 2.372463] [drm] UVD is enabled in VM mode
> [ 2.372463] [drm] UVD ENC is enabled in VM mode
> [ 2.372467] [drm] VCE enabled in VM mode
> [ 2.488633] [drm] GPU posting now...
> [ 2.507783] [drm] RAS INFO: ras initialized successfully, hardware ability[0] ras_mask[0]
> [ 2.507792] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
> [ 2.507860] amdgpu 0000:03:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
> [ 2.507862] amdgpu 0000:03:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
> [ 2.507876] [drm] Detected VRAM RAM=2048M, BAR=256M
> [ 2.507876] [drm] RAM width 128bits GDDR5
> [ 2.507899] [drm] amdgpu: 2048M of VRAM memory ready
> [ 2.507902] [drm] amdgpu: 3072M of GTT memory ready.
> [ 2.507934] [drm] GART: num cpu pages 65536, num gpu pages 65536
> [ 2.508844] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
> [ 2.508992] [drm] Chained IB support enabled!
> [ 2.511020] [drm] Found UVD firmware Version: 1.130 Family ID: 16
> [ 2.513477] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
> [ 2.576488] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
> [ 2.576521] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
> [ 2.576542] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
> [ 2.576563] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
> [ 2.576584] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
> [ 2.576604] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
> [ 2.576625] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
> ...
> [ 2.590298] [drm] Display Core initialized with v3.2.27!
> [ 2.590367] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [ 2.590368] [drm] Driver supports precise vblank timestamp query.
> [ 2.617310] [drm] UVD and UVD ENC initialized successfully.
> [ 2.727249] [drm] VCE initialized successfully.
> [ 2.734907] [drm] Initialized amdgpu 3.32.0 20150101 for 0000:03:00.0 on minor 1
> [ 3.911826] amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on uvd (-110).
> [ 4.239828] amdgpu: [powerplay]
> failed to send message 15b ret is 0
> [ 4.838072] amdgpu: [powerplay]
> last message was failed ret is 0
> [ 5.339761] amdgpu: [powerplay]
> failed to send message 15a ret is 0
> [ 5.883169] amdgpu: [powerplay]
> last message was failed ret is 0
> [ 6.420651] amdgpu: [powerplay]
> failed to send message 155 ret is 0
> [ 6.420775] amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on vce0 (-110).
> [ 6.420862] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110).
> [ 6.925748] amdgpu: [powerplay]
> last message was failed ret is 0
> [ 7.419539] amdgpu: [powerplay]
> failed to send message 15b ret is 0
> [ 11.724123] amdgpu: [powerplay]
> last message was failed ret is 0
>
> and so on ...
>
> Regards.
>
> --
> Yann Droneaud
> OPTEYA
>
>
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-07-24 17:02 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-24 12:11 Problem with kernel major than 4.15.x Gilberto Nunes
2019-07-24 12:43 ` Gilberto Nunes
2019-07-24 12:44 ` Gilberto Nunes
2019-07-24 14:58 ` amdgpu errors reported with kernel 5.2.2 (was Re: Problem with kernel major than 4.15.x) Yann Droneaud
2019-07-24 17:00 ` Gilberto Nunes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).