| 1 |
On 2 June 2011 11:21, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> |
| 3 |
> Chromium is not the problem, Flash is the problem. |
| 4 |
> |
| 5 |
> Flash is a piece of shit that has never worked right and Adobe are a bunch of |
| 6 |
> fools that cannot code properly or securely. I can comfortably say this based |
| 7 |
> on long hard bitter experience by the entire Linux community. |
| 8 |
> |
| 9 |
> If you choose to use Flash, you get to put up with the resulting problems. |
| 10 |
|
| 11 |
I'm not sure the Flash is the problem. Chromium uses Flash through |
| 12 |
nspluginwrapper. I removed nspluginwrapper package and I recompiled |
| 13 |
few package which depended on nspluginwrapper package. And Chromium |
| 14 |
freezin and creating a D process as you can see on this picture. [1] |
| 15 |
|
| 16 |
http://sayusi.hu/blog/picture_about_htop |
| 17 |
|
| 18 |
I asked my friends - they are *nix administrators, and they told me |
| 19 |
this below could be helpful. However, I don't have any idea what it |
| 20 |
means. |
| 21 |
|
| 22 |
sa-home sayusi # cat /proc/6725/wchan |
| 23 |
call_rwsem_down_read_failed |
| 24 |
sa-home sayusi # |
| 25 |
|
| 26 |
The callstack look like this (the copied just a part of it): |
| 27 |
Jun 25 18:33:38 sa-home eep+0x7c/0x80 |
| 28 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8142017b>] |
| 29 |
system_call_fastpath+0x16/0x1b |
| 30 |
Jun 25 18:33:38 sa-home kernel: chrome S ffff8800b334b790 |
| 31 |
0 6923 6730 0x00000000 |
| 32 |
Jun 25 18:33:38 sa-home kernel: ffff8800a6c47c48 0000000000000086 |
| 33 |
ffff8800a6c47b18 ffffffff8109fe4a |
| 34 |
Jun 25 18:33:38 sa-home kernel: ffff8800a6c47fd8 ffff8800a6c46010 |
| 35 |
0000000000000001 ffff8800b334b9a0 |
| 36 |
Jun 25 18:33:38 sa-home kernel: 0000000000004000 000000000000d580 |
| 37 |
ffff8800a6c47fd8 00000001a6c47d48 |
| 38 |
Jun 25 18:33:38 sa-home kernel: Call Trace: |
| 39 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8109fe4a>] ? |
| 40 |
zone_watermark_ok+0x1a/0x20 |
| 41 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8120a330>] ? |
| 42 |
timerqueue_add+0x60/0xb0 |
| 43 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff81054aef>] ? |
| 44 |
__hrtimer_start_range_ns+0x1df/0x3d0 |
| 45 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff810600fa>] ? |
| 46 |
get_futex_key+0x15a/0x1c0 |
| 47 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff810603b5>] |
| 48 |
futex_wait_queue_me+0xc5/0x100 |
| 49 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff810605fc>] |
| 50 |
futex_wait+0x1ac/0x290 |
| 51 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff81053e40>] ? |
| 52 |
update_rmtp+0x80/0x80 |
| 53 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff810624b1>] |
| 54 |
do_futex+0x101/0xac0 |
| 55 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff810b6ee0>] ? |
| 56 |
handle_mm_fault+0x120/0x230 |
| 57 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff81026a6c>] ? |
| 58 |
do_page_fault+0x1ac/0x430 |
| 59 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff810be7b4>] ? |
| 60 |
do_mmap_pgoff+0x344/0x390 |
| 61 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff81062ee6>] |
| 62 |
sys_futex+0x76/0x170 |
| 63 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff810be900>] ? |
| 64 |
sys_mmap_pgoff+0x100/0x190 |
| 65 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8142017b>] |
| 66 |
system_call_fastpath+0x16/0x1b |
| 67 |
Jun 25 18:33:38 sa-home kernel: chrome S 0000000000000001 |
| 68 |
0 6927 6730 0x00000000 |
| 69 |
Jun 25 18:33:38 sa-home kernel: ffff8800a6d0bda8 0000000000000086 |
| 70 |
0000000000000001 ffff88013f4c1710 |
| 71 |
Jun 25 18:33:38 sa-home kernel: ffff8800a6d0bfd8 ffff8800a6d0a010 |
| 72 |
0000000000000001 ffff8800a6c8eec0 |
| 73 |
Jun 25 18:33:38 sa-home kernel: 0000000000004000 000000000000d580 |
| 74 |
ffff8800a6d0bfd8 000000018171eec8 |
| 75 |
Jun 25 18:33:38 sa-home kernel: Call Trace: |
| 76 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8136daad>] ? |
| 77 |
sock_aio_read+0x16d/0x180 |
| 78 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8141e360>] ? |
| 79 |
__mutex_lock_slowpath+0x1c0/0x260 |
| 80 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8136d4f5>] ? |
| 81 |
sock_poll+0x15/0x20 |
| 82 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8141ec55>] |
| 83 |
schedule_hrtimeout_range_clock+0x115/0x130 |
| 84 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8141e199>] ? |
| 85 |
mutex_unlock+0x9/0x10 |
| 86 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff81106ea3>] ? |
| 87 |
ep_scan_ready_list+0x183/0x190 |
| 88 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8141ec7e>] |
| 89 |
schedule_hrtimeout_range+0xe/0x10 |
| 90 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff811071bc>] |
| 91 |
ep_poll+0x2ec/0x350 |
| 92 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff81031b10>] ? |
| 93 |
try_to_wake_up+0x120/0x120 |
| 94 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff811072e5>] |
| 95 |
sys_epoll_wait+0xc5/0xe0 |
| 96 |
Jun 25 18:33:38 sa-home kernel: [<ffffffff8142017b>] |
| 97 |
system_call_fastpath+0x16/0x1b |
| 98 |
Jun 25 18:33:38 sa-home kernel: SignalSender S ffff8800b3f079d0 |
| 99 |
0 6928 6730 0x00000000 |
| 100 |
Jun 25 18:33:38 sa-home kernel: ffff8800a6c85c48 0000000000000086 |
| 101 |
0000000000000000 ffffffff81611020 |
| 102 |
Jun 25 18:33:38 sa-home kernel: ffff8800a6c85fd8 ffff8800a6c84010 |
| 103 |
0000000000000000 ffff8800b3f07be0 |
| 104 |
Jun 25 18:33:38 sa-home kernel: 0000000000004000 000000000000d580 |
| 105 |
ffff8800a6c85fd8 0000000000000000 |
| 106 |
|
| 107 |
My question is that, should I report it on bugs.gentoo.org? By the |
| 108 |
way, this bug is not depend on the version. |
| 109 |
|
| 110 |
-- |
| 111 |
- - |
| 112 |
-- Csanyi Andras (Sayusi Ando) -- http://sayusi.hu -- |
| 113 |
http://facebook.com/andras.csanyi |
| 114 |
-- ""Trust in God and keep your gunpowder dry!" - Cromwell |
Archives