Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #94336 > unrolled thread

Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2

Started byBernhard Schmidt <berni@debian.org>
First post2026-10-04 00:10 +0200
Last post2026-10-06 09:20 +0200
Articles 7 — 3 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2 Bernhard Schmidt <berni@debian.org> - 2026-10-04 00:10 +0200
    Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2 Ben Hutchings <ben@decadent.org.uk> - 2026-10-04 13:30 +0200
      Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2 Bernhard Schmidt <berni@debian.org> - 2026-10-04 22:50 +0200
        Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2 Salvatore Bonaccorso <carnil@debian.org> - 2026-10-05 07:50 +0200
          Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2 Bernhard Schmidt <berni@debian.org> - 2026-10-05 13:10 +0200
            Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2 Salvatore Bonaccorso <carnil@debian.org> - 2026-10-05 13:20 +0200
              Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2 Salvatore Bonaccorso <carnil@debian.org> - 2026-10-06 09:20 +0200

#94336 — Bug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2

FromBernhard Schmidt <berni@debian.org>
Date2026-10-04 00:10 +0200
SubjectBug#1149564: linux-image-6.12.111+deb13-amd64: 6.12.111-1 regression crash bnxt_en: DMAR: DRHD: handling fault status reg 2
Message-ID<NKg5z-3nF5-5@gated-at.bofh.it>
On 03/10/26 04:34 PM, Salvatore Bonaccorso wrote:
 > > 
> > > v6.18.53: c8050386a2209b2a474c1eb4bd1574dc19129bfb bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()
> > > v7.2.7: 37e08dc821a57fe0592c917486b638caa888b46d bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()
> > > v7.3-rc3: b814dfbfeb0a68c9a52073f2caa05a2d5247a329 bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()
> > > 
> > > -> this one was not backported to 6.11.y, but looks fine as the code
> > > was only introduced in v6.13-rc2 (and backported to v6.12.20).
> > 
> > And now this still got backported to the v6.12.112 released today.
> > 
> > > v6.18.53: 8ade95619cbfd1fc57f0f1a9a5ebdca2345a8d27 bnxt_en: Don't free the live ring's TPA state on queue restart failure
> > > v7.2.7: 0596a7caa6fc283e142716739099c038d8714082 bnxt_en: Don't free the live ring's TPA state on queue restart failure
> > > v7.3-rc3: 5ce7f36c334d723954855ac769ede2fe0e8f89c8 bnxt_en: Don't free the live ring's TPA state on queue restart failure
> > > 
> > > Same as above.
> > 
> > And this as well
> > 
> > Aurelien, Bernhard, while I'm working on importing and rebasing
> > 6.12.112 for the next update in trixie, would it be possible you pick
> > those two commits on top to see if they fix the problem? (It might
> > though be possible they do not apply clieanly without more depending
> > fixes which were included in 6.12.112).
> > 
> > If that will not work I can provide you preliminary builds somehwere
> > for 6.12.112 instread.
> 
> Unofficial builds for the unsigned images will appear trough:
> https://debusine.debian.net/debian/developers/work-request/1411088/
> (that is a version without debian/changelog cleanup et al).

