linux-kernel - Re: [PATCH 44/47] PCI: enable driver multi-threaded probe

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: <20060927185124.GA9552@aepfle.de>
Date:	Wed, 27 Sep 2006 20:51:24 +0200
From:	Olaf Hering <olaf@...fle.de>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 44/47] PCI: enable driver multi-threaded probe

On Mon, Sep 25, Greg KH wrote:

> Use at your own risk!!!

I havent debugged it, but it seems to reorder the driver probing, offb
vs. nvidiafb (-bad, +good):

-Using unsupported 1024x768 NVDA,Display-A at 90020000, depth=8, pitch=1024
-PCI: Unable to reserve mem region #2:10000000@...00000 for device 0000:0a:00.0
-nvidiafb: cannot request PCI regions
+nvidiafb: Device ID: 10de0141 
+nvidiafb: CRTC0 analog found
+nvidiafb: CRTC1 analog found
+nvidiafb: Found OF EDID for head 1
+nvidiafb: EDID found from BUS1
+nvidiafb: EDID found from BUS2
+nvidiafb: CRTC 0 appears to have a CRT attached
+nvidiafb: Using CRT on CRTC 0
 Console: switching to colour frame buffer device 128x48
-fb0: Open Firmware frame buffer device on /pci@0,f0000000/NVDA,Parent@...VDA,Display-A@0
+nvidiafb: PCI nVidia NV14 framebuffer (64MB @ 0x90000000)


Download attachment "dmesg.sync.txt.gz" of type "application/x-gunzip" (5262 bytes)

Download attachment "dmesg.async.txt.gz" of type "application/x-gunzip" (5689 bytes)