I had a networking config option in my build unchecked while trying to resolve the earlier issue. Now I occasionally get the netstat report but I can still get it to hang., Try this scenario, it seems a little more reproducible: open Qemu/ELKS configured for telnet/http from host, enter telnet 127.0.0.1 2323 from ELKS enter netstat if you get invalid socket error, type netstat again -- for me it hangs if you get a valid netstat report, hit the enter key on your telnet session then try netstat again in ELKS. I get invalid socket try netstat again in ELKS. I get a hung system atthis point On Sun, Mar 5, 2017 at 1:56 AM, Georg Potthast 2 <nospam@xxxxxxxxxxxxxxxx> wrote: > 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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx >> >> 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@xxxxxxxxxxxxxxx >> 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
