public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Folke Ashberg <folke@ashberg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: hpt366.c: wrong timings used since 2.6.8
Date: Sun, 29 Aug 2004 14:18:04 +0100	[thread overview]
Message-ID: <1093785484.27935.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20040826223617.GA4557@ashberg.de>

On Iau, 2004-08-26 at 23:36, Folke Ashberg wrote:
> I saw that hpt366.c got support for HPT372_N_ and its special timings, but
> that timings have been used for my HPT372_A_ and caused the Oops.

The change you suggest is definitely wrong and will cause disk
corruption on the 372N

> I did the following and now it works:

Please post the actual oops data and if you can the rid/did.  The 372N
is identified by two things - PCI ID _or_ RID/DID. Not all 372N cards
have the unique PCI ID.


      reply	other threads:[~2004-08-29 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 22:36 hpt366.c: wrong timings used since 2.6.8 Folke Ashberg
2004-08-29 13:18 ` Alan Cox [this message]

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=1093785484.27935.18.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=folke@ashberg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox