| Bug ID | 89619 |
|---|---|
| Summary | Chrome crashes in 64 bit r600 driver while running google maps |
| Product | Mesa |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/r600 |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | jrpstonecarver@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Sorry folks, I am new to this and will do my best. I first reported this bug to Google. They got all the data here: https://code.google.com/p/chromium/issues/detail?id=467821 and told me that this is a bug in the r600 driver. Back in December I updated from 32 bit Ubuntu 12.04 to 64 bit Ubuntu 14.04 and have had major stability issues with Chrome ever since, particularly while using Google Maps. This URL https://www.google.com/maps/place/Los+Gatos,+CA+95033/@37.1893925,-121.9894751,11z/data=!4m2!3m1!1s0x808e39d2fbec72d9:0x4b03e7246671be9b was the first time I've managed to capture something that crashes chrome reliably, however. At their suggestion I tried running chrome with --disable-gpu and at least with a simple test the problem went away. I think these drivers are the default in Ubuntu now, but they seem to be causing me a lot of grief. You can pickup what Google got from the crash report Chrome sent to them from the bug listed above. And for the time being I will figure out how to run with --disable-gpu on all the time to see if that avoids my issue. Failing that I guess it's time to figure out how to go back to ATI's drivers. If there is additional data I can provide somehow, I am happy to try. I'm no wizard, but I will follow instructions and get whatever you need if possible. Thanks.
From the chrome bug report Driver vendor Mesa Driver version 10.1.3 10.1 was released over a year ago. A lot of bugs have been fixed since then. Can you try a more recent version? 10.5.1 was released recently.
(In reply to Ilia Mirkin from comment #1) > From the chrome bug report >=20 > Driver vendor Mesa > Driver version 10.1.3 >=20 > 10.1 was released over a year ago. A lot of bugs have been fixed since= then. > Can you try a more recent version? 10.5.1 was released recently. To be brutally honest, I'm not sure. 14.04 is an LTS release that is suppos= ed to be supported for 2 years at least, and possibly 5. And it is using the default driver that Ubuntu makes available, not one of my particular choice= . If Ubuntu supplied an update I would pick it up, but I don't normally install = my own device drivers. If that is the only choice, I can try to figure it out, but it would be far better if Ubuntu provided updates via the usual distribution path, at least IMHO. Alternately, if you can point me at a good sent of instructions for how to = do this, you could save me some time.
(In reply to Jeff Powell from comment #2) > (In reply to Ilia Mirkin from comment #1) > > From the chrome bug report > >=20 > > Driver vendor Mesa > > Driver version 10.1.3 > >=20 > > 10.1 was released over a year ago. A lot of bugs have been fixed = since then. > > Can you try a more recent version? 10.5.1 was released recently. >=20 > To be brutally honest, I'm not sure. 14.04 is an LTS release that is > supposed to be supported for 2 years at least, and possibly 5. And it = is > using the default driver that Ubuntu makes available, not one of my > particular choice. If Ubuntu supplied an update I would pick it up, bu= t I > don't normally install my own device drivers. I see. Well, the way LTS generally works is "if it worked before, it'l= l keep working, but you get security/etc updates". It didn't work for you bef= ore, so that strategy won't work too well for you. >=20 > If that is the only choice, I can try to figure it out, but it would b= e far > better if Ubuntu provided updates via the usual distribution path, at = least > IMHO. >=20 > Alternately, if you can point me at a good sent of instructions for ho= w to > do this, you could save me some time. I'm not particularly knowledgeable on Ubuntu. "oibaf ppa" is some= thing I've heard said in connection to Ubuntu and easier availability of pre-packaged mesa. A quick search turns up h= ttps://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers which makes claims about supporting Ubuntu 14.04. Hope this helps.
Thanks. I'm running out of time today, but I'll check that out tomorrow and see what I can learn. Gotta be a way to do this.
We'll need at least a proper backtrace of the crash with debug= ging symbols for r600_dri.so and libgallium.so.0.0.0.
Ubuntu also ships updated mesa drivers as part of the hwe stacks, honestly I don't know why they don't offer them as some kind of update with the update-manager tool (if you'd download 14.04 lts now, you'd get the new version automatically), so you have to install it manually. https://wiki.ubuntu.com/Kernel/LTSEnablementStack It won't be quite cutting edge but still quite a bit newer (10.3.2 in fact).
Thank you for that last reply, Roland. I had no idea that update path was available in Ubuntu. I've applied it and things seem to be improved. I'll keep an eye out for additional updates of that type in the future as well.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/543.