<div dir="auto">Hi Karol.<div dir="auto"><br></div><div dir="auto">I sent the originsl report to Ben and LKML. Thorsten then added you, Lyude Paul and the dri-devel and nouveau lists. So you should have received this report on or about January 19.</div><div dir="auto"><br></div><div dir="auto">Chris</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 27 Jan 2023, 11:35 Karol Herbst, <<a href="mailto:kherbst@redhat.com" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">kherbst@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Where was the original email sent to anyway, because I don't have it at all.<br>
<br>
Anyhow, I suspect we want to fetch logs to see what's happening, but<br>
due to the nature of this bug it might get difficult.<br>
<br>
I'm checking out the laptops I have here if I can reproduce this<br>
issue, but I think all mine with Turing GPUs are fine.<br>
<br>
Maybe Ben has any idea what might be wrong with<br>
0e44c21708761977dcbea9b846b51a6fb684907a or if that's an issue which<br>
is already fixed by not upstreamed patches as I think I remember Ben<br>
to talk about something like that recently.<br>
<br>
Karol<br>
<br>
On Fri, Jan 27, 2023 at 12:20 PM Linux kernel regression tracking<br>
(Thorsten Leemhuis) <<a href="mailto:regressions@leemhuis.info" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">regressions@leemhuis.info</a>> wrote:<br>
><br>
> Hi, this is your Linux kernel regression tracker. Top-posting for once,<br>
> to make this easily accessible to everyone.<br>
><br>
> @nouveau-maintainers, did anyone take a look at this? The report is<br>
> already 8 days old and I don't see a single reply. Sure, we'll likely<br>
> get a -rc8, but still it would be good to not fix this on the finish line.<br>
><br>
> Chris, btw, did you try if you can revert the commit on top of latest<br>
> mainline? And if so, does it fix the problem?<br>
><br>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)<br>
> --<br>
> Everything you wanna know about Linux kernel regression tracking:<br>
> <a href="https://linux-regtracking.leemhuis.info/about/#tldr" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://linux-regtracking.leemhuis.info/about/#tldr</a><br>
> If I did something stupid, please tell me, as explained on that page.<br>
><br>
> #regzbot poke<br>
><br>
> On 19.01.23 15:33, Linux kernel regression tracking (Thorsten Leemhuis)<br>
> wrote:<br>
> > [adding various lists and the two other nouveau maintainers to the list<br>
> > of recipients]<br>
><br>
> > On 18.01.23 21:59, Chris Clayton wrote:<br>
> >> Hi.<br>
> >><br>
> >> I build and installed the lastest development kernel earlier this week. I've found that when I try the laptop down (or<br>
> >> reboot it), it hangs right at the end of closing the current session. The last line I see on the screen when rebooting is:<br>
> >><br>
> >> sd 4:0:0:0: [sda] Synchronising SCSI cache<br>
> >><br>
> >> when closing down I see one additional line:<br>
> >><br>
> >> sd 4:0:0:0 [sda]Stopping disk<br>
> >><br>
> >> In both cases the machine then hangs and I have to hold down the power button fot a few seconds to switch it off.<br>
> >><br>
> >> Linux 6.1 is OK but 6.2-rc1 hangs, so I bisected between this two and landed on:<br>
> >><br>
> >> # first bad commit: [0e44c21708761977dcbea9b846b51a6fb684907a] drm/nouveau/flcn: new code to load+boot simple HS FWs<br>
> >> (VPR scrubber)<br>
> >><br>
> >> I built and installed a kernel with f15cde64b66161bfa74fb58f4e5697d8265b802e (the parent of the bad commit) checked out<br>
> >> and that shuts down and reboots fine. It the did the same with the bad commit checked out and that does indeed hang, so<br>
> >> I'm confident the bisect outcome is OK.<br>
> >><br>
> >> Kernels 6.1.6 and 5.15.88 are also OK.<br>
> >><br>
> >> My system had dual GPUs - one intel and one NVidia. Related extracts from 'lscpi -v' is:<br>
> >><br>
> >> 00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05) (prog-if 00 [VGA controller])<br>
> >> Subsystem: CLEVO/KAPOK Computer CometLake-H GT2 [UHD Graphics]<br>
> >><br>
> >> Flags: bus master, fast devsel, latency 0, IRQ 142<br>
> >><br>
> >> Memory at c2000000 (64-bit, non-prefetchable) [size=16M]<br>
> >><br>
> >> Memory at a0000000 (64-bit, prefetchable) [size=256M]<br>
> >><br>
> >> I/O ports at 5000 [size=64]<br>
> >><br>
> >> Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]<br>
> >><br>
> >> Capabilities: [40] Vendor Specific Information: Len=0c <?><br>
> >><br>
> >> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00<br>
> >><br>
> >> Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-<br>
> >><br>
> >> Capabilities: [d0] Power Management version 2<br>
> >><br>
> >> Kernel driver in use: i915<br>
> >><br>
> >> Kernel modules: i915<br>
> >><br>
> >><br>
> >> 01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1) (prog-if 00 [VGA<br>
> >> controller])<br>
> >> Subsystem: CLEVO/KAPOK Computer TU117M [GeForce GTX 1650 Ti Mobile]<br>
> >> Flags: bus master, fast devsel, latency 0, IRQ 141<br>
> >> Memory at c4000000 (32-bit, non-prefetchable) [size=16M]<br>
> >> Memory at b0000000 (64-bit, prefetchable) [size=256M]<br>
> >> Memory at c0000000 (64-bit, prefetchable) [size=32M]<br>
> >> I/O ports at 4000 [size=128]<br>
> >> Expansion ROM at c3000000 [disabled] [size=512K]<br>
> >> Capabilities: [60] Power Management version 3<br>
> >> Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+<br>
> >> Capabilities: [78] Express Legacy Endpoint, MSI 00<br>
> >> Kernel driver in use: nouveau<br>
> >> Kernel modules: nouveau<br>
> >><br>
> >> DRI_PRIME=1 is exported in one of my init scripts (yes, I am still using sysvinit).<br>
> >><br>
> >> I've attached the bisect.log, but please let me know if I can provide any other diagnostics. Please cc me as I'm not<br>
> >> subscribed.<br>
> ><br>
> > Thanks for the report. To be sure the issue doesn't fall through the<br>
> > cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression<br>
> > tracking bot:<br>
> ><br>
> > #regzbot ^introduced e44c2170876197<br>
> > #regzbot title drm: nouveau: hangs on poweroff/reboot<br>
> > #regzbot ignore-activity<br>
> ><br>
> > This isn't a regression? This issue or a fix for it are already<br>
> > discussed somewhere else? It was fixed already? You want to clarify when<br>
> > the regression started to happen? Or point out I got the title or<br>
> > something else totally wrong? Then just reply and tell me -- ideally<br>
> > while also telling regzbot about it, as explained by the page listed in<br>
> > the footer of this mail.<br>
> ><br>
> > Developers: When fixing the issue, remember to add 'Link:' tags pointing<br>
> > to the report (the parent of this mail). See page linked in footer for<br>
> > details.<br>
> ><br>
> > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)<br>
> > --<br>
> > Everything you wanna know about Linux kernel regression tracking:<br>
> > <a href="https://linux-regtracking.leemhuis.info/about/#tldr" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://linux-regtracking.leemhuis.info/about/#tldr</a><br>
> > That page also explains what to do if mails like this annoy you.<br>
><br>
<br>
</blockquote></div>