Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1731029 > unrolled thread
| Started by | Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
|---|---|
| First post | 2017-09-12 19:00 +0200 |
| Last post | 2017-09-13 16:40 +0200 |
| Articles | 6 on this page of 26 — 6 participants |
Back to article view | Back to linux.kernel
[PATCH 4.4 00/31] 4.4.88-stable review Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:00 +0200
[PATCH 4.4 01/31] usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:00 +0200
[PATCH 4.4 26/31] btrfs: resume qgroup rescan on rw remount Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 15/31] mwifiex: correct channel stat buffer overflows Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 28/31] ALSA: msnd: Optimize / harden DSP and MIDI loops Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 05/31] USB: core: Avoid race of async_completed() w/ usbdev_release() Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 12/31] rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 04/31] usb:xhci:Fix regression when ATI chipsets detected Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 09/31] intel_th: pci: Add Cannon Lake PCH-LP support Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 06/31] staging/rts5208: fix incorrect shift to extract upper nybble Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 13/31] Bluetooth: Add support of 13d3:3494 RTL8723BE device Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 21/31] drm: adv7511: really enable interrupts for EDID detection Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 22/31] drm/bridge: adv7511: Fix mutex deadlock when interrupts are disabled Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 11/31] Input: trackpoint - assume 3 buttons when buttons detection fails Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 07/31] driver core: bus: Fix a potential double free Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 16/31] drm/nouveau/pci/msi: disable MSI on big-endian platforms by default Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 30/31] ARM: 8692/1: mm: abort uaccess retries upon fatal signal Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 18/31] cs5536: add support for IDE controller variant Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 03/31] usb: Add device quirk for Logitech HD Pro Webcam C920-C Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
[PATCH 4.4 23/31] drm/bridge: adv7511: Use work_struct to defer hotplug handing to out of irq context Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-12 19:20 +0200
Re: [PATCH 4.4 00/31] 4.4.88-stable review Shuah Khan <shuahkh@osg.samsung.com> - 2017-09-13 02:20 +0200
Re: [PATCH 4.4 00/31] 4.4.88-stable review Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-09-13 03:10 +0200
Re: [PATCH 4.4 00/31] 4.4.88-stable review Kevin Hilman <khilman@baylibre.com> - 2017-09-14 00:00 +0200
Re: [PATCH 4.4 00/31] 4.4.88-stable review Stephen Boyd <sboyd@codeaurora.org> - 2017-09-19 08:00 +0200
Re: [PATCH 4.4 00/31] 4.4.88-stable review Mark Brown <broonie@kernel.org> - 2017-09-19 13:20 +0200
Re: [PATCH 4.4 00/31] 4.4.88-stable review Guenter Roeck <linux@roeck-us.net> - 2017-09-13 16:40 +0200
Page 2 of 2 — ← Prev page 1 [2]
| From | Shuah Khan <shuahkh@osg.samsung.com> |
|---|---|
| Date | 2017-09-13 02:20 +0200 |
| Message-ID | <up3zk-8qb-7@gated-at.bofh.it> |
| In reply to | #1731029 |
On 09/12/2017 10:55 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.88 release. > There are 31 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Sep 14 16:52:38 UTC 2017. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.88-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.4.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah
[toc] | [prev] | [next] | [standalone]
| From | Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
|---|---|
| Date | 2017-09-13 03:10 +0200 |
| Message-ID | <up4lH-wf-1@gated-at.bofh.it> |
| In reply to | #1731029 |
On Tue, Sep 12, 2017 at 03:57:50PM -0700, kernelci.org bot wrote: > stable-rc/linux-4.4.y boot: 450 boots: 1 failed, 446 passed with 3 offline (v4.4.87-32-gb8c205d85576) > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ > > Tree: stable-rc > Branch: linux-4.4.y > Git Describe: v4.4.87-32-gb8c205d85576 > Git Commit: b8c205d855764e3db05a17ab4d03a19a5d609bdd > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 68 unique boards, 21 SoC families, 34 builds out of 203 > > Boot Regressions Detected: > > arm: > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > qcom-apq8064-cm-qs600: > lab-baylibre-seattle: new failure (last pass: v4.4.85-16-gcd99a4f3f43b) Is this a real failure? thanks, greg k-h
[toc] | [prev] | [next] | [standalone]
| From | Kevin Hilman <khilman@baylibre.com> |
|---|---|
| Date | 2017-09-14 00:00 +0200 |
| Message-ID | <upnRo-4qH-13@gated-at.bofh.it> |
| In reply to | #1731319 |
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes: > On Tue, Sep 12, 2017 at 03:57:50PM -0700, kernelci.org bot wrote: >> stable-rc/linux-4.4.y boot: 450 boots: 1 failed, 446 passed with 3 offline (v4.4.87-32-gb8c205d85576) >> >> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ >> Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ >> >> Tree: stable-rc >> Branch: linux-4.4.y >> Git Describe: v4.4.87-32-gb8c205d85576 >> Git Commit: b8c205d855764e3db05a17ab4d03a19a5d609bdd >> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 68 unique boards, 21 SoC families, 34 builds out of 203 >> >> Boot Regressions Detected: >> >> arm: >> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: >> qcom-apq8064-cm-qs600: >> lab-baylibre-seattle: new failure (last pass: v4.4.85-16-gcd99a4f3f43b) > > Is this a real failure? I tried to boot this a few more times, and it's still failing so it apprears it's a new regression. Added qcom maintainenrs to Cc to see if they have any ideas. These failures with CONFIG_PROVE_LOCKING seem to be more often related to bootloader issues with kernel size than actual CONFIG_PROVE_LOCKING, so I'm note exactly sure which is which here. Kevin
[toc] | [prev] | [next] | [standalone]
| From | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| Date | 2017-09-19 08:00 +0200 |
| Message-ID | <urjJE-6l-7@gated-at.bofh.it> |
| In reply to | #1731957 |
On 09/13, Kevin Hilman wrote: > Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes: > > > On Tue, Sep 12, 2017 at 03:57:50PM -0700, kernelci.org bot wrote: > >> stable-rc/linux-4.4.y boot: 450 boots: 1 failed, 446 passed with 3 offline (v4.4.87-32-gb8c205d85576) > >> > >> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ > >> Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.87-32-gb8c205d85576/ > >> > >> Tree: stable-rc > >> Branch: linux-4.4.y > >> Git Describe: v4.4.87-32-gb8c205d85576 > >> Git Commit: b8c205d855764e3db05a17ab4d03a19a5d609bdd > >> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> Tested: 68 unique boards, 21 SoC families, 34 builds out of 203 > >> > >> Boot Regressions Detected: > >> > >> arm: > >> > >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y: > >> qcom-apq8064-cm-qs600: > >> lab-baylibre-seattle: new failure (last pass: v4.4.85-16-gcd99a4f3f43b) > > > > Is this a real failure? > > I tried to boot this a few more times, and it's still failing so it > apprears it's a new regression. > > Added qcom maintainenrs to Cc to see if they have any ideas. > > These failures with CONFIG_PROVE_LOCKING seem to be more often related > to bootloader issues with kernel size than actual CONFIG_PROVE_LOCKING, > so I'm note exactly sure which is which here. > Usually when the kernel becomes too large we don't see any output on the console at all. That's because the decompressor overwrites something like the dtb or the initrd when it uncompresses the kernel and then serial console can't be found. In this case, it looks like it booted up and then got stuck when trying to run /init from the ramdisk? Or maybe it got stuck in some interrupt storm with mmc? There are some regulator warnings that seem to be ignored earlier for the mmc. [ 2.252965] s4: voltage operation not allowed [ 2.258505] mmci-pl18x 12400000.sdcc: Voltage switch failed No idea if that forebodes doom though. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
[toc] | [prev] | [next] | [standalone]
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Date | 2017-09-19 13:20 +0200 |
| Message-ID | <uroJk-4LH-3@gated-at.bofh.it> |
| In reply to | #1734666 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Sep 18, 2017 at 10:50:37PM -0700, Stephen Boyd wrote: > storm with mmc? There are some regulator warnings that seem to be > ignored earlier for the mmc. > [ 2.252965] s4: voltage operation not allowed > [ 2.258505] mmci-pl18x 12400000.sdcc: Voltage switch failed > No idea if that forebodes doom though. Those look like they're for MMC so I'd not expect them to result in silent boot, though they could be a warning that something else is wrong with the regulators I guess.
[toc] | [prev] | [next] | [standalone]
| From | Guenter Roeck <linux@roeck-us.net> |
|---|---|
| Date | 2017-09-13 16:40 +0200 |
| Message-ID | <upgZA-7n-17@gated-at.bofh.it> |
| In reply to | #1731029 |
On Tue, Sep 12, 2017 at 09:55:55AM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.88 release. > There are 31 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Thu Sep 14 16:52:38 UTC 2017. > Anything received after that time might be too late. > Build results: total: 145 pass: 145 fail: 0 Qemu test results: total: 115 pass: 115 fail: 0 Details are available at http://kerneltests.org/builders. Guenter
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.kernel
csiph-web