From: Jens Axboe <axboe@suse.de>
To: Dave Olien <dmo@osdl.org>
Cc: Daniel Phillips <phillips@arcor.de>,
Samium Gromoff <_deepfire@mail.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [2.5] DAC960
Date: Fri, 20 Sep 2002 08:20:13 +0200 [thread overview]
Message-ID: <20020920062013.GD3990@suse.de> (raw)
In-Reply-To: <20020919142505.B27767@acpi.pdx.osdl.net>
On Thu, Sep 19 2002, Dave Olien wrote:
>
> Daniel
>
> Here's my latest progress on my changes to the DAC960 driver.
>
> I spent Tuesday banging my head trying to figure out why data blocks
> written to disk to SOMETIMES were read back with DIFFERENT data.
> On wednesday, I changed from using Linux 2.5.34 to using Linux 2.5.36.
> My bad data problem went away with that change. There must have been
> an important change in the 2.5.36 BIO code.
Neither 2.5.35 nor 2.5.36 has any critical bio fixes, so I would look
into this a bit more if I were you. Only if you were using
bio_kmap_irq() would there be something to look for, but DAC960 is not.
That was 2.5.35. 2.5.36 just starts sizing bio_vec pools based on free
memory, no bug fixes. Likewise in the block layer, I'm not seeing
anything.
--
Jens Axboe
next prev parent reply other threads:[~2002-09-20 6:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 5:30 Samium Gromoff
2002-09-10 6:20 ` Jens Axboe
2002-09-10 16:16 ` Dave Olien
2002-09-15 4:21 ` Daniel Phillips
2002-09-15 13:19 ` Jens Axboe
2002-09-15 15:23 ` Daniel Phillips
2002-09-15 16:18 ` Daniel Phillips
2002-09-16 20:13 ` Dave Olien
2002-09-16 20:26 ` Daniel Phillips
2002-09-16 22:08 ` Dave Olien
2002-09-16 22:25 ` Dave Olien
2002-09-19 18:49 ` Dave Olien
2002-09-19 19:16 ` Daniel Phillips
2002-09-19 22:09 ` Dave Olien
2002-09-19 22:21 ` Daniel Phillips
2002-09-20 6:21 ` Jens Axboe
2002-09-20 21:32 ` Daniel Phillips
2002-09-19 21:25 ` Dave Olien
2002-09-20 6:20 ` Jens Axboe [this message]
2002-09-15 15:14 ` Alan Cox
2002-09-15 16:20 ` Daniel Phillips
2002-09-18 16:17 James Bottomley
2002-09-18 16:40 ` Daniel Phillips
2002-09-23 19:23 Dave Olien
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=20020920062013.GD3990@suse.de \
--to=axboe@suse.de \
--cc=_deepfire@mail.ru \
--cc=dmo@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
/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
Powered by JetHome