All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Guenter Roeck <linux@roeck-us.net>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.11-rc1
Date: Tue, 30 Jul 2024 12:35:43 -0600	[thread overview]
Message-ID: <3f65bfad-bd04-4651-bbe3-e2b1925f1a13@kernel.dk> (raw)
In-Reply-To: <5963cdad-40be-4278-a84e-2a804334e77c@roeck-us.net>

On 7/30/24 12:22 PM, Guenter Roeck wrote:
> On 7/30/24 10:20, Jens Axboe wrote:
>> On 7/30/24 11:04 AM, Guenter Roeck wrote:
>>> On Mon, Jul 29, 2024 at 08:29:20AM -0700, Guenter Roeck wrote:
>>>> On Sun, Jul 28, 2024 at 02:40:01PM -0700, Linus Torvalds wrote:
>>>>> The merge window felt pretty normal, and the stats all look pretty
>>>>> normal too. I was expecting things to be quieter because of summer
>>>>> vacations, but that (still) doesn't actually seem to have been the
>>>>> case.
>>>>>
>>>>> There's 12k+ regular commits (and another 850 merge commits), so as
>>>>> always the summary of this all is just my merge log. The diffstats are
>>>>> also (once again) dominated by some big hardware descriptions (another
>>>>> AMD GPU register dump accounts for ~45% of the lines in the diff, and
>>>>> some more perf event JSON descriptor files account for another 5%).
>>>>>
>>>>> But if you ignore those HW dumps, the diff too looks perfectly
>>>>> regular: drivers account for a bit over half (even when not counting
>>>>> the AMD register description noise). The rest is roughly one third
>>>>> architecture updates (lots of it is dts files, so I guess I could have
>>>>> lumped that in with "more hw descriptor tables"), one third tooling
>>>>> and documentation, and one third "core kernel" (filesystems,
>>>>> networking, VM and kernel). Very roughly.
>>>>>
>>>>> If you want more details, you should get the git tree, and then narrow
>>>>> things down based on interests.
>>>>>
>>>>
>>>> Build results:
>>>>     total: 158 pass: 139 fail: 19
>>>> Failed builds:
>>> ...
>>>>     i386:q35:pentium3:defconfig:pae:nosmp:net=ne2k_pci:initrd
>>>
>>> This failure bisects to commit 0256994887d7 ("Merge tag
>>> 'for-6.11/block-post-20240722' of git://git.kernel.dk/linux"). I have no
>>> idea why that would be the case, but it is easy to reproduce. Maybe it is
>>> coincidental. Either case, copying Jens in case he has an idea.
>>
>> I can take a look, but please post some details on what is actually
>> being run here so I can attempt to reproduce it. I looked at your
>> initial email too, and there's a link in there to:
>>
>> https://kerneltests.org/builders
>>
>> but I'm still not sure what's being run.
>>
> 
> Please see http://server.roeck-us.net/qemu/x86-nosmp/

Works fine for me on current master, boots and run self tests and
then shuts down. Tried it 5 times now.

axboe@r7625 ~/g/linux-vm (master)> qemu-system-i386 --version
QEMU emulator version 8.2.4 (Debian 1:8.2.4+ds-1)
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers

Then tried 6.11-rc1 10 times in a loop, and also didn't see any failures.

I then switched to using gcc-11 as that seems to be what you are using,
and them it does indeed bomb during boot. Funky. I'll check the post
branch and see if it's anything from there.

-- 
Jens Axboe



  reply	other threads:[~2024-07-30 18:35 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 21:40 Linux 6.11-rc1 Linus Torvalds
2024-07-29  9:28 ` Build regressions/improvements in v6.11-rc1 Geert Uytterhoeven
2024-07-29  9:35   ` Geert Uytterhoeven
2024-07-29  9:35     ` Geert Uytterhoeven
2024-07-29  9:54     ` Arnd Bergmann
2024-07-29  9:54       ` Arnd Bergmann
2024-07-29 10:07       ` Geert Uytterhoeven
2024-07-29 10:07         ` Geert Uytterhoeven
2024-07-29 15:29 ` Linux 6.11-rc1 Guenter Roeck
2024-07-29 19:23   ` Linus Torvalds
2024-07-29 19:50     ` Linus Torvalds
2024-07-29 21:34       ` Arnd Bergmann
2024-07-29 23:47         ` Linus Torvalds
2024-07-30 15:47           ` Arnd Bergmann
2024-07-30  7:54     ` Peter Zijlstra
2024-07-31 15:45     ` Guenter Roeck
2024-07-30 17:04   ` Guenter Roeck
2024-07-30 17:20     ` Jens Axboe
2024-07-30 18:22       ` Guenter Roeck
2024-07-30 18:35         ` Jens Axboe [this message]
2024-07-30 18:54           ` Jens Axboe
2024-07-30 18:53     ` Linus Torvalds
2024-07-30 19:22       ` Peter Zijlstra
2024-07-30 19:31         ` Jens Axboe
2024-07-30 19:34           ` Jens Axboe
2024-07-30 19:38           ` Peter Zijlstra
2024-07-30 19:41             ` Linus Torvalds
2024-07-30 20:04             ` Guenter Roeck
2024-07-30 20:09               ` Peter Zijlstra
2024-07-30 21:12                 ` Peter Zijlstra
2024-07-30 23:29                 ` Guenter Roeck
2024-07-30 23:54                   ` Linus Torvalds
2024-07-31  8:21                     ` Borislav Petkov
2024-07-31  9:11                       ` Peter Zijlstra
2024-07-31 10:02                         ` Borislav Petkov
2024-07-31 14:37                       ` Guenter Roeck
2024-07-31 13:24                     ` Jens Axboe
2024-07-30 20:13               ` Linus Torvalds
2024-07-30 20:24             ` Guenter Roeck
2024-07-31 12:20               ` Peter Zijlstra
2024-07-31 13:03                 ` Thomas Gleixner
2024-07-31 15:55                   ` Peter Zijlstra
2024-07-31 16:17                     ` Linus Torvalds
2024-07-31 16:31                       ` Peter Zijlstra
2024-07-31 16:50                         ` Guenter Roeck
2024-07-31 16:51                         ` Peter Zijlstra
2024-07-31 17:26                           ` Thomas Gleixner
2024-07-31 21:20                             ` Peter Zijlstra
2024-07-31 21:23                               ` Linus Torvalds
2024-07-31 21:26                                 ` Peter Zijlstra
2024-07-31 21:41                                   ` Linus Torvalds
2024-07-31 21:47                                     ` Thomas Gleixner
2024-07-31 22:22                               ` Guenter Roeck
2024-08-01  8:54                                 ` Peter Zijlstra
2024-08-01 10:55                         ` [tip: x86/urgent] x86/mm: Fix pti_clone_pgtable() alignment assumption tip-bot2 for Peter Zijlstra
2024-08-01 13:03                         ` tip-bot2 for Peter Zijlstra
2024-07-31 16:49                       ` Linux 6.11-rc1 Guenter Roeck
2024-07-31 17:19                         ` Thomas Gleixner
2024-07-31 10:33       ` Peter Zijlstra
2024-07-31 14:15         ` Peter Zijlstra
2024-08-02 17:35   ` Linus Walleij
2024-08-02 19:40     ` Guenter Roeck

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=3f65bfad-bd04-4651-bbe3-e2b1925f1a13@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=torvalds@linux-foundation.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.