seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2018/10/20, 08:51:11


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: (solved) kernel 4.17  (Read 2219 times)

0 Members and 1 Guest are viewing this topic.

Offline titan

  • User
  • Posts: 189
(solved) kernel 4.17
« on: 2018/06/05, 12:29:35 »
I think this may be a problem for those using Ryzen 5 CPU with Radeon GPU but latest 4.17.0 towo 1 fails to boot just runs throught to loading /temp and stops . 4.17.0 rc3 is still working fine though
« Last Edit: 2018/07/31, 18:40:07 by piper »

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #1 on: 2018/06/11, 10:10:56 »
I still have problem with latest kernel  4.17.0 towo 2  . Strange how rc3 works fine.



Code: [Select]
inxi -G
Graphics:  Card-1: AMD Raven Bridge [Radeon Vega Series / Radeon Vega Mobile Series] driver: amdgpu v: kernel
           Display: x11 server: X.Org 1.20.0 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa tty: N/A
           OpenGL: renderer: AMD RAVEN (DRM 3.25.0 / 4.17.0-rc3-siduction-amd64 LLVM 6.0.0) v: 4.5 Mesa 18.0.5

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.184
Re: kernel 4.17
« Reply #2 on: 2018/06/11, 10:50:12 »
2 posts with no relevant or helpfull info.
Btw, rc3 was not the only available RC, so i would like to know, since which kernel you have problems.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #3 on: 2018/06/11, 11:31:53 »
What info would help. When I try to boot with 4.17.0 towo 1 it starts to boot but stops when it gets to loading /temp, I assume it would be loading video drivers next ? . I have just tried 4.17.0 towo 2 from this morning and the same happens. I did have a problem getting the pc to boot when I first built it but after installing 4.17.0 rc3 from experimental it worked fine, I have not tried any other kernels.

thanks

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.184
Re: kernel 4.17
« Reply #4 on: 2018/06/11, 12:51:59 »
At least the journal from a failed start would help.
And rc5, rc6 and rc7 are available in our experimental, so you can try them.
« Last Edit: 2018/06/11, 12:55:42 by towo »
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #5 on: 2018/06/11, 13:05:07 »
I don't know how to get a journal from a failed start.    :(   I just assumed a kernel version later that the an earlier rc would be progressive. I am happy using rc3, it works. I disabled experimental repro. If a kernel journal would be useful for you I am happy to do that but I will need instructions.
thanks

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #6 on: 2018/06/11, 13:15:51 »
Just tried 4.17.0 rc7 same situation

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.184
Re: kernel 4.17
« Reply #7 on: 2018/06/11, 13:47:47 »
1. boot the failing kernel
2. reboot into a working one
3. journalctl -b -1
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #8 on: 2018/06/11, 13:50:58 »
Just also tried rc5 and 6
Code: [Select]
ian@sid2:~$  journalctl -b -1
-- Logs begin at Sat 2018-05-05 12:47:44 BST, end at Mon 2018-06-11 12:48:31 BST. --
Jun 11 12:46:42 sid2 kernel: Linux version 4.17.0-rc6-siduction-amd64 (towo@siduction.org) (gcc version 7.3.0 (Debian 7.3.0-19)) #1 SMP
Jun 11 12:46:42 sid2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-rc6-siduction-amd64 root=UUID=6782f1a8-05e4-4d77-addd-bb28b7
Jun 11 12:46:42 sid2 kernel: KERNEL supported cpus:
Jun 11 12:46:42 sid2 kernel:   Intel GenuineIntel
Jun 11 12:46:42 sid2 kernel:   AMD AuthenticAMD
Jun 11 12:46:42 sid2 kernel:   Centaur CentaurHauls
Jun 11 12:46:42 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 11 12:46:42 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 11 12:46:42 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 11 12:46:42 sid2 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 11 12:46:42 sid2 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Jun 11 12:46:42 sid2 kernel: e820: BIOS-provided physical RAM map:
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x0000000004000000-0x0000000004009fff] ACPI NVS
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000000400a000-0x0000000009bfffff] usable
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x0000000009c00000-0x0000000009ffffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000affffff] usable
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000000b020000-0x000000009a598fff] usable
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009a599000-0x000000009a6b0fff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009a6b1000-0x000000009a6cbfff] ACPI data
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009a6cc000-0x000000009a7cefff] usable
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009a7cf000-0x000000009ab86fff] ACPI NVS
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009ab87000-0x000000009b8abfff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009b8ac000-0x000000009b94cfff] type 20
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009b94d000-0x000000009dffffff] usable
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x000000009e000000-0x00000000dfffffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fd800000-0x00000000fdffffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 11 12:46:42 sid2 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f33ffff] usable
Jun 11 12:46:42 sid2 kernel: NX (Execute Disable) protection: active
Jun 11 12:46:42 sid2 kernel: efi: EFI v2.60 by American Megatrends
Jun 11 12:46:42 sid2 kernel: efi:  ACPI 2.0=0x9a6b3000  ACPI=0x9a6b3000  SMBIOS=0x9b81a000  SMBIOS 3.0=0x9b819000  ESRT=0x97eb6018  MEM
Jun 11 12:46:42 sid2 kernel: SMBIOS 3.1.1 present.
Jun 11 12:46:42 sid2 kernel: DMI: System manufacturer System Product Name/PRIME B350M-E, BIOS 4011 04/19/2018
Jun 11 12:46:42 sid2 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 11 12:46:42 sid2 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 11 12:46:42 sid2 kernel: e820: last_pfn = 0x21f340 max_arch_pfn = 0x400000000
Jun 11 12:46:42 sid2 kernel: MTRR default type: uncachable
Jun 11 12:46:42 sid2 kernel: MTRR fixed ranges enabled:
Jun 11 12:46:42 sid2 kernel:   00000-9FFFF write-back
Jun 11 12:46:42 sid2 kernel:   A0000-BFFFF write-through
Jun 11 12:46:42 sid2 kernel:   C0000-FFFFF write-protect
Jun 11 12:46:42 sid2 kernel: MTRR variable ranges enabled:
Jun 11 12:46:42 sid2 kernel:   0 base 000000000000 mask FFFF80000000 write-back
Jun 11 12:46:42 sid2 kernel:   1 base 000080000000 mask FFFFC0000000 write-back
Jun 11 12:46:42 sid2 kernel:   2 base 0000C0000000 mask FFFFE0000000 write-back
Jun 11 12:46:42 sid2 kernel:   3 disabled
Jun 11 12:46:42 sid2 kernel:   4 disabled
Jun 11 12:46:42 sid2 kernel:   5 disabled
Jun 11 12:46:42 sid2 kernel:   6 disabled
Jun 11 12:46:42 sid2 kernel:   7 disabled
Jun 11 12:46:42 sid2 kernel: TOM2: 0000000220000000 aka 8704M
lines 1-67


Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.184
Re: kernel 4.17
« Reply #9 on: 2018/06/11, 14:30:12 »
These are the changes between rc3 and rc7:

