Jeff, Thanks for testing and for the positive results from the PPA kernel. ccing the bug.
Regards Manoj Iyer On Tue, Aug 8, 2017 at 12:32 PM, Jeff Hugo <jh...@qti.qualcomm.com> wrote: > I tested the kernel from > https://launchpad.net/~centriq-team/+archive/ubuntu/lp1709123 on a > device which reproduced the issue 100% of the time in the first two > reboots of reboot stress testing. The SRU kernel was stable after 20 > reboots in a row. The SRU is validated. Boot log snippet showing > the kernel that was booted: > > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 0.000000] Linux version 4.10.0-30-generic > (buildd@bos01-arm64-043) (gcc version 5.4.0 20160609 (Ubuntu/Linaro > 5.4.0-6ubuntu1~16.04.4) ) #34~lp709123+build.1-Ubuntu SMP Mon Aug 7 > 18:13:24 UTC 2017 (Ubuntu 4.10.0-30.34~lp709123+build.1-generic > 4.10.17) > [ 0.000000] Boot CPU: AArch64 Processor [510f8000] > > Jeffrey Hugo > Senior Engineer > Qualcomm Datacenter Technologies, Inc. > 1-303-247-5002 > > -----Original Message----- > From: bandera-external-boun...@lists.canonical.com > [mailto:bandera-external-boun...@lists.canonical.com] On Behalf Of > Timur Tabi > Sent: Monday, August 07, 2017 12:49 PM > To: Manoj Iyer <manoj.i...@canonical.com> > Cc: bandera-exter...@lists.canonical.com > Subject: Re: regarding Pl011 patch for public bug# 1709123 > > On 08/07/2017 12:01 PM, Manoj Iyer wrote: >> Timur, >> >> Couple things wrt https://launchpad.net/bugs/1709123, >> >> 1. I backported your pl011 patch to 4.10, is there any additional >> patch that I need to pull in for 4.10? >> >> backported from linux-next commit >> 37ef38f3f83891a2f413fb872bae7d0f9bb95b27 tty: pl011: fix >> initialization order of QDF2400 E44 > > I presume you already have these: > > tty: pl011: fix earlycon work-around for QDF2400 erratum 44 > tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 > >> 2. I will get a kernel built today, and post a request to test on >> the >> public bug. Would you be able to verify that on a system with the FW >> HW configuration that it is known to fail and report back your test >> results in the bug ref? so that I can submit the SRU ? > > Sure. > > -- > Bandera-external mailing list > bandera-exter...@lists.canonical.com > Modify settings or unsubscribe at: > https://lists.canonical.com/mailman/listinfo/bandera-external > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709123 Title: [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware and 1.1 silicon Status in linux package in Ubuntu: Triaged Bug description: [Impact] Another bug was found in the pl011/spcr code that implements the work-around for erratum E44. This erratum affects QDF2400 v1.1 silicon. The software bug is only exposed when using Firmware 2.0 or later (estimated release October 2017). To ensure compatibility with future firmware, the Ubuntu kernel should apply the aforementioned patch. Without this patch, customers using the 2.0 firmware and 1.1 silicon might not have a functional UART console, either sometimes or always. It is expected that this problem does not occur with 2.0 or later silicon. [Test Case] Upgrade firmware to v2.0 on a QDF2400 server with 1.1 silicon, and the kernel should fail to boot, with the patch applied, we should see no boot failure. [Fix] Following patch in linux-next fixes this issue: 37ef38f3f838 tty: pl011: fix initialization order of QDF2400 E44 [Regression Potential] This is a bug fix to tty driver and limited to qdf2400. Low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
