From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.11-rc2
Date: Mon, 5 Aug 2024 09:00:01 -0700 [thread overview]
Message-ID: <378f3810-8b3f-416f-90ec-c81bb3f29123@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wh01xPAWUT_=J1TehFOu3SST12UTNuB=QQTeRw+1N4pDQ@mail.gmail.com>
On Sun, Aug 04, 2024 at 02:00:57PM -0700, Linus Torvalds wrote:
> So rc1 had a fair number of annoying small build or test failures on
> Guenter's test matrix, which never looks good. But most of them seemed
> to be of the "stupid and trivial" variety, which obviously doesn't
> instill confidence in the process, but also isn't exactly scary. When
> the microblaze tinyconfig doesn't build cleanly, it may not be a great
> look, but it's also probably not a showstopper for actual use.
>
> Hopefully we've gotten rid of the bulk of the silly noise here in rc2,
> and not added too much new noise, so that we can get on with the
> process of finding more meaningful issues.
>
Build results:
total: 158 pass: 158 fail: 0
Qemu test results:
total: 539 pass: 516 fail: 23
Failed tests:
microblaze:petalogix-s3adsp1800:initrd
microblaze:petalogix-s3adsp1800:rootfs
microblaze:petalogix-ml605:initrd
microblaze:petalogix-ml605:rootfs
microblazeel:petalogix-s3adsp1800:initrd
microblazeel:petalogix-s3adsp1800:rootfs
microblazeel:petalogix-ml605:initrd
microblazeel:petalogix-ml605:rootfs
mips64:malta:malta_defconfig:nocd:smp:net=e1000-82544gc:ide:ext2
ppc:mpc8544ds:mpc85xx_defconfig:net=e1000:initrd
ppc:mpc8544ds:mpc85xx_defconfig:scsi[53C895A]:net=ne2k_pci:btrfs
ppc:mpc8544ds:mpc85xx_defconfig:sata-sii3112:net=rtl8139:ext2
ppc:mpc8544ds:mpc85xx_defconfig:sdhci-mmc:net=usb-ohci:ext2
ppc:mpc8544ds:mpc85xx_smp_defconfig:net=e1000:initrd
ppc:mpc8544ds:mpc85xx_smp_defconfig:scsi[DC395]:net=i82550:ext2
ppc:mpc8544ds:mpc85xx_smp_defconfig:scsi[53C895A]:net=usb-ohci:btrfs
ppc:mpc8544ds:mpc85xx_smp_defconfig:sata-sii3112:net=ne2k_pci:ext2
ppc:ppce500:corenet32_smp_defconfig:e500:net=rtl8139:initrd
ppc:ppce500:corenet32_smp_defconfig:e500:net=virtio-net:nvme:btrfs
ppc:ppce500:corenet32_smp_defconfig:e500:net=eTSEC:sdhci-mmc:ext2
ppc:ppce500:corenet32_smp_defconfig:e500:net=e1000:mmc:cramfs
ppc:ppce500:corenet32_smp_defconfig:e500:net=tulip:scsi[53C895A]:ext2
ppc:ppce500:corenet32_smp_defconfig:e500:net=i82562:sata-sii3112:ext2
Unit test results:
pass: 332158 fail: 0
The microblaze test failures are triggered by commit 721f4a6526da
("mm/memblock: remove empty dummy entry"). The fix is at
https://lore.kernel.org/all/20240729053327.4091459-1-rppt@kernel.org/
and should hopefully be sent upstream in the near future.
The ppc failures bisect to commit 6b0e82791bd0 ("powerpc/e500: switch to 64
bits PGD on 85xx (32 bits)"). This commit is related to other hugepage
related patches and can not easily be reverted. I don't know the status.
Given the context (changing the pgd sixe) it may well be a qemu problem.
The mips64 test failure is a networking interface failure. It started
happening a week or two ago. The problem is spurious and thus difficult
to bisect.
There is also a spurious failure with parisc64 images, triggered by commit
c37927a203fa ("genirq: Set IRQF_COND_ONESHOT in request_irq()"). The same
problem is also seen in v6.10.3 where that patch was backported. This is a
heisenbug: Any debugging added to figure out what is going on makes it
disappear. I don't know if it is a race condition or a bug in qemu or
something else. I did not see this problem with v6.11-rc2 but with an
interim image (v6.11-rc1-272-g17712b7ea075).
Guenter
next prev parent reply other threads:[~2024-08-05 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 21:00 Linus Torvalds
2024-08-05 8:00 ` Build regressions/improvements in v6.11-rc2 Geert Uytterhoeven
2024-08-05 8:25 ` Geert Uytterhoeven
2024-08-05 16:00 ` Guenter Roeck [this message]
2024-08-06 4:21 ` Linux 6.11-rc2 Guenter Roeck
2024-08-06 5:13 ` [REGRESSION] QEMU malta MIPS64 network failure (was: Re: Linux 6.11-rc2) Jiaxun Yang
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=378f3810-8b3f-416f-90ec-c81bb3f29123@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®