Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Willy Tarreau <w@1wt.eu>, 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: Mon, 2 Jan 2023 10:35:47 +0700	[thread overview]
Message-ID: <Y7JRE4yO6ZOj0HyH@debian.me> (raw)
In-Reply-To: <20230101100518.GA21587@1wt.eu>

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]

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.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-01-02  3:35 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 [this message]
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=Y7JRE4yO6ZOj0HyH@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lukasz@pm.kalamlacki.eu \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /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