Re: [PATCH 5.15 000/374] 5.15.148-rc1 review

Re: [PATCH 5.15 000/374] 5.15.148-rc1 review

[Jon Hunter]

Hi Greg,

On 22/01/2024 23:54, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.148 release.
> There are 374 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 Wed, 24 Jan 2024 23:56:49 +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.148-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-5.15.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

...
  
> Douglas Anderson <dianders@chromium.org>
>      r8152: Choose our USB config with choose_configuration() rather than probe()


The above commit is causing a boot regression on the Tegra210 Jetson TX1
board and reverting this commit fixes it. This also happens with
linux-6.1.y, linux-6.6.y and linux-6.7.y. I am not seeing this on the
mainline.


Test results for stable-v5.15:
     10 builds:	10 pass, 0 fail
     28 boots:	26 pass, 2 fail
     74 tests:	74 pass, 0 fail

Linux version:	5.15.148-rc1-g59db9667b9d1
Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
                 tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
                 tegra20-ventana, tegra210-p2371-2180,
                 tegra210-p3450-0000, tegra30-cardhu-a04

Boot failures:	tegra210-p2371-2180


Looking at the console I am seeing the following panic ...

[    5.262192] r8152-cfgselector 2-1: reset SuperSpeed USB device number 2 using tegra-xusb
[    5.367566] r8152 2-1:1.0: load rtl8153a-3 v2 02/07/20 successfully
[    5.415902] r8152 2-1:1.0 eth0: v1.12.13
[    5.423122] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[    5.431970] Mem abort info:
[    5.434799]   ESR = 0x0000000086000004
[    5.438596]   EC = 0x21: IABT (current EL), IL = 32 bits
[    5.443963]   SET = 0, FnV = 0
[    5.447078]   EA = 0, S1PTW = 0
[    5.450254]   FSC = 0x04: level 0 translation fault
[    5.455160] [0000000000000000] user address but active_mm is swapper
[    5.461551] Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP
[    5.467830] Modules linked in:
[    5.470892] CPU: 2 PID: 120 Comm: kworker/2:3 Not tainted 5.15.147-00306-gfca62e959560 #8
[    5.479075] Hardware name: NVIDIA Jetson TX1 Developer Kit (DT)
[    5.484995] Workqueue: usb_hub_wq hub_event
[    5.489196] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    5.496163] pc : 0x0
[    5.498354] lr : usb_probe_device+0x34/0xb8
[    5.502548] sp : ffff80000aad3990
[    5.505863] x29: ffff80000aad3990 x28: ffff0000825810a8 x27: ffff80000a464958
[    5.513015] x26: ffff80000a3190f8 x25: ffff80000a34df50 x24: 0000000000000000
[    5.520163] x23: 0000000000000001 x22: 000000000000001d x21: ffff000082581000
[    5.527309] x20: ffff80000a34d1d0 x19: ffff80000a34d210 x18: 0000000000000000
[    5.534456] x17: 313a312d322f312d x16: 322f326273752f62 x15: 0000000000000001
[    5.541602] x14: 0000000000000002 x13: 00000000000777aa x12: 0000000000000001
[    5.548746] x11: 0000000000000028 x10: 0000000000000001 x9 : 0000000000000228
[    5.555892] x8 : 0101010101010101 x7 : 7f7f7f7f7f7f7f7f x6 : 000000000ef0212c
[    5.563038] x5 : 00ffffffffffffff x4 : ffff80000a34ef88 x3 : 0000000000000000
[    5.570184] x2 : ffffffffffffff00 x1 : 0000000000000000 x0 : ffff000082581000
[    5.577329] Call trace:
[    5.579777]  0x0
[    5.581619]  really_probe+0xb4/0x2e0
[    5.585208]  __driver_probe_device+0x7c/0x120
[    5.589570]  driver_probe_device+0x40/0x130
[    5.593757]  __device_attach_driver+0x94/0xe0
[    5.598120]  bus_for_each_drv+0x70/0xc8
[    5.601963]  __device_attach+0xfc/0x188
[    5.605803]  device_initial_probe+0x10/0x18
[    5.609993]  bus_probe_device+0x94/0xa0
[    5.613833]  device_add+0x4ac/0x838
[    5.617326]  usb_new_device+0x1e4/0x580
[    5.621167]  hub_event+0x918/0x1350
[    5.624658]  process_one_work+0x1f4/0x4c0
[    5.628675]  worker_thread+0x48/0x470
[    5.632342]  kthread+0x120/0x158
[    5.635579]  ret_from_fork+0x10/0x20
[    5.639166] Code: bad PC value
[    5.642224] ---[ end trace f266fb655cdbc485 ]---


Jon

-- 
nvpublic

Re: [PATCH 5.15 000/374] 5.15.148-rc1 review

[Greg Kroah-Hartman]

On Tue, Jan 23, 2024 at 03:35:24PM +0000, Jon Hunter wrote:
> Hi Greg,
> 
> On 22/01/2024 23:54, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.148 release.
> > There are 374 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 Wed, 24 Jan 2024 23:56:49 +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.148-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-5.15.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> ...
> > Douglas Anderson <dianders@chromium.org>
> >      r8152: Choose our USB config with choose_configuration() rather than probe()
> 
> 
> The above commit is causing a boot regression on the Tegra210 Jetson TX1
> board and reverting this commit fixes it. This also happens with
> linux-6.1.y, linux-6.6.y and linux-6.7.y. I am not seeing this on the
> mainline.

Ok, thanks for letting us know, I was a bit "worried" about these
changes, so I'll back them out and push out new -rc releases.   If the
ChromeOS developers want them backported, I'll let them provide a
working series.

thanks!

greg k-h