mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Segaud <matt@minas-morgul.org>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: [OT] Re: 2.6.10 xfs segfault on boot startup?
Date: Mon, 27 Dec 2004 16:37:00 +0100	[thread overview]
Message-ID: <87wtv392hv.fsf@barad-dur.crans.org> (raw)
In-Reply-To: <200412241942.36264.gene.heskett@verizon.net> (Gene Heskett's message of "Fri, 24 Dec 2004 19:42:36 -0500")

Gene Heskett <gene.heskett@verizon.net> disait dernièrement que :

> Greetings all;
>
> I just rebooted to a "still got that new car smell" fresh 2.6.10, and 
> this went by on the boot screen while it was starting the various 
> services in init.d:
>
> Starting xfs: /etc/rc3.d/S90xfs: line 137:  2377 Segmentation fault      
> ttmkfdir -d . -o fonts.scale
> /etc/rc3.d/S90xfs: line 137:  2404 Segmentation fault      ttmkfdir 
> -d . -o fonts.scale

it is a userland problem. seems like you have some garbage in your fonts dir.

>
> I had installed some new ttf fonts over the last day or so, and had 
> used them with the beta OOo-1.9-xxx before rebooting from 
> 2.6.10-V0.33-04, but when I did a 'service xfs restart' just before 
> seeing if startx worked (it did obviousy) no further errors were 
> output, and it was running when I did that, so its apparently not 
> repeatable.

I had this message when emerging xorg-x11 on my gentoo box. ttmkfdir does
not seem robust enough when upgrading fonts.

> But it was a bit puzzling.  Anybody have an idea?  Self-healing 
> software, the Holy Grail...
>
> Merry Christmas wishes to all that celebrate it on this list.

thx, merry xmas

-- 
if (!cost_analysis) goto darwinism;

	- Mike Galbraith explaining economics on linux-kernel


      parent reply	other threads:[~2004-12-27 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25  0:42 Gene Heskett
2004-12-25  0:50 ` Lee Revell
2004-12-25  2:14   ` Gene Heskett
2004-12-27 15:37 ` Mathieu Segaud [this message]

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=87wtv392hv.fsf@barad-dur.crans.org \
    --to=matt@minas-morgul.org \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®