From: James Ray <j.ray@qmul.ac.uk>
To: Tejun Heo <htejun@gmail.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: Bug? ahci.c
Date: Tue, 27 Feb 2007 15:56:05 +0000 [thread overview]
Message-ID: <45E45495.2020800@qmul.ac.uk> (raw)
In-Reply-To: <45E44C26.2010207@gmail.com>
Tejun Heo wrote:
> James Ray wrote:
>> Jeff, All,
>> We have just started using some new machines with The Intel ESB2
>> chipset in them (PCI Id: 8086:2681) for the SATA Controller.
>> With any kernels above 2.6.15 (as far as I can tell from my testing at
>> least) we are getting problems with them.
>>
>> This is the output I have managed to collect from the server (Its hard
>> to get much more since the system gets more and more unresponsive as
>> these errors progress):
>> <3>ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x80002 action 0x2 frozen
>> <3>ata2.00: (irq_stat 0x08000000, interface fatal error)
>> <3>ata2.00: tag 0 cmd 0x35 Emask 0x10 stat 0x50 err 0x0 (ATA bus error)
>> <6>ata2: soft resetting port
>> <3>ata2: softreset failed (1st FIS failed)
>> <4>ata2: softreset failed, retrying in 5 secs
>> <6>ata2: hard resetting port
>> <4>ata2: port is slow to respond, please be patient
>
> Can you test 2.6.20.1 and report full dmesg? Thanks.
>
I managed to get a response from Jeff on the linux-kernel list which I
have yet to respond to (sorry!).
This problem was fixed by dodgy NCQ on the disk itself, S/N:
WMANM2828677 P/N: WD1600JS-60MHB1 (Western Digital 160Gb). If I disabled
the disk it worked fine, or replaced the disks with Some Seagates it
worked fine also!
I am running a 2.6.19 at the moment quite happily. Still want me to test
a 2.6.20.1? I might be able to get a bit of time later on this week.
--
James Ray. <j.ray@qmul.ac.uk>
Computing Services
Queen Mary, University of London
next prev parent reply other threads:[~2007-02-27 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 12:21 Bug? ahci.c James Ray
2007-02-27 15:20 ` Tejun Heo
2007-02-27 15:56 ` James Ray [this message]
2007-02-27 16:05 ` Tejun Heo
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=45E45495.2020800@qmul.ac.uk \
--to=j.ray@qmul.ac.uk \
--cc=htejun@gmail.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).