Bug 1599828

Summary: Things don't work properly(mount, Startx)
Product: [Fedora] Fedora Reporter: jamie <jamiemarchant47>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-17 01:01:31 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
Wrong log. none

Description jamie 2018-07-10 16:53:38 UTC 
Description of problem:
With the new kernel I can't run "Startx", mount and some other commands give me a "bad address" error. Startx gives an error about missing screens? Xinit and StartXFCE work but then NetworkManager does not work. 

Version-Release number of selected component (if applicable):
4.17.3-100.fc27.x86_64

How reproducible:
Allways 

Steps to Reproduce:
1. Start the new Kernal, try and "mount" a drive and you will get "bad address", also try and run StartX from a TTY(without X running automatically) 
2.
3.

Actual results:
As I said above. 

Expected results:
It works 

Additional info:
Comment 1 jamie 2018-07-10 18:19:30 UTC 
I've updated some of the dropdowns.
Comment 2 jamie 2018-07-10 18:21:04 UTC 
I've read somewhere that sometimes you have weird issues like that if you have a bad Busybox(which is part of Initframs, is that same package?)
Comment 3 jamie 2018-07-10 18:21:46 UTC 
Oops! Accidently changed the dropdowns again?
Comment 4 Laura Abbott 2018-07-10 19:15:29 UTC 
Can you share error logs for each of the problems you are reporting?
Comment 5 jamie 2018-07-10 20:15:14 UTC 
Created attachment 1457907 [details]
Wrong log.
Comment 6 jamie 2018-07-10 20:16:26 UTC 
Would the others things: NetworkManager, mount be in the journal?
Comment 7 jamie 2018-07-10 20:26:27 UTC 
That was the wrong one. I can't find the Xorg log with the error in it, but I did see it at the time? I'll get it for you when you tell me where to find the others.
Comment 8 jamie 2018-07-10 20:27:06 UTC 
(In reply to jamie from comment #7)
> That was the wrong one. I can't find the Xorg log with the error in it, but
> I did see it at the time? I'll get it for you when you tell me where to find
> the others.

If I can, it's hard cause I don't have working internet when using that kernel.
Comment 9 Justin M. Forbes 2018-07-23 15:06:32 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 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  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 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.
Comment 10 jamie 2018-07-24 14:22:17 UTC 
Still happens on newer kernels :(.
Comment 11 jamie 2018-11-17 01:01:31 UTC 
Fixed in 4.18.18-100.fc27.x86_64.