public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] New Gentoo system has become unstable and unusable - help, please!
Date: Fri, 12 Feb 2010 08:54:53 +0000	[thread overview]
Message-ID: <20100212085453.GA1207@muc.de> (raw)

Hi, Gentoo,

My new Gentoo box has become unusably unstable.

The first sign was when the compiler threw a segfault whilst emerging
the xfce window manager.  I "solved" this by emerging Openbox instead.

Then I got another compiler segfault whilst emerging firefox (yes, I
know there's a binary for this).

Then, on somebody's advice (not fully understood), I did

    # emerge -e gcc

, to try and get a consistent working gcc.  This crashed.  I repeated
the invocation, and it crashed more quickly.  :-(

At this point, I thought, just reload "everything" from the stage3, with

    # cd / ; bunzip2 /stage3-amd64-20100121.tar.gz

, which didn't help either.  I emerged gentoolkit, to see if I could get
some handle on the mess.  Then

    # revdep-rebuild -p

threw a segfault.

At this point, I'm feeling a bit sad.  My rough guess is that there's
some conflict somewhere between 32-bit and 64-bit code, and some of my
USE flags are inconsistent with some others, or the kernel, or something
like that.

One other thing I remember vaguely is that early on, some emerge told me
I had to "revdep-rebuild" something.  I wasn't able to do this through
not yet knowing what "revdep-rebuild" meant, and not having any file of
that name on my system.  Could this be the cause?

Finally, is there a way of reloading/rebuilding ALL the executables
onto/on my system without discarding all my painfully wrought config
files and without portage getting confused?

Thanks in advance for the help!

-- 
Alan Mackenzie (Nuremberg, Germany).



             reply	other threads:[~2010-02-12  8:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  8:54 Alan Mackenzie [this message]
2010-02-12  8:50 ` [gentoo-user] New Gentoo system has become unstable and unusable - help, please! Alan McKinnon
2010-02-12  9:13   ` William Kenworthy
2010-02-12  9:46   ` Alan Mackenzie
2010-02-12  9:49     ` Helmut Jarausch
2010-02-12  9:56     ` Lewis Handy
2010-02-12  9:57     ` Daniel Wagener
2010-02-12 10:05     ` Roy Wright
2010-02-12 10:10     ` Roy Wright
2010-02-12 10:33     ` Alan McKinnon
2010-02-12 11:22   ` Alan Mackenzie
2010-02-12 12:43     ` [gentoo-user] Ramifications of memtest86 Alan Mackenzie
2010-02-12 12:43       ` Dale
2010-02-12 13:23         ` Alan Mackenzie
2010-02-12 14:27           ` Dale
2010-02-12 19:25             ` [gentoo-user] Ramifications of memtest86. Got it! Alan Mackenzie
2010-02-12 20:03               ` [gentoo-user] " Nikos Chantziaras
2010-02-12 23:27               ` [gentoo-user] " Dale
2010-02-13 17:43                 ` Alan Mackenzie
2010-02-13 22:46                   ` Volker Armin Hemmann
2010-02-14  0:08                   ` Dale
2010-02-14  0:13                     ` Volker Armin Hemmann
2010-02-14  5:46                   ` Alan McKinnon
2010-02-12 13:00       ` [gentoo-user] Ramifications of memtest86 Alan McKinnon
2010-02-12 12:56     ` [gentoo-user] New Gentoo system has become unstable and unusable - help, please! Volker Armin Hemmann
2010-02-12 19:20       ` Alan Mackenzie
2010-02-12 12:17 ` Mark Knecht
2010-02-12 12:33 ` Helmut Jarausch
2010-02-12 15:24   ` Paul Hartman
2010-02-12 16:35   ` Volker Armin Hemmann
2010-02-13  1:02     ` [gentoo-user] " walt
2010-02-13  1:10       ` Dale
2010-02-13  1:11       ` Volker Armin Hemmann

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=20100212085453.GA1207@muc.de \
    --to=acm@muc.de \
    --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