mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Stefano Manni <stefano.manni@gmail.com>, barebox@lists.infradead.org
Subject: Re: eth frame error on imx6ul
Date: Mon, 5 Aug 2024 18:57:47 +0200	[thread overview]
Message-ID: <9695c594-d410-4e72-afeb-68777a82ce71@pengutronix.de> (raw)
In-Reply-To: <34a3bd84065357c7ab6e8a55c6ec34f5267edad6.camel@gmail.com>

On 05.08.24 16:38, Stefano Manni wrote:
> Hello Ahmad
> 
> On Mon, 2024-08-05 at 15:54 +0200, Ahmad Fatoum wrote:
>>
>> Do you have TFTP or something running while seeing these errors,
>> or when do they pop up?
> 
> They pop up unconditionally just after ifup. If I run tcpdump on the
> same LAN I see a lot of multicast/broadcast frames and probably the
> error comes out on the reception of them. Also because I figured out
> from fec_imx.h that 0x00000886 means:
> 
> #define FEC_RBD_LAST		0x0800	/**< Receive BD status: Buffer
> is last in frame (useless here!) */
> #define FEC_RBD_BC		0x0080	/**< Receive BD status: The
> received frame is broadcast frame */
> #define FEC_RBD_CR		0x0004	/**< Receive BD status: CRC
> error */
> #define FEC_RBD_OV		0x0002	/**< Receive BD status: Receive
> FIFO overrun */

You can enable CONFIG_CMD_ETHLOG to capture the frames and see if
the frame that triggers the error looks odd in some way.

Cheers,
Ahmad


> 
> Best,
> Stefano
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2024-08-05 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 13:48 Stefano Manni
2024-08-05 13:54 ` Ahmad Fatoum
2024-08-05 14:38   ` Stefano Manni
2024-08-05 16:57     ` Ahmad Fatoum [this message]
2024-08-06  7:59       ` Stefano Manni

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=9695c594-d410-4e72-afeb-68777a82ce71@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=stefano.manni@gmail.com \
    /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