On Tue, Nov 16, 2021 at 09:41:07PM -0800, Scott Bruce wrote: > On 11/16/21 13:59, Scott Bruce wrote: > > On 11/16/21 07:01, Greg Kroah-Hartman wrote: > >> This is the start of the stable review cycle for the 5.15.3 release. > >> There are 927 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, 18 Nov 2021 14:24:22 +0000. > >> Anything received after that time might be too late. > >> > >> The whole patch series can be found in one patch at: > >> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.3-rc2.gz > >> > >> or in the git tree and branch at: > >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> linux-5.15.y > >> and the diffstat can be found below. > >> > >> thanks, > >> > >> greg k-h > >> > > > > Regression found on x86-64 AMD (ASUS GA503QR, Cezanne platform) > > somewhere between 7f9a9d5d9983 and 5.15.3-rc1. The very early -rc1 tag > > from a day and a half ago boots fine, -rc1 final and -rc2 boot into a > > kernel panic during init. > > > > Unfortunately I can't gather any useful debug info from the panic as the > > relevant bits are instantly pushed off the screen by rest of the dump. > > > > Here's what I'm left with on screen after the panic, hopefully someone > > can get something useful out of it: > > https://photos.app.goo.gl/6FrYPfZCY6YdnPDz6 > > > > I'll bisect and try to narrow this down some today but I'm running > > builds on my laptop while I work so it won't be super quick. > > > > Scott > > Reverting c3fc9d9e8f2dc518a8ce3c77f833a11b47865944 "x86: Fix > __get_wchan() for !STACKTRACE" resolves this issue. > > With this revert in place 5.15.3-rc2 boots successfully with no dmesg > regressions on my AMD Cezanne laptop, I'll wait for actual use > tomorrow to leave a proper > tested by. This is odd. Do you see the same issues in 5.16-rc1? We want this commit in here as we "need" bc9bbb81730e ("x86: Fix get_wchan() to support the ORC unwinder") because it fixes things that are reported to be broken. thanks, greg k-h
