From: Jens Axboe <axboe@suse.de>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: [PATCH] 2.4 IDE core for 2.5, #2 (was Re: [PATCH] 2.4 IDE core for 2.5)
Date: Wed, 10 Jul 2002 13:11:15 +0200 [thread overview]
Message-ID: <20020710111115.GJ3185@suse.de> (raw)
In-Reply-To: <20020710054356.GE3185@suse.de>
On Wed, Jul 10 2002, Jens Axboe wrote:
> > This afternoon I booted 2.5.25 with your patches and two more,
> > one to prevent an oops when shutting down, the other to fix
> > ethernet cards detection. Started torturing two disks on
> > HPT366. After 3 minutes
> >
> > hde: status error: status=0x50 { DriveReady SeekComplete }
> > hde: no DRQ after issuing WRITE
> >
> > and seven minutes later
> >
> > hde: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
> > hde: task_out_intr: error=0x04 { DriveStatusError }
> >
> > Soon lots of processes were hanging in D. Reboot. e2fsck.
>
> The above seems to be plain pio, you didn't use multi mode did you? I
> think my current tree has the multi-page multi mode bio issue resolved,
> however I'll test for some hours before sending out the next patch set.
Care to try the next version? I've completely disabled task file i/o
since it does seem to be broken in pio, and fixed the multi-write
multi-page bio bug as well. There are a number of other changes in
there. There are split patches like last time, but also one big patch:
*.kernel.org/pub/linux/kernel/people/axboe/patches/v2.5/2.5.25/
00_25ide-compile-1a
no changes, rediffed
05_25pci-ids-1a
no changes, rediffed
10_24ide-core-2
various fixes, see old/ for the complete list
15_24-misc-bits-2
added (broken) sparc64 bits. too lazy to revert these right,
waiting for update
20_ide-build-config-1a
consolidate config and build split
25_ide-scsi-1
no changes, rediffed
and finally,
ide24-for-2.5-2
all of the above
Also pull'able from bk://linux25-24ide@project.bkbits.net/linux25-24ide
(soonish)
--
Jens Axboe
next prev parent reply other threads:[~2002-07-10 11:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 10:22 [PATCH] 2.4 IDE core for 2.5 Jens Axboe
2002-07-09 10:48 ` Anton Altaparmakov
2002-07-09 10:49 ` Jens Axboe
2002-07-09 10:51 ` Vojtech Pavlik
2002-07-09 10:53 ` Jens Axboe
2002-07-09 11:17 ` Jens Axboe
2002-07-09 12:52 ` Bartlomiej Zolnierkiewicz
2002-07-09 12:56 ` Jens Axboe
2002-07-09 13:13 ` Bartlomiej Zolnierkiewicz
[not found] ` <Pine.SOL.4.30.0207091510450.28198-100000@mion.elka.pw.edu.pl>
2002-07-09 13:16 ` Jens Axboe
2002-07-09 11:11 ` Erik Andersen
2002-07-09 11:13 ` Roy Sigurd Karlsbakk
[not found] ` <200207091313.07199.roy@karlsbakk.net>
2002-07-09 11:20 ` Jens Axboe
2002-07-09 21:43 ` Miles Lane
2002-07-09 11:24 ` Thunder from the hill
2002-07-09 12:43 ` Tobias Rittweiler
2002-07-09 12:48 ` Jens Axboe
2002-07-09 12:54 ` Jens Axboe
2002-07-09 13:31 ` Re[3]: " Tobias Rittweiler
[not found] ` <20020709124827.GA1940@suse.de>
2002-07-09 12:57 ` Re[2]: " Tobias Rittweiler
2002-07-09 20:07 ` Andries Brouwer
2002-07-10 5:43 ` Jens Axboe
2002-07-10 11:11 ` Jens Axboe [this message]
2002-07-12 11:06 ` [PATCH] 2.4 IDE core for 2.5, #2 (was Re: [PATCH] 2.4 IDE core for 2.5) Andries Brouwer
2002-07-12 11:23 ` IDE Anders Widman
2002-07-11 9:54 ` [PATCH] 2.4 IDE core for 2.5 Rogier Wolff
2002-07-11 9:56 ` Jens Axboe
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=20020710111115.GJ3185@suse.de \
--to=axboe@suse.de \
--cc=aebr@win.tue.nl \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).