Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #88827 > unrolled thread

Bug#1111184: linux: Kernel panic on boot with amdgpu driver

Started byRuslanSemchenko <uncleruc2075@gmail.com>
First post2025-08-15 12:50 +0200
Last post2025-09-24 06:00 +0200
Articles 7 — 3 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1111184: linux: Kernel panic on boot with amdgpu driver RuslanSemchenko <uncleruc2075@gmail.com> - 2025-08-15 12:50 +0200
    Processed: Re: Bug#1111184: linux: Kernel panic on boot with  amdgpu driver "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-08-15 22:10 +0200
    Bug#1111184: linux: Kernel panic on boot with amdgpu driver Salvatore Bonaccorso <carnil@debian.org> - 2025-08-15 22:10 +0200
    Processed: Re: Bug#1111184: linux: Kernel panic on boot with  amdgpu driver "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-08-20 09:20 +0200
    Bug#1111184: linux: Kernel panic on boot with amdgpu driver Salvatore Bonaccorso <carnil@debian.org> - 2025-09-06 13:40 +0200
    Bug#1111184: closing 1111184 Salvatore Bonaccorso <carnil@debian.org> - 2025-09-24 06:00 +0200
    Bug#1111184: linux: Kernel panic on boot with amdgpu driver Salvatore Bonaccorso <carnil@debian.org> - 2025-09-24 06:00 +0200

#88827 — Bug#1111184: linux: Kernel panic on boot with amdgpu driver

FromRuslanSemchenko <uncleruc2075@gmail.com>
Date2025-08-15 12:50 +0200
SubjectBug#1111184: linux: Kernel panic on boot with amdgpu driver
Message-ID<Lk0at-7Myp-1@gated-at.bofh.it>
Source: linux
Version: 6.12.41+deb13-amd64
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: debian-amd64@lists.debian.org
User: debian-amd64@lists.debian.org
Usertags: amd64

Dear Maintainer,

After upgrading to Debian 13 (Trixie), the system fails to boot and crashes with a kernel panic related to the amdgpu driver. This issue was not present in Debian 12 (Bookworm).

Steps to reproduce:
1. Boot the system with the 6.12.41+deb13-amd64 kernel.
2. The kernel panic occurs during the boot process, before the graphical environment loads.

Expected behavior:
The system should boot normally and load the graphical environment without errors, as it did in Debian 12.

Actual behavior:
The system hangs with a kernel panic. The following lines are from the dmesg log:

