From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] Invalid Netconsole source MAC address [was: Re: [STATUS] v2012.07-rc1 is out - release date July 23]
Date: Mon, 23 Jul 2012 22:41:22 +0200 [thread overview]
Message-ID: <201207232241.22673.michael@walle.cc> (raw)
In-Reply-To: <CANr=Z=aKmR+0bb0D2PPZLwYjSYft6J7simFL5puAjDQWVczPkA@mail.gmail.com>
Hi Joe,
Am Montag 23 Juli 2012, 21:30:28 schrieb Joe Hershberger:
> On Sat, Jul 21, 2012 at 1:04 PM, Michael Walle <michael@walle.cc> wrote:
> > Mh i guess NetLoop isn't called and thus NetOurEther is never
> > initialized. Similar issue like
> > d7310c7e63ca9ffd42527dc9735cb505cbe908b7. Initializing NetOurEther in
> > net_init() fixes the problem.
>
> I tested this on Panda board and wireshark reports the correct source
> MAC address.
>
> Please provide details of which board and driver you are using.
Board: LS-CHLv2/kirkwood arm; ethaddr set to some valid ethernet address ;)
If NetLoop isn't called the internal ethernet address is not initialized.
Hopefully the following sequence triggers the bug:
- boot the board, _dont_ do any network interaction
- setenv stdout nc
- type sth on the serial console
--> now the packets are send with source MAC == 00:00:00:00:00:00.
If you look at the code NetOurEther is only initialized in NetLoop and i guess
NetLoop() isn't called for outgoing NetConsole packets.
--
Michael
next prev parent reply other threads:[~2012-07-23 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 18:04 [U-Boot] Invalid Netconsole source MAC address [was: Re: [STATUS] v2012.07-rc1 is out - release date July 23] Michael Walle
2012-07-23 19:30 ` Joe Hershberger
2012-07-23 20:41 ` Michael Walle [this message]
2012-07-23 22:07 ` Joe Hershberger
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=201207232241.22673.michael@walle.cc \
--to=michael@walle.cc \
--cc=u-boot@lists.denx.de \
/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