Re: amd64 direct map causing crashes at boot (Re: CVS commit: src/sys/arch)

[Nicolas Joly <njoly%pasteur.fr@localhost>]

On Fri, Dec 09, 2011 at 02:41:16PM +0100, Manuel Bouyer wrote:
> On Thu, Dec 08, 2011 at 11:24:35PM +0100, Nicolas Joly wrote:
> > On Thu, Dec 08, 2011 at 11:21:31PM +0100, Joerg Sonnenberger wrote:
> > > On Thu, Dec 08, 2011 at 11:10:41PM +0100, Nicolas Joly wrote:
> > > > I do have two machines that fail to boot with this change.
> > > > 
> > > > 1) A Dell Optiplex 740 that reboots early after loading the kernel.
> > > >    Includes 1 "AMD Athlon(tm) 64 X2 Dual Core Processor 4800+" CPU.
> > > > 
> > > > 2) A Supermicro H8DG6-F motherboard (only 1 socket populated) later on
> > > >    boot mostly when sshd start (or fc-cache is updated).
> > > >    Includes 1 "AMD Opteron(tm) Processor 6128A" CPU
> > > 
> > > Can you try to disable the use of 1GB pages?
> > 
> > Already tested for the 6128A, still no luck.
> 
> Can you print the content of mem_clusters[] and mem_cluster_count ?
> I wonder if we're missing some memory ...

Here's the DEBUG_MEMLOAD output that Chuck already asked

BIOS MEMORY MAP (12 ENTRIES):
    addr 0x0  size 0x93800  type 0x1
    addr 0x93800  size 0xc800  type 0x2
    addr 0xe6000  size 0x1a000  type 0x2
    addr 0x100000  size 0xb7d80000  type 0x1
    addr 0xb7e8e000  size 0x2000  type 0x9
    addr 0xb7e90000  size 0x24000  type 0x3
    addr 0xb7eb4000  size 0x2c000  type 0x4
    addr 0xb7ee0000  size 0x20000  type 0x2
    addr 0xb7f00000  size 0x100000  type 0x2
    addr 0xe0000000  size 0x10000000  type 0x2
    addr 0xffe00000  size 0x200000  type 0x2
    addr 0x100000000  size 0x148000000  type 0x1
loading first16q 0xf000-0x93000 (0xf-0x93)
loading first4gq 0x133e000-0xb7e80000 (0x133e-0xb7e80)
loading default 0x100000000-0x248000000 (0x100000-0x248000)

Does this fit your needs or do you need mem_clusters output too ?

-- 
Nicolas Joly

Projects and Developments in Bioinformatics
Institut Pasteur, Paris.