Bug#679158: asus-wmi: use ASUS_WMI_METHODID_DSTS2 as default DSTS ID

[Jonathan Nieder <jrnieder@gmail.com>]

# letting version tracking do its work
tags 679158 - experimental
tags 679158 + moreinfo
quit

Hi Carsten,

Carsten Otto wrote:

> ** Tainted: F (2)
>  * Module has been forcibly loaded.
[...]
> [ 8266.250230] asus_wmi: module_layout: kernel tainted.
> [ 8266.250238] Disabling lock debugging due to kernel taint
> [ 8266.250245] asus_wmi: version magic '3.4.1 SMP mod_unload ' should be '3.4-trunk-amd64 SMP mod_unload modversions '
> [ 8278.852163] asus_wmi: version magic '3.4.1 SMP mod_unload ' should be '3.4-trunk-amd64 SMP mod_unload modversions '

The kernel package has an asus_wmi module, but you seem to be loading
one from somewhere else.  Can you say more about what happened?

What symptoms did you experience?  Which kernel version did the
problem start with --- is this a regression?  Once we understand the
nature of the problem, we can move on to figuring out how to fix it.

The patch you pointed to addresses a symptom that would be signalled
by "Can't find DSTS" in the kernel log, which I don't see in yours.

Thanks for your interest and hope that helps,
Jonathan