On Thu, Nov 09, 2017 at 09:15:53AM -0500, Derrick Lobo wrote:
> The daily beta version of nebtsd 8 does not support ixg 5gb NIC's, the
> support was enabled in 7.99
That doesn't make sense - if it's in 7.anything, it's in 8. When we cut
the 8 branch, we move the version number on HEAD to 8.99.
Updating src tree:
P src/common/dist/zlib/inflate.c
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/bsd/acpica/bin/iasl/Makefile
P src/external/bsd/nvi/dist/cl/cl_funcs.c
P src/external/bsd/nvi/dist/common/cut.h
P src/external/bsd/nvi/dist/common/multibyte.h
P
Okay, so it is triggered by a ATAPI command.
I've had concern that maybe code mishandle ATAPI failures, but the recovery
code seems to be okay as far as I can read it.
I've changed the message to not show unless debugging, so it should not
spam you again.
Jaromir
2017-11-10 23:03 GMT+01:00
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
Im fine with not supporting the hardware interface(I wasn't using it
anyways), but the kernel should not go in a panic state, since I cant
upgrade the server or use it
From: port-amd64-ow...@netbsd.org [mailto:port-amd64-ow...@netbsd.org] On
Behalf Of Derrick Lobo
Sent: Thursday, November 9,
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
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
hibernate/suspend.
Jaromir
2017-11-10 10:49 GMT+01:00