From: David Mosberger <davidm@hpl.hp.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 22:45:02 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205382@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205362@msgid-missing>
A hardware problem is certainly a possibility. We really haven't seen
any problems with PCI access once the kernel buffer overflow was
fixed. It was working well even before upgrading to the latest fw.
Do you have another machine you could try?
--david
>>>>> On Tue, 22 Aug 2000 15:07:10 -0700, Johannes Erdfelt <jerdfelt@valinux.com> said:
Johannes> On Tue, Aug 22, 2000, Johannes Erdfelt
Johannes> <jerdfelt@valinux.com> wrote:
>> I'll try upgrading him to ver 59 of the workstations firmware to
>> see if it helps.
Johannes> Build 59 still has the same problem. I'm curious if this
Johannes> could be caused by a hardware problem? The machine locked
Johannes> up while reading the image off of the floppy in EFI as
Johannes> well as at the "hit any other key to continue" prompt in
Johannes> the startup.nsh script.
Johannes> The machine seems stable in Linux (compiling the kernel,
Johannes> etc) so I was quite surprised to see those 2 lockups.
next prev parent reply other threads:[~2000-08-22 22:45 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
2000-08-22 22:07 ` Johannes Erdfelt
2000-08-22 22:45 ` David Mosberger [this message]
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-105590678205382@msgid-missing \
--to=davidm@hpl.hp.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