<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - v3.13-rc8 nv4e + msi = random lockups"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74492#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - v3.13-rc8 nv4e + msi = random lockups"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74492">bug 74492</a>
from <span class="vcard"><a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> <span class="fn">Ilia Mirkin</span></a>
</span></b>
<pre>Yes, probably the same thing as that bug, although unfortunately the bug filer
from #73445 never responded to my suggestion.
Definitely sounds like something IRQ-ish is going bad. I think the ultimate
resolution will be to just disable MSI on nv4e, but if you don't mind, could
you attach the output of
# lspci -vvvnn
# cat /proc/interrupts
(Run as root -- well, really just the lspci bit needs root.)
for both the NvMSI=0 case as well as the default case. Even more ideally, do
this when the corruption begins (for when MSI is enabled). Also, can you attach
a dmesg of a boot without NvMSI=0? Do you see funny interrupt errors in dmesg
(like "irq 16 nobody cared" sort of thing)?</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>