You are not logged in.

#1 2013-08-21 15:24:32

warm
Member
Registered: 2009-06-23
Posts: 45

Strange kernel message in dmesg

At every boot I get the next message in dmesg but all seems to be working after that:

...
[    5.108514] asus_wmi: SFUN value: 0x0
[    5.120764] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input8
[    5.140135] asus_wmi: Disabling ACPI video driver
[    5.147464] Adding 2097148k swap on /dev/sda1.  Priority:-1 extents:1 across:2097148k SSFS
[    5.188620] ------------[ cut here ]------------
[    5.188799] WARNING: at kernel/mutex.c:341 __mutex_lock_slowpath+0x27f/0x340()
[    5.189017] DEBUG_LOCKS_WARN_ON(in_interrupt())
[    5.189155] Modules linked in:
[    5.189261]  eeepc_wmi(+) asus_wmi sparse_keymap arc4 ath9k ath9k_common coretemp ath9k_hw microcode ath uvcvideo vid
eobuf2_vmalloc videobuf2_memops i2c_i801(+) psmouse videobuf2_core snd_hda_codec_hdmi serio_raw of_i2c pcspkr mac80211 v
ideodev snd_hda_codec_realtek media snd_hda_intel(+) cfg80211 snd_hda_codec snd_hwdep atl1c lpc_ich rfkill snd_pcm snd_p
age_alloc snd_timer snd soundcore thermal evdev ac battery wmi button acpi_cpufreq mperf processor btrfs crc32c libcrc32
c xor zlib_deflate raid6_pq sd_mod ahci libahci libata uhci_hcd ehci_pci ehci_hcd scsi_mod usbcore usb_common gma500_gfx
 video i2c_algo_bit drm_kms_helper drm agpgart i2c_core
