From: Nicolas STRANSKY <Nico@stransky.cx>
To: linux-ide@vger.kernel.org
Subject: Re: libata-tj and SMART
Date: Wed, 17 May 2006 23:15:43 +0200 [thread overview]
Message-ID: <e4g3or$jbm$1@sea.gmane.org> (raw)
In-Reply-To: <4469893A.10901@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Le 05/16/2006 10:11 AM, Tejun Heo a écrit :
Hi,
> If you've got some time though, I'd like to see what's really going on.
> Can you modify #undef ATA_DEBUT to #define ATA_DEBUG in
> include/linux/libata.h and post the kernel messages after issuing above
> command? Be warned that it will produce a LOT of messages while booting
> if you're using SATA disks for your system, and it can considerably slow
> down booting.
Here it is.
I first did a "smartctl -d ata -a -o on /dev/sda" and then a "smartctl
-d ata -a -S on /dev/sda" which are the two commands triggering errors
on this drive with you patch.
BTW the system is running very well with your patch apart from this
smartctl problem.
Regards,
--
Nico
Peut-être découvrirons-nous un jour que la même logique est à l'oeuvre
dans la pensée mythique et dans la pensée scientifique, et que l'homme
a toujours pensé aussi bien.
-+- Claude Lévi-Strauss, Anthropologie structurale -+-
[-- Attachment #2: kern.log.bz2 --]
[-- Type: application/x-bzip, Size: 4550 bytes --]
next prev parent reply other threads:[~2006-05-17 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 22:41 libata-tj and SMART Nicolas STRANSKY
2006-05-15 23:13 ` Tejun Heo
2006-05-16 7:44 ` Nicolas STRANSKY
2006-05-16 8:11 ` Tejun Heo
2006-05-16 8:36 ` Nicolas STRANSKY
2006-05-17 21:15 ` Nicolas STRANSKY [this message]
2006-05-18 4:00 ` Tejun Heo
2006-05-18 15:54 ` Jeff Garzik
2006-05-19 3:43 ` [PATCH 1/1] libata: Fix the HSM error_mask mapping (was: Re: libata-tj and SMART) Albert Lee
2006-05-19 5:22 ` [PATCH 1/1] libata: Fix the HSM error_mask mapping Albert Lee
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='e4g3or$jbm$1@sea.gmane.org' \
--to=nico@stransky.cx \
--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).