From: Olaf Hering <olh@suse.de>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MESH not found with 2.4.1 on 7500
Date: Wed, 7 Feb 2001 09:49:54 +0100 [thread overview]
Message-ID: <20010207094954.A10127@suse.de> (raw)
In-Reply-To: <20010207011911.1fa55761.toe@unlserve.unl.edu>; from toe@unlserve.unl.edu on Wed, Feb 07, 2001 at 01:19:11AM -0600
On Wed, Feb 07, Takashi Oe wrote:
> On Wed, 7 Feb 2001 07:54:04 +0100, Olaf Hering <olh@suse.de> wrote:
>
> > On Tue, Feb 06, Takashi Oe wrote:
> > > message output, you should have something like:
> > >
> > > SCSI subsystem driver Revision: 1.00
>
> The SCSI message is missing once again from your dmesg. If you are
> absolutely sure your kernel is built with SCSI support, do "make
> distclean" and try again. If the SCSI subsystem message is still missing,
> attach your .config file along with dmesg. You are working with bk tree,
> right? In any case, can't you at least find out where the machine check
> is happening?
It happens with CONFIG_RTC, but appearently only on this 7500/100.
Wallstreet, beige G3 (unverified) and every newworld can have this
option enabled.
CONFIG_RTC is currently a bit useless on pmac so its safe to disable it.
CONFIG_PPC_RTC does the job.
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-07 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 16:37 MESH not found with 2.4.1 on 7500 Olaf Hering
2001-02-06 17:21 ` Takashi Oe
2001-02-07 6:54 ` Olaf Hering
2001-02-07 7:19 ` Takashi Oe
2001-02-07 8:49 ` Olaf Hering [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-08 17:59 Vincent Favre-Nicolin
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=20010207094954.A10127@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.