Description of problem: Trying to start a 2nd X session (did that on mga4 just a few weeks ago) results in seg fault Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Ctl+Alt+F2 2. login as another user 3. startx -- :1 Reproducible: Steps to Reproduce:
Created attachment 6864 [details] log file
BTW, running Linux 4.1.1 because I was having wireless issues after mga5 upgrade. See bug 16291
I can't reproduce this, but I'm not using the Intel driver (radeon here) and it looked like you are by quickly skimming your log. Also, upgrading the kernel could have an impact (does it still do the same with the Mageia 5 kernel?).
CC: (none) => thierry.vignaud
Well you're not running a mga kernel, so the issue may be there... Does it work with mga5 kernel?
Keywords: (none) => NEEDINFOSource RPM: (none) => kernel, x11-server-xorg, x11-driver-video-intel
I see these in my repository... $ ll media/core/release/*kernel* | grep laptop -rw-r--r-- 1 pfortin pfortin 39642948 Jan 18 2015 media/core/release/kernel-tmb-laptop-3.18.3-1.mga5-1-1.mga5.x86_64.rpm -rw-r--r-- 1 pfortin pfortin 7773328 Jan 18 2015 media/core/release/kernel-tmb-laptop-devel-3.18.3-1.mga5-1-1.mga5.x86_64.rpm -rw-r--r-- 1 pfortin pfortin 29134 Jan 18 2015 media/core/release/kernel-tmb-laptop-devel-latest-3.18.3-1.mga5.x86_64.rpm -rw-r--r-- 1 pfortin pfortin 29102 Jan 18 2015 media/core/release/kernel-tmb-laptop-latest-3.18.3-1.mga5.x86_64.rpm but, these don't show up in mcc... I only see 3.14 laptop kernels in the list... (Should I bug this? Could be a mirror race...) I believe the laptop packages are being (have been?) merged with the desktops; but never got around to checking that this wouldn't cause other problems (lid open/close, etc). However, trying to update stuff that was released this week, I ran into bug 16510... so I'll wait for that to be resolved before trying an mga5 kernel.
/var/log/messages contains: Aug 30 12:44:57 prf sensord: Chip: radeon-pci-0100 Aug 30 12:44:57 prf sensord: Adapter: PCI adapter Aug 30 12:44:57 prf sensord: Error getting sensor data: radeon/#0: Can't read Aug 30 12:44:57 prf sensord: sensor read error (-1) When I issue "startx -- :1" on pty2, I get this dumped into /var/log/messages: Aug 30 12:56:23 prf acpid: client 8083[0:0] has disconnected Aug 30 12:56:26 prf kernel: [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e Aug 30 12:56:26 prf kernel: [drm] PCIE gen 3 link speeds already enabled Aug 30 12:56:26 prf kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000000078C000). Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: WB enabled Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880807869c00 Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff880807869c04 Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff880807869c08 Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff880807869c0c Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff880807869c10 Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000076c98 and cpu addr 0xffffc90000836c98 Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and cpu addr 0xffff880807869c18 Aug 30 12:56:26 prf kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and cpu addr 0xffff880807869c1c Aug 30 12:56:26 prf kernel: [drm] ring test on 0 succeeded in 3 usecs Aug 30 12:56:26 prf kernel: [drm] ring test on 1 succeeded in 2 usecs Aug 30 12:56:26 prf kernel: [drm] ring test on 2 succeeded in 2 usecs Aug 30 12:56:26 prf kernel: [drm] ring test on 3 succeeded in 4 usecs Aug 30 12:56:26 prf kernel: [drm] ring test on 4 succeeded in 4 usecs Aug 30 12:56:26 prf kernel: [drm] ring test on 5 succeeded in 2 usecs Aug 30 12:56:26 prf kernel: [drm] UVD initialized successfully. Aug 30 12:56:26 prf kernel: [drm] ring test on 6 succeeded in 9 usecs Aug 30 12:56:26 prf kernel: [drm] ring test on 7 succeeded in 3 usecs Aug 30 12:56:26 prf kernel: [drm] VCE initialized successfully. Aug 30 12:56:26 prf kernel: [drm] ib test on ring 0 succeeded in 0 usecs Aug 30 12:56:26 prf kernel: [drm] ib test on ring 1 succeeded in 0 usecs Aug 30 12:56:26 prf kernel: [drm] ib test on ring 2 succeeded in 0 usecs Aug 30 12:56:26 prf kernel: [drm] ib test on ring 3 succeeded in 0 usecs Aug 30 12:56:26 prf kernel: [drm] ib test on ring 4 succeeded in 0 usecs Aug 30 12:56:26 prf kernel: [drm] ib test on ring 5 succeeded Aug 30 12:56:27 prf kernel: [drm] ib test on ring 6 succeeded Aug 30 12:56:27 prf kernel: [drm] ib test on ring 7 succeeded Aug 30 12:56:27 prf acpid: client connected from 6918[0:500] Aug 30 12:56:27 prf acpid: 1 client rule loaded Aug 30 12:56:27 prf acpid: client connected from 6918[0:500] Aug 30 12:56:27 prf acpid: 1 client rule loaded Aug 30 12:56:33 prf acpid: client 6918[0:500] has disconnected Aug 30 12:56:33 prf acpid: client 6918[0:500] has disconnected Aug 30 12:56:39 prf acpid: client connected from 8083[0:0] Aug 30 12:56:39 prf acpid: 1 client rule loaded Early in /var/log/Xorg.1.log, I see this: [ 2549.163] (EE) systemd-logind: failed to take device /dev/dri/card0: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [ 2550.043] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Sounds like I need to solve "permission denied", then go from there... suggestions where to look and/or what to adjust?
Nothing? Maybe due to having 2 graphics? System: Dell Precision M6800 i7-4710MQ CPU @ 2.50GHz 32GB RAM Video: [laptop display] Saturn XT [FirePro M6100] (AMD/ATI) Card:ATI Radeon HD 6400 and later (radeon/fglrx) [2nd] 4th Gen Core Processor Integrated Graphics Controller (Intel) Intel 810 and later Display: 1920x1080 Will attach Xlog.{0,1,diff} -- diff created after s/\n<timestamp>/\n/g
Created attachment 7029 [details] Xlog.0 (normal start -- w/o timestamps)
Created attachment 7030 [details] Xlog.1 (crashes -- w/o timestamps)
Created attachment 7031 [details] Xlog.diff (diff Xlog.0 Xlog.1) Note this: > (EE) systemd-logind: failed to take device /dev/dri/card0: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blo cked the reply, the reply timeout expired, or the network connection was broken. > (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied 40a43 > (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 11 paused 0 Got fd for card1 which is not in use...
Please reopen this bug report if you can reproduce this when using a Mageia kernel. Closing as invalid for now.
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => INVALID
Created attachment 7916 [details] crash log # uname -a Linux prf.pfortin.com 4.1.15-desktop-2.mga5 #1 SMP Wed Jan 20 17:05:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Keywords: NEEDINFO => (none)Assignee: bugsquad => tmb
Attachment 7029 is obsolete: 0 => 1
Attachment 7030 is obsolete: 0 => 1
Attachment 7031 is obsolete: 0 => 1
Attachment 6864 is obsolete: 0 => 1
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
resolved with official mga6
Status: REOPENED => RESOLVEDResolution: (none) => WORKSFORME