Summary: | www-client/chromium-34.0.1847.116 w/ x11-drivers/nvidia-drivers-334.21 kernel NULL pointer dereference | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
Component: | [OLD] Library | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | evan.teran, jer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Justin Lecher (RETIRED)
2014-04-07 06:03:25 UTC
Run nvidia-bug-report.sh and report it upstream. (In reply to Jeroen Roovers from comment #1) > Run nvidia-bug-report.sh and report it upstream. Hopefully you don't plan to stabilize it. This driver is broken. (In reply to Justin Lecher from comment #2) > Hopefully you don't plan to stabilize it. This driver is broken. 14 Mar 2014; Jeroen Roovers <jer@gentoo.org> nvidia-drivers-334.21.ebuild: Stable for AMD64 x86 too. I would expect more bug reports in that case. This happens reproducibly when ever I close chromium. But there is no segf or any other dump of information. I fire up chromium, go to html5test.com, the test doesn't succeed means it hangs/runs forever, I close chromium and get this. What happens when you set intel_iommu=off on the kernel command line? So far completely disabling iommu code in the kernel helps here. But I will observe this further. This has also ben reported to NVIDIA *** Bug 507452 has been marked as a duplicate of this bug. *** Looks exactly like bug #433102 and bug #410631. *** This bug has been marked as a duplicate of bug 433102 *** |