See inline answer below. Simon Roscic <simon <at> segfault.info> writes:
> > i did some further tests with different kernel versions: > 3.5-rc6: OK > 3.4.4: OK > 3.2.22: OK > 3.0.1 - 3.0.22: OK > 3.0.23 - 3.0.36: not OK > 2.6.35.13: OK Let me add that kernel 3.0.38 also experiences the same for SLES 11 SP2. A restart of the network resolves it temporarily for a few hours. After running fine for a few hours after upgrade from 2.6.3x to 3.0.38 via zypper, this is not a good situation. > > now lets have a closer look at a kernel version which works: > ..... > > (before someone asks why i "must" use kernel 3.0.x ... because this are > SLES 11 SP2 VMs and they currently ship kernel 3.0.34) Going to raise an SR with Novell about this. > > i hope i described the problem in a way so that the kernel network > stack maintainers can understand the problem, please conact me if you > have further questions, and please CC me as i am not subscribed to > linux-kernel. this message is already on linux-netdev, if you wish you > can CC your answer also there. > > kind regards, > Simon Roscic. > > Best regards, Rune "TheFlyingCorpse" Darrud -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
