| Summary: | [NVD9] GF119M boot hang with 3.15.2 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | sven <sven.pilz+freedesktop> | ||||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||
| Status: | RESOLVED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | ||||||||
| Version: | unspecified | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
Created attachment 102096 [details]
xorg log
The xorg backtrace has intel_drv.so in it. What makes you say this is a nouveau bug? (In reply to comment #2) > The xorg backtrace has intel_drv.so in it. What makes you say this is a > nouveau bug? I don't know if nouveau crashes the xserver. Should have stated that more clearly, sorry. This may be more a symptom that started to appear with the boot hangs and the error messages from the kernel driver. (In reply to comment #3) > (In reply to comment #2) > > The xorg backtrace has intel_drv.so in it. What makes you say this is a > > nouveau bug? > > I don't know if nouveau crashes the xserver. Should have stated that more > clearly, sorry. This may be more a symptom that started to appear with the > boot hangs and the error messages from the kernel driver. Ah. So the dmesg is from a perfectly-fine boot, yes? (Other than the error messages, which are probably not a big deal.) Can you bisect the boot hang? (Or at least get a dmesg from it, e.g. with netconsole) (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > The xorg backtrace has intel_drv.so in it. What makes you say this is a > > > nouveau bug? > > > > I don't know if nouveau crashes the xserver. Should have stated that more > > clearly, sorry. This may be more a symptom that started to appear with the > > boot hangs and the error messages from the kernel driver. > > Ah. So the dmesg is from a perfectly-fine boot, yes? (Other than the error > messages, which are probably not a big deal.) Yes. > Can you bisect the boot hang? (Or at least get a dmesg from it, e.g. with > netconsole) I now tried a couple of boots in a row and one of them actually succeeded (with glxgears and own OpenGL applications). But the other times it got stuck during boot, though not always before the switch to native resolution. One hanged with some systemd error (rfkill stuff). I will try to get more information. But it looks like there may be a couple of problems or everything is just a symptom of some deeper one. Which still is strange is that the symptoms disappear when I switch to the Intel card or Optimus in the BIOS. Maybe some ACPI problems and nothing directly related to nouveau. Sorry for bothering you with that :-). I guess you should close the bug and if I find something related to nouveau I'll open a new one. (In reply to comment #2) > The xorg backtrace has intel_drv.so in it. What makes you say this is a > nouveau bug? The bug (DRI_PRIME=1 ...) was indeed to the Intel driver (see Bug #80001) and is fixed in version 2.99.914. From the latest comments, doesn't sound like there was any nouveau issue at all in the first place. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 102095 [details] dmesg Hello everybody. I'm using a ThinkPad T420 with Optimus. Since 3.15 the boot hangs during KMS, when I use the discrete card (GF119M [Quadro NVS 4200M]). With the Intel card or Optimus, the system boots. Though I see those message from the kernel, also after standby: nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x002140 [ !ENGINE ] When I try to use the Nvidia card via PRIME with, the xserver crashes. I tested the PRIME way with: xrandr --setprovideroffloadsink nouveau Intel DRI_PRIME=1 glxgears