[lkml]   [2009]   [Dec]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Regression in module wmi since 2.6.32 (bisected to commit 1caab3c)
    On 12/25/2009 07:18 PM, Carlos Corbacho wrote:
    > On Friday 25 December 2009 22:09:28 Larry Finger wrote:
    >> On 12/25/2009 03:58 PM, Carlos Corbacho wrote:
    >>> On Friday 25 December 2009 21:35:49 Larry Finger wrote:
    >>>> Should I attach the files DSDT.dat, acpidump.out, or DSDT?
    >>> DSDT from /proc/acpi/dsdt will do fine for my purposes.
    >> Attached.
    > This is the same as bugzilla #14846 - in both cases, the GUID 05901221-D566-11D1-B2F0-00A0C9062910 (a data block query) is duplicated in two different devices, although both look like they are nVidia related hooks.
    > Since we don't currently have any in kernel drivers that use that stuff, and the query in question just returns a binary MOF, the simplest solution (for now) seems to be to just ignore these duplicates - if and when someone wants to support these hooks, they can clean the mess up properly when they figure out how WMI is supposed to cope with conflicting GUID's.
    > Matthew, you looked at NVIF for your sins, can you see a better solution? We could just blacklist the offending GUID, rather than trying to catch all duplicates? Although just ignoring all duplicates strikes me as a better solution to catch the next time that J Random BIOS Developer decides to duplicate GUIDs in WMI.
    > Initial patch below which takes the "ignore all duplicate GUIDs" approach.

    The patch fixes my machine.



     \ /
      Last update: 2009-12-26 16:43    [W:0.031 / U:3.096 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site