From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: Xorg does not work on sparc32 in 2.6 (except on cg14)
Date: Sat, 05 Feb 2005 03:19:43 +0000 [thread overview]
Message-ID: <1107573583.3951.225.camel@localhost.localdomain> (raw)
In-Reply-To: <1107553760.3951.211.camel@localhost.localdomain>
On Fri, 2005-02-04 at 17:15 -0800, William Lee Irwin III wrote:
> On Fri, Feb 04, 2005 at 04:40:27PM -0600, Tom 'spot' Callaway wrote:
> > 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!
>
> How much do the vmalloc_start patches fix here?
The vmalloc_start patches don't affect this problem at all. The results
are identical in all of the cases:
- VMALLOC_START at 0xfe600000
- VMALLOC_START reset to 0xfe300000
- VMALLOC_START set to vmalloc_start_addr (which gets set to 0xfe300000
on sun4m, and 0xfe600000 on sun4/sun4c) as in the patch I sent to the
list today.
~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-05 3:19 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
2005-02-05 1:15 ` William Lee Irwin III
2005-02-05 3:19 ` Tom 'spot' Callaway [this message]
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=1107573583.3951.225.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.