http://paste.debian.net/1028766/

There is nothing about AMD CPU or GPU.
And that is the whole log? Nothing more?
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #10 on: 2018/06/11, 14:56:10 »
I think that was the log after rc5 failed and I rebooted with rc3, would you like me to try a later rc or 4.17.0 towo 2
What I posted was all that was available from  journalctl -b -1
After I eventually got the pc to boot with the rc3 some weeks ago I disabled experimental and have done nothing else apart from regular du from usual repros. I tried 4.17.0. towo 1 when it became available and today towo 2

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #11 on: 2018/06/11, 15:00:54 »
Maybe I cocked up during the original install, this is what I posted in the thread about my original problems
"More progress, I downloaded the amdgpu drivers from AMD, They have an install script which fails with wrong OS so I edited the install script changing ubuntu to debian. The amdgpu drivers then appeared in synaptic but not installed so I installed them and now the system boots from HD but graphics only have one size, xrandr only shows one size. after trying a few things I decided to remove the new AMD drivers and to my surprise the system now boots and with all the available screen sizes showing in xrandr."               

Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #12 on: 2018/06/11, 15:24:22 »
I don't know if this is any help
Code: [Select]
ian@sid2:~$  dmesg | grep -i amd
[    0.000000] Linux version 4.17.0-rc3-siduction-amd64 (towo@siduction.org) (gcc version 7.3.0 (Debian 7.3.0-17)) #1 SMP PREEMPT siduction 4.17~rc3-1~exp1 (2018-04-30)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-rc3-siduction-amd64 root=UUID=6782f1a8-05e4-4d77-addd-bb28b77c32ea ro quiet resume=UUID=2018e83a-a247-44d0-ac84-0f93fb1d3c3f systemd.show_status=1
[    0.000000]   AMD AuthenticAMD
[    0.000000] RAMDISK: [mem 0x3412b000-0x3608cfff]
[    0.000000] ACPI: SSDT 0x000000009A6C9180 001A41 (v01 AMD    AmdTable 00000001 INTL 20120913)
[    0.000000] ACPI: SSDT 0x000000009A6BDCE8 005367 (v02 AMD    AmdTable 00000002 MSFT 02000002)
[    0.000000] ACPI: SSDT 0x000000009A6C3050 00119C (v01 AMD    AMD CPU  00000001 AMD  00000001)
[    0.000000] ACPI: CRAT 0x000000009A6C41F0 000810 (v01 AMD    AMD CRAT 00000001 AMD  00000001)
[    0.000000] ACPI: CDIT 0x000000009A6C4A00 000029 (v01 AMD    AMD CDIT 00000001 AMD  00000001)
[    0.000000] ACPI: SSDT 0x000000009A6C4A30 002DA8 (v01 AMD    AMD AOD  00000001 INTL 20120913)
[    0.000000] ACPI: IVRS 0x000000009A6C78D0 0000D0 (v02 AMD    AMD IVRS 00000001 AMD  00000000)
[    0.000000] ACPI: SSDT 0x000000009A6C79A0 0000F8 (v01 AMD    AMD PT   00001000 INTL 20120913)
[    0.000000] ACPI: SSDT 0x000000009A6C7A98 000E96 (v01 AMD    AmdTable 00000001 INTL 20120913)
[    0.000000] ACPI: SSDT 0x000000009A6C8930 000850 (v01 AMD    AmdTable 00000001 INTL 20120913)
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-rc3-siduction-amd64 root=UUID=6782f1a8-05e4-4d77-addd-bb28b77c32ea ro quiet resume=UUID=2018e83a-a247-44d0-ac84-0f93fb1d3c3f systemd.show_status=1
[    0.014625] Spectre V2 : Mitigation: Full AMD retpoline
[    0.018000] smpboot: CPU0: AMD Ryzen 5 2400G with Radeon Vega Graphics (family: 0x17, model: 0x11, stepping: 0x0)
[    0.022009] Performance Events: Fam17h core perfctr, AMD PMU driver.
[    0.103838] ACPI Error: AE_ALREADY_EXISTS, (SSDT:  AMD PT) while loading table (20180313/tbxfload-197)
[    0.529327] AMD-Vi: Unable to write to IOMMU perf counter.
[    0.532305] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
[    0.532306] AMD-Vi: Extended features (0x4f77ef22294ada):
[    0.532308] AMD-Vi: Interrupt remapping enabled
[    0.532309] AMD-Vi: virtual APIC enabled
[    0.626782] AMD-Vi: Lazy IO/TLB flushing enabled
[    0.627451] amd_uncore: AMD NB counters detected
[    0.627457] amd_uncore: AMD LLC counters detected
[    0.725903] usb usb1: Manufacturer: Linux 4.17.0-rc3-siduction-amd64 xhci-hcd
[    0.730766] usb usb2: Manufacturer: Linux 4.17.0-rc3-siduction-amd64 xhci-hcd
[    0.733499] usb usb3: Manufacturer: Linux 4.17.0-rc3-siduction-amd64 xhci-hcd
[    0.734017] usb usb4: Manufacturer: Linux 4.17.0-rc3-siduction-amd64 xhci-hcd
[    0.735528] usb usb5: Manufacturer: Linux 4.17.0-rc3-siduction-amd64 xhci-hcd
[    0.735808] usb usb6: Manufacturer: Linux 4.17.0-rc3-siduction-amd64 xhci-hcd
[    3.751565] [drm] amdgpu kernel modesetting enabled.
[    3.762617] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[    3.767972] fb: switching to amdgpudrmfb from EFI VGA
[    3.770143] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_gpu_info.bin
[    3.791230] amdgpu 0000:08:00.0: VRAM: 1024M 0x000000F400000000 - 0x000000F43FFFFFFF (1024M used)
[    3.791232] amdgpu 0000:08:00.0: GTT: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF
[    3.791369] [drm] amdgpu: 1024M of VRAM memory ready
[    3.791371] [drm] amdgpu: 3072M of GTT memory ready.
[    3.792042] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_asd.bin
[    3.792334] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_pfp.bin
[    3.792604] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_me.bin
[    3.792849] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_ce.bin
[    3.793132] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_rlc.bin
[    3.794383] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_mec.bin
[    3.795599] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_mec2.bin
[    3.797031] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_sdma.bin
[    3.798603] amdgpu 0000:08:00.0: firmware: direct-loading firmware amdgpu/raven_vcn.bin
[    3.866324] amdgpu: [powerplay] dpm has been enabled
[    3.928740] fbcon: amdgpudrmfb (fb0) is primary device
[    3.982001] amdgpu 0000:08:00.0: fb0: amdgpudrmfb frame buffer device
[    3.993041] amdgpu 0000:08:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0
[    3.993043] amdgpu 0000:08:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0
[    3.993044] amdgpu 0000:08:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0
[    3.993046] amdgpu 0000:08:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0
[    3.993048] amdgpu 0000:08:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0
[    3.993050] amdgpu 0000:08:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0
[    3.993052] amdgpu 0000:08:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0
[    3.993054] amdgpu 0000:08:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0
[    3.993055] amdgpu 0000:08:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0
[    3.993057] amdgpu 0000:08:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0
[    3.993059] amdgpu 0000:08:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1
[    3.993060] amdgpu 0000:08:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1
[    3.993062] amdgpu 0000:08:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1
[    3.993063] amdgpu 0000:08:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1
[    4.002330] [drm] Initialized amdgpu 3.25.0 20150101 for 0000:08:00.0 on minor 0
ian@sid2:~$


Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #13 on: 2018/06/13, 09:33:17 »
Just tried 4.17.1 -towo 1 and boot fails with  AMD Ryzen 5 2400G  journal log below

