Bug 37796 - [NV43] 2.6.39: system freezes for 1-2 seconds
Summary: [NV43] 2.6.39: system freezes for 1-2 seconds
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-31 09:46 UTC by magist3r
Modified: 2013-08-19 16:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
kernel log (77.57 KB, text/plain)
2011-05-31 09:46 UTC, magist3r
no flags Details
test (613 bytes, patch)
2011-05-31 10:34 UTC, Marcin Slusarz
no flags Details | Splinter Review
kernel log (with patch) (63.85 KB, text/plain)
2011-06-03 08:01 UTC, magist3r
no flags Details

Description magist3r 2011-05-31 09:46:04 UTC
Created attachment 47400 [details]
kernel log

Аfter upgrading to 2.6.39 system was freezing for a few seconds. After an hour of work disabled kwin effects.

sudo /sbin/lspci | grep -i nvidia
08:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2)
openSUSE 11.4
kde 4.6.3
xorg 7.6-1.9.3
xorg-x11-driver-video-nouveau-0.0.16_20110115_b795ca6
libdrm-2.4.23
Mesa-7.10.2
Comment 1 Marcin Slusarz 2011-05-31 10:32:47 UTC
It seems to be connected to commit 7948758d27be1b69b6a79ed4f3f22e36a3b95965
"drm/nv40: implement support for on-chip PCIEGART"

It's not possible to revert this patch directly, so can you verify it by applying attached patch?
Comment 2 Marcin Slusarz 2011-05-31 10:34:31 UTC
Created attachment 47404 [details] [review]
test
Comment 3 magist3r 2011-05-31 13:13:24 UTC
It works fine for me with this patch, thank you. In which version of kernel I can  expect this patch?
Comment 4 magist3r 2011-05-31 13:21:02 UTC
Hm... No. Freezes happened again. And I have this messages again:
[  745.865807] [drm] nouveau 0000:08:00.0: vm flush timeout: 0x00000032
[  759.986271] [drm] nouveau 0000:08:00.0: vm flush timeout: 0x00000032
Comment 5 Marcin Slusarz 2011-05-31 14:08:39 UTC
Impossible with this patch applied. You probably didn't boot the right kernel.

And please note that this patch won't be applied to any tree/version. It's just a temporary workaround.
Comment 6 magist3r 2011-05-31 20:39:36 UTC
I've just rebuild the kernel module without rebuilding kernel. 
If it is just workaround, can I expect a real fix of this problem in future kernel (3.0, 3.1 or?)?
Comment 7 magist3r 2011-06-03 08:01:32 UTC
Created attachment 47477 [details]
kernel log (with patch)
Comment 8 magist3r 2011-06-03 08:06:50 UTC
magist3r@lnx-admin:/lib/modules/2.6.39-30-desktop/kernel/drivers/gpu/drm/nouveau> la
итого 19968
drwxr-xr-x  2 root root     4096 Июн  3 21:04 .
drwxr-xr-x 13 root root     4096 Июн  1 02:01 ..
-rw-r--r--  1 root root 19599018 Июн  3 20:01 nouveau.ko
-rw-r--r--  1 root root   839588 Май 21 22:59 nouveau.ko.old

As you can see, the size of new kernel module is about 20 times bigger. And I don't now why.
Comment 9 Marcin Slusarz 2011-12-06 11:18:30 UTC
It seems very similar patch was applied to 3.0 kernel. Can you verify it works now?
Comment 10 Ilia Mirkin 2013-08-19 16:40:54 UTC
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.

Thanks,

The Nouveau Team


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.