Hello everyone,
I let the system running for almost 12 hours
but the failure didn't show up.
I'll provide you the dropwatch output once the
failure happens again.
- Sebastiano
On Thu, Aug 1, 2013 at 4:40 PM, Sebastiano Spicuglia
wrote:
> Hi Hannes,
>
> here the info about the commit:
>
> comm
On Thu, 01 Aug 2013 at 14:34 GMT, Sebastiano Spicuglia
wrote:
>
> The machine suddenly stops to be connected to the network.
> Running "ifdown eth0" "ifup eth0" the network starts to work
> again for few minutes and then the failure happens again.
> It is not even possible to ping the machine.
>
Hi Hannes,
here the info about the commit:
commit 6c504ecf506705a6575541b28824e13090bd223b
Merge: 2408c2e bf903e4
Author: Linus Torvalds
Date: Fri Jul 26 14:40:10 2013 -0700
Regards
Sebastiano
On Thu, Aug 1, 2013 at 4:36 PM, Hannes Frederic Sowa
wrote:
> On Thu, Aug 01, 2013 at 04:34:00PM
On Thu, Aug 01, 2013 at 04:34:00PM +0200, Sebastiano Spicuglia wrote:
> [Kernel version from /proc/version ]
>
> Linux version 3.11.0-rc2+ (r...@cache.pdbg) (gcc version 4.7.2 (Debian
> 4.7.2-5) ) #5 SMP Thu Aug 1 14:20:35 CEST 2013
Which commit exactly?
Thanks,
Hannes
--
To unsubscribe from
[Summary]
the network layer stops to work without any message.
[Description]
The machine suddenly stops to be connected to the network.
Running "ifdown eth0" "ifup eth0" the network starts to work
again for few minutes and then the failure happens again.
It is not even possible to ping the machi
5 matches
Mail list logo