linux-kernel - Re: [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR

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: <501B0536.6070001@mso.anu.edu.au>
Date:	Fri, 03 Aug 2012 08:54:46 +1000
From:	Francois Rigaut <frigaut@....anu.edu.au>
To:	Greg KH <gregkh@...uxfoundation.org>,
	Matthew Garrett <mjg59@...f.ucam.org>, matt.fleming@...el.com,
	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
	x86@...nel.org, linux-pci@...r.kernel.org, bhelgaas@...gle.com
Subject: Re: [PATCH V2 1/4] EFI: Stash ROMs if they're not in the PCI BAR

Seth,

I have put the osx system.log, which is the only file where I can see 
mux and AGC related message, at http://maumae.net/retina/system.log
Thanks,
Francois

On 03/08/12 08:40, Francois Rigaut wrote:
> Hi Seth,
>
> Sorry for the belated response. On Oz time here.
> I don't have a /var/log/kernel.log !
> Let me make sure of something:
> This switcher code is to be run on osx, no? That's where gfxcardstatus 
> lives and where I can effect the card switch. Just to make sure.
> So I'm running osx mountain lion, and the only thing I see in the logs 
> when I switch cards (using gfxcardstatus) is what I pasted below. and 
> you're right, it was not in message.log, but system.log (it was late). 
> I just went through the whole thing again.
> Am I missing something?
> Cheers,
> Francois
>
> On 03/08/12 02:12, Seth Forshee wrote:
>> On Fri, Aug 03, 2012 at 12:57:33AM +1000, Francois Rigaut wrote:
>>> Greg, Seth,
>>>
>>> Here is what the message.log shows:
>>>
>>> switching to the HD4000 (integrated):
>>>
>>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x42803c0
>>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: 
>>> CGXMuxAcknowledge: Posting glitchless acknowledge
>>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: 
>>> MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 
>>> 0x042803c0 device: 0x10c678320  isBackBuffered: 0 numComp: 1 numDisp: 3
>>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x42803c0
>>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x3f003d
>>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x3f003e
>>> Aug  3 00:49:55 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x3f003f
>>>
>>> switching to the nvidia (discrete):
>>>
>>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x42803c0
>>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x3f003d
>>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x3f003e
>>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x3f003f
>>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: 
>>> CGXMuxAcknowledge: Posting glitchless acknowledge
>>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: 
>>> MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 
>>> 0x042803c0 device: 0x10c678320  isBackBuffered: 0 numComp: 1 numDisp: 3
>>> Aug  3 00:50:35 poliahu.ctio.noao.edu WindowServer[79]: Received 
>>> display connect changed for display 0x42803c0
>>>
>>> Hope that helps.
>> Thanks for trying it out, but it's not really what I was hoping for. I
>> get a bunch of messages similar to these in /var/log/kernel.log, mixed
>> in with a lot of other stuff.
>>
>>   AGC:: setMuxRegister:1666 (728, 1, 1)
>>   AGC:: setMuxRegister:1666 (710, 1, 4)
>>   AGC:: getMuxRegister:1647 (716, 1) = 1
>>
>> I don't even have message.log. You don't have a kernel.log? Do you see
>> any messages like those if you run dmesg?
>>
>> Seth

--
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/