Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Jun 2005 22:31:25 +0200
From:      Marius Strobl <marius@alchemy.franken.de>
To:        Hiroki Sato <hrs@freebsd.org>
Cc:        sparc64@freebsd.org
Subject:   Re: E4500 with 24GB RAM
Message-ID:  <20050606223125.A80582@newtrinity.zeist.de>
In-Reply-To: <20050607.015510.21897573.hrs@allbsd.org>; from hrs@freebsd.org on Tue, Jun 07, 2005 at 01:55:10AM %2B0900
References:  <20050530.025302.64839649.hrs@allbsd.org> <429A7B4D.3080102@samsco.org> <20050607.015510.21897573.hrs@allbsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 07, 2005 at 01:55:10AM +0900, Hiroki Sato wrote:
> Scott Long <scottl@samsco.org> wrote
>   in <429A7B4D.3080102@samsco.org>:
> 
> sc> I'd guess that you're the first to have access to so much memory
> sc> and a machine to hold it.  The error means that vm_map_find()
> sc> returned KERN_NO_SPACE.  It could be that there is a 64-bit bug
> sc> in the code, or it could be that the page tables to index so much
> sc> memory consume all available space in the kernel map.
> 
>  Thanks.  Jake gave me an advice about kern.maxbcache tunable, and
>  I finally make it boot with kern.maxbcache=524288000.
>  However, the hme driver seems to have a problem:
> 
>  |panic: iommu_enter: XXX: physical address too large (0x5e3fcc000)
>  |cpuid = 0
>  |KDB: enter: panic
>  |[thread pid 442 tid 100215 ]
>  |Stopped at      kdb_enter+0x3c: ta              %xcc, 1
>  |db> tr
>  |Tracing pid 442 tid 100215 td 0xfffff800af657b80
>  |panic() at panic+0x16c
>  |iommu_enter() at iommu_enter+0x3c
>  |iommu_dvmamap_load_buffer() at iommu_dvmamap_load_buffer+0x118
>  |iommu_dvmamap_load_mbuf() at iommu_dvmamap_load_mbuf+0x170
>  |hme_load_txmbuf() at hme_load_txmbuf+0x68
>  |hme_start_locked() at hme_start_locked+0x1bc
>  |hme_start() at hme_start+0x2c
>  |if_start() at if_start+0xa0
>  |ether_output_frame() at ether_output_frame+0x244
>  |ether_output() at ether_output+0x474
>  |ip_output() at ip_output+0xa98
>  |udp_output() at udp_output+0x5b4
>  |udp_send() at udp_send+0x14
>  |sosend() at sosend+0x654
> 
>  When INVARIANTS enabled this panic occurs instantly.
> 

You're probably hitting the 16GB limit of the current IOMMU code.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050606223125.A80582>