On Wed, 21 Aug 2019 at 13:41, Naoya Horiguchi wrote:
>
> On Tue, Aug 20, 2019 at 03:03:55PM +0800, Wanpeng Li wrote:
> > Cc Mel Gorman, Kirill, Dave Hansen,
> > On Tue, 11 Jun 2019 at 07:51, Naoya Horiguchi
> > wrote:
> > >
> > > On Wed, May 29, 2019 at 04:31:01PM -0700, Mike Kravetz wrote:
> >
On Tue, Aug 20, 2019 at 03:03:55PM +0800, Wanpeng Li wrote:
> Cc Mel Gorman, Kirill, Dave Hansen,
> On Tue, 11 Jun 2019 at 07:51, Naoya Horiguchi
> wrote:
> >
> > On Wed, May 29, 2019 at 04:31:01PM -0700, Mike Kravetz wrote:
> > > On 5/28/19 2:49 AM, Wanpeng Li wrote:
> > > > Cc Paolo,
> > > >
Cc Mel Gorman, Kirill, Dave Hansen,
On Tue, 11 Jun 2019 at 07:51, Naoya Horiguchi wrote:
>
> On Wed, May 29, 2019 at 04:31:01PM -0700, Mike Kravetz wrote:
> > On 5/28/19 2:49 AM, Wanpeng Li wrote:
> > > Cc Paolo,
> > > Hi all,
> > > On Wed, 14 Feb 2018 at 06:34, Mike Kravetz
> > > wrote:
> > >>
On Tue, 11 Jun 2019 at 07:51, Naoya Horiguchi wrote:
>
> On Wed, May 29, 2019 at 04:31:01PM -0700, Mike Kravetz wrote:
> > On 5/28/19 2:49 AM, Wanpeng Li wrote:
> > > Cc Paolo,
> > > Hi all,
> > > On Wed, 14 Feb 2018 at 06:34, Mike Kravetz
> > > wrote:
> > >>
> > >> On 02/12/2018 06:48 PM,
On Wed, May 29, 2019 at 04:31:01PM -0700, Mike Kravetz wrote:
> On 5/28/19 2:49 AM, Wanpeng Li wrote:
> > Cc Paolo,
> > Hi all,
> > On Wed, 14 Feb 2018 at 06:34, Mike Kravetz wrote:
> >>
> >> On 02/12/2018 06:48 PM, Michael Ellerman wrote:
> >>> Andrew Morton writes:
> >>>
> On Thu, 08 Feb
On 5/28/19 2:49 AM, Wanpeng Li wrote:
> Cc Paolo,
> Hi all,
> On Wed, 14 Feb 2018 at 06:34, Mike Kravetz wrote:
>>
>> On 02/12/2018 06:48 PM, Michael Ellerman wrote:
>>> Andrew Morton writes:
>>>
On Thu, 08 Feb 2018 12:30:45 + Punit Agrawal
wrote:
>>
>> So I don't
Cc Paolo,
Hi all,
On Wed, 14 Feb 2018 at 06:34, Mike Kravetz wrote:
>
> On 02/12/2018 06:48 PM, Michael Ellerman wrote:
> > Andrew Morton writes:
> >
> >> On Thu, 08 Feb 2018 12:30:45 + Punit Agrawal
> >> wrote:
> >>
>
> So I don't think that the above test result means that
On 02/12/2018 06:48 PM, Michael Ellerman wrote:
> Andrew Morton writes:
>
>> On Thu, 08 Feb 2018 12:30:45 + Punit Agrawal
>> wrote:
>>
So I don't think that the above test result means that errors are properly
handled, and
On 02/12/2018 06:48 PM, Michael Ellerman wrote:
> Andrew Morton writes:
>
>> On Thu, 08 Feb 2018 12:30:45 + Punit Agrawal
>> wrote:
>>
So I don't think that the above test result means that errors are properly
handled, and the proposed patch should help for arm64.
>>>
>>>
On 02/08/2018 09:30 PM, Punit Agrawal wrote:
> Horiguchi-san,
>
> Naoya Horiguchi writes:
>
>> Hi Punit,
>>
>> On Mon, Feb 05, 2018 at 03:05:43PM +, Punit Agrawal wrote:
>>> Naoya Horiguchi writes:
>>>
>
> [...]
>
You can
On 02/08/2018 09:30 PM, Punit Agrawal wrote:
> Horiguchi-san,
>
> Naoya Horiguchi writes:
>
>> Hi Punit,
>>
>> On Mon, Feb 05, 2018 at 03:05:43PM +, Punit Agrawal wrote:
>>> Naoya Horiguchi writes:
>>>
>
> [...]
>
You can easily reproduce this by calling madvise(MADV_HWPOISON)
On Thu, 08 Feb 2018 12:30:45 + Punit Agrawal wrote:
> >
> > So I don't think that the above test result means that errors are properly
> > handled, and the proposed patch should help for arm64.
>
> Although, the deviation of pud_huge() avoids a kernel crash the code
>
On Thu, 08 Feb 2018 12:30:45 + Punit Agrawal wrote:
> >
> > So I don't think that the above test result means that errors are properly
> > handled, and the proposed patch should help for arm64.
>
> Although, the deviation of pud_huge() avoids a kernel crash the code
> would be easier to
Horiguchi-san,
Naoya Horiguchi writes:
> Hi Punit,
>
> On Mon, Feb 05, 2018 at 03:05:43PM +, Punit Agrawal wrote:
>> Naoya Horiguchi writes:
>>
[...]
>> >
>> > You can easily reproduce this by calling madvise(MADV_HWPOISON) twice on
Horiguchi-san,
Naoya Horiguchi writes:
> Hi Punit,
>
> On Mon, Feb 05, 2018 at 03:05:43PM +, Punit Agrawal wrote:
>> Naoya Horiguchi writes:
>>
[...]
>> >
>> > You can easily reproduce this by calling madvise(MADV_HWPOISON) twice on
>> > a 1GB hugepage. This happens because
Hi Punit,
On Mon, Feb 05, 2018 at 03:05:43PM +, Punit Agrawal wrote:
> Naoya Horiguchi writes:
>
> > Recently the following BUG was reported:
> >
> > Injecting memory failure for pfn 0x3c at process virtual address
> > 0x7fe3
> > Memory
Hi Punit,
On Mon, Feb 05, 2018 at 03:05:43PM +, Punit Agrawal wrote:
> Naoya Horiguchi writes:
>
> > Recently the following BUG was reported:
> >
> > Injecting memory failure for pfn 0x3c at process virtual address
> > 0x7fe3
> > Memory failure: 0x3c: recovery
Naoya Horiguchi writes:
> Recently the following BUG was reported:
>
> Injecting memory failure for pfn 0x3c at process virtual address
> 0x7fe3
> Memory failure: 0x3c: recovery action for huge page: Recovered
> BUG: unable to handle kernel
Naoya Horiguchi writes:
> Recently the following BUG was reported:
>
> Injecting memory failure for pfn 0x3c at process virtual address
> 0x7fe3
> Memory failure: 0x3c: recovery action for huge page: Recovered
> BUG: unable to handle kernel paging request at
On 01/29/2018 07:54 PM, Naoya Horiguchi wrote:
> Recently the following BUG was reported:
>
> Injecting memory failure for pfn 0x3c at process virtual address
> 0x7fe3
> Memory failure: 0x3c: recovery action for huge page: Recovered
> BUG: unable to handle kernel
On 01/29/2018 07:54 PM, Naoya Horiguchi wrote:
> Recently the following BUG was reported:
>
> Injecting memory failure for pfn 0x3c at process virtual address
> 0x7fe3
> Memory failure: 0x3c: recovery action for huge page: Recovered
> BUG: unable to handle kernel
Recently the following BUG was reported:
Injecting memory failure for pfn 0x3c at process virtual address
0x7fe3
Memory failure: 0x3c: recovery action for huge page: Recovered
BUG: unable to handle kernel paging request at 8dfcc0003000
IP:
Recently the following BUG was reported:
Injecting memory failure for pfn 0x3c at process virtual address
0x7fe3
Memory failure: 0x3c: recovery action for huge page: Recovered
BUG: unable to handle kernel paging request at 8dfcc0003000
IP:
23 matches
Mail list logo