All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15748] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
Date: Wed, 14 Apr 2010 07:29:26 GMT	[thread overview]
Message-ID: <201004140729.o3E7TQBc005306@demeter.kernel.org> (raw)
In-Reply-To: <bug-15748-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=15748


Thomas Hellstrom <thellstrom@vmware.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thellstrom@vmware.com




--- Comment #1 from Thomas Hellstrom <thellstrom@vmware.com>  2010-04-14 07:29:21 ---
My guess is this is a Nouveau after-resume bug. The ttm move memcpy path is
quite well exercised elsewhere....

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

  reply	other threads:[~2010-04-14  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10 11:20 [Bug 15748] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000028 bugzilla-daemon
2010-04-14  7:29 ` bugzilla-daemon [this message]
2012-07-11 15:08 ` [Bug 15748] " bugzilla-daemon

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=201004140729.o3E7TQBc005306@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.