PDA

View Full Version : F13 + Skype +Opera


nimnull22
20th April 2010, 11:20 PM
Hi.
Please take a look at this output of dmesg:

This happened when I start Opera
Version 10.10, Build 4742, System i686, 2.6.33.2-41.fc13.i686.PAE, Qt library 3.3.8b

operapluginwrap[1344]: segfault at 0 ip (null) sp bff0ac2c error 4 in libXt.so.6.0.0[110000+58000]
operapluginwrap[1377]: segfault at 0 ip (null) sp bfb1f93c error 4 in libm-2.11.90.so[110000+28000]
operapluginwrap[1409]: segfault at 0 ip (null) sp bfc25bec error 4 in libstdc++.so.6.0.13[110000+de000]
operapluginwrap[1425]: segfault at 0 ip (null) sp bfc3ca2c error 4 in libgcc_s-4.4.3-20100409.so.1[110000+1d000]
opera used greatest stack depth: 4924 bytes left
operapluginwrap[1600]: segfault at 0 ip (null) sp bf94f80c error 4 in librt-2.11.90.so[110000+8000]
operapluginwrap[1632]: segfault at 0 ip (null) sp bffbfe2c error 4 in libXt.so.6.0.0[110000+58000]
operapluginwrap[1664]: segfault at 0 ip (null) sp bf9deadc error 4 in libXext.so.6.4.0[110000+10000]
operapluginwrap[1680]: segfault at 0 ip (null) sp bf8a405c error 4 in libgmodule-2.0.so.0.2400.0[110000+3000]
type=1401 audit(1271800069.829:13316): security_compute_sid: invalid context system_u:system_r:xauth_t:s0-s0:c0.c1023 for scontext=system_u:system_r:unconfined_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xauth_exec_t:s0 tclass=process
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
process `skype' is using obsolete setsockopt SO_BSDCOMPAT
operapluginwrap[2350]: segfault at 0 ip (null) sp bfaaebfc error 4 in libgcc_s-4.4.3-20100409.so.1[110000+1d000]
operapluginwrap[2383]: segfault at 0 ip (null) sp bfcf6dfc error 4 in libdl-2.11.90.so[110000+3000]
operapluginwrap[2415]: segfault at 0 ip (null) sp bfaeaa0c error 4 in libXt.so.6.0.0[110000+58000]
operapluginwrap[2431]: segfault at 0 ip (null) sp bff8e69c error 4 in libstdc++.so.6.0.13[110000+de000]



This, I think, when I started Skype 2.1.0.81:

=================================
[ INFO: inconsistent lock state ]
2.6.33.2-41.fc13.i686.PAE #1
---------------------------------
inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
skype/2498 [HC1[1]:SC0[0]:HE0:SE1] takes:
(&(&tu->qlock)->rlock){?.+...}, at: [<f9300585>] snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
{HARDIRQ-ON-W} state was registered at:
[<c046a47c>] __lock_acquire+0x2d4/0xb89
[<c046adc4>] lock_acquire+0x93/0xb1
[<c07c61c3>] _raw_spin_lock+0x23/0x53
[<f930046d>] snd_timer_user_ccallback+0x5a/0x9d [snd_timer]
[<f9300e02>] snd_timer_notify1+0x82/0xfe [snd_timer]
[<f9300fa8>] _snd_timer_stop+0x12a/0x134 [snd_timer]
[<f93010a9>] snd_timer_stop+0x18/0x47 [snd_timer]
[<f9301d0d>] snd_timer_user_params+0x90/0x1dc [snd_timer]
[<f930255f>] snd_timer_user_ioctl+0x5b1/0x6d4 [snd_timer]
[<c04f3bf1>] vfs_ioctl+0x2c/0x96
[<c04f41a4>] do_vfs_ioctl+0x49b/0x4d9
[<c04f4228>] sys_ioctl+0x46/0x66
[<c07c6b44>] syscall_call+0x7/0xb
irq event stamp: 434926
hardirqs last enabled at (434925): [<c07c6922>] _raw_spin_unlock_irq+0x27/0x30
hardirqs last disabled at (434926): [<c04091ae>] common_interrupt+0x2e/0x3c
softirqs last enabled at (434908): [<c0447c97>] __do_softirq+0x164/0x173
softirqs last disabled at (434903): [<c0447ce1>] do_softirq+0x3b/0x5f

other info that might help us debug this:
2 locks held by skype/2498:
#0: (snd_pcm_link_rwlock){.-.-..}, at: [<f9327de6>] snd_pcm_period_elapsed+0x65/0x40e [snd_pcm]
#1: (&(&substream->self_group.lock)->rlock){-.-...}, at: [<f9327df9>] snd_pcm_period_elapsed+0x78/0x40e [snd_pcm]

stack backtrace:
Pid: 2498, comm: skype Not tainted 2.6.33.2-41.fc13.i686.PAE #1
Call Trace:
[<c07c3fad>] ? printk+0x14/0x17
[<c0469476>] valid_state+0x131/0x144
[<c046957b>] mark_lock+0xf2/0x1e1
[<c0469c30>] ? check_usage_forwards+0x0/0x68
[<c046a40e>] __lock_acquire+0x266/0xb89
[<c040d935>] ? sched_clock+0x9/0xd
[<c045e57b>] ? sched_clock_local+0x17/0x11e
[<c046adc4>] lock_acquire+0x93/0xb1
[<f9300585>] ? snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
[<c07c61c3>] _raw_spin_lock+0x23/0x53
[<f9300585>] ? snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
[<f9300585>] snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
[<f9300557>] ? snd_timer_user_tinterrupt+0x0/0x137 [snd_timer]
[<f9301537>] snd_timer_interrupt+0x20e/0x263 [snd_timer]
[<f9328139>] snd_pcm_period_elapsed+0x3b8/0x40e [snd_pcm]
[<f93f825e>] ? snd_intel8x0_interrupt+0x17b/0x1e0 [snd_intel8x0]
[<c0468546>] ? trace_hardirqs_off+0xb/0xd
[<f93f8271>] snd_intel8x0_interrupt+0x18e/0x1e0 [snd_intel8x0]
[<c049012d>] handle_IRQ_event+0x4b/0xf6
[<c0491aef>] handle_fasteoi_irq+0x86/0xbd
[<c040a7dc>] handle_irq+0x40/0x4c
[<c040a04b>] do_IRQ+0x46/0x9f
[<c04091b5>] common_interrupt+0x35/0x3c
[<c046007b>] ? sys_setgroups+0x4b/0xb4
[<c07c6924>] ? _raw_spin_unlock_irq+0x29/0x30
[<c0453d55>] do_sys_times+0x59/0x8b
[<c0453da5>] sys_times+0x1e/0x48
[<c07c6b44>] syscall_call+0x7/0xb
[<c07c0000>] ? amd_64_threshold_cpu_callback+0x113/0x245

This happens then I tried to open audio settings in skype, after a while skype closes it self.

Desktop - XFCE 4.6.1

nimnull22
22nd April 2010, 11:29 PM
I don't know if any one is interested, but after last update to 2.6.33.2-57.fc13.i686.PAE, after skype starts it take about 100% CPU and I got follow in dmesg:


=================================
[ INFO: inconsistent lock state ]
2.6.33.2-57.fc13.i686.PAE #1
---------------------------------
inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
skype/1870 [HC1[1]:SC0[0]:HE0:SE1] takes:
(&(&tu->qlock)->rlock){?.+...}, at: [<f92d9585>] snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
{HARDIRQ-ON-W} state was registered at:
[<c046a44c>] __lock_acquire+0x2d4/0xb89
[<c046ad94>] lock_acquire+0x93/0xb1
[<c07c6593>] _raw_spin_lock+0x23/0x53
[<f92d946d>] snd_timer_user_ccallback+0x5a/0x9d [snd_timer]
[<f92d9e02>] snd_timer_notify1+0x82/0xfe [snd_timer]
[<f92d9fa8>] _snd_timer_stop+0x12a/0x134 [snd_timer]
[<f92da0a9>] snd_timer_stop+0x18/0x47 [snd_timer]
[<f92dad0d>] snd_timer_user_params+0x90/0x1dc [snd_timer]
[<f92db55f>] snd_timer_user_ioctl+0x5b1/0x6d4 [snd_timer]
[<c04f3bc1>] vfs_ioctl+0x2c/0x96
[<c04f4174>] do_vfs_ioctl+0x49b/0x4d9
[<c04f41f8>] sys_ioctl+0x46/0x66
[<c07c6f14>] syscall_call+0x7/0xb
irq event stamp: 442326
hardirqs last enabled at (442325): [<c07c6cf2>] _raw_spin_unlock_irq+0x27/0x30
hardirqs last disabled at (442326): [<c04091ae>] common_interrupt+0x2e/0x3c
softirqs last enabled at (442070): [<c0447c67>] __do_softirq+0x164/0x173
softirqs last disabled at (442065): [<c0447cb1>] do_softirq+0x3b/0x5f

other info that might help us debug this:
2 locks held by skype/1870:
#0: (snd_pcm_link_rwlock){.-.-..}, at: [<f9364dea>] snd_pcm_period_elapsed+0x65/0x40e [snd_pcm]
#1: (&(&substream->self_group.lock)->rlock){-.-...}, at: [<f9364dfd>] snd_pcm_period_elapsed+0x78/0x40e [snd_pcm]

stack backtrace:
Pid: 1870, comm: skype Not tainted 2.6.33.2-57.fc13.i686.PAE #1
Call Trace:
[<c07c437d>] ? printk+0x14/0x17
[<c0469446>] valid_state+0x131/0x144
[<c046954b>] mark_lock+0xf2/0x1e1
[<c0469c00>] ? check_usage_forwards+0x0/0x68
[<c046a3de>] __lock_acquire+0x266/0xb89
[<c040d935>] ? sched_clock+0x9/0xd
[<c045e54b>] ? sched_clock_local+0x17/0x11e
[<c046ad94>] lock_acquire+0x93/0xb1
[<f92d9585>] ? snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
[<c07c6593>] _raw_spin_lock+0x23/0x53
[<f92d9585>] ? snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
[<f92d9585>] snd_timer_user_tinterrupt+0x2e/0x137 [snd_timer]
[<f92d9557>] ? snd_timer_user_tinterrupt+0x0/0x137 [snd_timer]
[<f92da537>] snd_timer_interrupt+0x20e/0x263 [snd_timer]
[<f936513d>] snd_pcm_period_elapsed+0x3b8/0x40e [snd_pcm]
[<f960c25e>] ? snd_intel8x0_interrupt+0x17b/0x1e0 [snd_intel8x0]
[<c0468516>] ? trace_hardirqs_off+0xb/0xd
[<f960c271>] snd_intel8x0_interrupt+0x18e/0x1e0 [snd_intel8x0]
[<c04900fd>] handle_IRQ_event+0x4b/0xf6
[<c0491abf>] handle_fasteoi_irq+0x86/0xbd
[<c040a7dc>] handle_irq+0x40/0x4c
[<c040a04b>] do_IRQ+0x46/0x9f
[<c04c8430>] ? might_fault+0x4c/0x86
[<c04091b5>] common_interrupt+0x35/0x3c
[<c04c8430>] ? might_fault+0x4c/0x86
[<c04c007b>] ? kswapd+0x4cd/0x6de
[<c046b731>] ? lock_release+0x178/0x183
[<c04c8465>] might_fault+0x81/0x86
[<c05ccac6>] copy_to_user+0x34/0x10a
[<c0453d83>] sys_times+0x2c/0x48
[<c07c6f14>] syscall_call+0x7/0xb
[<c07c0000>] ? allocate_threshold_blocks+0x145/0x1be

Hope it will help to fix.