From: Jerome Glisse <glisse@freedesktop.org>
To: Andy Lutomirski <luto@mit.edu>
Cc: Jerome Glisse <jglisse@redhat.com>,
airlied@gmail.com, dri-devel@lists.sf.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device
Date: Tue, 23 Jun 2009 15:35:09 +0200 [thread overview]
Message-ID: <1245764109.2674.1.camel@localhost> (raw)
In-Reply-To: <4A40D4D7.9070306@mit.edu>
On Tue, 2009-06-23 at 09:12 -0400, Andy Lutomirski wrote:
> Andy Lutomirski wrote:
> > Jerome Glisse wrote:
> >> smem.start is a physical address which kernel can remap to access
> >> video memory of the fb buffer. We now pin the fb buffer into vram
> >> by doing so we are loosing vram but fbdev need to be reworked to
> >> allow change in framebuffer address.
> >
> > I tested this (and the corresponding 2/2 initialization order, but
> > with radeon as a module), and plymouth seems to be fully functional
> > (graphical boot, password prompt, etc).
> >
> > (The driver set the wrong mode, but that's a different issue.)
> >
> > Thanks!
> >
> > Tested-by: Andy Lutomirski <luto@mit.edu>
> >
> Got an oops after awhile:
>
> BUG: Bad page state in process gpg-agent pfn:37dd5
> page:ffffea0000c38698 flags:200000000050000c count:0 mapcount:0
> mapping:(null) index:7fd35e311
> Pid: 3131, comm: gpg-agent Not tainted 2.6.30 #5
> Call Trace:
> [<ffffffff810bc99b>] bad_page+0x115/0x13e
> [<ffffffff810bcbd3>] free_pages_check+0x3c/0x6d
> [<ffffffff810bde8f>] free_hot_cold_page+0x4e/0x151
> [<ffffffff810bdfce>] __pagevec_free+0x3c/0x65
> [<ffffffff810c1c82>] release_pages+0x1a5/0x1cb
> [<ffffffff810de357>] free_pages_and_swap_cache+0x6d/0x9e
> [<ffffffff810d584b>] tlb_finish_mmu+0x41/0x63
> [<ffffffff810d5b3f>] exit_mmap+0xfb/0x138
> [<ffffffff8104beae>] mmput+0x55/0xc1
> [<ffffffff81050626>] exit_mm+0x10e/0x12f
> [<ffffffff8105226f>] do_exit+0x1b4/0x6a8
> [<ffffffff8106c6b0>] ? up_read+0x1c/0x32
> [<ffffffff810527e2>] do_group_exit+0x7f/0xac
> [<ffffffff81052834>] sys_exit_group+0x25/0x3d
> [<ffffffff8100beab>] system_call_fastpath+0x16/0x1b
>
> I don't know if this is related to the drm changes.
>
> Back to 2.6.29 for me :) (I actually use this machine, so I'd rather
> not run kernels that cause random corruption.)
>
> --Andy
Could you get a trace using Linus pte check patch he posted earlier
on the other thread ?
Jerome
next prev parent reply other threads:[~2009-06-23 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 16:15 [PATCH 1/2] radeon: fix radeon kms framebuffer device Jerome Glisse
2009-06-23 2:39 ` Andy Lutomirski
2009-06-23 13:12 ` Andy Lutomirski
2009-06-23 13:35 ` Jerome Glisse [this message]
2009-06-24 5:26 ` Andrew Lutomirski
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=1245764109.2674.1.camel@localhost \
--to=glisse@freedesktop.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
/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.