From: Robert Hancock <hancockrwd@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>
Subject: Re: libata EH running when switching VTs
Date: Mon, 24 Jan 2011 19:23:30 -0600 [thread overview]
Message-ID: <4D3E2612.2060808@gmail.com> (raw)
In-Reply-To: <201101221831.09448.toralf.foerster@gmx.de>
On 01/22/2011 11:31 AM, Toralf Förster wrote:
>
> Robert Hancock wrote at 17:36:15
>> (CCing linux-ide)
>>
>> On 01/22/2011 09:25 AM, Toralf Förster wrote:
>>> Hello,
>>>
>>> Henrique de Moraes Holschuh wrote at 14:11:12
>>>
>>>> I don't even know whom to refer you to. Maybe ask in LKML directly?
>>>> Use the subject "libata EH running when switching VTs". If one of
>>>> those VTs are in X.org control, say that as well.
>>>
>>> I'm wondering why I get this in /var/log/messages w/ kernel 2.6.37 when I
>>> switch from VT7 (running xorg ) to VT12 (or 1 or 2 or another number) and
>>> back:
>>>
>>>
>>> 2011-01-22T16:20:53.854+01:00 n22 kernel: ata1: hard resetting link
>>> 2011-01-22T16:20:54.163+01:00 n22 kernel: ata1: SATA link up 1.5 Gbps
>>> (SStatus 113 SControl 300)
>>> 2011-01-22T16:20:54.164+01:00 n22 kernel: ata1.00: ACPI cmd
>>> ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
>>> 2011-01-22T16:20:54.164+01:00 n22 kernel: ata1.00: ACPI cmd
>>> f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
>>> 2011-01-22T16:20:54.165+01:00 n22 kernel: ata1.00: ACPI cmd
>>> ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
>>> 2011-01-22T16:20:54.165+01:00 n22 kernel: ata1.00: ACPI cmd
>>> ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
>>> 2011-01-22T16:20:54.169+01:00 n22 kernel: ata1.00: ACPI cmd
>>> ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
>>> 2011-01-22T16:20:54.169+01:00 n22 kernel: ata1.00: ACPI cmd
>>> f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
>>> 2011-01-22T16:20:54.169+01:00 n22 kernel: ata1.00: ACPI cmd
>>> ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
>>> 2011-01-22T16:20:54.169+01:00 n22 kernel: ata1.00: ACPI cmd
>>> ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
>>> 2011-01-22T16:20:54.170+01:00 n22 kernel: ata1.00: configured for
>>> UDMA/100 2011-01-22T16:20:54.171+01:00 n22 kernel: ata1: EH complete
>>>
>>>
>>> I'm running an almost stable Gentoo on a ThinkPad T400 with current
>>> kernel (2.6.37, earlier shows this behaviour too)
>>
>> Is that the only output you're getting? Can you post the full dmesg log
>> from bootup?
>
> Of course - attached here
Curious, there seems to be no indication of why EH was triggered,
doesn't seem to be have been due to an error. Does this also happen in
single-user mode or with minimal processes running? It's possible that
userspace is triggering this somehow.
next prev parent reply other threads:[~2011-01-25 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 15:25 libata EH running when switching VTs Toralf Förster
2011-01-22 16:36 ` Robert Hancock
2011-01-22 17:31 ` Toralf Förster
2011-01-25 1:23 ` Robert Hancock [this message]
2011-01-25 9:17 ` Toralf Förster
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=4D3E2612.2060808@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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