All of lore.kernel.org
 help / color / mirror / Atom feed
From: pietrushnic <pietrushnic@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unable to receive DHCP packets (qemu-system-arm)
Date: Sun, 12 May 2013 02:22:56 +0200	[thread overview]
Message-ID: <518EE0E0.5040500@gmail.com> (raw)

Hi all,
I'm unable to receive DHCP packets using qemu-system-arm 1.4.91 with 
u-boot (commit: 2988eac). Problem occurs on Ubuntu 12.04 (I tried also 
Debian wheezy and there was no issue). I accidentally discover that 
adding '-net dump,file=/tmp/dump.pcap' cause that problem disapear, but 
want to dig it and find out what the root cause is.

I tried to debug issue from u-boot source code perspective and added 
verbose logging, but can't see anything strange enough:
- log with fail - qemu w/o additional dump command - 
https://gist.github.com/pietrushnic/5561859
- log with pass - qemu w/ addional dump param - 
https://gist.github.com/pietrushnic/5561866
Difference:
- smc_rcv status is always 0 , NetLoop timeouts for failed case
- on failed case u-boot receive some packets but not DHCP offer (I 
positively verified w/ tcpdump that server sent this packet)

I'm trying to narrow down this problem from both (qemu and u-boot) side. 
Is there anything else what I can do to confirm that this is not u-boot 
issue ?
Maybe someone heard about this kind of problem ?

My network configuration based on: http://toast.djw.org.uk/qemu.html
I'm using versatilepb_config compiled with arm-unknown-linux-gnueabi 
(created using crosstool-NG).

If provided information are insufficient, just let me know.

Regards,
pietrushnic

                 reply	other threads:[~2013-05-12  0:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=518EE0E0.5040500@gmail.com \
    --to=pietrushnic@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.