[FDOM] qpe crashes, no pin entry dialog

Konstantin Chaosspawn23 at gmx.net
Tue Sep 23 12:24:37 CEST 2008


I installed FDOM on my SD Card (2 GB), and at first everything (including PIN
entry) was working fine, but now (I did an opkg upgrade at some point, but I'm
not sure if this is in any way connected) after booting the PIN-entry dialog
doesn't pop up, and after a while a message stating that qpe died pops up.

However, I noticed something suspicious in the dmesg output:

[   72.370000] BUG: sleeping function called from invalid context at
kernel/mutex.c:207
[   72.370000] in_atomic():0, irqs_disabled():128
[   72.370000] 2 locks held by gesd/1426:
[   72.370000]  #0:  (&evdev->mutex){....}, at: [<c01d3f94>] evdev_open+0xec/0x18c
[   72.370000]  #1:  (&dev->mutex){....}, at: [<c01cefe4>]
input_open_device+0x24/0xac
[   72.370000] [<c002dbfc>] (dump_stack+0x0/0x14) from [<c0042d34>]
(__might_sleep+0xdc/0xf8)
[   72.370000] [<c0042c58>] (__might_sleep+0x0/0xf8) from [<c02d0d14>]
(mutex_lock_nested+0x28/0x2a0)
[   72.370000]  r5:c7d76c2c r4:00000047
[   72.370000] [<c02d0cec>] (mutex_lock_nested+0x0/0x2a0) from [<c01d4f78>]
(reg_set_bit_mask+0x30/0x6c)
[   72.370000] [<c01d4f48>] (reg_set_bit_mask+0x0/0x6c) from [<c01d503c>]
(lis302dl_input_open+0x30/0x58)
[   72.370000]  r8:c7d778e0 r7:c7d74660 r6:00000000 r5:c7d76c20 r4:a0000013
[   72.370000] [<c01d500c>] (lis302dl_input_open+0x0/0x58) from [<c01cf034>]
(input_open_device+0x74/0xac)
[   72.370000]  r5:c7d7781c r4:c7d74000
[   72.370000] [<c01cefc0>] (input_open_device+0x0/0xac) from [<c01d3fc8>]
(evdev_open+0x120/0x18c)
[   72.370000]  r7:00000000 r6:c69ab000 r5:c7d77800 r4:c7d77894
[   72.370000] [<c01d3ea8>] (evdev_open+0x0/0x18c) from [<c01d0c3c>]
(input_open_file+0xf0/0x1b4)
[   72.370000] [<c01d0b4c>] (input_open_file+0x0/0x1b4) from [<c009d534>]
(chrdev_open+0x198/0x1e0)
[   72.370000]  r7:c68353c0 r6:c6892108 r5:c7c6ec60 r4:00000000
[   72.370000] [<c009d39c>] (chrdev_open+0x0/0x1e0) from [<c0098770>]
(__dentry_open+0x140/0x228)
[   72.370000]  r7:c009d39c r6:c6892108 r5:00000000 r4:c68353c0
[   72.370000] [<c0098630>] (__dentry_open+0x0/0x228) from [<c0098904>]
(nameidata_to_filp+0x34/0x4c)
[   72.370000] [<c00988d0>] (nameidata_to_filp+0x0/0x4c) from [<c009895c>]
(do_filp_open+0x40/0x48)
[   72.370000]  r4:00000000
[   72.370000] [<c009891c>] (do_filp_open+0x0/0x48) from [<c00989bc>]
(do_sys_open+0x58/0xe8)
[   72.370000]  r5:40ba84d8 r4:00000000
[   72.370000] [<c0098964>] (do_sys_open+0x0/0xe8) from [<c0098a84>]
(sys_open+0x24/0x28)
[   72.370000]  r8:c00290a8 r7:00000005 r6:00000002 r5:bed0ce44 r4:00012574
[   72.370000] [<c0098a60>] (sys_open+0x0/0x28) from [<c0028f00>]
(ret_fast_syscall+0x0/0x2c)

Maybe that is connected to my problem in any way?
Is this a known problem, or can any of you make something out of this?

Regards,
Konstantin



More information about the support mailing list