| Summary: | [NV05] when ubuntu tests the gnome environment the nouveau_vieux_dri (ver) segfaults | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Gullik <gullik.webjorn> | ||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | major | ||||||
| Priority: | medium | ||||||
| Version: | unspecified | ||||||
| Hardware: | x86 (IA32) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
Hi, I assume you are using an NVIDIA RIVA TNT2-based graphics card (NV5). I have observed somewhat similar instability of RIVA TNT2 M64 with VIA Technologies Apollo MVP3 chipset. Of all the graphics chips I have tested, RIVA TNT2 M64 is by far the worst in terms of system stability on an Apollo MVP3 chipset-based mainboard. I have tested this Apollo MVP3 chipset-based mainboard against various NVIDIA, ATI Technologies, and SiS graphics chips. In case of NVIDIA, their new stuff (i.e., GeForce 2 MX, GeForce 4 MX, and GeForce FX) work much better than RIVA TNT2 M64. Strange problem since RIVA TNT2 M64 works fine on many other AGP-based mainboards I have. I assume it is some kind of VIA Technologies specific device driver bug that manifests itself when mated with RIVA TNT2. Refer to this report I have submitted. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1065300 I will be filing a bug report regarding this issue with freedesktop.org soon. Regards, fpgahardwareengineer (In reply to Comment 1) Hi, I just uploaded a bug report regarding NVIDIA RIVA TNT2 M64 graphics chip and VIA Technologies Apollo MVP3 chipset. https://bugs.freedesktop.org/show_bug.cgi?id=56340 Regards, fpgahardwareengineer Gullik As your crash indicates a segfault in unity_support_t/nouveau_vieux_dri.so It (nouveau_vieux_dri.so) is part of the nouveau-dri (the mesa 3d driver), which is not supported as of yet The other issue mentioned may or maynot be related, pending on the data to be provided In order to make progress on this issue, we'd need a stacktrace, or at least a disassembly of the code in question. I think each of the crashes happen in the same place. If you see: [ 33.776104] unity_support_t[1416]: segfault at 4 ip 0013f564 sp bfb8a430 error 4 in nouveau_vieux_dri.so[131000+2f000] Then load up nouveau_vieux_dri.so in gdb (gdb /path/to/nouveau_vieux_dri.so) and run "disassemble 0xe564". I think. (I never remember how to read those crash reports. But I just did 0x13f564 - 0x131000. No clue what the 0x2f000 is.) No response to request for additional info. Marking as invalid. (I might have some patches to nouveau_vieux that fix at least one segfault at some point semi-soon, but no way to tell if they're at all related to the issues here.) |
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.
Created attachment 63451 [details] log from desktop computer with nvidia agp card Ubuntu 12.04 LTS logs "system errors", and activates error reporting tool, however the error tool claims 12.04 is "stable" and thus not being worked on. I thought you might be interested, since the error footprint(s) look solveable. I attach my dmesg.log, there are 3 bugchecks in the last few lines Regards, Gullik