Bug 133768

Summary:	[panic] MONITOR PANIC: vcpu-0:VMM64 DoubleFault src=MONITOR @ rip=0xfffffffffc24e530 rsp=0xfffffffffc001000 regs=0xfffffffffc048f40 (0xfffffffffc24e9f1,0xfffffffffc24e530)While Powering ON FreeBSD 7.1 -64bit guest with 64GB RAM
Product:	Base System	Reporter:	Vishwas Karmalekar <vishwas.karmalekar>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Open ---
Severity:	Affects Only Me	Keywords:	crash
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description Vishwas Karmalekar 2009-04-16 07:20:01 UTC

FreeBSD 7.1 - 32bit-

Configuring PAE in FreeBSD 6.3 & 7.1 systems follow different steps. 
In FreeBSD 7.1 -32bit, the PAE kernel configuration file is included with the distribution, one doesn't need to create it.
Steps that I followed-
cd /usr/src/sys/i386/conf 
config PAE 
cd ../compile/PAE 
make cleandepend && make depend 
make  
make install 
reboot
Systems works perfectly with 16GB RAM(This means PAE is working in the guest.)

* With 24GB & 32GB memory, system hangs & gives error-
  Panic : Page fault error.

* With 64GB of RAM, the system hangs & gives error-

MONITOR PANIC: vcpu-0:DoubleFault @ 0x4020:0xb91d8 (0xff0,0x1064) (0xb6cb8, 0xb9130)

FreeBSD 7.1 - 64bit
There are no issues uptil 24GB RAM.

* With 32GB RAM,  system hangs & gives error-
  Panic : Page fault error.

* With 64GB of RAM, the system hangs & gives error-

MONITOR PANIC: vcpu-0:VMM64 DoubleFault src=MONITOR @ rip=0xfffffffffc24e530 rsp=0xfffffffffc001000 regs=0xfffffffffc048f40 (0xfffffffffc24e9f1,0xfffffffffc24e530


My query is-
(1) 64GB works fine if PAE is enabled in 32bit FBSD 7.1 32bit?
(2) Am I making any mistake in executing steps.
(3) The reason behind Panic: Page fault
(4) The reason behinf Memory Panic
(5) Is this a OS related issue.


Please let me know the solution for the above issue.

Thanks in advance.

Vishwas

How-To-Repeat: If I change the RAM size to 16GB, both of the dead systems are UP & work very well. Ofcourse, it takes a large "UP time". (may be 10-15 mins)

If one changes the system ram to 64GB, the issue can be reproduced.

Comment 1 Gavin Atkinson freebsd_committer

2009-04-17 16:57:59 UTC

State Changed
From-To: open->feedback

To submitter: it looks like you are attempting this inside a virtual 
machine, is that correct?  If so, what software are you using? 
Secondly, when you have 32GB or 64GB of memory configured, when does 
the panic happen?  Is it during boot, or at some point after boot? 

Coupld you also please provide output from the following commands? (if 
possible, while the machine is configured for 32 or 64GB of RAM) 

"pciconf -lv" 
"dmesg" 
"memcontrol list" 

Thanks!

Comment 2 Gavin Atkinson freebsd_committer

2009-04-17 16:57:59 UTC

Responsible Changed
From-To: freebsd-bugs->gavin

Track

Comment 3 Eitan Adler freebsd_committer

2017-12-31 07:59:26 UTC

For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped

Comment 4 Graham Perrin freebsd_committer

2022-10-17 12:17:18 UTC

Keyword: 

    crash

– in lieu of summary line prefix: 

    [panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>