public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Gyes <floam@sh.nu>
To: Jon Escombe <lists@dresco.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATA warnings in dmesg
Date: Tue, 18 Oct 2005 06:31:37 -0700	[thread overview]
Message-ID: <1129642297.12659.3.camel@localhost> (raw)
In-Reply-To: <4354A09C.8010202@dresco.co.uk>

On Tue, 2005-10-18 at 08:13 +0100, Jon Escombe wrote:
> I don't think you need to worry. Those messages are produced from the 
> libata passthough code, whenever sense data has been requested...
> 
> 0xb0 looks like a SMART command, so I would guess (haven't looked at 
> -mm) that the ata ioctl handlers have been updated to request it.

That would make sense. I have a daemon running that requests the
temperature via SMART every minute or so. Even still, this fills up my
entire dmesg after not a very long time, can I turn these messages off
somehow? If not, can you point me to where in the code I could kill a
printk?

Aaron Gyes


  reply	other threads:[~2005-10-18 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  4:33 ATA warnings in dmesg Aaron Gyes
2005-10-18  7:13 ` Jon Escombe
2005-10-18 13:31   ` Aaron Gyes [this message]
2005-10-18 20:43     ` Jon Escombe

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=1129642297.12659.3.camel@localhost \
    --to=floam@sh.nu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@dresco.co.uk \
    /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