On 09/21/2013 01:20 PM, Phill Whiteside wrote:
> Lars, 
>
> thanks for that.. can you update the bug.. there is the impossible
> part of pulling in something from the 3.12 kernel. Any reports we can
> give to the bug will hopefully assist the kernel team, as zram seems
> to fairly broken in the 3.11 kernel.
>
> Regards,
>
> Phill.
>
>
> On 21 September 2013 18:11, Lars Noodén <lars.noo...@gmail.com
> <mailto:lars.noo...@gmail.com>> 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
>
>     --
>     Mailing list: https://launchpad.net/~lubuntu-qa
>     <https://launchpad.net/%7Elubuntu-qa>
>     Post to     : lubuntu-qa@lists.launchpad.net
>     <mailto:lubuntu-qa@lists.launchpad.net>
>     Unsubscribe : https://launchpad.net/~lubuntu-qa
>     <https://launchpad.net/%7Elubuntu-qa>
>     More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> -- 
> https://wiki.ubuntu.com/phillw

First of all, Thanks for all the hard work, everyone. 

Do we know for sure if this issue is actually fixed in upstream
v3.12-rc1?  Lars, were you able to test and ISO with the test kernel
built in, or can you reproduce the bug just by booting into the test kernel?

Thanks,

Joe


-- 
Mailing list: https://launchpad.net/~lubuntu-qa
Post to     : lubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~lubuntu-qa
More help   : https://help.launchpad.net/ListHelp

Reply via email to