Re: [2.6.7-mm5 ACPI] Error: Looking up [SERN] in namespace

From: Niel Lambrechts (antispam_at_absamail.co.za)
Date: 07/17/04

  • Next message: Lasse Kärkkäinen / Tronic: "OT: tabs and spaces"
    To: Linux Kernel ML <linux-kernel@vger.kernel.org>
    Date:	Sat, 17 Jul 2004 23:24:23 +0200
    
    

    On Fri, 2004-07-16 at 00:50, Niel Lambrechts wrote:
    > Hi,
    >
    > I get the following (repetitive) dmesg on my Thinkpad R50P:
    >
    > dswload-0292: *** Error: Looking up [SERN] in namespace, AE_ALREADY_EXISTS
    > psparse-0597 [86051] ps_parse_loop : During name lookup/catalog, AE_ALREADY_EXISTS
    > psparse-1133: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.GBIF] (Node c1567fa8), AE_ALREADY_EXISTS
    > osl-0899 [86055] os_wait_semaphore : Failed to acquire semaphore[dff5e580|1|0], AE_TIME
    > dswload-0641: *** Error: Looking up [SERN] in namespace, AE_NOT_FOUND
    > psparse-0597 [86064] ps_parse_loop : During name lookup/catalog, AE_NOT_FOUND
    > psparse-1133: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.GBIF] (Node c1567fa8), AE_NOT_FOUND
    > psparse-1133: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT0._BIF] (Node c1567928), AE_NOT_FOUND
    > acpi_battery-0146 [86057] acpi_battery_get_info : Error evaluating _BIF
    > osl-0899 [87427] os_wait_semaphore : Failed to acquire semaphore[dff5e580|1|0], AE_TIME
    > osl-0899 [95484] os_wait_semaphore : Failed to acquire semaphore[dff5e580|1|0], AE_TIME
    > osl-0899 [96766] os_wait_semaphore : Failed to acquire semaphore[dff5e580|1|0], AE_TIME
    > osl-0899 [98886] os_wait_semaphore : Failed to acquire semaphore[dff5e580|1|0], AE_TIME
    > osl-0899 [101057] os_wait_semaphore : Failed to acquire semaphore[dff5e580|1|0], AE_TIME
    >
    > The last line is especially repetitive.
    >
    > I also notice:
    > acpi_battery-0146 [86057] acpi_battery_get_info : Error evaluating _BIF

    My fault - failed to do a make clean after replacing the previous version of my dsdt table and recompiling the kernel.

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


  • Next message: Lasse Kärkkäinen / Tronic: "OT: tabs and spaces"

    Relevant Pages

    • Re: 2.6.7-mm2 build errors...
      ... send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • [PATCH 2/4] pfnmap: cow_user_page needs mask
      ... The fault address to cow_user_page is not usually page aligned, ... send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: "stable" vs "security stable"
      ... My fault. ... >> something wrong, and need to revert. ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: 2.6.8.1-mm4
      ... > they will return -EFAULT on a fault rather than the number of bytes which ... send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: [RFC] Changing COW detection to be memory hotplug friendly
      ... Keeping the swap slot ... is valuable if read fault, but once the page is dirtied, wouldn't ... I cannot imagine a good enough range of swap performance tests. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)