<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - (bisected) kernel>=3.7 breaks nouveau with acceleration for GeForce 6150SE nForce 430"
href="https://bugs.freedesktop.org/show_bug.cgi?id=61287">61287</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>nouveau@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>(bisected) kernel>=3.7 breaks nouveau with acceleration for GeForce 6150SE nForce 430
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>xorg-team@lists.x.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>balducci@units.it
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/nouveau
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr></table>
<p>
<div>
<pre>Hello,
I am experiencing X11 problems with kernel>=3.7 (including latest 3.8
release) with the following GPU:
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2)
I am on an AMD Athlon 64 X2 Dual Core Processor, running in
32bit mode and using DRM/NOUVEAU in KMS.
Further (possibly) useful information about software versions is:
mesa 9.0.2
libdrm 2.4.42
xf86-video-nouveau 1.0.6
xorg-server 1.13.2
I can boot just fine in KMS.
Also X11 (which I run with startx) boots nicely and is *almost*
perfectly functional (which is why it took me a while to focus the
problem)
The problem is apparently related to acceleration: if I run glxgears
(or vmd, a molecular visualization code which uses acceleration), the
X server suddenly looks (to me) overloaded and unstable (e.g. I cannot move
the pointer any more); within some 10-20 sec I can escape to the
console with CTRL-ALT-F1 and just kill manually the X server with
CTRL-c. This however takes a bit and in the meantime I get the
following repeated messages (apparently) from some nouveau component
on the console:
nouveau E[ 891] failed to idle channel 0xcccc0000
After this, the GPU is apparently left in a sort of locked state: if I
restart X, the screen shows the image just before the crash and is
totally unresponsive. However, I can still shutdown X with CTRL-ALT-F1
and kill manually the server. In order to have X running again I have
to reboot the machine.
The problem is completely reproducible.
If I boot into kernel-3.6.10 (everything else unchanged), nothing of the
above happens and glxgears (and vmd) work absolutely fine.
I have bisected the kernel commits from 3.6.10 to 3.7-rc1 in
drivers/gpu/drm/nouveau/ and it turns out that:
612a9aab56a93533e76e3ad91642db7033e03b69 is the first bad commit
commit 612a9aab56a93533e76e3ad91642db7033e03b69
Merge: 3a49431 268d283
Author: Linus Torvalds <<a href="mailto:torvalds@linux-foundation.org">torvalds@linux-foundation.org</a>>
Date: Wed Oct 3 23:28:59 2012 -0700
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
Pull drm merge (part 1) from Dave Airlie:
"So first of all my tree and uapi stuff has a conflict mess, its my
fault as the nouveau stuff didn't hit -next as were trying to rebase
regressions out of it before we merged.
Highlights:
- SH mobile modesetting driver and associated helpers
- some DRM core documentation
- i915 modesetting rework, haswell hdmi, haswell and vlv fixes,
write
combined pte writing, ilk rc6 support,
- nouveau: major driver rework into a hw core driver, makes features
like SLI a lot saner to implement,
- psb: add eDP/DP support for Cedarview
- radeon: 2 layer page tables, async VM pte updates, better PLL
selection for > 2 screens, better ACPI interactions
[...]
Problems for the same GPU with kernel>=3.7 have been already reported
here:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=905629">https://bugzilla.redhat.com/show_bug.cgi?id=905629</a>
However, it is not clear to me if that report and the present one are
dealing with the same thing...
Please, find enclosed:
=> kernel configuration
=> xorg configuration
=> xorg log after the crash
=> dmesg after the crash
(To avoid possible confusion: I opened a bug here some time ago for
another problem with another NVIDIA GPU (<a class="bz_bug_link
bz_status_NEW "
title="NEW --- - DRM NOUVEAU: cannot boot with kernel >=3.7"
href="show_bug.cgi?id=58776">Bug 58776</a>): in that report I
said that this GPU was working fine: of course, I did not discovered
yet the present issue)
I thank you very much in advance for any help
ciao
gabriele</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>