XPost: linux.debian.bugs.dist   
   From: eof@kiyuko.org   
      
   Source: linux   
   Version: 6.17.13-1   
   Severity: normal   
      
   I'm running testing on a Surface Go 2 tablet and things overall work   
   pretty nicely. I had installed stable originally, but later upgraded   
   primarily to enjoy newer and more refined versions of phosh.   
      
   I have, however, encountered one regression: VTs don't work correctly   
   with the latest kernel, to the point where they're pretty much   
   unusable.   
      
   The behavior I'm seeing is as such: from the Wayland (phosh) session   
   running on tty7, I can switch to a tty2 using Ctrl+Alt+F2, and the   
   usual login prompt is displayed correctly. When I type in my   
   username, however, the screen doesn't get updated.   
      
   I can force an update by switching to other VTs and then back. There   
   doesn't seem to be a precise pattern to how many of these switches   
   are necessary to trigger a refresh: sometimes it's enough to do   
      
     tty2 -> tty3 -> tty2   
      
   but other times additional switches are needed. For each of these   
   switches, there's a chance that the login prompt will be updated to   
   show the actual VT in the first line, while other times that won't   
   happen. Again, if there's a pattern to this, I haven't been able to   
   figure out what it is. Switching to the Wayland session on tty7 and   
   then back reliably forces a refresh.   
      
   Additionally, the entire screen occasionally gets corrupted while   
   sitting idle. It's hard to describe, but it looks as if the rows of   
   pixels all get shifted horizontally by different amounts. The   
   corruption lasts maybe 20-30 seconds, then things return to normal. I   
   can take a picture of the screen and attach it to the bug report if   
   that's useful.   
      
   None of this happens when booting the current stable kernel,   
   linux-image-6.12.57+deb13-amd64 (6.12.57-1), so it appears to be a   
   kernel regression.   
      
   Note that I'm working under the assumption that the issue is limited   
   to the Surface Go 2 hardware, but in reality I'm not running testing   
   on any other machine right now so it could be more widespread. I just   
   expect that it would have been noticed and reported already if that   
   had been the case.   
      
   I'm happy to provide any additional information upon request.   
      
      
   -- System Information:   
   Debian Release: 13.2   
     APT prefers stable-updates   
     APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,   
   'stable')   
   Architecture: amd64 (x86_64)   
      
   Kernel: Linux 6.12.57+deb13-amd64 (SMP w/8 CPU threads; PREEMPT)   
   Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),    
   ANGUAGE=en_US:en   
   Shell: /bin/sh linked to /usr/bin/dash   
   Init: systemd (via /run/systemd/system)   
   LSM: AppArmor: enabled   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iQIzBAABCgAdFiEEO48t9niVypx3EjLf954fxUKFg6wFAmlapdoACgkQ954fxUKF   
   g6ywHRAAoFdqTjU1FhqI0rKa2Fa0rlkVFpVIoXyfB4fbyvKJPOIv6SCgQo1B5FA6   
   3dbQWP8za/2JBBwPfTPd5ewyXJ/R4Q7bEBdM/K0C5FfS6YudrxxS/rKyYuWiCxUM   
   jPoCIs9BNInSrWj2pOgw8kG/9U8BzxVbXP9DWRl9AeUgxvDqXUm/cICmBPOLH3sF   
   LyUHRif2ljJlYk+768863CcX7J2YWWFhl53iKMq+BnMDd+Bc1AR1ZX0UwEvBEi4M   
   ldntk+aXEgbw41wXMXIj2GIz5FAop9fUVsKfiFO3YCpkp669mjPzffxstHCHxYL7   
   0a0CoODJ3j1nguQ0RTbDU3Q3o6aUTkYWe+spjea3/b2VBrPG28jxhULdgtO5bNNs   
   xL5ZoRxaTdGuG1FyspaOD2wxfioRbByLXXpXkAmJLU5uDCtF6tKB8NCy9NTRdTX3   
   nedy6omh2ql4lv9C0UwsKLKENz3v+U5xnWHggO22q6QTTgnxuBCGvY2eDiWmrJpx   
   uQznpTonYRHxl1H0yvqX7LclsKoAgfWGgIBU1dPzImXjasmodtJlicyNfhrSGJas   
   WkONPuArdHBrKtdkzvgBkZwQgZf1DmiUDObwL2T7eg5coFom9wociXLbW8ImiTOH   
   norroKFV+IBJHhNOB6zrjxLDQPkw6MTMW0VFaZ9hAaeANgQzbiE=   
   =oaYQ   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)