public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Alan McKinnon <alan.mckinnon@gmail.com>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "Illegal instruction" error
Date: Mon, 11 Oct 2010 15:57:39 -0700	[thread overview]
Message-ID: <AANLkTikxovDNmFs0ToY+o43piis5-SRR0mu+DWX7PsTF@mail.gmail.com> (raw)
In-Reply-To: <201010120021.38829.alan.mckinnon@gmail.com>

On Mon, Oct 11, 2010 at 3:21 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> Apparently, though unproven, at 23:02 on Monday 11 October 2010, Mark Knecht
> did opine thusly:
>
>> On Mon, Oct 11, 2010 at 1:39 PM, Alan McKinnon <alan.mckinnon@gmail.com>
> wrote:
>> > Uh-oh.
>> >
>> > genlop started failing today with the mysterious error "Illegal
>> > instruction", and it's consistent - every time. That's all the message,
>> > nothing else:
>> >
>> > $ genlop -t portage
>> > Illegal instruction
>> >
>> > Now emerge dbus-glib fails similarly:
>> >
>> > /bin/sh: line 21:  1084 Illegal instruction     /usr/bin/gtkdoc-rebase --
>> > relative --dest-dir=/var/tmp/portage/dev-libs/dbus-glib-0.88/image/
>> > --html- dir=${installdir}
>> >
>> >
>> > I don't really know where to start looking.....
>> > I just know Google is going to give me millions of useless hits with that
>> > search, but I'll hope over to b.g.o. meanwhile and poke around unless
>> > someone else has a better idea.
>>
>> Alan,
>>    Consider (if possible - is this a desktop or some in service
>> server?) powering down your machine, reseating your memory DIMMs,
>> powering back up and if possible running memtest86 (assuming it's an
>> x86 machine) and then seeing if the error goes away.
>>
>>    I've run into this a couple of times when memory problems have appeared.
>
>
> Yes, that was it - memtest failed almost immediately. It's my notebook, with
> 2 x 2G memory banks - either one in either position works fine. With both,
> memtest fails and always at the same place - step 48 of whatever.
>
> So I guess it's the motherboard and I'll be calling Dell Support in the
> morning. Am I glad the company insists we buy 3 year next-day on-site
> corporate support for all hardware right now? You betcha!
>

Not glad for the problem but glad I could help.

Best wishes getting it fixed fast and back on your lap.

Cheers,
Mark



  reply	other threads:[~2010-10-11 22:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 20:39 [gentoo-user] "Illegal instruction" error Alan McKinnon
2010-10-11 21:02 ` Mark Knecht
2010-10-11 22:21   ` Alan McKinnon
2010-10-11 22:57     ` Mark Knecht [this message]
2010-10-11 21:24 ` Daniel Pielmeier
2010-10-11 22:26   ` Alan McKinnon
2010-10-11 22:40     ` Daniel Pielmeier
2010-10-11 22:58       ` Alan McKinnon
2010-10-11 23:08         ` Dale
2010-10-11 23:53           ` Alan McKinnon
2010-10-12  6:29             ` Daniel Pielmeier
2010-10-11 23:06     ` Iain Buchanan

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=AANLkTikxovDNmFs0ToY+o43piis5-SRR0mu+DWX7PsTF@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=alan.mckinnon@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