From: Martin Dalecki <dalecki@evision-ventures.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Andre Hedrick <andre@linux-ide.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linux-2.5.7.fix2.patch
Date: Wed, 27 Mar 2002 17:40:13 +0100 [thread overview]
Message-ID: <3CA1F5ED.2060203@evision-ventures.com> (raw)
In-Reply-To: <5.1.0.14.2.20020327154219.05069c30@pop.cus.cam.ac.uk>
Anton Altaparmakov wrote:
> 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.
I can see the same. This is due to the hossed timeout handling
and choose_drive in the current state. If I can finally find
it, please expect me to release the next slew of patches.
> 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?
Could you tell me whatever the problematic interface is
maybe sharing the IRQ between two IDE channels?
If not. Could you test out whatever the problem remains if
you set the unmask IRQ flag with hdparm?
next prev parent reply other threads:[~2002-03-27 16: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 ` [PATCH] linux-2.5.7.fix2.patch Anton Altaparmakov
2002-03-27 16:40 ` Martin Dalecki [this message]
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=3CA1F5ED.2060203@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=aia21@cam.ac.uk \
--cc=andre@linux-ide.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