[TH - 64] Chromium chromoli po upgrade

[Elan Ruusamäe]

On 11.02.2013 22:24, Lukasz Glebicki wrote:
> On Friday 30 of November 2012 09:54:20 Łukasz Maśko wrote:
>> >Dnia piątek, 30 listopada 2012, Grzegorz Sójka napisał:
>>> > >U mnie chromium-browser-23.0.1271.64-3.x86_64 też się wywraca. Na dwóch
>>> > >różnych maszynach x86_64 te same objawy. Pojawia się okno ale zamiast
>>> > >strony startowej na środku jest smutna mordka i komentarz, że coś poszło
>>> > >nie tak. Dmesg wywala:
>>> > >
>>> > >[  282.276966] chromium-browse[2097]: segfault at 122 ip
>>> > >00007fafd200d713 sp 00007fafb7372370 error 6 in
>>> > >chromium-browser[7fafd11d3000+3d17000]
>>> > >[  294.557690] chromium-browse[2119]: segfault at 122 ip
>>> > >00007fafd200d713 sp 00007fafb7372370 error 6 in
>>> > >chromium-browser[7fafd11d3000+3d17000]
>> >
>> >Czyżby pierwszy raz od dawna, że i686 jest OK a na x86_64 nie?
> Hello,
> Topic taken from users-pl, which describe unusable cb since version 23.
>
> The problem with chromium-browser occurs with seccomp-filter.
>
> Running chromium with --disable-seccomp-filter-sandbox is a workaround.
>
> Google took me to:
>
> http://code.google.com/p/chromium/issues/detail?id=149834
>
> and then to
>
> http://src.chromium.org/viewvc/chrome/branches/1271/src/content/common/sandbox_seccomp_bpf_linux.cc?r1=162147&r2=162146&pathrev=162147
> http://src.chromium.org/viewvc/chrome/trunk/src/content/browser/renderer_host/render_process_host_impl.cc?r1=140792&r2=140875&pathrev=140875
>
> It seems that source has this patch, but it doesn't work.
>
> Any ideas?

as much i understood reading the bugreport then "segfault at NUMBER", 
means syscall NUMBER in HEX, the reports you referred had 0x19, but our 
(yours and mine) are 0x122 hex (290 dec) which is different syscall:

Feb 11 19:38:59 blodnatt kernel: : [  375.154516] chromium-browse[3544]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  375.292081] chromium-browse[3551]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  375.857206] chromium-browse[3563]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  375.882080] chromium-browse[3568]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  376.026527] chromium-browse[3573]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  376.037300] chromium-browse[3578]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  376.053965] chromium-browse[3583]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  376.075011] chromium-browse[3588]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:00 blodnatt kernel: : [  376.097798] chromium-browse[3593]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:14 blodnatt kernel: : [  390.074960] chromium-browse[3648]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:15 blodnatt kernel: : [  391.065551] chromium-browse[3653]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:16 blodnatt kernel: : [  391.664702] chromium-browse[3658]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:25 blodnatt kernel: : [  400.947865] chromium-browse[3664]: 
segfault at 122 ip 00007f3f9c5ea353 sp 00007f3f865e5330 error 6 in 
chromium-browser[7f3f9b794000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.581665] chromium-browse[3716]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.588052] chromium-browse[3719]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.599777] chromium-browse[3725]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.622623] chromium-browse[3732]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.637877] chromium-browse[3736]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.693884] chromium-browse[3742]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.726017] chromium-browse[3746]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.754289] chromium-browse[3753]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:39:30 blodnatt kernel: : [  405.865100] chromium-browse[3757]: 
segfault at 122 ip 00007f8c747b4353 sp 00007f8c5e7af330 error 6 in 
chromium-browser[7f8c7395e000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.213160] chromium-browse[4938]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.220722] chromium-browse[4941]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.249485] chromium-browse[4949]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.268072] chromium-browse[4954]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.278388] chromium-browse[4959]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.317336] chromium-browse[4964]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.373686] chromium-browse[4969]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.395218] chromium-browse[4974]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]
Feb 11 19:40:31 blodnatt kernel: : [  466.530506] chromium-browse[4978]: 
segfault at 122 ip 00007fc083ddb353 sp 00007fc06ddd6330 error 6 in 
chromium-browser[7fc082f85000+3e95000]


$ grep  -r  __NR_.*290 /usr/include/asm
/usr/include/asm/unistd_32.h:#define __NR_ioprio_get 290
/usr/include/asm/unistd_64.h:#define __NR_eventfd2 290
/usr/include/asm/unistd_x32.h:#define __NR_eventfd2 (__X32_SYSCALL_BIT + 
290)

so seems different problem, you could try patch similarily by allowing 
__NR_eventfd2 ?

ps: you can add --disable-seccomp-filter-sandbox to 
/etc/chromium-browser/default as CHROMIUM_FLAGS env var
or "Chrome Flags" inside profile (as text file) to make the option more 
permanent. also $CHROMIUM_USER_FLAGS works as well (put it to your 
~/.*profile) if you don't create the "Chrome Flags" file.


-- 
glen