public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] virtualbox woes
Date: Sun, 31 Jul 2022 14:14:39 -0700	[thread overview]
Message-ID: <CAK2H+efCzQU-m7w372cxYXBVrUOVPM9GPGzBauxjTmyAsTpCGA@mail.gmail.com> (raw)
In-Reply-To: <Y5WUDIEU.E3RVDDTA.IKLRTNUG@CBXU6SYS.GLGPM655.2LDBQ436>

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

On Sun, Jul 31, 2022 at 10:58 AM Jack <ostroffjh@users.sourceforge.net>
wrote:
<SNIP>
> Sorry, I misread.  You shut down after it crashes.  Any idea what makes
> it crash?  Does it crash if you just start it and just let it sit?
> >
> > Jack

Jack,
   I'm no expert at reading crash reports but the screenshot he provided
earlier looks to me like the boot started, worked its way through the
initram stuff and then when handing over control to the main kernel
got mixed up and jumped to address 0000 which segfaults.

   I have no idea what that means in terms of a specific Gentoo
build. Is the kernel binary corrupted? The initram? Beyond my
abilities.

Mark

[-- Attachment #2: Type: text/html, Size: 938 bytes --]

  reply	other threads:[~2022-07-31 21:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 13:27 [gentoo-user] virtualbox woes Matthew Sacks
2022-07-31 13:30 ` Mark Knecht
2022-07-31 13:40   ` Matthew Sacks
2022-07-31 14:03     ` Mark Knecht
2022-07-31 14:08       ` Matthew Sacks
2022-07-31 14:46         ` Julien Roy
2022-07-31 14:46         ` Mark Knecht
2022-07-31 14:45 ` Jack
2022-07-31 17:58   ` Jack
2022-07-31 21:14     ` Mark Knecht [this message]
2022-08-01  0:46   ` Matthew Sacks
2022-08-01  8:17     ` Michael
2022-08-02  1:02       ` Matthew Sacks
2022-08-01  9:45     ` J. Roeleveld

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=CAK2H+efCzQU-m7w372cxYXBVrUOVPM9GPGzBauxjTmyAsTpCGA@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.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