From: Willy Tarreau <w@1wt.eu>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Lukasz Kalamlacki <lukasz@pm.kalamlacki.eu>,
Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
Pavlos Parissis <pavlos.parissis@gmail.com>
Subject: Re: Cannot compile 6.1.2 kernel release
Date: Mon, 2 Jan 2023 04:55:46 +0100 [thread overview]
Message-ID: <20230102035546.GA28406@1wt.eu> (raw)
In-Reply-To: <Y7JRE4yO6ZOj0HyH@debian.me>
Hi Bagas,
On Mon, Jan 02, 2023 at 10:35:47AM +0700, Bagas Sanjaya wrote:
> On Sun, Jan 01, 2023 at 11:05:18AM +0100, Willy Tarreau wrote:
> > >
> > > To be precise I have this on gcc 10 in Debian:
> > >
> > >
> > > during GIMPLE pass: fre
> > > drivers/media/pci/cx18/cx18-i2c.c: In function 'init_cx18_i2c':
> > > drivers/media/pci/cx18/cx18-i2c.c:300:1: internal compiler error:
> > > Segmentation fault
> > > 300 | }
> >
> > As Greg said it's definitely a compiler bug, so it will interest Gcc
> > developers, or your distro's gcc package maintainers in case it's not
> > up to date. There are toolchains available on kernel.org here:
> >
> > https://mirrors.edge.kernel.org/pub/tools/crosstool/
> >
> > The laest 10.x available is 10.4. If it works with this one it may indicate
> > that your package is lacking some recent fixes, so it might be a question
> > for your distro's gcc package maintainers. If it fails it indicates a bug
> > not yet fixed in gcc and your distro maintainers won't be of any help here,
> > you'll have to report it to the gcc devs instead.
> >
> > Note that they'll very likely ask about a reproducer (and most likely your
> > config). But a quick test for me with this driver built as a module on
> > x86_64 with gcc-10.4 from kernel.org doesn't show any problem:
> >
> > $ make CROSS_COMPILE=/f/tc/nolibc/gcc-10.4.0-nolibc/x86_64-linux/bin/x86_64-linux- drivers/media/pci/cx18/cx18-i2c.o
> > (...)
> > CC [M] drivers/media/pci/cx18/cx18-i2c.o
> > $ ll drivers/media/pci/cx18/cx18-i2c.o
> > -rw-rw-r-- 1 willy users 33920 Jan 1 11:00 drivers/media/pci/cx18/cx18-i2c.o
> >
>
> Hi Willy,
>
> I can confirmed that no segfault reported when compiling
> x86_64-defconfig + CONFIG_VIDEO_CX18 using default gcc from Debian 11,
> so this can be hardware issues.
Unlikely, hardware issues rarely cause a crash on the same file in a
project as large as the kernel. However, a bug in the compiler may be
triggered by specific combinations of options, or even the environment
sometimes.
Also, Pavlos also got the problem on 6.0.16 and got it fixed by updating
the compiler.
I think that someone should report the bug to the debian gcc maintainers
and tell them that 10.4.0 as shipped on kernel.org fixes the problem. It
could help them reproduce the issue, update, confirm the problem is gone,
and issue a fixed package.
Thanks,
Willy
next prev parent reply other threads:[~2023-01-02 3:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 16:58 Cannot compile 6.1.2 kernel release Łukasz Kalamłacki
2023-01-01 6:53 ` Willy Tarreau
2023-01-01 8:14 ` Łukasz Kalamłacki
2023-01-01 8:47 ` Greg KH
2023-01-01 9:01 ` Łukasz Kalamłacki
2023-01-01 10:05 ` Willy Tarreau
2023-01-01 10:12 ` Łukasz Kalamłacki
2023-01-01 10:20 ` Greg KH
2023-01-01 10:38 ` Łukasz Kalamłacki
2023-01-02 0:13 ` Pavlos Parissis
2023-01-02 3:35 ` Bagas Sanjaya
2023-01-02 3:55 ` Willy Tarreau [this message]
2023-01-03 16:32 ` Łukasz Kalamłacki
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=20230102035546.GA28406@1wt.eu \
--to=w@1wt.eu \
--cc=bagasdotme@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lukasz@pm.kalamlacki.eu \
--cc=pavlos.parissis@gmail.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.