From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15276] New: latest git kernel: general protection fault: 0000 [#1]
Date: Thu, 11 Feb 2010 19:38:14 GMT [thread overview]
Message-ID: <bug-15276-2300@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=15276
Summary: latest git kernel: general protection fault: 0000 [#1]
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: maciej.rutecki@gmail.com
CC: markus@trippelsdorf.de
Regression: Yes
Subject : latest git kernel: general protection fault: 0000 [#1]
Submitter : Markus Trippelsdorf <markus@trippelsdorf.de>
Date : 2010-02-09 8:36
Message-ID : 20100209083605.GA1766@arch.tripp.de
References : http://marc.info/?l=linux-kernel&m=126570498804223&w=2
This entry is being used for tracking a regression from 2.6.33. Please don't
close it until the problem is fixed in the mainline.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
next reply other threads:[~2010-02-11 19:38 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 19:38 bugzilla-daemon [this message]
2010-02-11 19:43 ` [Bug 15276] latest git kernel: general protection fault: 0000 [#1] bugzilla-daemon
2010-02-12 7:36 ` bugzilla-daemon
2010-02-12 9:35 ` bugzilla-daemon
2010-02-12 9:52 ` bugzilla-daemon
2010-02-12 9:52 ` bugzilla-daemon
2010-02-12 9:54 ` bugzilla-daemon
2010-02-12 19:04 ` bugzilla-daemon
2010-02-12 21:05 ` bugzilla-daemon
2010-02-12 22:28 ` bugzilla-daemon
2010-02-12 22:31 ` bugzilla-daemon
2010-02-13 7:41 ` bugzilla-daemon
2010-02-13 8:08 ` bugzilla-daemon
2010-02-13 9:42 ` bugzilla-daemon
2010-02-13 10:42 ` bugzilla-daemon
2010-02-13 13:43 ` bugzilla-daemon
2010-02-13 14:45 ` bugzilla-daemon
2010-02-13 15:44 ` bugzilla-daemon
2010-02-13 17:18 ` bugzilla-daemon
2010-02-13 17:27 ` bugzilla-daemon
2010-02-14 8:39 ` bugzilla-daemon
2010-02-14 17:46 ` bugzilla-daemon
2010-02-14 22:28 ` bugzilla-daemon
2010-02-14 23:37 ` bugzilla-daemon
2010-02-14 23:39 ` bugzilla-daemon
2010-02-15 15:53 ` bugzilla-daemon
2010-02-15 19:22 ` bugzilla-daemon
2010-02-15 19:48 ` bugzilla-daemon
2010-02-15 20:33 ` bugzilla-daemon
2010-02-16 14:24 ` bugzilla-daemon
2010-02-16 14:26 ` bugzilla-daemon
2010-02-16 16:37 ` bugzilla-daemon
2010-02-16 17:36 ` bugzilla-daemon
2010-02-16 22:21 ` bugzilla-daemon
2010-02-17 5:14 ` bugzilla-daemon
2010-02-17 10:04 ` bugzilla-daemon
2010-02-17 10:31 ` bugzilla-daemon
2010-02-18 23:09 ` bugzilla-daemon
2010-02-19 14:37 ` bugzilla-daemon
2010-02-22 11:57 ` bugzilla-daemon
2010-02-22 12:20 ` bugzilla-daemon
2010-02-22 12:22 ` bugzilla-daemon
2010-02-23 22:49 ` bugzilla-daemon
2010-02-23 23:16 ` bugzilla-daemon
2010-02-24 0:15 ` bugzilla-daemon
2010-02-24 3:30 ` bugzilla-daemon
2010-02-24 17:42 ` bugzilla-daemon
2010-02-24 18:35 ` bugzilla-daemon
2010-02-24 23:44 ` bugzilla-daemon
2010-02-26 10:40 ` bugzilla-daemon
2010-03-06 21:38 ` bugzilla-daemon
2010-03-07 8:06 ` bugzilla-daemon
2010-03-07 9:44 ` bugzilla-daemon
2010-03-10 15:42 ` bugzilla-daemon
2010-03-11 9:44 ` bugzilla-daemon
2010-03-11 15:35 ` bugzilla-daemon
2010-03-12 19:36 ` bugzilla-daemon
2010-03-12 20:58 ` bugzilla-daemon
2010-03-13 1:00 ` 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=bug-15276-2300@http.bugzilla.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.