From: Tejun Heo <htejun@gmail.com>
To: "Dâniel Fraga" <fragabr@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_nv: "abnormal status 0x7F on port 0xE407"
Date: Mon, 05 Mar 2007 14:04:28 +0900 [thread overview]
Message-ID: <45EBA4DC.3030201@gmail.com> (raw)
In-Reply-To: <kjmob4-j82.ln1@tux.abusar.org>
Dâniel Fraga wrote:
> Linux 2.6.20
> x86_64
> nforce 410 chipset
> ST3160811AS (Seagate 160GB SATA 2)
>
> sata_nv 0000:00:0e.0: version 3.2
> ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
> ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 23
> PCI: Setting latency timer of device 0000:00:0e.0 to 64
> ata1: SATA max UDMA/133 cmd 0xE800 ctl 0xE482 bmdma 0xE000 irq 23
> ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE082 bmdma 0xE008 irq 23
> scsi0 : sata_nv
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32)
> ata1.00: ata1: dev 0 multi count 16
> ata1.00: configured for UDMA/133
> scsi1 : sata_nv
> ata2: SATA link down (SStatus 0 SControl 300)
> ATA: abnormal status 0x7F on port 0xE407
>
> I bought this HD today and it is working perfectly, but it's
> strange the last message. Should I worry about it?
>
> I saw many similar logs on Google, so I think it's harmless,
> right? Thanks!
Yeap, it's harmless and the message is being removed in the devel tree.
Thanks.
--
tejun
prev parent reply other threads:[~2007-03-05 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 17:07 sata_nv: "abnormal status 0x7F on port 0xE407" Dâniel Fraga
2007-03-05 5:04 ` Tejun Heo [this message]
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=45EBA4DC.3030201@gmail.com \
--to=htejun@gmail.com \
--cc=fragabr@gmail.com \
--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).