Mailinglist Archive: opensuse-bugs (8956 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=215937

           Summary: Inestability and 3D slownes in 10.1 related to driver
                    NVIDIA-Linux-x86-1.0-8776-pkg1.run
           Product: SUSE Linux 10.1
           Version: Final
          Platform: PC
        OS/Version: SuSE Linux 10.1
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: X11 3rd Party
        AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: robin.listas@xxxxxxxxxxxxxx
         QAContact: sndirsch@xxxxxxxxxx


Several reports of slow 3D accelerated display using the propietary nvidia
driver in SuSE 10.1 came out recently in the suse-linux-e@xxxxxxxx email list,
on diferent cards. We have been talking with Matthias Hopf from SuSE; some of
the testing I did was sugested by him, and I'm filling this report on his
request.

(This report is mostly what I wrote in
<http://lists.suse.com/archive/suse-linux-e/2006-Oct/3883.html>).


I have experienced what I though was a low frame rate using glxgears, but that
is no longer so clear in my case. The wheels do turn very slow, though. And I
have experienced jerkiness in 3D games like "planet penguin racer" and
"FlightGear".

But much more worrisome is that I could consistently crash X just by resizing
columns in konqueror or opening zapping-0.10cvs6-1 (gnome TV app). X crashed,
freezin keyboard and display, not the mouse, By sshing I saw "X" maxing at
around 99% cpu. One of the crashes was hard and I lost the rpm database and
gnome desktop configurations. I recovered it, but I can't know when I did the
qt YOU update (announcement last Wed, 25 Oct 2006). I mention this because I
think the results I had a few days back and those in the early hours today have
changed somewhat.

After two or three days testings (and crashings) I decided to reinstall SuSE
9.3 in another partition and try the same 1.0-8776 driver there. It worked
perfect. No slownes noticiable, no jerkiness, no crashes. I will attach later
my report.

Next day (early hours today) I tried again with 10.1, with the idea of getting
a verbose log (the type the NVidia folks want). I could not crash it as esily. 
Something had changed. Konqueror did not crash it. The game "planet penguin
racer" experienced few jerks. Not consistent with what I had experienced three
days back - I think the qt update came here. And it did not crash in an hour or
two.

But! As soon as I tried to start zapping-0.10cvs6-1 (which displayed a pink
screen with audio, no video) very strange things happened: my home XFS
partition closed straight away, other partitions unaffected. I had to reboot,
no data lost, and I was able to run "nvidia-bug-report.sh" (file attached
later) sucesfully. This is a log excerpt:

/var/log/warn:

Oct 27 01:03:53 nimrodel gconfd (cer-6078): Could not open saved state file
'/home/cer/.gconfd/saved_state.tmp' for writing: Input/output error


/var/log/kernel:

Oct 27 01:03:27 nimrodel kernel: xfs_iunlink_remove: xfs_itobp()  returned an
error 990 on hdd8.  Returning error.
Oct 27 01:03:27 nimrodel kernel: xfs_inactive:  xfs_ifree() returned an error =
990 on hdd8
Oct 27 01:03:27 nimrodel kernel: xfs_force_shutdown(hdd8,0x1) called from line
1762 of file fs/xfs/xfs_vnodeops.c.  Return address = 0xf92d9bcb
Oct 27 01:03:27 nimrodel kernel: Filesystem "hdd8": I/O Error Detected. 
Shutting down filesystem: hdd8
Oct 27 01:03:27 nimrodel kernel: Please umount the filesystem, and rectify the
problem(s)
Oct 27 01:09:36 nimrodel kernel: xfs_force_shutdown(hdd8,0x1) called from line
338 of file fs/xfs/xfs_rw.c.  Return address = 0xf92d9bcb
Oct 27 01:09:43 nimrodel kernel: audit(1161904183.600:7): audit_pid=0 old=4155
by auid=4294967295
Oct 27 01:09:45 nimrodel kernel: pnp: Device 00:0d disabled.
Oct 27 01:09:45 nimrodel kernel: gameport: kgameportd exiting
Oct 27 01:09:47 nimrodel kernel: device eth0 left promiscuous mode
Oct 27 01:09:50 nimrodel kernel: Kernel logging (proc) stopped.
Oct 27 01:09:50 nimrodel kernel: Kernel log daemon terminating.


I rebooted and tried again. Thinking that the "zapping" I tried is a cvs
version (though it works fine with the open nv driver), I tried with kdetv...
and it crashed instantly, but diferently (with the same pink display, I think).
 The symptom was that the command prompt did not return in any xterm. I had
also logged in externally in advance by ssh, as a safeguard to be able to run
commands after the expected 'X' crash, but this session also crashed when I
exited the "top" I had running there. I was able to run "nvidia-bug-report.sh"
in an xterm I fortunately had running as root (file attached later). After
rebooting, I saw in the kernel log 12 Ooops, right at the crash instant; I will
attach the kernel log excerpts later.


It is very suspicious and worrisome that two different TV apps can crash the
system in such a way, affecting kernel space. I know that NVidia driver taint
the kernel, but... 9.3 is not affected, therefore something has changed in our
camp.


See what you can do/think. Request more data if you need, but I'm a bit afraid
of crashing the system so many times: one of these I will not come out
unscathed.


Hardware: Pentium IV @ 1800 Mhz circa 2001. 1 GiB ram. Three HD. Video card:
NVidia GeForce2 MX/MX 400

I will attach logs in an hour or two.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.