| Summary: | rv790 oops when switching to fbcon after resume from sleep after hdmi became active. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Andy Furniss <adf.lists> | ||||
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | medium | ||||||
| Version: | XOrg git | ||||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
It seems that this only happens on the second mem sleep - so to trigger it looks like I need to boot with tv off, turn on tv but not enaable, sleep and resume, then sleep again will give oops. (In reply to comment #1) > It seems that this only happens on the second mem sleep - so to trigger it > looks like I need to boot with tv off, turn on tv but not enaable, sleep and > resume, then sleep again will give oops. More testing - To trigger this I need to resume from mem sleep after hdmi device became active that wasn't active at boot. It doesn't matter if it becomes active before I sleep of during sleep - when I come out of sleep I am then set up for the Oops. It seems that it's fbcon and nothing to do with sleeping again - I can now trigger just by switching from X to fbcon VT. I can't trigger this anymore with current drm-fixes |
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 81834 [details] oops hdmi RV790 running drm-next as it was on 260613 Have used echo mem > /sys/power/state for some time now, though I don't think this is a regression - just a situation that I haven't hit before. Haven't tested every senario but it seems that if I boot and use single DVI monitor then someone else turns on TV which is connected DVI -> hdmi then if I use mem sleep I get an oops. If the TV is on already when I boot it doesn't happen. I am not enabling the TV with xrandr as it's not me that is using it.