http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c1 --- Comment #1 from Stakanov Schufter --- Created attachment 773993 --> http://bugzilla.opensuse.org/attachment.cgi?id=773993&action=edit more detailed output dmesg from the same dmesg, maybe necessary -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c3 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(stakanov@freenet. |needinfo?(tiwai@suse.com) |de) | --- Comment #3 from Stakanov Schufter --- Created attachment 774048 --> http://bugzilla.opensuse.org/attachment.cgi?id=774048&action=edit dmesg (with sudo dmesg > file) hope that is the desired info how to I get hold on hwinfo output? Same in terminal as dmesg? BTW, I am left currently without wlan or eth and had to manualy delete resolve.conf to get it back with eth at least. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c5 --- Comment #5 from Takashi Iwai --- Thanks. At best, could you try to get the full kernel messages of the session showing the iwlwifi error (either from journalctl or messages archive). Also, you may try to toggle the power management option via iwconfig, too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c7 --- Comment #7 from Takashi Iwai --- Either the output of "journalctl -k" or /var/log/messages. With journalctl, you can pass like "-b -1" or "-b -2" to see the previous or the one earlier session. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c9 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai@suse.com) | --- Comment #9 from Stakanov Schufter --- Created attachment 774063 --> http://bugzilla.opensuse.org/attachment.cgi?id=774063&action=edit output journactl with -k as this is a new install, the -k -b -1 gave: Specifying boot ID or boot offset has no effect, no persistent journal was found. So hopefully that -k is what you need and want. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c11 --- Comment #11 from Stakanov Schufter --- Created attachment 774293 --> http://bugzilla.opensuse.org/attachment.cgi?id=774293&action=edit journalctl_-k_-r_right_after_accident I was going to send you the var/log/msg part but in that very moment I had another wlan crash. If you restart then you can connect to wlan (you need to restart) but then, wlan does not resolve dnd?? Or at least it seams so. Resolve.conf is not appearing different or altered. I join journalctl -k -r as I have made the journal persistent now. I will also post the var/log/msg of the day about which you asked (but as I do not know where to cut, i allow me the whole journal. Sorry for answering right now, but as akonadi decided to hide your mail until an akonadictl fsck, I saw your reply only today. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c16 --- Comment #16 from Stakanov Schufter --- Created attachment 774565 --> http://bugzilla.opensuse.org/attachment.cgi?id=774565&action=edit that is the log after the adviced restart of networkstack No difference, wlan is dead. You need to restart the entire system to get wlan back. Restart of the network stack, although it does not give error has no effect. What I did notice: when shutting down with sudo shutdown -r now, I get a warning about "dm-crypt not getting io control on the ssd" or similar. I tried to find these messages (that are repeated as scrolling message before the restart) in the logs, but eventually I do not know where to search. Again this event was after 2 h of idle time. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c18 --- Comment #18 from Stakanov Schufter --- I observed this behavior now for quite some time. Stable points are: a) the crash seems to appear only when beforehand the system was either suspended to disc or suspended to ram (long time idle). b) the crash is considering only and exclusively wlan functionality. It manifests in two varieties of "gravity". Or the wlan is visible, you can connect to it but it does not resolve addresses. Or the wlan hardware "disappears" right after the incident. c) when attaching an Ethernet cable, although the wlan remains not present, or not functional, you have flawless connection without any problem. I am writing this with exactly this situation. d) sometimes, but no always, the wlan disappearance is concomitant with a high system load and temperature which follow the event. Please let me know what I could do to find out the reason of this (which is present only in Leap 15. 42.2/3 were O.K. with wlan). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c20 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tiwai@suse.com) --- Comment #20 from Stakanov Schufter --- (In reply to Takashi Iwai from comment #19)

Could you double-check the latest Leap 42.3 kernel doesn't show this behavior? The leap 42.3 kernel should still work on Leap 15.0 user-space, too. Just install it via zypper in --oldpackage.

I'm asking this because Leap 42.3 kernel had already a bunch of iwlwifi backports. So it was far more than the stock 4.4.x kernel. If Leap 42.3 kernel still works and Leap 15.0 doesn't, we can narrow down the regression range, at least.

Just to be on the safe side (as I have never tried this). I have to register a 42.3 Repo (which is probably 42.3 update). Thereafter the syntax would be: sudo zypper in -from (name of the repo) --oldpackage nameofthepackage.rpm? Is this correct? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c23 --- Comment #23 from Stakanov Schufter --- Created attachment 775891 --> http://bugzilla.opensuse.org/attachment.cgi?id=775891&action=edit dmesg - wlan crash the same ssid shown twice dmesg and journalctl -k-r after crash with the standard kernel. I join this in the hope of some more info, the new is: when the wlan crashes the the wlan ssid is shown as connected with 0kb/s but it is shown a second time (non connected). Since I have only one wlan with that ssid, this might well be related, so maybe the two files give some insight. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c25 --- Comment #25 from Stakanov Schufter --- Created attachment 775924 --> http://bugzilla.opensuse.org/attachment.cgi?id=775924&action=edit Not able to update assoc_msk? Situation was: crash of wlan as usual. Wlan indicator blinks fast, disk aktivity led continues to work all the time. No wlan any more. impossible to shut down from the plasma desktop. Possible to shutdown from terminal with the known issue that the kernel complains about not being able to release the io_ctl from /dev/sda2. When I restarted no wlan from the very beginning: in the journal there was all red with the wlan complaining about not being able to change accoc_msk. I would also think about a hardware problem but as the card works without problems with the 4.4 kernel I would think that can be excluded. As long as you do not educate me otherwise. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c27 --- Comment #27 from Stakanov Schufter --- Today I started up the system and it did hang before it would start up to the desktop. I was able to switch to tty8 (as there during boot the messages seems to appear) and the line were: [ 17.750603] ACPI Warning: SystemIO range 0x0000000000001028-0x000000000000102F conflicts with OpRegion 0x0000000000001000-0x000000000000107F (\_SB.PCI0.LPC.PMIO) (20170303/utaddress-247) [ 17.750626] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.750630] ACPI Warning: SystemIO range 0x00000000000011C0-0x00000000000011CF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\_SB.PCI0.LPC.LPIO) (20170303/utaddress-247) [ 17.750634] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.750635] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\_SB.PCI0.LPC.LPIO) (20170303/utaddress-247) [ 17.750639] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.750640] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\_SB.PCI0.LPC.LPIO) (20170303/utaddress-247) [ 17.750644] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.750645] lpc_ich: Resource conflict(s) found affecting gpio_ich while the resource conflict affecting gpio_ich was the last line, the led of the wlan was flickering wildly. This lasted for about 20 - 30 seconds. Then the system started up, and as it started up the wlan stopped to flicker. Can it be that the new kernel does something different with ACPI settings and IO? After boot up the wlan worked normally, but of course after a long time idle situation it will crash. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c28 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tiwai@suse.com) --- Comment #28 from Stakanov Schufter --- Any update on this? Although it happens (with minor frequency after several hours of work, it happens much more frequently and faster (from 20 minutes to max 2 hours) after the system was previously suspended to disc and then awoken. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c30 --- Comment #30 from Stakanov Schufter --- This has changed characteristics as I have now seldom wlan crashes with the 4.12 kernel but now I experience shutdowns due to Core temp (in CPU1) of more then 112°C. This temperature problem is linked to the kernel and does not appear with the 4.4 kernel. And (a part of the temperature warning) I do not see any error message in the logs. With the 4.4 kernel and same charge I have a CPU Temp of 65°C with low ventilator activity and that corresponds to the normal (Lenovo has a somewhat low ventilation in Linux). The only difference AFAIK was an update of intel ucode. WLAN still crashes but just after having suspended the system, while this has become seldom due to constant emergency shutdown due to overheat. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c32 Vanista Herion changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vanista@gmail.com --- Comment #32 from Vanista Herion --- I have the same issue on a System 76 Galago Ultra Pro running Tumbleweed v20180917. Device: Intel Corporation Centrino Advanced-N 6235 (rev 24) Kernel: 4.18.7-1-default #1 SMP PREEMPT Sun Sep 9 10:26:20 UTC 2018 (952d850) x86_64 x86_64 x86_64 GNU/Linux Params: BOOT_IMAGE=/boot/vmlinuz-4.18.7-1-default root=UUID=c0af6a57-0eb7-4be7-809c-af53b6334a19 splash=silent resume=/dev/disk/by-label/Swap quiet pcie_aspm=force Symptoms are very similar although the crash can also be spontaneous while working. And nothing else than a full reboot will bring the interface back in working state. After the crash it shows up but it's unable to connect to anything. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c34 --- Comment #34 from Stakanov Schufter --- Created attachment 791562 --> http://bugzilla.opensuse.org/attachment.cgi?id=791562&action=edit dmesg output of wlan during recent crashes. Quite verbouse. Adding an attachment of a recent crashes. Since there are EXT4 problems in 4.19 I am using - trying to use - the default kernel and it crashes to my dismay with regularity. Joining output of dmesg. uname -a Linux roadrunner.suse 4.12.14-lp150.12.25-default #1 SMP Thu Nov 1 06:14:23 UTC 2018 (3fcf457) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1097605 http://bugzilla.opensuse.org/show_bug.cgi?id=1097605#c35 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #35 from Stakanov Schufter --- Linux roadrunner.suse 4.12.14-lp150.12.48-default #1 SMP Tue Feb 12 14:01:48 UTC 2019 (268f014) x86_64 x86_64 x86_64 GNU/Linux As of Leap 15 this does not happen any more. However since the last kernel update now he wlan does not wake up any more. You have to do a full restart. This happens 50 % of the time. Thus rendering hibernation nearly impossible / useless. I am opening a new bug for this and close this one. -- You are receiving this mail because: You are on the CC list for the bug.