[   40.387452] Modules linked in: amdgpu(+) amdxcp drm_exec gpu_sched drm_buddy crc16 hid_multitouch radeon hid_generic usbhid hid i2c_algo_bit drm_suballoc_helper ums_realtek sd_mod uas drm_display_helper usb_storage cec ahci rc_core libahci drm_ttm_helper ttm libata ohci_pci drm_kms_helper ehci_pci ehci_hcd drm ohci_hcd sp5100_tco scsi_mod watchdog usbcore i2c_piix4 serio_raw i2c_smbus scsi_common usb_common video battery wmi button
[   40.387553] CPU: 0 UID: 0 PID: 178 Comm: (udev-worker) Not tainted 6.12.41+deb13-amd64 #1  Debian 6.12.41-1
[   40.387565] Hardware name: acer ICONIA Tab W500/WT1, BIOS V1.14 08/12/2011
[   40.387570] RIP: 0010:find_kallsyms_symbol+0xcb/0x170
[   40.387595] Code: 9c 00 00 00 48 89 cd 41 89 d4 0f 1f 44 00 00 83 c2 01 48 83 c0 18 39 d7 74 32 66 83 78 06 00 74 ee 8b 08 49 03 48 10 0f b6 31 <40> 84 f6 74 e0 40 80 fe 2e 74 4c 40 80 fe 4c 74 ad 40 80 fe 24 75
[   40.387603] RSP: 0018:ffffc095c046b708 EFLAGS: 00000286
[   40.387611] RAX: ffffffffc1b2b6a8 RBX: ffffffffc0ffd340 RCX: ffffffffc1bdb365
[   40.387617] RDX: 0000000000009b9c RSI: 0000000000000075 RDI: 000000000000b453
[   40.387622] RBP: ffffffffc0ffd2f0 R08: ffffffffc1bf5b18 R09: ffffffffc0ffd2f4
[   40.387626] R10: 0000000000000000 R11: ffffc095c046b7a8 R12: 00000000000039c0
[   40.387631] R13: ffffc095c046b7b6 R14: 0000000000000000 R15: 0000000000000000
[   40.387637] FS:  00007fc0c4a66980(0000) GS:ffff99f1a4e00000(0000) knlGS:0000000000000000
[   40.387644] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   40.387649] CR2: 000055f5c141e858 CR3: 0000000001928000 CR4: 00000000000006f0
[   40.387655] Call Trace:
[   40.387662]  <TASK>
[   40.387670]  ? dc_clock_type_to_atom+0x4/0x50 [amdgpu]
[   40.393568]  module_address_lookup+0x5f/0xb0
[   40.393590]  ? dc_clock_type_to_atom+0x4/0x50 [amdgpu]
[   40.399419]  kallsyms_lookup_buildid+0xbb/0x120
[   40.399439]  kallsyms_lookup+0x18/0x30
[   40.399449]  test_for_valid_rec+0x64/0xb0
[   40.399476]  ftrace_module_enable+0x1d3/0x320
[   40.399487]  load_module+0x1915/0x1d60
[   40.399509]  ? init_module_from_file+0x89/0xe0
[   40.399519]  init_module_from_file+0x89/0xe0
[   40.399533]  idempotent_init_module+0x11e/0x310
[   40.399546]  __x64_sys_finit_module+0x5e/0xb0
[   40.399557]  do_syscall_64+0x82/0x190
[   40.399576]  ? __pfx_page_put_link+0x10/0x10
[   40.399591]  ? do_sys_openat2+0x9c/0xe0
[   40.399602]  ? syscall_exit_to_user_mode+0x4d/0x210
[   40.399619]  ? do_syscall_64+0x8e/0x190
[   40.399629]  ? do_syscall_64+0x8e/0x190
[   40.399638]  ? exc_page_fault+0x7e/0x180
[   40.399648]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[   40.399666] RIP: 0033:0x7fc0c55c2779
[   40.399677] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 4f 86 0d 00 f7 d8 64 89 01 48
[   40.399684] RSP: 002b:00007ffd5b2abb08 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[   40.399692] RAX: ffffffffffffffda RBX: 000055f5c1440580 RCX: 00007fc0c55c2779
[   40.399697] RDX: 0000000000000004 RSI: 00007fc0c3d8844d RDI: 0000000000000026
[   40.399702] RBP: 0000000000000004 R08: 0000000000000000 R09: 000055f5c1419fd0
[   40.399707] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc0c3d8844d
[   40.399711] R13: 0000000000020000 R14: 000055f5c1440140 R15: 0000000000000000
[   40.399720]  </TASK>

-- System Information:
Debian Release: 13.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.41+deb13-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_SOFTLOCKUP
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

[toc] | [next] | [standalone]

#88838 — Processed: Re: Bug#1111184: linux: Kernel panic on boot with amdgpu driver

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-08-15 22:10 +0200
SubjectProcessed: Re: Bug#1111184: linux: Kernel panic on boot with amdgpu driver
Message-ID<Lk8Up-7SLQ-11@gated-at.bofh.it>
In reply to#88827
Processing control commands:

> tags -1 + moreinfo
Bug #1111184 [src:linux] linux: Kernel panic on boot with amdgpu driver
Added tag(s) moreinfo.

-- 
1111184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111184
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#88839

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-08-15 22:10 +0200
Message-ID<Lk8Up-7SLQ-1@gated-at.bofh.it>
In reply to#88827
Control: tags -1 + moreinfo

