On 2018/07/25 22:57, Alexandre Ratchov wrote: > On Wed, Jul 25, 2018 at 05:10:05PM +0100, Stuart Henderson wrote: > > On 2018/07/25 15:26, Alexandre Ratchov wrote: > > > On Wed, Jul 25, 2018 at 11:56:04AM +0100, Stuart Henderson wrote: > > > > On 2018/07/25 12:00, Antoine Jacoutot wrote: > > > > > > I see the exact same issue as you do. > > > > > > I'll try with s/modesetting/intel and see if it improves things. > > > > > > > > > > OK I can already confirm this "fixes" the issue for me. > > > > > > > > It's been up for long enough now that I agree. > > > > > > > > For anyone else running into this, here is the xorg.conf stanza to > > > > switch (no other entries are needed in the file). > > > > > > > > Section "Device" > > > > Identifier "Intel Graphics" > > > > Driver "intel" > > > > EndSection > > > > > > > > > > Do you remember if the problem occurs with the modesetting driver if > > > you disable acceleration, ie you add: > > > > > > Option "AccelMethod" "none" > > > > > > to the "Device" section? > > > > > > > I hadn't tried that before. I just gave it a go, didn't see any freezes, > > but browser rendering was so slow as to be useless - Firefox took about > > 10 minutes to get to a state where I could interact with it (didn't help > > that the saved open tab was a complex map I suppose) and ~30 seconds to > > react to anything. chromium wasn't quite as bad, but I couldn't live > > with it. > > This is strange, firefox starts almost immediately on both of my > machines (~1.5s on the faster one, i5-2500K) , with: > > Section "Device" > Identifier "Card0" > Driver "modesetting" > Option "SWcursor" "on" > Option "AccelMethod" "none" > EndSection > > AFAIU, if AccelMethod is set to none, the device behaves like a bare > framebuffer (given "modern" memory speeds, this covers all desktop > needs, ex. mplayer uses ~6% CPU for a full-screen 720p movie). So, > what you observe may be unrelated to graphics. Which processes consume > CPU and appear to spin? >
With 'Driver modesetting / AccelMethod none' the busiest firefox process uses 100-200% cpu while it's loading saved tabs etc, and this takes ~10 minutes. With 'Driver intel' it loads the same tabs and starts responding in about 10 seconds. With no xorg.conf, so 'Driver modesetting' and default AccelMethod, it loads tabs and starts responding reasonably quickly (I'm not going back to it to check now, but probably also about 10 seconds), but I get freezes very often. Anyway unless somebody has a particular request that will help track down what's going on, I'll stick with intel, as it significantly reduces the risk of me wanting to hammer a screwdriver through the monitors (or, possibly worse, consider buying a Mac) if I'm trying to actually get anything done :)
