Bug 1370795

Summary: Kernel 4.7.2-200: intermittent problems on i686
Product: [Fedora] Fedora Reporter: Bojan Smojver <bojan>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: gansalmon, ichavero, itamar, 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: 2016-09-08 00:17:04 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:
Attachments:
Description Flags
OOPS on the i686 VM after boot with the scratch kernel from bug #1370061 none

Description Bojan Smojver 2016-08-27 11:22:56 UTC 
Created attachment 1194741 [details]
OOPS on the i686 VM after boot with the scratch kernel from bug #1370061

Description of problem:
My i686 VM running on VMware ESX intermittently doesn't boot properly or hangs on reboot. Unfortunately, I don't have console access, so the only diagnostic I was able to capture was an OOPS in the journal.

Version-Release number of selected component (if applicable):
4.7.2-200

How reproducible:
Sometimes.

Steps to Reproduce:
1. Boot into this kernel or reboot with this kernel.
2. VM hangs.

Actual results:
VM hangs.

Expected results:
Kernel 4.6.7 work fine.

Additional info:
Comment 1 Bojan Smojver 2016-08-30 06:22:28 UTC 
Last time I had trouble with this VM was when Buslogic SCSI driver was modified. At that time, I asked the folks in charge of the host OS to switch my VM to LSI controller (mptbase/mptspi). I see there were some recent changes to the kernel in that part of the tree that are not present in 4.6.x.

I cannot judge what those changes are, but it would be good to know if anyone else can replicate the issue by moving their VMware config to LSI hardware and rebooting into 4.7.2.

Totally wild guess, of course...
Comment 2 Bojan Smojver 2016-09-01 09:05:10 UTC 
Here is what I've done in conjunction with ESX admins:

- VMware hardware was updated to version 8
- LSI SCSI controller was replaced with Paravirtual SCSI (i.e. mptbase/mptspi -> vmw_pvscsi)

The VM was booted into 4.7.2-201 kernel twice thus far, once with fsck performed on boot. Everything seems OK for now.

So, maybe it has something to do with LSI driver changes that are only present I. 4.7. Totally Wild guess, of course.
Comment 3 Bojan Smojver 2016-09-08 00:17:04 UTC 
Unable to replicate this at all since I switched to pvscsi. Now, whether that is what actually contributed, I cannot really test. So, closing.