From: Johannes Erdfelt <jerdfelt@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: IA-64 XFree86 (was: XFree 4.0.1 module loading)
Date: Tue, 22 Aug 2000 21:22:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205380@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205362@msgid-missing>
On Mon, Aug 21, 2000, Mark Vojkovich <mvojkovich@valinux.com> wrote:
>
> On Mon, 21 Aug 2000, David Mosberger wrote:
>
> > >>>>> On Mon, 21 Aug 2000 12:34:11 -0700 (PDT), Mark Vojkovich <mvojkovich@valinux.com> said:
> >
> > Mark> 1) Firmware issues that prevent the X-server from working
> > Mark> reliably with SMP (even lspci locks up in the SAL code).
> >
> > As Bill already pointed out, we have seen any problems since we fixed
> > /proc/bus/pci/devices not to overwrite kernel memory. We have a
> > dual-CPU BigSur here which runs X fine and lspci doesn't crash the
> > machine. The quick and dirty hack is to use 16KB page size.
>
> OK, that's good news. I'll get somebody to update the kernel
> on my dual-CPU BigSur and give it a try.
Nope, this was not the problem. We have the same problem going directly
to the hardware as well, as XFree and scanpci (XFree tool) does. But, it
couldn't hurt to try the patch.
I'll try upgrading him to ver 59 of the workstations firmware to see if
it helps.
JE
next prev parent reply other threads:[~2000-08-22 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-21 16:30 [Linux-ia64] Re: IA-64 XFree86 (was: XFree 4.0.1 module loading) Keith Packard
2000-08-21 16:35 ` Marc Aurele La France
2000-08-21 17:00 ` Jes Sorensen
2000-08-21 19:34 ` Mark Vojkovich
2000-08-21 21:02 ` Marc Aurele La France
2000-08-21 21:19 ` Bill Nottingham
2000-08-21 22:40 ` Mark Vojkovich
2000-08-22 1:29 ` David Mosberger
2000-08-22 2:38 ` Mark Vojkovich
2000-08-22 21:22 ` Johannes Erdfelt [this message]
2000-08-22 22:07 ` Johannes Erdfelt
2000-08-22 22:45 ` David Mosberger
2000-10-31 0:26 ` Johannes Erdfelt
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=marc-linux-ia64-105590678205380@msgid-missing \
--to=jerdfelt@valinux.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox