From: Tejun Heo <htejun@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-ide@vger.kernel.org
Subject: Re: [2.6.23-rc3] Regression: "spurious completions during NCQ"
Date: Tue, 14 Aug 2007 19:11:17 +0900 [thread overview]
Message-ID: <46C17FC5.8090605@gmail.com> (raw)
In-Reply-To: <200708132005.14697.elendil@planet.nl>
Frans Pop wrote:
> Hi,
>
> I've been running 2.6.23-rc2 without problems. Today I compiled 2.6.23-rc3
> and shortly after boot got the following messages in my logs:
>
> kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x7ffc7 FIS=005040a1:00000020
> kernel: ata1.00: cmd 61/30:00:73:96:db/00:00:04:00:00/40 tag 0 cdb 0x0 data 24576 out
> kernel: res 50/00:08:7b:97:db/00:00:04:00:00/40 Emask 0x2 (HSM violation)
> [...]
> kernel: ata1: soft resetting port
> kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> kernel: ata1.00: configured for UDMA/133
> kernel: ata1: EH complete
> kernel: sd 0:0:0:0: [sda] 321672960 512-byte hardware sectors (164697 MB)
> kernel: sd 0:0:0:0: [sda] Write Protect is off
> kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>
> A grep in the logs shows that the first error has never occurred before.
> I was doing nothing special at the time (SVN checkout, not even running X).
>
> Full kern.log for that boot and lsmod attached.
> My system is Debian unstable with 2.6.23 built from Linus' git tree.
How reproducible is the problem?
--
tejun
next prev parent reply other threads:[~2007-08-14 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 18:05 [2.6.23-rc3] Regression: "spurious completions during NCQ" Frans Pop
2007-08-14 10:11 ` Tejun Heo [this message]
2007-08-15 7:21 ` Frans Pop
2007-08-15 7:32 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-09-22 13:11 Carsten Otto
2007-10-04 16:16 ` Carsten Otto
2007-10-24 10:18 ` Tejun Heo
2007-10-28 20:53 ` Carsten Otto
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=46C17FC5.8090605@gmail.com \
--to=htejun@gmail.com \
--cc=elendil@planet.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.