Hi Dave,
Dave Täht schreef op 2/3/17 13:10:
On 3/2/17 11:51 AM, Stijn Segers wrote:
> Thanks Sebastian, turned out to be a silly syntax error, I have it all
> disabled now. Ethtool -k and ethtool -K printing/requiring different
> stuff doesn't help of course :-)
>
> I re-enabled SQM, will see ho
On 3/2/17 11:51 AM, Stijn Segers wrote:
> Thanks Sebastian, turned out to be a silly syntax error, I have it all
> disabled now. Ethtool -k and ethtool -K printing/requiring different
> stuff doesn't help of course :-)
>
> I re-enabled SQM, will see how that works out with the offloading disable
Thanks Sebastian, turned out to be a silly syntax error, I have it all
disabled now. Ethtool -k and ethtool -K printing/requiring different
stuff doesn't help of course :-)
I re-enabled SQM, will see how that works out with the offloading
disabled.
Cheers
Stijn
___
On Thu, Mar 2, 2017 at 2:32 AM, Martin Tippmann wrote:
> On Wed, Mar 1, 2017 at 11:40 PM, Weedy wrote:
>> On 28 February 2017 at 05:40, Martin Tippmann wrote:
>>> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
>>> wrote:
Okay, so I tracked it down to cake being the culprit. When I disable t
On Wed, Mar 1, 2017 at 11:40 PM, Weedy wrote:
> On 28 February 2017 at 05:40, Martin Tippmann wrote:
>> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
>> wrote:
>>> Okay, so I tracked it down to cake being the culprit. When I disable the
>>> Cake SQM instance, no more of those traces, and no more
On 1 March 2017 at 17:40, Weedy wrote:
> On 28 February 2017 at 05:40, Martin Tippmann wrote:
>> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
>> wrote:
>>> Okay, so I tracked it down to cake being the culprit. When I disable the
>>> Cake SQM instance, no more of those traces, and no more sudden
On 28 February 2017 at 05:40, Martin Tippmann wrote:
> On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
> wrote:
>> Okay, so I tracked it down to cake being the culprit. When I disable the
>> Cake SQM instance, no more of those traces, and no more sudden reboots.
>>
>> If I can help debug this, let
Hi Stijn,
> On Mar 1, 2017, at 21:28, Stijn Segers
> wrote:
>
> Op wo, 1 mrt 2017 om 10:59 , schreef Sebastian Moeller :
>> Hi Stijn,
>>> On Mar 1, 2017, at 10:46, Stijn Segers
>>> wrote:
>>> Hi Baptiste,
>>> Thanks for your input. I found this thread [1] however which suggests
>>> offloadi
Op wo, 1 mrt 2017 om 10:59 , schreef Sebastian Moeller
:
Hi Stijn,
On Mar 1, 2017, at 10:46, Stijn Segers
wrote:
Hi Baptiste,
Thanks for your input. I found this thread [1] however which
suggests offloading capabilities:
"The GSW is found in all of the 1000mbit SoCs. it has 5 extern
> On Mar 1, 2017, at 10:59, Sebastian Moeller wrote:
>
> Hi Stijn,
>
>
>> On Mar 1, 2017, at 10:46, Stijn Segers
>> wrote:
>>
>> Hi Baptiste,
>>
>> Thanks for your input. I found this thread [1] however which suggests
>> offloading capabilities:
>>
>> "The GSW is found in all of the 1000
Hi Stijn,
> On Mar 1, 2017, at 10:46, Stijn Segers
> wrote:
>
> Hi Baptiste,
>
> Thanks for your input. I found this thread [1] however which suggests
> offloading capabilities:
>
> "The GSW is found in all of the 1000mbit SoCs. it has 5 external ports,
> 1-2 cpu ports and 1 further port th
Hi Baptiste,
Thanks for your input. I found this thread [1] however which suggests
offloading capabilities:
"The GSW is found in all of the 1000mbit SoCs. it has 5 external ports,
1-2 cpu ports and 1 further port that the internal HW offloading engine
connects to. The switch core used is a MT7
On Wed, Mar 01, 2017 at 08:23:13AM +0100, Stijn Segers wrote:
> OK... So I tried to disable offloading on the WAN interface (eth0.2 for the
> DIR-860L), but that throws the following error:
>
> # ethtool -K tso off gso off gro off eth0
> Cannot get device feature names: No such device
>
> Same fo
Op di, 28 feb 2017 om 11:40 , schreef Martin Tippmann :
On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
wrote:
Okay, so I tracked it down to cake being the culprit. When I
disable the
Cake SQM instance, no more of those traces, and no more sudden
reboots.
If I can help debug this, let me kn
Op di, 28 feb 2017 om 1:15 , schreef Eric Luehrsen
:
On 02/27/2017 03:17 PM, Stijn Segers wrote:
Okay, so I tracked it down to cake being the culprit. When I
disable the
Cake SQM instance, no more of those traces, and no more sudden
reboots.
If I can help debug this, let me know - I enab
On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers
wrote:
> Okay, so I tracked it down to cake being the culprit. When I disable the
> Cake SQM instance, no more of those traces, and no more sudden reboots.
>
> If I can help debug this, let me know - I enabled a Cake SQM instance on an
> APU2 and so fa
On 02/27/2017 03:17 PM, Stijn Segers wrote:
> Okay, so I tracked it down to cake being the culprit. When I disable the
> Cake SQM instance, no more of those traces, and no more sudden reboots.
>
> If I can help debug this, let me know - I enabled a Cake SQM instance on
> an APU2 and so far that s
Okay, so I tracked it down to cake being the culprit. When I disable
the Cake SQM instance, no more of those traces, and no more sudden
reboots.
If I can help debug this, let me know - I enabled a Cake SQM instance
on an APU2 and so far that seems to run fine.
So, in short: .50/51 bump is ok
18 matches
Mail list logo
