All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 69029] [NVA8] GPU lockup since kernel 3.11 upgrade
Date: Tue, 28 Jan 2014 09:21:52 +0000	[thread overview]
Message-ID: <bug-69029-8800-xpcciMfvo8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69029-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 987 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=69029

--- Comment #11 from Frederic Crozat <fred-ku13qjcBzYesTnJN9+BGXg@public.gmane.org> ---
(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.

[-- Attachment #1.2: Type: text/html, Size: 1818 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-01-28  9:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 11:35 [Bug 69029] New: GT218 (NVA8): GPU lockup since kernel 3.11 upgrade bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-69029-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-06 11:36   ` [Bug 69029] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 12:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 16:16   ` [Bug 69029] [NVA8] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-23 19:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-25 13:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27  7:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-14 16:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-14 16:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-14 20:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-28  3:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-28  9:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-10-22  8:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-69029-8800-xpcciMfvo8@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.