I've installed F12 and updated to the latest version and I think that I have an issue with the Xorg-server. In random time, I got black screen, no mouse and no keyword works, but the OS works because I can connect from another machine using SSH. I tried using GNOME and KDE and it freezes in both cases. I have an Nvidia card and I've tried with nomodeset and without it. Thanks Salu2... masch...
Created attachment 365826 [details] Logs from the Xorg and messages
There were many changes in nouveau driver, probably one of them broke this (assuming it worked in Fedora 11). On a quick look, I don't see anything useful in the logs, but I leave to the developers to judge and eventually request more info...
How can I contact with them? or Do I need to wait them?
Sort of. Ben, are you reading this?
Reporter, since you want to help to debug this issue, it would be good to provide some more information. 1) Did it already happen in Fedora 11 or is it Fedora 12 specific? 2) Does your card work with "nv" driver?
When exactly are those logs from? Could you wait until the problem happens, then reboot to runlevel 3 (console mode), take a copy of the logs at that point, and attach *those*? Also, an indication of the time (on your system) when the crash happened will be useful, then we know where to look in /var/log/messages . This bug is assigned to Ben Skeggs, who is one of the lead nouveau developers. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I've using Fedora 11 and there was problem, this only happens in Fedora 12. I've tried with nv and I can't start X Server, please see the log Xorg.0.log.nv. I've tried with vesa and I get the issue with nouveau, at first time it works but after a 50 minutes I get blank screen. I attached the new logs for the condition you told me.
Created attachment 365978 [details] Xorg.0.log.nv
Created attachment 365979 [details] Xorg.0.log.vesa
Created attachment 365980 [details] messages log
sorry, I forgot to mention that with nv driver does not start X.
Please take a look on the Xorg backtrace.
Created attachment 365982 [details] Xorg backtrace
I don't know if it helps, but if I checked the process status when the machines doesn't respond, the Xorg process gets almost 100% usage of CPU and the keyword doesn't respond. If I kill the Xorg process the keyword starts to respond but I can't open any terminal using the keyword shortcuts (ALT+CTRL+F1...F2..F3.....F12).
Ben, just to be clear: I think you only need to look at the backtrace in comment #13, the rest can be ignored. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I've tested it with nv driver and with the nomodeset kernel option and I got the the same issue, please view the Xorg NV backtrace.
Created attachment 366440 [details] Xorg NV backtrace
Seems like the backtrace is in evdev both times. Re-assigning to evdev for now. Ben, does this seem sensible to you?
Apparently not. Edited highlights of discussion with ajax: <ajax> adamw: if you ever see PostMotionEvent -> mieqEnqueue -> xorg_backtrace, it is _not_ the input driver at fault. <ajax> adamw: that's the input core politely telling you "hey, we've been getting a lot of input events and not processing them, we're probably stuck waiting for the hardware" <ajax> which, indeed, you're in XAACopyArea, which is the accelerated copy path [ed. note: ajax is referring to the nv backtrace here] <ajax> the nouveau backtrace looks... different. <adamw> ajax: hmm, and the nouveau backtrace is in something completely different <adamw> ajax: so looks like he ran into two different bugs on the same hardware. fun! so, this goes back to nouveau for now, since it looks like the failure on nv is just coincidental and we're not caring about nv any more. It would be good if you could _really_ test with vesa as well, though, Mario (remember the last time you tried to do this it seems like you didn't manage it at all, and it was still using nouveau). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
so we discussed this on IRC yesterday. Reporter's /var/log/messages is http://pastebin.com/m6f073582 . Note the big kernel trace that starts at: Oct 28 22:32:58 pelotiux kernel: 8>] ? default_wake_function+0x0/0x12 and runs all the way down to the bottom. Comments from airlied and ben: Oct 28 18:56:43 <airlied> masch: oh stuck in the video bios not good Oct 28 18:57:16 <airlied> not sure what we can do there. Oct 28 18:57:37 <airlied> I think this is possible an escalate to ajax issue. Oct 28 18:57:51 <airlied> it might be a bug in the int10 emulation Oct 28 18:58:12 <airlied> we should file the vesa bug with that backtrace in it Oct 28 18:58:25 <airlied> and see if ajax can take a look. Oct 28 18:58:33 <airlied> might be worth attaching the bios to it Oct 28 18:58:40 <darktama> would this emulate int10 though? being x86 wouldn't vm86 mode get used? Oct 28 18:59:15 <airlied> I'm not sure I think we always do emulate now in fedora Oct 28 18:59:15 <darktama> ah Oct 28 18:59:27 <airlied> --with-int10=x86emu Oct 28 18:59:34 <airlied> suggests so Re-assigning to vesa and ajax on the basis of that conversation. I'm not sure how the reporter should 'attach the BIOS', Dave or Adam please explain that if it's needed. Thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 366734 [details] kernel trace from reporter
I know I shouldn't use the NVIDIA proprietary drivers, but I installed the version 190.42 and I don't have this issue. Please, feel free to ask me any test for nouveau driver. I will use proprietary drivers until I got this fix.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I've reinstalled F12 with final release and the latest updates and it happened again, I have the black screen issue. I've attached the logs.
Created attachment 372748 [details] message backtrace
Created attachment 372749 [details] xorg log
Is F13/F14 any better?
Sorry, now I have another video card, I do not have GeForce 7950 card any more. salu2... masch...
Ok, thanks for letting me know :)