Possible bug in 3.4.9 and maybe 3.5.3?
I was going through the logs after a graphics (xorg/radeon/ttm) -this happened today 19/8- related kernel panic and i discovered this from yesterday:
Aug 18 21:49:07 mainland kernel: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:3406]
Aug 18 21:49:07 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:07 mainland kernel: CPU 2
Aug 18 21:49:07 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:07 mainland kernel:
Aug 18 21:49:07 mainland kernel: Pid: 3406, comm: kworker/2:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:49:07 mainland kernel: RIP: 0010:[<ffffffff8146ad75>] [<ffffffff8146ad75>] _raw_spin_lock+0x35/0x40
Aug 18 21:49:07 mainland kernel: RSP: 0018:ffff88025ca7bc00 EFLAGS: 00000297
Aug 18 21:49:07 mainland kernel: RAX: 0000000000000069 RBX: ffff88031ec8e940 RCX: ffff8801584c0580
Aug 18 21:49:07 mainland kernel: RDX: 000000000000006a RSI: 0000000000000008 RDI: ffffffff81a806fc
Aug 18 21:49:07 mainland kernel: RBP: ffff88025ca7bc00 R08: ffffffff81618d40 R09: 0000000000000000
Aug 18 21:49:07 mainland kernel: R10: ffff8802f3ebcf10 R11: 0000000000000000 R12: ffff88025ca7bbd0
Aug 18 21:49:07 mainland kernel: R13: 0000000000000000 R14: 0200000000000000 R15: 0000000000000000
Aug 18 21:49:07 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Aug 18 21:49:07 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 18 21:49:07 mainland kernel: CR2: 00007f850dc67000 CR3: 000000000380b000 CR4: 00000000001407e0
Aug 18 21:49:07 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:49:07 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:49:07 mainland kernel: Process kworker/2:2 (pid: 3406, threadinfo ffff88025ca7a000, task ffff8802c7cfdf40)
Aug 18 21:49:07 mainland kernel: Stack:
Aug 18 21:49:07 mainland kernel: ffff88025ca7bc10 ffffffff811b8955 ffff88025ca7bcf0 ffffffff811badd2
Aug 18 21:49:07 mainland kernel: ffff88025ca7bc50 ffffffff81159f6d ffff88025ca7bc60 ffff88029b923210
Aug 18 21:49:07 mainland kernel: ffff88025ca7bfd8 ffff88025ca7bfd8 ffff88025ca7bc70 ffffffff8118492b
Aug 18 21:49:07 mainland kernel: Call Trace:
Aug 18 21:49:07 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:07 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
Aug 18 21:49:07 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:07 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:07 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:07 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:07 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:07 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:07 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:07 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:07 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:07 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:07 mainland kernel: Code: 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00 00 f3 90
Aug 18 21:49:07 mainland kernel: Call Trace:
Aug 18 21:49:07 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:07 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
Aug 18 21:49:07 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:07 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:07 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:07 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:07 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:07 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:07 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:07 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:07 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:07 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:07 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:08 mainland kernel: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:2:3797]
Aug 18 21:49:08 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:08 mainland kernel: CPU 3
Aug 18 21:49:08 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:08 mainland kernel:
Aug 18 21:49:08 mainland kernel: Pid: 3797, comm: kworker/3:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:49:08 mainland kernel: RIP: 0010:[<ffffffff811badeb>] [<ffffffff811badeb>] locks_remove_flock+0xdb/0x130
Aug 18 21:49:08 mainland kernel: RSP: 0018:ffff880259133c20 EFLAGS: 00000286
Aug 18 21:49:08 mainland kernel: RAX: ffff88029b923830 RBX: ffff880259133fd8 RCX: ffff8801584c0550
Aug 18 21:49:08 mainland kernel: RDX: 0000000000000069 RSI: 0000000000000008 RDI: ffffffff81a806fc
Aug 18 21:49:08 mainland kernel: RBP: ffff880259133cf0 R08: ffffffff81618d40 R09: 0000000000000000
Aug 18 21:49:08 mainland kernel: R10: ffff88025f179610 R11: 0000000000000000 R12: ffff880259133bf0
Aug 18 21:49:08 mainland kernel: R13: 0000000100000002 R14: 0000000000000000 R15: 0000000000000297
Aug 18 21:49:08 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ecc0000(0000) knlGS:0000000000000000
Aug 18 21:49:08 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 18 21:49:08 mainland kernel: CR2: 00007f8507a34000 CR3: 000000000380b000 CR4: 00000000001407e0
Aug 18 21:49:08 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:49:08 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:49:08 mainland kernel: Process kworker/3:2 (pid: 3797, threadinfo ffff880259132000, task ffff88025ae727b0)
Aug 18 21:49:08 mainland kernel: Stack:
Aug 18 21:49:08 mainland kernel: ffff880259133c50 ffffffff81159f6d ffff880259133c60 ffff88029ba652d0
Aug 18 21:49:08 mainland kernel: ffff880259133fd8 ffff880259133fd8 ffff880259133c70 ffffffff8118492b
Aug 18 21:49:08 mainland kernel: ffff88029ba65240 000000018040002b 0000000059133c90 0000000000000000
Aug 18 21:49:08 mainland kernel: Call Trace:
Aug 18 21:49:08 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:08 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:08 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:08 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:08 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:08 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:08 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:08 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:08 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:08 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:08 mainland kernel: Code: 85 c0 74 09 48 8d bd 30 ff ff ff ff d0 e8 6e db ff ff 48 81 c3 48 01 00 00 eb 08 0f 1f 44 00 00 48 89 c3 48 8b 03 48 85
Aug 18 21:49:08 mainland kernel: Call Trace:
Aug 18 21:49:08 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:08 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:08 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:08 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:08 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:08 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:08 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:08 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:08 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:08 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:08 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:27 mainland kernel: BUG: soft lockup - CPU#0 stuck for 22s! [firefox:3820]
Aug 18 21:49:27 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:27 mainland kernel: CPU 0
Aug 18 21:49:27 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:27 mainland kernel:
Aug 18 21:49:27 mainland kernel: Pid: 3820, comm: firefox Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:49:27 mainland kernel: RIP: 0010:[<ffffffff8146ad72>] [<ffffffff8146ad72>] _raw_spin_lock+0x32/0x40
Aug 18 21:49:27 mainland kernel: RSP: 0018:ffff880157001dd8 EFLAGS: 00000293
Aug 18 21:49:27 mainland kernel: RAX: 0000000000000069 RBX: 0000000000000001 RCX: 0000000000000000
Aug 18 21:49:27 mainland kernel: RDX: 000000000000006b RSI: ffffffff816f15a2 RDI: ffffffff81a806fc
Aug 18 21:49:27 mainland kernel: RBP: ffff880157001dd8 R08: 0000000000016490 R09: ffff8802fd7c8900
Aug 18 21:49:27 mainland kernel: R10: 0000000000000002 R11: 0000000000000293 R12: 00000000ffffffff
Aug 18 21:49:27 mainland kernel: R13: 0000000000000000 R14: ffff88030b76c600 R15: 0000000000000000
Aug 18 21:49:27 mainland kernel: FS: 00007fe462bff700(0000) GS:ffff88031ec00000(0000) knlGS:0000000000000000
Aug 18 21:49:27 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 18 21:49:27 mainland kernel: CR2: 00007f850dd47000 CR3: 000000025aa34000 CR4: 00000000001407f0
Aug 18 21:49:27 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:49:27 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:49:27 mainland kernel: Process firefox (pid: 3820, threadinfo ffff880157000000, task ffff8802c7cfc770)
Aug 18 21:49:27 mainland kernel: Stack:
Aug 18 21:49:27 mainland kernel: ffff880157001de8 ffffffff811b8955 ffff880157001e48 ffffffff811b9465
Aug 18 21:49:27 mainland kernel: ffff8802c7cfcc00 ffffffff81159e4f ffff8802fd7c8900 0000000000000000
Aug 18 21:49:27 mainland kernel: ffff880157001e48 ffff8802fd7c8840 0000000000000000 ffff8802c7cfc770
Aug 18 21:49:27 mainland kernel: Call Trace:
Aug 18 21:49:27 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:27 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
Aug 18 21:49:27 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
Aug 18 21:49:27 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
Aug 18 21:49:27 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
Aug 18 21:49:27 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
Aug 18 21:49:27 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
Aug 18 21:49:27 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
Aug 18 21:49:27 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
Aug 18 21:49:27 mainland kernel: Code: 00 00 65 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00
Aug 18 21:49:27 mainland kernel: Call Trace:
Aug 18 21:49:27 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:27 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
Aug 18 21:49:27 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
Aug 18 21:49:27 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
Aug 18 21:49:27 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
Aug 18 21:49:27 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
Aug 18 21:49:27 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
Aug 18 21:49:27 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
Aug 18 21:49:27 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
Aug 18 21:49:35 mainland kernel: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:3406]
Aug 18 21:49:35 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:35 mainland kernel: CPU 2
Aug 18 21:49:35 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:35 mainland kernel:
Aug 18 21:49:35 mainland kernel: Pid: 3406, comm: kworker/2:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:49:35 mainland kernel: RIP: 0010:[<ffffffff8146ad75>] [<ffffffff8146ad75>] _raw_spin_lock+0x35/0x40
Aug 18 21:49:35 mainland kernel: RSP: 0018:ffff88025ca7bc00 EFLAGS: 00000297
Aug 18 21:49:35 mainland kernel: RAX: 0000000000000069 RBX: ffff88031ec8e940 RCX: ffff8801584c0580
Aug 18 21:49:35 mainland kernel: RDX: 000000000000006a RSI: 0000000000000008 RDI: ffffffff81a806fc
Aug 18 21:49:35 mainland kernel: RBP: ffff88025ca7bc00 R08: ffffffff81618d40 R09: 0000000000000000
Aug 18 21:49:35 mainland kernel: R10: ffff8802f3ebcf10 R11: 0000000000000000 R12: ffff88025ca7bbd0
Aug 18 21:49:35 mainland kernel: R13: 0000000000000000 R14: 0200000000000000 R15: 0000000000000000
Aug 18 21:49:35 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Aug 18 21:49:35 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 18 21:49:35 mainland kernel: CR2: 00007f850dc67000 CR3: 000000000380b000 CR4: 00000000001407e0
Aug 18 21:49:35 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:49:35 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:49:35 mainland kernel: Process kworker/2:2 (pid: 3406, threadinfo ffff88025ca7a000, task ffff8802c7cfdf40)
Aug 18 21:49:35 mainland kernel: Stack:
Aug 18 21:49:35 mainland kernel: ffff88025ca7bc10 ffffffff811b8955 ffff88025ca7bcf0 ffffffff811badd2
Aug 18 21:49:35 mainland kernel: ffff88025ca7bc50 ffffffff81159f6d ffff88025ca7bc60 ffff88029b923210
Aug 18 21:49:35 mainland kernel: ffff88025ca7bfd8 ffff88025ca7bfd8 ffff88025ca7bc70 ffffffff8118492b
Aug 18 21:49:35 mainland kernel: Call Trace:
Aug 18 21:49:35 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:35 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
Aug 18 21:49:35 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:35 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:35 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:35 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:35 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:35 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:35 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:35 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:35 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:35 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:35 mainland kernel: Code: 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00 00 f3 90
Aug 18 21:49:35 mainland kernel: Call Trace:
Aug 18 21:49:35 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:35 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
Aug 18 21:49:35 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:35 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:35 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:35 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:35 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:35 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:35 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:35 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:35 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:35 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:35 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:36 mainland kernel: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:2:3797]
Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:36 mainland kernel: CPU 3
Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:36 mainland kernel:
Aug 18 21:49:36 mainland kernel: Pid: 3797, comm: kworker/3:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:49:36 mainland kernel: RIP: 0010:[<ffffffff811badeb>] [<ffffffff811badeb>] locks_remove_flock+0xdb/0x130
Aug 18 21:49:36 mainland kernel: RSP: 0018:ffff880259133c20 EFLAGS: 00000282
Aug 18 21:49:36 mainland kernel: RAX: ffff8801584c0698 RBX: ffff880259133fd8 RCX: ffff8801584c0550
Aug 18 21:49:36 mainland kernel: RDX: 0000000000000069 RSI: 0000000000000008 RDI: ffffffff81a806fc
Aug 18 21:49:36 mainland kernel: RBP: ffff880259133cf0 R08: ffffffff81618d40 R09: 0000000000000000
Aug 18 21:49:36 mainland kernel: R10: ffff88025f179610 R11: 0000000000000000 R12: ffff880259133bf0
Aug 18 21:49:36 mainland kernel: R13: 0000000100000002 R14: 0000000000000000 R15: 0000000000000297
Aug 18 21:49:36 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ecc0000(0000) knlGS:0000000000000000
Aug 18 21:49:36 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 18 21:49:36 mainland kernel: CR2: 00007f8507a34000 CR3: 000000000380b000 CR4: 00000000001407e0
Aug 18 21:49:36 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:49:36 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:49:36 mainland kernel: Process kworker/3:2 (pid: 3797, threadinfo ffff880259132000, task ffff88025ae727b0)
Aug 18 21:49:36 mainland kernel: Stack:
Aug 18 21:49:36 mainland kernel: ffff880259133c50 ffffffff81159f6d ffff880259133c60 ffff88029ba652d0
Aug 18 21:49:36 mainland kernel: ffff880259133fd8 ffff880259133fd8 ffff880259133c70 ffffffff8118492b
Aug 18 21:49:36 mainland kernel: ffff88029ba65240 000000018040002b 0000000059133c90 0000000000000000
Aug 18 21:49:36 mainland kernel: Call Trace:
Aug 18 21:49:36 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:36 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:36 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:36 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:36 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:36 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:36 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:36 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:36 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:36 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:36 mainland kernel: Code: 85 c0 74 09 48 8d bd 30 ff ff ff ff d0 e8 6e db ff ff 48 81 c3 48 01 00 00 eb 08 0f 1f 44 00 00 48 89 c3 48 8b 03 48 85
Aug 18 21:49:36 mainland kernel: Call Trace:
Aug 18 21:49:36 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
Aug 18 21:49:36 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
Aug 18 21:49:36 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
Aug 18 21:49:36 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
Aug 18 21:49:36 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
Aug 18 21:49:36 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
Aug 18 21:49:36 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
Aug 18 21:49:36 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
Aug 18 21:49:36 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
Aug 18 21:49:36 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
Aug 18 21:49:36 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
Aug 18 21:49:36 mainland kernel: BUG: soft lockup - CPU#6 stuck for 22s! [firefox:3805]
Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:36 mainland kernel: CPU 6
Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:36 mainland kernel:
Aug 18 21:49:36 mainland kernel: Pid: 3805, comm: firefox Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:49:36 mainland kernel: RIP: 0010:[<ffffffff8146ad75>] [<ffffffff8146ad75>] _raw_spin_lock+0x35/0x40
Aug 18 21:49:36 mainland kernel: RSP: 0018:ffff8802f433fdd8 EFLAGS: 00000293
Aug 18 21:49:36 mainland kernel: RAX: 0000000000000069 RBX: 0000000000000000 RCX: 0000000000000000
Aug 18 21:49:36 mainland kernel: RDX: 000000000000006c RSI: ffffffff816f15a2 RDI: ffffffff81a806fc
Aug 18 21:49:36 mainland kernel: RBP: ffff8802f433fdd8 R08: 0000000000016490 R09: ffff8802bde4ef00
Aug 18 21:49:36 mainland kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
Aug 18 21:49:36 mainland kernel: R13: ffff8802f433e000 R14: ffffffff81132ceb R15: ffff8802f433fdf8
Aug 18 21:49:36 mainland kernel: FS: 00007fe47e1a7740(0000) GS:ffff88031ed80000(0000) knlGS:0000000000000000
Aug 18 21:49:36 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 18 21:49:36 mainland kernel: CR2: 00007fe4583c1000 CR3: 000000025aa34000 CR4: 00000000001407e0
Aug 18 21:49:36 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:49:36 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:49:36 mainland kernel: Process firefox (pid: 3805, threadinfo ffff8802f433e000, task ffff8802c7cf8000)
Aug 18 21:49:36 mainland kernel: Stack:
Aug 18 21:49:36 mainland kernel: ffff8802f433fde8 ffffffff811b8955 ffff8802f433fe48 ffffffff811b9465
Aug 18 21:49:36 mainland kernel: ffff8802f433fe38 ffffffff81159e4f ffff8802bde4ef00 00007fe4583c1000
Aug 18 21:49:36 mainland kernel: 0000000000000029 ffff8802bde4ec00 0000000000000000 ffff8802c7cf8000
Aug 18 21:49:36 mainland kernel: Call Trace:
Aug 18 21:49:36 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:36 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
Aug 18 21:49:36 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
Aug 18 21:49:36 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
Aug 18 21:49:36 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
Aug 18 21:49:36 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
Aug 18 21:49:36 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
Aug 18 21:49:36 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
Aug 18 21:49:36 mainland kernel: Code: 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00 00 f3 90
Aug 18 21:49:36 mainland kernel: Call Trace:
Aug 18 21:49:36 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:36 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
Aug 18 21:49:36 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
Aug 18 21:49:36 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
Aug 18 21:49:36 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
Aug 18 21:49:36 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
Aug 18 21:49:36 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
Aug 18 21:49:36 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
Aug 18 21:49:55 mainland kernel: BUG: soft lockup - CPU#0 stuck for 22s! [firefox:3820]
Aug 18 21:49:55 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:55 mainland kernel: CPU 0
Aug 18 21:49:55 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:49:55 mainland kernel:
Aug 18 21:49:55 mainland kernel: Pid: 3820, comm: firefox Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:49:55 mainland kernel: RIP: 0010:[<ffffffff8146ad72>] [<ffffffff8146ad72>] _raw_spin_lock+0x32/0x40
Aug 18 21:49:55 mainland kernel: RSP: 0018:ffff880157001dd8 EFLAGS: 00000293
Aug 18 21:49:55 mainland kernel: RAX: 0000000000000069 RBX: 0000000000000001 RCX: 0000000000000000
Aug 18 21:49:55 mainland kernel: RDX: 000000000000006b RSI: ffffffff816f15a2 RDI: ffffffff81a806fc
Aug 18 21:49:55 mainland kernel: RBP: ffff880157001dd8 R08: 0000000000016490 R09: ffff8802fd7c8900
Aug 18 21:49:55 mainland kernel: R10: 0000000000000002 R11: 0000000000000293 R12: 00000000ffffffff
Aug 18 21:49:55 mainland kernel: R13: 0000000000000000 R14: ffff88030b76c600 R15: 0000000000000000
Aug 18 21:49:55 mainland kernel: FS: 00007fe462bff700(0000) GS:ffff88031ec00000(0000) knlGS:0000000000000000
Aug 18 21:49:55 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 18 21:49:55 mainland kernel: CR2: 00007f850dd47000 CR3: 000000025aa34000 CR4: 00000000001407f0
Aug 18 21:49:55 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:49:55 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:49:55 mainland kernel: Process firefox (pid: 3820, threadinfo ffff880157000000, task ffff8802c7cfc770)
Aug 18 21:49:55 mainland kernel: Stack:
Aug 18 21:49:55 mainland kernel: ffff880157001de8 ffffffff811b8955 ffff880157001e48 ffffffff811b9465
Aug 18 21:49:55 mainland kernel: ffff8802c7cfcc00 ffffffff81159e4f ffff8802fd7c8900 0000000000000000
Aug 18 21:49:55 mainland kernel: ffff880157001e48 ffff8802fd7c8840 0000000000000000 ffff8802c7cfc770
Aug 18 21:49:55 mainland kernel: Call Trace:
Aug 18 21:49:55 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:55 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
Aug 18 21:49:55 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
Aug 18 21:49:55 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
Aug 18 21:49:55 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
Aug 18 21:49:55 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
Aug 18 21:49:55 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
Aug 18 21:49:55 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
Aug 18 21:49:55 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
Aug 18 21:49:55 mainland kernel: Code: 00 00 65 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00
Aug 18 21:49:55 mainland kernel: Call Trace:
Aug 18 21:49:55 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:49:55 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
Aug 18 21:49:55 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
Aug 18 21:49:55 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
Aug 18 21:49:55 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
Aug 18 21:49:55 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
Aug 18 21:49:55 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
Aug 18 21:49:55 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
Aug 18 21:49:55 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
Aug 18 21:50:03 mainland kernel: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:3406]
Aug 18 21:50:03 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:50:03 mainland kernel: CPU 2
Aug 18 21:50:03 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
Aug 18 21:50:03 mainland kernel:
Aug 18 21:50:03 mainland kernel: Pid: 3406, comm: kworker/2:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
Aug 18 21:50:03 mainland kernel: RIP: 0010:[<ffffffff8146ad72>] [<ffffffff8146ad72>] _raw_spin_lock+0x32/0x40
Aug 18 21:50:03 mainland kernel: RSP: 0018:ffff88025ca7bc00 EFLAGS: 00000297
Aug 18 21:50:03 mainland kernel: RAX: 0000000000000069 RBX: ffff88031ec8e940 RCX: ffff8801584c0580
Aug 18 21:50:03 mainland kernel: RDX: 000000000000006a RSI: 0000000000000008 RDI: ffffffff81a806fc
Aug 18 21:50:03 mainland kernel: RBP: ffff88025ca7bc00 R08: ffffffff81618d40 R09: 0000000000000000
Aug 18 21:50:03 mainland kernel: R10: ffff8802f3ebcf10 R11: 0000000000000000 R12: ffff88025ca7bbd0
Aug 18 21:50:03 mainland kernel: R13: 0000000000000000 R14: 0200000000000000 R15: 0000000000000000
Aug 18 21:50:03 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Aug 18 21:50:03 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Aug 18 21:50:03 mainland kernel: CR2: 00007f850dc67000 CR3: 000000000380b000 CR4: 00000000001407e0
Aug 18 21:50:03 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 18 21:50:03 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 18 21:50:03 mainland kernel: Process kworker/2:2 (pid: 3406, threadinfo ffff88025ca7a000, task ffff8802c7cfdf40)
Aug 18 21:50:03 mainland kernel: Stack:
Aug 18 21:50:03 mainland kernel: ffff88025ca7bc10 ffffffff811b8955 ffff88025ca7bcf0 ffffffff811badd2
Aug 18 21:50:03 mainland kernel: ffff88025ca7bc50 ffffffff81159f6d ffff88025ca7bc60 ffff88029b923210
Aug 18 21:50:03 mainland kernel: ffff88025ca7bfd8 ffff88025ca7bfd8 ffff88025ca7bc70 ffffffff8118492b
Aug 18 21:50:03 mainland kernel: Call Trace:
Aug 18 21:50:03 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
Aug 18 21:50:03 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
Any ideas and anything i can do?
Last edited by 89c51 (2012-08-31 20:26:13)
Sorry for bumping but i got this beauty some minutes ago.
Sep 20 20:13:00 mainland dbus[378]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.0" (uid=0 pid=376 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" me
Sep 20 22:35:53 mainland kernel: general protection fault: 0000 [#1] PREEMPT SMP
Sep 20 22:35:53 mainland kernel: CPU 2
Sep 20 22:35:53 mainland kernel: Modules linked in:
Sep 20 22:35:53 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
Sep 20 22:35:53 mainland kernel:
Sep 20 22:35:53 mainland kernel: Pid: 402, comm: Xorg Not tainted 3.5.4-1-ARCH #1 /DZ77BH-55K
Sep 20 22:35:53 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:35:53 mainland kernel: RSP: 0018:ffff8803009898c8 EFLAGS: 00010286
Sep 20 22:35:53 mainland kernel: RAX: 0000000000000000 RBX: 0000000000000002 RCX: 00000000465a5002
Sep 20 22:35:53 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffffa0064871
Sep 20 22:35:53 mainland kernel: RBP: ffff880300989908 R08: 0000000000016710 R09: 00000000001c0217
Sep 20 22:35:53 mainland kernel: R10: 0000000000000002 R11: ffffffffa00649a8 R12: 00000000000000d0
Sep 20 22:35:53 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: ffff88030d1143c0
Sep 20 22:35:53 mainland kernel: FS: 00007f7f13315880(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Sep 20 22:35:53 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 20 22:35:53 mainland kernel: CR2: 00007f7f0b5d1000 CR3: 000000030092a000 CR4: 00000000001407e0
Sep 20 22:35:53 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 20 22:35:53 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 20 22:35:53 mainland kernel: Process Xorg (pid: 402, threadinfo ffff880300988000, task ffff88030a1e1020)
Sep 20 22:35:53 mainland kernel: Stack:
Sep 20 22:35:53 mainland kernel: 00000000000200d0 0000000000000028 ffff880300989908 0000000000000002
Sep 20 22:35:53 mainland kernel: 0000000000000002 ffff88016733c4c0 ffff88025307ca00 ffff88030d1143c0
Sep 20 22:35:53 mainland kernel: ffff8803009899f8 ffffffffa0064871 ffff880300989938 ffffffff8114b9db
Sep 20 22:35:53 mainland kernel: Call Trace:
Sep 20 22:35:53 mainland kernel: [<ffffffffa0064871>] ttm_dma_populate+0x551/0x990 [ttm]
Sep 20 22:35:53 mainland kernel: [<ffffffff8114b9db>] ? insert_vmalloc_vmlist+0x6b/0x80
Sep 20 22:35:53 mainland kernel: [<ffffffff8114e505>] ? __vmalloc_node+0x35/0x40
Sep 20 22:35:53 mainland kernel: [<ffffffffa00b68df>] radeon_ttm_tt_populate+0x22f/0x260 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffffa00b699c>] ? radeon_ttm_tt_create+0x8c/0x100 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffffa005b0be>] ttm_tt_bind+0x3e/0x70 [ttm]
Sep 20 22:35:53 mainland kernel: [<ffffffffa005d387>] ttm_bo_handle_move_mem+0x507/0x590 [ttm]
Sep 20 22:35:53 mainland kernel: [<ffffffff811926e7>] ? inode_init_always+0x107/0x1d0
Sep 20 22:35:53 mainland kernel: [<ffffffffa005e392>] ttm_bo_move_buffer+0x142/0x150 [ttm]
Sep 20 22:35:53 mainland kernel: [<ffffffffa005e43d>] ttm_bo_validate+0x9d/0x120 [ttm]
Sep 20 22:35:53 mainland kernel: [<ffffffffa005e7cf>] ttm_bo_init+0x30f/0x3e0 [ttm]
Sep 20 22:35:53 mainland kernel: [<ffffffffa00b75c6>] radeon_bo_create+0x1b6/0x300 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffffa00b7290>] ? radeon_bo_clear_va+0xd0/0xd0 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffffa00c9491>] radeon_gem_object_create+0x61/0x100 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffffa00c989a>] radeon_gem_create_ioctl+0x5a/0xf0 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffff8147b83e>] ? mutex_unlock+0xe/0x10
Sep 20 22:35:53 mainland kernel: [<ffffffffa00c9b18>] ? radeon_gem_busy_ioctl+0x98/0x110 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffffa00104f3>] drm_ioctl+0x4c3/0x570 [drm]
Sep 20 22:35:53 mainland kernel: [<ffffffffa00c9840>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
Sep 20 22:35:53 mainland kernel: [<ffffffff814815c4>] ? do_page_fault+0x2c4/0x580
Sep 20 22:35:53 mainland kernel: [<ffffffff811463ed>] ? do_mmap_pgoff+0x24d/0x340
Sep 20 22:35:53 mainland kernel: [<ffffffff8118aad7>] do_vfs_ioctl+0x97/0x530
Sep 20 22:35:53 mainland kernel: [<ffffffff8118b009>] sys_ioctl+0x99/0xa0
Sep 20 22:35:53 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
Sep 20 22:35:53 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
Sep 20 22:35:53 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:35:53 mainland kernel: RSP <ffff8803009898c8>
Sep 20 22:35:53 mainland kernel: ---[ end trace 6841e94d0f65e4c5 ]---
Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#2] PREEMPT SMP
Sep 20 22:36:11 mainland kernel: CPU 2
Sep 20 22:36:11 mainland kernel: Modules linked in:
Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: Pid: 378, comm: dbus-daemon Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
Sep 20 22:36:11 mainland avahi-daemon[371]: Disconnected from D-Bus, exiting.
Sep 20 22:36:11 mainland avahi-daemon[371]: Got SIGTERM, quitting.
Sep 20 22:36:11 mainland avahi-daemon[371]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Sep 20 22:36:11 mainland NetworkManager[364]: <warn> disconnected by the system bus.
Sep 20 22:36:11 mainland rtkit-daemon[567]: Exiting cleanly.
Sep 20 22:36:11 mainland rtkit-daemon[567]: Demoting known real-time threads.
Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 699 of process 699 (/usr/bin/pulseaudio).
Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 598 of process 565 (/usr/bin/pulseaudio).
Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 597 of process 565 (/usr/bin/pulseaudio).
Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 593 of process 565 (/usr/bin/pulseaudio).
Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 565 of process 565 (/usr/bin/pulseaudio).
Sep 20 22:36:11 mainland rtkit-daemon[567]: Demoted 5 threads.
Sep 20 22:36:11 mainland rtkit-daemon[567]: Exiting watchdog thread.
Sep 20 22:36:11 mainland rtkit-daemon[567]: Exiting canary thread.
Sep 20 22:36:11 mainland avahi-daemon[371]: avahi-daemon 0.6.31 exiting.
Sep 20 22:36:11 mainland gdm-simple-slave[399]: WARNING: Child process 611 was already dead.
Sep 20 22:36:11 mainland gdm-simple-slave[399]: WARNING: Unable to kill session worker process
Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland NetworkManager[364]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Sep 20 22:36:11 mainland colord[709]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Sep 20 22:36:11 mainland colord-sane[721]: Failed cupsGetDevices
Sep 20 22:36:11 mainland colord-sane[721]: Failed cupsGetDevices
Sep 20 22:36:11 mainland colord-sane[721]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Sep 20 22:36:11 mainland accounts-daemon[427]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Sep 20 22:36:11 mainland systemd[1]: upower.service: main process exited, code=exited, status=1
Sep 20 22:36:11 mainland console-kit-daemon[430]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting
Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff88030b555de8 EFLAGS: 00010286
Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff88030afdf3b0 RCX: 00000000465a5002
Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000080d0 RDI: ffffffffa022144d
Sep 20 22:36:11 mainland kernel: RBP: ffff88030b555e28 R08: 0000000000016710 R09: 2222222222222222
Sep 20 22:36:11 mainland kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000080d0
Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: ffff88030a101d00
Sep 20 22:36:11 mainland kernel: FS: 00007f8e02dec700(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 20 22:36:11 mainland kernel: CR2: 00007f7f0b5d1000 CR3: 000000030c2bf000 CR4: 00000000001407e0
Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 20 22:36:11 mainland kernel: Process dbus-daemon (pid: 378, threadinfo ffff88030b554000, task ffff88030a1e2850)
Sep 20 22:36:11 mainland kernel: Stack:
Sep 20 22:36:11 mainland kernel: ffff88030bc66020 0000000000000030 ffff88030b555e08 ffff88030afdf3b0
Sep 20 22:36:11 mainland kernel: ffff88030afdf3b0 0000000000000000 ffff88030a06a000 ffff88030a101d00
Sep 20 22:36:11 mainland kernel: ffff88030b555ed8 ffffffffa022144d ffff88030b555eb8 ffffffff8147b116
Sep 20 22:36:11 mainland kernel: Call Trace:
Sep 20 22:36:11 mainland kernel: [<ffffffffa022144d>] ext4_readdir+0x68d/0x7c0 [ext4]
Sep 20 22:36:11 mainland kernel: [<ffffffff8147b116>] ? __mutex_lock_killable_slowpath+0x266/0x3f0
Sep 20 22:36:11 mainland kernel: [<ffffffff8118b010>] ? sys_ioctl+0xa0/0xa0
Sep 20 22:36:11 mainland kernel: [<ffffffff8118b010>] ? sys_ioctl+0xa0/0xa0
Sep 20 22:36:11 mainland kernel: [<ffffffff8118b010>] ? sys_ioctl+0xa0/0xa0
Sep 20 22:36:11 mainland kernel: [<ffffffff8118b358>] vfs_readdir+0xb8/0xe0
Sep 20 22:36:11 mainland kernel: [<ffffffff8118b480>] sys_getdents+0x80/0x100
Sep 20 22:36:11 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
Sep 20 22:36:11 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
Sep 20 22:36:11 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland kernel: RSP <ffff88030b555de8>
Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c6 ]---
Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#3] PREEMPT SMP
Sep 20 22:36:11 mainland kernel: CPU 2
Sep 20 22:36:11 mainland kernel: Modules linked in:
Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: Pid: 719, comm: gdbus Tainted: G D 3.5.4-1-ARCH #1
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: /DZ77BH-55K
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>]
Sep 20 22:36:11 mainland kernel: [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff8802fb3f5eb8 EFLAGS: 00010286
Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: 0000000000000012 RCX: 00000000465a5002
Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffff811bfeb9
Sep 20 22:36:11 mainland kernel: RBP: ffff8802fb3f5ef8 R08: 0000000000016710 R09: 0000000000000000
Sep 20 22:36:11 mainland kernel: R10: 00000000fffffff0 R11: 0000000000000246 R12: 00000000000000d0
Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: 00007f7ac4001e00
Sep 20 22:36:11 mainland kernel: FS: 00007f7ac8926700(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 20 22:36:11 mainland kernel: CR2: 000000000162c580 CR3: 0000000300a56000 CR4: 00000000001407e0
Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 20 22:36:11 mainland kernel: Process gdbus (pid: 719, threadinfo ffff8802fb3f4000, task ffff8802fe331020)
Sep 20 22:36:11 mainland kernel: Stack:
Sep 20 22:36:11 mainland kernel: 0000000000000000
Sep 20 22:36:11 mainland kernel: 0000000000000030
Sep 20 22:36:11 mainland kernel: 0000000000000000
Sep 20 22:36:11 mainland kernel: 0000000000000012
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: 0000000000080800
Sep 20 22:36:11 mainland kernel: 0000000000000000
Sep 20 22:36:11 mainland kernel: 00007f7ac4005b80
Sep 20 22:36:11 mainland kernel: 00007f7ac4001e00
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: ffff8802fb3f5f38
Sep 20 22:36:11 mainland kernel: ffffffff811bfeb9
Sep 20 22:36:11 mainland kernel: 00007f7ac89259a8
Sep 20 22:36:11 mainland kernel: 0000000000dfda80
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: Call Trace:
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: [<ffffffff811bfeb9>] eventfd_file_create+0x49/0xe0
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: [<ffffffff811bff8d>] sys_eventfd2+0x3d/0x80
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
Sep 20 22:36:11 mainland kernel: Code:
Sep 20 22:36:11 mainland kernel: 48
Sep 20 22:36:11 mainland kernel: 89
Sep 20 22:36:11 mainland kernel: 55
Sep 20 22:36:11 mainland kernel: c8
Sep 20 22:36:11 mainland kernel: 49
Sep 20 22:36:11 mainland kernel: 8b
Sep 20 22:36:11 mainland kernel: 06
Sep 20 22:36:11 mainland kernel: 65
Sep 20 22:36:11 mainland kernel: 48
Sep 20 22:36:11 mainland kernel: 03
Sep 20 22:36:11 mainland kernel: 04
Sep 20 22:36:11 mainland kernel: 25
Sep 20 22:36:11 mainland kernel: e0
Sep 20 22:36:11 mainland kernel: db
Sep 20 22:36:11 mainland kernel: 00
Sep 20 22:36:11 mainland kernel: 00
Sep 20 22:36:11 mainland kernel: 48
Sep 20 22:36:11 mainland kernel: 8b
Sep 20 22:36:11 mainland kernel: 50
Sep 20 22:36:11 mainland kernel: 08
Sep 20 22:36:11 mainland kernel: 4c
Sep 20 22:36:11 mainland kernel: 8b
Sep 20 22:36:11 mainland kernel: 28
Sep 20 22:36:11 mainland kernel: 4d
Sep 20 22:36:11 mainland kernel: 85
Sep 20 22:36:11 mainland kernel: ed
Sep 20 22:36:11 mainland kernel: 0f
Sep 20 22:36:11 mainland kernel: 84
Sep 20 22:36:11 mainland kernel: c7
Sep 20 22:36:11 mainland kernel: 00
Sep 20 22:36:11 mainland kernel: 00
Sep 20 22:36:11 mainland kernel: 00
Sep 20 22:36:11 mainland kernel: 49
Sep 20 22:36:11 mainland kernel: 63
Sep 20 22:36:11 mainland kernel: 46
Sep 20 22:36:11 mainland kernel: 20
Sep 20 22:36:11 mainland kernel: 4d
Sep 20 22:36:11 mainland kernel: 8b
Sep 20 22:36:11 mainland kernel: 06
Sep 20 22:36:11 mainland kernel: 48
Sep 20 22:36:11 mainland kernel: 8d
Sep 20 22:36:11 mainland kernel: 4a
Sep 20 22:36:11 mainland kernel: 40
Sep 20 22:36:11 mainland kernel: <49>
Sep 20 22:36:11 mainland kernel: 8b
Sep 20 22:36:11 mainland kernel: 5c
Sep 20 22:36:11 mainland kernel: 05
Sep 20 22:36:11 mainland kernel: 00
Sep 20 22:36:11 mainland kernel: 4c
Sep 20 22:36:11 mainland kernel: 89
Sep 20 22:36:11 mainland kernel: e8
Sep 20 22:36:11 mainland kernel: 65
Sep 20 22:36:11 mainland kernel: 49
Sep 20 22:36:11 mainland kernel: 0f
Sep 20 22:36:11 mainland kernel: c7
Sep 20 22:36:11 mainland kernel: 08
Sep 20 22:36:11 mainland kernel: 0f
Sep 20 22:36:11 mainland kernel: 94
Sep 20 22:36:11 mainland kernel: c0
Sep 20 22:36:11 mainland kernel: 84
Sep 20 22:36:11 mainland kernel: c0
Sep 20 22:36:11 mainland kernel: 74
Sep 20 22:36:11 mainland kernel: c5
Sep 20 22:36:11 mainland kernel: 49
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: RIP
Sep 20 22:36:11 mainland kernel: [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland kernel: RSP <ffff8802fb3f5eb8>
Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c7 ]---
Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#4] PREEMPT SMP
Sep 20 22:36:11 mainland kernel: CPU 2
Sep 20 22:36:11 mainland kernel: Modules linked in:
Sep 20 22:36:11 mainland pulseaudio[4003]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
Sep 20 22:36:11 mainland pulseaudio[4004]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: Pid: 1967, comm: threaded-ml Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff8802533afe08 EFLAGS: 00010286
Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff8802b7ac5680 RCX: 00000000465a5002
Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffff81369ca4
Sep 20 22:36:11 mainland kernel: RBP: ffff8802533afe48 R08: 0000000000016710 R09: 0000000000000000
Sep 20 22:36:11 mainland kernel: R10: 00007f10d9cf7278 R11: 0000000000000202 R12: 00000000000000d0
Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: 00007f10b0595a48
Sep 20 22:36:11 mainland kernel: FS: 00007f10d9cf8700(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 20 22:36:11 mainland kernel: CR2: 00007f1102256000 CR3: 00000002fb09c000 CR4: 00000000001407e0
Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 20 22:36:11 mainland kernel: Process threaded-ml (pid: 1967, threadinfo ffff8802533ae000, task ffff880255b51830)
Sep 20 22:36:11 mainland kernel: Stack:
Sep 20 22:36:11 mainland kernel: ffff8802533afec8 0000000000000040 0000000000810010 ffff8802b7ac5680
Sep 20 22:36:11 mainland kernel: ffff88030d079800 0000000000000000 0000000000000000 00007f10b0595a48
Sep 20 22:36:11 mainland kernel: ffff8802533afe68 ffffffff81369ca4 0000000000000001 ffff88030d079800
Sep 20 22:36:11 mainland kernel: Call Trace:
Sep 20 22:36:11 mainland kernel: [<ffffffff81369ca4>] sock_alloc_inode+0x44/0xd0
Sep 20 22:36:11 mainland kernel: [<ffffffff811927d6>] alloc_inode+0x26/0xa0
Sep 20 22:36:11 mainland kernel: [<ffffffff8119400a>] new_inode_pseudo+0x1a/0x70
Sep 20 22:36:11 mainland kernel: [<ffffffff8136bb0e>] sock_alloc+0x1e/0x80
Sep 20 22:36:11 mainland kernel: [<ffffffff8136c6fd>] __sock_create+0x9d/0x240
Sep 20 22:36:11 mainland kernel: [<ffffffff8136c900>] sock_create+0x30/0x40
Sep 20 22:36:11 mainland kernel: [<ffffffff8136cecb>] sys_socket+0x2b/0x70
Sep 20 22:36:11 mainland kernel: [<ffffffff8114650b>] ? sys_munmap+0x2b/0x40
Sep 20 22:36:11 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
Sep 20 22:36:11 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
Sep 20 22:36:11 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland kernel: RSP <ffff8802533afe08>
Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c8 ]---
Sep 20 22:36:11 mainland systemd[1]: Unit upower.service entered failed state.
Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#5] PREEMPT SMP
Sep 20 22:36:11 mainland kernel: CPU 2
Sep 20 22:36:11 mainland kernel: Modules linked in:
Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: Pid: 2, comm: kthreadd Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff88030d4e5c90 EFLAGS: 00010286
Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff88030988f240 RCX: 00000000465a5002
Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffff8107c7d6
Sep 20 22:36:11 mainland kernel: RBP: ffff88030d4e5cd0 R08: 0000000000016710 R09: 00000000ffffffff
Sep 20 22:36:11 mainland kernel: R10: fffffffffffffffe R11: ffffffffffffffc0 R12: 00000000000000d0
Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: ffff8802fe32c000
Sep 20 22:36:11 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Sep 20 22:36:11 mainland kernel: CR2: 00007f1102256000 CR3: 000000030bf52000 CR4: 00000000001407e0
Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 20 22:36:11 mainland kernel: Process kthreadd (pid: 2, threadinfo ffff88030d4e4000, task ffff88030d4d8810)
Sep 20 22:36:11 mainland kernel: Stack:
Sep 20 22:36:11 mainland kernel: ffff88030d4d8810 0000000000000030 ffff88030d4e5cb0 ffff88030988f240
Sep 20 22:36:11 mainland kernel: ffff8802f87de0c0 0000000000800711 ffff8802f87de0c0 ffff8802fe32c000
Sep 20 22:36:11 mainland kernel: ffff88030d4e5d10 ffffffff8107c7d6 ffff88030d4d8858 0000000000000001
Sep 20 22:36:11 mainland kernel: Call Trace:
Sep 20 22:36:11 mainland kernel: [<ffffffff8107c7d6>] copy_creds+0xb6/0x1e0
Sep 20 22:36:11 mainland kernel: [<ffffffff8104f8c9>] copy_process.part.21+0x289/0x1530
Sep 20 22:36:11 mainland kernel: [<ffffffff81050cf5>] do_fork+0x135/0x3a0
Sep 20 22:36:11 mainland kernel: [<ffffffff8101d4f6>] kernel_thread+0x76/0x80
Sep 20 22:36:11 mainland kernel: [<ffffffff81074ee0>] ? kthread_freezable_should_stop+0x70/0x70
Sep 20 22:36:11 mainland kernel: [<ffffffff81486860>] ? gs_change+0x13/0x13
Sep 20 22:36:11 mainland kernel: [<ffffffff810753f0>] kthreadd+0x120/0x160
Sep 20 22:36:11 mainland kernel: [<ffffffff810814c9>] ? finish_task_switch+0x49/0xe0
Sep 20 22:36:11 mainland kernel: [<ffffffff81486864>] kernel_thread_helper+0x4/0x10
Sep 20 22:36:11 mainland kernel: [<ffffffff810752d0>] ? tsk_fork_get_node+0x30/0x30
Sep 20 22:36:11 mainland kernel: [<ffffffff81486860>] ? gs_change+0x13/0x13
Sep 20 22:36:11 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
Sep 20 22:36:11 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
Sep 20 22:36:11 mainland kernel: RSP <ffff88030d4e5c90>
Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c9 ]---
Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#6] PREEMPT SMP
Sep 20 22:36:11 mainland kernel: CPU 2
Sep 20 22:36:11 mainland kernel: Modules linked in:
Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
Sep 20 22:36:11 mainland kernel:
Sep 20 22:36:11 mainland kernel: Pid: 84, comm: kworker/u:6 Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff81163f72>] [<ffffffff81163f72>] __kmalloc+0x62/0x180
Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff88030b20fb20 EFLAGS: 00010286
Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff8802fb1a4390 RCX: 00000000465a5002
Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 0000000000000000 RDI: ffffffff81250236
Sep 20 22:36:11 mainland kernel: RBP: ffff88030b20fb60 R08: 0000000000016710 R09: ffff880312018000
Sep 20 22:36:11 mainland kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000080d0
Sep 20 22:36:11 mainland kernel: R13: 0000000000000024 R14: ffff880312002700 R15: ff333333ff333333
Sep 20 22:36:11 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Sep 20 22:36:11 mainland kernel: CR2: 00007f1102256000 CR3: 000000000380c000 CR4: 00000000001407e0
Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep 20 22:36:11 mainland kernel: Process kworker/u:6 (pid: 84, threadinfo ffff88030b20e000, task ffff88030d7b60c0)
Sep 20 22:36:11 mainland kernel: Stack:
Sep 20 22:36:11 mainland kernel: ffff88030b20fb50 ffffffff811648ec ffff88030b20fb50 ffff8802fb1a4390
Sep 20 22:36:11 mainland kernel: 0000000000000024 0000000000000000 00000000000000d0 ffff880309970d80
Sep 20 22:36:11 mainland kernel: ffff88030b20fb90 ffffffff81250236 ffff8802fb1a4390 0000000000000001
Sep 20 22:36:11 mainland kernel: Call Trace:
Sep 20 22:36:11 mainland kernel: [<ffffffff811648ec>] ? kfree+0x2c/0x150
Sep 20 22:36:11 mainland kernel: [<ffffffff81250236>] kobject_get_path+0x56/0xc0
Sep 20 22:36:11 mainland kernel: [<ffffffff81250ffb>] kobject_uevent_env+0xfb/0x4b0
Sep 20 22:36:11 mainland kernel: [<ffffffff813aa09e>] ? netlink_broadcast_filtered+0x11e/0x3d0
Sep 20 22:36:11 mainland kernel: [<ffffffff812513bb>] kobject_uevent+0xb/0x10
Sep 20 22:36:11 mainland kernel: [<ffffffff8124fead>] kobject_release+0x8d/0xa0
Sep 20 22:36:11 mainland kernel: [<ffffffff8124fd2c>] kobject_put+0x2c/0x60
Sep 20 22:36:11 mainland kernel: [<ffffffff813989c8>] net_rx_queue_update_kobjects+0xa8/0xe0
Sep 20 22:36:11 mainland kernel: [<ffffffff81398b76>] netdev_unregister_kobject+0x46/0x80
Sep 20 22:36:11 mainland kernel: [<ffffffff81380b52>] rollback_registered_many+0x1b2/0x260
Sep 20 22:36:11 mainland kernel: [<ffffffff81380c1b>] unregister_netdevice_many+0x1b/0x80
Sep 20 22:36:11 mainland kernel: [<ffffffff81383495>] default_device_exit_batch+0xa5/0xf0
Sep 20 22:36:11 mainland kernel: [<ffffffff8137c183>] ops_exit_list.isra.1+0x53/0x60
Sep 20 22:36:11 mainland kernel: [<ffffffff8137c9a8>] cleanup_net+0x108/0x1a0
Sep 20 22:36:11 mainland kernel: [<ffffffff8106effa>] process_one_work+0x12a/0x440
Sep 20 22:36:11 mainland kernel: [<ffffffff8137c8a0>] ? net_drop_ns+0x50/0x50
Sep 20 22:36:11 mainland kernel: [<ffffffff8106f85e>] worker_thread+0x12e/0x2d0
Sep 20 22:36:11 mainland kernel: [<ffffffff8106f730>] ? manage_workers.isra.26+0x1f0/0x1f0
Sep 20 22:36:11 mainland kernel: [<ffffffff81074f73>] kthread+0x93/0xa0
Sep 20 22:36:11 mainland kernel: [<ffffffff81486864>] kernel_thread_helper+0x4/0x10
Sep 20 22:36:11 mainland kernel: [<ffffffff81074ee0>] ? kthread_freezable_should_stop+0x70/0x70
Sep 20 22:36:11 mainland kernel: [<ffffffff81486860>] ? gs_change+0x13/0x13
Sep 20 22:36:11 mainland kernel: Code: 48 8b 7d 08 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 38 4d 85 ff 0f 84 cb 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 1c 07 4c 89 f8 65 49 0f
Sep 20 22:36:11 mainland kernel: RIP [<ffffffff81163f72>] __kmalloc+0x62/0x180
Sep 20 22:36:11 mainland kernel: RSP <ffff88030b20fb20>
Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4ca ]---
Sep 20 22:36:11 mainland kernel: BUG: unable to handle kernel paging request at fffffffffffffff8
----- Reboot -----
The panicks i get are quite rare . I checked the memory recently (memtest) and was ok. My motherboard has a firmware problem where it misroutes irqs. Could this be the root to my problems?? And if its not the motherboard FW related to this how can i determine which HW part fails.
Last edited by 89c51 (2012-09-20 19:50:10)
Similar Messages
-
Possible bug: Saving array with extended and double precision to spreadsheet
If one concatenates a double precision array and an extended precision array with the "build array" vi and then saves using "Write to Spreadsheet File" vi any digits to the right of the decimal place are set to zero in the saved file. This happens regardless of the format signifier input (e.g. %.10f) to the "Write to Spreadsheet File" vi.
I am on Vista Ultimate 32 bit and labview 9.0
This is a possible bug that is easily circumvented by converting to one type before combining arrar to a spreadsheet. Nonetheless, it is a bug and it cost me some time.
Solved!
Go to Solution.
Attachments:
Spreadsheet save bug.vi 9 KBHi JL,
no, it's not a bug - it's a feature
Well, if you would look more closely you would recognize the "Save to Spreadsheet" as polymorphic VI. As this polymorphic VI doesn't support EXT numbers internally (it only supports DBL, I64 and String) LabVIEW chooses the instance with most accuracy: I64 (I64 has 64 bits precision, DBL only 53...). So your options are:
- set the instance to use as DBL (by right-click and "Select type...")
- make a copy of this VI, save it with a different name and make it support EXT numbers (don't rework the polymorphic VI as you would break compatibility with other LV installations or future revisions)
And yes, those coercion dots always signal some conversions - you should atleast check what's going on there...
Message Edited by GerdW on 05-21-2010 10:01 PM
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome -
External Table - possible bug related to record size and total bytes in fil
I have an External Table defined with fixed record size, using Oracle 10.2.0.2.0 on HP/UX. At 279 byte records (1 or more fields, doesn't seem to matter), it can read almost 5M bytes in the file (17,421 records to be exact). At 280 byte records, it can not, but blows up with "partial record at end of file" - which is nonsense. It can read up to 3744 records, just below 1,048,320 bytes (1M bytes). 1 record over that, it blows up.
Now, If I add READSIZE and set it to 1.5M, then it works. I found this extends further, for instance 280 recsize with READSIZE 1.5M will work for a while but blows up on 39M bytes in the file (I didn't bother figuring exactly where it stops working in this case). Increasing READSIZE to 5M works again, for 78M bytes in file. But change the definition to have 560 byte records and it blows up. Decrease the file size to 39M bytes and it still won't work with 560 byte records.
Anyone have any explanation for this behavior? The docs say READSIZE is the read buffer, but only mentions that it is important to the largest record that can be processed - mine are only 280/560 bytes. My table definition is practically taken right out of the example in the docs for fixed length records (change the fields, sizes, names and it is identical - all clauses the same).
We are going to be using these external tables a lot, and need them to be reliable, so increasing READSIZE to the largest value I can doesn't make me comfortable, since I can't be sure in production how large an input file may become.
Should I report this as a bug to Oracle, or am I missing something?
Thanks,
BobI have an External Table defined with fixed record size, using Oracle 10.2.0.2.0 on HP/UX. At 279 byte records (1 or more fields, doesn't seem to matter), it can read almost 5M bytes in the file (17,421 records to be exact). At 280 byte records, it can not, but blows up with "partial record at end of file" - which is nonsense. It can read up to 3744 records, just below 1,048,320 bytes (1M bytes). 1 record over that, it blows up.
Now, If I add READSIZE and set it to 1.5M, then it works. I found this extends further, for instance 280 recsize with READSIZE 1.5M will work for a while but blows up on 39M bytes in the file (I didn't bother figuring exactly where it stops working in this case). Increasing READSIZE to 5M works again, for 78M bytes in file. But change the definition to have 560 byte records and it blows up. Decrease the file size to 39M bytes and it still won't work with 560 byte records.
Anyone have any explanation for this behavior? The docs say READSIZE is the read buffer, but only mentions that it is important to the largest record that can be processed - mine are only 280/560 bytes. My table definition is practically taken right out of the example in the docs for fixed length records (change the fields, sizes, names and it is identical - all clauses the same).
We are going to be using these external tables a lot, and need them to be reliable, so increasing READSIZE to the largest value I can doesn't make me comfortable, since I can't be sure in production how large an input file may become.
Should I report this as a bug to Oracle, or am I missing something?
Thanks,
Bob -
Hello,
I came up with a way to use drag-and-drop interactions that will take advantage of file input so that I may create a drag-and-drop interaction that uses one draggable object over and over allowing multiple scoring/tracking possibilities. Example use...is having the draggable object be dynamic in that it randomly changes its text so that a learner can drag a term it's possible classification.........thus allowing the possibility of having many terms easily loaded without having to redo a drag-and-drop interaction for each needed terms/classifications updates/changes.
My Issue: When using a variable to represent the text for a draggable Smart Shape object, I'm getting the error message "undefined" when, clicking/pressing on the object, as well as during the drag of the object. This issue occurs when publishing the project in an HTML5 format. Flash interestingly enough seems to work perfect...but we are not interested in publishing via Flash any longer.
To better help you explore this error message, I've set up a test project so that you can see when and how the "undefined" message shows up during a drag-and-drop interaction. I've also included the Captivate 8 project file used to make the exploration project I'm sharing in this post.
Link to Captivate project I created for you all to explore "undefined" error message": http://iti.cscc.edu/drag_and_drop_bug/
Link to this Captivate 8 Project file: http://iti.cscc.edu/drag_and_drop_bug.cptx
It's pretty interesting how things react in this demo, please try the following actions to see some interesting happenings:
Drag the Yellow (or variable drag box) to the drag target.
Drag Black Hello square to Drag target and click undo or reset - watch the undefined message come up on the Yellow (or variable drag box).
Drag the Yellow (or variable drag box) to the drag target and then use the undo or reset.
Move both draggable boxes to the drag target and use the undo and reset buttons...
Anyhow, I know you all are sharp and will run the demo through its paces.
I'd really be very honored if anyone help me figure out how I could (when publishing out to HTML5) no longer have the "undefined" error message show up when using drag-and-drop with a variable for shape text. This technique has been well received at the college I work at...and I have many future project requests for using such an idea on a variety of similar interactions. I'd love see a solution or see if this might be a bug Adobe may be able to fix!
I tried to find a solution to the issue documented here for quite some time, but I was not able to find anyone with this problem much less attempting the idea I'm sharing in the help request - save the darn "undefined" message that comes up!
Many thanks in advance for any help and/or direction that you all may be able to provide,
PaulHello,
I just wanted to supply a minor update related to my drag-and-drop question/issue stated above:
I did another test using Captivate 7, and found that the undefined error (publishing as HTML5) does not appear and the variable data remains visible - except the variable data turns very small and does not honor any font size related settings.
I did go ahead and submit this to Adobe as a possible bug today.
Thanks again for any help related to this issue. If the issued documented above is solved, it will allow many amazing things to be done using Captivate's drag-and-drop for both regular type projects as well as interaction development for iBooks!
Matter of fact if this issue gets fixed, I'll publish a Blog entry (or video) on way's I've used Captivate's drag-and-drop to create dynamic learning activities for Higher Ed. and for use in iBooks.
~ Paul -
Copy and paste adjustment problem/ possible bug.
Hi all
I have just encountered a very strange problem/ possible bug.
I have been working on a file in photoshop cs5 that had come from lightroom 5.3. This was then saved (automaticaly becomes tiff file in Lightroom). I then wanted to make some more adjustments to it in lightroom (using local adjustment clarity). I then tried to copy the settings of the adjustment brush from the tiff to the original raw file. This is where it gets very strange. The adjustments are copied but they are rotated ccw by 90 degrees! I can replicate this every time.
Could someone else try to see if this problem exists on their catalogs or if its a corrpution problem my end.Noted on the bug, thanks.
1762hd wrote:
Hi Geoff
Heres the summary for bug report - please note this bug also affects radial filter/healing brush and crop
Scenario
1 open a portrait raw image in photoshop using render using lightroom (I am using cs5)
2 back in lightroom make a change using the - adjustment brush/ radial filter/healing brush or crop - to the newly created tiff image.
3 copy and paste this adjustment to the original raw file.
problem
all effects are rotated. -
Possible bug with Pick flag and Collections
Odd behaviours in v3.3 (Windows) with pick flags in Collections:
Create (or use) a Collection Set which contains a number of different collections
Assign Pick plag to one photo in each collection
Bug 1: Highlight Collection Set and note that none of the images shows the Pick Flag in the thumbnail view. Also Filtering this view with Pick flag fails to pick up the Flagged images
Now return to one of the Collections within the Set and create a Virtual Copy of one of the images that has a Pick flag. (Note virtual copy does not have a flag - which seems logical). Return to Collection Set and (Bug 2) note that Pick flag has disappeared from original image and now appears on Virtual copy.
Something wrong here somewhere I suspect.lightshop wrote:
Odd behaviours in v3.3 (Windows) with pick flags in Collections:
Create (or use) a Collection Set which contains a number of different collections
Assign Pick plag to one photo in each collection
Bug 1: Highlight Collection Set and note that none of the images shows the Pick Flag in the thumbnail view. Also Filtering this view with Pick flag fails to pick up the Flagged images
Now return to one of the Collections within the Set and create a Virtual Copy of one of the images that has a Pick flag. (Note virtual copy does not have a flag - which seems logical). Return to Collection Set and (Bug 2) note that Pick flag has disappeared from original image and now appears on Virtual copy.
Something wrong here somewhere I suspect.
I could partially repeat bug 2.
I have Collection Set (Test) which contain to collections: "Collection 1" and "Collection 2". Both Collections contain 4 images.
I selected "Collection 1" and applied Pick flag to all those images. When I select Test (Collection Set) I got 8 images shown, which none had flags. Ok, this works as expected. I selected "Collection 1" and then selected 1 image and made Virtual copy from it. Lr show me now 4 images with Flag and 1 virtual copy without. Again, works as expected. I now select Test (Collection Set) and I get 9 images (as expected), but one of them, the virtual copy, has pick flag applied. Not as expected. If I go back to "Collection 1" I get four images with Pick flags and one virtual copy without. (as expected.) -
The JB installation experience and findings (possible bugs?)
MOST IMPORTANT - if you phone appears hung - leave it alone! I would personally say if it appears hung longer than 15 minutes then it probably warrants a manual reboot at that point.
I was on the road when I decided to start the OTA pull. I was on 4G and my phone switched to 3G (in an area I always have 4G) and there it stayed until the OTA update was downloaded. Took me ~45 minutes for it to finish downloading. It rebooted - ran through it's little droid robot status bar thingy. When it reached the point of "updating apps" it appeared frozen. The little circle hour glass wasn't spinning. It sat there for ~5 minutes and then the phone rebooted. When it came back up a window appeared stating "updating 3 apps". Then the phone continued to load on up. Immediately I started getting application updates available. Google+, Google (something else or another) and a few other apps I run such as Astro File Viewer.
Under the hood of JB I found they added a new contact widget which I so badly missed having from my RAZR MAXX. I immediately added that and added the new contacts. Took the dog outside to pee and when I came back the first contact I added to the widget now also populated the 2nd spot (3 spots available). So it repeated itself. I went to edit it and then it changed back to the original contact I had put there. (bug?) I rebooted and the changes stuck.
I've noticed the phone "hitches" (sliding gets a little jerky) when sliding screens when an announcement appears. This particular instance was when a new mail from my Exchange server was announced as well as gmail. (bug?)
I benchmarked ICS and the best I could get with Quadrant on a fresh boot run was ~4900. I just ran it on JB and pulled 6097. That's pretty substantial gains right there folks!
I also noticed the shutdown/plane mode/restart menu has changed. It actually makes better sense now IMHO.
Over all I'm thankful Verizon "finally" got this update out. If I continue to have minor "hitches" I just might perform a good ole fashioned restore/wipe.MOST IMPORTANT - if you phone appears hung - leave it alone! I would personally say if it appears hung longer than 15 minutes then it probably warrants a manual reboot at that point.
I was on the road when I decided to start the OTA pull. I was on 4G and my phone switched to 3G (in an area I always have 4G) and there it stayed until the OTA update was downloaded. Took me ~45 minutes for it to finish downloading. It rebooted - ran through it's little droid robot status bar thingy. When it reached the point of "updating apps" it appeared frozen. The little circle hour glass wasn't spinning. It sat there for ~5 minutes and then the phone rebooted. When it came back up a window appeared stating "updating 3 apps". Then the phone continued to load on up. Immediately I started getting application updates available. Google+, Google (something else or another) and a few other apps I run such as Astro File Viewer.
Under the hood of JB I found they added a new contact widget which I so badly missed having from my RAZR MAXX. I immediately added that and added the new contacts. Took the dog outside to pee and when I came back the first contact I added to the widget now also populated the 2nd spot (3 spots available). So it repeated itself. I went to edit it and then it changed back to the original contact I had put there. (bug?) I rebooted and the changes stuck.
I've noticed the phone "hitches" (sliding gets a little jerky) when sliding screens when an announcement appears. This particular instance was when a new mail from my Exchange server was announced as well as gmail. (bug?)
I benchmarked ICS and the best I could get with Quadrant on a fresh boot run was ~4900. I just ran it on JB and pulled 6097. That's pretty substantial gains right there folks!
I also noticed the shutdown/plane mode/restart menu has changed. It actually makes better sense now IMHO.
Over all I'm thankful Verizon "finally" got this update out. If I continue to have minor "hitches" I just might perform a good ole fashioned restore/wipe. -
On-demand process in page processing - possible bug?
Hi
Came across a possible bug today, certainly not a big one and unlike to affect many people but...
1. Create an on-demand application process
2. Create an on-demand page process that calls the application process
3. Delete the application process.
Now at this point, the page process is still available for editing/deleting etc.
4. Copy the application.
In the new version of the application, the page process shows as plain text in the application builder with no link to edit or delete it and when the page is run, it predictably fails at the processing point of the page process when it tries to find the application process (the id from wwv_flow_processing is shown in the error for the old application process).
The only way to get rid of the page process is to select 'Edit All' and then select and delete it - then everything is hunky dory again.
A minor issue I know, but maybe someone will have the same issue one day and stumble across this thread :)
Cheers
BenAt the moment I cannot say if your link can help. Right now the call of the On demand Process looks like this:
Inside annonymous PL/SQL Region:
<script type="text/javascript">
get = new htmldb_Get(null,'||:APP_ID||'.,'APPLICATION_PROCESS=F_REPORT_NAME',0);
gReturn = get.get();
document.write(gReturn);
</script> -
Possible bug with iTunes 11 ?? (with Smart Playlists)
Hi folks
New to Apple Support, but after upgrading to iTunes 11 earlier today (on my Mac Mini) I've discovered a potential bug / difference in the way it operates compared to earlier versions. Can someone else try something similar and see if they get the same result - I think I read somewhere that v11 is not available on Windows yet, so I cant compare what happens there
I've imported all our CD's into iTunes, and we've set up several Smart Playlists (SP). Using the Rating setting for the songs, we can break them up into groups, eg
Rating 0 = not yet processed
Rating 1 = not interested in listening to again
Rating 2 = kids songs (for our children)
Rating 3 = christmas songs
Rating 4 = songs i like, but my wife probably wouldnt
Rating 5 = songs we both like - good for background music etc
Using Home Sharing to our iPad's rocks !!
Now, onto the bug.
Using the SP that has just songs with Rating 0, I could play any song, set the Rating to whatever, and naturally once set, that disappears from the SP
In all earlier versions of iTunes, playback would continue with the next song, so I could set that Rating, etc etc. Worked really well to churn through a chunk of songs in say 15 minute blocks
With iTunes v11, playback stops as soon as I set the Rating.
How can you help ?????????? Set up a smart playlist with whatever criteria you like - make sure you have a number of songs returned and ensure Live Updating is set, have a song playing, and make that song no longer valid for that SP. Anyone doing this in earlier versions of iTunes should have the next song begin, and if this is a bug, then those using iTunes 11 will have playback stop
Sorry for the long post, but in order to determine a potential bug, you need to describe the situation and how to test it.
Thanks for reading
PS I'm on a 2010 Mac Mini with OSX v10.7.x (whatever the current release of that is) and just upgraded to iTunes 11Soo, maybe it isnt possible bug, but the way Apple have changed iTunes when going to v11. Stooopid
Anyway, found this link about downgrading to an earlier version. I've just completed it and found one or two "errors" in the method, which I'll detail below
http://www.emacconsulting.com/apple/itunes/downgrade-itunes-11-to-itunes-10-7/
In the latter part of the instructions
11) Open your iTunes Music Folder.
If you never moved your iTunes folder it’s located here:
Your HD/Your User/Music/iTunes
Or go to the Finder type: Command + Shift + G
Paste this into the the dialog: ~/Music/iTunes
If you moved it to another hard drive, you will know where to locate your iTunes folder.
12) Open the “Previous iTunes Libraries” folder.
13) Find the most recent copy of the “iTunes Library 2012-xx-xx.itl” file.
Normally it will the last file at the bottom of the list.
14) Drag a copy of the file into the iTunes folder.
15) Delete the “iTunes Library” file.
16) Change the name of the “iTunes Library 2012-xx-xx.itl” to ”iTunes Library” with no .itl extension.
In #11, I simply went to "My HD"/Users/"My User"/Music/iTunes
Copied the latest .itl and moved it up a directory level
The old file in #15 is called "iTunes Library.itl" - which I renamed, and renamed the copied version back to "iTunes Library.itl" = though I do have extensions showing, some people may not and hence wont see the .itl
Anyway all is fixed in my world, and when I launched v10.7, it asked me if I wanted to upgrade to v11 - I said No and not to prompt me again. Playcount issue is resulved, as is changing SmartList criteria with playback continuing
Apple - please correct these bugs before releasing any new versions of iTunes... you've made a very large number of people unhappy -
Hi Everyone.
I would like to report what I think is a bug in Apex 4.0.2.
If you go to my workspace on apex.oracle.com:
Workspace = EEG
Username = [email protected]
Password = galaxy (all lowercase)
Run the application: 37796 - Elie_Various_Goodies [no credentials are required]
This app was imported from my 4.0.1 workspace at my job. On the page I created two Date Picker items, P1_BEGIN_DATE and P1_END_DATE. I set them up so that whenever a user selects a begin date, a dynamic action "MANAGE_DATES" fires and automatically sets P1_END_DATE to this selected begin date value. Now when a user goes to select an end date, the displayed calendar starts at the previously selected begin date rather than the default of "Today".
All of this worked fine on my office (4.0.1) workspace. However, after exporting this app and then importing onto apex.oracle.com, none of this functionality would work. Even worse, whenever I try to select a begin date or even an end date, the selected dates never make it into the date picker fields. Displaying the "Session" window shows these fields as empty.
It was only after I copied the two date picker fields and also re-created my dynamic action (P1_BEGIN_DATE2, P1_END_DATE2, MANAGE_DATES) did my functionality return.
This behavior is quite strange. I can only think this is some sort of bug attributed to the export/import process when exporting a 4.0.1 app into a 4.0.2 workspace. I am not sure if this bizarre behavior happens with non-date picker items. Nor am I sure if this beavior would be repeated if I export/import from 4.0.2 into the another 4.0.2 environment.
Another strange thing I noticed. If I change my date picker items to be "date picker (classic)" type items, the dynamic action does not work at all. This is true in both 4.0.2 and 4.0.1. I'm not sure if this a bug or not. It could be that the classic date picker is just not "javascript" enabled so to speak. If that is true, then it would have been nice if the docs would have warned us about this.
Has anyone else seen this behavior?
Thank you.
ElieHi Joel.
First let me thank you for the warning about allowing "everyone" access to my workspace.
You're correct, of course. Anyone could destroy anything within my workspace. I guess I was too trusting especially as I have seen many posts on the Forum where others have given access to their workspace so that responders can offer help. I really should be more discreet about this. Again, thank you. Needless to say, I have changed my password.
With respect to the possible bug, the MANAGE_DATES dynamic action is intended to be a submit page because that is the only way I can see to get BOTH the P1_END_DATE date picker item as well as the end date textual field to be assigned the selected P1_BEGIN_DATE. I tried to use a dynamic action in which javascript sets the value of the end date textual field to the selected P1_BEGIN_DATE value. This works without the need to submit the page. Unfortunately, this does not cause the P1_END_DATE date picker item to default to this value. Instead, the default remains at today's date. This is why I finally resorted to a dynamic action that submits the page whenever a new value is selected (that is, a "change" event) from the P1_BEGIN_DATE date picker item.
All of this works in my office 4.0.1 environment. However, I was puzzled when this fails under 4.0.2 on the hosted web site at apex.oracle.com. This is why I posted a "possible" bug in 4.0.2.
I hope this all makes sense.
One more thing, as already mentioned in my original post, this "defaulting a date picker" functionality does NOT work at all for the "classic" date picker items in both 4.0.1 nor in 4.0.2. I realize one can implement this functionality (I' guessing) my using, say, a "onChange" javascript call to submit the page. It's just funny that the "classic" date picker items are not acted upon by the dynamic action MANAGE_DATES that submits the page.
Thank you.
Elie -
Is it possible to use an exact phrase and a wildcard in the same query
I am building an address finder, and i have an option where the user can enter part or a full uk postcode. There is a ctxcat index on the address field. I am having a problem searching for part of the postcode, if i enter 'ZZ1 2*' it finds all ZZ1 and all house number 2's if i enter ' " ZZ1 2"*' it fails with an error, is this a bug or is it not possibl to use the exact phrasing and wildcard at the same time.
If its not possible can anyone suggest another way round this query.
Thankhi,
in my table i have a column called address,
these would contain something along the lines of these 2 records.
10 high street anytown ZZ1 3ZZ
3 bridge street anytown ZZ1 8ZZ
If searching on the postcode, the user may enter ZZ1 3 at the moment this would bring back both records, the first one from the ZZ1 and the second one from the house number 3. however if ZZ1 3 is entered i am wanting to just search on the postcode, so it would only match on the first record. so i would like to put the double quotes round the "ZZ1 3" to match on the exact phrase, but then no records come back because of the two letters after the 3, this was why i am asking about the wildcards after the exact phrase ,atch, so it can match the exact phrase of 'ZZ1 3' but then allow any characters after that.
hope this explaings my problem a bit better. -
Possible bug in Photoshop CS6 with app.activeDocument.path.
JavaScript running in Photoshop CS6 under OS X 10.7.5 returns the wrong result for app.activeDocument.path when the file is located on the boot drive. The result is undefined and an error message incorrectly states that the document has not been saved yet. If the file is located on a remote volume, the correct path is returned.
To reproduce this problem, create a new file in Photoshop CS6 on a Mac. Save the file to the desktop. With the file still open, run the following script in ExtendScript Toolkit.
// start script
var thePath = app.activeDocument.path;
alert(thePath);
// end script
Running the same script with a file located on a server volume open in Photoshop correctly returns "/path/to/file.psd" instead of undefined and no error occurs.
This appears to be a bug in Photoshop CS6's JavaScript implementation. This problem did not exist in Photoshop CS3.
A similar issue prevents Photoshop CS6 from saving files to the boot drive using activeDocument.saveAs.
Has anyone else experienced this problem? If so, have you discovered an alternate method to determine the file path or save a file on the boot drive?Don't know if this will help much but at least you can use it to check a document's filepath without throwing an error. And maybe tell if the problem is with the Photoshop DOM.
function hasFilePath(){// returns true/false
var ref = new ActionReference();
ref.putEnumerated( charIDToTypeID("Dcmn"), charIDToTypeID("Ordn"), charIDToTypeID("Trgt") );
return executeActionGet(ref).hasKey(stringIDToTypeID('fileReference'));
function getFilePath(){// returns path as a string if exists, undefined if not
var ref = new ActionReference();
ref.putEnumerated( charIDToTypeID("Dcmn"), charIDToTypeID("Ordn"), charIDToTypeID("Trgt") );
var desc = executeActionGet(ref);
if(desc.hasKey(stringIDToTypeID('fileReference'))) return decodeURI(desc.getPath(stringIDToTypeID('fileReference'))); -
Is it possible to output to div monitor and s-video at the same time?
I'm editing video and want to see the broadcast results on the fly (ie monitor and tv side by side, same image onscreen). Is it possible to output to div monitor and s-video at the same time? Maybe thru a splitter cable. I'm concerned about resolution issues.
This is not possible with a mini.
-
Possible bug? formatted number 0 displays as 4,294,967,295
This is really two questions in one. First, I have a routine
that sometimes provides a result of 0, which is *sometimes*
displayed in an AdvancedDataGrid column as 4,294,967,295, which I'm
assuming is somehow a meaningful number (largest int?). Anyway, I
have an ADG with a column defined as:
<mx:AdvancedDataGridColumn headerText="Remaining work"
labelFunction="rem_work_fmt" textAlign="right" />
The labelFunction called is shown below:
private function rem_work_fmt(item:Object,
column:AdvancedDataGridColumn):String
var num:String =
numberFormatter.format(item.get_remaining_work());
trace ("result: " + num);
return num;
The trace output prints: "result: 0" as expected, but the
number displayed in the grid is sometimes 0 and sometimes
4,294,967,295.
More weirdness, this only happens to the last column in the
ADG. I call the same format logic on a different column and have
never seen the wrong result. Also, the same underlying function
"get_remaining_work()" is called elsewhere on the same data and the
result is correctly displayed in a text field as 0.
Second question, I've run into some other possible bugs,
which I haven't reported because I found a work around. How does
one do that in the beta program?lw1001,
Bugs can be filed in the public bug base at
http://bugs.adobe.com/flex/
You'll need to sign up before you can submit bugs.
Also, if you can attach the bug files to the bug report, it
makes it a lot easier for Adobe to investigate.
Let me know if you have any further questions/problems.
Peter -
A possible *bug* in java jcombobox
Hi all,
I think i found a possible bug in java jcombobox .. i am sure some of you must have already experienced it..
supposedly you put a jcombobox in a jpanel
returned the panel from a method to a calling method..
and that method adds it to another panel that it had created to a frame..
and if this happens dynamicaly at runtime, as only after u click a button..
meaning : without adding the combobox or the immediate parent panelto the contentpane .. directly..
Then,
your combox's keylistener may not catch events fired.
.. this has happened to me many times.. and always i could only find a way out
.. by adding the combobox to panel that is loaded during startup itself and is
.. not returned through a method call.
Your opinions please ?
'Harish.All components in a UI are created at run-time.
When you create your JFrame you call pack() to align and resize the UI. This validates all the components, and sets the default focus on what ever component should have the focus at start up.
When you create components and add them as children of another component you have to validate the child and parent. This can be done by calling JComponent.validate()
As for keylisteners not getting called, this might be fixed if you call grabFocus on the new combobox. I can't see a reason why any listener would stop working.
For me to really understand what your talking about. I'd need to see source code reproducing this problem.
Maybe you are looking for
-
[SOLVED] Pacman "config file could not be read" error during Arch ins
I've been attempting to get Arch setup for a while now, and after having some trouble with partitions, my wireless connecting, and setting up repos and mirrors, which the Wiki helped me solve, I've hit a bigger bump. While updating the system using
-
I have a few compile errors. Can someone give me direction?
I have some compile areas in the following code and I am not really sure how to correct. Can someone give guidance? Thanks import java.io.*; import java.util.*; import java.awt.*; import java.awt.Window.*; import java.awt.event.*; import javax.swing.
-
Frontend Trend Monitoring - Monthly trends for queries
I am currently working on a front end, to get result for the Top 10 Worst Performing Queries. I need to get the query for each and every month as per the user specification, in a Descending order for every month. I think, it is not possible to get th
-
This is a jpg downloaded from the internet. For starters, I'd like to know how best to remove the row of text above the picture without disturbing the pattern underneath. Then I want to bring it into Encore as a DVD menu with a replacement layer wher
-
ITunes (6.05) application quits unexpectedly in OS 10.2.8
Computer wizard and sage: It's getting monotonous. Every time I try to play 6.0.5 iTunes on my OS 10.2.8 system (with a G4), iTunes shuts itself off after a few seconds and a message pops up -- "the iTunes application has quit unexpectedly." I've fre