All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: root@chaos.analogic.com
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
	Matthew Allum <mallum@xblox.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Multiple kernels OOPS at boot on Fujitsu pt510 ( AMD DX100 CPU ) - ksymoops output attached
Date: 02 Mar 2002 04:53:23 +0100	[thread overview]
Message-ID: <m24rjzy6a4.fsf@anano.mitica> (raw)
In-Reply-To: <Pine.LNX.3.95.1020301123724.5515A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1020301123724.5515A-100000@chaos.analogic.com>

>>>>> "richard" == Richard B Johnson <root@chaos.analogic.com> writes:

Hi

richard> Once somebody makes a kernel they has both a working loop device and
richard> a working initial RAM Disk, I will use that kernel. In the meantime,
richard> I'm stuck at 2.4.1.

I am not sure what you are doing, and I don't remeber seing your
script to reproduce the problem, but I can confirm you that:
- loop device works
- initrd works

We used it for Mandrake kernels, and it works with SCSI without any
problems.  Could you send me your script to create the intrd to me to
take a look?

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  reply	other threads:[~2002-03-02 16:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 14:44 Multiple kernels OOPS at boot on Fujitsu pt510 ( AMD DX100 CPU ) - ksymoops output attached Matthew Allum
2002-03-01 14:54 ` Richard B. Johnson
2002-03-01 15:52   ` Zwane Mwaikambo
2002-03-01 17:50     ` Richard B. Johnson
2002-03-02  3:53       ` Juan Quintela [this message]
2002-03-01 17:36 ` Alan Cox
2002-03-01 18:25   ` Matthew Allum
  -- strict thread matches above, loose matches on Subject: below --
2002-03-01 18:12 Torrey Hoffman
2002-03-01 19:22 ` Richard B. Johnson
2002-03-01 20:04 Torrey Hoffman

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=m24rjzy6a4.fsf@anano.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mallum@xblox.net \
    --cc=root@chaos.analogic.com \
    --cc=zwane@linux.realnet.co.sz \
    /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.