similar to: Warnings in dmesg and results of mmiotrace 10de:1140 Geforce620m Optimus Laptop Acer E1-531G

Od: "Ilia Mirkin" <imirkin at alum.mit.edu> Do: "Lampshade" <lampshade at poczta.fm>; Wys?ane: 19:07 Czwartek 2014-07-10 Temat: Re: [Nouveau] Warnings in dmesg and results of mmiotrace 10de:1140 Geforce620m Optimus Laptop Acer E1-531G > On Thu, Jul 10, 2014 at 11:01 AM, Lampshade wrote: > > Hello > > in dmesg I always have these informations (I

Od: "Ilia Mirkin" <imirkin at alum.mit.edu> Do: "Lampshade" <lampshade at poczta.fm>; Wys?ane: 19:07 Czwartek 2014-07-10 Temat: Re: [Nouveau] Warnings in dmesg and results of mmiotrace 10de:1140 Geforce620m Optimus Laptop Acer E1-531G > On Thu, Jul 10, 2014 at 11:01 AM, Lampshade wrote: > > Hello > > in dmesg I always have these informations (I

https://bugs.freedesktop.org/show_bug.cgi?id=85742 Bug ID: 85742 Summary: GF117M Can *not* use nouveau at all Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee: nouveau

On Fri, 20 Mar 2009 00:06:39 -0500 Jason Detring <detringj at gmail.com> wrote: > Speaking of contributing, would you like a tester for Nouveau on > SPARC64? I have access to an Ultra 45 and a pair of PCI boards (TnT2, > GeForce 6200, both with x86 VBIOSes unfortunately). I don't own any > PCI-E boards yet, but that can change if there's interest. I have no idea about

On Fri, 25 Oct 2013 17:19:56 +0400 Eugene Shatokhin <euspectre at gmail.com> wrote: > Hi, > > 2013/10/25 Pekka Paalanen <pq at iki.fi> > ... > > We could use some comments from the real reverse-engineers. I used > > to be mostly a tool writer. > > > > Yes, if some experts could share their knowledge of this matter, this would > be most

On Wed, 8 Apr 2020 13:53:23 -0700 Nathan Chancellor <natechancellor at gmail.com> wrote: > When building with Clang + -Wtautological-compare and > CONFIG_CPUMASK_OFFSTACK unset: > > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' > equal to a null pointer is always false [-Wtautological-pointer-compare] > if (downed_cpus == NULL

On Wed, Apr 8, 2020 at 10:53 PM Nathan Chancellor <natechancellor at gmail.com> wrote: > > When building with Clang + -Wtautological-compare and > CONFIG_CPUMASK_OFFSTACK unset: > Hi Nathan, thanks for the quick patch. I can confirm I have no CONFIG_CPUMASK_OFFSTACK set. Regards, - Sedat - > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus'

On Wed, Apr 8, 2020 at 11:12 PM Sedat Dilek <sedat.dilek at gmail.com> wrote: > > On Wed, Apr 8, 2020 at 10:53 PM Nathan Chancellor > <natechancellor at gmail.com> wrote: > > > > When building with Clang + -Wtautological-compare and > > CONFIG_CPUMASK_OFFSTACK unset: > > > > Hi Nathan, > > thanks for the quick patch. > > I can confirm

On Wed, Apr 08, 2020 at 01:53:23PM -0700, Nathan Chancellor wrote: > When building with Clang + -Wtautological-compare and > CONFIG_CPUMASK_OFFSTACK unset: > > arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' > equal to a null pointer is always false [-Wtautological-pointer-compare] > if (downed_cpus == NULL && >

On Mon, 18 May 2020 11:52:47 -0700 Nick Desaulniers <ndesaulniers at google.com> wrote: > On Mon, May 18, 2020 at 2:31 AM Nathan Chancellor > <natechancellor at gmail.com> wrote: > > > > On Wed, Apr 08, 2020 at 01:53:23PM -0700, Nathan Chancellor wrote: > > > When building with Clang + -Wtautological-compare and > > > CONFIG_CPUMASK_OFFSTACK

Hi, 2013/10/25 Pekka Paalanen <pq at iki.fi> > > Just curious, how do you detect interesting instructions to > instrument from uninteresting instructions that do not access mmio > areas? > > As I currently use this for data race detection in general, there is no need to separate accesses to mmio areas from the accesses to other memory. The tool just tracks all except the

I need this application to rum my laptop buttons. Like WiFi, Web Browser, Bluetooth and volume control. Here is the link for the Win7 x86 version. http://global-download.acer.com/GDFiles/Application/LaunchManager/LaunchManager_Dritek_3.0.02_W7x86W7x64_A.zip?acerid=634111298367326931&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE%206920G&OS=ALL&LC=en&BC=ACER&SC=PA_7 Thank

http://bugs.freedesktop.org/show_bug.cgi?id=27230 Summary: [105M / Acer] Bad EDID causes nouveau to fail on Acer Extensa 5635G laptop Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hi, > Ah, you are not using the ftrace framework nor relayfs? Mmiotrace used to be relayfs at one point and then converted to ftrace. Yes, I considered these when I started working on KernelStrider but finally borrowed ideas from Perf and implemented them. A mmapped ring buffer does its job well and has a higher throughput than Ftrace in my case. > Are you saying that you intercept

If something calls ioremap with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap the address passed to unregister_kmmio_probe was PAGE_SIZE aligned by the caller leading to a complete freeze of the machine. We should always page

4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but

3.18-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but

4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but

4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but

From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 6d60ce384d1d5ca32b595244db4077a419acc687 ] If something calls ioremap() with an address not aligned to PAGE_SIZE, the returned address might be not aligned as well. This led to a probe registered on exactly the returned address, but the entire page was armed for mmiotracing. On calling iounmap() the address passed to