Summary: | Chrome crashes in 64 bit r600 driver while running google maps | ||
---|---|---|---|
Product: | Mesa | Reporter: | Jeff Powell <jrpstonecarver> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | jrpstonecarver |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jeff Powell
2015-03-18 00:06:11 UTC
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 > > 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. 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, 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 > > > > 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. > > 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, but I > don't normally install my own device drivers. I see. Well, the way LTS generally works is "if it worked before, it'll keep working, but you get security/etc updates". It didn't work for you before, so that strategy won't work too well for you. > > 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. I'm not particularly knowledgeable on Ubuntu. "oibaf ppa" is something I've heard said in connection to Ubuntu and easier availability of pre-packaged mesa. A quick search turns up https://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 debugging 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. -- 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. |
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.