From: Florian Lohoff <flo@rfc822.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Kernel Oops when booting on DECstation
Date: Mon, 18 Dec 2000 12:07:14 +0100 [thread overview]
Message-ID: <20001218120714.C401@paradigm.rfc822.org> (raw)
In-Reply-To: <20001216085603.A514@sumpf.cyrius.com>; from tbm@cyrius.com on Sat, Dec 16, 2000 at 08:56:03AM +0100
On Sat, Dec 16, 2000 at 08:56:03AM +0100, Martin Michlmayr wrote:
> Linux version 2.4.0-test8-pre1 (flo@slimer.rfc822.org) (gcc version egcs-2.90.20
[...]
> Any ideas? (I hope and think that it has nothing to do with me
> booting from a NetBSD partition. I don't have ethernet on the machine
> and thus have to boot the kernel from the existing FFS partition in
> order to start Linux and then run delo. NetBSD boots and works, btw.)
I have the suspicion that you are running into a bug Harald and me
solved when booting my /150 from Disk. It seems the Firmware KN04 V2.1k
doesnt correctly reset/disable the SCSI Controller and the Ethernet
chip causing the system to crash immediatly in the "request_irq" section.
I guess the backtrace is bogus but i might be wrong. I would recommend
trying to compile a current cvs kernel yourself and retry.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2000-12-18 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 7:56 Kernel Oops when booting on DECstation Martin Michlmayr
2000-12-16 10:20 ` Karel van Houten
2000-12-16 10:20 ` Karel van Houten
2000-12-16 11:19 ` Keith Owens
2000-12-16 15:00 ` Martin Michlmayr
2000-12-16 15:09 ` Keith Owens
2000-12-17 20:23 ` Martin Michlmayr
2000-12-18 18:48 ` Jun Sun
2000-12-18 11:07 ` Florian Lohoff [this message]
2000-12-19 12:48 ` Martin Michlmayr
2000-12-19 17:03 ` Harald Koerfgen
2000-12-19 17:09 ` Karel van Houten
2000-12-19 17:09 ` Karel van Houten
2000-12-22 10:44 ` Maciej W. Rozycki
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=20001218120714.C401@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=tbm@cyrius.com \
/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.