linux-kernel - Re: BCM4312 Fails when xdm is started

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:	Tue, 25 Nov 2008 12:05:49 +0100
From:	Michael Buesch <mb@...sch.de>
To:	Yuval Hager <yuval@...amzon.net>
Cc:	Larry Finger <Larry.Finger@...inger.net>,
	LKML <linux-kernel@...r.kernel.org>,
	wireless <linux-wireless@...r.kernel.org>,
	bcm43xx-dev@...ts.berlios.de
Subject: Re: BCM4312 Fails when xdm is started

On Tuesday 25 November 2008 06:43:22 Yuval Hager wrote:
> However, I have some few interesting findings. 
> First, this is totally unrelated to b43, but to the PCI. I get the flawed 1's 
> read from lspci even without loading b43.
> 
> I played around with different video drivers and the results are:
> * If using the 'via' driver, I lose the PCIe card immediately upon 
> initialization
> * Using the 'openchrome' (trunk version), It works well in the beginning. 
> After first blanking the register reads are all 1's, and then when the screen 
> is blank I get a different read (some registers are correct, some are wrong), 
> and when the screen is unblanked, I get 0xff's again. Very consistent and 
> predictabe (same read every time).
> * Using the 'vesa' driver I could not recreate the problem. I could not get 
> the screen to blank for some reason, but closing the lid, going on 
> standby/hibernate, restarting X - all didn't matter much to the PCI and the 
> wireless card kept on working.

Ok, then you should report the stuff to the X guys. This is not a b43 problem
and I also don't think it's a kernel problem.

-- 
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/