<div dir="ltr">Hi,<div><br></div><div>I've asked Joe (kernel team) about what plans the kernel team have for the kernel that will be shipped with 14.04 LTS. I've also stressed that this is not an urgent request! Kernel freeze is about NOW! That team have been working flat out to get as many gremlins sorted as possible. They are entitled to now catch their breath, just as we testers do after a milestone testing run. Cometh the release-candidate, all teams need to have their batteries re-charged for the final push in one week as the 14.04 release is now just a fortnight away.</div>
<div><br></div><div>So, now is the time the to concentrate on 'critical' bugs that would break an installation. We will never win the war against bugs, we must instead concentrate on winning battles :D</div><div><br>
</div><div>Regards,</div><div><br></div><div>Phill.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 3 October 2013 20:56, John Hupp <span dir="ltr"><<a href="mailto:lubuntu@prpcompany.com" target="_blank">lubuntu@prpcompany.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Good to hear, thanks!<div><div class="h5"><br>
<br>
On 10/3/2013 3:04 PM, Leszek Lesner wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div style="text-align:initial;color:rgb(31,73,125);font-size:initial;width:100%;font-family:Calibri,'Slate Pro',sans-serif">It is already
fixed for/in saucy</div>
<div style="text-align:initial;color:rgb(31,73,125);font-size:initial;width:100%;font-family:Calibri,'Slate Pro',sans-serif"><br style="display:initial">
</div>
<table style="border-spacing:0px" width="100%">
<tbody>
<tr>
<td colspan="2" style="text-align:initial;font-size:initial">
<div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in;font-family:Tahoma,'BB Alpha Sans','Slate Pro';font-size:10pt">
<div><b>Von: </b>John Hupp</div>
<div><b>Gesendet: </b>Donnerstag, 3. Oktober 2013 21:00</div>
<div><b>An: </b>Phill Whiteside</div>
<div><b>Cc: </b>Leszek Lesner;
<a href="mailto:lubuntu-users@lists.ubuntu.com" target="_blank">lubuntu-users@lists.ubuntu.com</a></div>
<div><b>Betreff: </b>Re: AW: zRAM broken on Raring?</div>
</div>
</td>
</tr>
</tbody>
</table>
<br>
<div style>
<div>Does that also mean that zram will
not be fixed in time for the Saucy release?<br>
<br>
On 10/3/2013 1:38 PM, Phill Whiteside wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I strongly suspect that the <span style="font-family:arial,sans-serif;font-size:13px"> the
'sudo parted -l' output of 'Error: /dev/zram1:
unrecognised disk label', has been around for quite some
time. I think it was found when people went digging into
the issue with zram freezing.</span>
<div> <span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">The
good news is that that particular error is not seen in
the 3.12rc1 and rc2 kernel that I ran as part of digging
into the freeze issue. I'm not completely sure if ubuntu
will be switching to this kernel for the 14.04 LTS. That
is a decision for the kernel team.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">Regards,</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">Phill.</span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 2 October 2013 20:11, John Hupp
<span dir="ltr"><<a href="mailto:lubuntu@prpcompany.com" target="_blank">lubuntu@prpcompany.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div>On 9/29/2013 4:17 AM, Leszek Lesner wrote:<br>
</div>
<blockquote type="cite">
<div>It can be disabled just like
any other upstart service. </div>
<div>Here is a short documentation
link: <a href="http://upstart.ubuntu.com/cookbook/#disabling-a-job-from-automatically-starting" target="_blank">http://upstart.ubuntu.com/cookbook/#disabling-a-job-from-automatically-starting</a></div>
<div><br>
</div>
<div>So renaming
/etc/init/zram-config.conf to
/etc/init/zram-config.donotstart should work
here.</div>
</blockquote>
<br>
</div>
Thanks, Leszek, this was the cleanest work-around.
Disabling the Upstart job means that the zram
configurations never run to begin with. <br>
<br>
And it doesn't leave anything dubious dangling (like
the 'sudo parted -l' output of 'Error: /dev/zram1:
unrecognised disk label').
<div>
<div><br>
<br>
<blockquote type="cite">
<div><br style="display:initial">
</div>
<table style="border-spacing:0px" width="100%">
<tbody>
<tr>
<td colspan="2" style="text-align:initial;font-size:initial">
<div>
<div><b>Von: </b>Nio Wiklund</div>
<div><b>Gesendet: </b>Sonntag, 29.
September 2013 10:11</div>
<div><b>An: </b>Leszek Lesner; John
Hupp; <a href="mailto:lubuntu-users@lists.ubuntu.com" target="_blank">lubuntu-users@lists.ubuntu.com</a></div>
<div><b>Betreff: </b>Re: AW: zRAM
broken on Raring?</div>
</div>
</td>
</tr>
</tbody>
</table>
<br>
<div>Hi Leszek,<br>
<br>
John has zRAM in Raring. It was pulled in by a
package he installed, and<br>
I try to help him switch it off.<br>
<br>
Probably it is better to do it in /etc/init.d,
but I am not familiar<br>
with that method, so I didn't suggest that
method. Please describe it,<br>
I'm reading and learning :-)<br>
<br>
Best regards<br>
Nio<br>
<br>
On 2013-09-29 10:03, Leszek Lesner wrote:<br>
> Honestlky I don't get the cronjob. Why is
it necessary? On reboot the<br>
> init system runs the stop command on
zram-config in /etc/init.d which<br>
> dies exactly the same as the cronjob
here.<br>
> <br>
> *Von: *Nio Wiklund<br>
> *Gesendet: *Sonntag, 29. September 2013
08:29<br>
> *An: *John Hupp; <a href="mailto:lubuntu-users@lists.ubuntu.com" target="_blank">lubuntu-users@lists.ubuntu.com</a><br>
> *Betreff: *Re: zRAM broken on Raring?<br>
> <br>
> <br>
> On 2013-09-29 02:23, John Hupp wrote:<br>
>> On 9/28/2013 12:23 PM, sudodus wrote:<br>
>>> Hi John,<br>
>>><br>
>>> Yes, let us hope the bug will be
fixed soon, and it will be<br>
>>> back-ported :-)<br>
>>><br>
>>> Can you run your application
without zRAM? You can switch it off in a<br>
>>> simple way (and have it ready for
reactivation) like this with crontab.<br>
>>> Edit the crontab with<br>
>>><br>
>>> sudo crontab -e<br>
>>><br>
>>> $ sudo crontab -l |tail -n3<br>
>>> # m h dom mon dow command<br>
>>> @reboot /sbin/swapoff /dev/zram*<br>
>>> @reboot /sbin/rmmod zram<br>
>>><br>
>>> Best regards<br>
>>> Nio<br>
>><br>
>> I set up a root crontab as you
suggested, Nio, and syslog confirms that<br>
>> the two crontab commands are run
after the zram setup commands.<br>
>><br>
>> But sudo parted -l still reports:<br>
>> Error: /dev/zram1: unrecognised disk
label<br>
>><br>
>> Does anyone know if the zram1 device
would be using memory (the setup<br>
>> command designated 512MB for zram on
this 1GB setup) or otherwise doing<br>
>> any harm?<br>
> <br>
> Hi John,<br>
> <br>
> The zRAM is not removed, only
de-activated. Only if zRAM is used already<br>
> '@reboot', when cron runs the command,
and there is no place to put the<br>
> content, then swapoff would fail (I
think).<br>
> <br>
> 1. Did you check with<br>
> <br>
> swapon -s<br>
> <br>
> This command should return no zram block
device.<br>
> <br>
> 2. Check the memory with<br>
> <br>
> free -m<br>
> <br>
> and install and run<br>
> <br>
> htop<br>
> <br>
> to check if something related to zram is
running or using memory.<br>
> <br>
> Best regards<br>
> Nio<br>
> <br>
> -- <br>
> Lubuntu-users mailing list<br>
> <a href="mailto:Lubuntu-users@lists.ubuntu.com" target="_blank">Lubuntu-users@lists.ubuntu.com</a><br>
> Modify settings or unsubscribe at:<br>
> <a href="https://lists.ubuntu.com/mailman/listinfo/lubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/lubuntu-users</a><br>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
<br>
--<br>
Lubuntu-users mailing list<br>
<a href="mailto:Lubuntu-users@lists.ubuntu.com" target="_blank">Lubuntu-users@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/lubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/lubuntu-users<br clear="all">
<div><br>
</div>
-- <br>
</a><a href="https://wiki.ubuntu.com/phillw" target="_blank">https://wiki.ubuntu.com/phillw</a>
</blockquote>
</div>
</div>
</blockquote>
<br>
<br>
</div>
</blockquote>
<br>
</div></div></div>
<br>--<br>
Lubuntu-users mailing list<br>
<a href="mailto:Lubuntu-users@lists.ubuntu.com">Lubuntu-users@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/lubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/lubuntu-users<br clear="all"><div><br></div>-- <br><a href="https://wiki.ubuntu.com/phillw" target="_blank">https://wiki.ubuntu.com/phillw</a>
</a>
</blockquote></div></div>