From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Xorg does not work on sparc32 in 2.6 (except on cg14)
Date: Fri, 04 Feb 2005 22:40:27 +0000 [thread overview]
Message-ID: <1107556827.3951.213.camel@localhost.localdomain> (raw)
In-Reply-To: <1107553760.3951.211.camel@localhost.localdomain>
Resending, since I think Evolution ate it. Apologies if this shows up twice.
With a working pte_read, and VMALLOC_START set sanely, the next major
bug that Aurora users have noticed is that Xorg does not work on sparc32
hardware running 2.6, with one exception: Bob Breuer has been able to
get the cg14 to work.
My SS20 with a CG6 (TGX+) works fine in 2.4. When I attempt to run Xorg
in 2.6 (specifically, 2.6.11-rc2-bk3), the Xorg.0.log claims that it is
running, but the kernel has actually oopsed:
kernel BUG at arch/sparc/mm/srmmu.c:140!
\|/ ____ \|/
"@'/ ,. \`@"
/_| \__/ |_\
\__U_/
Xorg(2681): Kernel bad trap [#1]
PSR: 404010c2 PC: f001d8c4 NPC: f001d8c8 Y: 00000000 Not tainted
PC: <srmmu_pte_pfn+0x24/0x30>
%G: 0000008c 404010e1 f01fd40c f0ab1e5c f002be4c 00000008 f215e000
00000000
%O: 00000029 f01d43e8 0000008c 00000020 00000060 f00f33a0 f215fd18
f001d8bc
RPC: <srmmu_pte_pfn+0x1c/0x30>
%L: f215fd38 f3ea0d4c f0288c00 00000000 f30fea2c f30f9b9c 00100100
00200200
%I: e2070026 00000ec0 503b0000 f002e938 00000060 f00f33a0 f215fd80
f0061974
Caller[f0061974]: copy_page_range+0x2fc/0x47c
Caller[f002e9f4]: copy_process+0x5b4/0xdd0
Caller[f002f2cc]: do_fork+0x4c/0x1d0
Caller[f0011120]: syscall_is_too_hard+0x34/0x40
Caller[501c835c]: 0x501c835c
Instruction DUMP: 901223e8 7fffd23c 9210208c <91d02005> 81c7e008
81e80000 9de3bf98 c4060000 033c0000
This is being triggered with the BUG() in this function in
arch/sparc/mm/srmmu.c:
static unsigned long srmmu_pte_pfn(pte_t pte)
{
if (srmmu_device_memory(pte_val(pte))) {
/* XXX Anton obviously had something in mind when he did
this.
* But what?
*/
/* return (struct page *)~0; */
BUG();
}
return (pte_val(pte) & SRMMU_PTE_PMASK) >> (PAGE_SHIFT-4);
}
This is being BTFIXEDUP to pte_pfn.
Removing the if (srmmu_device_memory(pte_val(pte))) check stops the
oops, but it doesn't make X work. The screen goes blank, but the X
session never appears.
I've got a couple of other framebuffer SBUS cards that I plan on
testing, but the only success report I have is from Bob's cg14.
So, does anyone know whats happening here? Why would the cg14 work when
a cg6 does not? This isn't an Xorg config file error, as far as Xorg is
concerned, the X session is running, twm is in the ps tree, and an xterm
is open. The monitor is a stock Sun 15 inch, no special cabling.
Any and all help is appreciated.
~spot
---
Tom "spot" Callaway <tcallawa(a)redhat*com> LCA, RHCE
Red Hat Sales Engineer || Aurora Linux Project Leader
"If you are going through hell, keep going."
-- Sir Winston Churchill
next prev parent reply other threads:[~2005-02-04 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 21:49 Xorg does not work on sparc32 in 2.6 (except on cg14) Tom 'spot' Callaway
2005-02-04 22:40 ` Tom 'spot' Callaway [this message]
2005-02-05 1:15 ` William Lee Irwin III
2005-02-05 3:19 ` Tom 'spot' Callaway
2005-02-05 6:06 ` David S. Miller
2005-02-05 16:25 ` Tom 'spot' Callaway
2005-02-08 16:42 ` Georg Chini
2005-02-08 16:58 ` Tom 'spot' Callaway
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=1107556827.3951.213.camel@localhost.localdomain \
--to=tcallawa@redhat.com \
--cc=sparclinux@vger.kernel.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.