Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #90742 > unrolled thread
| Started by | Bastian Blank <waldi@debian.org> |
|---|---|
| First post | 2026-01-07 20:50 +0100 |
| Last post | 2026-01-19 22:00 +0100 |
| Articles | 3 — 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.
Bug#1123591: reportbug: Kernel 6.17.11 "ixgbe"-driver broken (OEM Intel X540-AT2 card) Bastian Blank <waldi@debian.org> - 2026-01-07 20:50 +0100
Bug#1123591: reportbug: Kernel 6.17.11 "ixgbe"-driver broken (OEM Intel X540-AT2 card) Radostin Dimitrov <radostin.m.dimitrov@gmail.com> - 2026-01-08 11:10 +0100
Bug#1123591: reportbug: Kernel 6.17.11 "ixgbe"-driver broken (OEM Intel X540-AT2 card) Uwe Kleine-König <ukleinek@debian.org> - 2026-01-19 22:00 +0100
| From | Bastian Blank <waldi@debian.org> |
|---|---|
| Date | 2026-01-07 20:50 +0100 |
| Subject | Bug#1123591: reportbug: Kernel 6.17.11 "ixgbe"-driver broken (OEM Intel X540-AT2 card) |
| Message-ID | <MaHHz-8Pm2-1@gated-at.bofh.it> |
On Thu, Dec 18, 2025 at 07:35:44PM +0200, Radostin Dimitrov wrote:
> >> ipv6.disable=1 is unsupported.
I still see this,
> >> > ** Tainted: OE (12288)
> >> > * externally-built ("out-of-tree") module was loaded
> >> > * unsigned module was loaded
> >> You have proprietary modules loaded. Does it also fail without?
And nvidia loaded.
Anyway, please update the firmware.
https://de.msi.com/Motherboard/MAG-X870E-TOMAHAWK-WIFI/support shows
2.A91, while your system reports 1.A61.
You've run into broken firmware, I would say. The whole network card
does not get any memory for the queues assigned:
> [ 0.265921] pci 0000:04:04.0: bridge window [mem size 0x00900000 64bit pref]: can't assign; no space
> [ 0.265922] pci 0000:04:04.0: bridge window [mem size 0x00900000 64bit pref]: failed to assign
> [ 0.265923] pci 0000:04:04.0: bridge window [mem size 0x00900000 64bit pref]: can't assign; no space
> [ 0.265924] pci 0000:04:04.0: bridge window [mem size 0x00900000 64bit pref]: failed to assign
> [ 0.265926] pci 0000:04:00.0: PCI bridge to [bus 05]
> [ 0.265936] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]: can't assign; no space
> [ 0.265937] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]: failed to assign
> [ 0.265938] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]: can't assign; no space
> [ 0.265939] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]: failed to assign
> [ 0.265940] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]: can't assign; no space
> [ 0.265941] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]: failed to assign
> [ 0.265942] pci 0000:06:00.0: VF BAR 0 [mem size 0x00100000 64bit pref]: can't assign; no space
> [ 0.265943] pci 0000:06:00.0: VF BAR 0 [mem size 0x00100000 64bit pref]: failed to assign
> [ 0.265944] pci 0000:06:00.0: VF BAR 3 [mem size 0x00100000 64bit pref]: can't assign; no space
> [ 0.265945] pci 0000:06:00.0: VF BAR 3 [mem size 0x00100000 64bit pref]: failed to assign
> [ 0.265946] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]: can't assign; no space
> [ 0.265947] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]: failed to assign
> [ 0.265948] pci 0000:06:00.1: VF BAR 0 [mem size 0x00100000 64bit pref]: can't assign; no space
> [ 0.265949] pci 0000:06:00.1: VF BAR 0 [mem size 0x00100000 64bit pref]: failed to assign
> [ 0.265950] pci 0000:06:00.1: VF BAR 3 [mem size 0x00100000 64bit pref]: can't assign; no space
> [ 0.265951] pci 0000:06:00.1: VF BAR 3 [mem size 0x00100000 64bit pref]: failed to assign
> [ 0.265952] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]: can't assign; no space
> [ 0.265953] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]: failed to assign
> [ 0.265954] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]: can't assign; no space
> [ 0.265955] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]: failed to assign
> [ 0.265956] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]: can't assign; no space
> [ 0.265957] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]: failed to assign
> [ 0.265958] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]: can't assign; no space
> [ 0.265959] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]: failed to assign
Bastian
--
The joys of love made her human and the agonies of love destroyed her.
-- Spock, "Requiem for Methuselah", stardate 5842.8
[toc] | [next] | [standalone]
| From | Radostin Dimitrov <radostin.m.dimitrov@gmail.com> |
|---|---|
| Date | 2026-01-08 11:10 +0100 |
| Message-ID | <MaV7P-8ZjE-1@gated-at.bofh.it> |
| In reply to | #90742 |
[Multipart message — attachments visible in raw view] — view raw
Hello, Bastian, Guys,
I followed your instructions to the letter and did the test without the
nvidia driver (results attached, as requested).
Same unpredictable behaviour - sometimes the NIC would work for like 5
mins, other times for 20 mins (before detaching itself with "Adapter
firmware error").
It works on Windows, hence I isolated this from being a hardware fault. As
mentioned, it's been working for several years without issues.
On the UEFI topic - I am monitoring MSI's mobo page for upcoming updates.
But you're wrong about the model - I am on "Edge Ti WiFi", not "Tomahawk",
if that would make a difference, of course. Let me know if you need further
details and if I need to do other tests.
Thanks & Cheers !
On Wed, Jan 7, 2026 at 9:47 PM Bastian Blank <waldi@debian.org> wrote:
> On Thu, Dec 18, 2025 at 07:35:44PM +0200, Radostin Dimitrov wrote:
> > >> ipv6.disable=1 is unsupported.
>
> I still see this,
>
> > >> > ** Tainted: OE (12288)
> > >> > * externally-built ("out-of-tree") module was loaded
> > >> > * unsigned module was loaded
> > >> You have proprietary modules loaded. Does it also fail without?
>
> And nvidia loaded.
>
> Anyway, please update the firmware.
> https://de.msi.com/Motherboard/MAG-X870E-TOMAHAWK-WIFI/support shows
> 2.A91, while your system reports 1.A61.
>
> You've run into broken firmware, I would say. The whole network card
> does not get any memory for the queues assigned:
>
> > [ 0.265921] pci 0000:04:04.0: bridge window [mem size 0x00900000
> 64bit pref]: can't assign; no space
> > [ 0.265922] pci 0000:04:04.0: bridge window [mem size 0x00900000
> 64bit pref]: failed to assign
> > [ 0.265923] pci 0000:04:04.0: bridge window [mem size 0x00900000
> 64bit pref]: can't assign; no space
> > [ 0.265924] pci 0000:04:04.0: bridge window [mem size 0x00900000
> 64bit pref]: failed to assign
> > [ 0.265926] pci 0000:04:00.0: PCI bridge to [bus 05]
> > [ 0.265936] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]:
> can't assign; no space
> > [ 0.265937] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]:
> failed to assign
> > [ 0.265938] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]:
> can't assign; no space
> > [ 0.265939] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]:
> failed to assign
> > [ 0.265940] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]:
> can't assign; no space
> > [ 0.265941] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]:
> failed to assign
> > [ 0.265942] pci 0000:06:00.0: VF BAR 0 [mem size 0x00100000 64bit
> pref]: can't assign; no space
> > [ 0.265943] pci 0000:06:00.0: VF BAR 0 [mem size 0x00100000 64bit
> pref]: failed to assign
> > [ 0.265944] pci 0000:06:00.0: VF BAR 3 [mem size 0x00100000 64bit
> pref]: can't assign; no space
> > [ 0.265945] pci 0000:06:00.0: VF BAR 3 [mem size 0x00100000 64bit
> pref]: failed to assign
> > [ 0.265946] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]:
> can't assign; no space
> > [ 0.265947] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]:
> failed to assign
> > [ 0.265948] pci 0000:06:00.1: VF BAR 0 [mem size 0x00100000 64bit
> pref]: can't assign; no space
> > [ 0.265949] pci 0000:06:00.1: VF BAR 0 [mem size 0x00100000 64bit
> pref]: failed to assign
> > [ 0.265950] pci 0000:06:00.1: VF BAR 3 [mem size 0x00100000 64bit
> pref]: can't assign; no space
> > [ 0.265951] pci 0000:06:00.1: VF BAR 3 [mem size 0x00100000 64bit
> pref]: failed to assign
> > [ 0.265952] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]:
> can't assign; no space
> > [ 0.265953] pci 0000:06:00.0: BAR 0 [mem size 0x00200000 64bit pref]:
> failed to assign
> > [ 0.265954] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]:
> can't assign; no space
> > [ 0.265955] pci 0000:06:00.1: BAR 0 [mem size 0x00200000 64bit pref]:
> failed to assign
> > [ 0.265956] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]:
> can't assign; no space
> > [ 0.265957] pci 0000:06:00.0: BAR 4 [mem size 0x00004000 64bit pref]:
> failed to assign
> > [ 0.265958] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]:
> can't assign; no space
> > [ 0.265959] pci 0000:06:00.1: BAR 4 [mem size 0x00004000 64bit pref]:
> failed to assign
>
> Bastian
>
> --
> The joys of love made her human and the agonies of love destroyed her.
> -- Spock, "Requiem for Methuselah", stardate 5842.8
>
[toc] | [prev] | [next] | [standalone]
| From | Uwe Kleine-König <ukleinek@debian.org> |
|---|---|
| Date | 2026-01-19 22:00 +0100 |
| Message-ID | <Mf4vT-bMzu-1@gated-at.bofh.it> |
| In reply to | #90747 |
[Multipart message — attachments visible in raw view] — view raw
Hello Radostin, On Thu, Jan 08, 2026 at 12:03:14PM +0200, Radostin Dimitrov wrote: > I followed your instructions to the letter and did the test without the > nvidia driver (results attached, as requested). This mail doesn't has an attachment and the previously attached kernel log had the nvidia module loaded. So there is a misunderstanding somewhere (or you just forgot to attach a recent kernel log?). > Same unpredictable behaviour - sometimes the NIC would work for like 5 > mins, other times for 20 mins (before detaching itself with "Adapter > firmware error"). > It works on Windows, hence I isolated this from being a hardware fault. As > mentioned, it's been working for several years without issues. Can you install older kernels and check if this gives you a working setup again? Please tell if you need instructions to do so. It would be interesting to know the newest kernel that still worked and/or the oldest broken kernel. Best regards Uwe
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web