From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gilberto.nunes32@gmail.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by lists.proxmox.com (Postfix) with ESMTPS id 3736BBC7A3
for <pve-user@lists.proxmox.com>; Thu, 28 Mar 2024 16:58:21 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 1666510C4E
for <pve-user@lists.proxmox.com>; Thu, 28 Mar 2024 16:58:21 +0100 (CET)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com
[IPv6:2a00:1450:4864:20::236])
(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
by firstgate.proxmox.com (Proxmox) with ESMTPS
for <pve-user@lists.proxmox.com>; Thu, 28 Mar 2024 16:58:19 +0100 (CET)
Received: by mail-lj1-x236.google.com with SMTP id
38308e7fff4ca-2d4515ec3aaso10191281fa.1
for <pve-user@lists.proxmox.com>; Thu, 28 Mar 2024 08:58:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1711641492; x=1712246292; darn=lists.proxmox.com;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:from:to:cc:subject:date:message-id:reply-to;
bh=nLKPsArJG0bRueGd7MwAbat25XQCgNISnzQr9NDYhzk=;
b=JupggbGz/fRWaWY1y14/PNA0Otp5ohyTjePHoZZAOm8cZLGacwJoOSPbqBgRw/h7UA
sLIwxF2wkczT6cOFplRtt/2YuTNcrKKCCe4WuCn0DixPxfiP5M+jaRTCudGs1s5a5/cH
zNn+kSb/8p8vMtUtk5Ebnf7bBvJvMudXY5DcSnryxdctAjtFvQ38WbtiMp5oAC1Z/7Vb
Tq4dRBS7+ZiABOdDM2m6sYK6WoETE1gIpXlsDtzDKYW0Lt9BC+8WysP0lyj6mOT0tJRN
VgHbIH4q4yW3psflRMxu2Kp6ftMEZ7/Lo2K+YO/JDY23/+jZnkdOoCrljWNubGmSNdN+
1Fqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1711641492; x=1712246292;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=nLKPsArJG0bRueGd7MwAbat25XQCgNISnzQr9NDYhzk=;
b=uvIw+uiHNnqHzqAuine7FeJyBLpgVUUrC0cWL/hlGV89mbbXTtRxn9YVTxrNAbvAJn
EPdUyrUmM2uHdBLgeHnVR4GuTKJpQq/zC2X5jkPGAcqWrgDFULCJ354Bav/0mXg+0dG5
Tm9nb0F7CCZ223hRm9k7ZG71Pk243tPEQ8RNajPY4hNwq56AxD09quGJxnF+dQLHPc7/
Sw73cT4f+TwH/Rfpk2Vwd2/y3QXe2SjIqKCNC+j4GFgi9ObgtbwamBtZCRhkdpQpacRA
gLW7QMhxrdttax/tMIcfMx31sAstt6c/povETfVz6VpBtWPf/grqwWUXA+19orJYrN6F
CK3Q==
X-Gm-Message-State: AOJu0YwXBtBqagzp24xRWG6f0tSbUgvFYHxReo5/wQLuhELIC6YhQNY5
U1ClRpwygNa5oQxytRmRj3AXQR10x4WMExaTqtch0z+4Gn28vw/s+eyh0vfyvIgUDqswsh2K+Ap
aYGurkZkPqLnRoOnTqC2AFeEPwM7RIoAk27/JaA==
X-Google-Smtp-Source: AGHT+IETKcLnAG4v3l0Xw6dlfbzgGrUyC+cMUyi7zzmOBNO504gtUo+FkbarlUNBpkjhT2BLyr5PXXwt/PhtssceX7w=
X-Received: by 2002:a2e:99d8:0:b0:2d4:8411:8b41 with SMTP id
l24-20020a2e99d8000000b002d484118b41mr903559ljj.17.1711641491664; Thu, 28 Mar
2024 08:58:11 -0700 (PDT)
MIME-Version: 1.0
References: <D8D305A2-D2B7-4A5D-821C-65DE75621457@kmi.com>
<93280CB8-7582-4456-9101-D594CE2C86A2@kmi.com>
<mailman.755.1711637904.434.pve-user@lists.proxmox.com>
<CAOKSTBvmuqr7R8KntqREdoP5f5hE2U+n-m0WTsXsN=wNPWkaKw@mail.gmail.com>
<mailman.761.1711641292.434.pve-user@lists.proxmox.com>
In-Reply-To: <mailman.761.1711641292.434.pve-user@lists.proxmox.com>
From: Gilberto Ferreira <gilberto.nunes32@gmail.com>
Date: Thu, 28 Mar 2024 12:57:35 -0300
Message-ID: <CAOKSTBv8gpAeQd2LMniAdBeRKJFdMcVRB6qX1k309cu5EAE1QQ@mail.gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.042 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DKIM_SIGNED 0.1 Message has a DKIM or DK signature,
not necessarily valid
DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's
domain
DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from
domain DMARC_PASS -0.1 DMARC pass policy
FREEMAIL_ENVFROM_END_DIGIT 0.25 Envelope-from freemail username ends in digit
FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider
HTML_MESSAGE 0.001 HTML included in message
POISEN_SPAM_PILL_4 0.1 random spam to be learned in bayes
RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/,
no trust
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
Subject: Re: [PVE-User] 6.5.13-3-pve kernel panic on shutdown
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>,
<mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>,
<mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2024 15:58:21 -0000
https://medium.com/@nothanjack/dealing-with-apei-generic-hardware-error-sou=
rce-problems-in-linux-a8ee8a67c8c1
---
Gilberto Nunes Ferreira
(47) 99676-7530 - Whatsapp / Telegram
Em qui., 28 de mar. de 2024 =C3=A0s 12:54, Stefan Radman via pve-user <
pve-user@lists.proxmox.com> escreveu:
>
>
>
> ---------- Forwarded message ----------
> From: Stefan Radman <stefan.radman@me.com>
> To: Proxmox VE user list <pve-user@lists.proxmox.com>
> Cc:
> Bcc:
> Date: Thu, 28 Mar 2024 16:47:43 +0100
> Subject: Re: [PVE-User] 6.5.13-3-pve kernel panic on shutdown
> Hi Gilberto
>
> The server firmware is up to date.
>
> Stefan
>
> > On Mar 28, 2024, at 16:18, Gilberto Ferreira <gilberto.nunes32@gmail.co=
m>
> wrote:
> >
> > Try to update the server firmware.
> > ---
> > Gilberto Nunes Ferreira
> > (47) 99676-7530 - Whatsapp / Telegram
> >
> >
> >
> >
> >
> >
> > Em qui., 28 de mar. de 2024 =C3=A0s 11:58, Stefan Radman via pve-user <
> > pve-user@lists.proxmox.com <mailto:pve-user@lists.proxmox.com>>
> escreveu:
> >
> >>
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: Stefan Radman <stefan.radman@me.com <mailto:stefan.radman@me.com
> >>
> >> To: PVE User List <pve-user@pve.proxmox.com <mailto:
> pve-user@pve.proxmox.com>>
> >> Cc:
> >> Bcc:
> >> Date: Thu, 28 Mar 2024 15:50:02 +0100
> >> Subject: 6.5.13-3-pve kernel panic on shutdown
> >> I recently noticed that a Dell Poweredge R540 currently running Proxmo=
x
> VE
> >> 8.1.8 (kernel 6.5.13-3-pve) throws a kernel panic on shutdown.
> >>
> >> The kernel panic is triggered 3-4 seconds after the last network
> interface
> >> goes down (onboard BCM5720 LOM), while the system enters S5 (sleep)
> state.
> >>
> >> [84459.970212] bond0: (slave eno1): link status definitely down,
> disabling
> >> slave
> >> [84459.982170] bond0: (slave eno2): link status definitely down,
> disabling
> >> slave
> >> [84459.990037] tg3 0000:04:00.0 eno1: left promiscuous mode
> >> [84459.995822] tg3 0000:04:00.0 eno1: left allmulticast mode
> >> [84460.001615] bond0: now running without any active interface!
> >> [84460.018133] vmbr0: port 1(bond0) entered disabled state
> >> [84460.291379] ACPI: PM: Preparing to enter system sleep state S5
> >> [84463.685113] {1}[Hardware Error]: Hardware error from APEI Generic
> >> Hardware Error Source: 5
> >>
> >> This is reproducible on every reboot.
> >>
> >> R540 and BCM5720 are running the latest firmware available from the De=
ll
> >> support website.
> >>
> >> Link [2] below seem to suggest that my problem is related to a
> combination
> >> of ACPI S5, the tg3 driver and the BCM5720 on-board NIC.
> >>
> >> Has anyone else seen this lately (or ever) with Promox VE?
> >>
> >> Thank you
> >>
> >> Stefan
> >>
> >> [1] Use ACPI S5 for reboot #1904225: causes reboot crash on Dell T440
> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962730
> >>
> >> [2] [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" whi=
ch
> >> causes Bus Fatal Error when rebooting system with BCM5720 NIC
> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471
> >>
> >> [3] tg3: Disable tg3 device on system reboot to avoid triggering AER
> >>
> >>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit=
/?id=3D2ca1c94ce0b65a2ce7512b718f3d8a0fe6224bca
> >>
> >>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/d=
rivers/net/ethernet/broadcom/tg3.c?id=3D2ca1c94ce0b65a2ce7512b718f3d8a0fe62=
24bca#n18074
> >>
> >> [4] * [PATCH] tg3: Disable tg3 device on system reboot to avoid
> triggering
> >> AER
> >>
> >>
> https://lore.kernel.org/netdev/CAAd53p7PmEp+vWLz+fGdDntGQ2KqgL54fo86Bpy7o=
y9tKzXsAg@mail.gmail.com/T/
> >>
> >> [5] [v4,2/2] PM: ACPI: reboot: Reinstate S5 for reboot
> >>
> >>
> https://patches.linaro.org/project/linux-acpi/patch/20220916043319.119716=
-2-kai.heng.feng@canonical.com/
> >>
> >> [6] * [PATCH] tg3: add new module param to force device power down on
> >> reboot
> >>
> >>
> https://lore.kernel.org/lkml/d8ed4af1-5c83-4895-9fc3-9aea25724fd9@gmail.c=
om/T/
> >>
> >>
> >> [84458.600189] systemd-shutdown[1]: Syncing filesystems and block
> devices.
> >> [84458.607141] systemd-shutdown[1]: Rebooting.
> >> [84458.612283] spi-nor spi0.0: Software reset failed: -524
> >> [84459.777370] megaraid_sas 0000:17:00.0: megasas_disable_intr_fusion =
is
> >> called outbound_intr_mask:0x40000009
> >> [84459.970212] bond0: (slave eno1): link status definitely down,
> disabling
> >> slave
> >> [84459.982170] bond0: (slave eno2): link status definitely down,
> disabling
> >> slave
> >> [84459.990037] tg3 0000:04:00.0 eno1: left promiscuous mode
> >> [84459.995822] tg3 0000:04:00.0 eno1: left allmulticast mode
> >> [84460.001615] bond0: now running without any active interface!
> >> [84460.018133] vmbr0: port 1(bond0) entered disabled state
> >> [84460.291379] ACPI: PM: Preparing to enter system sleep state S5
> >> [84463.685113] {1}[Hardware Error]: Hardware error from APEI Generic
> >> Hardware Error Source: 5
> >> [84463.685116] {1}[Hardware Error]: event severity: fatal
> >> [84463.685117] {1}[Hardware Error]: Error 0, type: fatal
> >> [84463.685119] {1}[Hardware Error]: section_type: PCIe error
> >> [84463.685120] {1}[Hardware Error]: port_type: 0, PCIe end point
> >> [84463.685121] {1}[Hardware Error]: version: 3.0
> >> [84463.685122] {1}[Hardware Error]: command: 0x0002, status: 0x0010
> >> [84463.685123] {1}[Hardware Error]: device_id: 0000:04:00.1
> >> [84463.685125] {1}[Hardware Error]: slot: 0
> >> [84463.685126] {1}[Hardware Error]: secondary_bus: 0x00
> >> [84463.685127] {1}[Hardware Error]: vendor_id: 0x14e4, device_id:
> 0x165f
> >> [84463.685128] {1}[Hardware Error]: class_code: 020000
> >> [84463.685129] {1}[Hardware Error]: aer_uncor_status: 0x00100000,
> >> aer_uncor_mask: 0x00010000
> >> [84463.685130] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
> >> [84463.685131] {1}[Hardware Error]: TLP Header: 40000001 0000010f
> >> 90028090 00000000
> >> [84463.685134] Kernel panic - not syncing: Fatal hardware error!
> >> [84463.685136] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: P
> O
> >> 6.5.13-3-pve #1
> >> [84463.685139] Hardware name: Dell Inc. PowerEdge R540/0VC7DK, BIOS
> 2.21.1
> >> 03/07/2024
> >> [84463.685140] Call Trace:
> >> [84463.685142] <NMI>
> >> =E2=80=A6
> >>
> >> root@pve:~# pveversion
> >> pve-manager/8.1.8/d29041d9f87575d0 (running kernel: 6.5.13-3-pve)
> >> root@pve:~# ethtool -i eno2
> >> driver: tg3
> >> version: 6.5.13-3-pve
> >> firmware-version: FFV22.71.3 bc 5720-v1.39
> >> expansion-rom-version:
> >> bus-info: 0000:04:00.1
> >> supports-statistics: yes
> >> supports-test: yes
> >> supports-eeprom-access: yes
> >> supports-register-dump: yes
> >> supports-priv-flags: no
> >> root@pve:~# lspci | fgrep 04:00.1
> >> 04:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme
> >> BCM5720 Gigabit Ethernet PCIe
> >>
> >>
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: Stefan Radman via pve-user <pve-user@lists.proxmox.com <mailto:
> pve-user@lists.proxmox.com>>
> >> To: PVE User List <pve-user@pve.proxmox.com <mailto:
> pve-user@pve.proxmox.com>>
> >> Cc: Stefan Radman <stefan.radman@me.com <mailto:stefan.radman@me.com>>
> >> Bcc:
> >> Date: Thu, 28 Mar 2024 15:50:02 +0100
> >> Subject: [PVE-User] 6.5.13-3-pve kernel panic on shutdown
> >> _______________________________________________
> >> pve-user mailing list
> >> pve-user@lists.proxmox.com <mailto:pve-user@lists.proxmox.com>
> >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >>
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com <mailto:pve-user@lists.proxmox.com>
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
>
>
> ---------- Forwarded message ----------
> From: Stefan Radman via pve-user <pve-user@lists.proxmox.com>
> To: Proxmox VE user list <pve-user@lists.proxmox.com>
> Cc: Stefan Radman <stefan.radman@me.com>
> Bcc:
> Date: Thu, 28 Mar 2024 16:47:43 +0100
> Subject: Re: [PVE-User] 6.5.13-3-pve kernel panic on shutdown
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>