lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 10 Aug 2023 06:19:44 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        Ben Skeggs <bskeggs@...hat.com>,
        Karol Herbst <kherbst@...hat.com>,
        Lyude Paul <lyude@...hat.com>,
        Peter Bottomley <peebee@....com>, peter@...bee.org.uk
Cc:     Linux Nouveau <nouveau@...ts.freedesktop.org>,
        Linux Stable <stable@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux DRI Development <dri-devel@...ts.freedesktop.org>,
        Linux Regressions <regressions@...ts.linux.dev>
Subject: Re: [Nouveau] Fwd: System (Xeon Nvidia) hangs at boot terminal after
 kernel 6.4.7

On 10.08.23 05:03, Bagas Sanjaya wrote:
> 
> I notice a regression report on Bugzilla [1]. Quoting from it:
> 
>> Kernel 6.4.6 compiled from source worked AOK on my desktop with Intel Xeon cpu and Nvidia graphics - see below for system specs.
>>
>> Kernels 6.4.7 & 6.4.8 also compiled from source with identical configs hang with a frozen boot terminal screen after a significant way through the boot sequence (e.g. whilst running /etc/profile). The system may still be running as a sound is emitted when the power button is pressed (only way to escape from the system hang).
> [...]
>> Computer Profile:
>>  Machine                    Dell Inc. Precision WorkStation T5400   (version: Not Specified)
>>  Mainboard                  Dell Inc. 0RW203 (version: NA)
>>  • BIOS                     Dell Inc. A11 | Date: 04/30/2012 | Type: Legacy
>>  • CPU                      Intel(R) Xeon(R) CPU E5450 @ 3.00GHz (4 cores)
>>  • RAM                      Total: 7955 MB | Used: 1555 MB (19.5%) | Actual Used: 775 MB (9.7%)
>>  Graphics                   Resolution: 1366x768 pixels | Display Server: X.Org 21.1.8
>>  • device-0                 NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2)
>>  Audio                      ALSA
>>  • device-0                 Intel Corporation 631xESB/632xESB High Definition Audio Controller [8086:269a] (rev 09)
>>  • device-1                 NVIDIA Corporation High Definition Audio Controller [10de:0be3] (rev a1)
>>  Network                    wlan1
>>  • device-0                 Ethernet: Broadcom Inc. and subsidiaries NetXtreme BCM5754 Gigabit Ethernet PCI Express [14e4:167a] (rev 02)
> 
> See Bugzilla for the full thread.
> [...]
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217776

Not my area of expertise, but nevertheless pretty sure this is the same
issue already discussed here, as it's a GT218 there as well at 6.4.7 is
the version that commit was backported to:

https://lore.kernel.org/all/20230806213107.GFZNARG6moWpFuSJ9W@fat_crate.local/

No final solution ready yet, but looks like the culprit will be reverted.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