Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Diederik de Haas
Hi Emanuele, On Tuesday, 10 October 2023 15:02:07 CEST Emanuele Rocca wrote: > On 2023-10-10 01:54, Diederik de Haas wrote: > > On Tuesday, 10 October 2023 12:10:07 CEST Emanuele Rocca wrote: > > > CONFIG_PREEMPT_DYNAMIC is set to 'y' by default on amd64 > > > due to HAVE_PREEMPT_DYNAMIC_CALL

Bug#1053764: radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch unnecessary for amdgpu now

2023-10-10 Thread Mario Limonciello
Package: linux Version: 6.5.0-1 Hi, The patch carried by the Debian kernel bugfix/all/radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch isn't necessary specifically for amdgpu anymore with modern kernels. AMDGPU has been modified to check for the existence of firmware

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Marc Haber
On Tue, Oct 10, 2023 at 12:32:22PM +0200, Emanuele Rocca wrote: > On 2023-10-10 12:14, Johannes Schauer Marin Rodrigues wrote: > > Quoting Emanuele Rocca (2023-10-10 12:10:07) > > > Setting CONFIG_HAVE_PREEMPT_DYNAMIC=y on arm64 is likely safe for us too, > > > but > > > we may want to run some

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Diederik de Haas
On Tuesday, 10 October 2023 14:17:50 CEST Vincent Blut wrote: > > Neither does amd64. So it appears something else is causing > > CONFIG_PREEMPT_DYNAMIC to be enabled on amd64. > > From the commit message introducing PREEMPT_DYNAMIC:¹ > > CONFIG_PREEMPT_DYNAMIC is automatically selected by

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Emanuele Rocca
Hi Diederik, On 2023-10-10 01:54, Diederik de Haas wrote: > On Tuesday, 10 October 2023 12:10:07 CEST Emanuele Rocca wrote: > > CONFIG_PREEMPT_DYNAMIC is set to 'y' by default on amd64 due to > > HAVE_PREEMPT_DYNAMIC_CALL being 'y', see: > >

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Vincent Blut
Hi, Le 2023-10-10 13:54, Diederik de Haas a écrit : > On Tuesday, 10 October 2023 12:10:07 CEST Emanuele Rocca wrote: > > CONFIG_PREEMPT_DYNAMIC is set to 'y' by default on amd64 due to > > HAVE_PREEMPT_DYNAMIC_CALL being 'y', see: > >

Bug#939079: nouveau: screen dimensions and resolution are wrong

2023-10-10 Thread Vincent Lefevre
Control: found -1 6.1.55-1 On 2019-09-01 04:11:15 +0200, Vincent Lefevre wrote: > With the nouveau driver, I get: > > $ xdpyinfo > [...] > screen #0: > dimensions:3200x1800 pixels (846x476 millimeters) > resolution:96x96 dots per inch > [...] > > which is wrong! After installing

Processed: Re: nouveau: screen dimensions and resolution are wrong

2023-10-10 Thread Debian Bug Tracking System
Processing control commands: > found -1 6.1.55-1 Bug #939079 [src:linux] nouveau: screen dimensions and resolution are wrong Marked as found in versions linux/6.1.55-1. -- 939079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939079 Debian Bug Tracking System Contact ow...@bugs.debian.org

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Diederik de Haas
On Tuesday, 10 October 2023 12:10:07 CEST Emanuele Rocca wrote: > CONFIG_PREEMPT_DYNAMIC is set to 'y' by default on amd64 due to > HAVE_PREEMPT_DYNAMIC_CALL being 'y', see: > https://sources.debian.org/src/linux/6.5.6-1/kernel/Kconfig.preempt/?hl=101# > L101 > > arm64 does not have

Bug#1053750: linux-image-6.1.0-13-amd64: "Hardware Error" during shutdown that is not a hardware problem

2023-10-10 Thread Laurent Bonnaud
Hi again, the error log in my previous message comes from this directory: /var/lib/systemd/pstore/7285820828300/ Each time the system reboots, a new directory is created, and 3 files are created in it. For the sake of completeness, here are the 3 files. Thanks, --

Bug#1053750: linux-image-6.1.0-13-amd64: "Hardware Error" during shutdown that is not a hardware problem

2023-10-10 Thread Laurent Bonnaud
Package: src:linux Version: 6.1.55-1 Severity: normal Dear Maintainer, each time this system is rebooted, during shutdown, the kernel outputs the following error message. The kernel thinks it encountered a "Hardware Error", but the error is most probably not a hardware error, because I also

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Emanuele Rocca
Hello Johannes, On 2023-10-10 12:14, Johannes Schauer Marin Rodrigues wrote: > Quoting Emanuele Rocca (2023-10-10 12:10:07) > > Setting CONFIG_HAVE_PREEMPT_DYNAMIC=y on arm64 is likely safe for us too, > > but > > we may want to run some benchmark first to see if there are any noticeable > >

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Johannes Schauer Marin Rodrigues
Hi, Quoting Emanuele Rocca (2023-10-10 12:10:07) > Setting CONFIG_HAVE_PREEMPT_DYNAMIC=y on arm64 is likely safe for us too, but > we may want to run some benchmark first to see if there are any noticeable > slowdowns. I have a couple of arm64 boards here that I can run benchmarks on. What would

Re: CONFIG_PREEMPT_DYNAMIC=y?

2023-10-10 Thread Emanuele Rocca
Hi, On 2023-10-08 07:17, Diederik de Haas wrote: > $ grep PREEMPT_DYNAMIC /boot/config-6.5.0-1-amd64 > CONFIG_PREEMPT_DYNAMIC=y > CONFIG_HAVE_PREEMPT_DYNAMIC=y > CONFIG_HAVE_PREEMPT_DYNAMIC_CALL=y [...] > $ grep PREEMPT_DYNAMIC /boot/config-6.1.0-13-arm64 > # CONFIG_PREEMPT_DYNAMIC is not set