Date: Sun, 7 Aug 2005 21:24:24 GMT From: Hans Meyer <asstech@matik.com.br> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/84656: kernel panic when kern.maxdsiz is => hw.physmem Message-ID: <200508072124.j77LOObN047409@www.freebsd.org> Resent-Message-ID: <200508072150.j77Lo9r8087359@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 84656
>Category: kern
>Synopsis: kernel panic when kern.maxdsiz is => hw.physmem
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Aug 07 21:50:09 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Hans Meyer
>Release: 5.4R - 5.3R 4.11R
>Organization:
Infomatik
>Environment:
FreeBSD gw.lucenet.com.br 5.4-RELEASE FreeBSD 5.4-RELEASE #5: Fri Aug 5 11:42:14 BRST 2005 hmm@gw.lucenet.com.br:/usr/src/sys/i386/compile/wipgw i386
>Description:
I saw the other PRs
when setting kern.maxdsiz in /boot/loader.conf to a higher value than hw.physmem a kernel panic right after the kernel load when real memory and available memory should appear.
this appearently is hardware related because it happens on Sempron and other P4/Asus motherboards but not on AMD XP/Asus MBs. Memory amount does not matter, I get it on 1 to 4GB RAM. On AMD the higher value is accepted and the machine runs fine even when swapping after.
Compiling MAXDSIZ or setting in loader.conf makes no diference as well as acpi enable or not
The panic messages are cannot allocate virtual memory
there is no core
>How-To-Repeat:
>Fix:
remove /boot/loder.conf
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508072124.j77LOObN047409>