From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Brad Campbell <brad@wasp.net.au>
Cc: Jeff Garzik <jgarzik@pobox.com>,
David Howells <dhowells@redhat.com>,
linux-ide@vger.kernel.org
Subject: Re: Fun with HPT302N (Rocket Raid 1520 PCI card)
Date: Thu, 02 Nov 2006 16:24:15 +0000 [thread overview]
Message-ID: <1162484655.11965.212.camel@localhost.localdomain> (raw)
In-Reply-To: <4548927F.10804@wasp.net.au>
Ar Mer, 2006-11-01 am 16:26 +0400, ysgrifennodd Brad Campbell:
> Here is a complete dmesg from a Rocketraid 1540 (htp37x with bridges) if it helps.
> (4 ports, 3 have drives and the 4th exhibits the failure David is seeing)
>
> http://www.nabble.com/2.6.19-rc3-pata_hpt37x-dying-with-%22irq-16:-nobody-cared%22-t2504272.html
>
> I still have this in a machine dedicated for testing if you need more info.
That one is really very useful. The error handling is leaving some kind
of IRQ status no cleared which in turn brings the house down. I think
there are two different things in the log here - one is the empty port,
the other is some kind of other failure.
With a current -mm kernel can you stick ATA_FLAG_DETECT_POLLING on the
various .flags = ATA_FLAG_SLAVE_POSS|.... lines for each ata_port_info
structure in hpt37x_init_one then see if the identify behaviour is
happier.
That recipe is probably what we need to do for all the PATA chips that
don't have reliable device presence bits.
Alan
next prev parent reply other threads:[~2006-11-02 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 10:04 Fun with HPT302N (Rocket Raid 1520 PCI card) David Howells
2006-11-01 9:32 ` Jeff Garzik
2006-11-01 12:17 ` Alan Cox
2006-11-01 12:26 ` Brad Campbell
2006-11-02 16:24 ` Alan Cox [this message]
2006-11-03 9:19 ` Brad Campbell
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=1162484655.11965.212.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=brad@wasp.net.au \
--cc=dhowells@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).