From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Jeremy Drake <jeremyd@apptechsys.com>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] SMP support
Date: Tue, 05 Mar 2002 18:05:41 -0700 [thread overview]
Message-ID: <20020306010541.A8BB84853@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Jeremy Drake <jeremyd@apptechsys.com> of "Tue, 05 Mar 2002 14:40:23 PST." <Pine.LNX.4.33L2.0203051434270.6941-100000@eiger.apptechsys.com>
Jeremy Drake wrote:
> I am running debian-hppa on a J5000, and I am using the 2.4.17-32-smp
> kernel. It detects both processors at boot, and shows them both in
> /proc/cpuinfo, but /proc/stat shows this
>
> cpu 599904 33379482 34656795 68636319
> cpu0 0 0 64 68636186
> cpu1 599904 33379482 34656731 133
>
> I interpret this to mean that everything is happening on cpu1 and cpu0 is
> just sitting idle. Is this a bug, or am I doing something wrong?
sounds like a bug.
I've never looked at /proc/stat.
> Also, I am unable to build any kernels myself. I get a bunch of depmod
> errors, like these
>
> depmod: Unhandled relocation of type 74 for printk_Rsmp_dd132261
> depmod: Unhandled relocation of type 74 for usb_deregister_Rsmp_c6f994d5
I've seen this when CONFIG_PA20 is enabled but CONFIG_PARISC64 is not.
Don't know if that's your problem, but it's worth checking.
You don't need to enable CONFIG_PA20 in order to run a 32-bit kernel
on any system that will support 32-bit kernels (A500/L-class only
support 64-bit kernel).
grant
next prev parent reply other threads:[~2002-03-06 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 22:40 [parisc-linux] SMP support Jeremy Drake
2002-03-05 22:52 ` Randolph Chung
2002-03-06 1:05 ` Grant Grundler [this message]
2002-03-06 15:10 ` Michael S.Zick
2002-03-06 20:05 ` Jeremy Drake
2002-03-20 22:16 ` M. Grabert
2002-03-21 7:08 ` Grant Grundler
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=20020306010541.A8BB84853@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=jeremyd@apptechsys.com \
--cc=parisc-linux@parisc-linux.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