[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: closing Bullseye bugs pointing to a fix in Unstable?

On 23.07.2022 12:39, Thomas Schmitt wrote:

Hi,


Surely "Closes:" is very convenient, but wouldn't you agree that this
puts the users of Stable at a disadvantage?

Well, "stable" means old software with old bugs. Those who want the new
bugs, which are introduced by fixing the old ones, have to run something
else.
Then why "nvidia-driver" in Stable was switched from previous "460.91.03-1" version to "470.129.06-6~deb11u1"? 
    $ rmadison nvidia-driver
    nvidia-driver | 340.106-1                    | oldoldoldstable/non-free    | amd64, armhf, i386     nvidia-driver | 390.138-1                    | oldoldstable/non-free       | amd64, armhf, i386     nvidia-driver | 418.152.00-1~bpo9+1          | stretch-backports/non-free  | amd64, armhf, i386     nvidia-driver | 418.211.00-1                 | oldstable/non-free          | amd64, armhf, i386     nvidia-driver | 470.103.01-1~bpo11+1         | bullseye-backports/non-free | amd64, arm64     nvidia-driver | 470.129.06-6~deb11u1~bpo10+1 | buster-backports/non-free   | amd64, arm64     nvidia-driver | 470.129.06-6~deb11u1         | stable/non-free             | amd64, arm64     nvidia-driver | 470.129.06-6                 | testing/non-free            | amd64, arm64     nvidia-driver | 470.129.06-6                 | unstable/non-free           | amd64, arm64     nvidia-driver | 510.73.08-3                  | experimental/non-free       | amd64, arm64
This change made my system unstable, causing it to freeze sporadically with "Xid" error in syslog.     kernel: NVRM: GPU at PCI:0000:01:00: GPU-7565947f-d476-7159-d106-172c793521e6 
    kernel: NVRM: Xid (PCI:0000:01:00): 8, pid=2039, Channel 00000010

And now I can't perform an easy enough downgrade to last working version.
Freezes are only happening with 470.xxx versions of the "nvidia-driver", every other versions up to 460.91.03 worked flawlessly. 

    $ lspci
    ...
    01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) (prog-if 00 [VGA controller]) 
            Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB]
            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+             Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- 
            Latency: 0
            Interrupt: pin A routed to IRQ 135
            IOMMU group: 1
            Region 0: Memory at ee000000 (32-bit, non-prefetchable) [size=16M] 
            Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
            Region 3: Memory at e0000000 (64-bit, prefetchable) [size=32M]
            Region 5: I/O ports at e000 [size=128]
            Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
            Capabilities: <access denied>
            Kernel driver in use: nvidia
            Kernel modules: nvidia

    $ uname -a
    Linux fortune 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux 

Should I file a new bug?
If so, what is the best way to do it, if the last freeze happened 4 days ago, according by timestamps in syslog, and now I plan to downgrade the driver to be able to use full capabilities of my PC? 


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀
Reply to: