Bug 1094763 - Kernel 3.14.x: highly unstable on my system causes kernel ooops'es and other output
Summary: Kernel 3.14.x: highly unstable on my system causes kernel ooops'es and other ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-06 12:43 UTC by Ali Akcaagac
Modified: 2014-09-15 23:16 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-15 23:16:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Gibb0r me Bug! (18.90 KB, text/x-log)
2014-05-06 12:43 UTC, Ali Akcaagac
no flags Details

Description Ali Akcaagac 2014-05-06 12:43:04 UTC
Created attachment 892853 [details]
Gibb0r me Bug!

Hi

I don't know whats up but I ran in heavy kernel issues with ALL 3.14.x versions. With 3.13.x I never ran into any issues.

A couple of days ago I md5sum'd all my files on an external hardisk. When I woke up during night to administrate the situation I figured out to get tons of issues spit out on my console. I didn't paid attention because I was more worried to cleanly unmount the harddisk - which I did. This happened with 3.14.1.

A couple of days ago 3.14.2 showed up and I assumed that this "issue" might have been solved and that I might not be the only one. Now today the same issues happened. Trying to access some stuff on the USB and voila. The same stuff being spit out. Again I was able to cleanly unmount the harddisk but this time with messages.log

Please have a look and if possible sent a fix. Again: I didn't had these issues with previous kernels 3.13.x and earlier.

Comment 1 Ali Akcaagac 2014-09-15 23:16:06 UTC
Closing this bug since 3.14.x got replaced by 3.16.x and the issues were gone.


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