linux-kernel - Re: [Regression] 2.6.37-rc1: Lenovo T61 mute button does not work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 06 Dec 2010 17:42:56 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	Lukas Hejtmanek <xhejtman@....muni.cz>
Cc:	"Moore, Robert" <robert.moore@...el.com>,
	"Brown, Len" <len.brown@...el.com>,
	Calvin Walton <calvin.walton@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Regression] 2.6.37-rc1: Lenovo T61 mute button does not work

On Mon, 2010-12-06 at 17:31 +0800, Lukas Hejtmanek wrote:
> On Mon, Dec 06, 2010 at 09:37:04AM +0800, Lin Ming wrote:
> > > which apparently does not work with Lenovo T61.
> > 
> > I'm looking at this regression.
> 
> I did some debugging. It looks like this:
> [    0.000000] ACPI: DMI detected: Lenovo ThinkPad T61
> [    0.000000] ACPI: Set_osi_linux Added _OSI(Linux)
> [    0.000000] Pid: 0, comm: swapper Not tainted 2.6.37-rc3+ #122
> [    0.000000] Call Trace:
> [    0.000000]  [<ffffffff8162c0a1>] ? set_osi_linux+0x4b/0x6b
> [    0.000000]  [<ffffffff8162bbe7>] ? dmi_enable_osi_linux+0x11/0x18
> [    0.000000]  [<ffffffff812f7313>] ? dmi_check_system+0x33/0x50
> [    0.000000]  [<ffffffff8162bdc2>] ? acpi_blacklisted+0x16a/0x190
> [    0.000000]  [<ffffffff81617b6e>] ? acpi_boot_table_init+0x3a/0x75
> [    0.000000]  [<ffffffff81611cf3>] ? setup_arch+0x6d5/0x7a8
> [    0.000000]  [<ffffffff814072f2>] ? printk+0x40/0x46
> [    0.000000]  [<ffffffff816108de>] ? start_kernel+0xbe/0x323
> [    0.000000]  [<ffffffff816103de>] ? x86_64_start_kernel+0xf9/0xff
> 
> after this call, osi_linux.dmi is set.
> 
> However, after this call:
> [    0.186721] Call Trace:
> [    0.186721]  [<ffffffff8120ecad>] ? acpi_install_interface_handler+0x4d/0x56
> [    0.186750]  [<ffffffff8162c0a1>] ? set_osi_linux+0x4b/0x6b
> [    0.186777]  [<ffffffff811edefa>] ? acpi_os_initialize1+0x10f/0x13d
> [    0.186803]  [<ffffffff8162c3fa>] ? acpi_bus_init+0xa/0x1e2
> [    0.186829]  [<ffffffff811c498c>] ? kobject_create_and_add+0x3c/0x80
> [    0.186855]  [<ffffffff8162c63b>] ? acpi_init+0x69/0xdf
> [    0.186880]  [<ffffffff810002da>] ? do_one_initcall+0x3a/0x170
> [    0.186906]  [<ffffffff81610c75>] ? kernel_init+0x132/0x1be
> [    0.186932]  [<ffffffff81003b94>] ? kernel_thread_helper+0x4/0x10
> [    0.186958]  [<ffffffff81610b43>] ? kernel_init+0x0/0x1be
> [    0.187577]  [<ffffffff81003b90>] ? kernel_thread_helper+0x0/0x10
> 
> osi_linux.cmdline is set.

Do you have acpi_osi=Linux in kernel boot parameters?

Please attach the dmesg.

Thanks.

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