9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Xiao-Yong Jin <meta.jxy@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] kernel crash in bhyve
Date: Wed, 9 Dec 2020 15:22:26 -0600	[thread overview]
Message-ID: <BB40C446-2B8B-4912-A828-527C4CC31015@gmail.com> (raw)
In-Reply-To: <B6A7B558B0B7B380D6551E392EA253A2@felloff.net>


> On Dec 9, 2020, at 2:52 PM, cinap_lenrek@felloff.net wrote:
> 
> yeah, its like i said. after mtrrexclude, theres no
> more ram left.
> 
> so i guess the mtrr's are probably programmed to
> everything uncached.
> 
> can you try to boot with *nomtrr= please?

The first chunk of the output in my last email was with *nomtrr=
and it booted fine.

Plan 9
wrmsr to register 0x401(0) on vcpu 0
                                   125 holes free
0x00024000 0x0009f000 503808
0x00100000 0x00110000 65536
0x005f7000 0x136ff000 319848448
320417792 bytes free
cpu0: 6785MHz GenuineIntel P6 (AX 000306A9 CX F69A6217 DX 9F8BFBFF)
LAPIC: fee00000 0xffffff00fee00000
ELCR: 0260
cpu0: lapic clock at 268MHz
#l0: virtio: 1000Mbps port 0x2080 irq 6 ea 52540000b008
1024M memory: 336M kernel data, 688M user, 1313M swap

  reply	other threads:[~2020-12-09 21:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 18:18 Xiao-Yong Jin
2020-12-09 18:26 ` [9front] " Xiao-Yong Jin
2020-12-09 18:44   ` ori
2020-12-09 19:05 ` [9front] " cinap_lenrek
2020-12-09 19:42   ` Xiao-Yong Jin
2020-12-09 20:52     ` cinap_lenrek
2020-12-09 21:22       ` Xiao-Yong Jin [this message]
2020-12-09 22:04         ` cinap_lenrek
2020-12-09 22:36           ` Xiao-Yong Jin
2020-12-09 23:18             ` cinap_lenrek
2020-12-10  0:10               ` Xiao-Yong Jin
2020-12-10  0:45                 ` cinap_lenrek
2020-12-10 11:30                 ` cinap_lenrek
2020-12-10 20:37                   ` Xiao-Yong Jin
2020-12-10 23:12                     ` Nick Owens
2020-12-11  4:55                       ` Xiao-Yong Jin
2020-12-11 14:27                         ` cinap_lenrek
2020-12-11  1:12                   ` ori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BB40C446-2B8B-4912-A828-527C4CC31015@gmail.com \
    --to=meta.jxy@gmail.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).