Hi Bruce,
> On 25 Jul 2016, at 03:40, Bruce Ashfield wrote:
>
> On 2016-07-24 6:09 PM, Chris Tapp wrote:
>> I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may
>> have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051.
>>
>> I’m using a J1900 (listed as affec
On Sun, Jul 24, 2016 at 7:38 AM, Khem Raj wrote:
> On Sun, Jul 24, 2016 at 12:34 AM, Edward Wingate wrote:
>> Ah, I found it. I had inadvertently deleted one line
>> (DISTRO="mydistro") from my layer's conf/layer.conf.
>>
>> Am I doing this right though? Do I need DISTRO="mydistro" in both
>> c
This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version w
On Sun, Jul 24, 2016 at 2:42 PM, Chris Sykes <
ch...@newforest-technology.co.uk> wrote:
> Hi,
>
> At the end of last week I hit a known kernel memory leak in the
> linux-yocto 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly
> results in an OOM kernel panic on my platform (x86, 1G RAM
On 2016-07-24 6:09 PM, Chris Tapp wrote:
I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may
have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051.
I’m using a J1900 (listed as affected) and the system locks up totally (running
a graphics-based application)
I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may
have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051.
I’m using a J1900 (listed as affected) and the system locks up totally (running
a graphics-based application) after an indeterminate period.
Using the s
On Sun, Jul 24, 2016 at 11:42 AM, Chris Sykes
wrote:
> Hi,
>
> At the end of last week I hit a known kernel memory leak in the linux-yocto
> 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly results in an
> OOM kernel panic on my platform (x86, 1G RAM).
>
> The patch below fixed the pr
Hi,
At the end of last week I hit a known kernel memory leak in the
linux-yocto 4.1 branch, as delivered in 2.1 / krogoth. It rather
quickly results in an OOM kernel panic on my platform (x86, 1G RAM).
The patch below fixed the problem for me:
http://www.spinics.net/lists/stable/msg138760.ht
On Sun, Jul 24, 2016 at 12:34 AM, Edward Wingate wrote:
> Ah, I found it. I had inadvertently deleted one line
> (DISTRO="mydistro") from my layer's conf/layer.conf.
>
> Am I doing this right though? Do I need DISTRO="mydistro" in both
> conf/layer.conf and conf/distro/mydistro.conf?
Just conf/
Ah, I found it. I had inadvertently deleted one line
(DISTRO="mydistro") from my layer's conf/layer.conf.
Am I doing this right though? Do I need DISTRO="mydistro" in both
conf/layer.conf and conf/distro/mydistro.conf? Removing it from
either doesn't work, but it seems redundant to put it in my
On Sat, Jul 23, 2016 at 11:05 PM, Khem Raj wrote:
> Move these DISTRO settings above require conf/distro/poky.conf
That didn't change anything. And it had been working like that for a
long time now. Just a few days ago, it stopped taking effect and
reverting back to poky. I have not been able
11 matches
Mail list logo
