Summary: | x11-drivers/nvidia-drivers-270.41.19: crash on sys-kernel/hardened-sources-2.6.38-r6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Efros <powerman-asdf> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Kernel Team (OBSOLETE) <hardened-kernel+disabled> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | hardened, kingjon3377, wbrana |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | possible patch |
Description
Alex Efros
2011-08-07 09:32:36 UTC
Created attachment 282399 [details, diff]
possible patch
Wow, thanks, patch works for me! I'm debating what to do with this patch, but leaning towards not including it because nvidia-drivers has had a bad history under hardened. The nouveau drivers are working well and we prefer them on hardened. Is there any strong reason why you opt for nvidia over nouveau? (In reply to comment #3) > Is there any strong reason why you opt for nvidia over nouveau? VMware hardware acceleration for guest Windows. (In reply to comment #3) > Is there any strong reason why you opt for nvidia over nouveau? nouveau is unstable see http://nouveau.freedesktop.org/wiki/MesaDrivers (In reply to comment #3) > I'm debating what to do with this patch, but leaning towards not including it While you debating, this bug just hit me once again - after upgrade to x11-drivers/nvidia-drivers-275.09.07. Thanks God, this patch is compatible with new version, so it was ease to add one more ebuild to /usr/local/portage… after I've spend some time trying to find out what's going on, why it doesn't work, and some time later was surprised to find previous nvidia-drivers was installed from /usr/local/portage… and, finally, I recall situation with this patch and realized what I should do to fix it. Please, don't make me do all this crap once again few months later. If it's really "kernel memory leak" as reported by PaX - it must be fixed in nvidia-drivers (either in ebuild or by reporting upstream), because if it leak on hardened, then it leak in same way on non-hardened too (but no one notices that). If it doesn't leak, and it's false alarm by PaX - then PaX should be fixed. Here is absolutely nothing to debate, sorry. I agree there are issues with nvidia-drivers on hardened, and agree nouveau is probably should be used instead… as soon as it will support 3D acceleration for Windows in VMware (and all other features it doesn't support yet and which I don't need but other people may need) - i.e. when it become real drop-in replacement for nvidia-drivers. (In reply to comment #3) > I'm debating what to do with this patch, but leaning towards not including it Is this a patch against the nvidia-drivers? If so then its not for me to say what to do with it. If the x11 team wishes, they can include it. They can include it conditionally on USE="pax_kernel". (Not "hardened" since that refers to the tool chain). I would contact NVIDIA wrt this patch. Run nvidia-bug-report.sh to collect some info about your system and e-mail the output, along with the patch and a description of the problem to linux-bugs@nvidia.com. Until they resolve the issue in their official driver, you can place the patch in /etc/portage/patches/x11-drivers/nvidia-drivers/hardened.patch and you should be set. |