public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: ssd@nevets.oau.org (Steven S. Dick)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11 (pre1, final) OOPS during boot/modprobe
Date: Sat, 25 Nov 2000 23:05:13 +1100	[thread overview]
Message-ID: <6809.975153913@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 25 Nov 2000 06:10:54 CDT." <m13zdEM-000QAFC@nevets.oau.org>

On Sat, 25 Nov 2000 06:10:54 -0500 (EST), 
ssd@nevets.oau.org (Steven S. Dick) wrote:
>2.4.0-test11-pre1 seems to have broken something.
>I have no problems with test10, but test11-pre1 gives three oops
>messages during boot.  test11-final gives the exact same OOPS messages...

Which modutils?  And if it is not 2.3.21, upgrade.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-25 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-25 11:10 2.4.0-test11 (pre1, final) OOPS during boot/modprobe Steven S. Dick
2000-11-25 12:05 ` Keith Owens [this message]
2000-11-25 12:27   ` Russell King
2000-11-25 12:36     ` Keith Owens
2000-11-25 16:21     ` Steven S. Dick
2000-11-25 17:03       ` Keith Owens

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=6809.975153913@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssd@nevets.oau.org \
    /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