From: Michael Ellerman <mpe@ellerman.id.au>
To: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Constant ata messages on console with commit 28361c403683 ("libata: add extra internal command") (was Re: [GIT PULL 2/2] libata changes for v4.18-rc1)
Date: Mon, 18 Jun 2018 17:33:57 +1000 [thread overview]
Message-ID: <87bmc8a6qi.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180605191525.GF1351649@devbig577.frc2.facebook.com>
Tejun Heo <tj@kernel.org> writes:
...
> Jens Axboe (10):
> libata: introduce notion of separate hardware tags
> libata: convert core and drivers to ->hw_tag usage
> libata: bump ->qc_active to a 64-bit type
> libata: use ata_tag_internal() consistently
> libata: remove assumption that ATA_MAX_QUEUE - 1 is the max
> sata_nv: set host can_queue count appropriately
> libata: add extra internal command
Replying here because I can't find the original mail.
The above commit is causing one of my machines to constantly spew ata
messages on the console, according to bisect:
# first bad commit: [28361c403683c2b00d4f5e76045f3ccd299bf99d] libata: add extra internal command
To get it to boot I have to also apply:
88e10092f6a6 ("sata_fsl: use the right type for tag bitshift")
The system boots OK and seems fine, except that it's just printing
multiple of these per second:
ata2: Signature Update detected @ 0 msecs
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/100
ata2: Signature Update detected @ 0 msecs
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/100
ata2: Signature Update detected @ 0 msecs
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/100
ata2: Signature Update detected @ 0 msecs
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/100
ata2: Signature Update detected @ 0 msecs
And it never seems to stop.
The machine is a Freescale/NXP P5020ds, using the sata_fsl driver
presumably. Any ideas?
cheers
next prev parent reply other threads:[~2018-06-18 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 19:08 [GIT PULL 1/2] libata changes for v4.18-rc1 Tejun Heo
2018-06-05 19:15 ` [GIT PULL 2/2] " Tejun Heo
2018-06-18 7:33 ` Michael Ellerman [this message]
2018-06-18 14:33 ` Constant ata messages on console with commit 28361c403683 ("libata: add extra internal command") (was Re: [GIT PULL 2/2] libata changes for v4.18-rc1) Jens Axboe
2018-06-19 7:29 ` Michael Ellerman
2018-06-19 15:26 ` Jens Axboe
2018-06-19 15:39 ` Jens Axboe
2018-06-19 23:35 ` Michael Ellerman
2018-06-19 23:38 ` Jens Axboe
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=87bmc8a6qi.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=axboe@kernel.dk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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).