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]
Message-ID: <ff26929d-9fb0-3c85-2594-dc2937c1ba9a@bell.net>
Date:   Fri, 6 Jan 2023 02:28:55 -0500
From:   Matt Fagnani <matt.fagnani@...l.net>
To:     Vasant Hegde <vasant.hegde@....com>,
        Baolu Lu <baolu.lu@...ux.intel.com>,
        Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     Joerg Roedel <jroedel@...e.de>,
        "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
        LKML <linux-kernel@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        Linux PCI <linux-pci@...r.kernel.org>,
        Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [regression, bisected, pci/iommu] BugĀ 216865 - Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled

I booted 6.2-rc2 + patch with rd.driver.blacklist=amdgpu on the kernel 
command line to prevent amdgpu from being started while the initramfs 
was in use. The black screen problem happened later in the boot. I 
pressed sysrq+alt+s,u,b to do an emergency sync, remount read-only, and 
reboot. The journal for that boot was shown on the next boot. The two 
warnings which I previously reported weren't shown in the journal, but 
the same null pointer dereference which made amdgpu crash happened. I'm 
attaching the kernel log from the journal of that boot.


View attachment "6.2-rc2-patch-blacklist-amdgpu-journalctl-b-1-k-1.txt" of type "text/plain" (108544 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