Code: [Select]
ian@sid2:~$ journalctl -b -1
-- Logs begin at Sat 2018-05-05 12:47:44 BST, end at Wed 2018-06-13 08:21:41 BST. --
Jun 13 08:20:19 sid2 kernel: Linux version 4.17.1-towo.1-siduction-amd64 (towo@siduction.org) (gcc version 7.3.0 (Debian 7.3.0-21)) #1
Jun 13 08:20:19 sid2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.1-towo.1-siduction-amd64 root=UUID=6782f1a8-05e4-4d77-addd-bb2
Jun 13 08:20:19 sid2 kernel: KERNEL supported cpus:
Jun 13 08:20:19 sid2 kernel:   Intel GenuineIntel
Jun 13 08:20:19 sid2 kernel:   AMD AuthenticAMD
Jun 13 08:20:19 sid2 kernel:   Centaur CentaurHauls
Jun 13 08:20:19 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 13 08:20:19 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 13 08:20:19 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 13 08:20:19 sid2 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 13 08:20:19 sid2 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Jun 13 08:20:19 sid2 kernel: e820: BIOS-provided physical RAM map:
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x0000000004000000-0x0000000004009fff] ACPI NVS
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000000400a000-0x0000000009bfffff] usable
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x0000000009c00000-0x0000000009ffffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000affffff] usable
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000000b020000-0x000000009a598fff] usable
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009a599000-0x000000009a6b0fff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009a6b1000-0x000000009a6cbfff] ACPI data
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009a6cc000-0x000000009a7cefff] usable
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009a7cf000-0x000000009ab86fff] ACPI NVS
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009ab87000-0x000000009b8abfff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009b8ac000-0x000000009b94cfff] type 20
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009b94d000-0x000000009dffffff] usable
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x000000009e000000-0x00000000dfffffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fd800000-0x00000000fdffffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 13 08:20:19 sid2 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f33ffff] usable
Jun 13 08:20:19 sid2 kernel: NX (Execute Disable) protection: active
Jun 13 08:20:19 sid2 kernel: efi: EFI v2.60 by American Megatrends
Jun 13 08:20:19 sid2 kernel: efi:  ACPI 2.0=0x9a6b3000  ACPI=0x9a6b3000  SMBIOS=0x9b81a000  SMBIOS 3.0=0x9b819000  ESRT=0x97eb6018  MEM
Jun 13 08:20:19 sid2 kernel: SMBIOS 3.1.1 present.
Jun 13 08:20:19 sid2 kernel: DMI: System manufacturer System Product Name/PRIME B350M-E, BIOS 4011 04/19/2018
Jun 13 08:20:19 sid2 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 13 08:20:19 sid2 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 13 08:20:19 sid2 kernel: e820: last_pfn = 0x21f340 max_arch_pfn = 0x400000000
Jun 13 08:20:19 sid2 kernel: MTRR default type: uncachable
Jun 13 08:20:19 sid2 kernel: MTRR fixed ranges enabled:
Jun 13 08:20:19 sid2 kernel:   00000-9FFFF write-back
Jun 13 08:20:19 sid2 kernel:   A0000-BFFFF write-through
Jun 13 08:20:19 sid2 kernel:   C0000-FFFFF write-protect
Jun 13 08:20:19 sid2 kernel: MTRR variable ranges enabled:
Jun 13 08:20:19 sid2 kernel:   0 base 000000000000 mask FFFF80000000 write-back
Jun 13 08:20:19 sid2 kernel:   1 base 000080000000 mask FFFFC0000000 write-back
Jun 13 08:20:19 sid2 kernel:   2 base 0000C0000000 mask FFFFE0000000 write-back
Jun 13 08:20:19 sid2 kernel:   3 disabled
Jun 13 08:20:19 sid2 kernel:   4 disabled
Jun 13 08:20:19 sid2 kernel:   5 disabled
Jun 13 08:20:19 sid2 kernel:   6 disabled
Jun 13 08:20:19 sid2 kernel:   7 disabled
Jun 13 08:20:19 sid2 kernel: TOM2: 0000000220000000 aka 8704M
lines 1-67


Offline titan

  • User
  • Posts: 189
Re: kernel 4.17
« Reply #14 on: 2018/06/13, 20:32:44 »
I don't know if this is any help a report from Phoronix using  Kernel 4.17  with AMD Ryzen 5 2400G with same mobo and Bios version, says it runs well and is stable.


https://www.phoronix.com/scan.php?page=article&item=ryzen-2400g-may&num=1