Took about an hour, but still crashed :-(

Oct 03 22:43:51 nm3 kernel: Linux version 6.12+unreleased-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian 6.12.112->
Oct 03 22:43:51 nm3 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.12+unreleased-amd64 root=/dev/mapper/sysvg-root ro quiet
[...]
Oct 03 23:47:24 nm3 kernel: DMAR: DRHD: handling fault status reg 2
Oct 03 23:47:24 nm3 kernel: DMAR: [DMA Read NO_PASID] Request device [19:00.0] fault addr 0xde00b000 [fault reason 0x06] PTE Read access is not set
Oct 03 23:47:24 nm3 kernel: bnxt_en 0000:19:00.1 eno2np1: Fatal firmware reset event, data1: 0x201, data2: 0xda27, min wait 1300 ms, max wait 4200 ms
Oct 03 23:47:24 nm3 systemd-networkd[1237]: eno2np1: Lost carrier
Oct 03 23:47:24 nm3 kernel: bond0: (slave eno2np1): link status definitely down, disabling slave
Oct 03 23:47:25 nm3 kernel: bnxt_en 0000:19:00.0 eno1np0: Abandoning msg {0x23 0x2c5b} len: 0 due to firmware status: 0x2000001
Oct 03 23:47:25 nm3 kernel: bnxt_en 0000:19:00.0 eno1np0: Abandoning msg {0xb4 0x2c5c} len: 0 due to firmware status: 0x2000001

I still don't get why my bisection attempt failed so badly,
6.12.111-stable (the one compiled from the kernel.org stable tree
following your bisection instructions) has been running for 36+ hours
before I voluntarily rebooted into your 6.12.112 kernel.

Bernhard

[toc] | [next] | [standalone]

#94344

FromBen Hutchings <ben@decadent.org.uk>
Date2026-10-04 13:30 +0200
Message-ID<NKszL-3uls-5@gated-at.bofh.it>
In reply to#94336

[Multipart message — attachments visible in raw view] — view raw

On Sat, 2026-10-03 at 23:59 +0200, Bernhard Schmidt wrote:
[...]
> I still don't get why my bisection attempt failed so badly,
> 6.12.111-stable (the one compiled from the kernel.org stable tree
> following your bisection instructions) has been running for 36+ hours
> before I voluntarily rebooted into your 6.12.112 kernel.

I believe this is because Debian's config sets a default mode for the
Intel IOMMU driver which is not present upstream.

When building from the upstream source, make sure you have
CONFIG_INTEL_IOMMU_DEFAULT_ON=y in the .config file, or add
"intel_iommu=on" to the kernel boot parameters.

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
                                                           - Bill Gates

[toc] | [prev] | [next] | [standalone]

#94347

FromBernhard Schmidt <berni@debian.org>
Date2026-10-04 22:50 +0200
Message-ID<NKBjH-3z8D-5@gated-at.bofh.it>
In reply to#94344
On 04/10/26 02:16 PM, Bernhard Schmidt wrote:

Hi,

> What I don't get though, I followed Salvatore's instructions from a stock
> Debian kernel which say
> 
>     cp /boot/config-$(uname -r) .config
>     yes '' | make localmodconfig
>     make savedefconfig
>     mv defconfig arch/x86/configs/my_defconfig
> 
> so all settings should be the same. But as I wrote before, the kernel sizes
> are wildly different, so possibly something went wrong here.
> 
> -rw-r--r--  1 root root   283542 Oct  3 15:02 config-6.12+unreleased-amd64
> -rw-r--r--  1 root root   171116 Oct  2 01:00 config-6.12.107
> -rw-r--r--  1 root root   283337 Aug 29 06:19 config-6.12.107+deb13-amd64
> -rw-r--r--  1 root root   171310 Oct  2 01:05 config-6.12.111
> -rw-r--r--  1 root root   283542 Sep 28 14:18 config-6.12.111+deb13-amd64
> 
> root@nm3:/boot# grep CONFIG_INTEL_IOMMU_DEFAULT_ON config-6.12*
> config-6.12+unreleased-amd64:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> config-6.12+unreleased-amd64:CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y
> config-6.12.107:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> config-6.12.107+deb13-amd64:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> config-6.12.107+deb13-amd64:CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y
> config-6.12.111:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> config-6.12.111+deb13-amd64:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> config-6.12.111+deb13-amd64:CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y
> 
> That setting is not set for both my kernels, the trixie kernels and the one
> Salvatore sent out yesterday. So maybe it's enabled somewhere else in Debian
> (a kernel patch)?
> 
> Anyway, I booted "my" .111 with intel_iommu=on now and it shows the "Adding
> to iommu group" messages, so it should crash now.

Nope :-(

That kernel (built straight from the linux-stable tree) does not crash,
even with IOMMU enabled. At least for the last 8 hours.

So although I copied over the config as instructed the 6.12.111-stable
tree behaves differently, has a wildly different size of the .config and
the binaries, and does not crash.

Bernhard

[toc] | [prev] | [next] | [standalone]

#94352

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-10-05 07:50 +0200
Message-ID<NKJKh-3DOG-1@gated-at.bofh.it>
In reply to#94347
Hi all,

On Sun, Oct 04, 2026 at 10:47:17PM +0200, Bernhard Schmidt wrote:
> On 04/10/26 02:16 PM, Bernhard Schmidt wrote:
> 
> Hi,
> 
> > What I don't get though, I followed Salvatore's instructions from a stock
> > Debian kernel which say
> > 
> >     cp /boot/config-$(uname -r) .config
> >     yes '' | make localmodconfig
> >     make savedefconfig
> >     mv defconfig arch/x86/configs/my_defconfig
> > 
> > so all settings should be the same. But as I wrote before, the kernel sizes
> > are wildly different, so possibly something went wrong here.
> > 
> > -rw-r--r--  1 root root   283542 Oct  3 15:02 config-6.12+unreleased-amd64
> > -rw-r--r--  1 root root   171116 Oct  2 01:00 config-6.12.107
> > -rw-r--r--  1 root root   283337 Aug 29 06:19 config-6.12.107+deb13-amd64
> > -rw-r--r--  1 root root   171310 Oct  2 01:05 config-6.12.111
> > -rw-r--r--  1 root root   283542 Sep 28 14:18 config-6.12.111+deb13-amd64
> > 
> > root@nm3:/boot# grep CONFIG_INTEL_IOMMU_DEFAULT_ON config-6.12*
> > config-6.12+unreleased-amd64:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> > config-6.12+unreleased-amd64:CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y
> > config-6.12.107:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> > config-6.12.107+deb13-amd64:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> > config-6.12.107+deb13-amd64:CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y
> > config-6.12.111:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> > config-6.12.111+deb13-amd64:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> > config-6.12.111+deb13-amd64:CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y
> > 
> > That setting is not set for both my kernels, the trixie kernels and the one
> > Salvatore sent out yesterday. So maybe it's enabled somewhere else in Debian
> > (a kernel patch)?
> > 
> > Anyway, I booted "my" .111 with intel_iommu=on now and it shows the "Adding
> > to iommu group" messages, so it should crash now.
> 
> Nope :-(
> 
> That kernel (built straight from the linux-stable tree) does not crash,
> even with IOMMU enabled. At least for the last 8 hours.
> 
> So although I copied over the config as instructed the 6.12.111-stable
> tree behaves differently, has a wildly different size of the .config and
> the binaries, and does not crash.

So this mgiht now be the same as in meanwhile reported upstream,
https://lore.kernel.org/stable/20261004122616.56714cbd@nargothrond/

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#94356

FromBernhard Schmidt <berni@debian.org>
Date2026-10-05 13:10 +0200
Message-ID<NKOJY-3Gsi-17@gated-at.bofh.it>
In reply to#94352
On 05/10/26 07:47 AM, Salvatore Bonaccorso wrote:
 
> So this mgiht now be the same as in meanwhile reported upstream,
> https://lore.kernel.org/stable/20261004122616.56714cbd@nargothrond/

I think that looks promising. 

While I still cannot reproduce that with the upstream stable tree, I can
confirm that

- Debian 6.12.111-1 does not crash when there is no VLAN configured
- Debian 6.12.111-1 + debian/bin/test-patches with the patch from 
  https://lore.kernel.org/stable/ef6eb827-71a6-40a6-a4b7-8e514ab595d3@kernel.org/
  appears to be stable as well.

It has already been submitted to netdev and to stable

https://lore.kernel.org/netdev/20261005023812.130639-1-edumazet@kernel.org/

Bernhard

[toc] | [prev] | [next] | [standalone]

#94358

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-10-05 13:20 +0200
Message-ID<NKOTE-3Gw0-3@gated-at.bofh.it>
In reply to#94356
Hi,

On Mon, Oct 05, 2026 at 01:00:22PM +0200, Bernhard Schmidt wrote:
> On 05/10/26 07:47 AM, Salvatore Bonaccorso wrote:
>  
> > So this mgiht now be the same as in meanwhile reported upstream,
> > https://lore.kernel.org/stable/20261004122616.56714cbd@nargothrond/
> 
> I think that looks promising. 
> 
> While I still cannot reproduce that with the upstream stable tree, I can
> confirm that
> 
> - Debian 6.12.111-1 does not crash when there is no VLAN configured
> - Debian 6.12.111-1 + debian/bin/test-patches with the patch from 
>   https://lore.kernel.org/stable/ef6eb827-71a6-40a6-a4b7-8e514ab595d3@kernel.org/
>   appears to be stable as well.
> 
> It has already been submitted to netdev and to stable
> 
> https://lore.kernel.org/netdev/20261005023812.130639-1-edumazet@kernel.org/

Thanks for having done that already; was going in fact to suggest
exactly that to pick the change and test it with bin/test-patches.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#94369

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-10-06 09:20 +0200
Message-ID<NL7CV-3Qqf-9@gated-at.bofh.it>
In reply to#94358
Hi Bernhard, Aurelien, Rudolph,

On Mon, Oct 05, 2026 at 01:08:40PM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Mon, Oct 05, 2026 at 01:00:22PM +0200, Bernhard Schmidt wrote:
> > On 05/10/26 07:47 AM, Salvatore Bonaccorso wrote:
> >  
> > > So this mgiht now be the same as in meanwhile reported upstream,
> > > https://lore.kernel.org/stable/20261004122616.56714cbd@nargothrond/
> > 
> > I think that looks promising. 
> > 
> > While I still cannot reproduce that with the upstream stable tree, I can
> > confirm that
> > 
> > - Debian 6.12.111-1 does not crash when there is no VLAN configured
> > - Debian 6.12.111-1 + debian/bin/test-patches with the patch from 
> >   https://lore.kernel.org/stable/ef6eb827-71a6-40a6-a4b7-8e514ab595d3@kernel.org/
> >   appears to be stable as well.
> > 
> > It has already been submitted to netdev and to stable
> > 
> > https://lore.kernel.org/netdev/20261005023812.130639-1-edumazet@kernel.org/
> 
> Thanks for having done that already; was going in fact to suggest
> exactly that to pick the change and test it with bin/test-patches.

v2 posted for testinng:
https://lore.kernel.org/netdev/20261006042153.199444-1-edumazet@kernel.org/

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web