From: Ralf Baechle <ralf@oss.sgi.com>
To: George Gensure <werkt@csh.rit.edu>
Cc: linux-mips@oss.sgi.com
Subject: Re: oops after rtc
Date: Fri, 7 Sep 2001 03:43:45 +0200 [thread overview]
Message-ID: <20010907034345.A16052@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.SOL.4.31.0109062054550.12489-100000@fury.csh.rit.edu>; from werkt@csh.rit.edu on Thu, Sep 06, 2001 at 08:56:22PM -0400
On Thu, Sep 06, 2001 at 08:56:22PM -0400, George Gensure wrote:
> sorry, latest cvs off of oss + fast_sysmips + entry.S patches (entry.S is
> supposed to fix some build segfaults) indy r5000, and I haven't decoded
> the oops message yet... (currently away from machine)
I'm quite certain that this isn't a RTC related oops. I've got the
same machine and for me the kernel is locking up when remounting the root
r/w. I'm looking into the issue but don't hold your breath, so much
to do ...
Ralf
prev parent reply other threads:[~2001-09-07 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 0:15 oops after rtc George Gensure
2001-09-07 0:15 ` George Gensure
2001-09-07 0:46 ` Ralf Baechle
2001-09-07 0:56 ` George Gensure
2001-09-07 0:56 ` George Gensure
2001-09-07 1:43 ` Ralf Baechle [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=20010907034345.A16052@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=werkt@csh.rit.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