All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28402] random radeon/kms/drm related freezes with kernel 2.6.34
Date: Tue, 26 Oct 2010 04:44:19 -0700 (PDT)	[thread overview]
Message-ID: <20101026114419.CBBCE13000D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28402-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=28402

--- Comment #89 from Helmut Jarausch <jarausch@igpm.rwth-aachen.de> 2010-10-26 04:44:16 PDT ---
(In reply to comment #85)
> Created an attachment (id=39651)
 View: https://bugs.freedesktop.org/attachment.cgi?id=39651
 Review: https://bugs.freedesktop.org/review?bug=28402&attachment=39651

> Make sure MC vram map is >= pci aperture size
> 
> Ok, I think I found the root cause in this bug.  The vram map in the memory
> controller needs to be >= the pci aperture size.  For the systems here, the
> vram size is 64 MB and the aperture size is 128 MB so the vram map in the mc
> needs to be at least 128 MB.  However, it's getting set to 64 MB.

Could you please tell me which git archive this patch has gone into.
It doesn't seem to be the official linux-next:    next-20101026

Many thanks for a hint (I do need to get a patchset against stock 2.6.36)

Helmut.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-10-26 11:44 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28402-502@http.bugs.freedesktop.org/>
2010-06-05 18:18 ` [Bug 28402] Kernel 2.6.34 freezes randomly bugzilla-daemon
2010-06-08 20:20 ` bugzilla-daemon
2010-06-08 20:33 ` bugzilla-daemon
2010-06-11 18:29 ` bugzilla-daemon
2010-06-11 18:36 ` bugzilla-daemon
2010-06-12 12:19 ` bugzilla-daemon
2010-06-16 12:12 ` bugzilla-daemon
2010-06-16 12:22 ` bugzilla-daemon
2010-06-18 13:44 ` bugzilla-daemon
2010-07-13 12:26 ` bugzilla-daemon
2010-08-15 21:21 ` bugzilla-daemon
2010-08-16 13:14 ` bugzilla-daemon
2010-08-29  0:16 ` bugzilla-daemon
2010-08-29  0:18 ` bugzilla-daemon
2010-08-29 20:39 ` bugzilla-daemon
2010-08-30 12:39 ` bugzilla-daemon
2010-08-30 16:30 ` bugzilla-daemon
2010-08-30 16:33 ` bugzilla-daemon
2010-08-30 16:35 ` bugzilla-daemon
2010-08-30 16:35 ` bugzilla-daemon
2010-08-30 16:36 ` bugzilla-daemon
2010-08-30 16:37 ` bugzilla-daemon
2010-08-30 16:37 ` bugzilla-daemon
2010-08-30 16:38 ` bugzilla-daemon
2010-08-30 16:39 ` bugzilla-daemon
2010-08-30 16:55 ` bugzilla-daemon
2010-08-30 18:27 ` bugzilla-daemon
2010-08-31 13:37 ` bugzilla-daemon
2010-08-31 16:21 ` bugzilla-daemon
2010-08-31 20:04 ` bugzilla-daemon
2010-08-31 20:19 ` bugzilla-daemon
2010-09-01 11:37 ` bugzilla-daemon
2010-09-01 16:42 ` bugzilla-daemon
2010-09-02 14:46 ` bugzilla-daemon
2010-09-02 15:46 ` bugzilla-daemon
2010-09-02 16:14 ` bugzilla-daemon
2010-09-02 18:10 ` bugzilla-daemon
2010-09-05 12:11 ` bugzilla-daemon
2010-09-05 22:25 ` bugzilla-daemon
2010-09-05 22:30 ` bugzilla-daemon
2010-09-05 22:39 ` bugzilla-daemon
2010-09-05 23:02 ` bugzilla-daemon
2010-09-06  8:53 ` bugzilla-daemon
2010-09-06  8:55 ` bugzilla-daemon
2010-09-06  9:03 ` bugzilla-daemon
2010-09-06 15:07 ` bugzilla-daemon
2010-09-07 10:48 ` bugzilla-daemon
2010-09-07 12:37 ` bugzilla-daemon
2010-09-07 15:34 ` bugzilla-daemon
2010-09-07 19:25 ` bugzilla-daemon
2010-09-08  8:45 ` bugzilla-daemon
2010-09-08 12:02 ` bugzilla-daemon
2010-09-08 16:09 ` bugzilla-daemon
2010-09-08 16:43 ` bugzilla-daemon
2010-09-08 17:42 ` bugzilla-daemon
2010-09-08 19:42 ` bugzilla-daemon
2010-09-08 19:44 ` [Bug 28402] random radeon/kms/drm related freezes with kernel 2.6.34 bugzilla-daemon
2010-09-08 21:45 ` bugzilla-daemon
2010-09-09 10:00 ` bugzilla-daemon
2010-09-09 11:11 ` bugzilla-daemon
2010-09-09 11:24 ` bugzilla-daemon
2010-09-09 11:48 ` bugzilla-daemon
2010-09-09 13:08 ` bugzilla-daemon
2010-09-09 13:09 ` bugzilla-daemon
2010-09-09 13:27 ` bugzilla-daemon
2010-09-09 13:31 ` bugzilla-daemon
2010-09-09 14:11 ` bugzilla-daemon
2010-09-09 14:36 ` bugzilla-daemon
2010-09-09 21:23 ` bugzilla-daemon
2010-09-10  7:33 ` bugzilla-daemon
2010-09-14 13:17 ` bugzilla-daemon
2010-09-16 14:10 ` bugzilla-daemon
2010-09-21 10:38 ` bugzilla-daemon
2010-09-21 12:31 ` bugzilla-daemon
2010-09-21 12:42 ` bugzilla-daemon
2010-09-21 12:50 ` bugzilla-daemon
2010-09-21 13:02 ` bugzilla-daemon
2010-09-21 13:11 ` bugzilla-daemon
2010-09-21 13:39 ` bugzilla-daemon
2010-09-21 18:26 ` bugzilla-daemon
2010-10-12 12:17 ` bugzilla-daemon
2010-10-15  0:00 ` bugzilla-daemon
2010-10-15 12:05 ` bugzilla-daemon
2010-10-17 13:15 ` bugzilla-daemon
2010-10-20 20:31 ` bugzilla-daemon
2010-10-21 17:26 ` bugzilla-daemon
2010-10-21 22:56 ` bugzilla-daemon
2010-10-23 13:56 ` bugzilla-daemon
2010-10-24 12:03 ` bugzilla-daemon
2010-10-24 14:23 ` bugzilla-daemon
2010-10-25 17:21 ` bugzilla-daemon
2010-10-26 11:44 ` bugzilla-daemon [this message]
2010-10-26 16:05 ` bugzilla-daemon
2010-10-26 16:26 ` bugzilla-daemon
2010-10-27 11:50 ` bugzilla-daemon
2010-10-29 12:55 ` bugzilla-daemon
2010-10-29 14:10 ` bugzilla-daemon
2010-10-29 17:24 ` bugzilla-daemon
2010-11-02 13:53 ` bugzilla-daemon
2010-11-03 22:10 ` bugzilla-daemon
2010-12-05 14:44 ` bugzilla-daemon
2011-02-09 10:25 ` 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=20101026114419.CBBCE13000D@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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.