[    5.191891] CPU: 3 PID: 188 Comm: systemd-udevd Not tainted 3.10.7-1-ARCH #1
[    5.192121] Hardware name: ASUSTeK COMPUTER INC. X101CH/X101CH, BIOS X101CH.0501 01/06/2012
[    5.195414]  f657ded0 f657ded0 f657de98 c0505c7e f657dec0 c013aeee c05e5ccb f657deec
[    5.199086]  00000155 c050860f c050860f f67da418 f67da418 80808081 f657ded8 c013af43
[    5.203031]  00000009 f657ded0 c05e5ccb f657deec f657df1c c050860f c05e5ce3 00000155
[    5.206860] Call Trace:
[    5.210724]  [<c0505c7e>] dump_stack+0x16/0x18
[    5.214682]  [<c013aeee>] warn_slowpath_common+0x5e/0x80
[    5.218403]  [<c050860f>] ? __mutex_lock_slowpath+0x27f/0x340
[    5.222596]  [<c050860f>] ? __mutex_lock_slowpath+0x27f/0x340
[    5.226856]  [<c013af43>] warn_slowpath_fmt+0x33/0x40
[    5.230941]  [<c050860f>] __mutex_lock_slowpath+0x27f/0x340
[    5.235158]  [<c03ecb6e>] ? ps2_handle_ack+0x6e/0xd0
[    5.238905]  [<c05086e0>] mutex_lock+0x10/0x20
[    5.242375]  [<f814d4d0>] do_gma_backlight_set+0x20/0x40 [gma500_gfx]
[    5.245979]  [<f814d57f>] gma_backlight_set+0x2f/0x40 [gma500_gfx]
[    5.249656]  [<f815c61e>] psb_intel_opregion_asle_intr+0xae/0x100 [gma500_gfx]
[    5.253466]  [<f815ab87>] psb_irq_handler+0x1a7/0x1b0 [gma500_gfx]
[    5.257344]  [<c01b315d>] handle_irq_event_percpu+0x3d/0x1f0
[    5.261600]  [<c01b3341>] handle_irq_event+0x31/0x50
[    5.265585]  [<c01b5700>] ? handle_level_irq+0xb0/0xb0
[    5.269632]  [<c01b5766>] handle_edge_irq+0x66/0x120
[    5.273763]  <IRQ>  [<c051154c>] ? do_IRQ+0x3c/0xb0
[    5.277971]  [<c05113f3>] ? common_interrupt+0x33/0x38
[    5.282235]  [<c050a670>] ? _raw_spin_unlock_irqrestore+0x20/0x40
[    5.286632]  [<c04164e2>] ? pci_conf1_write+0xa2/0xf0
[    5.291008]  [<c04197b8>] ? raw_pci_write+0x68/0x80
[    5.295311]  [<c036529e>] ? acpi_os_write_pci_configuration+0x62/0x79
[    5.299622]  [<c037b9af>] ? acpi_ex_system_io_space_handler+0x42/0x42
[    5.303848]  [<c037b9e3>] ? acpi_ex_pci_config_space_handler+0x34/0x51
[    5.308035]  [<c0375a73>] ? acpi_ev_address_space_dispatch+0x1a3/0x1f5
[    5.312119]  [<c037b780>] ? acpi_ex_do_logical_op+0x162/0x162
[    5.316025]  [<c0378928>] ? acpi_ex_access_region+0x1f0/0x279
[    5.319760]  [<c0378928>] ? acpi_ex_access_region+0x1f0/0x279
[    5.323284]  [<c0378d83>] ? acpi_ex_field_datum_io+0x108/0x1ce
[    5.326683]  [<c0378f34>] ? acpi_ex_write_with_update_rule+0xeb/0xf3
[    5.329915]  [<c0378928>] ? acpi_ex_access_region+0x1f0/0x279
[    5.333067]  [<c0378f34>] ? acpi_ex_write_with_update_rule+0xeb/0xf3
[    5.336167]  [<c0378c63>] ? acpi_ex_insert_into_field+0x2b2/0x2ca
[    5.339303]  [<c0378715>] ? acpi_ex_write_data_to_field+0x18e/0x1b1
[    5.342261]  [<c03895d3>] ? acpi_ut_allocate_object_desc_dbg+0x3b/0x70
[    5.345211]  [<c03895d3>] ? acpi_ut_allocate_object_desc_dbg+0x3b/0x70
[    5.348026]  [<c037c5f5>] ? acpi_ex_store_object_to_node+0x91/0xeb
[    5.350847]  [<c037c709>] ? acpi_ex_store+0xba/0x219
[    5.353664]  [<c0379e1e>] ? acpi_ex_opcode_1A_1T_1R+0x426/0x53a
[    5.356463]  [<c037c27a>] ? acpi_ex_resolve_operands+0x1db/0x4c5
[    5.359309]  [<c0372b5c>] ? acpi_ds_exec_end_op+0xc4/0x3a8
[    5.362131]  [<c038291d>] ? acpi_ps_get_next_arg+0x300/0x35f
[    5.364970]  [<c0383ae0>] ? acpi_ps_append_arg+0x1e/0x82
[    5.367755]  [<c0382e13>] ? acpi_ps_parse_loop+0x497/0x4d4
[    5.370527]  [<c0373f06>] ? acpi_ds_delete_walk_state+0xc1/0xc7
[    5.373281]  [<c038376e>] ? acpi_ps_parse_aml+0x8a/0x23c
[    5.376012]  [<c0383ed2>] ? acpi_ps_execute_method+0x19e/0x23c
[    5.378727]  [<c037f04c>] ? acpi_ns_evaluate+0xb4/0x19a
[    5.381365]  [<c03815a3>] ? acpi_evaluate_object+0x9b/0x1ee
[    5.383983]  [<c0381604>] ? acpi_evaluate_object+0xfc/0x1ee
[    5.386587]  [<f906886b>] ? wmi_evaluate_method+0xdb/0xf0 [wmi]
[    5.389204]  [<fa32006b>] ? asus_wmi_evaluate_method+0x4b/0xb0 [asus_wmi]
[    5.391904]  [<fa320416>] ? update_bl_status+0x86/0xe0 [asus_wmi]
[    5.394591]  [<fa3219ae>] ? asus_wmi_probe+0x52e/0xbc0 [asus_wmi]
[    5.397246]  [<c03ce5ee>] ? platform_drv_probe+0x2e/0x60
[    5.399887]  [<c03cc6d9>] ? driver_probe_device+0x79/0x360
[    5.402516]  [<c03cca71>] ? __driver_attach+0x71/0x80
[    5.405174]  [<c03cca00>] ? __device_attach+0x40/0x40
[    5.407750]  [<c03caaf7>] ? bus_for_each_dev+0x47/0x80
[    5.410321]  [<c03cc1de>] ? driver_attach+0x1e/0x20
[    5.412872]  [<c03cca00>] ? __device_attach+0x40/0x40
[    5.415418]  [<c03cbe17>] ? bus_add_driver+0x1c7/0x280
[    5.417965]  [<c03cd04a>] ? driver_register+0x6a/0x130
[    5.420664]  [<c03ce3d0>] ? platform_driver_register+0x40/0x50
[    5.423273]  [<c03ce487>] ? platform_driver_probe+0x17/0x80
[    5.425871]  [<c03ce882>] ? platform_create_bundle+0x82/0xa0
[    5.428446]  [<fa321480>] ? asus_wmi_hwmon_exit.isra.8+0x30/0x30 [asus_wmi]
[    5.431113]  [<fa32e000>] ? 0xfa32dfff
[    5.433706]  [<fa321024>] ? asus_wmi_register_driver+0x54/0x70 [asus_wmi]
[    5.436417]  [<fa32e00d>] ? eeepc_wmi_init+0xd/0xf [eeepc_wmi]
[    5.439103]  [<c01001b2>] ? do_one_initcall+0xb2/0x170
[    5.441775]  [<c0160364>] ? __blocking_notifier_call_chain+0x44/0x60
[    5.444580]  [<c019aaa1>] ? load_module+0x19f1/0x2300
[    5.447344]  [<c019b43f>] ? SyS_init_module+0x8f/0xf0
[    5.450109]  [<c0510f0d>] ? sysenter_do_call+0x12/0x28
[    5.452862] ---[ end trace 2c35b0a383426af0 ]---
[    5.461638] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: discard,data=ordered
[    5.595302] systemd-logind[251]: Watching system buttons on /dev/input/event4 (Lid Switch)
[    5.595786] systemd-logind[251]: Watching system buttons on /dev/input/event3 (Sleep Button)
...

