Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Lukasz Kalamlacki <lukasz@pm.kalamlacki.eu>
Cc: Greg KH <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Re: Cannot compile 6.1.2 kernel release
Date: Sun, 1 Jan 2023 11:05:18 +0100	[thread overview]
Message-ID: <20230101100518.GA21587@1wt.eu> (raw)
In-Reply-To: <187e8f10-2b73-3a18-d9ad-48b2d84bd6b9@pm.kalamlacki.eu>

On Sun, Jan 01, 2023 at 09:01:22AM +0000, Lukasz Kalamlacki wrote:
> 
> On 1.01.2023 09:47, Greg KH wrote:
> > On Sun, Jan 01, 2023 at 08:14:12AM +0000, Lukasz Kalamlacki wrote:
> >> On 1.01.2023 07:53, Willy Tarreau wrote:
> >>> On Sat, Dec 31, 2022 at 04:58:51PM +0000, Lukasz Kalamlacki wrote:
> >>>> Hey,
> >>>>
> >>>>
> >>>> Do you have an issue compiling 6.1.2 linux kernel?
> >>>>
> >>>> I cannot compile it.
> >>> For me it compiles and boots. You'll need to share your config and error
> >>> report if you want to get some help.
> >>>
> >>> Willy
> >> I was trying to compile on Debian Bullseye where default gcc is version
> >> 10, when I upgraded gcc to version 12 from sid repo i Was able to
> >> compile too. On stable Debian without addition during compile
> >> "segmentation fault" occurs at the compilation of cx8-i2c.c file. You
> >> can try on kvm or virtualbox this compilation.
> > Sounds like a gcc bug you should be notifying the gcc developers about.
> >
> > good luck!
> >
> > greg k-h
> 
> 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

Hoping this helps,
Willy

  reply	other threads:[~2023-01-01 10:05 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 [this message]
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
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=20230101100518.GA21587@1wt.eu \
    --to=w@1wt.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=lukasz@pm.kalamlacki.eu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox