Hi Ian,
thank you for responding to this issue. After i recognized the
connection loss, i attached a serial console and monitored the eth ports
with ethtool. Swapping the cable between eth0 and eth1. eth0 was always
dead with no link detection. eth1 was always working fine. I
quadrochecked it a fe
Control: tag -1 +moreinfo
On Mon, 2015-01-12 at 17:30 +0100, Draghi wrote:
n...@none.net bounces with an unknown account. Hopefully you see this
here some other way.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
Control: found -1 3.16.7-ckt2-1
Control: notfound -1 3.16.0-4
On Mon, 2015-01-12 at 17:30 +0100, Draghi wrote:
> Source: linux
> Version: 3.16.0-4
FYI, this is the ABI not the package version. The version can be seen in
uname or in your kernel log in:
Linux version 3.16.0-4-kirkwood (debi
Source: linux
Version: 3.16.0-4
Severity: important
I am using a QNAP TS-419P II. After upgrading from Wheezy, eth0 stopped working
while eth1 still does.
ethtool reports no link when plugging in the cable.
This is partially similar to #719680
For the complete log see: http://forum.qnap.com/viewt
4 matches
Mail list logo
