All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Andreas Arens <ari@goron.de>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] AMD IDE oops in current 2.4-ac
Date: Wed, 12 Feb 2003 19:49:12 +0000	[thread overview]
Message-ID: <20030212194912.GA24138@codemonkey.org.uk> (raw)
In-Reply-To: <20030212204815.A8782@www.goron.de>

On Wed, Feb 12, 2003 at 08:48:15PM +0100, Andreas Arens wrote:
 > Current 2.4.21-pre4-ac kernels oops in amd74xx.c with
 > certain chipsets due to a table order problem. The
 > problem is correctly detected by a BUG() in the pci probe
 > routine, which should trigger for all non-nforce chipsets.

If moving entries in the table caused a bug, adding new entries
could do the same too perhaps ? This sounds quite fragile
based on your description & diff.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2003-02-12 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 19:48 [PATCH] AMD IDE oops in current 2.4-ac Andreas Arens
2003-02-12 19:49 ` Dave Jones [this message]
2003-02-12 20:37   ` Andreas Arens
2003-02-12 22:55   ` Ruslan U. Zakirov

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=20030212194912.GA24138@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ari@goron.de \
    --cc=linux-kernel@vger.kernel.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 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.