On Sun, May 28, 2023 at 02:35:18PM -0400, beld zhang wrote: > ---------- Forwarded message --------- > From: beld zhang > Date: Sun, May 28, 2023 at 2:07 PM > Subject: Re: 6.1.30: thunderbolt: Clear registers properly when auto > clear isn't in use cause call trace after resume > To: Mario Limonciello > > On Sun, May 28, 2023 at 8:55 AM Mario Limonciello > <mario.limonciello@xxxxxxx> wrote: > > > > This is specific resuming from s2idle, doesn't happen at boot? > > > > Does it happen with hot-plugging or hot-unplugging a TBT3 or USB4 dock too? > > > > In addition to checking mainline, can you please attach a full dmesg to > > somewhere ephemeral like a kernel bugzilla with thunderbolt.dyndbg='+p' > > on the kernel command line set? > > > > 6.4-rc4: > *) test 1~4 was done with usb hub with ethernet plugged-in > model: UE330, usb 3.0 3-port hub & GIgabit Ether adapter > a rapoo wireless mouse in one of the ports > 1) no crash at boot > until [169.099024] > 2) no crash after plug an extra usb dock > from [297.004691] > 3) no crash after remove it > from [373.273511] > 4) crash after suspend/resume: 2 call-stacks > from [438.356253] > 5) removed that hub(only ac-power left): NO crash after resume > from [551.820333] > 6) plug in the hub(no mouse): NO crash after resume > from [1250.256607] > 7) put on mouse: CRASH after resume > from [1311.400963] > mouse model: Rapoo Wireless Optical Mouse 1620 > > sorry I have no idea how to fill a proper bug report at kernel > bugzilla, hope these shared links work. > btw I have no TB devices to test. > > dmesg: > https://drive.google.com/file/d/1bUWnV7q2ziM4tdTzmuGiVuvEzaLcdfKm/view?usp=sharing > > config: > https://drive.google.com/file/d/1It75_AV5tOzfkXXBAX5zAiZMoeJAe0Au/view?usp=sharing <formletter> This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for how to do this properly. </formletter>
