Created an attachment (id=24816)
debug logs for patch v8
I applied the latest patch (v8) to my PPA against the current Jaunty package (2:2.6.3-0ubuntu9pitti1). Again I captured logs right after a clean X.org startup (startup.*), right after a monitor off/on cycle (not included, since no change), and a while after a VT switch.
I didn't see any underruns happen after switching off the monitor. Perhaps the effect during lunch break is that the monitor gets disabled by the screensaver (DPMS off), which acts more like a VT switch?
The underruns started some minutes after a real VT switch, and due to the new patch I get them logged now:
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
The attached logs have just one instance of those, but the underruns become more frequent now. After the first underrun happened, I got this change:
Created an attachment (id=24816)
debug logs for patch v8
I applied the latest patch (v8) to my PPA against the current Jaunty package (2:2.6. 3-0ubuntu9pitti 1). Again I captured logs right after a clean X.org startup (startup.*), right after a monitor off/on cycle (not included, since no change), and a while after a VT switch.
I didn't see any underruns happen after switching off the monitor. Perhaps the effect during lunch break is that the monitor gets disabled by the screensaver (DPMS off), which acts more like a VT switch?
The underruns started some minutes after a real VT switch, and due to the new patch I get them logged now:
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
(EE) intel(0): underrun on pipe A!
The attached logs have just one instance of those, but the underruns become more frequent now. After the first underrun happened, I got this change:
-(II): FBC_STATUS: 0x20000000
+(II): FBC_STATUS: 0x60000000
(vtswitch2.regs)