From: "David S. Miller" <davem@davemloft.net>
To: trizt@iname.com
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: Sparc: Kernel 2.6.13 to 2.6.15-rc2 bug when running X11
Date: Sat, 10 Dec 2005 14:35:23 -0800 (PST) [thread overview]
Message-ID: <20051210.143523.106612727.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512102314530.4626@lai.local.lan>
From: "J.O. Aho" <trizt@iname.com>
Date: Sat, 10 Dec 2005 23:25:36 +0100 (CET)
> I have to say I don't have much knowledge about the kernel code, but in
> arch/sparc64/mm/generic.c it looks for me that no matter what if
> io_remap_pte_range() is called it will result in a bug output, is this
> supposed to happen? Looking at arch/sparc/mm/generic.c I can't find any
> similar functionality.
That's not true. The bug triggers if the page table mapping
is valid already, which should never occur when we are setting
up new mappings. We should always find the PTEs we are filling
in as empty at this point in time. That is what that bug check
is making sure of.
It doesn't trigger for me here with the Xorg server, on an
Ultra60 with CreatorFB. I do get the cursor in the corner
and a non-functional screen but I can switch around to other
VC's and kill the X server cleanly. I definitely don't get
those kernel log messages.
Please retest with this debug tracing added:
--- a/arch/sparc64/mm/generic.c.~1~ 2005-12-10 14:34:18.000000000 -0800
+++ b/arch/sparc64/mm/generic.c 2005-12-10 14:34:56.000000000 -0800
@@ -137,6 +137,12 @@
int space = GET_IOSPACE(pfn);
unsigned long offset = GET_PFN(pfn) << PAGE_SHIFT;
+#if 1
+ printk("IO[%s:%d]: remap_pfn_range(s[%lx]e[%lx],f[%lx],pfn[%lx],sz[%lx],prot[%lx])\n",
+ current->comm, current->pid,
+ vma->vm_start, vma->vm_end,
+ from, pfn, size, pgprot_val(prot));
+#endif
/* See comment in mm/memory.c remap_pfn_range */
vma->vm_flags |= VM_IO | VM_RESERVED | VM_PFNMAP;
next prev parent reply other threads:[~2005-12-10 22:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 2:04 J.O. Aho
2005-12-06 2:17 ` David S. Miller
2005-12-06 16:10 ` J.O. Aho
2005-12-06 23:23 ` David S. Miller
2005-12-07 11:05 ` J.O. Aho
2005-12-07 14:07 ` Ben Collins
2005-12-07 15:42 ` J.O. Aho
2005-12-07 20:34 ` David S. Miller
2005-12-07 21:22 ` J.O. Aho
2005-12-07 21:32 ` David S. Miller
2005-12-09 12:07 ` J.O. Aho
2005-12-10 22:25 ` J.O. Aho
2005-12-10 22:35 ` David S. Miller [this message]
2005-12-10 22:52 ` J.O. Aho
2005-12-10 23:00 ` David S. Miller
2005-12-10 23:22 ` J.O. Aho
2005-12-12 5:07 ` David S. Miller
2005-12-12 8:26 ` J.O. Aho
2005-12-12 16:28 ` J.O. Aho
2006-02-01 13:15 ` J.O. Aho
2005-12-12 10:13 Mark Fortescue
2005-12-12 10:38 ` J.O. Aho
2005-12-12 22:26 ` David S. Miller
2005-12-18 22:03 ` J.O. Aho
2005-12-18 23:10 ` David S. Miller
2006-01-03 14:01 ` J.O. Aho
2006-01-03 20:18 ` David S. Miller
2006-01-03 21:15 ` J.O. Aho
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=20051210.143523.106612727.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=trizt@iname.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®