DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: Ciara Loftus <ciara.loftus@intel.com>, dev@dpdk.org
Cc: bruce.richardson@intel.com, stable@dpdk.org
Subject: Re: [PATCH] net/e1000: fix crash when built with GCC 13
Date: Fri, 10 Oct 2025 15:31:51 +0200	[thread overview]
Message-ID: <f2050e39-4fb2-44cb-bbf6-e0fca99ab9cd@6wind.com> (raw)
In-Reply-To: <20251010125848.965340-1-ciara.loftus@intel.com>

On 10/10/25 14:58, Ciara Loftus wrote:
> The e1000 PMD crashes during initialisation in a Ubuntu 24.04 VM when
> compiled with gcc-13 with -O3 optimisations. This patch introduces a
> compiler barrier after the register read that was causing the issue.
> 
> Bugzilla ID: 1691
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>

Tested-by: Thierry Herbelot <thierry.herbelot@6wind.com>

The patch fixes the crash at startup.

	Thanks

	Thierry

> ---
>   drivers/net/intel/e1000/base/e1000_mac.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/intel/e1000/base/e1000_mac.c b/drivers/net/intel/e1000/base/e1000_mac.c
> index 2fa97d12a9..41aae86ffe 100644
> --- a/drivers/net/intel/e1000/base/e1000_mac.c
> +++ b/drivers/net/intel/e1000/base/e1000_mac.c
> @@ -1842,6 +1842,7 @@ s32 e1000_id_led_init_generic(struct e1000_hw *hw)
>   		return ret_val;
>   
>   	mac->ledctl_default = E1000_READ_REG(hw, E1000_LEDCTL);
> +	rte_compiler_barrier();
>   	mac->ledctl_mode1 = mac->ledctl_default;
>   	mac->ledctl_mode2 = mac->ledctl_default;
>   

-- 
Thierry Herbelot

      reply	other threads:[~2025-10-10 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 12:58 Ciara Loftus
2025-10-10 13:31 ` Thierry Herbelot [this message]

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=f2050e39-4fb2-44cb-bbf6-e0fca99ab9cd@6wind.com \
    --to=thierry.herbelot@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).