On Sat, Mar 18, 2017 at 06:09:33PM -0400, Bruce Momjian,,, wrote:
> On Sat, Mar 18, 2017 at 10:06:53PM +, Ben Hutchings wrote:
> > > It seems nothing changed.
> >
> > Try:
> > ethtool -A eth0 rx off tx off autoneg off
> > instead.
>
> OK, that worked:
>
> $ ethtool -A eth0 rx off
On Sat, Mar 18, 2017 at 10:06:53PM +, Ben Hutchings wrote:
> On Sat, Mar 18, 2017 at 05:10:50PM -0400, Bruce Momjian,,, wrote:
> [...]
> > I then ran:
> >
> > $ ethtool -A eth0 rx off tx off
> >
> > $ ethtool -a eth0
> > Pause parameters for eth0:
> > Autonegotiate: on
> >
On Sat, Mar 18, 2017 at 05:10:50PM -0400, Bruce Momjian,,, wrote:
[...]
> I then ran:
>
> $ ethtool -A eth0 rx off tx off
>
> $ ethtool -a eth0
> Pause parameters for eth0:
> Autonegotiate: on
> RX: on
> TX: on
>
> It seems nothing
On Sat, Mar 18, 2017 at 10:08:10PM +0100, Julien Aubin wrote:
> OK I did this. Does it have a huge impact on the system except mitigating
> the flaw ? (I don't think I have an HDLC hardware...)
If you don't know whether you have it, you don't have it. :-)
Ben.
--
Ben Hutchings
Life is like a
systemtap currently fails to build modules when the kernel source and
object trees are separate.
systemtap adds something like -I"/usr/share/systemtap/runtime" to
EXTRA_CFLAGS, and addtree should not adjust this as it's specifying an
absolute directory. But since make has no understanding of
Processing commands for cont...@bugs.debian.org:
> tags 856474 - help
Bug #856474 [src:linux] stap: include runtime_defines.h not found
Removed tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
856474:
Here is the dmesg output from just this afternoon:
[Mar18 12:40] e1000e :03:00.0 eth0: Reset adapter unexpectedly
[ +3.891401] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
[Mar18 13:40] e1000e :03:00.0 eth0: Reset adapter unexpectedly
On Sat, Mar 18, 2017 at 09:02:10PM +, Ben Hutchings wrote:
> Control: retitle -1 TX watchdog fires on e1000e interface
> Control: tag -1 moreinfo
>
> Please don't confuse e1000 and e1000e; they are quite different drivers
> for different chips.
Oh, thanks for the fix. I think I used e1000
OK I did this. Does it have a huge impact on the system except mitigating
the flaw ? (I don't think I have an HDLC hardware...)
2017-03-18 21:54 GMT+01:00 Ben Hutchings :
> On Sat, 2017-03-18 at 17:01 +0100, Julien Aubin wrote:
> > Source: linux
> > Severity: critical
> >
Processing control commands:
> retitle -1 TX watchdog fires on e1000e interface
Bug #858125 [src:linux] e1000: ethernet interface hangs occasionally, kernel
reports hang
Changed Bug title to 'TX watchdog fires on e1000e interface' from 'e1000:
ethernet interface hangs occasionally, kernel
Control: retitle -1 TX watchdog fires on e1000e interface
Control: tag -1 moreinfo
Please don't confuse e1000 and e1000e; they are quite different drivers
for different chips.
Does it help if you disable flow control by running:
ethtool -A eth0 rx off tx off
(Check the current settings
On Sat, 2017-03-18 at 17:01 +0100, Julien Aubin wrote:
> Source: linux
> Severity: critical
> Tags: security
> Justification: root security hole
>
> Hi,
>
> Security issue CVE-2017-2636 (severity 7.8) has been disclosed and the fix
> has
> been provided for Jessie and Wheezy. The problem is that
Processing commands for cont...@bugs.debian.org:
> severity 858125 important
Bug #858125 [src:linux] e1000: ethernet interface hangs occasionally, kernel
reports hang
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Here is a more complete dmesg output with a few resets included at the
bottom. You can see there is 14 minutes between the resets:
[Mar18 12:26] [ cut here ]
[ +0.19] WARNING: CPU: 0 PID: 0 at
Package: src:linux
Version: 3.16.39-1
Severity: critical
File: e1000
Justification: breaks unrelated software
Dear Maintainer,
I have had intermittent hangs of my two built-in ethernet interfaces since
switching from 100Mb ethernet to 1Gb ethernet. During the
hangs, no traffic passes through
Hi
On Sat, Mar 18, 2017 at 05:01:56PM +0100, Julien Aubin wrote:
> Source: linux
> Severity: critical
> Tags: security
> Justification: root security hole
>
> Hi,
>
> Security issue CVE-2017-2636 (severity 7.8) has been disclosed and the fix
> has
> been provided for Jessie and Wheezy. The
Processing commands for cont...@bugs.debian.org:
> retitle 858122 linux: CVE-2017-2636: tty: n_hdlc: get rid of racy n_hdlc.tbuf
Bug #858122 [src:linux] Upgrade linux kernel to 4.9.15 in sid and stretch
Changed Bug title to 'linux: CVE-2017-2636: tty: n_hdlc: get rid of racy
n_hdlc.tbuf' from
Source: linux
Severity: critical
Tags: security
Justification: root security hole
Hi,
Security issue CVE-2017-2636 (severity 7.8) has been disclosed and the fix
has
been provided for Jessie and Wheezy. The problem is that there's as of now
no
fix available for sid and stretch while things become
18 matches
Mail list logo