Bug 1319351 - kworker page allocation failure when changing external USB hard drive [NEEDINFO]
Summary: kworker page allocation failure when changing external USB hard drive
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1321481 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 23:15 UTC by txctest
Modified: 2016-10-26 16:46 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:46:57 UTC
Type: Bug
labbott: needinfo? (txctest)


Attachments (Terms of Use)
Kernel 4.4.3 errors (19.15 KB, text/plain)
2016-03-18 23:15 UTC, txctest
no flags Details
Kernel 4.3.x correct behavior (3.61 KB, text/plain)
2016-03-18 23:17 UTC, txctest
no flags Details
Kernel 4.4.6 errors (19.39 KB, text/plain)
2016-04-08 16:53 UTC, txctest
no flags Details

Description txctest 2016-03-18 23:15:19 UTC
Created attachment 1137904 [details]
Kernel 4.4.3 errors

Description of problem: After upgrading kernel to 4.4.2-301.fc23.x86_64 and later kernel reports an error:
kworker/6:x: page allocation failure: order:7, mode:0x208c020
after replacing external USB 3 hard drive. After that system will not recognize drive until the reboot. The same system had never had any issues with the same external USB drives with all kernel versions prior to 4.4.x (starting with Fedora 21 and kernel 4.3.x included).

Version-Release number of selected component (if applicable): 4.4.2-301.fc23.x86_64, 4.4.3-300.fc23.x86_64, 4.4.4-301.fc23.x86_64


How reproducible: always


Steps to Reproduce:
1. Power off existing external USB 3 hard drive.
2. Disconnect old drive and connect a new drive.
3. Power on newly connected USB 3 hard drive.

Actual results:


Expected results:


Additional info:

Comment 1 txctest 2016-03-18 23:17:53 UTC
Created attachment 1137905 [details]
Kernel 4.3.x correct behavior

This attachment contains kernel messages when system worked properly (kernels 4.3.x and older).

Comment 2 txctest 2016-03-18 23:25:03 UTC
Actual results: newly connected USB drive is not accessible.
Expected results: USB drive is available for use.

Comment 3 txctest 2016-04-08 16:53:56 UTC
Created attachment 1145192 [details]
Kernel 4.4.6 errors

As of kernel 4.4.6 error still persists and reboot required to access newly connected USB drive.

Comment 4 Laura Abbott 2016-04-08 22:19:39 UTC
Looks like there is a fix upstream https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=55ff8cfbc4e12a7d2187df523938cc671fbebdd1 . This should show up in the next stable release.

Comment 5 Laura Abbott 2016-04-18 21:30:09 UTC
*** Bug 1321033 has been marked as a duplicate of this bug. ***

Comment 6 Laura Abbott 2016-04-18 21:30:31 UTC
*** Bug 1321481 has been marked as a duplicate of this bug. ***

Comment 7 Laura Abbott 2016-09-23 19:30:29 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 8 Laura Abbott 2016-10-26 16:46:57 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.