Linux-8086 Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Potthast 2 <nospam@georgpotthast.de>
To: Jody Bruchon <jody@jodybruchon.com>,
	Derek Johansen <djohanse678@gmail.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: /dev/eth error
Date: Sun, 5 Mar 2017 09:56:08 +0100 (CET)	[thread overview]
Message-ID: <1926931262.151011.1488704168838@communicator.strato.com> (raw)
In-Reply-To: <CAOv0vdn+CoX-_8m6Q6_UYPVPne0GK-dMu+HnakzPES-3B2dWJQ@mail.gmail.com>

Derek,

I tried to follow your observations but netstat does not hang here and I can access the httpd server before and after entering the netstat command as well.

By the way, netstat on ELKS does not read any command line parameters.

Georg

> Derek Johansen <djohanse678@gmail.com> hat am 5. März 2017 um 07:41 geschrieben:
> 
> 
> Another perturbation along these lines.  If I start qemu.sh configured
> to use httpd, then from my web browser navigate to
> http://localhost:8080, I see the web browser served from ELKS as
> expected.
> 
>   If i start netstat in ELKS, then  try to navigate to
> http://localhost:8080 from my browser, the browser spins for a few
> minutes then errors out with an error page "Server not found"
> 
> On Sat, Mar 4, 2017 at 9:45 PM, Derek Johansen <djohanse678@gmail.com> wrote:
> > Thanks Jody.  That worked. But...
> >
> > Next problem :-
> >
> > Using this latest build, I start qemu with sudo ./qemu.sh (no edits to
> > any files after the git pull)
> >
> > On ELKS:
> >
> > login as root
> >
> >>cd /bin
> >>ls
> >>netstat -h
> >
> > <<<HANG>>>>
> >
> > The problem: Calling netstat -h hangs qemu.
> >
> > Thanks,
> > Derek
> >
> > On Sat, Mar 4, 2017 at 8:58 PM, Jody Bruchon <jody@jodybruchon.com> wrote:
> >> On 2017-03-04 10:17 PM, Derek Johansen wrote:
> >>>
> >>> After pulling in all of todays changes, I see these errors again as
> >>> described in original email.  Previously I had not enabled networking
> >>> or the ne2k driver, and the problem was fixed when I enabled them
> >>> during the ./build.sh script.  Now I enable them during the ./uild.sh
> >>> script and when I start ELKS with sudo ./qemu.sh these errors are
> >>> back.
> >>
> >> I forgot to pull in config.h for the new ethernet init call. Fixed in the
> >> latest commit (commit 3e48ec5) and doesn't error out in QEMU anymore.
> >>
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-03-05  8:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04  4:04 /dev/eth error Derek Johansen
2017-03-04  5:49 ` Derek Johansen
2017-03-04  9:32   ` Marc-François LUCCA-DANIAU
2017-03-05  3:17     ` Derek Johansen
2017-03-05  3:58       ` Jody Bruchon
2017-03-05  4:45         ` Derek Johansen
2017-03-05  6:41           ` Derek Johansen
2017-03-05  8:56             ` Georg Potthast 2 [this message]
2017-03-05  9:21               ` Derek Johansen
2017-03-05 10:01                 ` Georg Potthast 2

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=1926931262.151011.1488704168838@communicator.strato.com \
    --to=nospam@georgpotthast.de \
    --cc=djohanse678@gmail.com \
    --cc=jody@jodybruchon.com \
    --cc=linux-8086@vger.kernel.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