Looks like a remote gdb session is causing a read request to a address that is part of the GIC. The GIC expects all reads targeting it to original from a CPU and thus have a context id.
Do you have a remote debugger attached? You could change the gig to ignore any requests that don't have a context id set instead of asserting. Ali On Apr 15, 2012, at 10:53 PM, Samuel Hitz wrote: > Hi there, > > I'm getting a > > Assertion `privateFlags.isSet(VALID_CONTEXT_ID)' failed > > while initializing the GIC. Here is a backtrace from gem5 > > gem5.debug: build/ARM/mem/request.hh:459: int Request::contextId() const: > Assertion `privateFlags.isSet(VALID_CONTEXT_ID)' failed. > > Program received signal SIGABRT, Aborted. > 0x00007ffff6460c35 in raise () from /lib/libc.so.6 > (gdb) bt > #0 0x00007ffff6460c35 in raise () from /lib/libc.so.6 > #1 0x00007ffff64620b8 in abort () from /lib/libc.so.6 > #2 0x00007ffff6459c12 in __assert_fail_base () from /lib/libc.so.6 > #3 0x00007ffff6459cc2 in __assert_fail () from /lib/libc.so.6 > #4 0x000000000180cebc in Request::contextId (this=0x7fffffffb100) at > build/ARM/mem/request.hh:459 > #5 0x0000000001821f75 in Gic::readDistributor (this=0x369ffd0, > pkt=0x7fffffffb0a0) at build/ARM/dev/arm/gic.cc:145 > #6 0x00000000018215d6 in Gic::read (this=0x369ffd0, pkt=0x7fffffffb0a0) at > build/ARM/dev/arm/gic.cc:117 > #7 0x0000000001791b42 in PioPort::recvAtomic (this=0x36a0000, > pkt=0x7fffffffb0a0) at build/ARM/dev/io_device.cc:47 > #8 0x000000000189b514 in SimpleTimingPort::recvFunctional (this=0x36a0000, > pkt=0x7fffffffb0a0) at build/ARM/mem/tport.cc:87 > #9 0x000000000053fea6 in Port::sendFunctional (this=0x35235c0, > pkt=0x7fffffffb0a0) at build/ARM/mem/port.hh:210 > #10 0x000000000188cde6 in Bus::recvFunctional (this=0x3659da0, > pkt=0x7fffffffb0a0) at build/ARM/mem/bus.cc:473 > #11 0x0000000001891911 in Bus::BusPort::recvFunctional (this=0x3446ad0, > pkt=0x7fffffffb0a0) at build/ARM/mem/bus.hh:113 > #12 0x000000000053fea6 in Port::sendFunctional (this=0x36b59e8, > pkt=0x7fffffffb0a0) at build/ARM/mem/port.hh:210 > #13 0x000000000189ccda in PortProxy::blobHelper (this=0x36bb900, > addr=520097792, p=0x376ec70 "", size=8, cmd=...) at > build/ARM/mem/port_proxy.cc:53 > #14 0x00000000016b9133 in PortProxy::readBlob (this=0x36bb900, > addr=520097792, p=0x376ec70 "", size=8) at build/ARM/mem/port_proxy.hh:101 > #15 0x000000000189d148 in FSTranslatingPortProxy::readBlob (this=0x36bb900, > addr=3218083840, p=0x376ec70 "", size=8) at > build/ARM/mem/fs_translating_port_proxy.cc:82 > #16 0x000000000140ef60 in BaseRemoteGDB::read (this=0x36bb5e0, > vaddr=3218083840, size=8, data=0x376ec70 "") at > build/ARM/base/remote_gdb.cc:465 > #17 0x0000000001415cdb in BaseRemoteGDB::trap (this=0x36bb5e0, type=5) at > build/ARM/base/remote_gdb.cc:744 > #18 0x0000000001412551 in BaseRemoteGDB::HardBreakpoint::process > (this=0x376da70, tc=0x36b7950) at build/ARM/base/remote_gdb.cc:535 > #19 0x0000000001505c30 in PCEventQueue::doService (this=0x360d820, > tc=0x36b7950) at build/ARM/cpu/pc_event.cc:102 > #20 0x00000000015261fa in PCEventQueue::service (this=0x360d820, > tc=0x36b7950) at build/ARM/cpu/pc_event.hh:107 > #21 0x000000000152624c in BaseSimpleCPU::checkPcEventQueue (this=0x36b56f0) > at build/ARM/cpu/simple/base.hh:98 > #22 0x0000000001524c4c in AtomicSimpleCPU::tick (this=0x36b56f0) at > build/ARM/cpu/simple/atomic.cc:446 > #23 0x0000000001520504 in AtomicSimpleCPU::TickEvent::process > (this=0x36b5980) at build/ARM/cpu/simple/atomic.cc:59 > #24 0x000000000145fecc in EventQueue::serviceOne (this=0x28cf0e0) at > build/ARM/sim/eventq.cc:204 > #25 0x00000000014b5533 in simulate (num_cycles=9223372036854775807) at > build/ARM/sim/simulate.cc:73 > #26 0x0000000000447c7c in _wrap_simulate__SWIG_0 (args=0x34ece50) at > build/ARM/python/swig/event_wrap.cc:4475 > #27 0x0000000000447e3a in _wrap_simulate (self=0x0, args=0x34ece50) at > build/ARM/python/swig/event_wrap.cc:4525 > #28 0x00007ffff74d91b9 in PyEval_EvalFrameEx () from > /usr/lib/libpython2.7.so.1.0 > #29 0x00007ffff74da86f in PyEval_EvalCodeEx () from > /usr/lib/libpython2.7.so.1.0 > #30 0x00007ffff74d8a9e in PyEval_EvalFrameEx () from > /usr/lib/libpython2.7.so.1.0 > #31 0x00007ffff74d94a8 in PyEval_EvalFrameEx () from > /usr/lib/libpython2.7.so.1.0 > #32 0x00007ffff74da86f in PyEval_EvalCodeEx () from > /usr/lib/libpython2.7.so.1.0 > #33 0x00007ffff74da9a2 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0 > #34 0x00007ffff74d8d20 in PyEval_EvalFrameEx () from > /usr/lib/libpython2.7.so.1.0 > #35 0x00007ffff74da86f in PyEval_EvalCodeEx () from > /usr/lib/libpython2.7.so.1.0 > #36 0x00007ffff74d8a9e in PyEval_EvalFrameEx () from > /usr/lib/libpython2.7.so.1.0 > #37 0x00007ffff74da86f in PyEval_EvalCodeEx () from > /usr/lib/libpython2.7.so.1.0 > #38 0x00007ffff74da9a2 in PyEval_EvalCode () from /usr/lib/libpython2.7.so.1.0 > #39 0x00007ffff74f4cac in run_mod () from /usr/lib/libpython2.7.so.1.0 > #40 0x00007ffff74f589d in PyRun_StringFlags () from > /usr/lib/libpython2.7.so.1.0 > #41 0x000000000146ad38 in m5Main (argc=3, argv=0x7fffffffe0e8) at > build/ARM/sim/init.cc:256 > #42 0x000000000040b16b in main (argc=3, argv=0x7fffffffe0e8) at > build/ARM/sim/main.cc:57 > > I have no idea, what's causing this. Can someone with some insight shed some > light on this? > > Best, > > Sam > _______________________________________________ > 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
