From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org,
Martin Dalecki <dalecki@evision-ventures.com>
Subject: Re: [PATCH] linux-2.5.7.fix2.patch
Date: Wed, 27 Mar 2002 15:46:44 +0000 [thread overview]
Message-ID: <5.1.0.14.2.20020327154219.05069c30@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10203231441530.1053-200000@master.linux-ide. org>
Hi Andre,
I tried this patch on my laptop to see if it would make my atapi cdrom data
underrun problems go away.
Unfortunately booting 2.5.7 + your patch causes hda: lost interrupt
messages to appear. It still manages to progress through the boot scripts
ok for a while, albeit very, very slowly, but eventually after several lost
interrupt messages the kernel crashes.
Vanilla 2.5.7 boots fine but the cdrom doesn't work due to the data/buffer
underruns...
I am quite happy to help debug this, let me know what info you would like
to see... Can I enable debugging somewhere to get more interesting messages
or should I try anything?
Cheers,
Anton
At 22:53 23/03/02, Andre Hedrick wrote:
>Martin et al.
>
>This is the next step in stablizing the transport layer.
>I have not booted but it will compile, and it is nearly identical to what
>I generated for 2.4 to be released soon.
>
>The comments are harsh on the interface but it functionally correct.
>If you get an device error in PIO, bad things can happen to the data.
>This is no different in the stock 2.4.0->2.4.18->19x.
>
>Of of all the transport data handlers.
>
>CLEAN and SAFE:
> DMA read/write is safe and has always been.
> Single sector PIO WRITING is clean and safe.
>
>DIRTY but operational (error events in the hardware will cause data problems)
> Single sector PIO READING can corrupt a single sector if there
> is a device error.
> Multi-Read/Write will corrupt and misreport data only on an error.
>
>What is still lacking in block is the much needed in proccess bio walker.
>Once I can finish coding this fix into BLOCK, then I can complete the
>transport layer and slap it on a bus analyzer and force articial errors on
>the buss to see if the driver behaves correctly. If this passes, we are
>good to run like the wind.
>
>Regards,
>
>Andre Hedrick
>LAD Storage Consulting Group
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next parent reply other threads:[~2002-03-27 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10203231441530.1053-200000@master.linux-ide. org>
2002-03-27 15:46 ` Anton Altaparmakov [this message]
2002-03-27 16:40 ` Martin Dalecki
2002-03-27 20:06 ` Andre Hedrick
2002-03-23 22:53 Andre Hedrick
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=5.1.0.14.2.20020327154219.05069c30@pop.cus.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=andre@linux-ide.org \
--cc=dalecki@evision-ventures.com \
--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
all inboxes | Powered by JetHome®