Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-09 Thread Stefan Reinauer
On 4/9/10 12:47 PM, Rudolf Marek wrote: >> Does this interfere with suspend/resume? Is there a ticket already >> created >> for this? It looks like something that would be hard to debug in system. > > It does, but I ignore that because I think this code is not used when > CAR is used? > On intel c

Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-09 Thread Rudolf Marek
Does this interfere with suspend/resume? Is there a ticket already created for this? It looks like something that would be hard to debug in system. It does, but I ignore that because I think this code is not used when CAR is used? Rudolf -- coreboot mailing list: coreboot@coreboot.org http:

Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-08 Thread Myles Watson
On Tue, Apr 6, 2010 at 4:21 PM, Myles Watson wrote: > I'm seeing code reads to memset() in coreboot_ram interleaved with byte > writes to somewhere high on the stack (_estack -0x1fC). This is a k8. > It turns out init_processor_name() was being called with the cache disabled. It doesn't look l

Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-07 Thread Myles Watson
> On Tue, Apr 06, 2010 at 04:21:57PM -0600, Myles Watson wrote: > > I'm seeing code reads to memset() in coreboot_ram interleaved with byte > > writes to somewhere high on the stack (_estack -0x1fC). This is a k8. > > > > I can't find the place during the RAM stage when we are calling memset > wit

Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-06 Thread Kevin O'Connor
On Tue, Apr 06, 2010 at 04:21:57PM -0600, Myles Watson wrote: > I'm seeing code reads to memset() in coreboot_ram interleaved with byte > writes to somewhere high on the stack (_estack -0x1fC). This is a k8. > > I can't find the place during the RAM stage when we are calling memset with > caches

Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-06 Thread Myles Watson
> Maybe you can run under SimNow and use a memory access breakpoint? Good idea. How do you tell in SimNow if an access is cached or not? Thanks, Myles -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-06 Thread Rudolf Marek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Myles Watson wrote: >> Maybe you can run under SimNow and use a memory access breakpoint? > Good idea. How do you tell in SimNow if an access is cached or not? Dont know maybe you can check CPU state after a breakpoint? Rudolf > > Thanks, > Myles

Re: [coreboot] memset called to somewhere high on the stack (uncached)

2010-04-06 Thread Rudolf Marek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maybe you can run under SimNow and use a memory access breakpoint? Rudolf -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAku7tQsACgkQ3J9wPJqZRNVLPQCeOgzlrj7S

[coreboot] memset called to somewhere high on the stack (uncached)

2010-04-06 Thread Myles Watson
I'm seeing code reads to memset() in coreboot_ram interleaved with byte writes to somewhere high on the stack (_estack -0x1fC). This is a k8. I can't find the place during the RAM stage when we are calling memset with caches disabled. Does this ring a bell for anyone? Thanks, Myles -- corebo