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: Sun, 14 Feb 2010 17:46:50 GMT	[thread overview]
Message-ID: <201002141746.o1EHkorB019270@demeter.kernel.org> (raw)
In-Reply-To: <bug-15276-2300@http.bugzilla.kernel.org/>

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





--- Comment #20 from Panagiotis Papadakos <papadako@csd.uoc.gr>  2010-02-14 17:46:41 ---
Well it seems that I can't reproduce it with the above steps (I also can't get
transparencies to the konsoles, although I enable them in the profiles). Again
I got a lockup (without compositing), by watching a flash video in the browser,
with the keyboard leds blinking. This means a kernel Ooops if I am not wrong,
but unfortunately I could not trace it in the messages or any other of my
system's logs.

P.S.
1) Maybe the lockups are irrelevant to the radeon driver? syslog shows some
weird messages like the one below:

TCP: Peer 77.49.168.178:26010/57630 unexpectedly shrunk window
2809809291:2809816491 (repaired),

which happens for example when watching a flash video from the web. Do you have
such messages? Are your systems online during the lockup?

2) My next steps is to try and get the lockup with the laptop offline.

-- 
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
--

  parent reply	other threads:[~2010-02-14 17:46 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
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 [this message]
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
     [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
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

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=201002141746.o1EHkorB019270@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.