Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1260157 - vmwgfx segfault when restarting NetworkManager
Summary: vmwgfx segfault when restarting NetworkManager
Keywords:
Status: CLOSED DUPLICATE of bug 1227193
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: x86_64
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: 2015-09-04 15:16 UTC by fulminemizzega
Modified: 2015-09-04 20:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-04 20:51:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
fresh f22 dmesg, kernel 4.0.4 (deleted)
2015-09-04 15:16 UTC, fulminemizzega 		no flags Details
fresh f22 journal, kernel 4.0.4 (deleted)
2015-09-04 15:17 UTC, fulminemizzega 		no flags Details
loginctl output (deleted)
2015-09-04 15:18 UTC, fulminemizzega 		no flags Details
updated f22 dmesg, kernel 4.1.6 (deleted)
2015-09-04 15:30 UTC, fulminemizzega 		no flags Details
updated f22 journal, kernel 4.1.6 (deleted)
2015-09-04 15:31 UTC, fulminemizzega 		no flags Details
View All

Description fulminemizzega 2015-09-04 15:16:23 UTC 
Created attachment 1070323 [details]
fresh f22 dmesg, kernel 4.0.4

Description of problem:
Fedora 22 Workstation inside VMWare Workstation on Windows (vers 10, 11 tested) has weird issues when restarting NetworkManager, dmesg shows segfault [...] in vmwgfx_dri.so. Restarting NetworkManager (or even issuing nmcli networking off) brings back to gdm login. I think the old session remains active, but I can't access to it, I need to login another time, by looking at loginctl. The issue is present both in fresh f22 install and also after dnf upgrade and reboot into new kernel.

Version-Release number of selected component (if applicable):
Fedora 22 Workstation
kernel-4.0.4-301.fc22
kernel-4.1.6-.fc22
VMWare Workstation 10, 11 for Windows

How reproducible: always


Steps to Reproduce:
1. Create a VM with VMware workstation 10 or 11 of F22 Workstation
2. Run systemctl restart NetworkManager (or nmcli networking off)
3. Check dmesg

Actual results: UI session is kicked back to login


Expected results: vmwgfx should not segfault when restarting nm...


Additional info: see attachments
Comment 1 fulminemizzega 2015-09-04 15:17:24 UTC 
Created attachment 1070324 [details]
fresh f22 journal, kernel 4.0.4
Comment 2 fulminemizzega 2015-09-04 15:18:13 UTC 
Created attachment 1070325 [details]
loginctl output
Comment 3 fulminemizzega 2015-09-04 15:30:29 UTC 
Created attachment 1070328 [details]
updated f22 dmesg, kernel 4.1.6

This is how I obtained this:
Started VM, login, systemctl restart NetworkManager
screen flickers, goes back to GDM, then back to previous session (I can see same terminal open). Then issuing again systemctl restart NetworkManager, back to GDM, trying to login but then displays stays black, back to TTY, login as root, restart GDM, then I'm able to get this. Same goes for following journal attachment.
Comment 4 fulminemizzega 2015-09-04 15:31:13 UTC 
Created attachment 1070329 [details]
updated f22 journal, kernel 4.1.6
Comment 5 fulminemizzega 2015-09-04 15:42:30 UTC 
Sorry, I missed one step:
Started VM, login, systemctl restart NetworkManager
screen flickers, goes back to GDM, *THEN* pressing Ctrl+Alt+F2 I'm able to go back to previous session.
I'm not able to do the same the second time, instead after pressing Ctrl+Alt+F2 I only get to an empty console.
Comment 6 Josh Boyer 2015-09-04 17:05:05 UTC 
Isn't this the same as bug 1227193 ?
Comment 7 fulminemizzega 2015-09-04 17:10:49 UTC 
Hello Josh,
it looks really similar, the only difference is that here I'm able to trigger it by restarting networkmanager or with nmcli (and I don't understand how the two things can be related). I'm going to update to F23 and test with kernel-4.2.0-1.fc23
Comment 8 fulminemizzega 2015-09-04 19:36:26 UTC 
Josh,
I'm sorry to have bothered you and the other maintainers, the issue I reported here is clearly gone, on fedora 23 with kernel 4.2.0-1.fc23 everything is ok.
You can close this bug.
Comment 9 Josh Boyer 2015-09-04 20:51:01 UTC 
No problem at all.  Thank you for reporting.

*** This bug has been marked as a duplicate of bug 1227193 ***
Note You need to log in before you can comment on or make changes to this bug.