Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1186363
Summary: | kernel 3.18.3 breaks wifi | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Conrad S <conradsand.arma> |
Component: | kernel | Assignee: | fedora-kernel-wireless-iwl |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 21 | CC: | conradsand.arma, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-25 01:40:07 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1190933 | ||
Bug Blocks: |
Description
Conrad S
2015-01-27 14:36:32 UTC
Related bug: https://bugzilla.kernel.org/show_bug.cgi?id=92151 Please attach dmesg output from working and non-working kernel. This turned out to be a problem with ext4 in kernel 3.18. My /etc/fstab had journal_async_commit for the root partition. Apparently the journal_async_commit option cannot be enabled during a remount. As the root partition is already mounted by the time it reads /etc/fstab, the ext4 driver in 3.18 sees journal_async_commit and "helpfully" remounts root as read-only. This in turn causes wifi to break. This is arguably boneheaded behaviour on the part of the ext4 driver. The real fix is to have a more strict kernel patch review process, in order prevent such boneheaded behaviour ending up in the kernel. https://bugzilla.redhat.com/show_bug.cgi?id=1190933 I don't know how wifi problem could possibly depend on ext4 problem. Can we get info requested in comment 2 ? It's as simple as it sounds: ext4 has a bug which causes the root filesystem (/) to become read-only at boot. This in turn stops wifi connecting properly. I presume this is because NetworkManager (or a related subsystem) can't write to the root filesystem (maybe to the /etc directory?). By having journal_async_commit in /etc/fstab, I can reliably put the root filesystem into read-only at boot, and hence cause problems for wifi. Without journal_async_commit in /etc/fstab, wifi works properly. Removing journal_async_commit solves the issue for me, but it does point to the actual bug being in the ext4 driver. |