On Fri, Aug 15, 2025 at 01:43:12PM +0300, RuslanSemchenko wrote:
> Source: linux
> Version: 6.12.41+deb13-amd64
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> X-Debbugs-Cc: debian-amd64@lists.debian.org
> User: debian-amd64@lists.debian.org
> Usertags: amd64
> 
> Dear Maintainer,
> 
> After upgrading to Debian 13 (Trixie), the system fails to boot and crashes with a kernel panic related to the amdgpu driver. This issue was not present in Debian 12 (Bookworm).
> 
> Steps to reproduce:
> 1. Boot the system with the 6.12.41+deb13-amd64 kernel.
> 2. The kernel panic occurs during the boot process, before the graphical environment loads.
> 
> Expected behavior:
> The system should boot normally and load the graphical environment without errors, as it did in Debian 12.
> 
> Actual behavior:
> The system hangs with a kernel panic. The following lines are from the dmesg log:
> 
> [   40.387452] Modules linked in: amdgpu(+) amdxcp drm_exec gpu_sched drm_buddy crc16 hid_multitouch radeon hid_generic usbhid hid i2c_algo_bit drm_suballoc_helper ums_realtek sd_mod uas drm_display_helper usb_storage cec ahci rc_core libahci drm_ttm_helper ttm libata ohci_pci drm_kms_helper ehci_pci ehci_hcd drm ohci_hcd sp5100_tco scsi_mod watchdog usbcore i2c_piix4 serio_raw i2c_smbus scsi_common usb_common video battery wmi button
> [   40.387553] CPU: 0 UID: 0 PID: 178 Comm: (udev-worker) Not tainted 6.12.41+deb13-amd64 #1  Debian 6.12.41-1
> [   40.387565] Hardware name: acer ICONIA Tab W500/WT1, BIOS V1.14 08/12/2011
> [   40.387570] RIP: 0010:find_kallsyms_symbol+0xcb/0x170
> [   40.387595] Code: 9c 00 00 00 48 89 cd 41 89 d4 0f 1f 44 00 00 83 c2 01 48 83 c0 18 39 d7 74 32 66 83 78 06 00 74 ee 8b 08 49 03 48 10 0f b6 31 <40> 84 f6 74 e0 40 80 fe 2e 74 4c 40 80 fe 4c 74 ad 40 80 fe 24 75
> [   40.387603] RSP: 0018:ffffc095c046b708 EFLAGS: 00000286
> [   40.387611] RAX: ffffffffc1b2b6a8 RBX: ffffffffc0ffd340 RCX: ffffffffc1bdb365
> [   40.387617] RDX: 0000000000009b9c RSI: 0000000000000075 RDI: 000000000000b453
> [   40.387622] RBP: ffffffffc0ffd2f0 R08: ffffffffc1bf5b18 R09: ffffffffc0ffd2f4
> [   40.387626] R10: 0000000000000000 R11: ffffc095c046b7a8 R12: 00000000000039c0
> [   40.387631] R13: ffffc095c046b7b6 R14: 0000000000000000 R15: 0000000000000000
> [   40.387637] FS:  00007fc0c4a66980(0000) GS:ffff99f1a4e00000(0000) knlGS:0000000000000000
> [   40.387644] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [   40.387649] CR2: 000055f5c141e858 CR3: 0000000001928000 CR4: 00000000000006f0
> [   40.387655] Call Trace:
> [   40.387662]  <TASK>
> [   40.387670]  ? dc_clock_type_to_atom+0x4/0x50 [amdgpu]
> [   40.393568]  module_address_lookup+0x5f/0xb0
> [   40.393590]  ? dc_clock_type_to_atom+0x4/0x50 [amdgpu]
> [   40.399419]  kallsyms_lookup_buildid+0xbb/0x120
> [   40.399439]  kallsyms_lookup+0x18/0x30
> [   40.399449]  test_for_valid_rec+0x64/0xb0
> [   40.399476]  ftrace_module_enable+0x1d3/0x320
> [   40.399487]  load_module+0x1915/0x1d60
> [   40.399509]  ? init_module_from_file+0x89/0xe0
> [   40.399519]  init_module_from_file+0x89/0xe0
> [   40.399533]  idempotent_init_module+0x11e/0x310
> [   40.399546]  __x64_sys_finit_module+0x5e/0xb0
> [   40.399557]  do_syscall_64+0x82/0x190
> [   40.399576]  ? __pfx_page_put_link+0x10/0x10
> [   40.399591]  ? do_sys_openat2+0x9c/0xe0
> [   40.399602]  ? syscall_exit_to_user_mode+0x4d/0x210
> [   40.399619]  ? do_syscall_64+0x8e/0x190
> [   40.399629]  ? do_syscall_64+0x8e/0x190
> [   40.399638]  ? exc_page_fault+0x7e/0x180
> [   40.399648]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
> [   40.399666] RIP: 0033:0x7fc0c55c2779
> [   40.399677] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 4f 86 0d 00 f7 d8 64 89 01 48
> [   40.399684] RSP: 002b:00007ffd5b2abb08 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
> [   40.399692] RAX: ffffffffffffffda RBX: 000055f5c1440580 RCX: 00007fc0c55c2779
> [   40.399697] RDX: 0000000000000004 RSI: 00007fc0c3d8844d RDI: 0000000000000026
> [   40.399702] RBP: 0000000000000004 R08: 0000000000000000 R09: 000055f5c1419fd0
> [   40.399707] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc0c3d8844d
> [   40.399711] R13: 0000000000020000 R14: 000055f5c1440140 R15: 0000000000000000
> [   40.399720]  </TASK>

Since there are several amdgpu related issues, it is right now not
clear if this one is a duplicate of those. Thus:

If the system is still repsonsive, could you gather please the *full*
kernel log and post it here for further analysis (e.g. if you can
login via SSH).

If the system is not responding, can you please attach it to a
netconsole. Instructions are in
https://www.kernel.org/doc/html/latest/networking/netconsole.html#netconsole
.

