On Wed, Jan 10, 2018 at 12:42:47PM +0200, Darius Ski wrote:
> Hi,
>
> On Fri, Jan 5, 2018 at 11:38 AM, Steffen Klassert
> wrote:
> > On Tue, Dec 19, 2017 at 10:50:42AM +0200, Darius Ski wrote:
> >> Hi,
> >>
> >> thanks a lot for the patch. I have applied it to 4.14.7 and crossed
> >> fingers, hop
Hi,
On Fri, Jan 5, 2018 at 11:38 AM, Steffen Klassert
wrote:
> On Tue, Dec 19, 2017 at 10:50:42AM +0200, Darius Ski wrote:
>> Hi,
>>
>> thanks a lot for the patch. I have applied it to 4.14.7 and crossed
>> fingers, hopefully no more problems.
>>
>> I will let community know if there are any more
On Tue, Dec 19, 2017 at 10:50:42AM +0200, Darius Ski wrote:
> Hi,
>
> thanks a lot for the patch. I have applied it to 4.14.7 and crossed
> fingers, hopefully no more problems.
>
> I will let community know if there are any more crashes.
Any news on this, did the patch help?
Hi,
thanks a lot for the patch. I have applied it to 4.14.7 and crossed
fingers, hopefully no more problems.
I will let community know if there are any more crashes.
Thanks!
Darius.
On Mon, Dec 18, 2017 at 2:22 PM, Steffen Klassert
wrote:
> On Mon, Dec 18, 2017 at 01:50:10PM +0200, Darius Sk
On Mon, Dec 18, 2017 at 01:50:10PM +0200, Darius Ski wrote:
> Hi,
>
> running 4.14.6 with 3 IPSec tunnels via Racoon/setkey and today woke up to
> this:
>
> [Mon Dec 18 07:26:15 2017] [ cut here ]
> [Mon Dec 18 07:26:15 2017] WARNING: CPU: 0 PID: 10555 at
> ./include/net/
