Looking at the trace, it appears as though you just restored from a checkpoint. Is this the case? If so, what does the checkpoint dropping run do after that checkpoint is created? It's so early in the trace that I would guess it's a serialization bug, particularly in the TSO code. However, I looked quickly at the code and and nothing seemed to jump out at me. If you can provide me with an EthernetAll trace from the checkpoint run and from the restored run I can work on figuring out what the problem is.
Ali On Jan 28, 2009, at 2:53 AM, Rick Strong wrote: > >> There are three possibilities here: >> a) A kernel bug >> b) a device model/driver bug >> c) a checkpointing bug (as it relates to (b)) >> >> What kernel version are you using? Could you put the ethernet trace >> somewhere so I could look at it? >> >> Ali >> > > I am using the kernel 2.6.18 with M5 patches. > > I have put the ethernet traces up at http://rickshin.ucsd.edu. It is > the > only link. If you take a look, let me know what you think. > > Best, > -Rick > > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
