Kernel panic on wifi connection

Hello,

I’ve faced strange issue. I’ve changed network password on my wifi. I’ve added some special characters and now every time I connect to wifi after 1-5minutes it crashes (my caps lock is blinking and OS is basically dead). I see nothing in journal after reboot, to be honest I don’t know how to debug it. Any ideas on how to approach this problem? I’m attaching some details, I’m not adding logs as there is nothing there.

To add more context, I’ve just connected to wifi using hotspot that has password with letters and digits only - it’s working for longer than 15 minutes. On the other hand wifi connection is working fine on mobile phones, other laptop - I see cause within my OS.

It’s working on eth connection without any errors.

lsb_release -a

LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
Distributor ID: openSUSE
Description: openSUSE Leap 15.0
Release: 15.0
Codename: n/a

uname -a

Linux home 4.12.14-lp150.12.82-default #1 SMP Tue Nov 12 16:32:38 UTC 2019 (c939e24) x86_64 x86_64 x86_64 GNU/Linux

lspci | egrep -i ‘network|ethernet’

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM (rev 04)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)

lshw -class network

*-network
description: Ethernet interface
product: Ethernet Connection I218-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: em1
version: 04
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.6-3 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:49 memory:f7c00000-f7c1ffff memory:f7c3c000-f7c3cfff ioport:f080(size=32)
*-network
description: Wireless interface
product: Wireless 7260
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlan0
version: 73
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.12.14-lp150.12.82-default firmware=17.3216344376.0 ip=192.168.43.85 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:47 memory:f7a00000-f7a01fff

@OpenSusek:

Are your special characters conforming to these rules?

  • Alphabetic characters “a-z” and “A-Z”.
  • Numbers “0-9”.
  • Spaces.
  • Additional characters: “_ - ! " # $ % & ’ ( ) * + , . / : ; < = > ? @ \ ] ^ ´ { | } ~”.

Characters which are not allowed include:

  • Mutated vowels, such as “ß ü ö ä Ü Ö Ä”.
  • Special characters, such as “§ ` µ „ “ ” € ¢ © ¶ ® ² ³ ° ^”

Hi,

Yes, my characters are only from legit pool. To be more precise besides alphabetic characters and numbers only one special is “@”.

@OpenSusek:

OK. Then, for the misbehaving Laptop, try a very simple password – the minimum your WiFi base station allows – something like “1234AbCd” (8 characters).
And then, a very long (63 characters) simple password – for example “12345678 abcdefgh 87654321 ABCDEFGH qwertyui ZXCVBNML asdfghjk0”.

Does the misbehaving Laptop have the newest BIOS/UEFI for that hardware?
Is the package “kernel-firmware” up-to-date?

Please inspect the systemd Journal to determine which ‘7260’ firmware has been loaded to the Intel Wireless Interface.
Please check which driver is being used by the Intel Wireless Interface: “lspci -s 02:00.0 -v”.

And,
If you are reasonably sure you can replicate the problem (You’re pretty sure it happens nearly all the time within 5 minutes of connecting),
You can also view your system log entries in real time for those 5 minutes…

journalctl -f

TSU