On Mon, Apr 16, 2012 at 11:28 AM, Steve Reinhardt <[email protected]> wrote: > This literally means what it says, so it's clearly your problem: > > warn: Sockets disabled, not accepting terminal connections > > I believe the test config sets a flag that disables the terminal sockets > since otherwise some other random program connecting to the port could cause > the test to fail. I don't recall the exact line, but if you look through > the config you should be able to find it. >
Yes, I just did my bit of searching and found it. It's in run.py : m5.disableAllListeners() with a comment above that says the same thing : # Since we're in batch mode, dont allow tcp socket connections Thanks for the help. Anirudh > Steve > > > On Mon, Apr 16, 2012 at 8:04 AM, Anirudh Sivaraman <[email protected]> > wrote: >> >> On Mon, Apr 16, 2012 at 10:55 AM, Steve Reinhardt <[email protected]> >> wrote: >> > Check the output. 3456 is the default port for terminal connections, >> > but >> > obviously if you're simulating multiple systems on the same host (in the >> > same or separate instances of gem5) they can't all use the same port, so >> > they'll increment the port number until they find a free one. The >> > output >> > will tell you which port number(s) is/are being used. >> >> Thank you for the prompt reply. I looked at the output and I can't >> find any indication of any port number. This is despite running just >> one instance of twosys-tsunami-simple-atomic. I tried a few port >> numbers beyond 3456 as well. I wonder if this means anything (from the >> output) : >> >> warn: Sockets disabled, not accepting terminal connections >> 0: testsys.tsunami.io.rtc: Real-time clock set to Thu Jan 1 00:00:00 >> 2009 >> 0: drivesys.tsunami.io.rtc: Real-time clock set to Thu Jan 1 >> 00:00:00 2009 >> warn: Sockets disabled, not accepting gdb connections >> >> Why does this happen ? >> >> Anirudh >> > >> > Steve >> > >> > On Mon, Apr 16, 2012 at 7:50 AM, Anirudh Sivaraman >> > <[email protected]> >> > wrote: >> >> >> >> Hi >> >> >> >> I have been trying to modify twosys-tsunami-simple-atomic to work with >> >> EtherTap instead of EtherLink. I have connected the TCP listener port >> >> on the GEM5 end to a tap interface using socat. I have also checked >> >> that if I inject packets into the tap interface, GEM5 is able to see >> >> them. I now want to ping one GEM5 instance from another using a tap >> >> interface. >> >> >> >> So, after running : >> >> build/ALPHA/gem5.opt tests/run.py >> >> >> >> >> >> build/ALPHA/tests/opt/quick/fs/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic >> >> >> >> I run m5term localhost 3456 so that I can interact with the simulated >> >> system. This returns immediately and doesn't open a shell as it >> >> usually does. As far as I know, this is the only way to get a shell on >> >> GEM5. Is there a better way ? >> >> >> >> Anirudh >> >> _______________________________________________ >> >> gem5-users mailing list >> >> [email protected] >> >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> > >> > >> > >> > _______________________________________________ >> > gem5-users mailing list >> > [email protected] >> > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> _______________________________________________ >> gem5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
