Bug 39612
Summary: | radeon blocks with new style fencing | ||
---|---|---|---|
Product: | Drivers | Reporter: | Linas (linas_fi) |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | NEEDINFO --- | ||
Severity: | normal | CC: | alan, alexdeucher |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.6.2 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: |
Xorg log
Xorg log mieq Other Xorg log |
Description
Linas
2011-07-19 18:45:39 UTC
Please attach your xorg log and dmesg output. Does booting with radeon.no_wb=1 on the kernel command line in grub help? Created attachment 67342 [details]
Xorg log
Sorry for the delay. I'm attaching the file.
The radeon.no_wb=1 workaround does indeed work. Much appreciated.
Instead of showing only the mouse pointer (if lucky), shows the full screen again.
Is this still needing workarounds or can I close it ? Created attachment 84201 [details]
Xorg log mieq
Testing with 3.6.2, radeon.no_wb=1 is still needed, although it seems a bit better.
You can get -with a little difficulty- to switch virtual terminals, so it is possible to SIGINT the xserver. Interestingly, although the first startx leads to a blank screen, a second startx runs the DE without being apparently affected. ?!
Booting with radeon.no_wb=1 the DE shows directly the first time, as it should.
In one failed instance, the Xorg log showed errors of «[mi] EQ overflowing.», «[mi] EQ overflow continuing. 100 events have been dropped.», «[mi] EQ overflow continuing. 200 events have been dropped.»... I am attaching this log.
Created attachment 84211 [details]
Other Xorg log
Another failed Xorg log, this time without overflowing errors.
Is this still an issue with current kernels and userspace stack? I still have video problems, although causing a freeze at some random point*, rather than a black screen after boot. * Or you can make it deterministic by running something like /usr/lib/xscreensaver/kumppa ;) (In reply to Linas from comment #7) > I still have video problems, although causing a freeze at some random > point*, rather than a black screen after boot. Are you sure it's still the same problem? Does no_wb=1 still work around it? |