Bug#1022025: Can't enable amdgpu driver in linux-image-5.10.0-19-amd64
Original problem confirmed here. Booting prior kernel works fine: # xdriinfo Screen 0: radeonsi # pinxi -C --vs pinxi 3.3.22-08 (2022-10-18) CPU: Info: quad core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G bits: 64 type: MT MCP cache: L2: 4 MiB Speed (MHz): avg: 1700 min/max: 1700/3700 cores: 1: 1700 2: 1700 3: 1700 4: 1700 # pinxi -GSaz System: Kernel: 5.10.0-14-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/vmlinuz.old root=LABEL= noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1440x900@60 5 Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0 vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 11 (bullseye) Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel alternate: radeon arch: GCN-2 code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1,DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97") s-diag: 944mm (37.18") Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: top-left model: NEC EA243WM serial: built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l model: Acer K272HUL serial: built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: top-right model: Dell P2213 serial: built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD KAVERI (DRM 3.40.0 5.10.0-14-amd64 LLVM 11.0.1) direct render: Yes Booting is not prevented with radeon.cik_support=1 amdgpu.cik_support=0 instead of radeon.cik_support=0 amdgpu.cik_support=1 on Grub linu line, but X doesn't start. https://paste.debian.net/plain/1257669 and https://paste.debian.net/plain/1257670 are Xorg.0.logs from booting with none of those boot parameters, the latter from attempting to force use of the modesetting DIX display driver via /etc/X11/xorg.conf.d/. https://paste.debian.net/plain/1257668 is last 100 lines of journal from attempt to boot normally with 5.10.0-19 and radeon.cik_support=0 amdgpu.cik_support=1. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Bug#1022025: fails to boot on machines with AMD integrated graphics
I tried again, same result. Either the patches aren't working OR I don't adequately know how to install test kernels. In no uncertain terms, it could very well be my lack of knowledge and ability in this regard. On Wed, 19 Oct 2022 16:01:14 + Dan Coleman wrote: > I'm recompiling to start from scratch and make sure I did this correctly, > but I'll be away from my computer for several hours. If anyone else wants to > jump in and report their own findings, feel free! Hopefully there's some new > info when I get back. > > Thanks very much to Salvatore and Diederik for their help. > > On 10/19/22 10:38 AM, Dan Coleman wrote: > > Ok, I think I succeeded in getting the test kernel to install, but it did > > not solve the issue. The fans ramped up a bit, and I didn't get any errors > > about DRM on the console, but it still hung on the black screen. > > > > Of course, I may have royally screwed up installing the kernel (thank > > goodness for Timeshift), so I welcome another, more experienced tester to > > verify my own findings. > > > > On 10/19/22 10:26 AM, Salvatore Bonaccorso wrote: > >> Hi Dan, hi Diederik > >> > >> On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: > >>> On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: > $ sudo dpkg -i > ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: > considering removing linux-image-5.10.0-19-amd64 in favour of > linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with > removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): > linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) > linux-image-5.10.0-19-amd64 is to be removed. > >>> AFAICT, the last line indicates the problem. > >>> I do know how I would resolve it on my system and if my initial attempt > >>> fails > >>> how to fix that, but I don't feel comfortable suggesting that to you. > >>> > >>> So, I'll let Salvatore take over as he's (WAY) more experienced then I > >>> am. > >> You need to have (temporarily at least) removed the signed package > >> indeed, as they are conflicting. If you do it with apt-get install > >> ./path/to/local/package.deb all the surronding work should be done as > >> well. > >> > >> (And you have the 18 ABI kernel still installed to which you can go > >> back if th test package does no work). > >> > >> After testing, make sure to reinstall the linux-image-amd64 package > >> again. > >> > >> Regards, > >> Salvatore > > >
Bug#1022061: debian-kernel-handbook: improve kernel build steps for newbies
Hi there! This was me, and yes, it was unclear. The short version is that I was sent two patches to test on a kernel, and I had NO idea how to do that. I first tried installing linux-source (which doesn't have a debian subfolder from what I could tell), but then learned that actually what I needed to do was run `apt source linux`. I didn't know that all I needed to do was go to the root of that directory and use test-patches in debian/bin/test-patches. When I finally managed to get the test kernel compiled, I couldn't install it, either via apt or dpkg. I was told that apt would take care of removing the dependencies causing the conflict, but it didn't. DKMS wasn't triggered, it was a mess. I really appreciate the work that goes into making kernel builds painless, but there are some missing steps. $ apt source linux $ cd linux-*/ $ debian/bin/test-patches -j14 /path/to/patch At this point, everything is fine. But try installing the resulting .deb(s) with either apt or dpkg, and you'll get a whole host of errors and not know what to do. Really unclear for end users trying to help by testing. On Wed, 19 Oct 2022 17:41:55 +0200 Diederik de Haas wrote: > Package: debian-kernel-handbook > Version: 1.0.20 > Severity: normal > > In https://bugs.debian.org/1022025#37 I saw another example of someone > who hadn't built a kernel before, found the proper instructions but > didn't succeed in building a (patched) kernel. > > All it took to succeed was some light guidance. And I know that when I > was at that stage, I had similar problems. > > This bug is intended to collect the experiences/problems/etc that > newbies run into, which in turn allows us/me to improve the > documentation for everyone. > > I do intend to submit a MR to improve it, but first we need to collect > the issues newbies run into, which will be done in this bug. > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), > (500, 'stable'), (101, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.0.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > debian-kernel-handbook depends on no packages. > > Versions of packages debian-kernel-handbook recommends: > ii firefox [www-browser] 106.0-1 > ii firefox-esr [www-browser] 102.4.0esr-1 > ii konqueror [www-browser] 4:21.12.3-1 > ii qutebrowser [www-browser] 2.5.2-1 > ii w3m [www-browser] 0.5.3+git20220429-1+b1 > > debian-kernel-handbook suggests no packages. > > -- no debconf information > > >
Bug#1019424: linux-image-5.19.0-1-amd64: endless loop at poweroff/reboot with "block device autoloading is deprecated and will be removed"
On Wed, 19 Oct 2022 12:51:56 +0200 Diederik de Haas wrote: > On woensdag 19 oktober 2022 11:48:22 CEST Roderich Schupp wrote: > > The problem has gone away in linux 6.0.2-1, apparently fixed by > > 4c66a326b5ab784cddd72de07ac5b6210e9e1b06 Revert "block: freeze the > > queue earlier in del_gendisk" > > so for my case you may close this bug. > > Francesco, is the bug fixed for you too with 6.0.2-1? Yes, it seems that the bug is fixed for me too with the Linux kernel version currently in sid (6.0.2-1). I would say that this bug report may stay closed. Thank you for pinging me. Bye! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpRWAWZ00x7x.pgp Description: PGP signature
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Failed to boot kernel 5.10.0-19 with: CPU: AMD Ryzen 7 3800X (16) (no integrated graphics) GPU: AMD ATI Radeon Vega Frontier Edition No issues with kernel 5.10.0-18. --- Ian
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
I can confirm too AMD® Ryzen 7 4700u with radeon graphics × 8 AMD® Renoir
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Same thing here with an AMD Ryzen 5 PRO 3400G system. Also gnome-shell have been complaining about "Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 62 failed: Permission denied" for some time. I don't know what is CRTC 62, but clearly it is related.
Bug#1022051: linux-image-5.10.0-19-amd64: drm errors 'flip_done timed out' during boot
Package: src:linux Version: 5.10.149-1 Followup-For: Bug #1022051 X-Debbugs-Cc: p...@web.de Dear Maintainer, This morning kernel package linux-image-5.10.0-19-amd64 was installed on my PC with AMD Ryzen 7 5700G CPU. After the installation of the package the PC booted very slowly show> [ 15.624720] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 25.864724] [drm:drm_atomic_helper_wait_for_dependencies ([drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 36.104725] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out [ 46.344721] [drm:drm_atomic_helper_wait_for_flip_done (drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out root: recovering journal root: clean, 397409/3145728 files, 5192985/12582912 blocks [ 47.942087] sp5100-tco sp5100-tco: Watchdog hardware is disabled fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress [ 48.523039] r8152 4-2.4:1.0: firmware: failed to load rtl_nic/rt18153b-2.fw (-2) [ 48.523041] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 56.585021] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 66.825042] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out [ 77.065076] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip.done timed out [ 87.305057] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 97.544998] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:80:HDMI-A-1] flip_done timed out [ 107.784928] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out [ 118.024970] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR«* [CRTC:62:crtc-0] flip_done timed out [ 128.265161] [drm:drm_atomic_helper_wait_for_dependencies (drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 138.505040] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out [ 148.745042] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 158.985003] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 169.225025] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:80:HDMI-A-1] flip.done timed out [ 179.464985] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out [ 189.704990] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 199.944982] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*« [CRTC:62:crtc-0] flip.done timed out [ 210.185111] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out [ 220.425049] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 230.664937] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out [ 240.905037] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:80:HDMI-A-1] flip_done timed out [ 251.144926] [dem:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out [ 261.385010] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out After about 5 minutes the screen turned to black (no GUI was initialized) and remained in this state. At this point in time it was at least possible to logon to the machine via ssh. Removal of package linux-image-5.10.0-19-amd64 and rollback to linux-image-5.10.0-18-amd64 has solved the issue. -- Package-specific info: ** Version: Linux version 5.10.0-19-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-1 (2022-10-17) ** Command line: BOOT_IMAGE=/vmlinuz-5.10.0-19-amd64 root=/dev/mapper/vg_raid1-root ro quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: ASUS product_name: System Product Name product_version: System Version chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 2603 board_vendor: ASUSTeK COMPUTER INC. board_name: ProArt B550-CREATOR board_version: Rev X.0x ** Loaded modules: nfnetlink cbc cts rpcsec_gss_krb5 nfsv4 dns_resolver nfs nfs_ssc fscache bridge stp llc binfmt_misc cdc_ether
Bug#1022025: Problem Kernelupdate 5.10.0-19 on AMD Hardware
I have checked something. All three System have completly same installation: On Athlon 220GE without seperate graphics card) After Update to 5.10.0-19 first Blank Screen, after a lot of Time (~30 Minutes) comes Lightdm up, but each Keystroke need Minutes! So i think wie CPU are very very slowly. On Ryzen 3 3250U without seperate graphics card) Same effect, but i have not testet to wait until Ligthdm comes up. On Ryzen 5 2400G with separate Graphics AMD Radeon RX570) No Failure I hope it helps to detect the issue. Marcus Am 19.10.22 um 15:31 schrieb Salvatore Bonaccorso: Hi Marcus, On Wed, Oct 19, 2022 at 02:57:40PM +0200, PC-vor-Ort, Marcus Orthbandt wrote: Hello Kernel-Team, the latest Update for 5.10.0-19 (149-1) prevent Boot of Linux on AMD-Machines. do you know these Bug currently? Can you have a look if the following matches your issue: https://bugs.debian.org/1022025 Regards, Salvatore
Bug#1022068: linux: kernel NULL pointer dereference in nouveau driver on Thinkpad W541
Source: linux Version: 6.0.2-1 Severity: important After upgrading to linux 6.0.2-1 I see the following message during boot: +--- | [3.723631] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device | [...] | [3.855523] vga_switcheroo: enabled | [3.855536] nouveau :01:00.0: DRM: VRAM: 2048 MiB | [3.855537] nouveau :01:00.0: DRM: GART: 1048576 MiB | [3.855539] nouveau :01:00.0: DRM: TMDS table version 2.0 | [3.855541] nouveau :01:00.0: DRM: DCB version 4.0 | [3.855542] nouveau :01:00.0: DRM: DCB outp 00: 08800fc6 0f420010 | [3.855544] nouveau :01:00.0: DRM: DCB outp 01: 08000f82 00020010 | [3.855545] nouveau :01:00.0: DRM: DCB conn 00: 0146 | [3.857230] nouveau :01:00.0: DRM: MM: using COPY for buffer copies | [3.858820] BUG: kernel NULL pointer dereference, address: 0020 | [3.858838] #PF: supervisor read access in kernel mode | [3.858847] #PF: error_code(0x) - not-present page | [3.858856] PGD 0 P4D 0 | [3.858864] Oops: [#1] PREEMPT SMP PTI | [3.858872] CPU: 1 PID: 427 Comm: systemd-udevd Not tainted 6.0.0-1-amd64 #1 Debian 6.0.2-1 | [3.858886] Hardware name: LENOVO 20EGS1FD00/20EGS1FD00, BIOS GNET88WW (2.36 ) 05/30/2018 | [3.858898] RIP: 0010:nvif_object_mthd+0xba/0x200 [nouveau] | [3.858982] Code: 72 ce 41 8d 56 20 49 8b 44 24 08 83 fa 17 0f 86 35 01 00 00 4c 39 e0 0f 84 ea 00 00 00 4c 89 63 10 31 c9 48 89 de c6 43 06 ff <48> 8b 78 20 48 8b 40 38 48 8b 40 28 e8 d5 e3 95 ce 48 8b 3c 24 4c | [3.859008] RSP: 0018:a8e7409bb718 EFLAGS: 00010246 | [3.859018] RAX: RBX: a8e7409bb720 RCX: | [3.859030] RDX: 0028 RSI: a8e7409bb720 RDI: a8e7409bb748 | [3.859042] RBP: R08: a8e7409bb968 R09: 0008 | [3.859053] R10: 95661041f9c0 R11: a8e740e3 R12: 9565ca2114f8 | [3.859065] R13: a8e7409bb720 R14: 0008 R15: a8e7409bb740 | [3.859076] FS: 7fc0a2a6e8c0() GS:956d1e24() knlGS: | [3.859090] CS: 0010 DS: ES: CR0: 80050033 | [3.859100] CR2: 0020 CR3: 000100f74001 CR4: 001706e0 | [3.859112] Call Trace: | [3.859120] | [3.859128] nvif_conn_hpd_status+0x35/0xe0 [nouveau] | [3.859209] nouveau_dp_detect+0x2d0/0x410 [nouveau] | [3.859302] nouveau_connector_detect+0x9b/0x550 [nouveau] | [3.859395] drm_helper_probe_detect+0x84/0xb0 [drm_kms_helper] | [3.859421] drm_helper_probe_single_connector_modes+0x361/0x510 [drm_kms_helper] | [3.859444] drm_client_modeset_probe+0x224/0x1490 [drm] | [3.859487] ? nouveau_cli_init+0x3ea/0x490 [nouveau] | [3.859582] ? __pm_runtime_suspend+0x6a/0x100 | [3.859593] __drm_fb_helper_initial_config_and_unlock+0x44/0x510 [drm_kms_helper] | [3.859618] ? drm_client_init+0x133/0x160 [drm] | [3.859653] nouveau_fbcon_init+0x14a/0x1c0 [nouveau] | [3.859736] nouveau_drm_device_init+0x1ec/0x7a0 [nouveau] | [3.859819] ? pci_update_current_state+0x6e/0xa0 | [3.859831] nouveau_drm_probe+0x128/0x1f0 [nouveau] | [3.859913] ? _raw_spin_unlock_irqrestore+0x23/0x40 | [3.859925] local_pci_probe+0x41/0x80 | [3.859935] pci_device_probe+0xc3/0x230 | [3.859946] really_probe+0xde/0x380 | [3.859955] ? pm_runtime_barrier+0x50/0x90 | [3.859963] __driver_probe_device+0x78/0x170 | [3.859972] driver_probe_device+0x1f/0x90 | [3.859981] __driver_attach+0xd1/0x1d0 | [3.859990] ? __device_attach_driver+0x110/0x110 | [3.86] bus_for_each_dev+0x87/0xd0 | [3.860011] bus_add_driver+0x1ae/0x200 | [3.860019] driver_register+0x89/0xe0 | [3.860028] ? 0xc0731000 | [3.860035] do_one_initcall+0x59/0x220 | [3.860047] do_init_module+0x4a/0x200 | [3.860057] __do_sys_finit_module+0xac/0x120 | [3.860067] do_syscall_64+0x3a/0xc0 | [3.860077] entry_SYSCALL_64_after_hwframe+0x63/0xcd | [3.860088] RIP: 0033:0x7fc0a3177859 | [3.860096] Code: 08 44 89 e0 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 87 05 0f 00 f7 d8 64 89 01 48 | [3.860121] RSP: 002b:7ffdb9440778 EFLAGS: 0246 ORIG_RAX: 0139 | [3.860133] RAX: ffda RBX: 55f6ea1a8cf0 RCX: 7fc0a3177859 | [3.860144] RDX: RSI: 7fc0a3327efd RDI: 0015 | [3.860155] RBP: 7fc0a3327efd R08: R09: 55f6ea1af1a0 | [3.860167] R10: 0015 R11: 0246 R12: 0002 | [3.860178] R13: R14: 55f6ea1df350 R15: 55f6e964fcc1 | [3.860190] | [3.860196] Modules linked in: raid1 md_mod i915 nouveau(+) sd_mod t10_pi sr_mod crc64_rocksoft_generic cdrom crc64_rocksoft
Bug#1022025: fails to boot on machines with AMD integrated graphics
I'm recompiling to start from scratch and make sure I did this correctly, but I'll be away from my computer for several hours. If anyone else wants to jump in and report their own findings, feel free! Hopefully there's some new info when I get back. Thanks very much to Salvatore and Diederik for their help. On 10/19/22 10:38 AM, Dan Coleman wrote: > Ok, I think I succeeded in getting the test kernel to install, but it did not > solve the issue. The fans ramped up a bit, and I didn't get any errors about > DRM on the console, but it still hung on the black screen. > > Of course, I may have royally screwed up installing the kernel (thank > goodness for Timeshift), so I welcome another, more experienced tester to > verify my own findings. > > On 10/19/22 10:26 AM, Salvatore Bonaccorso wrote: >> Hi Dan, hi Diederik >> >> On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: >>> On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: $ sudo dpkg -i ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: considering removing linux-image-5.10.0-19-amd64 in favour of linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) linux-image-5.10.0-19-amd64 is to be removed. >>> AFAICT, the last line indicates the problem. >>> I do know how I would resolve it on my system and if my initial attempt >>> fails >>> how to fix that, but I don't feel comfortable suggesting that to you. >>> >>> So, I'll let Salvatore take over as he's (WAY) more experienced then I am. >> You need to have (temporarily at least) removed the signed package >> indeed, as they are conflicting. If you do it with apt-get install >> ./path/to/local/package.deb all the surronding work should be done as >> well. >> >> (And you have the 18 ABI kernel still installed to which you can go >> back if th test package does no work). >> >> After testing, make sure to reinstall the linux-image-amd64 package >> again. >> >> Regards, >> Salvatore
Bug#1022061: debian-kernel-handbook: improve kernel build steps for newbies
Package: debian-kernel-handbook Version: 1.0.20 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 In https://bugs.debian.org/1022025#37 I saw another example of someone who hadn't built a kernel before, found the proper instructions but didn't succeed in building a (patched) kernel. All it took to succeed was some light guidance. And I know that when I was at that stage, I had similar problems. This bug is intended to collect the experiences/problems/etc that newbies run into, which in turn allows us/me to improve the documentation for everyone. I do intend to submit a MR to improve it, but first we need to collect the issues newbies run into, which will be done in this bug. - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled debian-kernel-handbook depends on no packages. Versions of packages debian-kernel-handbook recommends: ii firefox [www-browser] 106.0-1 ii firefox-esr [www-browser] 102.4.0esr-1 ii konqueror [www-browser]4:21.12.3-1 ii qutebrowser [www-browser] 2.5.2-1 ii w3m [www-browser] 0.5.3+git20220429-1+b1 debian-kernel-handbook suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCY1AavAAKCRDXblvOeH7b bvUZAQCULw272Gb13pivISHTmnfbKEQ9JnSHSgXI+rHwSAVJ7gD/Qucrg6F0eUAO z81Be4N3hfK+A8eCDWcezzvOZudQvQo= =MIDA -END PGP SIGNATURE-
Bug#1022025: fails to boot on machines with AMD integrated graphics
Ok, I think I succeeded in getting the test kernel to install, but it did not solve the issue. The fans ramped up a bit, and I didn't get any errors about DRM on the console, but it still hung on the black screen. Of course, I may have royally screwed up installing the kernel (thank goodness for Timeshift), so I welcome another, more experienced tester to verify my own findings. On 10/19/22 10:26 AM, Salvatore Bonaccorso wrote: > Hi Dan, hi Diederik > > On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: >> On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: >>> $ sudo dpkg -i >>> ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: >>> considering removing linux-image-5.10.0-19-amd64 in favour of >>> linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with >>> removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): >>> linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) >>> linux-image-5.10.0-19-amd64 is to be removed. >> AFAICT, the last line indicates the problem. >> I do know how I would resolve it on my system and if my initial attempt fails >> how to fix that, but I don't feel comfortable suggesting that to you. >> >> So, I'll let Salvatore take over as he's (WAY) more experienced then I am. > You need to have (temporarily at least) removed the signed package > indeed, as they are conflicting. If you do it with apt-get install > ./path/to/local/package.deb all the surronding work should be done as > well. > > (And you have the 18 ABI kernel still installed to which you can go > back if th test package does no work). > > After testing, make sure to reinstall the linux-image-amd64 package > again. > > Regards, > Salvatore
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi Dan, hi Diederik On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: > On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: > > $ sudo dpkg -i > > ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: > > considering removing linux-image-5.10.0-19-amd64 in favour of > > linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with > > removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): > > linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) > > linux-image-5.10.0-19-amd64 is to be removed. > > AFAICT, the last line indicates the problem. > I do know how I would resolve it on my system and if my initial attempt fails > how to fix that, but I don't feel comfortable suggesting that to you. > > So, I'll let Salvatore take over as he's (WAY) more experienced then I am. You need to have (temporarily at least) removed the signed package indeed, as they are conflicting. If you do it with apt-get install ./path/to/local/package.deb all the surronding work should be done as well. (And you have the 18 ABI kernel still installed to which you can go back if th test package does no work). After testing, make sure to reinstall the linux-image-amd64 package again. Regards, Salvatore
Processed: severity of 1022051 is important, forcibly merging 1022025 1022051
Processing commands for cont...@bugs.debian.org: > severity 1022051 important Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Ignoring request to change severity of Bug 1022051 to the same value. Ignoring request to change severity of Bug 1022025 to the same value. Ignoring request to change severity of Bug 1022042 to the same value. > forcemerge 1022025 1022051 Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible Merged 1022025 1022042 1022051 > thanks Stopping processing here. Please contact me if you need assistance. -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042 1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1022051: linux-image-5.10.0-19-amd64: no boot possible
Processing control commands: > severity -1 important Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible Severity set to 'important' from 'critical' > merge -1 1022025 Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible Added tag(s) moreinfo and upstream. Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Merged 1022025 1022042 1022051 -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042 1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022051: linux-image-5.10.0-19-amd64: no boot possible
Control: severity -1 important Control: merge -1 1022025 On Wednesday, 19 October 2022 16:28:10 CEST Michael wrote: > Package: src:linux > Version: 5.10.149-1 > Severity: critical This is the same issue as https://bugs.debian.org/1022025, thus merging signature.asc Description: This is a digitally signed message part.
Bug#1022025: fails to boot on machines with AMD integrated graphics
On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: > $ sudo dpkg -i > ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: > considering removing linux-image-5.10.0-19-amd64 in favour of > linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with > removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): > linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) > linux-image-5.10.0-19-amd64 is to be removed. AFAICT, the last line indicates the problem. I do know how I would resolve it on my system and if my initial attempt fails how to fix that, but I don't feel comfortable suggesting that to you. So, I'll let Salvatore take over as he's (WAY) more experienced then I am. signature.asc Description: This is a digitally signed message part.
Processed: reassign 1019186 to src:linux, reassign 1019195 to src:linux, reassign 1020597 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1019186 src:linux 5.10.0-16 Bug #1019186 [src:linux-image] USB xHCI not worker under kernel 5.10+ 11th Gen Intel Warning: Unknown package 'src:linux-image' Bug reassigned from package 'src:linux-image' to 'src:linux'. No longer marked as found in versions linux-image/5.10.0-16. Ignoring request to alter fixed versions of bug #1019186 to the same values previously set Bug #1019186 [src:linux] USB xHCI not worker under kernel 5.10+ 11th Gen Intel The source 'linux' and version '5.10.0-16' do not appear to match any binary packages Marked as found in versions linux/5.10.0-16. > reassign 1019195 src:linux Bug #1019195 [src:linux-image] debian 11.4 32 bits kernel panic at boot # Package linux-image-5.10.0-17-686 Warning: Unknown package 'src:linux-image' Bug reassigned from package 'src:linux-image' to 'src:linux'. Ignoring request to alter found versions of bug #1019195 to the same values previously set Ignoring request to alter fixed versions of bug #1019195 to the same values previously set > reassign 1020597 src:linux 5.10.136-1 Bug #1020597 [src:linux-image] r8169 transmit queue 0 timed out Warning: Unknown package 'src:linux-image' Bug reassigned from package 'src:linux-image' to 'src:linux'. No longer marked as found in versions linux-image/5.10.136-1. Ignoring request to alter fixed versions of bug #1020597 to the same values previously set Bug #1020597 [src:linux] r8169 transmit queue 0 timed out Marked as found in versions linux/5.10.136-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1019186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019186 1019195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019195 1020597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1000517 to src:linux, reassign 1013180 to src:linux, submitter 1013180 ...
Processing commands for cont...@bugs.debian.org: > reassign 1000517 src:linux 4.19.208-1 Bug #1000517 [linux-image-4.19.0-18-amd64] Kernel NVIDIA Vulkan: rcu: INFO: rcu_sched self-detected stall on CPU Warning: Unknown package 'linux-image-4.19.0-18-amd64' Bug reassigned from package 'linux-image-4.19.0-18-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/4.19.208+1. Ignoring request to alter fixed versions of bug #1000517 to the same values previously set Bug #1000517 [src:linux] Kernel NVIDIA Vulkan: rcu: INFO: rcu_sched self-detected stall on CPU Marked as found in versions linux/4.19.208-1. > reassign 1013180 src:linux 5.18.0-1 Bug #1013180 [linux-image-5.18.0-1-amd64] linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel Warning: Unknown package 'linux-image-5.18.0-1-amd64' Bug reassigned from package 'linux-image-5.18.0-1-amd64' to 'src:linux'. No longer marked as found in versions 5.18.0-1. Ignoring request to alter fixed versions of bug #1013180 to the same values previously set Bug #1013180 [src:linux] linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel The source 'linux' and version '5.18.0-1' do not appear to match any binary packages Marked as found in versions linux/5.18.0-1. > submitter 1013180 Alexandr Podgorniy Bug #1013180 [src:linux] linux-image-5.18.0-1-amd64: System doesn't go to sleep in 5.18.0-1 kernel Changed Bug submitter to 'Alexandr Podgorniy ' from 'Alexandr Podgorniy '. > reassign 1018002 src:linux 5.19-1~exp1 Bug #1018002 [linux-headers-5.19.0-trunk-amd64] linux: Skipping BTF generation for /my/own/lkm.ko due to unavailability of vmlinux Warning: Unknown package 'linux-headers-5.19.0-trunk-amd64' Bug reassigned from package 'linux-headers-5.19.0-trunk-amd64' to 'src:linux'. No longer marked as found in versions linux/5.19-1~exp1. Ignoring request to alter fixed versions of bug #1018002 to the same values previously set Bug #1018002 [src:linux] linux: Skipping BTF generation for /my/own/lkm.ko due to unavailability of vmlinux Marked as found in versions linux/5.19-1~exp1. > reassign 1019186 src:linux-image 5.10.0-16 Bug #1019186 [linux-image] USB xHCI not worker under kernel 5.10+ 11th Gen Intel Warning: Unknown package 'linux-image' Bug reassigned from package 'linux-image' to 'src:linux-image'. Warning: Unknown package 'src:linux-image' Warning: Unknown package 'src:linux-image' No longer marked as found in versions 5.10.0-16. Warning: Unknown package 'src:linux-image' Warning: Unknown package 'src:linux-image' Ignoring request to alter fixed versions of bug #1019186 to the same values previously set Warning: Unknown package 'src:linux-image' Bug #1019186 [src:linux-image] USB xHCI not worker under kernel 5.10+ 11th Gen Intel Warning: Unknown package 'src:linux-image' The source 'linux-image' and version '5.10.0-16' do not appear to match any binary packages Marked as found in versions linux-image/5.10.0-16. Warning: Unknown package 'src:linux-image' > reassign 1019195 src:linux-image Bug #1019195 [linux-image-5.10.0-17-686] debian 11.4 32 bits kernel panic at boot # Package linux-image-5.10.0-17-686 Warning: Unknown package 'linux-image-5.10.0-17-686' Bug reassigned from package 'linux-image-5.10.0-17-686' to 'src:linux-image'. Warning: Unknown package 'src:linux-image' Warning: Unknown package 'src:linux-image' Ignoring request to alter found versions of bug #1019195 to the same values previously set Warning: Unknown package 'src:linux-image' Warning: Unknown package 'src:linux-image' Ignoring request to alter fixed versions of bug #1019195 to the same values previously set Warning: Unknown package 'src:linux-image' > reassign 1020597 src:linux-image 5.10.136-1 Bug #1020597 [linux-image-5.10.0-17-amd64] r8169 transmit queue 0 timed out Warning: Unknown package 'linux-image-5.10.0-17-amd64' Bug reassigned from package 'linux-image-5.10.0-17-amd64' to 'src:linux-image'. Warning: Unknown package 'src:linux-image' Warning: Unknown package 'src:linux-image' No longer marked as found in versions linux-signed-amd64/5.10.136+1. Warning: Unknown package 'src:linux-image' Warning: Unknown package 'src:linux-image' Ignoring request to alter fixed versions of bug #1020597 to the same values previously set Warning: Unknown package 'src:linux-image' Bug #1020597 [src:linux-image] r8169 transmit queue 0 timed out Warning: Unknown package 'src:linux-image' The source 'linux-image' and version '5.10.136-1' do not appear to match any binary packages Marked as found in versions linux-image/5.10.136-1. Warning: Unknown package 'src:linux-image' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000517 1013180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013180 1018002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018002 1019186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019186 1019195:
Bug#1022051: linux-image-5.10.0-19-amd64: no boot possible
Package: src:linux Version: 5.10.149-1 Followup-For: Bug #1022051 Same issue here, similar system -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: BESSTAR TECH LIMITED product_name: HM80 product_version: Default string chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 5.16 board_vendor: BESSTAR TECH LIMITED board_name: HM80 board_version: Default string ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630] Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nvme Kernel modules: nvme 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) DeviceName: Onboard LAN Brodcom Subsystem: Realtek Semiconductor Co., Ltd.
Bug#1022025: fails to boot on machines with AMD integrated graphics
$ sudo dpkg -i ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: considering removing linux-image-5.10.0-19-amd64 in favour of linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) linux-image-5.10.0-19-amd64 is to be removed. dpkg: regarding .../linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb containing linux-image-5.10.0-19-amd64-unsigned: linux-image-5.10.0-19-amd64-unsigned conflicts with linux-image-5.10.0-19-amd64 linux-image-5.10.0-19-amd64 (version 5.10.149-1) is present and installed. dpkg: error processing archive ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb (--install): conflicting packages - not installing linux-image-5.10.0-19-amd64-unsigned Errors were encountered while processing: ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb On 10/19/22 09:32 AM, Diederik de Haas wrote: > On Wednesday, 19 October 2022 16:12:22 CEST Dan Coleman wrote: >> I've built the test kernel successfully, how do I install it? I have the >> following four files. >> >> linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb >> linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb >> linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb >> linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb > # = do as root or with 'sudo' > > # dpkg -i linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb
Bug#1022025: fails to boot on machines with AMD integrated graphics
On Wednesday, 19 October 2022 16:12:22 CEST Dan Coleman wrote: > I've built the test kernel successfully, how do I install it? I have the > following four files. > > linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb > linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb > linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb > linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb # = do as root or with 'sudo' # dpkg -i linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb signature.asc Description: This is a digitally signed message part.
Bug#1022051: linux-image-5.10.0-19-amd64: no boot possible
Package: src:linux Version: 5.10.149-1 Severity: critical Justification: breaks the whole system 5.10.0-18 works without problems the problem starts with the error: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out this part of the journal might help: Okt 19 16:00:16 hiltrup kernel: [ cut here ] Okt 19 16:00:16 hiltrup kernel: WARNING: CPU: 0 PID: 206 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7391 amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu] Okt 19 16:00:16 hiltrup kernel: Modules linked in: amdgpu(+) gpu_sched i2c_algo_bit xhci_pci ttm xhci_hcd nvme ahci drm_kms_helper libahci nvme_core usbcore libata r8169 t10_pi crc_t10dif cec realtek crct10dif_generic hid_generic mdio_devres drm crct10dif_pclmul crc32_pclmul crc32c_intel scsi_mod libphy i2c_piix4 usb_common crct10dif_common i2c_hid wmi battery video hid button Okt 19 16:00:16 hiltrup kernel: CPU: 0 PID: 206 Comm: systemd-udevd Not tainted 5.10.0-19-amd64 #1 Debian 5.10.149-1 Okt 19 16:00:16 hiltrup kernel: Hardware name: TUXEDO TUXEDO Pulse 14 Gen1/PULSE1401, BIOS N.1.07.A03 05/11/2021 Okt 19 16:00:16 hiltrup kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x23af/0x2440 [amdgpu] Okt 19 16:00:16 hiltrup kernel: Code: a8 fd ff ff 01 c7 85 a4 fd ff ff 37 00 00 00 c7 85 ac fd ff ff 20 00 00 00 e8 9d 39 13 00 e9 f4 fa ff ff 0f 0b e9 5f f9 ff ff <0f> 0b e9 af f9 ff ff 0f 0b 0f 0b e9 c6 f9 ff ff 49 8b 06 41 0f b6 Okt 19 16:00:16 hiltrup kernel: RSP: 0018:b2538077b3e0 EFLAGS: 00010002 Okt 19 16:00:16 hiltrup kernel: RAX: 0002 RBX: 0997 RCX: 99ba40b62918 Okt 19 16:00:16 hiltrup kernel: RDX: 0001 RSI: 0297 RDI: 99bac8a20188 Okt 19 16:00:16 hiltrup kernel: RBP: b2538077b6d8 R08: 0005 R09: Okt 19 16:00:16 hiltrup kernel: R10: b2538077b340 R11: b2538077b344 R12: 0297 Okt 19 16:00:16 hiltrup kernel: R13: 99ba40b62800 R14: 99c7f625c000 R15: 99bac8cd1780 Okt 19 16:00:16 hiltrup kernel: FS: 7fea294bb8c0() GS:99c90f60() knlGS: Okt 19 16:00:16 hiltrup kernel: CS: 0010 DS: ES: CR0: 80050033 Okt 19 16:00:16 hiltrup kernel: CR2: 7fea29a4e8cc CR3: 00010bf22000 CR4: 00350ef0 Okt 19 16:00:16 hiltrup kernel: Call Trace: Okt 19 16:00:16 hiltrup kernel: ? __switch_to+0x114/0x460 Okt 19 16:00:16 hiltrup kernel: commit_tail+0x94/0x130 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: drm_atomic_helper_commit+0x11b/0x140 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: drm_client_modeset_commit_atomic+0x1e8/0x230 [drm] Okt 19 16:00:16 hiltrup kernel: drm_client_modeset_commit_locked+0x56/0x160 [drm] Okt 19 16:00:16 hiltrup kernel: drm_fb_helper_pan_display+0xdc/0x210 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: fb_pan_display+0x87/0x110 Okt 19 16:00:16 hiltrup kernel: bit_update_start+0x1a/0x40 Okt 19 16:00:16 hiltrup kernel: fbcon_switch+0x31c/0x490 Okt 19 16:00:16 hiltrup kernel: redraw_screen+0xe5/0x250 Okt 19 16:00:16 hiltrup kernel: do_bind_con_driver.isra.0.cold+0xad/0x103 Okt 19 16:00:16 hiltrup kernel: do_take_over_console+0x116/0x190 Okt 19 16:00:16 hiltrup kernel: do_fbcon_takeover+0x5c/0xc0 Okt 19 16:00:16 hiltrup kernel: register_framebuffer+0x1e4/0x300 Okt 19 16:00:16 hiltrup kernel: __drm_fb_helper_initial_config_and_unlock+0x321/0x4a0 [drm_kms_helper] Okt 19 16:00:16 hiltrup kernel: amdgpu_fbdev_init+0xbd/0x100 [amdgpu] Okt 19 16:00:16 hiltrup kernel: amdgpu_device_init.cold+0x1740/0x1a8e [amdgpu] Okt 19 16:00:16 hiltrup kernel: ? pci_conf1_read+0xa4/0x100 Okt 19 16:00:16 hiltrup kernel: ? pci_bus_read_config_word+0x49/0x70 Okt 19 16:00:16 hiltrup kernel: amdgpu_driver_load_kms+0x2b/0x1f0 [amdgpu] Okt 19 16:00:16 hiltrup kernel: amdgpu_pci_probe+0x187/0x210 [amdgpu] Okt 19 16:00:16 hiltrup kernel: local_pci_probe+0x42/0x80 Okt 19 16:00:16 hiltrup kernel: ? _cond_resched+0x16/0x50 Okt 19 16:00:16 hiltrup kernel: pci_device_probe+0x101/0x1b0 Okt 19 16:00:16 hiltrup kernel: really_probe+0x222/0x480 Okt 19 16:00:16 hiltrup kernel: driver_probe_device+0xe5/0x150 Okt 19 16:00:16 hiltrup kernel: device_driver_attach+0xa9/0xb0 Okt 19 16:00:16 hiltrup kernel: __driver_attach+0xb5/0x170 Okt 19 16:00:16 hiltrup kernel: ? device_driver_attach+0xb0/0xb0 Okt 19 16:00:16 hiltrup kernel: ? device_driver_attach+0xb0/0xb0 Okt 19 16:00:16 hiltrup kernel: bus_for_each_dev+0x78/0xc0 Okt 19 16:00:16 hiltrup kernel: bus_add_driver+0x13a/0x200 Okt 19 16:00:16 hiltrup kernel: driver_register+0x8b/0xe0 Okt 19 16:00:16 hiltrup kernel: ? 0xc0cf9000 Okt 19 16:00:16 hiltrup kernel: do_one_initcall+0x44/0x1d0 Okt 19 16:00:16 hiltrup kernel: ? do_init_module+0x23/0x250 Okt 19 16:00:16 hiltrup kernel: ? kmem_cache_alloc_trace+0xf5/0x200 Okt 19 16:00:16 hiltrup kernel: do_init_module+0x4c/0x250 Okt 19 16:00:16 hiltrup kernel:
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi, I've built the test kernel successfully, how do I install it? I have the following four files. linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb On 10/19/22 08:18 AM, Salvatore Bonaccorso wrote: > Hi Dan, > > On Wed, Oct 19, 2022 at 12:55:16PM +, Dan Coleman wrote: >> Hi, >> >> I would love to, but I'm afraid I don't know how. If you or anyone on the >> chain is willing to show me what commands to enter (I tried following >> thishttps://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html >> but got as far as 4.2.2 and couldn't find a debian directory in the source >> that I unpacked by following the prior instructions), I would be grateful. >> >> That said, I understand time and resources are limited, so no worries if >> that's not possible! > When you do fetch the source package the output will look like: > > # apt-get source linux > Reading package lists... Done > NOTICE: 'linux' packaging is maintained in the 'Git' version control system > at: > https://salsa.debian.org/kernel-team/linux.git > Please use: > git clonehttps://salsa.debian.org/kernel-team/linux.git > to retrieve the latest (possibly unreleased) updates to the package. > Need to get 124 MB of source archives. > Get:1http://security.debian.org/debian-security bullseye-security/main linux > 5.10.149-1 (dsc) [197 kB] > Get:2http://security.debian.org/debian-security bullseye-security/main linux > 5.10.149-1 (tar) [122 MB] > Get:3http://security.debian.org/debian-security bullseye-security/main linux > 5.10.149-1 (diff) [1549 kB] > Fetched 124 MB in 1s (95.7 MB/s) > dpkg-source: info: extracting linux in linux-5.10.149 > dpkg-source: info: unpacking linux_5.10.149.orig.tar.xz > dpkg-source: info: unpacking linux_5.10.149-1.debian.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying debian/gitignore.patch > dpkg-source: info: applying > debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch > [...] > dpkg-source: info: applying > bugfix/all/tools-perf-pmu-events-fix-reproducibility.patch > dpkg-source: info: applying > bugfix/all/bpftool-fix-version-string-in-recursive-builds.patch > dpkg-source: info: applying debian/overlayfs-permit-mounts-in-userns.patch > > Now you have in the current working directory the linux-5.10.149 directory. > > Did you process went that far? If so change into that directory where the > debian/ > directory which will include the debian/bin/test-patches to test-apply the > patches > we would like to test. > > If that will not help I will try to respin a build so anyone affected can test > > Hope this helps already, > > Regards, > Salvatore
Bug#1022042: #1022042 linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Same problem here, after update my laptop failed to boot after grub. Reverted to 5.10.0-18 which works. Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X415DAP_M415DA v: 1.0 serial: Mobo: ASUSTeK model: X415DAP v: 1.0 serial: UEFI: American Megatrends v: X415DAP.308 date: 04/15/2022 AMD Ryzen 3 3250U with Radeon Graphics
Processed: closing 1019424
Processing commands for cont...@bugs.debian.org: > close 1019424 6.0~rc7-1~exp1 Bug #1019424 [src:linux] linux-image-5.19.0-1-amd64: endless loop at poweroff/reboot with "block device autoloading is deprecated and will be removed" Marked as fixed in versions linux/6.0~rc7-1~exp1. Bug #1019424 [src:linux] linux-image-5.19.0-1-amd64: endless loop at poweroff/reboot with "block device autoloading is deprecated and will be removed" Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1019424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Problem Kernelupdate 5.10.0-19 on AMD Hardware
Hi Marcus, On Wed, Oct 19, 2022 at 02:57:40PM +0200, PC-vor-Ort, Marcus Orthbandt wrote: > Hello Kernel-Team, > > the latest Update for 5.10.0-19 (149-1) prevent Boot of Linux on > AMD-Machines. > > do you know these Bug currently? Can you have a look if the following matches your issue: https://bugs.debian.org/1022025 Regards, Salvatore
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi Dan, On Wed, Oct 19, 2022 at 12:55:16PM +, Dan Coleman wrote: > Hi, > > I would love to, but I'm afraid I don't know how. If you or anyone on the > chain is willing to show me what commands to enter (I tried following this > https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html > but got as far as 4.2.2 and couldn't find a debian directory in the source > that I unpacked by following the prior instructions), I would be grateful. > > That said, I understand time and resources are limited, so no worries if > that's not possible! When you do fetch the source package the output will look like: # apt-get source linux Reading package lists... Done NOTICE: 'linux' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/kernel-team/linux.git Please use: git clone https://salsa.debian.org/kernel-team/linux.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 124 MB of source archives. Get:1 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (dsc) [197 kB] Get:2 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (tar) [122 MB] Get:3 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (diff) [1549 kB] Fetched 124 MB in 1s (95.7 MB/s) dpkg-source: info: extracting linux in linux-5.10.149 dpkg-source: info: unpacking linux_5.10.149.orig.tar.xz dpkg-source: info: unpacking linux_5.10.149-1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying debian/gitignore.patch dpkg-source: info: applying debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch [...] dpkg-source: info: applying bugfix/all/tools-perf-pmu-events-fix-reproducibility.patch dpkg-source: info: applying bugfix/all/bpftool-fix-version-string-in-recursive-builds.patch dpkg-source: info: applying debian/overlayfs-permit-mounts-in-userns.patch Now you have in the current working directory the linux-5.10.149 directory. Did you process went that far? If so change into that directory where the debian/ directory which will include the debian/bin/test-patches to test-apply the patches we would like to test. If that will not help I will try to respin a build so anyone affected can test Hope this helps already, Regards, Salvatore
Problem Kernelupdate 5.10.0-19 on AMD Hardware
Hello Kernel-Team, the latest Update for 5.10.0-19 (149-1) prevent Boot of Linux on AMD-Machines. do you know these Bug currently? Marcus from Germany
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi, I would love to, but I'm afraid I don't know how. If you or anyone on the chain is willing to show me what commands to enter (I tried following this https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html but got as far as 4.2.2 and couldn't find a debian directory in the source that I unpacked by following the prior instructions), I would be grateful. That said, I understand time and resources are limited, so no worries if that's not possible! Best, Dan On 10/19/22 07:35 AM, Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > > Hi, > > On Wed, Oct 19, 2022 at 06:22:05AM +, Doublychargedhiggs wrote: >> Same problem here. Kernel version 5.10.149-1 (linux-image-5.10.0-19-amd64) >> hangs on initialisation of amdgpu >> driver, while version 5.10.140-1 (linux-image-5.10.0-18-amd64) boots without >> any problem. >> >> According to the changelogs on kernel.org there were several changes to >> amdgpu in versions >> 5.10.141, 5.10.143, 5.10.144 5.10.146 and 5.10.148. >> >> Some extract from my /var/log/messages just in case it is of any help: >> >> Oct 19 07:05:24 omikron kernel: [0.00] Linux version 5.10.0-19-amd64 >> (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, >> GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-1 >> (2022-10-17) >> Oct 19 07:05:24 omikron kernel: [0.00] Command line: >> BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 >> root=UUID=28af0276-7bd6-468f-b9c9-c743233a9468 ro quiet mem_encrypt=off >> snd_hda_intel.power_save=0 >> ... >> Oct 19 07:05:24 omikron kernel: [2.325914] [drm] amdgpu kernel >> modesetting enabled. >> Oct 19 07:05:24 omikron kernel: [2.327288] amdgpu: Topology: Add APU >> node [0x0:0x0] >> Oct 19 07:05:24 omikron kernel: [2.327398] fb0: switching to amdgpudrmfb >> from EFI VGA >> Oct 19 07:05:24 omikron kernel: [2.328120] Console: switching to colour >> dummy device 80x25 >> Oct 19 07:05:24 omikron kernel: [2.328366] amdgpu :05:00.0: vgaarb: >> deactivate vga console >> Oct 19 07:05:24 omikron kernel: [2.328431] amdgpu :05:00.0: enabling >> device (0006 -> 0007) >> Oct 19 07:05:24 omikron kernel: [2.328516] [drm] initializing kernel >> modesetting (RAVEN 0x1002:0x15DD 0x1002:0x15DD 0x83). >> Oct 19 07:05:24 omikron kernel: [2.328519] amdgpu :05:00.0: amdgpu: >> Trusted Memory Zone (TMZ) feature disabled as experimental (default) >> Oct 19 07:05:24 omikron kernel: [2.328536] [drm] register mmio base: >> 0xFE60 >> Oct 19 07:05:24 omikron kernel: [2.328537] [drm] register mmio size: >> 524288 >> Oct 19 07:05:24 omikron kernel: [2.328559] [drm] add ip block number 0 >> >> Oct 19 07:05:24 omikron kernel: [2.328561] [drm] add ip block number 1 >> >> Oct 19 07:05:24 omikron kernel: [2.328562] [drm] add ip block number 2 >> >> Oct 19 07:05:24 omikron kernel: [2.328564] [drm] add ip block number 3 >> >> Oct 19 07:05:24 omikron kernel: [2.328565] [drm] add ip block number 4 >> >> Oct 19 07:05:24 omikron kernel: [2.328567] [drm] add ip block number 5 >> >> Oct 19 07:05:24 omikron kernel: [2.328568] [drm] add ip block number 6 >> >> Oct 19 07:05:24 omikron kernel: [2.328570] [drm] add ip block number 7 >> >> Oct 19 07:05:24 omikron kernel: [2.328571] [drm] add ip block number 8 >> >> Oct 19 07:05:24 omikron kernel: [2.333054] input: HD-Audio Generic >> HDMI/DP,pcm=3 as >> /devices/pci:00/:00:08.1/:05:00.1/sound/card0/input6 >> Oct 19 07:05:24 omikron kernel: [2.334135] amdgpu :05:00.0: >> firmware: direct-loading firmware amdgpu/raven_gpu_info.bin >> Oct 19 07:05:24 omikron kernel: [2.334155] amdgpu :05:00.0: amdgpu: >> Fetched VBIOS from VFCT >> Oct 19 07:05:24 omikron kernel: [2.334157] amdgpu: ATOM BIOS: >> 113-RAVEN-113 >> Oct 19 07:05:24 omikron kernel: [2.334462] amdgpu :05:00.0: >> firmware: direct-loading firmware amdgpu/raven_sdma.bin >> Oct 19 07:05:24 omikron kernel: [2.334469] [drm] VCN decode is enabled >> in VM mode >> Oct 19 07:05:24 omikron kernel: [2.334470] [drm] VCN encode is enabled >> in VM mode >> Oct 19 07:05:24 omikron kernel: [2.334471] [drm] JPEG decode is enabled >> in VM mode >> Oct 19 07:05:24 omikron kernel: [2.334527] [drm] vm size is 262144 GB, 4 >> levels, block size is 9-bit, fragment size is 9-bit >> Oct 19 07:05:24 omikron kernel: [2.334539] amdgpu :05:00.0: amdgpu: >> VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used) >> Oct 19 07:05:24 omikron kernel: [2.334541] amdgpu :05:00.0: amdgpu: >> GART: 1024M 0x - 0x3FFF >> Oct 19 07:05:24 omikron kernel: [2.334543] amdgpu :05:00.0: amdgpu: >> AGP: 267419648M 0x00F8 - 0x >> Oct 19 07:05:24 omikron kernel: [2.334551] [drm] Detected VRAM >> RAM=2048M, BAR=2048M >> Oct 19 07:05:24 omikron kernel: [2.334552]
Bug#1022025: fails to boot on machines with AMD integrated graphics
Control: tags -1 + moreinfo Hi, On Wed, Oct 19, 2022 at 06:22:05AM +, Doublychargedhiggs wrote: > Same problem here. Kernel version 5.10.149-1 (linux-image-5.10.0-19-amd64) > hangs on initialisation of amdgpu > driver, while version 5.10.140-1 (linux-image-5.10.0-18-amd64) boots without > any problem. > > According to the changelogs on kernel.org there were several changes to > amdgpu in versions > 5.10.141, 5.10.143, 5.10.144 5.10.146 and 5.10.148. > > Some extract from my /var/log/messages just in case it is of any help: > > Oct 19 07:05:24 omikron kernel: [0.00] Linux version 5.10.0-19-amd64 > (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, > GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-1 (2022-10-17) > Oct 19 07:05:24 omikron kernel: [0.00] Command line: > BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 > root=UUID=28af0276-7bd6-468f-b9c9-c743233a9468 ro quiet mem_encrypt=off > snd_hda_intel.power_save=0 > ... > Oct 19 07:05:24 omikron kernel: [2.325914] [drm] amdgpu kernel > modesetting enabled. > Oct 19 07:05:24 omikron kernel: [2.327288] amdgpu: Topology: Add APU node > [0x0:0x0] > Oct 19 07:05:24 omikron kernel: [2.327398] fb0: switching to amdgpudrmfb > from EFI VGA > Oct 19 07:05:24 omikron kernel: [2.328120] Console: switching to colour > dummy device 80x25 > Oct 19 07:05:24 omikron kernel: [2.328366] amdgpu :05:00.0: vgaarb: > deactivate vga console > Oct 19 07:05:24 omikron kernel: [2.328431] amdgpu :05:00.0: enabling > device (0006 -> 0007) > Oct 19 07:05:24 omikron kernel: [2.328516] [drm] initializing kernel > modesetting (RAVEN 0x1002:0x15DD 0x1002:0x15DD 0x83). > Oct 19 07:05:24 omikron kernel: [2.328519] amdgpu :05:00.0: amdgpu: > Trusted Memory Zone (TMZ) feature disabled as experimental (default) > Oct 19 07:05:24 omikron kernel: [2.328536] [drm] register mmio base: > 0xFE60 > Oct 19 07:05:24 omikron kernel: [2.328537] [drm] register mmio size: > 524288 > Oct 19 07:05:24 omikron kernel: [2.328559] [drm] add ip block number 0 > > Oct 19 07:05:24 omikron kernel: [2.328561] [drm] add ip block number 1 > > Oct 19 07:05:24 omikron kernel: [2.328562] [drm] add ip block number 2 > > Oct 19 07:05:24 omikron kernel: [2.328564] [drm] add ip block number 3 > > Oct 19 07:05:24 omikron kernel: [2.328565] [drm] add ip block number 4 > > Oct 19 07:05:24 omikron kernel: [2.328567] [drm] add ip block number 5 > > Oct 19 07:05:24 omikron kernel: [2.328568] [drm] add ip block number 6 > > Oct 19 07:05:24 omikron kernel: [2.328570] [drm] add ip block number 7 > > Oct 19 07:05:24 omikron kernel: [2.328571] [drm] add ip block number 8 > > Oct 19 07:05:24 omikron kernel: [2.333054] input: HD-Audio Generic > HDMI/DP,pcm=3 as > /devices/pci:00/:00:08.1/:05:00.1/sound/card0/input6 > Oct 19 07:05:24 omikron kernel: [2.334135] amdgpu :05:00.0: firmware: > direct-loading firmware amdgpu/raven_gpu_info.bin > Oct 19 07:05:24 omikron kernel: [2.334155] amdgpu :05:00.0: amdgpu: > Fetched VBIOS from VFCT > Oct 19 07:05:24 omikron kernel: [2.334157] amdgpu: ATOM BIOS: > 113-RAVEN-113 > Oct 19 07:05:24 omikron kernel: [2.334462] amdgpu :05:00.0: firmware: > direct-loading firmware amdgpu/raven_sdma.bin > Oct 19 07:05:24 omikron kernel: [2.334469] [drm] VCN decode is enabled in > VM mode > Oct 19 07:05:24 omikron kernel: [2.334470] [drm] VCN encode is enabled in > VM mode > Oct 19 07:05:24 omikron kernel: [2.334471] [drm] JPEG decode is enabled > in VM mode > Oct 19 07:05:24 omikron kernel: [2.334527] [drm] vm size is 262144 GB, 4 > levels, block size is 9-bit, fragment size is 9-bit > Oct 19 07:05:24 omikron kernel: [2.334539] amdgpu :05:00.0: amdgpu: > VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used) > Oct 19 07:05:24 omikron kernel: [2.334541] amdgpu :05:00.0: amdgpu: > GART: 1024M 0x - 0x3FFF > Oct 19 07:05:24 omikron kernel: [2.334543] amdgpu :05:00.0: amdgpu: > AGP: 267419648M 0x00F8 - 0x > Oct 19 07:05:24 omikron kernel: [2.334551] [drm] Detected VRAM RAM=2048M, > BAR=2048M > Oct 19 07:05:24 omikron kernel: [2.334552] [drm] RAM width 128bits DDR4 > Oct 19 07:05:24 omikron kernel: [2.334618] [TTM] Zone kernel: Available > graphics memory: 15381802 KiB > Oct 19 07:05:24 omikron kernel: [2.334620] [TTM] Zone dma32: Available > graphics memory: 2097152 KiB > Oct 19 07:05:24 omikron kernel: [2.334621] [TTM] Initializing pool > allocator > Oct 19 07:05:24 omikron kernel: [2.334626] [TTM] Initializing DMA pool > allocator > Oct 19 07:05:24 omikron kernel: [2.334738] [drm] amdgpu: 2048M of VRAM > memory ready > Oct 19 07:05:24 omikron kernel: [2.334741] [drm] amdgpu: 3072M of GTT > memory ready. > Oct 19 07:05:24 omikron
Processed: Re: Bug#1022025: fails to boot on machines with AMD integrated graphics
Processing control commands: > tags -1 + moreinfo Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Ignoring request to alter tags of bug #1022025 to the same tags previously set Ignoring request to alter tags of bug #1022042 to the same tags previously set -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Dear Maintainer, i can confirm the problem. All of our notebooks with integrated AMD graphics (CPU: AMD Ryzen 7 PRO 4750U with Radeon Graphics) are affected and don't boot anymore. During boot the following error-messages appear: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out. [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:62:crtc-0] flip_done timed out. [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:52:plane-3] flip_done timed out. 5.10.0-18 boots without problems. Best Regards, Arndt Kaiser
Processed: Re: Bug#1022025: fails to boot on machines with AMD integrated graphics
Processing control commands: > tags -1 + moreinfo Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Added tag(s) moreinfo. Added tag(s) moreinfo. -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1022025 is important, tagging 1022025, forcibly merging 1022025 1022042
Processing commands for cont...@bugs.debian.org: > severity 1022025 important Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Severity set to 'important' from 'normal' > tags 1022025 + upstream Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Added tag(s) upstream. > forcemerge 1022025 1022042 Bug #1022025 [src:linux] Can't enable amdgpu driver in linux-image-5.10.0-19-amd64 Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Added tag(s) upstream. Merged 1022025 1022042 > thanks Stopping processing here. Please contact me if you need assistance. -- 1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025 1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022042: (No Subject)
Here is a reddit link with information from another user that is experiencing the same issue. They've reprinted the errors I referred to in the original bug report. https://www.reddit.com/r/debian/comments/y7t4bv/cant_boot_on_stable_bullseye_after_kernel_update/
Processed: reassign 1022042 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1022042 src:linux 5.10.149-1 Bug #1022042 [linux-image-amd64] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/5.10.149+1. Ignoring request to alter fixed versions of bug #1022042 to the same values previously set Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics Marked as found in versions linux/5.10.149-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Package: linux-image-amd64 Version: 5.10.149-1 Severity: important X-Debbugs-Cc: autop...@protonmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded to the latest security kernel on Stable (5.10.0-19). After upgrading, I rebooted. * What exactly did you do (or not do) that was effective (or ineffective)? Only thing that works to get 5.10.0-19 booting is to not have integrated AMD graphics. My other nvidia machine upgraded just fine. Disabling modesetting did not resolve the issue. * What was the outcome of this action? Computer gets past GRUB, attempts to boot, and then hangs on a black screen. After about 30 seconds, some error messages are spat out regarding DRM and "flip_done timed out" * What outcome did you expect instead? I expected the machine to boot normally. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-18-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-amd64 depends on: ii linux-image-5.10.0-19-amd64 5.10.149-1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information
Bug#1021905: marked as done (linux-image-6.0.0-trunk-amd64: fails to return from suspend)
Your message dated Wed, 19 Oct 2022 13:05:09 +0200 with message-id <1908902.e8pJXLqx7t@prancing-pony> and subject line Re: Bug#1021905: linux-image-6.0.0-trunk-amd64: fails to return from suspend has caused the Debian Bug report #1021905, regarding linux-image-6.0.0-trunk-amd64: fails to return from suspend to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1021905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-6.0.0-trunk-amd64 Version: 6.0-1~exp1 Severity: normal X-Debbugs-Cc: frc.gabr...@gmail.com Dear Maintainer, when using linux-image-6.0.0-trunk-amd64 I noticed that my computer does not return from suspend and checking the logs I found these lines: Oct 15 15:30:20 computer kernel: [ 209.936495] BUG: unable to handle page fault for address: 110e1680 Oct 15 15:30:20 computer kernel: [ 209.936507] #PF: supervisor read access in kernel mode Oct 15 15:30:20 computer kernel: [ 209.936513] #PF: error_code(0x) - not-present page Oct 15 15:30:20 computer kernel: [ 209.936517] PGD 0 P4D 0 Oct 15 15:30:20 computer kernel: [ 209.936521] Oops: [#1] PREEMPT SMP NOPTI Oct 15 15:30:20 computer kernel: [ 209.936526] CPU: 12 PID: 1271 Comm: krfcommd Not tainted 6.0.0-trunk-amd64 #1 Debian 6.0-1~exp1 Oct 15 15:30:20 computer kernel: [ 209.936532] Hardware name: LENOVO 21A4GE/21A4GE, BIOS R1MET49W (1.19 ) 06/27/2022 Oct 15 15:30:20 computer kernel: [ 209.936534] RIP: 0010:hci_send_acl+0x21/0x2f0 [bluetooth] Oct 15 15:30:20 computer kernel: [ 209.936588] Code: cc cc 0f 1f 80 00 00 00 00 0f 1f 44 00 00 41 57 49 89 ff 41 56 41 55 41 54 55 48 89 f5 53 48 83 ec 28 4c 8b 67 18 89 54 24 0c <4d> 8b 8c 24 80 06 00 00 4c 89 4c 24 18 66 90 0f b7 da 8b 4d 70 2b Oct 15 15:30:20 computer kernel: [ 209.936592] RSP: 0018:af6d4c31bc30 EFLAGS: 00010286 Oct 15 15:30:20 computer kernel: [ 209.936596] RAX: 8ed64afe2000 RBX: 0004 RCX: Oct 15 15:30:20 computer kernel: [ 209.936599] RDX: 0002 RSI: 8ed647a69500 RDI: 8ed691757600 Oct 15 15:30:20 computer kernel: [ 209.936601] RBP: 8ed647a69500 R08: 8ed6461b3ec0 R09: 000c Oct 15 15:30:20 computer kernel: [ 209.936603] R10: 0001 R11: 000c R12: 110e1000 Oct 15 15:30:20 computer kernel: [ 209.936605] R13: af6d4c31bd78 R14: 8ed647a69500 R15: 8ed691757600 Oct 15 15:30:20 computer kernel: [ 209.936608] FS: () GS:8edc5210() knlGS: Oct 15 15:30:20 computer kernel: [ 209.936611] CS: 0010 DS: ES: CR0: 80050033 Oct 15 15:30:20 computer kernel: [ 209.936614] CR2: 110e1680 CR3: 00055381 CR4: 00750ee0 Oct 15 15:30:20 computer kernel: [ 209.936617] PKRU: 5554 Oct 15 15:30:20 computer kernel: [ 209.936619] Call Trace: Oct 15 15:30:20 computer kernel: [ 209.936623] Oct 15 15:30:20 computer kernel: [ 209.936626] ? mutex_lock+0xe/0x30 Oct 15 15:30:20 computer kernel: [ 209.936637] l2cap_chan_send+0x12f/0xc60 [bluetooth] Oct 15 15:30:20 computer kernel: [ 209.936691] ? remove_wait_queue+0x20/0x60 Oct 15 15:30:20 computer kernel: [ 209.936698] ? _raw_spin_unlock_irqrestore+0x23/0x40 Oct 15 15:30:20 computer kernel: [ 209.936703] ? preempt_count_add+0x6a/0xa0 Oct 15 15:30:20 computer kernel: [ 209.936710] l2cap_sock_sendmsg+0x9a/0x100 [bluetooth] Oct 15 15:30:20 computer kernel: [ 209.936759] sock_sendmsg+0x5f/0x70 Oct 15 15:30:20 computer kernel: [ 209.936767] rfcomm_send_frame+0x62/0xa0 [rfcomm] Oct 15 15:30:20 computer kernel: [ 209.936778] rfcomm_send_disc.isra.0+0x80/0xd0 [rfcomm] Oct 15 15:30:20 computer kernel: [ 209.936787] __rfcomm_dlc_disconn+0x10a/0x120 [rfcomm] Oct 15 15:30:20 computer kernel: [ 209.936796] __rfcomm_dlc_close+0x60/0x200 [rfcomm] Oct 15 15:30:20 computer kernel: [ 209.936805] rfcomm_run+0x6f6/0x1900 [rfcomm] Oct 15 15:30:20 computer kernel: [ 209.936815] ? _raw_spin_rq_lock_irqsave+0x20/0x20 Oct 15 15:30:20 computer kernel: [ 209.936822] ? rfcomm_check_accept+0xa0/0xa0 [rfcomm] Oct 15 15:30:20 computer kernel: [ 209.936830] kthread+0xe9/0x110 Oct 15 15:30:20 computer kernel: [ 209.936836] ? kthread_complete_and_exit+0x20/0x20 Oct 15 15:30:20 computer kernel: [ 209.936840] ret_from_fork+0x22/0x30 Oct 15 15:30:20 computer kernel: [ 209.936849] Oct 15 15:30:20 computer kernel: [ 209.936851] Modules linked in: ehci_pci ipmi_devintf ehci_hcd ipmi_msghandler
Processed: Re: Bug#1021905: linux-image-6.0.0-trunk-amd64: fails to return from suspend
Processing commands for cont...@bugs.debian.org: > reassign 1021905 src:linux 6.0-1~exp1 Bug #1021905 [linux-image-6.0.0-trunk-amd64] linux-image-6.0.0-trunk-amd64: fails to return from suspend Warning: Unknown package 'linux-image-6.0.0-trunk-amd64' Bug reassigned from package 'linux-image-6.0.0-trunk-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.0+1~exp1. Ignoring request to alter fixed versions of bug #1021905 to the same values previously set Bug #1021905 [src:linux] linux-image-6.0.0-trunk-amd64: fails to return from suspend Marked as found in versions linux/6.0-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019424: linux-image-5.19.0-1-amd64: endless loop at poweroff/reboot with "block device autoloading is deprecated and will be removed"
On woensdag 19 oktober 2022 11:48:22 CEST Roderich Schupp wrote: > The problem has gone away in linux 6.0.2-1, apparently fixed by > 4c66a326b5ab784cddd72de07ac5b6210e9e1b06 Revert "block: freeze the > queue earlier in del_gendisk" > so for my case you may close this bug. Francesco, is the bug fixed for you too with 6.0.2-1? signature.asc Description: This is a digitally signed message part.
Bug#1019424: me too
On Fri, 9 Sep 2022 14:21:50 +0200 Roderich Schupp wrote: > Same here (complete system info below), TL;DR: > > kernel 5.19.0-1-686 > system is using md raid: > > $ cat proc/mdstat > Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [multipath] > [raid0] [raid10] > md1 : active raid5 sda3[3] sdc3[2] sdb3[1] > 2926059520 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] > [UUU] > > md0 : active raid1 sdc2[2] sdb2[1] sda2[3] > 101544 blocks super 1.2 [3/3] [UUU] The problem has gone away in linux 6.0.2-1, apparently fixed by 4c66a326b5ab784cddd72de07ac5b6210e9e1b06 Revert "block: freeze the queue earlier in del_gendisk" so for my case you may close this bug. Cheers, Roderich
Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others)
Chris Hofstaedtler writes: > * Diederik de Haas [221019 00:07]: >> On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote: >> > it appears quite some new btusb hardware was released recently. >> > linux-next has a lot of simple "Add xyz ID" patches for btusb.c: >> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/driv >> > ers/bluetooth/btusb.c >> > >> > Please consider applying 57117d7234dadfba2a83615b2a9369f6f2f9914f >> > and/or the other patches adding new hwids to btusb.c for the >> > bookworm kernel. >> >> It's already part of Linux 6.1-rc1 and it is expected that 6.1 will be the >> next LTS release and I'd guess thus also the Bookworm kernel. >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/bluetooth?h=v6.1-rc1 > > Right, that'd be good. I've manually applied > 57117d7234dadfba2a83615b2a9369f6f2f9914f against 5.9.11-1, and that > works for me; but only after making available > BT_RAM_CODE_MT7922_1_1_hdr.bin from linux-firmware.git. If this is a simple device ID addition without any other dependencies, then it qualifies for Linux stable. And you'll get it in Debian stable for free. New device ID patches are regularily backported to the maintained stable kernels, and usually picked up automatically by the stable maintainers. You can request a backport of a specific commit in mainline by sending an email to sta...@vger.kernel.org See https://docs.kernel.org/process/stable-kernel-rules.html Bjørn
Bug#1022025: Same here
Same problem here. Kernel version 5.10.149-1 (linux-image-5.10.0-19-amd64) hangs on initialisation of amdgpu driver, while version 5.10.140-1 (linux-image-5.10.0-18-amd64) boots without any problem. According to the changelogs on kernel.org there were several changes to amdgpu in versions 5.10.141, 5.10.143, 5.10.144 5.10.146 and 5.10.148. Some extract from my /var/log/messages just in case it is of any help: Oct 19 07:05:24 omikron kernel: [0.00] Linux version 5.10.0-19-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-1 (2022-10-17) Oct 19 07:05:24 omikron kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 root=UUID=28af0276-7bd6-468f-b9c9-c743233a9468 ro quiet mem_encrypt=off snd_hda_intel.power_save=0 ... Oct 19 07:05:24 omikron kernel: [2.325914] [drm] amdgpu kernel modesetting enabled. Oct 19 07:05:24 omikron kernel: [2.327288] amdgpu: Topology: Add APU node [0x0:0x0] Oct 19 07:05:24 omikron kernel: [2.327398] fb0: switching to amdgpudrmfb from EFI VGA Oct 19 07:05:24 omikron kernel: [2.328120] Console: switching to colour dummy device 80x25 Oct 19 07:05:24 omikron kernel: [2.328366] amdgpu :05:00.0: vgaarb: deactivate vga console Oct 19 07:05:24 omikron kernel: [2.328431] amdgpu :05:00.0: enabling device (0006 -> 0007) Oct 19 07:05:24 omikron kernel: [2.328516] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1002:0x15DD 0x83). Oct 19 07:05:24 omikron kernel: [2.328519] amdgpu :05:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) Oct 19 07:05:24 omikron kernel: [2.328536] [drm] register mmio base: 0xFE60 Oct 19 07:05:24 omikron kernel: [2.328537] [drm] register mmio size: 524288 Oct 19 07:05:24 omikron kernel: [2.328559] [drm] add ip block number 0 Oct 19 07:05:24 omikron kernel: [2.328561] [drm] add ip block number 1 Oct 19 07:05:24 omikron kernel: [2.328562] [drm] add ip block number 2 Oct 19 07:05:24 omikron kernel: [2.328564] [drm] add ip block number 3 Oct 19 07:05:24 omikron kernel: [2.328565] [drm] add ip block number 4 Oct 19 07:05:24 omikron kernel: [2.328567] [drm] add ip block number 5 Oct 19 07:05:24 omikron kernel: [2.328568] [drm] add ip block number 6 Oct 19 07:05:24 omikron kernel: [2.328570] [drm] add ip block number 7 Oct 19 07:05:24 omikron kernel: [2.328571] [drm] add ip block number 8 Oct 19 07:05:24 omikron kernel: [2.333054] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci:00/:00:08.1/:05:00.1/sound/card0/input6 Oct 19 07:05:24 omikron kernel: [2.334135] amdgpu :05:00.0: firmware: direct-loading firmware amdgpu/raven_gpu_info.bin Oct 19 07:05:24 omikron kernel: [2.334155] amdgpu :05:00.0: amdgpu: Fetched VBIOS from VFCT Oct 19 07:05:24 omikron kernel: [2.334157] amdgpu: ATOM BIOS: 113-RAVEN-113 Oct 19 07:05:24 omikron kernel: [2.334462] amdgpu :05:00.0: firmware: direct-loading firmware amdgpu/raven_sdma.bin Oct 19 07:05:24 omikron kernel: [2.334469] [drm] VCN decode is enabled in VM mode Oct 19 07:05:24 omikron kernel: [2.334470] [drm] VCN encode is enabled in VM mode Oct 19 07:05:24 omikron kernel: [2.334471] [drm] JPEG decode is enabled in VM mode Oct 19 07:05:24 omikron kernel: [2.334527] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit Oct 19 07:05:24 omikron kernel: [2.334539] amdgpu :05:00.0: amdgpu: VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used) Oct 19 07:05:24 omikron kernel: [2.334541] amdgpu :05:00.0: amdgpu: GART: 1024M 0x - 0x3FFF Oct 19 07:05:24 omikron kernel: [2.334543] amdgpu :05:00.0: amdgpu: AGP: 267419648M 0x00F8 - 0x Oct 19 07:05:24 omikron kernel: [2.334551] [drm] Detected VRAM RAM=2048M, BAR=2048M Oct 19 07:05:24 omikron kernel: [2.334552] [drm] RAM width 128bits DDR4 Oct 19 07:05:24 omikron kernel: [2.334618] [TTM] Zone kernel: Available graphics memory: 15381802 KiB Oct 19 07:05:24 omikron kernel: [2.334620] [TTM] Zone dma32: Available graphics memory: 2097152 KiB Oct 19 07:05:24 omikron kernel: [2.334621] [TTM] Initializing pool allocator Oct 19 07:05:24 omikron kernel: [2.334626] [TTM] Initializing DMA pool allocator Oct 19 07:05:24 omikron kernel: [2.334738] [drm] amdgpu: 2048M of VRAM memory ready Oct 19 07:05:24 omikron kernel: [2.334741] [drm] amdgpu: 3072M of GTT memory ready. Oct 19 07:05:24 omikron kernel: [2.334744] [drm] GART: num cpu pages 262144, num gpu pages 262144 Oct 19 07:05:24 omikron kernel: [2.335166] [drm] PCIE GART of 1024M enabled (table at 0x00F40090). Oct 19 07:05:24 omikron kernel: [2.336034] amdgpu :05:00.0: firmware: direct-loading firmware
