Re: radeon Disabling GPU acceleration (WB disabled?)

2019-10-22 Thread Alex Deucher
On Tue, Oct 22, 2019 at 12:09 PM Michel Dänzer  wrote:
>
> On 2019-10-20 11:21 p.m., Meelis Roos wrote:
> > I tried 5.2, 5.3 and 5.4-rc4 on my old Fujitsu RX220 with integrated
> > Radeon RV100. Dmesg tells that GPU acceleration is disabled. I do not
> > know if it has been enabled in the past - no old kernels handy at the
> > moment.
> >
> > From dmesg it looks like something with MTRR maybe: WB disabled.
>
> That's harmless.
>
>
> > [8.535975] [drm] Driver supports precise vblank timestamp query.
> > [8.535981] radeon :00:05.0: Disabling GPU acceleration
>
> This looks like drm_irq_install returns an error in radeon_irq_kms_init.
>

Check to see that the sbios assigns an irq to the device.  There may
be an option in the sbios configuration settings.  IIRC, some old
platforms didn't always assign interrupts to vga devices.

Alex
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Re: radeon Disabling GPU acceleration (WB disabled?)

2019-10-22 Thread Michel Dänzer
On 2019-10-20 11:21 p.m., Meelis Roos wrote:
> I tried 5.2, 5.3 and 5.4-rc4 on my old Fujitsu RX220 with integrated
> Radeon RV100. Dmesg tells that GPU acceleration is disabled. I do not
> know if it has been enabled in the past - no old kernels handy at the
> moment.
> 
> From dmesg it looks like something with MTRR maybe: WB disabled.

That's harmless.


> [    8.535975] [drm] Driver supports precise vblank timestamp query.
> [    8.535981] radeon :00:05.0: Disabling GPU acceleration

This looks like drm_irq_install returns an error in radeon_irq_kms_init.


-- 
Earthling Michel Dänzer   |   https://redhat.com
Libre software enthusiast | Mesa and X developer


radeon Disabling GPU acceleration (WB disabled?)

2019-10-20 Thread Meelis Roos

I tried 5.2, 5.3 and 5.4-rc4 on my old Fujitsu RX220 with integrated Radeon 
RV100. Dmesg tells that GPU acceleration is disabled. I do not know if it has 
been enabled in the past - no old kernels handy at the moment.

From dmesg it looks like something with MTRR maybe: WB disabled.

Any ideas what I could be doing wrong?

Full dmesg:

[0.00] Linux version 5.4.0-rc4 (mroos@rx220) (gcc version 9.2.1 
20191008 (Debian 9.2.1-9)) #5 SMP Sun Oct 20 23:59:18 EEST 2019
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-rc4 root=/dev/sda1 
ro
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x1ffd] usable
[0.00] BIOS-e820: [mem 0x1ffe-0x1ffedfff] ACPI data
[0.00] BIOS-e820: [mem 0x1ffee000-0x1ffe] ACPI NVS
[0.00] BIOS-e820: [mem 0x1fff-0x1fff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec02fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xfff0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0006dfff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.3 present.
[0.00] DMI: FUJITSU SIEMENS PRIMERGY RX220/D2130, BIOS 
08.11.Rev.0900.2130  02/13/2007
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 2393.847 MHz processor
[0.008641] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.008642] e820: remove [mem 0x000a-0x000f] usable
[0.017173] AGP: No AGP bridge found
[0.017255] last_pfn = 0x6e max_arch_pfn = 0x4
[0.017259] MTRR default type: uncachable
[0.017260] MTRR fixed ranges enabled:
[0.017261]   0-9 write-back
[0.017262]   A-E uncachable
[0.017263]   F-F write-protect
[0.017264] MTRR variable ranges enabled:
[0.017266]   0 base 01 mask FF write-back
[0.017267]   1 base 02 mask FE write-back
[0.017268]   2 base 04 mask FE write-back
[0.017269]   3 base 06 mask FF8000 write-back
[0.017271]   4 base 068000 mask FFC000 write-back
[0.017272]   5 base 00 mask FFE000 write-back
[0.017272]   6 disabled
[0.017273]   7 disabled
[0.017847] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[0.017962] e820: update [mem 0x2000-0x] usable ==> reserved
[0.017967] e820: update [mem 0x6c000-0x6dfff] usable ==> reserved
[0.017970] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 
512MB of RAM.
[0.017978] [ cut here ]
[0.017986] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/cpu/mtrr/cleanup.c:978 
mtrr_trim_uncached_memory+0x6d2/0x712
[0.017987] Modules linked in:
[0.017991] CPU: 0 PID: 0 Comm: swapper Not tainted 5.4.0-rc4 #5
[0.017993] Hardware name: FUJITSU SIEMENS PRIMERGY RX220/D2130, BIOS 
08.11.Rev.0900.2130  02/13/2007
[0.017996] RIP: 0010:mtrr_trim_uncached_memory+0x6d2/0x712
[0.017999] Code: ff ff 49 01 c4 4d 85 e4 0f 84 79 f9 ff ff 4c 89 e6 48 c7 c7 80 
75 ce 98 48 c1 ee 14 e8 81 3a f7 fe 83 3d 75 f0 08 00 00 75 02 <0f> 0b 48 c7 c7 
8e 73 ce 98 41 bd 01 00 00 00 e8 64 3a f7 fe e8 8b
[0.018001] RSP: :98e03e50 EFLAGS: 00010046 ORIG_RAX: 

[0.018003] RAX: 004c RBX: 0020 RCX: 0a70
[0.018004] RDX:  RSI: 0082 RDI: 99236dac
[0.018006] RBP: 991f0a98 R08: 002a R09: 2e4d415220666f20
[0.018007] R10: 202c79726f6d656d R11: 3520676e69736f6c R12: 2000
[0.018008] R13: 006c R14: 0001 R15: 0001
[0.018010] FS:  () GS:9912e000() 
knlGS:
[0.018012] CS:  0010 DS:  ES:  CR0: 80050033
[0.018013] CR2: 88832ce0cff8 CR3: 00032d198000 CR4: 06a0
[0.018014] Call Trace:
[0.018023]  ? setup_arch+0x410/0x73e
[0.018026]  ? start_kernel+0x55/0x459
[0.018029]  ? secondary_startup_64+0xa4/0xb0
[0.018034] random: get_random_bytes called from 
print_oops_end_marker+0x21/0x40 with crng_init=0
[0.018037] ---[ end trace c4df3968cc2d5337 ]---
[0.018039] update e820 for mtrr
[0.018046] modified physical RAM map:
[0.018048] modified: [mem 0x-0x0fff] reserved
[0.018049] modified: [mem 0x1000-0x0009fbff] usable
[