Bug 2223090 - BUG: KASAN: slab-out-of-bounds in amdgpu_sw_ring_ib_mark_offset+0x2c1/0x2e0 [amdgpu]
Summary: BUG: KASAN: slab-out-of-bounds in amdgpu_sw_ring_ib_mark_offset+0x2c1/0x2e0 [...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-15 12:54 UTC by Andrew
Modified: 2023-07-15 12:55 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
full dmesg from 6.3.12-200.fc38.x86_64+debug (172.84 KB, text/plain)
2023-07-15 12:54 UTC, Andrew
no flags Details
full dmesg from 6.3.11-200.fc38.x86_64+debug (175.27 KB, text/plain)
2023-07-15 12:55 UTC, Andrew
no flags Details

Description Andrew 2023-07-15 12:54:43 UTC
Created attachment 1975915 [details]
full dmesg from 6.3.12-200.fc38.x86_64+debug

I have this on 6.3.12-200.fc38.x86_64+debug
Reproducible: seems always, immediately after inserting amdgpu module. Not tainted kernel.
Absent on 6.2.x, I believe.

See also:
https://bugzilla.redhat.com/show_bug.cgi?id=2212779
https://bugzilla.redhat.com/show_bug.cgi?id=2216874 (happens on another PC)

Besides that, got some FS corruption once, might be related as well:

  [25768.103735] EXT4-fs error (device dm-0): ext4_lookup:1851: inode #1967329: comm dnf: iget: checksum invalid
  [25768.103745] Aborting journal on device dm-0-8.
  [25768.103923] EXT4-fs error (device dm-0): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journal
  [25768.104959] EXT4-fs (dm-0): Remounting filesystem read-only

Comment 1 Andrew 2023-07-15 12:55:38 UTC
Created attachment 1975916 [details]
full dmesg from 6.3.11-200.fc38.x86_64+debug


Note You need to log in before you can comment on or make changes to this bug.