On 2019-5-20 20:58, Hagbard Celine wrote:
> 2019-05-20 11:37 GMT+02:00, Chao Yu :
>> On 2019/5/16 1:01, Hagbard Celine wrote:
>>> 2019-05-15 18:50 GMT+02:00, Hagbard Celine :
2019-05-15 10:13 GMT+02:00, Chao Yu :
> On 2019/5/15 16:03, Hagbard Celine wrote:
>> 2019-05-15 4:25 GMT+02:00,
2019-05-20 11:37 GMT+02:00, Chao Yu :
> On 2019/5/16 1:01, Hagbard Celine wrote:
>> 2019-05-15 18:50 GMT+02:00, Hagbard Celine :
>>> 2019-05-15 10:13 GMT+02:00, Chao Yu :
On 2019/5/15 16:03, Hagbard Celine wrote:
> 2019-05-15 4:25 GMT+02:00, Chao Yu :
>> On 2019/5/15 2:13, Hagbard Celi
On 2019/5/16 1:01, Hagbard Celine wrote:
> 2019-05-15 18:50 GMT+02:00, Hagbard Celine :
>> 2019-05-15 10:13 GMT+02:00, Chao Yu :
>>> On 2019/5/15 16:03, Hagbard Celine wrote:
2019-05-15 4:25 GMT+02:00, Chao Yu :
> On 2019/5/15 2:13, Hagbard Celine wrote:
>> 2019-04-02 15:31 GMT+02:00,
2019-05-15 18:50 GMT+02:00, Hagbard Celine :
> 2019-05-15 10:13 GMT+02:00, Chao Yu :
>> On 2019/5/15 16:03, Hagbard Celine wrote:
>>> 2019-05-15 4:25 GMT+02:00, Chao Yu :
On 2019/5/15 2:13, Hagbard Celine wrote:
> 2019-04-02 15:31 GMT+02:00, Chao Yu :
>> On 2019-4-2 20:41, Hagbard Celi
2019-05-15 10:13 GMT+02:00, Chao Yu :
> On 2019/5/15 16:03, Hagbard Celine wrote:
>> 2019-05-15 4:25 GMT+02:00, Chao Yu :
>>> On 2019/5/15 2:13, Hagbard Celine wrote:
2019-04-02 15:31 GMT+02:00, Chao Yu :
> On 2019-4-2 20:41, Hagbard Celine wrote:
>> That seems to have fixed it. No mor
On 2019/5/15 16:03, Hagbard Celine wrote:
> 2019-05-15 4:25 GMT+02:00, Chao Yu :
>> On 2019/5/15 2:13, Hagbard Celine wrote:
>>> 2019-04-02 15:31 GMT+02:00, Chao Yu :
On 2019-4-2 20:41, Hagbard Celine wrote:
> That seems to have fixed it. No more errors in syslog after extracting
> my
2019-05-15 4:25 GMT+02:00, Chao Yu :
> On 2019/5/15 2:13, Hagbard Celine wrote:
>> 2019-04-02 15:31 GMT+02:00, Chao Yu :
>>> On 2019-4-2 20:41, Hagbard Celine wrote:
That seems to have fixed it. No more errors in syslog after extracting
my stage3 tarball. Also ran a couple of kernel compi
On 2019/5/15 2:13, Hagbard Celine wrote:
> 2019-04-02 15:31 GMT+02:00, Chao Yu :
>> On 2019-4-2 20:41, Hagbard Celine wrote:
>>> That seems to have fixed it. No more errors in syslog after extracting
>>> my stage3 tarball. Also ran a couple of kernel compiles on a partition
>>> mounted with data_fl
2019-04-02 15:31 GMT+02:00, Chao Yu :
> On 2019-4-2 20:41, Hagbard Celine wrote:
>> That seems to have fixed it. No more errors in syslog after extracting
>> my stage3 tarball. Also ran a couple of kernel compiles on a partition
>> mounted with data_flush and system seems stable.
>
> Thanks a lot f
On 2019-4-2 20:41, Hagbard Celine wrote:
> That seems to have fixed it. No more errors in syslog after extracting
> my stage3 tarball. Also ran a couple of kernel compiles on a partition
> mounted with data_flush and system seems stable.
Thanks a lot for your quick test. :)
Thanks,
>
> 2019-04-
That seems to have fixed it. No more errors in syslog after extracting
my stage3 tarball. Also ran a couple of kernel compiles on a partition
mounted with data_flush and system seems stable.
2019-04-01 10:05 GMT+02:00, Chao Yu :
> On 2019/3/31 2:54, Hagbard Celine wrote:
>> First, yes it is caused
On 2019/3/31 2:54, Hagbard Celine wrote:
> First, yes it is caused by data_flush, this is what I am trying to
> report. Without that option there is no "stack guard page was hit" and
> no "kernel stack overflow" and kernel is stable.
> This time I was using kernel 5.0.3, as can be seen in the log i
First, yes it is caused by data_flush, this is what I am trying to
report. Without that option there is no "stack guard page was hit" and
no "kernel stack overflow" and kernel is stable.
This time I was using kernel 5.0.3, as can be seen in the log in my first mail.
I do not remember exactly what k
Oh, sorry, it's quite possible that bug is caused by data_flush, could
remove that mount option first?
Thanks,
On 2019/3/30 11:25, Chao Yu wrote:
> Hi Hagbard,
>
> Sorry for the delay.
>
> On 2019/3/27 21:59, Hagbard Celine wrote:
>> Hi, this is a long standing bug that I've hit before on older
Hi Hagbard,
Sorry for the delay.
On 2019/3/27 21:59, Hagbard Celine wrote:
> Hi, this is a long standing bug that I've hit before on older kernels,
> but I was not able to get the syslog saved because of the nature of
> the bug. This time I had booted form a pen-drive, and was able to save
> the
Hi, this is a long standing bug that I've hit before on older kernels,
but I was not able to get the syslog saved because of the nature of
the bug. This time I had booted form a pen-drive, and was able to save
the log to it's efi-partition.
What i did to trigger it was to create a partition and for
16 matches
Mail list logo
