Bug 1391473

Summary:	ibm t40p won't boot with 4.8.4 or 4.7.9, works with 4.7.,5 or older kernel
Product:	[Fedora] Fedora	Reporter:	jeff <jeff>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	gansalmon, ichavero, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-12 12:57:22 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 jeff 2016-11-03 12:01:29 UTC

Description of problem:

I have an ibm t40p notebook. It has been running fedora 20, 21, 22, 23 and 24 without issue. When I updated to 4.7.9 kernel, it would hand during boot. I got a flashing "_" and no other output. I tried 4.8.4 and I got the same hang. When i use the older kernel, 4.7.5, it works fine.

Version-Release number of selected component (if applicable):
4.8.4 and 4.7.9

How reproducible:
100%

Steps to Reproduce:
1. patch system
2. reboot
3. hang

Actual results:
system will not boot

Expected results:
system successfully boots

Additional info:

Comment 1 jeff 2016-11-03 12:03:14 UTC

This is a notebook from around 2002. It uses a pentium M, 1.6ghz.
It has 2gb of ram, and an ide hard drive.

Comment 2 Justin M. Forbes 2017-04-11 14:47:03 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  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 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 3 jeff 2017-04-12 01:15:06 UTC

Issue resolved with new kernel.

Comment 4 Justin M. Forbes 2017-04-12 12:57:22 UTC

Thanks for the update