Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <4b0c06ba-b05c-071c-d494-67775bd7250f@gmail.com>
Date:   Thu, 10 Aug 2023 10:03:38 +0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.14.0
Content-Language: en-US
To:     Ben Skeggs <bskeggs@redhat.com>, Karol Herbst <kherbst@redhat.com>,
        Lyude Paul <lyude@redhat.com>,
        Peter Bottomley <peebee@gmx.com>, peter@peebee.org.uk
Cc:     Linux DRI Development <dri-devel@lists.freedesktop.org>,
        Linux Nouveau <nouveau@lists.freedesktop.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Regressions <regressions@lists.linux.dev>,
        Linux Stable <stable@vger.kernel.org>
From:   Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Fwd: System (Xeon Nvidia) hangs at boot terminal after kernel 6.4.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi,

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).
> 
> The issue seems to be specific to the hardware of this desktop as the problem kernels do boot through to completion on other machines.
> 
> A test was done with a different build (from Porteus) of kernel 6.5-RC4 and that did not hang - but kernel 6.4.7 from the same builder hung just like my build.
> 
> I apologise that I cannot provide any detailed diagnostics - but I can put diagnostics into /etc/profile and provide screenshots if requested.
> 
> Forum thread with more details and screenshots:
> https://forum.puppylinux.com/viewtopic.php?p=95733#p95733
> 
> 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.

FYI, this is stable-specific regression since it doesn't appear on mainline.
Also, I have asked the reporter to also open the issue on gitlab.freedesktop.org
tracker (as it is the standard for DRM subsystem).

To the reporter (on To: list): It'd been great if you also have netconsole
output on your Bugzilla report, providing that you have another machine
connecting to your problematic one.

Anyway, I'm adding this regression to be tracked by regzbot:

#regzbot introduced: v6.4.6..v6.4.7 https://bugzilla.kernel.org/show_bug.cgi?id=217776
#regzbot link: https://forum.puppylinux.com/viewtopic.php?p=95733#p95733

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217776

-- 
An old man doll... just what I always wanted! - Clara