From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 69029] [NVA8] GPU lockup since kernel 3.11 upgrade Date: Tue, 28 Jan 2014 09:21:52 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0728798765==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0728798765== Content-Type: multipart/alternative; boundary="1390900912.CDF6f2B2.20535"; charset="us-ascii" --1390900912.CDF6f2B2.20535 Date: Tue, 28 Jan 2014 09:21:52 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=69029 --- Comment #11 from Frederic Crozat --- (In reply to comment #10) > Frederic: Do I understand correctly that everything is consistently fine in > 3.10.x and consistently broken in 3.11.x? If so, could you try doing a > bisect to identify the offending commit? (First might be worth checking if > the issue still occurs in 3.13 btw.) BTW, your third "lockup" log doesn't > indicate that anything really went wrong -- just a kmalloc() failure which > should be handled by the surrounding code. Although the later xfs corruption > errors are a bit ominous... With 3.11.6, I get very few lockups (if any), which is making bisection irrelevant/impossible to do. the xfs corruption was caused by running mkinitrd which was trying to load xfs module even if there is no xfs partitions anywhere (this is now fixed). -- You are receiving this mail because: You are the assignee for the bug. --1390900912.CDF6f2B2.20535 Date: Tue, 28 Jan 2014 09:21:52 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 11 on bug 69029 from 
(In reply to comment #10)
> Frederic: Do I understand correctly that everything is consistently fine in
> 3.10.x and consistently broken in 3.11.x? If so, could you try doing a
> bisect to identify the offending commit? (First might be worth checking if
> the issue still occurs in 3.13 btw.) BTW, your third "lockup" log doesn't
> indicate that anything really went wrong -- just a kmalloc() failure which
> should be handled by the surrounding code. Although the later xfs corruption
> errors are a bit ominous... 

With 3.11.6, I get very few lockups (if any), which is making bisection
irrelevant/impossible to do.

the xfs corruption was caused by running mkinitrd which was trying to load xfs
module even if there is no xfs partitions anywhere (this is now fixed).

You are receiving this mail because:
  • You are the assignee for the bug.
--1390900912.CDF6f2B2.20535-- --===============0728798765== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Nouveau mailing list Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org http://lists.freedesktop.org/mailman/listinfo/nouveau --===============0728798765==--