Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com One thing I noticed this weekend. Time it took for 5.10.38/40 to reach testing from unstable: 7 days, despite this awful bug here. Time it took for 5.10.46 to reach testing from unstable: 20+ days and still counting.
Please do not mention freeze as an excuse. Debian has been in hard freeze since March, so I doubt that some "full freeze policy" has to do anything with it. Imho, one more release critical bug like this one would delay the release of bullseye even more, so you just marked it as important and let it be until it is "magically" solved one day. "Quality" testing... In other news, I asked an experienced linux user to have a look at my logs and he said there is nothing unusual. He also asked if there is a copy of /var/log/kern.log from those problematic boots, but unfortunately there is none right now. If I knew, I would have kept a copy. Once again, a random user offered me more support that the debian kernel team... on an issue that has to do with the kernel which is built from that team.
