On Mon, 2025-08-25 at 12:03 +0200, Johannes Berg wrote: > On Sat, 2025-08-23 at 09:23 +0200, Ingolf Gehrhardt wrote: > > > > I think this might be because of: > > > > [ 31.404357] iwlwifi 0000:05:00.0: Detected Intel(R) Centrino(R) > > Wireless-N 1030 BGN > > [ 31.506140] iwlwifi 0000:05:00.0: loaded firmware version 18.168.6.1 > > 6000g2b-6.ucode op_mode iwldvm > > [ 32.002851] iwlwifi 0000:05:00.0: CONFIG_IWLWIFI_DEBUG enabled > > [ 32.002925] iwlwifi 0000:05:00.0: CONFIG_IWLWIFI_DEBUGFS enabled > > [ 32.002937] iwlwifi 0000:05:00.0: CONFIG_IWLWIFI_DEVICE_TRACING > > enabled > > [ 32.002949] iwlwifi 0000:05:00.0: Detected Intel(R) Centrino(R) > > Wireless-N 1030 BGN, REV=0xB0 > > [ 32.093060] iwlwifi 0000:05:00.0: Failing on timeout while stopping > > DMA channel 8 [0xa5a5a5a2] > > [ 32.111342] WARNING: CPU: 1 PID: 467 at > > drivers/net/wireless/intel/iwlwifi/dvm/eeprom.c:212 > > iwl_parse_eeprom_data+0x5ba/0xe20 [iwldvm] > > Probably, assuming you didn't see that WARN_ON before? Just making sure. > > It's almost certainly with the config rework, and the only thing I can > imagine is that the EEPROM size is now wrong, but I don't see why that > would be the case. > > Could you change it to print the offset, address and eeprom_size when > this happens? Or maybe even print them both with the older kernel too > when it succeeds. > > Or maybe you can even bisect it? > > There's a somewhat related bug > https://bugzilla.kernel.org/show_bug.cgi?id=220477 > but that just misses the entries which was easy to fix. That doesn't > seem to be the case here since the firmware is loaded. Actually there's a ticket [1] with precisely this issue too, so it may be better to handle everything there. [1] https://bugzilla.kernel.org/show_bug.cgi?id=220472 johannes