The 'netconsole' Debian package might be helpful as well to setup the
netconsole part. 

Once you have the netcosole working, please retrigger the issue and
provide the full log dumped over the netconsole.

Ideally please as well test the current experimental version to see if
the issue is as well present in mainline.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#88933 — Processed: Re: Bug#1111184: linux: Kernel panic on boot with amdgpu driver

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-08-20 09:20 +0200
SubjectProcessed: Re: Bug#1111184: linux: Kernel panic on boot with amdgpu driver
Message-ID<LlLgZ-8XHf-1@gated-at.bofh.it>
In reply to#88827
Processing control commands:

> tag -1 + moreinfo
Bug #1111184 [src:linux] linux: Kernel panic on boot with amdgpu driver
Added tag(s) moreinfo.

-- 
1111184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111184
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#89088

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-09-06 13:40 +0200
Message-ID<LrZqY-deSX-63@gated-at.bofh.it>
In reply to#88827
Control: tags -1 + moreinfo

Hi,

On Mon, Aug 25, 2025 at 12:15:02AM +0300, Руслан Семченко wrote:
> Hello, Salvatore. I have completed the tests as requested. I can
> confirm that the 6.13.2-1~exp1 kernel is GOOD, while the
> 6.13~rc7-1~exp1 kernel is BAD.

Thanks, that is good so we have a good range of version narrow enough
to start now the bisect. Here is what you can do next (I updated the
arlier instructions with the now concrete numbers, important is to
redefine the "bisection" terms and then carefully at each step say if
it is "fixed" or "broken");

	git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
        cd linux-stable
        git checkout v6.13.2
	cp /boot/config-$(uname -r) .config
	yes '' | make localmodconfig
	make savedefconfig
	mv defconfig arch/x86/configs/my_defconfig

        # test 6.13.2 to ensure this is "good"
        make my_defconfig
        make -j $(nproc) bindeb-pkg
        ... install the resulting .deb package and confirm it successfully boots / problem does not exist

        # test 6.13~rc7 to ensure this is "bad"
        git checkout v6.13-rc7
        make my_defconfig
        make -j $(nproc) bindeb-pkg
        ... install the resulting .deb package and confirm it fails to boot / problem exists

Once it is confirmed that this affects so as well the version ranges
upstream, we can proceed:

	git bisect start --term-new=fixed --term-old=broken
	git bisect fixed v6.13.2
	git bisect broken v6.13-rc7

(note this is important, as usually git bisect "direction" is to
determine a breaking commit, but here we want to identify a fixing
commit and so the git bisect terms are redifinied to not always have
to "flip" mentally the meaning of bad and good).

In each bisection step git checks out a state between the oldest
known-bad and the newest known-good commit. In each step test using:
 
        make my_defconfig
        make -j $(nproc) bindeb-pkg
        ... install, try to boot / verify if problem exists

and if the problem is hit run:
 
        git bisect broken

and if the problem doesn't trigger run:
 
        git bisect fixed

. Please pay attention to always select the just built kernel for
booting, it won't always be the default kernel picked up by grub.
 
Iterate until git announces to have identified the first 'fixed'
commit.

Then provide the output of
 
        git bisect log
 
In the course of the bisection you might have to uninstall previous
kernels again to not exhaust the disk space in /boot. Also in the end
uninstall all self-built kernels again.

Is this all of enough help for you?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#89383 — Bug#1111184: closing 1111184

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-09-24 06:00 +0200
SubjectBug#1111184: closing 1111184
Message-ID<LyoPD-7Ws-7@gated-at.bofh.it>
In reply to#88827
close 1111184 6.16.1-1~exp1
thanks

[toc] | [prev] | [next] | [standalone]

#89385

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-09-24 06:00 +0200
Message-ID<LyoPD-7Ws-1@gated-at.bofh.it>
In reply to#88827
Hi,

On Thu, Sep 11, 2025 at 09:33:35PM +0300, Руслан Семченко wrote:
> Hello Salvatore sorry for long response but i can't do bisection as
> you say because my disk is not be in good and my system specs maybe
> dont be good for bisect at this time maybe be another think how to
> find bug ?

Unfortunately in this case we will need someone else who is samewise
affected to do the bisection and track down the commit fixing the
issue in upper branches.

What do you mean with "disk is not good"? Do you have too little disk
space available for the compilation? (or to too slow?). Once you have
actually the more stripped down my_defconfig targeted for your system
things should be smooter.

If you still can do it, please come back to this bugreport. For now I
will mark the bug as well fixed in the upper version as we found, and
keep the moreinfo tag.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web