From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15217] NULL pointer dereference after resume-from-disk
Date: Wed, 3 Feb 2010 22:25:00 GMT [thread overview]
Message-ID: <201002032225.o13MP0wd030008@demeter.kernel.org> (raw)
In-Reply-To: <bug-15217-2300@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15217
Rafał Miłecki <zajec5@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zajec5@gmail.com
--- Comment #3 from Rafał Miłecki <zajec5@gmail.com> 2010-02-03 22:24:57 ---
Is this reproducible? If so, please retest without sound card magic. Does it
actually help?
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-02-03 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15217-2300@http.bugzilla.kernel.org/>
2010-02-03 15:06 ` [Bug 15217] NULL pointer dereference after resume-from-disk bugzilla-daemon
2010-02-03 22:25 ` bugzilla-daemon [this message]
2010-02-04 14:05 ` bugzilla-daemon
[not found] <bug-15217-2300@https.bugzilla.kernel.org/>
2012-06-27 13:14 ` 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=201002032225.o13MP0wd030008@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.