All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: <linux-rt-users@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Sekhar Nori <nsekhar@ti.com>
Subject: Re: [4.4-rc6-rt1 PATCH 0/2] ARM: am437x: boot test report
Date: Wed, 13 Jan 2016 13:41:33 +0200	[thread overview]
Message-ID: <569637ED.1030304@ti.com> (raw)
In-Reply-To: <20160112171556.GB31009@linutronix.de>

On 01/12/2016 07:15 PM, Sebastian Andrzej Siewior wrote:
> * Grygorii Strashko | 2015-12-28 20:00:09 [+0200]:
> 
>> Hi All, Sebastian,
> Hi Grygorii,
> 
>> 3) Seems there are some problem with HIGHMEM :(. System crashes if I'm trying
>>    to run hackbench (see log 1). I can run hackbench only if HIGHMEM is disabled.
>>    I've also tried to disable CONFIG_CPU_SW_DOMAIN_PAN, CONFIG_ARM_PATCH_PHYS_VIRT,
>>    and CONFIG_CPUSETS, before disabling HIGHMEM.
>>    Sorry, I'll not able to investigate it further because of Christmas holidays here.
> 
> I see. It seems not to trigger anything on x86.

Yah. I saw other reports - it seems this issue is not triggered on ARM SMP also
(as per report from Tim Sander). Will try to dig deeper.


> 
>> 4) Could we revert commit 4fa5422 'ARM: OMAP2: Drop the concept of certain power
>>    domains not being able to lose context.'? It's not required for 4.4-rt wakeup
>>    and introduces build warnings.
> 
> done.

Thanks.

-- 
regards,
-grygorii

  reply	other threads:[~2016-01-13 11:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 18:00 [4.4-rc6-rt1 PATCH 0/2] ARM: am437x: boot test report Grygorii Strashko
2015-12-28 18:00 ` [4.4-rc6-rt1 PATCH 1/2] kernel/sched/core.c: UP: fix 'implicit declaration of function 'update_migrate_disable' Grygorii Strashko
2015-12-28 18:00   ` Grygorii Strashko
2015-12-28 18:00 ` [4.4-rc6-rt1 PATCH 2/2] kernel/time/timer.c: UP: fix undefined reference to `del_timer_sync' Grygorii Strashko
2016-01-12 16:47   ` Sebastian Andrzej Siewior
2016-01-12 17:15 ` [4.4-rc6-rt1 PATCH 0/2] ARM: am437x: boot test report Sebastian Andrzej Siewior
2016-01-13 11:41   ` Grygorii Strashko [this message]
2016-01-13 20:14     ` Grygorii Strashko
2016-01-14 20:11       ` Grygorii Strashko
2016-01-14 20:11         ` Grygorii Strashko
2016-01-14 21:30         ` Russell King - ARM Linux
2016-01-14 21:30           ` Russell King - ARM Linux
2016-01-15 11:35           ` Grygorii Strashko
2016-01-15 11:35             ` Grygorii Strashko
2016-01-15 11:36             ` Russell King - ARM Linux
2016-01-15 11:36               ` Russell King - ARM Linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=569637ED.1030304@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nsekhar@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.