From: Fionn Behrens <Fionn.Behrens@unix-ag.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP IRQ management issues in 2.4.x
Date: Fri, 22 Mar 2002 15:25:42 +0100 [thread overview]
Message-ID: <20020322152542.36250f11.fionn@unix-ag.org> (raw)
In-Reply-To: <E16oAlY-0006Qc-00@the-village.bc.nu>
On Thu, 21 Mar 2002 22:10:36 +0000 (GMT)
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > Mar 21 09:56:41 localhost kernel: hde: write_intr: status=0xd0 { Busy }
> > Mar 21 09:56:41 localhost kernel: ide2: reset: success
> > Mar 21 09:56:41 localhost kernel: hde: status error: status=0x58 {
> > DriveReady
> > SeekComplete DataRequest }
>
> That doesnt look like an interrupt problem to be honest. Perhaps nvdriver
> is triggering something else
>
> (the Busy is the drive saying its still waiting for something)
Just wanted to close the issue by saying it came out that it actually is NOT an IRQ problem.
Another close look at "hdparm -I" vs. "harparm -v" (and syslog) revealed that the hard disks had been configured for UDMA mode 5 by the controller (probably at boot time) while the Linux kernel set them to some IO mode.
Having found this out, I really wonder how the disks managed to work under any circumstances at all.
thanks for your hints and reading,
Fionn
--
I believe we have been called by history to lead the world.
G.W. Bush, 2002-03-01
next prev parent reply other threads:[~2002-03-22 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 13:57 Fionn Behrens
2002-03-21 14:31 ` Alan Cox
2002-03-21 21:38 ` Fionn Behrens
2002-03-21 22:10 ` Alan Cox
2002-03-22 14:25 ` Fionn Behrens [this message]
2002-03-22 15:11 ` Alan Cox
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=20020322152542.36250f11.fionn@unix-ag.org \
--to=fionn.behrens@unix-ag.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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®