mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Sun, 11 Dec 2005 21:07:52 -0800 (PST)	[thread overview]
Message-ID: <20051211.210752.83944980.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512110020050.4809@lai.local.lan>

From: "J.O. Aho" <trizt@iname.com>
Date: Sun, 11 Dec 2005 00:22:22 +0100 (CET)

> sbusfb_mmap: start[71800000] size[410000] off[4000000]
> sbusfb_mmap: page[0] map_size[2000]
> sbusfb_mmap: map_size is now 2000
> IO[X:6712]: 
> remap_pfn_range(s[71800000]e[71c10000],f[71800000],pfn[1fc0060],sz[2000],prot[80000000000006b0])
> sbusfb_mmap: page[2000] map_size[2000]
> sbusfb_mmap: map_size is now 2000
> IO[X:6712]: 
> remap_pfn_range(s[71800000]e[71c10000],f[71802000],pfn[1fc0060],sz[2000],prot[80000000000006b0])

This is the trace we needed.

That last line is impossible, the debugging of the last 3 lines shows
that:

1) "page" is equal to 0x2000
2) "map_size" is equal to 0x2000

Furthermore, the first line shows that:

3) "vma->vm_start" is 0x71800000

The io_remap_pfn_range() call in drivers/video/sbuslib.c is:

		r = io_remap_pfn_range(vma,
					vma->vm_start + page,
					MK_IOSPACE_PFN(iospace,
						map_offset >> PAGE_SHIFT),
					map_size,
					vma->vm_page_prot);

This means, it passes in "vma->vm_start + page" in as the start
address.

Yet the last line, printed by the tracing code in io_remap_pfn_range()
is getting 0x71800000, when it should be 0x71802000.

I strongly believe your kernel is being miscompiled by whatever
gcc is being used to build your kernels.

  reply	other threads:[~2005-12-12  5:07 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
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 [this message]
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=20051211.210752.83944980.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®