Bug 517243
| Summary: | X nouveau livecd hangs on x86_64 machine | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Han Pingtian <phan> |
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | airlied, ajax, awilliam, bskeggs, davidz, dcantrell, mcepl, mcepl, mnowak, mszpak, riku.seppala, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-16 15:28:21 UTC | Type: | --- |
| 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
Han Pingtian
2009-08-13 07:53:48 UTC
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information especially concerning your hardware we require that will be helpful in our diagnosis of this issue. Try to boot into runlevel 3 and then run startx. When it crashes, please collect /var/log/Xorg.0.log, and the output of the program dmesg. Please attach them as SEPARATE uncompressed files to this bug. We will review this issue again once you've had a chance to attach this information. Thank you very much in advance. Created attachment 357387 [details]
the xorg log file
Could we get that output from dmesg as well, please? I need to clarify one thing. The system will hang after 'startx'. So it seems that I cannot get the outputs of 'dmesg'. Or, could you please give me some methods for getting the outputs? Thanks. It looks like this is the last logs after 'startx', come from the /var/log/messages: ... Aug 17 02:34:27 localhost kernel: nouveau 0000:00:05.0: Allocating FIFO number 1 Aug 17 02:34:27 localhost kernel: nouveau 0000:00:05.0: PFIFO_DMA_PUSHER - Ch 1 Aug 17 02:34:27 localhost kernel: nouveau 0000:00:05.0: nouveau_fifo_alloc: initialised FIFO 1 Aug 17 02:34:33 localhost kernel: fuse init (API version 7.12) Aug 17 02:34:38 localhost setroubleshoot: SELinux is preventing the ck-get-x11-serv from using potentially mislabeled files (.Xauthority). For complete SELinux messages. run sealert -l 04a1bdc9-043c-4ab2-8c7a-da91ad79608a Aug 17 02:34:44 localhost gnome-session[1695]: WARNING: Application 'gnome-panel.desktop' failed to register before timeout Aug 17 02:34:54 localhost gnome-session[1695]: WARNING: Application 'gnome-nautilus.desktop' failed to register before timeout Aug 17 02:35:00 localhost kernel: ALSA sound/pci/hda/hda_intel.c:1136: Too big adjustment 32 Aug 17 02:35:01 localhost kernel: ALSA sound/pci/hda/hda_intel.c:1136: Too big adjustment 32 .... I also see this, amd turon 64 x2 geforce go 7600. Also kernel hangs unless I boot with nouveau.modeset=0. Bug 513863. About dmesg... just type dmesg. Or dmesg >dmesg.txt ? btw, I think there is more info on the /var/log/Xorg.0.log if you start: startx -- -logverbose 5 Created attachment 357728 [details]
Xorg log from 'startx -- -logverbose 5' and 'nouveau.modeset=0' kernel option
With nouveau.modeset=0 in the kernel command line, the system still hangs after startx.
Created attachment 357729 [details]
dmesg before startx
I still don't know how to get the output of dmesg after 'startx'. This one is the outputs before we rung 'startx'.
You can just attach /var/log/messages, it should contain the messages from the time of the hang. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #9) > You can just attach /var/log/messages, it should contain the messages from the > time of the hang. > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers The messages in comment #5 are those messages. Thanks. Rawhide 20090822 seems to work for me. Tha same with NVidia GeForce 7300 SE, AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ and Fedora 11 x86_64. Confirmed with vanilla Fedora 11 and xorg-x11-drv-nouveau-0.0.12-40.20090528git0c17b87.fc11.i586 nv driver works fine (but the way how to switch back to nv driver isn't clearly defined). riku and marcin, you have different adapters, hence probably not the same bug. Please file separate bugs or else we're going to get very confused. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Filled bug 519227. Created attachment 360427 [details]
/var/log/messages and /var/log/Xorg.0.log in x86_64 livecd 20090909 after startx
The driver still doesn't work with testday-20090909-x86_64.iso livecd. Again, I drop into the 'level 3' and 'startx', then there only some colorful dots scattered on the display and the system hangs up.
Sep 21 10:14:01 dhcp-65-9 kernel: ------------[ cut here ]------------ Sep 21 10:14:01 dhcp-65-9 kernel: WARNING: at drivers/gpu/drm/drm_crtc_helper.c:950 drm_helper_initial_config+0x4d/0x7f [drm_kms_helper]() (Tainted: G W ) Sep 21 10:14:01 dhcp-65-9 kernel: Hardware name: OptiPlex 740 Enhanced Sep 21 10:14:01 dhcp-65-9 kernel: Connected connector with 0 modes Sep 21 10:14:01 dhcp-65-9 kernel: Modules linked in: nouveau(+) ttm drm_kms_helper drm i2c_algo_bit i2c_core Sep 21 10:14:01 dhcp-65-9 kernel: Pid: 127, comm: work_for_cpu Tainted: G W 2.6.31-33.fc12.x86_64 #1 Sep 21 10:14:01 dhcp-65-9 kernel: Call Trace: Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff810642ec>] warn_slowpath_common+0x95/0xc3 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff810643a7>] warn_slowpath_fmt+0x50/0x66 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffffa0047e59>] drm_helper_initial_config+0x4d/0x7f [drm_kms_helper] Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffffa005ef56>] nouveau_card_init+0xb9f/0xbc3 [nouveau] Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffffa005f373>] nouveau_load+0x3c2/0x3e3 [nouveau] Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffffa001cabc>] drm_get_dev+0x3b9/0x4d0 [drm] Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff81503f2f>] ? thread_return+0x4e/0xd3 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff8107bd8c>] ? do_work_for_cpu+0x0/0x50 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffffa009b4e6>] nouveau_pci_probe+0x28/0xb42 [nouveau] Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff81296e7f>] local_pci_probe+0x2a/0x42 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff8107bdb3>] do_work_for_cpu+0x27/0x50 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff810810f4>] kthread+0xac/0xb4 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff8101312a>] child_rip+0xa/0x20 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff81012a90>] ? restore_args+0x0/0x30 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff81081048>] ? kthread+0x0/0xb4 Sep 21 10:14:01 dhcp-65-9 kernel: [<ffffffff81013120>] ? child_rip+0x0/0x20 Sep 21 10:14:01 dhcp-65-9 kernel: ---[ end trace e826f98e2f432b5d ]--- 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.] (In reply to comment #17) > 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). > It seems that this bug has been fixed with the latest rawhide. Thanks. 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 Thank you for letting us know. |