Am using hardy kernel now, 2.6.24. Will do some big transfers to see
what happens :)
Alan
On Dec 20, 2007 8:46 PM, mr <email address hidden> wrote:
> Thanks for the suggestion, I will give it a try but I myself won't be
> able to test as I am going away tomorrow for three weeks. Will
> definitely give it a shot when I get back though, thanks.
>
> Alan
>
>
> On Dec 20, 2007 6:33 PM, Chris Jones <email address hidden> wrote:
> > Alan: Something worth doing in the interim would be to try with hardy's kernel and see if it does the same (I can only see daily alternate installers, but booted into the expert mode I expect you can get a shell and set up the network by hand and run some stress testing on it).
> > If that's going to be a problem, let me know and I'll see if enough spare time shakes out of christmas to try it :)
> >
> > --
> > network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed out
> > https://bugs.launchpad.net/bugs/76489
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
Am using hardy kernel now, 2.6.24. Will do some big transfers to see
what happens :)
Alan
On Dec 20, 2007 8:46 PM, mr <email address hidden> wrote: /bugs.launchpad .net/bugs/ 76489
> Thanks for the suggestion, I will give it a try but I myself won't be
> able to test as I am going away tomorrow for three weeks. Will
> definitely give it a shot when I get back though, thanks.
>
> Alan
>
>
> On Dec 20, 2007 6:33 PM, Chris Jones <email address hidden> wrote:
> > Alan: Something worth doing in the interim would be to try with hardy's kernel and see if it does the same (I can only see daily alternate installers, but booted into the expert mode I expect you can get a shell and set up the network by hand and run some stress testing on it).
> > If that's going to be a problem, let me know and I'll see if enough spare time shakes out of christmas to try it :)
> >
> > --
> > network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed out
> > https:/
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>