All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15276] latest git kernel: general protection fault: 0000 [#1]
Date: Fri, 12 Feb 2010 19:04:38 GMT	[thread overview]
Message-ID: <201002121904.o1CJ4cKb014280@demeter.kernel.org> (raw)
In-Reply-To: <bug-15276-2300@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=15276


Michał Witkowski <neuro@o2.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |neuro@o2.pl




--- Comment #6 from Michał Witkowski <neuro@o2.pl>  2010-02-12 19:04:16 ---
I'm having similar issues to the ones described in the linked post:
http://bbs.archlinux.org/viewtopic.php?pid=706873#p706873

I have a Radeon Mobility 3450. The weird hangs started to appear after applying
the patch to fix bug 15186 to vanilla 2.6.33-rc6. Before that I never had hangs
with KMS.

Packages:
mesa-git 20100119
xf86-video-ati-git 20100119

I just compiled kernel 2.6.33-rc7, I'll report if the hangs appear here too.

-- 
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
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  parent reply	other threads:[~2010-02-12 19:04 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 19:38 [Bug 15276] New: latest git kernel: general protection fault: 0000 [#1] bugzilla-daemon
2010-02-11 19:43 ` [Bug 15276] " 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-02-14 23:31 2.6.33-rc8: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-14 23:38 ` [Bug #15276] latest git kernel: general protection fault: 0000 [#1] Rafael J. Wysocki
2010-02-21 21:25 2.6.33-rc8-git6: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-21 21:30 ` [Bug #15276] latest git kernel: general protection fault: 0000 [#1] Rafael J. Wysocki
2010-03-21 20:27 2.6.34-rc2: Reported regressions 2.6.32 -> 2.6.33 Rafael J. Wysocki
2010-03-21 20:30 ` [Bug #15276] latest git kernel: general protection fault: 0000 [#1] Rafael J. Wysocki
2010-03-21 20:30   ` Rafael J. Wysocki
2010-04-08 22:54 2.6.34-rc3-git8: Reported regressions 2.6.32 -> 2.6.33 Rafael J. Wysocki
2010-04-08 23:04 ` [Bug #15276] latest git kernel: general protection fault: 0000 [#1] Rafael J. Wysocki
     [not found] <bug-15276-2300@https.bugzilla.kernel.org/>
2010-03-21 15:02 ` [Bug 15276] " bugzilla-daemon
2010-03-21 19:45 ` bugzilla-daemon
2010-03-27 22:52 ` bugzilla-daemon
2010-03-27 23:21 ` bugzilla-daemon
2010-03-29  9:39 ` bugzilla-daemon
2010-03-29 13:17 ` bugzilla-daemon
2010-04-13 10:19 ` bugzilla-daemon
2010-04-13 15:42 ` bugzilla-daemon
2010-12-07 20:31 ` bugzilla-daemon
2010-12-07 20:31 ` 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=201002121904.o1CJ4cKb014280@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.