[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
- To: Stefan Hertenberger <email@example.com>
- Subject: Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
- From: Jaromír Doleček <jaromir.dolecek%gmail.com@localhost>
- Date: Fri, 10 Nov 2017 18:43:19 +0100
TFES usually means an unsupported command was sent to the device, or a
command was sent while previous was finished.
Could you please try to figure out what is the command sent to the cd0
device just before that error? It should be possible to turn the debug
messages on via the ahcdebug_mask variable in ddb, set it to DEBUG_XFERS
It could also be asynchronous notification from the device, which gets
mishandled as error. I see both your and Martin's device supports them
(SNTF capability). If there is no preceding command, it could be this.
2017-11-10 14:21 GMT+01:00 Stefan Hertenberger <firstname.lastname@example.org>:
> Am 10. November 2017 14:16:51 MEZ schrieb Martin Husemann <
>> On Fri, Nov 10, 2017 at 02:11:12PM +0100, Jaromír Dole?ek wrote:
>>> The TFD 0x2051 corresponds to Media Changed error, with DRDY/ERR status
>>> bits. Is it possible this message appears every time you change media in
>>> the cd0?
>>> Alternatively, I imagine this could be generated if the drive is setup to
>> For me it happens w/o any medium and never touching the drive.
> For me too, starts while booting w/o interaction from me.
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet
Main Index |
Thread Index |