From: Mark Lord <liml@rtr.ca>
To: Eamonn Hamilton <EAMONN.HAMILTON@saic.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: problems with sata_nv and MV88SX5081 under 2.6.28, fine under2.6.17.6
Date: Fri, 09 Jan 2009 14:46:11 -0500 [thread overview]
Message-ID: <4967A983.7040402@rtr.ca> (raw)
In-Reply-To: <1231340005.20422.84.camel@ukabzc383.uk.saic.com>
Eamonn Hamilton wrote:
> Hi,
>
> I look after a server with a bunch of drives hooked up to two 8 port
> PCI-X sata cards, detected as above.
>
> The server was running 2.6.17.6 which has sata_mv version 0.7, which
> worked fine. I recently upgraded the kernel to 2.6.18 with version 1.24,
> and started getting
>
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
>
> for several of the disks, and performance went through the floor because
> of multiple bus resets. Now, the system was running SMART monitoring,
> and in the course of some googling it was suggested that this perhaps
> was causing a timeout, however disabling the smartd made no difference.
>
> Reverting to 2.6.17.6 made the problem go away, suggesting something
> between 0.7 and 1.24 is causing some difficulty.
..
Yeah, there are vaguely similar reports from som of the 88SX6081 users as well.
I think the restructuring of the reset/probe code last year, to share more
of the libata core/sff stuff, probably messes up the older chipsets like those.
I'm looking into now, so please copy me on any extra postings on this topic.
Eamonn, are you available to test updates early, before they go upstream?
Thanks.
Mark
next prev parent reply other threads:[~2009-01-09 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 14:53 problems with sata_nv and MV88SX5081 under 2.6.28, fine under2.6.17.6 Eamonn Hamilton
2009-01-07 15:45 ` Alan Cox
2009-01-07 15:46 ` Eamonn Hamilton
2009-01-08 3:13 ` Robert Hancock
2009-01-08 10:51 ` problems with sata_nv and MV88SX5081 under 2.6.28, fineunder2.6.17.6 Eamonn Hamilton
2009-01-09 19:46 ` Mark Lord [this message]
[not found] ` <496B9130.2000708@pobox.com>
[not found] ` <D1CE94B2C9BA8C42AC5C7BBCD82D5DAE672F13@0602-its-exmb01.eu.saic.com>
[not found] ` <496BA7C5.2020802@pobox.com>
[not found] ` <D1CE94B2C9BA8C42AC5C7BBCD82D5DAE672F14@0602-its-exmb01.eu.saic.com>
[not found] ` <496BAA1F.5030802@pobox.com>
2009-01-13 17:01 ` problems with sata_nv and MV88SX5081 under 2.6.28, fine under2.6.17.6 Eamonn Hamilton
2009-01-13 19:27 ` problems with sata_mv and MV88SX5081 under 2.6.28, fine under 2.6.17.6 Mark Lord
2009-01-15 19:37 ` Mark Lord
2009-01-16 10:52 ` Eamonn Hamilton
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=4967A983.7040402@rtr.ca \
--to=liml@rtr.ca \
--cc=EAMONN.HAMILTON@saic.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).