From: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
To: Roger Lucas <roger@planbit.co.uk>
Cc: linux-acpi@vger.kernel.org, "'Suietov,
Fiodor F'" <fiodor.f.suietov@intel.com>
Subject: Re: Kernel eats memory with LG-81 motherboard , acpi_operand possible culprit?
Date: Fri, 15 Sep 2006 22:41:40 +0400 [thread overview]
Message-ID: <450AF3E4.8090808@linux.intel.com> (raw)
In-Reply-To: <20060915164139.7BBA412EDE@bluewhale.planbit.co.uk>
It is a leak mentioned by Fiodor -- bug #6514.
Roger Lucas wrote:
> Hi Alexey,
>
> Thanks for the quick responses - it looks like I either need to
> path+recompile the 2.6.16.20 kernel to allow a replacement DSDT file or use
> the 2.6.17.13 kernel.
>
> Can you clarify exactly what memory leak you think is the problem? I don't
> mind trying the 2.6.17.x kernel, but I would like to know exactly what the
> problem being resolved is.
>
> Thanks,
>
> Roger
>
>> -----Original Message-----
>> From: Alexey Starikovskiy [mailto:alexey_y_starikovskiy@linux.intel.com]
>> Sent: 15 September 2006 16:52
>> To: Suietov, Fiodor F
>> Cc: Roger Lucas; linux-acpi@vger.kernel.org
>> Subject: Re: Kernel eats memory with LG-81 motherboard , acpi_operand
>> possible culprit?
>>
>> Roger,
>> Please try to upgrade to 2.6.17.x, as it probably contains a fix to your
>> memory leak.
>>
>> Regards,
>> Alex.
>>
>> Suietov, Fiodor F wrote:
>>> Perhaps, it is related to #6514:
>>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=6514
>>>
>>> Thanks,
>>> Fiodor
>>>
>>>> -----Original Message-----
>>>> From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
>>>> owner@vger.kernel.org] On Behalf Of Alexey Starikovskiy
>>>> Sent: Friday, September 15, 2006 6:41 PM
>>>> To: Roger Lucas
>>>> Cc: linux-acpi@vger.kernel.org
>>>> Subject: Re: Kernel eats memory with LG-81 motherboard , acpi_operand
>>>> possible culprit?
>>>>
>>>> Roger,
>>>>
>>>> Please try to change Store(Local0, Local0) to Store(Zero, Local0) and
>>>> check if you still have a leak...
>>>>
>>>> Thanks,
>>>> Alex.
>>>>
>>>> Roger Lucas wrote:
>>>>> Some more information...
>>>>>
>>>>> It seems that there are bugs in the DSDT information. I followed
>>> the
>>>>> instructions on this link to analyse the DSDT table.
>>>>>
>>>>> http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
>>>>>
>>>>> When I recompiled it, the following errors occurred. I have no idea
>>>> what
>>>>> these mean or if they are important, but I suspect that they are not
>>>> good.
>>>>> The BIOS ASL was originally compiled with the Microsoft compiler.
>>>>>
>>>>> root@hydra:~# iasl -tc dsdt.dsl
>>>>>
>>>>> Intel ACPI Component Architecture
>>>>> ASL Optimizing Compiler version 20051216 [Jan 9 2006]
>>>>> Copyright (C) 2000 - 2005 Intel Corporation
>>>>> Supports ACPI Specification Revision 3.0
>>>>>
>>>>> dsdt.dsl 361: Method (\_WAK, 1, NotSerialized)
>>>>> Warning 2078 - ^ Reserved method must return a
>>> value
>>>> (_WAK)
>>>>> dsdt.dsl 394: Store (Local0, Local0)
>>>>> Error 1048 - ^ Method local variable is
>>> not
>>>>> initialized (Local0)
>>>>>
>>>>> dsdt.dsl 399: Store (Local0, Local0)
>>>>> Error 1048 - ^ Method local variable is
>>> not
>>>>> initialized (Local0)
>>>>>
>>>>> dsdt.dsl 5349: If (Or (PLCY, PLCY, Local7))
>>>>> Warning 2097 - ^ Statement is unreachable
>>>>>
>>>>> ASL Input: dsdt.dsl - 5433 lines, 178284 bytes, 2002 keywords
>>>>> Compilation complete. 2 Errors, 2 Warnings, 0 Remarks, 537
>>> Optimizations
>>>>> root@hydra:~#
>>>> -
>>>> To unsubscribe from this list: send the line "unsubscribe linux-acpi"
>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>> -
>>> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-09-15 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 15:18 Kernel eats memory with LG-81 motherboard , acpi_operand possible culprit? Suietov, Fiodor F
2006-09-15 15:52 ` Alexey Starikovskiy
2006-09-15 16:41 ` Roger Lucas
2006-09-15 18:41 ` Alexey Starikovskiy [this message]
2006-09-15 19:57 ` Roger Lucas
2006-09-15 21:08 ` Alexey Starikovskiy
2006-09-16 12:19 ` Roger Lucas
-- strict thread matches above, loose matches on Subject: below --
2006-09-15 12:19 Roger Lucas
2006-09-15 14:34 ` Roger Lucas
2006-09-15 14:40 ` Alexey Starikovskiy
2006-09-16 13:25 ` Roger Lucas
2006-09-16 16:44 ` Roger Lucas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=450AF3E4.8090808@linux.intel.com \
--to=alexey_y_starikovskiy@linux.intel.com \
--cc=fiodor.f.suietov@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=roger@planbit.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox