From: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Slade Watkins <srw@sladewatkins.net>,
Marc Miltenberger <marcmiltenberger@gmail.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: 6.0.0-RC kernels trigger Firefox snap bug with 6.0.0-rc3 through 6.0.0-rc7
Date: Fri, 14 Oct 2022 12:32:55 +0200 [thread overview]
Message-ID: <6375f31f-316a-bebc-6aec-c6241049e401@alu.unizg.hr> (raw)
In-Reply-To: <29362d2e-eec6-5a23-4354-cf8868d50b2c@alu.unizg.hr>
Hi everybody,
On 10/13/22 15:24, Mirsad Goran Todorovac wrote:
> Thank you for the instruction for how to shorten the bisection time.
> My fastest build was almost 2 hours.
>
> This bug did appear with the mainline Ubuntu's and ElRepo's 6.0.0
> kernels, however not with the
> /usr/bin/firefox build, but only that using snapd, squashfs and
> /snap/bin/firefox ...
>
> The Firefox 91.x esr was unaffected, indeed, in a couple of days of
> testing its work (on AL).
>
> However, please not that this bug is no deterministic, and that it can
> take from a couple of hours
> to an overnight work to manifest.
>
> The "make localmodconfig" feature will probably help reducing the
> build time, but I am also doing
> my day job stuff which by the Murphy's law surged right now ...
>
> You second request, to reproduce with Firefox from the dev site, is as
> you will understand impossible
> to meet: the bug occurred only with Firefox 104.x and 105.0.1,
> 105.0.2, 105.0.3 in Ubuntu snap
> release (and the snap release guest installed at AlmaLinux, the CentOS
> fork).
>
> I was able to confirm that AppArmor doesn't affect behaviour once the
> Firefox misbehaves.
> After starting to crash tabs and refusing to connect to the Internet
> from inside Yahoo mail (Chrome
> simultaneously connected), then it complained about libmozsandbox.so
> version and Verneed record.
>
> -Mirsad
>
> On 12.10.2022. 9:46, Bagas Sanjaya wrote:
>> Hi Mirsad,
>>
>> The bug doesn't appear on 6.0 mainline release. However, in my case,
>> Firefox is downloaded and installed from official Mozilla binary [1].
>>
>> Also, many developers here want to see bisection result. In order to
>> shorten kernel build time (and thus time needed for bisection),
>> you can strip out unneeded modules in your kernel configuration with
>> "make localmodconfig". Ensure that all devices on your computer is
>> plugged in before running that. And as other people pointed, base
>> your localmodconfig from last working kernel.
>>
>> In any case, please reproduce with Firefox from [1].
>>
>> Thanks.
>>
>> [1]: https://www.mozilla.org/en-US/firefox/
>>
I tried the "make localmodconfig" and provided the default answers
([ENTER]) to all questions
the script asked as advised here:
https://www.stolaf.edu/people/rab/os/linux-compile.html .
However, though it built much faster, the stripped version did not
trigger the bug.
I am now trying to reproduce the bug with v6.0-rc[123] with
config-{051913,060000}.
This brings a lot of combinations, and though I am a newbie, I noticed
that build scripts
start with "make clean" for both deb-pkg and rpm-pkg.
Is there a way to rebuild only the stuff that changed between the versions?
Thank you.
--
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
--
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
next prev parent reply other threads:[~2022-10-14 10:33 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 17:57 6.0.0-RC kernels trigger Firefox snap bug with 6.0.0-rc3 through 6.0.0-rc7 Mirsad Goran Todorovac
2022-09-30 10:48 ` BUG: " Mirsad Todorovac
2022-09-30 11:21 ` Slade Watkins
2022-09-30 11:44 ` Mirsad Todorovac
2022-09-30 12:03 ` Slade Watkins
2022-09-30 18:27 ` Slade Watkins
2022-10-03 8:18 ` Mirsad Goran Todorovac
2022-10-07 8:47 ` Slade Watkins
2022-10-07 10:55 ` Mirsad Goran Todorovac
2022-10-06 10:39 ` Marc Miltenberger
2022-10-06 16:27 ` Slade Watkins
2022-10-06 12:00 ` Thorsten Leemhuis
2022-10-06 12:25 ` Thorsten Leemhuis
2022-10-06 12:43 ` Mirsad Todorovac
2022-10-06 13:23 ` Thorsten Leemhuis
[not found] ` <c05134cc-92fa-dac2-e738-cf6fae194521@alu.unizg.hr>
2022-10-06 16:58 ` Thorsten Leemhuis
[not found] ` <f23494b5-b4ea-a32a-e260-4541039dedc8@alu.unizg.hr>
2022-10-07 6:09 ` Mirsad Goran Todorovac
2022-10-07 6:31 ` Mirsad Goran Todorovac
2022-10-08 13:41 ` Mirsad Goran Todorovac
2022-10-08 16:46 ` Mirsad Goran Todorovac
[not found] ` <c40786ab-8b3b-9b64-683f-dac589c024df@alu.unizg.hr>
2022-10-09 6:45 ` BUG reproduced: " Thorsten Leemhuis
2022-10-09 22:45 ` Slade Watkins
2022-10-11 17:53 ` Mirsad Goran Todorovac
2022-10-12 6:05 ` Mirsad Todorovac
2022-10-12 22:58 ` Slade Watkins
2022-10-06 12:38 ` Mirsad Todorovac
2022-10-12 7:46 ` Bagas Sanjaya
2022-10-13 13:24 ` Mirsad Goran Todorovac
2022-10-14 10:32 ` Mirsad Todorovac [this message]
2022-10-14 12:28 ` Bagas Sanjaya
2022-10-14 15:06 ` Mirsad Todorovac
2022-10-14 21:44 ` Mirsad Goran Todorovac
[not found] ` <ddf13e46-c091-80b2-3b57-c43ac45435f0@alu.unizg.hr>
2022-10-15 14:59 ` Fwd: BISECT result: " Mirsad Goran Todorovac
2022-10-15 15:32 ` Thorsten Leemhuis
2022-10-15 20:59 ` Phillip Lougher
2022-10-16 12:21 ` Bagas Sanjaya
2022-10-16 12:24 ` Bagas Sanjaya
2022-10-16 12:43 ` Thorsten Leemhuis
2022-11-04 12:06 ` BISECT result: 6.0.0-RC kernels trigger Firefox snap bug with 6.0.0-rc3 through 6.0.0-rc7 #forregzbot Thorsten Leemhuis
2022-10-17 9:45 ` BISECT result: 6.0.0-RC kernels trigger Firefox snap bug with 6.0.0-rc3 through 6.0.0-rc7 Bagas Sanjaya
2022-10-17 12:32 ` Bagas Sanjaya
2022-10-17 17:25 ` Phillip Lougher
2022-10-18 1:38 ` Bagas Sanjaya
2022-10-18 8:35 ` Bagas Sanjaya
2022-10-16 15:55 ` Mirsad Goran Todorovac
2022-10-16 19:55 ` Phillip Lougher
2022-10-16 20:19 ` Phillip Lougher
2022-10-17 2:03 ` Bagas Sanjaya
2022-10-17 2:41 ` Mirsad Goran Todorovac
2022-10-17 4:15 ` Bagas Sanjaya
2022-10-17 8:32 ` Mirsad Goran Todorovac
2022-10-17 13:22 ` Mirsad Goran Todorovac
2022-10-17 13:59 ` Phillip Lougher
2022-10-18 5:49 ` Mirsad Todorovac
2022-10-18 2:15 ` Jintao Yin
2022-10-18 6:52 ` Mirsad Todorovac
2022-10-18 8:24 ` Hsin-Yi Wang
2022-10-18 9:23 ` Mirsad Todorovac
2022-10-18 12:59 ` Bagas Sanjaya
2022-10-18 13:38 ` Phillip Lougher
2022-10-18 13:36 ` Phillip Lougher
2022-10-18 7:23 ` Bagas Sanjaya
2022-10-18 8:33 ` Bagas Sanjaya
2022-10-18 17:15 ` Phillip Lougher
2022-10-18 17:41 ` Mirsad Goran Todorovac
2022-10-18 17:41 ` Phillip Lougher
[not found] ` <1b41bf99-754e-8b90-cc2c-67f50642e2dc@alu.unizg.hr>
2022-10-18 21:34 ` Mirsad Goran Todorovac
2022-10-19 5:17 ` Slade Watkins
2022-10-19 11:07 ` Mirsad Goran Todorovac
2022-10-19 7:53 ` Bagas Sanjaya
2022-10-20 6:59 ` Jintao Yin
2022-10-20 7:43 ` Jintao Yin
2022-10-20 9:51 ` Mirsad Goran Todorovac
2022-10-20 13:02 ` Bagas Sanjaya
2022-10-20 13:55 ` Jintao Yin
2022-10-20 15:00 ` Mirsad Todorovac
2022-10-20 15:45 ` Phillip Lougher
2022-10-20 23:23 ` Bagas Sanjaya
2022-10-20 23:44 ` Slade Watkins
2022-10-21 1:48 ` Phillip Lougher
2022-10-21 7:12 ` Mirsad Goran Todorovac
2022-10-21 8:33 ` Mirsad Goran Todorovac
2022-10-21 3:09 ` Jintao Yin
2022-10-20 15:49 ` Phillip Lougher
2022-10-20 16:00 ` Mirsad Todorovac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6375f31f-316a-bebc-6aec-c6241049e401@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcmiltenberger@gmail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=srw@sladewatkins.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).