On Thu, May 28, 2015 at 03:41:49PM +0100, Ken Moffat wrote:
> On Wed, May 27, 2015 at 10:53:00PM -0700, Cong Wang wrote:
> > (Please always Cc netdev for networking bugs.)
> >
Sorry, didn't spot that. But anyway
>
> > For example:
> >
> > 1) What is your network setup? iptables? routes? etc.
>
On Wed, May 27, 2015 at 10:53:00PM -0700, Cong Wang wrote:
> (Please always Cc netdev for networking bugs.)
>
> On Sat, May 23, 2015 at 8:29 PM, Ken Moffat wrote:
> > On Sun, May 24, 2015 at 03:43:52AM +0100, Ken Moffat wrote:
> >> Anybody else suffering frm lost netwo
(Please always Cc netdev for networking bugs.)
On Sat, May 23, 2015 at 8:29 PM, Ken Moffat wrote:
> On Sun, May 24, 2015 at 03:43:52AM +0100, Ken Moffat wrote:
>> Anybody else suffering frm lost network connectivity in 4.0.x
>> kernels ? A couple of times this week, vim on an n
On Sun, May 24, 2015 at 03:43:52AM +0100, Ken Moffat wrote:
> Anybody else suffering frm lost network connectivity in 4.0.x
> kernels ? A couple of times this week, vim on an nfs-3 mount hung
> and I had to reboot. Both of those occasions were on an AMD desktop
> with the r8169 dri
Anybody else suffering frm lost network connectivity in 4.0.x
kernels ? A couple of times this week, vim on an nfs-3 mount hung
and I had to reboot. Both of those occasions were on an AMD desktop
with the r8169 driver, running 4.0.3. I thought it might be
specific to that machine. For the last
5 matches
Mail list logo