From: Tejun Heo <htejun@gmail.com>
To: aalderd.boac@wanadoo.nl
Cc: linux-ide@vger.kernel.org
Subject: Re: Seagate SATA 3GB/s drive connected to via vt8251 using ahci module
Date: Tue, 20 Jun 2006 02:18:19 +0900 [thread overview]
Message-ID: <4496DC5B.6040100@gmail.com> (raw)
In-Reply-To: <1150737053.4220.7.camel@anja>
Aalderd Bouwman wrote:
> Hm, I only have seen spurious interrupts when I have executed fdisk:
>
> Now doing fdisk /dev/sda or mke2fs /dev/sda1:
> Kernel log:
> Jun 8 18:52:19 server ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x2)
Can you double check the patch is actually applied. irq_stat 0x8 is
PORT_IRQ_SDB_FIS and if the patch were applied, it should have printed a
message starting with 'spurious SDB FIS...'
> Jun 8 18:53:09 server ata1.00: qc timeout (cmd 0x2f)
> Jun 8 18:53:09 server ata1: failed to read log page 10h (errno=-5)
> Jun 8 18:53:09 server ata1.00: exception Emask 0x1 SAct 0x7fffffff SErr 0x0 action 0x2 frozen
> Jun 8 18:53:09 server ata1.00: (irq_stat 0x40000000)
>
> Now I am unable to do fdisk because the drive is taken offline:
The patch only adds some debug messages such that the problem can be
analyzed better - it doesn't fix anything.
--
tejun
next prev parent reply other threads:[~2006-06-19 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 17:30 Seagate SATA 3GB/s drive connected to via vt8251 using ahci module Aalderd Bouwman
2006-06-09 5:44 ` Tejun Heo
2006-06-12 10:42 ` Aalderd Bouwman
2006-06-12 10:51 ` Tejun Heo
2006-06-12 11:24 ` Aalderd Bouwman
2006-06-18 2:56 ` Tejun Heo
2006-06-19 17:10 ` Aalderd Bouwman
2006-06-19 17:18 ` Tejun Heo [this message]
[not found] ` <1150745738.4302.1.camel@anja>
[not found] ` <20060620023312.GA1250@htj.dyndns.org>
2006-06-20 15:21 ` Aalderd Bouwman
2006-06-20 15:37 ` Tejun Heo
2006-06-20 19:31 ` Bastiaan Jacques
2006-06-21 7:25 ` Aalderd Bouwman
2006-06-21 14:12 ` [PATCH] ahci: disable NCQ support on vt8251 Tejun Heo
2006-06-23 3:22 ` Jeff Garzik
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=4496DC5B.6040100@gmail.com \
--to=htejun@gmail.com \
--cc=aalderd.boac@wanadoo.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.