* kmemleaks related to ACPI psparse
@ 2011-09-16 7:22 Sitsofe Wheeler
2011-09-16 7:29 ` Lin Ming
0 siblings, 1 reply; 5+ messages in thread
From: Sitsofe Wheeler @ 2011-09-16 7:22 UTC (permalink / raw)
To: Lin Ming, Bob Moore; +Cc: linux-acpi, linux-kernel
Hi,
In 3.1.0-rc5-dirty the following warning appeared in dmesg:
[ 249.506212] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20110623/evregion-478)
[ 249.506387] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.RCTP] (Node ee96daf0), AE_TIME (20110623/psparse-536)
[ 249.506636] ACPI Error: Method parse/execution failed [\_TZ_.RTMP] (Node eeb85000), AE_TIME (20110623/psparse-536)
[ 249.506827] ACPI Error: Method parse/execution failed [\_TZ_.TZ00._TMP] (Node eeb85190), AE_TIME (20110623/psparse-536)
[ 249.511953] Thermal: failed to read out thermal zone 0
Shortly followed by a bunch of kmemleak warnings (the initial trigger
has not been reproducible though):
unreferenced object 0xedcb81a0 (size 32):
comm "kworker/0:2", pid 389, jiffies 4294915201 (age 649.854s)
hex dump (first 32 bytes):
00 00 00 00 0d 01 70 00 00 00 00 00 00 00 00 00 ......p.........
00 00 00 00 d0 8d cb ed 00 00 00 00 01 00 00 00 ................
backtrace:
[<b0551807>] kmemleak_alloc+0x27/0x50
[<b0196435>] kmem_cache_alloc+0xc5/0x180
[<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
[<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
[<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
[<b02c61b4>] acpi_ps_execute_method+0x190/0x248
[<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
[<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
[<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
[<b02cf9de>] thermal_get_temp+0x34/0x5a
[<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
[<b03f6fcd>] thermal_zone_device_check+0xd/0x10
[<b013bd2c>] process_one_work+0x18c/0x3c0
[<b013e697>] worker_thread+0x107/0x310
[<b0141cac>] kthread+0x7c/0x90
[<b055e102>] kernel_thread_helper+0x6/0xd
unreferenced object 0xedcb8dd0 (size 32):
comm "kworker/0:2", pid 389, jiffies 4294915201 (age 649.854s)
hex dump (first 32 bytes):
a0 81 cb ed 0d 01 36 00 00 00 00 00 00 00 00 00 ......6.........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<b0551807>] kmemleak_alloc+0x27/0x50
[<b0196435>] kmem_cache_alloc+0xc5/0x180
[<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
[<b02c5159>] acpi_ps_complete_this_op+0xbb/0x146
[<b02c5202>] acpi_ps_complete_op+0x1e/0x208
[<b02c5afd>] acpi_ps_parse_loop+0x711/0x830
[<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
[<b02c61b4>] acpi_ps_execute_method+0x190/0x248
[<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
[<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
[<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
[<b02cf9de>] thermal_get_temp+0x34/0x5a
[<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
[<b03f6fcd>] thermal_zone_device_check+0xd/0x10
[<b013bd2c>] process_one_work+0x18c/0x3c0
[<b013e697>] worker_thread+0x107/0x310
unreferenced object 0xedcb84e0 (size 32):
comm "kworker/0:2", pid 389, jiffies 4294915202 (age 649.853s)
hex dump (first 32 bytes):
00 00 00 00 0d 01 a0 00 03 00 00 00 00 00 00 00 ................
00 00 00 00 00 80 cb ed 00 00 00 00 02 00 00 00 ................
backtrace:
[<b0551807>] kmemleak_alloc+0x27/0x50
[<b0196435>] kmem_cache_alloc+0xc5/0x180
[<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
[<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
[<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
[<b02c61b4>] acpi_ps_execute_method+0x190/0x248
[<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
[<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
[<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
[<b02cf9de>] thermal_get_temp+0x34/0x5a
[<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
[<b03f6fcd>] thermal_zone_device_check+0xd/0x10
[<b013bd2c>] process_one_work+0x18c/0x3c0
[<b013e697>] worker_thread+0x107/0x310
[<b0141cac>] kthread+0x7c/0x90
[<b055e102>] kernel_thread_helper+0x6/0xd
unreferenced object 0xedcb8000 (size 32):
comm "kworker/0:2", pid 389, jiffies 4294915209 (age 649.870s)
hex dump (first 32 bytes):
e0 84 cb ed 0d 01 a0 00 09 00 00 00 00 00 00 00 ................
00 00 00 00 90 8a cb ed 00 00 00 00 02 00 00 00 ................
backtrace:
[<b0551807>] kmemleak_alloc+0x27/0x50
[<b0196435>] kmem_cache_alloc+0xc5/0x180
[<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
[<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
[<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
[<b02c61b4>] acpi_ps_execute_method+0x190/0x248
[<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
[<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
[<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
[<b02cf9de>] thermal_get_temp+0x34/0x5a
[<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
[<b03f6fcd>] thermal_zone_device_check+0xd/0x10
[<b013bd2c>] process_one_work+0x18c/0x3c0
[<b013e697>] worker_thread+0x107/0x310
[<b0141cac>] kthread+0x7c/0x90
[<b055e102>] kernel_thread_helper+0x6/0xd
unreferenced object 0xedcb8a90 (size 32):
comm "kworker/0:2", pid 389, jiffies 4294915210 (age 649.869s)
hex dump (first 32 bytes):
00 80 cb ed 0d 01 70 00 14 00 00 00 00 00 00 00 ......p.........
00 00 00 00 40 83 cb ed 00 00 00 00 01 00 00 00 ....@...........
backtrace:
[<b0551807>] kmemleak_alloc+0x27/0x50
[<b0196435>] kmem_cache_alloc+0xc5/0x180
[<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
[<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
[<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
[<b02c61b4>] acpi_ps_execute_method+0x190/0x248
[<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
[<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
[<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
[<b02cf9de>] thermal_get_temp+0x34/0x5a
[<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
[<b03f6fcd>] thermal_zone_device_check+0xd/0x10
[<b013bd2c>] process_one_work+0x18c/0x3c0
[<b013e697>] worker_thread+0x107/0x310
[<b0141cac>] kthread+0x7c/0x90
[<b055e102>] kernel_thread_helper+0x6/0xd
unreferenced object 0xedcb8340 (size 32):
comm "kworker/0:2", pid 389, jiffies 4294915210 (age 649.869s)
hex dump (first 32 bytes):
90 8a cb ed 0d 01 2d 00 15 00 00 00 00 00 00 00 ......-.........
00 00 00 00 85 17 f8 ef 00 00 00 00 00 00 00 00 ................
backtrace:
[<b0551807>] kmemleak_alloc+0x27/0x50
[<b0196435>] kmem_cache_alloc+0xc5/0x180
[<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
[<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
[<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
[<b02c61b4>] acpi_ps_execute_method+0x190/0x248
[<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
[<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
[<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
[<b02cf9de>] thermal_get_temp+0x34/0x5a
[<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
[<b03f6fcd>] thermal_zone_device_check+0xd/0x10
[<b013bd2c>] process_one_work+0x18c/0x3c0
[<b013e697>] worker_thread+0x107/0x310
[<b0141cac>] kthread+0x7c/0x90
[<b055e102>] kernel_thread_helper+0x6/0xd
--
Sitsofe | http://sucs.org/~sits/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmemleaks related to ACPI psparse
2011-09-16 7:22 kmemleaks related to ACPI psparse Sitsofe Wheeler
@ 2011-09-16 7:29 ` Lin Ming
2011-09-16 9:02 ` Sitsofe Wheeler
0 siblings, 1 reply; 5+ messages in thread
From: Lin Ming @ 2011-09-16 7:29 UTC (permalink / raw)
To: Sitsofe Wheeler
Cc: Moore, Robert, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
On Fri, 2011-09-16 at 15:22 +0800, Sitsofe Wheeler wrote:
> Hi,
>
> In 3.1.0-rc5-dirty the following warning appeared in dmesg:
Hi,
Please attach the acpidump output.
Regards,
Lin Ming
>
> [ 249.506212] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20110623/evregion-478)
> [ 249.506387] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.RCTP] (Node ee96daf0), AE_TIME (20110623/psparse-536)
> [ 249.506636] ACPI Error: Method parse/execution failed [\_TZ_.RTMP] (Node eeb85000), AE_TIME (20110623/psparse-536)
> [ 249.506827] ACPI Error: Method parse/execution failed [\_TZ_.TZ00._TMP] (Node eeb85190), AE_TIME (20110623/psparse-536)
> [ 249.511953] Thermal: failed to read out thermal zone 0
>
> Shortly followed by a bunch of kmemleak warnings (the initial trigger
> has not been reproducible though):
>
> unreferenced object 0xedcb81a0 (size 32):
> comm "kworker/0:2", pid 389, jiffies 4294915201 (age 649.854s)
> hex dump (first 32 bytes):
> 00 00 00 00 0d 01 70 00 00 00 00 00 00 00 00 00 ......p.........
> 00 00 00 00 d0 8d cb ed 00 00 00 00 01 00 00 00 ................
> backtrace:
> [<b0551807>] kmemleak_alloc+0x27/0x50
> [<b0196435>] kmem_cache_alloc+0xc5/0x180
> [<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
> [<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
> [<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
> [<b02c61b4>] acpi_ps_execute_method+0x190/0x248
> [<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
> [<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
> [<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
> [<b02cf9de>] thermal_get_temp+0x34/0x5a
> [<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
> [<b03f6fcd>] thermal_zone_device_check+0xd/0x10
> [<b013bd2c>] process_one_work+0x18c/0x3c0
> [<b013e697>] worker_thread+0x107/0x310
> [<b0141cac>] kthread+0x7c/0x90
> [<b055e102>] kernel_thread_helper+0x6/0xd
> unreferenced object 0xedcb8dd0 (size 32):
> comm "kworker/0:2", pid 389, jiffies 4294915201 (age 649.854s)
> hex dump (first 32 bytes):
> a0 81 cb ed 0d 01 36 00 00 00 00 00 00 00 00 00 ......6.........
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<b0551807>] kmemleak_alloc+0x27/0x50
> [<b0196435>] kmem_cache_alloc+0xc5/0x180
> [<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
> [<b02c5159>] acpi_ps_complete_this_op+0xbb/0x146
> [<b02c5202>] acpi_ps_complete_op+0x1e/0x208
> [<b02c5afd>] acpi_ps_parse_loop+0x711/0x830
> [<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
> [<b02c61b4>] acpi_ps_execute_method+0x190/0x248
> [<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
> [<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
> [<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
> [<b02cf9de>] thermal_get_temp+0x34/0x5a
> [<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
> [<b03f6fcd>] thermal_zone_device_check+0xd/0x10
> [<b013bd2c>] process_one_work+0x18c/0x3c0
> [<b013e697>] worker_thread+0x107/0x310
> unreferenced object 0xedcb84e0 (size 32):
> comm "kworker/0:2", pid 389, jiffies 4294915202 (age 649.853s)
> hex dump (first 32 bytes):
> 00 00 00 00 0d 01 a0 00 03 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 80 cb ed 00 00 00 00 02 00 00 00 ................
> backtrace:
> [<b0551807>] kmemleak_alloc+0x27/0x50
> [<b0196435>] kmem_cache_alloc+0xc5/0x180
> [<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
> [<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
> [<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
> [<b02c61b4>] acpi_ps_execute_method+0x190/0x248
> [<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
> [<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
> [<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
> [<b02cf9de>] thermal_get_temp+0x34/0x5a
> [<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
> [<b03f6fcd>] thermal_zone_device_check+0xd/0x10
> [<b013bd2c>] process_one_work+0x18c/0x3c0
> [<b013e697>] worker_thread+0x107/0x310
> [<b0141cac>] kthread+0x7c/0x90
> [<b055e102>] kernel_thread_helper+0x6/0xd
> unreferenced object 0xedcb8000 (size 32):
> comm "kworker/0:2", pid 389, jiffies 4294915209 (age 649.870s)
> hex dump (first 32 bytes):
> e0 84 cb ed 0d 01 a0 00 09 00 00 00 00 00 00 00 ................
> 00 00 00 00 90 8a cb ed 00 00 00 00 02 00 00 00 ................
> backtrace:
> [<b0551807>] kmemleak_alloc+0x27/0x50
> [<b0196435>] kmem_cache_alloc+0xc5/0x180
> [<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
> [<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
> [<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
> [<b02c61b4>] acpi_ps_execute_method+0x190/0x248
> [<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
> [<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
> [<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
> [<b02cf9de>] thermal_get_temp+0x34/0x5a
> [<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
> [<b03f6fcd>] thermal_zone_device_check+0xd/0x10
> [<b013bd2c>] process_one_work+0x18c/0x3c0
> [<b013e697>] worker_thread+0x107/0x310
> [<b0141cac>] kthread+0x7c/0x90
> [<b055e102>] kernel_thread_helper+0x6/0xd
> unreferenced object 0xedcb8a90 (size 32):
> comm "kworker/0:2", pid 389, jiffies 4294915210 (age 649.869s)
> hex dump (first 32 bytes):
> 00 80 cb ed 0d 01 70 00 14 00 00 00 00 00 00 00 ......p.........
> 00 00 00 00 40 83 cb ed 00 00 00 00 01 00 00 00 ....@...........
> backtrace:
> [<b0551807>] kmemleak_alloc+0x27/0x50
> [<b0196435>] kmem_cache_alloc+0xc5/0x180
> [<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
> [<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
> [<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
> [<b02c61b4>] acpi_ps_execute_method+0x190/0x248
> [<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
> [<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
> [<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
> [<b02cf9de>] thermal_get_temp+0x34/0x5a
> [<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
> [<b03f6fcd>] thermal_zone_device_check+0xd/0x10
> [<b013bd2c>] process_one_work+0x18c/0x3c0
> [<b013e697>] worker_thread+0x107/0x310
> [<b0141cac>] kthread+0x7c/0x90
> [<b055e102>] kernel_thread_helper+0x6/0xd
> unreferenced object 0xedcb8340 (size 32):
> comm "kworker/0:2", pid 389, jiffies 4294915210 (age 649.869s)
> hex dump (first 32 bytes):
> 90 8a cb ed 0d 01 2d 00 15 00 00 00 00 00 00 00 ......-.........
> 00 00 00 00 85 17 f8 ef 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<b0551807>] kmemleak_alloc+0x27/0x50
> [<b0196435>] kmem_cache_alloc+0xc5/0x180
> [<b02c5faf>] acpi_ps_alloc_op+0x82/0x84
> [<b02c55d5>] acpi_ps_parse_loop+0x1e9/0x830
> [<b02c4e1e>] acpi_ps_parse_aml+0x87/0x235
> [<b02c61b4>] acpi_ps_execute_method+0x190/0x248
> [<b02c1f8b>] acpi_ns_evaluate+0xc7/0x179
> [<b02c1abd>] acpi_evaluate_object+0xd1/0x1c0
> [<b02ad0aa>] acpi_evaluate_integer+0x2a/0x51
> [<b02cf9de>] thermal_get_temp+0x34/0x5a
> [<b03f6d49>] thermal_zone_device_update+0x29/0x2a0
> [<b03f6fcd>] thermal_zone_device_check+0xd/0x10
> [<b013bd2c>] process_one_work+0x18c/0x3c0
> [<b013e697>] worker_thread+0x107/0x310
> [<b0141cac>] kthread+0x7c/0x90
> [<b055e102>] kernel_thread_helper+0x6/0xd
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmemleaks related to ACPI psparse
2011-09-16 7:29 ` Lin Ming
@ 2011-09-16 9:02 ` Sitsofe Wheeler
2011-10-04 6:37 ` Sitsofe Wheeler
0 siblings, 1 reply; 5+ messages in thread
From: Sitsofe Wheeler @ 2011-09-16 9:02 UTC (permalink / raw)
To: Lin Ming
Cc: Moore, Robert, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
Hello,
On Fri, Sep 16, 2011 at 03:29:54PM +0800, Lin Ming wrote:
> On Fri, 2011-09-16 at 15:22 +0800, Sitsofe Wheeler wrote:
> >
> > In 3.1.0-rc5-dirty the following warning appeared in dmesg:
>
> Please attach the acpidump output.
My EeePC 900's acpidump output should be attached as a gz.
--
Sitsofe | http://sucs.org/~sits/
[-- Attachment #2: eeepc900-acpidump.gz --]
[-- Type: application/octet-stream, Size: 33871 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmemleaks related to ACPI psparse
2011-09-16 9:02 ` Sitsofe Wheeler
@ 2011-10-04 6:37 ` Sitsofe Wheeler
2011-10-05 11:54 ` Lin Ming
0 siblings, 1 reply; 5+ messages in thread
From: Sitsofe Wheeler @ 2011-10-04 6:37 UTC (permalink / raw)
To: Sitsofe Wheeler
Cc: Lin Ming, Moore, Robert, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Hi,
On Fri, Sep 16, 2011 at 10:02:36AM +0100, Sitsofe Wheeler wrote:
>
> On Fri, Sep 16, 2011 at 03:29:54PM +0800, Lin Ming wrote:
> > On Fri, 2011-09-16 at 15:22 +0800, Sitsofe Wheeler wrote:
> > >
> > > In 3.1.0-rc5-dirty the following warning appeared in dmesg:
> >
> > Please attach the acpidump output.
>
> My EeePC 900's acpidump output should be attached as a gz.
This issue hasn't happened since - is it worth ignoring this for now?
--
Sitsofe | http://sucs.org/~sits/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: kmemleaks related to ACPI psparse
2011-10-04 6:37 ` Sitsofe Wheeler
@ 2011-10-05 11:54 ` Lin Ming
0 siblings, 0 replies; 5+ messages in thread
From: Lin Ming @ 2011-10-05 11:54 UTC (permalink / raw)
To: Sitsofe Wheeler
Cc: Moore, Robert, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
On Tue, 2011-10-04 at 14:37 +0800, Sitsofe Wheeler wrote:
> Hi,
>
> On Fri, Sep 16, 2011 at 10:02:36AM +0100, Sitsofe Wheeler wrote:
> >
> > On Fri, Sep 16, 2011 at 03:29:54PM +0800, Lin Ming wrote:
> > > On Fri, 2011-09-16 at 15:22 +0800, Sitsofe Wheeler wrote:
> > > >
> > > > In 3.1.0-rc5-dirty the following warning appeared in dmesg:
> > >
> > > Please attach the acpidump output.
> >
> > My EeePC 900's acpidump output should be attached as a gz.
>
> This issue hasn't happened since - is it worth ignoring this for now?
Yes.
Thanks for test.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-10-05 11:54 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-16 7:22 kmemleaks related to ACPI psparse Sitsofe Wheeler
2011-09-16 7:29 ` Lin Ming
2011-09-16 9:02 ` Sitsofe Wheeler
2011-10-04 6:37 ` Sitsofe Wheeler
2011-10-05 11:54 ` Lin Ming
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox