Bug 492461
| Summary: | Booting with nouveau.modeset=1 fails to start gdm | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> | ||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | airlied, ajax, awilliam, bskeggs, jturner, wally, wwoods | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-05-04 22:28:55 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
James Laska
2009-03-26 20:27:14 UTC
I've got a similar lockup; I tried booting into runlevel 3 (with modesetting on), ssh'ing in, and running 'telinit 5; tail -f /var/log/messages /var/log/Xorg.0.log'. System still hangs, but I've got some error messages: [drm] i2c and hpd detect differ: 0 vs 1 [drm] i2c and hpd detect differ: 0 vs 1 [drm] i2c and hpd detect differ: 0 vs 1 [drm] i2c and hpd detect differ: 0 vs 1 [drm] Allocating FIFO number 2 [drm] nouveau_fifo_alloc: initialised FIFO 2 [drm:nv50_display_command] *ERROR* timeout: 0x610300 = 0x80010081 [drm:nv50_display_command] *ERROR* timeout: 0x610300 = 0x80010885 [drm:nv50_display_command] *ERROR* timeout: 0x610300 = 0x8001089d [drm:nv50_display_command] *ERROR* timeout: 0x610300 = 0x80010881 ...[etc] lspci: 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400 GS (rev a1) drivers: kernel-2.6.29-9.fc11.x86_64 xorg-x11-drv-nouveau-0.0.12-16.20090326git01cee29.fc11.x86_64 Sounds similar to what I had happen with the Live CD with my Quadro 2700M nVidia hardware. James, Will - in both cases, is this happening only with KMS, and it works fine without KMS? (Also, Will, for my sanity can you include lspci -nn output - i.e. with the PCI ID - as well? I always go by the PCI ID when searching for duplicates etc. thanks!) James, you don't seem to have included any information about the hardware. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers from the wiki page, james appears to be reporting this with a Quadro FX 570, Smolt profile http://www.smolts.org/client/show/pub_94e555bc-c513-49a0-b2d8-1f3bc61300ec - James, please confirm (it's good to have this info in the bug as well as the Wiki page...) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Yes, this only happens with modeset on - I'm updating this bug from the machine in question. 01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS [10de:0422] (rev a1) thanks...guess we can assign for now. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #3) > James, Will - in both cases, is this happening only with KMS, and it works fine > without KMS? That is correct > James, you don't seem to have included any information about the hardware. Does the smolt URL provide sufficient information about the system? http://www.smolts.org/client/show/pub_94e555bc-c513-49a0-b2d8-1f3bc61300ec yep, that should be enough. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers How do things look here with the latest updates installed? Created attachment 342358 [details]
Rawhide Screenshot
I've reinstalled this system to rawhide today (previously F10) and it fails to boot post-install. The system hangs at the following screen. I'm not knowledgeable enough to determine the cause of the hang (nouveau, usb, acpi or OTHER). Any thoughts?
Retesting with -126 kernel (http://koji.fedoraproject.org/koji/buildinfo?buildID=100756). The reported issue no longer occurs :) Cool, thanks for testing! |