From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SuperMicro P6DGU
Date: Wed, 10 Nov 2004 13:48:17 +0000 [thread overview]
Message-ID: <8b46cc686faa291fa66ad80de397dd8d@vitanuova.com> (raw)
In-Reply-To: <48fa91a91dec3951895c5ab89a975502@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 154 bytes --]
i'd have said that was an old bug fixed by adding fpclear to l.s and main.c
and that kernel is somehow out of date, unless there's a new manifestation.
[-- Attachment #2: Type: message/rfc822, Size: 2947 bytes --]
From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SuperMicro P6DGU
Date: Wed, 10 Nov 2004 13:02:26 0000
Message-ID: <48fa91a91dec3951895c5ab89a975502@quintile.net>
Ok,
I understand a bit better now, I now have had 3 panics
and two of them where prevoked. Both these times I just rebooted
without halting - very early, just as fossil was comming up.
Both times I got an fp overflow and a panic, when I rebooted
again afterwards the system came up cleanly.
panic (fp overflow) fppc=0x22aab status=0x80c1 pc=0x00022aa9
The problem seems to occur after fossil has checked a dirty filesystem.
0x22aa9 in fossil relates to /sys/src/libc/386/vlrt.c:105 which is _v2d().
Suffice to say my box seems happy now, I have one unexplained crash but
I would be happy to put that down to a mains dropout.
The above info might help somone else if this bites more severely.
-Steve
next prev parent reply other threads:[~2004-11-10 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 13:02 Steve Simon
2004-11-10 13:48 ` C H Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-08 6:32 Steve Simon
2004-11-09 1:54 ` Jim McKie
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=8b46cc686faa291fa66ad80de397dd8d@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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).