On Wed, Jan 30, 2019 at 9:28 AM Lance Richardson wrote:
>
> On Wed, Jan 30, 2019 at 12:17 PM Cong Wang wrote:
> >
> > On Wed, Jan 30, 2019 at 8:54 AM Ivan Babrou wrote:
> > >
> > > Hey,
> > >
> > > We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
> > > crashed with the follo
On 30/01/19 16:51, Ivan Babrou wrote:
> Hey,
>
> We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
> crashed with the following:
>
> [ 2313.192006] general protection fault: [#1] SMP PTI
> [ 2313.205924] CPU: 32 PID: 65437 Comm: nginx-fl Tainted: G
> O 4.19.18-cloudfla
On 30/01/19 17:33, Edward Cree wrote:
> On 30/01/19 16:51, Ivan Babrou wrote:
>> Hey,
>>
>> We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
>> crashed with the following:
>>
>> [ 2313.192006] general protection fault: [#1] SMP PTI
>> [ 2313.205924] CPU: 32 PID: 65437 Comm
On Wed, Jan 30, 2019 at 12:17 PM Cong Wang wrote:
>
> On Wed, Jan 30, 2019 at 8:54 AM Ivan Babrou wrote:
> >
> > Hey,
> >
> > We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
> > crashed with the following:
> >
> > [ 2313.192006] general protection fault: [#1] SMP PTI
>
On Wed, Jan 30, 2019 at 8:54 AM Ivan Babrou wrote:
>
> Hey,
>
> We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
> crashed with the following:
>
> [ 2313.192006] general protection fault: [#1] SMP PTI
> [ 2313.205924] CPU: 32 PID: 65437 Comm: nginx-fl Tainted: G
> O
On 01/30/2019 08:51 AM, Ivan Babrou wrote:
> Hey,
>
> We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
> crashed with the following:
>
> [ 2313.192006] general protection fault: [#1] SMP PTI
> [ 2313.205924] CPU: 32 PID: 65437 Comm: nginx-fl Tainted: G
> O 4.19.1
Hey,
We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
crashed with the following:
[ 2313.192006] general protection fault: [#1] SMP PTI
[ 2313.205924] CPU: 32 PID: 65437 Comm: nginx-fl Tainted: G
O 4.19.18-cloudflare-2019.1.8 #2019.1.8
[ 2313.224973] Hardware name: