[Bug 817551] New: Loading of iwlwifi firmware is very slow
https://bugzilla.novell.com/show_bug.cgi?id=817551 https://bugzilla.novell.com/show_bug.cgi?id=817551#c0 Summary: Loading of iwlwifi firmware is very slow Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: tittiatcoke@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1492.0 Safari/537.36 SUSE/28.0.1492.0 After the recent update of systemd in Factory (to version 202), the loading of the iwlwifi firmware happens very late during the process. In my case, I have already logged into the KDE Desktop before the wireless is even activated. Checking dmesg, I get the following result: [ 1.953658] iwlwifi 0000:03:00.0: irq 40 for MSI/MSI-X [ 122.909870] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532 During the last two days I have been trying to find out the exact cause and if systemd is really to blame. Based on the changelogs I noticed that now udev is leaving the loading of the firmware up to the kernel. However this seems to have the above effect. When systemd is compiled however with "--with-firmware-path=/usr/lib/firmware", then the system behaves as expected and the wireless is up and running before the display manager becomes active. In this case dmesg shows: [ 9.816766] iwlwifi 0000:03:00.0: irq 40 for MSI/MSI-X [ 9.899872] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532 As said I am not sure if this is a kernel issue or that we should keep the ability to load firmware within udev. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c1
--- Comment #1 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c2
--- Comment #2 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c3
--- Comment #3 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c4
--- Comment #4 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c
FeiXiang Zhang
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c5
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c6
Cristian Rodríguez
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c7
--- Comment #7 from Cristian Rodríguez
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c8
--- Comment #8 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c9
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c10
Cristian Rodríguez
Christian,
So you mean that the network only becoming available after the desktop is loaded, is the right behavior ?? If that is the case, then I guess you and I have quite a different opinion about a working desktop. How would you expect that people would authenticate against an Active Directory/LDAP/Kerberos environment, if there is no network ??
It seems that at this moment the kernel is not ready for this and definitely doesn't support it the right way. Until that is fixed, this would be the only way to restore the correct functionality.
That you might not suffer from this, means that you are just lucky but don't rule out other users !!
The network interface comes up not after the desktop comes up, but after NetworkManager does.. driver autoload --> request_firmware --> interface up by NM/ifplugd.. the desktop has nothing do with this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c11
--- Comment #11 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c12
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c13
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c14
--- Comment #14 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c15
Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c16
--- Comment #16 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c17
--- Comment #17 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c18
--- Comment #18 from Robert Milasan
* We should retain the old behavior for some period of time (release or two) to allow older kernels still running on newer systems. This always worked and I see no reason to change that. There is nothing better for a random kernel developer to ask people reporting bugs to get back to their 12.1 kernel if the bug was present there already.
I agree and anyways firmware loading from udev has been enabled already in Factory. At least until all is fixed we can keep it like that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c19
Jiri Slaby
Few points: * I see perhaps the bug why it waits so long. I will build a fixed kernel for testing purposes. Let's see.
Well, could you test the kernel at: http://labs.suse.cz/jslaby/bug-817551/ ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=817551
https://bugzilla.novell.com/show_bug.cgi?id=817551#c20
Raymond Wooninck
http://bugzilla.novell.com/show_bug.cgi?id=817551
Franck Bui
participants (1)
-
bugzilla_noreply@novell.com