Bug 1010007

Summary:	New Kernel Fails To Identify Hardware and Freezes System
Product:	[Fedora] Fedora	Reporter:	KitchM <tech>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	19	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa, skottler
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:	2013-09-19 18:29:06 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:

Description KitchM 2013-09-19 16:57:51 UTC

Description of problem:
Just upgraded to 3.11.1-200.fc19 and found no improvement whatsoever.  The scanner does not work and software freezes up because of bad kernel support for hardware.

Version-Release number of selected component (if applicable):
3.11.1-200.fc19

How reproducible:
Always and forever

Steps to Reproduce:
1. Turn on scanner
2. Boot system with latest kernel
3. Run Simple Scan

Actual results:
System froze and required hardware reset.

Expected results:
Kernel should have found the hardware, and it should not have let the system freeze.

Additional info:
This has been going on for a year and needs to be addressed, IMHO.  If the kernel is not working correctly, then there will always remain a serious problem with the overall stability of the system.  That just stands to reason.  We cannot move forward with application issues until the basic system is stabilitzed.  Everything hinges upon this in an operating system.

I respectfully request that more people look more seriously at the kernel issues before moving forward on another Fedora version.

Thank you.

Comment 1 Josh Boyer 2013-09-19 18:29:06 UTC


*** This bug has been marked as a duplicate of bug 1000477 ***