lubuntu-qa team mailing list archive

[Nio Wiklund <nio.wiklund@xxxxxxxxx>]

On 2013-09-21 20:10, Lars Noodén wrote:
> On 09/21/2013 08:59 PM, JM wrote:
>> On Sat, 21 Sep 2013 20:11:47 +0300
>> Lars Noodén <lars.nooden@xxxxxxxxx> wrote:
>>
>>> On 09/21/2013 08:00 PM, Phill Whiteside wrote:
>>>> At this point it seems that we are trapped between a rock and a hard place.
>>>>
>>>> Kernel team <> ISO team. ::SIGH:: Such frustrations led to my resigning
>>>> from various teams, I've asked a couple of people who can make an ISO with
>>>> the test kernel if they would. Other than that, my hands are tied.
>>>>
>>>> We need an ISO with the patch that has been already applied upstream into
>>>> it.... Grrrrr.
>>>>
>>>> Regards,
>>>>
>>>> Phill.
>>>
>>> I did try this kernel the other day and it did lock up just like the one
>>> in the repository:
>>>
>>> linux-image-3.11.0-7-generic_3.11.0-7.14~lp1227202v1_amd64.deb
>>>
>>> I thought I wrote it in a message, but can't find it in my archive, so
>>> maybe I didn't.
>>>
>>> So far turning off zram seems to be the only thing that works.  Or at
>>> least seems to work, so far so good.
>>>
>>> Regards,
>>> /Lars
>>
>> Hi,
>>
>> Here is Joyce Markoll, aka Mélodie. I have used zram for many years in different shapes
>> (ramzswap once upon a time when it was only in the compcache project) and I am very
>> interested to see it setup in Lubuntu.
>>
>> I wanted to join the testing since some time now but didn't find the right moment for it
>> (except a fast test in a vbox machine some time ago), but now I'm zsyncing the iso to
>> test it in one of my old machines. (T30 1 GB ram and intel 1.86 Mhz proc).
>>
>> Just a thought:
>> have you set it up to create block devices which are as large as 50% of
>> the available ram, and one of those block devices for each processor detected, or did you
>> setup other values? 
>>
>> which method is used to start it at boot time?
>>
>> Regards,
>> Mélodie
>>
>> --
>>
>> LinuxVillage
>> http://linuxvillage.org
> 
> I've used whatever the default for the recent ISOs has been.  If you
> have a recipe for how to create the block devices you mention, I can try
> that in tomorrow's run.
> 
> Regards,
> /Lars
> 
I have managed to freeze the default daily build of today too, but not
with Joseph Salisbury's kernel. I tried hard to do the same things that
froze the standard kernel, but no, it did not freeze for me.

I limited the RAM to 384 MB to force swapping. Typically it would freeze
when I ran a youtube video and at the same time installed something
fairly big with apt-get. So Joseph's kernel is better, but according to
your tests, Lars, it can also freeze, so the bug fix did not take care
of everything.

Lars, can you describe how you make Joseph Salisbury's kernel freeze?
What environment, what programs etc so that I can try that too.

Best regards
Nio