All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: CaT <cat@zip.com.au>
Cc: torvalds@osdl.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: PDC20267 bug and corruption (was: Re: [BK PATCHES] ide-2.6 update)
Date: Sat, 30 Oct 2004 20:06:11 +0200	[thread overview]
Message-ID: <58cb370e04103011065c265ce4@mail.gmail.com> (raw)
In-Reply-To: <20041030034745.GA1287@zip.com.au>

On Sat, 30 Oct 2004 13:47:45 +1000, CaT <cat@zip.com.au> wrote:
> On Wed, Oct 27, 2004 at 03:51:14PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > http://bugme.osdl.org/show_bug.cgi?id=2494
> 
> Tried it via bk7, wasn't it.
> 
> Looks like I have found a bug relating to the pdc driver though.
> 
> The situation is such: I have 2 HDs connected to a PDC20267 PCI card,
> one on each channel, with a master on the primary channel and a slave on
> the secondry channel. Accessing each drive individually causes no
> problems at all but accessing them simultaneously (like copying data off
> one drive onto the other) causes the IDE layer to go to hell in a hand
> basket. I can duplicate this each and every time by doing the following:
> 
> 1. copying a few gig from hde to hdh
> 2. dd if=/dev/hde of=/dev/null
>    dd if=/dev/zero of=/dev/hdh
> 
> With method #1 I get the following:
> 
> Oct 27 00:37:39 nessie kernel: attempt to access beyond end of device
> Oct 27 00:37:39 nessie kernel: hdh1: rw=1, want=3034756264, limit=390716802
> Oct 27 00:37:40 nessie kernel: Aborting journal on device hdh1.
> Oct 27 00:37:40 nessie kernel: ext3_abort called.
> Oct 27 00:37:40 nessie kernel: EXT3-fs error (device hdh1): ext3_journal_start: Detected aborted journal
> Oct 27 00:37:40 nessie kernel: Remounting filesystem read-only
> Oct 27 00:37:40 nessie kernel: EXT3-fs error (device hdh1) in start_transaction: Journal has aborted

This comes from the block layer, generic_make_request(),
request is screwed up before it hits IDE layer.

> With method #2, a whole lot more fun occurs. The logfile I have is big
> (almost 400k) so I've compressed it and included it as an attachment.
> This is with kernel 2.6.10-rc1-bk7 (no logs survived from me testing
> this with rc1-mm2).

Indeed, this is a lot more fun. ;)

Is this bug new/old?

Is it pdc202xx_old specific?  Does the same havoc happen
if you connect drives to the on-board Intel IDE controller?

Please post /proc identify data for both drives and PCI config
space dump for PDC20267 so someone can verify them.

  reply	other threads:[~2004-10-30 18:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 13:07 [BK PATCHES] ide-2.6 update Bartlomiej Zolnierkiewicz
2004-10-27 13:34 ` CaT
2004-10-27 13:51   ` Bartlomiej Zolnierkiewicz
2004-10-27 14:33     ` Mikael Pettersson
2004-10-27 14:49       ` Bartlomiej Zolnierkiewicz
2004-10-30  3:47     ` PDC20267 bug and corruption (was: Re: [BK PATCHES] ide-2.6 update) CaT
2004-10-30 18:06       ` Bartlomiej Zolnierkiewicz [this message]
2004-10-30 23:48         ` CaT
2004-10-27 14:29 ` [BK PATCHES] ide-2.6 update J.A. Magallon
2004-10-27 15:07   ` Bartlomiej Zolnierkiewicz
2004-10-27 16:15 ` Gene Heskett
2004-10-27 16:22   ` Bartlomiej Zolnierkiewicz
2004-10-27 17:05     ` Gene Heskett
2004-10-27 17:02       ` Randy.Dunlap
2004-10-27 18:17         ` Gene Heskett
2004-10-27 17:15       ` Bartlomiej Zolnierkiewicz
2004-10-27 18:19         ` Gene Heskett
2004-10-27 17:20       ` Linus Torvalds
2004-10-27 18:26         ` Gene Heskett
2004-10-27 18:41           ` Linus Torvalds
2004-10-27 19:03             ` Gene Heskett
2004-10-28  6:45         ` Gene Heskett

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=58cb370e04103011065c265ce4@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=cat@zip.com.au \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.