public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Schwarzseher <fields35@coolgoose.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.68: SMP for arch/sparc broken?
Date: Tue, 29 Apr 2003 15:11:45 +0200	[thread overview]
Message-ID: <3EAE7A11.3040603@coolgoose.com> (raw)

Hi,
I'm currently trying to get linux running on my old (but it's my own :-) 
Tatung SparcStation 20 clone, mainly for acting as a dsl-router / 
firewall. Kind of exotic I guess, but funny. I must confess that I'm 
pretty new to linux on sparc while running linux on i386 for nearly 8 years.

The device has two processors (high speed 85MHz). I installed a debian 
distro and now trying to bring it on actual (or rather bleeding edge) 
software revisions.

While trying to compile a 2.5.68 kernel I stumbled into a problem: the 
function "cpu_possible":
while being defined for other architectures in include/asm-i386/smp.h or 
similar it is missing in include/asm-sparc/smp.h.
Unfortunately it seems to be needed to successfully compile a kernel 
because several other things depend on it. Also unfortunately I don't 
have the slightest idea on how to fix it because I'm not that deep in 
the sparc system architecture (or the linux kernel architecture).

Any suggestions (besides to stay with a (successfully for SMP compiled) 
2.4.20 kernel)?

Regards
Schwarzseher

P.S.: When already at the topic, now offtopic for this list: any ideas 
on why swapon /dev/sdc2 throws a core since I updated the kernel to 
2.4.20? The swapon systemcall is called and the swapspace is added but 
afterwards the swapon utility makes a segfault.


                 reply	other threads:[~2003-04-29 12:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3EAE7A11.3040603@coolgoose.com \
    --to=fields35@coolgoose.com \
    --cc=linux-kernel@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