Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Istvan Gyenes <frts@simba.sch.bme.hu>
Cc: "J.Steindlberger" <j@steindlberger.de>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] SMP kernel problems on a D350
Date: Thu, 19 Sep 2002 16:46:09 -0600	[thread overview]
Message-ID: <20020919224609.DF1314829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Istvan Gyenes <frts@simba.sch.bme.hu> of "Thu, 19 Sep 2002 11:17:00 +0200." <Pine.OSF.4.33.0209191111490.32375-100000@simba.sch.bme.hu>

Istvan Gyenes wrote:
> Hello Joerg,
> 
> The only difference between the non-smp and smp kernel config file is
> CONFIG_SMP=yes , AFAIK.
> I made a "make menuconfig" and the only thing I've changed is SMP support.

I'm paranoid. I do "make distclean" when doing anything other than
adding/removing drivers. Save/restore the .config if you need to before
running "make distclean".  I don't trust the Makefiles to rebuild
everything correctly for "global" CONFIG_ changes like "SMP".

> The strange thing is that the precompiled smp kernel from the install cd
> boots fine. (2.4.18-smp)

SMP on 2.4.19 isn't as stable yet.  So that's no surprise.

If you want to debug this further, define "EARLY_BOOTUP_DEBUG"
in arch/parisc/kernel/pdc_cons.c and you should get more output
about how far the kernel gets before it crashes/hangs.

grant

  parent reply	other threads:[~2002-09-19 22:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200209190805.KAA0000032531@simba.sch.bme.hu>
2002-09-19  9:17 ` [parisc-linux] SMP kernel problems on a D350 Istvan Gyenes
2002-09-19 12:21   ` J.Steindlberger
2002-09-19 12:29     ` Ryan Bradetich
2002-09-19 22:46   ` Grant Grundler [this message]
2002-09-20  8:28     ` Istvan Gyenes
2002-09-20 19:48       ` Carlos O'Donell
2002-09-20 20:02         ` Jeremy Drake
2002-09-20 20:37           ` Carlos O'Donell
2002-09-20 20:46             ` John David Anglin
2002-09-20 20:50               ` Randolph Chung
2002-09-20 20:55                 ` Carlos O'Donell
2002-09-21 23:20                   ` Randolph Chung
2002-09-22  0:57                     ` Grant Grundler
2002-09-20 20:55                 ` John David Anglin
2002-09-20 21:51                   ` Randolph Chung
2002-09-21  3:38             ` [parisc-linux] malloc limits John David Anglin
2002-09-21  4:14               ` Matthew Wilcox
2002-09-21  4:46                 ` Grant Grundler
2002-09-21  5:24                   ` John David Anglin
2002-09-21 22:33                     ` Grant Grundler
2002-09-22  5:43                       ` John David Anglin
2002-09-20 20:37           ` [parisc-linux] SMP kernel problems on a D350 Bdale Garbee
2002-09-20 20:52             ` Carlos O'Donell
2002-09-20 23:11             ` Jeremy Drake
2002-09-20 23:46               ` Jeremy Drake
2002-09-20 23:55               ` Robert Stanford
2002-09-21  4:31       ` Grant Grundler
     [not found] <20020921044102.3DD104829@dsl2.external.hp.com>
2002-09-23 17:23 ` Jeremy Drake
2002-09-19  7:38 Istvan Gyenes

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=20020919224609.DF1314829@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=frts@simba.sch.bme.hu \
    --cc=j@steindlberger.de \
    --cc=parisc-linux@lists.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