Re: Possible dcache BUG

[Andrew Morton]

"Udo A. Steinberg" <us15@xxxxxxxxxxxxxxxxxxxx> wrote:
>
>  However, then as slab usage went skyrocket after 3 days, I started logging
>  these:
> 
>   [<c013e98f>] __kmalloc+0x6f/0x80
>   [<c0217af9>] acpi_os_allocate+0xa/0xb
>   [<c022b9b6>] acpi_ut_callocate+0x30/0x7a
>   [<c022b840>] acpi_ut_acquire_from_cache+0x9d/0xaa
>   [<c022c7d8>] acpi_ut_create_generic_state+0xa/0x12
>   [<c021b0b2>] acpi_ds_result_stack_push+0x8/0x25
>   [<c021b268>] acpi_ds_create_walk_state+0x53/0x70
>   [<c0227913>] acpi_ps_delete_parse_tree+0x20/0x89
>   [<c0227238>] acpi_ps_parse_loop+0x550/0x7bb
>   [<c02274f0>] acpi_ps_parse_aml+0x4d/0x1a1
>   [<c0219dd4>] acpi_ds_call_control_method+0xd3/0x1b3
>   [<c0227505>] acpi_ps_parse_aml+0x62/0x1a1
>   [<c0227d1f>] acpi_psx_execute+0x13b/0x194
>   [<c0225212>] acpi_ns_execute_control_method+0x3b/0x47
>   [<c02251c0>] acpi_ns_evaluate_by_handle+0x6f/0x86
>   [<c02250cd>] acpi_ns_evaluate_relative+0xa9/0xc3
>   [<c02249c3>] acpi_evaluate_object+0xf3/0x1a0
>   [<c0160f56>] link_path_walk+0xbe6/0xe70
>   [<c022f496>] acpi_battery_get_status+0x68/0x102
>   [<c022f9b6>] acpi_battery_read_state+0x88/0x275
>   [<c018124b>] proc_file_read+0xbb/0x250
>   [<c0152ea1>] vfs_read+0xd1/0x130
>   [<c0153171>] sys_read+0x41/0x70
>   [<c01040db>] syscall_call+0x7/0xb

great, thanks for working that out.

Random guess: acpi_evaluate_object() is returning an error but is
allocating memory anyway.

In acpi_battery_get_status():

	status = acpi_evaluate_object(battery->handle, "_BST", NULL, &buffer);
	if (ACPI_FAILURE(status)) {
		ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Error evaluating _BST\n"));
		return_VALUE(-ENODEV);
	}

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