On 2022-02-04 01:19, Jason Self wrote: > The computer (amd64) fails to boot. The init was stuck at the > synchronization of the time through the network. This began between > 5.16.2 (good) and 5.16.3 (bad.) This continues on 5.16.4 and 5.16.5. > Git bisect revealed the following. In this case the nonfree firmwre is > not present on the system. Blacklisting the iwflwifi module works as a > workaround for now. I have several reports of Intel NUC 10th/11th gen not booting/crashing during boot after updating to 5.10.96 (from 5.10.91). At least one stack trace shows iwl_dealloc_ucode in the call path. The below commit is part of 5.10.96 So this regression seems to not only affect 5.16 series. Link: https://github.com/home-assistant/operating-system/issues/1739#issuecomment-1032013069 -- Stefan > > 6b5ad4bd0d78fef6bbe0ecdf96e09237c9c52cc1 is the first bad commit > commit 6b5ad4bd0d78fef6bbe0ecdf96e09237c9c52cc1 > Author: Johannes Berg <johannes.berg@xxxxxxxxx> > Date: Fri Dec 10 11:12:42 2021 +0200 > > iwlwifi: fix leaks/bad data after failed firmware load > > [ Upstream commit ab07506b0454bea606095951e19e72c282bfbb42 ] > > If firmware load fails after having loaded some parts of the > firmware, e.g. the IML image, then this would leak. For the > host command list we'd end up running into a WARN on the next > attempt to load another firmware image. > > Fix this by calling iwl_dealloc_ucode() on failures, and make > that also clear the data so we start fresh on the next round. > > Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx> > Signed-off-by: Luca Coelho <luciano.coelho@xxxxxxxxx> > Link: > > https://lore.kernel.org/r/iwlwifi.20211210110539.1f742f0eb58a.I1315f22f6aa632d94ae2069f85e1bca5e734dce0@changeid > Signed-off-by: Luca Coelho <luciano.coelho@xxxxxxxxx> > Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx> > > drivers/net/wireless/intel/iwlwifi/iwl-drv.c | 8 ++++++++ > 1 file changed, 8 insertions(+)
