[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[BUG] console-kit-daemon



Maybe...  Might not be "consolekit" at all...

I used "ssh" to login on my alpha this morning, and a simple "ps -ef"
triggered the following (retrieved from the physical console when the
"ps" hung):

Unable to handle kernel paging request at virtual address 0000000000000010
console-kit-dae(2477): Oops 0
pc = [<fffffc0000315838>]  ra = [<fffffc000031d8d4>]  ps = 0007    Tainted: G        W  
pc is at process_mcheck_info+0x48/0x310
ra is at cia_machine_check+0x94/0xb0
v0 = 0000000000000004  t0 = 0000000000000630  t1 = 0000000000000630
t2 = 0000000000000001  t3 = 0000000000008000  t4 = fffffc0000000000
t5 = 2fd2fd2fd2fd2fd3  t6 = 0000000000000096  t7 = fffffc001b21c000
s0 = 0000000000000000  s1 = fffffc00008240d0  s2 = 0000000000000000
s3 = 0000000000000000  s4 = 0000000000000000  s5 = fffffc0000984de8
s6 = 6db6db6db6db6db7
a0 = 0000000000000630  a1 = 0000000000000000  a2 = fffffc000073251d
a3 = 0000000000000000  a4 = 0000000000000000  a5 = 0000000000005108
t8 = fffffc0000984e04  t9 = 0000000000200200  t10= fffffc0023005a50
t11= 0000000000000001  pv = fffffc00003157f0  at = fffffc0023005a60
gp = fffffc00008588f0  sp = fffffc001b21f790
Disabling lock debugging due to kernel taint
Trace:
[<fffffc000031d8d4>] cia_machine_check+0x94/0xb0
[<fffffc0000315c80>] do_entInt+0x180/0x1e0
[<fffffc0000310dc0>] ret_from_sys_call+0x0/0x10
[<fffffc0000371c18>] get_page_from_freelist+0x2d8/0x5a0
[<fffffc00004dede0>] clear_page+0x0/0xc4
[<fffffc00004dee04>] clear_page+0x24/0xc4
[<fffffc00003728bc>] __alloc_pages_nodemask+0x11c/0x770
[<fffffc0000372f2c>] __get_free_pages+0x1c/0x60
[<fffffc0000372f10>] __get_free_pages+0x0/0x60
[<fffffc0000372f2c>] __get_free_pages+0x1c/0x60
[<fffffc000032ff7c>] __do_softirq+0x16c/0x1d0
[<fffffc0000330198>] do_softirq+0x58/0x60
[<fffffc0000330198>] do_softirq+0x58/0x60
[<fffffc0000315698>] handle_irq+0x88/0xe0
[<fffffc0000315bc4>] do_entInt+0xc4/0x1e0
[<fffffc0000372f2c>] __get_free_pages+0x1c/0x60
[<fffffc0000310dc0>] ret_from_sys_call+0x0/0x10
[<fffffc000039c63c>] swap_duplicate+0x2c/0x80
[<fffffc00003882e4>] __pte_alloc+0x34/0x170
[<fffffc00003891dc>] copy_pte_range+0x37c/0x3b0
[<fffffc000038a174>] copy_page_range+0x194/0x240
[<fffffc00003275e8>] dup_mm+0x348/0x510
[<fffffc0000328448>] copy_process+0xbb8/0xe90
[<fffffc00003288b0>] do_fork+0xa0/0x300
[<fffffc0000312f9c>] alpha_clone+0x3c/0x60
[<fffffc00003bb968>] vfs_readdir+0xf8/0x130
[<fffffc00003bb6f0>] filldir+0x0/0xc0
[<fffffc00003112c0>] sys_clone+0x10/0x20
[<fffffc0000310da4>] entSys+0xa4/0xc0

Code: a75e0000  a53e0008  a55e0010  23de0020  6bfa8001  a55d07d0 <a2910010> 261dffee 
note: console-kit-dae[2477] exited with preempt_count 1
BUG: scheduling while atomic: console-kit-dae/2477/0x00000001
Modules linked in: sit tunnel4 radeon ttm drm_kms_helper nfsd drm i2c_algo_bit lockd power_supply auth_rpcgss sunrpc exportfs parport_pc lp parport fuse nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack xt_tcpudp xt_limit ip6table_filter ip6_tables x_tables ipv6 loop evdev pcspkr unix
pc = [<fffffc00004dee04>]  ra = [<fffffc0000371c18>]  ps = 0000    Tainted: G      D W  
pc is at clear_page+0x24/0xc4
ra is at get_page_from_freelist+0x2d8/0x5a0
v0 = 0000000000000040  t0 = fffffc000085bbf0  t1 = fffffc0000984de8
t2 = 0000000000000001  t3 = 0000000000008000  t4 = fffffc0000000000
t5 = 2fd2fd2fd2fd2fd3  t6 = 0000000000000096  t7 = fffffc001b21c000
a0 = fffffc0008e37000  a1 = 0000000000000000  a2 = 00000000000001dd
a3 = fffffc00008330f8  a4 = 0000000000000000  a5 = 0000000000005108
t8 = fffffc0000984e04  t9 = 0000000000200200  t10= fffffc0023005a50
t11= 0000000000000001  pv = fffffc00004dede0  at = fffffc0023005a60
gp = fffffc00008588f0  sp = fffffc001b21f8d8

Kernel is version 3.1.0-rc9 plus the new accept4 and sendmmsg syscalls.
Further attempts to generate a process listing resulted in more hung
consoles, which meant the machine hung when I attempted a graceful reboot.
Ultimately had to hit the reset switch :-(.  Will try building 3.1.0-rc10
today and see if the problem recurs.

--Bob


Reply to: