XPost: linux.debian.bugs.dist 
 From: carnil@debian.org 
  
 Control: tags -1 + moreinfo 
  
 Hi, 
  
 On Tue, Sep 23, 2025 at 05:59:30PM +0000, Antwerpen, G. (Gert) van wrote: 
 > Package: linux-image-amd64 
 > Version: 6.12.0-1 (also reproducible with 6.16.3-1~bpo13+1) 
 > Severity: important 
 > Tags: upstream, regression 
 > 
 > Summary: 
 > Kernel oops / crash when running rsync on MSI X99A SLI PLUS (MS-7885). 
 > System was stable for years with Debian stable kernel 6.1.x. 
 > The problem only appears after upgrading to Trixie (kernel 6.12 and newer). 
 > 
 > System information: 
 > - Machine: MSI X99A SLI PLUS (MS-7885) 
 > - BIOS: 1.D0 (07/15/2016) 
 > - CPU: Intel Xeon (Haswell-E, socket 2011-3) 
 > - RAM: [please fill in, e.g. 64 GB DDR4 ECC/non-ECC] 
 > - Debian version: Trixie (testing) 
 > - Kernel versions tested: 
 >   - 6.1.x (Debian bookworm stable) €€€ works fine 
 >   - 6.12.0-1 (Debian Trixie) €€€ oops/crash 
 >   - 6.16.3-1~bpo13+1 (Debian Trixie backports) €€€ oops/crash 
 > 
 > Kernel log excerpt: 
 > BUG: unable to handle page fault for address: ffffffaabfe73e00 
 > #PF: supervisor instruction fetch in kernel mode 
 > #PF: error_code(0x0010) - not-present page 
 > PGD 1de231067 P4D 1de231067 PUD 0 
 > Oops: 0010 [#2] SMP PTI 
 > CPU: 9 UID: 40001 PID: 230866 Comm: rsync Tainted: G      D 
 6.16.3+deb13-amd64 #1 PREEMPT(lazy)  Debian 6.16.3-1~bpo13+1 
 > Hardware name: MSI MS-7885/X99A SLI PLUS(MS-7885), BIOS 1.D0 07/15/2016 
 > RIP: 0010:0xffffffaabfe73e00 
 > Code: Unable to access opcode bytes at 0xffffffaabfe73dd6. 
 > Call Trace: 
 >  filemap_readahead.isra.0+0x75/0xb0 
 >  filemap_get_pages+0x3ed/0x770 
 >  sock_write_iter+0x18e/0x1a0 
 >  ... 
 >  note: rsync[230866] exited with irqs disabled 
 > 
 > (Full logs can be provided if required.) 
 > 
 > Steps to reproduce: 
 > 1. Run rsync on large data sets (local disk to remote). 
 > 2. After some time, system crashes with kernel oops (see logs above). 
 > 3. Always reproducible on kernel >= 6.12, never seen on 6.1. 
 > 
 > Expected result: 
 > No kernel oops €€€ rsync should run reliably. 
 > 
 > Actual result: 
 > Kernel crashes with page fault in kernel mode, requiring system restart. 
 > 
 > Additional notes: 
 > - Hardware tested with memtest86+ (no errors). 
 > - No overclocking. 
 > - Issue seems to be a regression introduced in Linux 6.12. 
 > - Possibly related to filesystem or networking modules, but exact trigger 
 unknown. 
  
 Can you please provide full kernel logs of the problem happening. If 
 you do not get access to the machine after oops'ing the you might 
 attach a netconsole to get the relevant logs. 
  
 Additionally to the logs ideally you provide all the meta information 
 collected by running reportbug's bugscripts for the kernel reports. 
  
 As for the regreesion itself and identify the breaking commit: Can you 
 bisect the upstream changes. Ideallally you first can range bit closer 
 the upstream versions where it is regressing. You can use for that the 
 snapshot.debian.org service to fetch older linux-image versions. Once 
 you have  close enough range, then bisect the upstream changes (would 
 you need help and have instructions to do that?). 
  
 > -- This message may contain information that is not intended for you. If 
 you 
 are not the addressee or if this message was sent to you by mistake, you are 
 requested to inform the sender and delete the message. TNO accepts no 
 liability for the content of 
 this e-mail, for the manner in which you use it and for damage of any kind 
 resulting from the risks inherent to the electronic transmission of 
 messages. 
  
 YOu might want to drop this when filling a public bugreport ;-) 
  
 Regards, 
 Salvatore 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)