What does this mean and how to solve the problem ?

I had installed SSD drive and reinstalled Archlinux. Before that there was no such messages.

Offline

#2 2013-08-22 02:39:15

Pse
Member
Registered: 2008-03-15
Posts: 413

Re: Strange kernel message in dmesg

Looks like a kernel bug related to the backlight in your Asus laptop. If you're not experiencing any issues other than the report in the logs, I'd wait until a new kernel is out. Otherwise you might want to try with one of the kernel release candidates or git versions.

Offline

#3 2013-08-22 04:57:32

warm
Member
Registered: 2009-06-23
Posts: 45

Re: Strange kernel message in dmesg

Pse wrote:

Looks like a kernel bug related to the backlight in your Asus laptop. If you're not experiencing any issues other than the report in the logs, I'd wait until a new kernel is out. Otherwise you might want to try with one of the kernel release candidates or git versions.

I've waited several kernel versions and this issue still going.

backlight - You mean screen backlight or something else ?

What is the module name ? I'll try to blacklist it.

Offline

#4 2013-08-22 18:32:41

Pse
Member
Registered: 2008-03-15
Posts: 413

Re: Strange kernel message in dmesg

Asus WMI seems to be involved in that backtrace (module asus_wmi). It controls access to special keys and other (usually) laptop related stuff. I'd get the latest git version for the kernel and post in the kernel mailing list.

Offline

#5 2013-08-22 18:46:46

mich41
Member
Registered: 2012-06-22
Posts: 796

Re: Strange kernel message in dmesg

Looks like gma500 IRQ handler calls some backlight code which tries to lock some mutex. This could break the IRQ handler if mutex was already locked and hence the warning.

IOW, either gma500 shouldn't call backlight subsystem from IRQ or backlight subsystem shouldn't use mutexes here. I'd report this to gma500 guys.

Last edited by mich41 (2013-08-22 18:49:05)

Offline

Board footer

Powered by FluxBB