Summary: | [nvac] Nouveau drm causes failure to resume from suspend with any kernel newer than 2.6.36 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Daniel Lindgren <dali.spam> | ||||||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||||
Status: | RESOLVED INVALID | 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: |
|
Description
Daniel Lindgren
2011-09-02 00:03:22 UTC
Created attachment 50835 [details]
git bisect
Can you comment out nouveau_pm_init / nouveau_pm_fini calls from drivers/gpu/drm/nouveau/nouveau_state.c on e.g. 3.0 kernel and see if it fixes resume? And please attach dmesg output. Created attachment 50856 [details]
dmesg
(In reply to comment #2) > Can you comment out nouveau_pm_init / nouveau_pm_fini calls from > drivers/gpu/drm/nouveau/nouveau_state.c on e.g. 3.0 kernel and see if it fixes > resume? > > And please attach dmesg output. Tried it on 3.0.4, no difference. Attached dmesg, but be aware that I can't get any info from the computer after a failed resume until it has been rebooted. Ok. So this commit is unlikely to be the culprit. 2 another ideas: - does suspend/resume works at all without nouveau? - can netconsole catch anything after failed resume? (In reply to comment #5) > Ok. So this commit is unlikely to be the culprit. > 2 another ideas: > - does suspend/resume works at all without nouveau? > - can netconsole catch anything after failed resume? Blacklisted nouveau with 3.0.4, the screen is still black after resume but the machine is alive and I can ssh into it. No reboot. Netconsole didn't produce anything after resume. Verified that it worked by inserting a USB stick before resume, but nothing logged after. No ping responses either, the network's probably gone. Starting netconsole however changed the behaviour a bit, the machine reboots a little faster, about 20 seconds after I hit the power button to resume. Without netconsole it takes 40 seconds until it reboots. > Netconsole didn't produce anything after resume. Verified that it worked by
> inserting a USB stick before resume, but nothing logged after. No ping
> responses either, the network's probably gone.
I finally managed to get some output and there is a kernel panic, see attached netconsole.log.
Created attachment 50865 [details]
netconsole with kernel panic
1) If without nouveau you cannot resume properly, then your problems with nouveau are not nouveau fault. Maybe you could fiddle with some BIOS options and see how it will affect s/r. 2) Machine Check Exceptions report *hardware errors* - your hardware is probably dying. I have no idea why it started with kernel upgrade. (In reply to comment #9) > 1) If without nouveau you cannot resume properly, then your problems with > nouveau are not nouveau fault. Maybe you could fiddle with some BIOS options > and see how it will affect s/r. I've done that in the past, when the problems started with kernel 2.6.37. Couldn't find anything that improved the situation. > 2) Machine Check Exceptions report *hardware errors* - your hardware is > probably dying. > > I have no idea why it started with kernel upgrade. 1) Resume/suspend with any kernel older than 2.6.37 works without a hitch, no MCE. 2) Besides resume problems, the machine is rock solid with both older and newer kernels. 3) When nouveau is blacklisted, there is no MCE. The machine wakes but doesn't activate the monitor correctly, I can however ssh into the machine. 4) I have no problems with resume/suspend when running Windows 7 on the machine and no crashes either. Semms unlikely to me that if the hardware truly is faulty the only situation it ever shows up is when nouveau is loaded during a resume from suspend with a kernel newer than 2.6.36. It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report. In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one. Thanks, The Nouveau Team |
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.