All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: UP 1.0.9 on ss5/170
Date: Sun, 14 Jun 1998 04:10:50 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90222357631019@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222357631014@msgid-missing>

> > As soon as UP 1.1 comes out, I plan to upgrade my ss5/110 to ss5/170 so
> > I'll probably come back with questions once I start trying this.
> > 
> > You say that if I get things to run on ss5/110 and I simply put the disks
> > in a ss5/170 that will work? 
> 
> It seems that way. Although gcc dies with a sig 11 more often than not,
> and /usr/bin/telnet seems to be flaky too :/
> 
> I'm not sure if this is a generic problem or only on the ss5/170.

That's exactly the behaviour like TurboSPARC port currently works (and has
for at least half a year).
It is flaky, it is probably some cache flushing issue or whatever.
If you'd have time and want to do that, I could tell you how you can debug
it and what to look at.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.105 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________

  parent reply	other threads:[~1998-06-14  4:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-13 10:30 UP 1.0.9 on ss5/170 Grant Beattie
1998-06-13 22:32 ` Marc Duponcheel
1998-06-14  3:44 ` Grant Beattie
1998-06-14  4:10 ` Jakub Jelinek [this message]
1998-06-14  8:08 ` Grant Beattie

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-ultrasparc-90222357631019@msgid-missing \
    --to=jj@sunsite.ms.mff.cuni.cz \
    --cc=ultralinux@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.