All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Jeremy Drake <jeremyd@apptechsys.com>
Cc: parisc-linux@parisc-linux.org, debian-hppa@lists.debian.org
Subject: [parisc-linux] Re: Kernel 2.4.17-32-smp problem
Date: Sun, 24 Mar 2002 01:14:32 -0700	[thread overview]
Message-ID: <20020324081432.82653483C@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Jeremy Drake <jeremyd@apptechsys.com> of "Sat, 23 Mar 2002 20:03:00 PST." <Pine.LNX.4.33L2.0203231953470.13376-100000@eiger.apptechsys.com>

Jeremy Drake wrote:
> Recently, I ran apt-get upgrade, and it upgraded my kernel-image
> 2.4.17-32-smp.  I rebooted, and the box now crashes periodically.

Where you running an SMP kernel before?
(If so, which version?)

Normally I'd say get the latest (2.4.18 based) kernel.
But I know the SMP variant hangs on my A500 pretty quickly.
I haven't had a chance to debug this since I've been spending spare
cycle working on PA8700 support (bug workarounds in SBA code).

IIRC, the debian buildd machine is also a J5000 and runs a
non-SMP kernel for similar (same?) reason.

hth,
grant

  parent reply	other threads:[~2002-03-24  8:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-24  4:03 [parisc-linux] Kernel 2.4.17-32-smp problem Jeremy Drake
2002-03-24  8:14 ` [parisc-linux] " Grant Grundler
2002-03-24  8:14 ` Grant Grundler [this message]
2002-03-24 17:33   ` Jeremy Drake
2002-03-25  3:58     ` Grant Grundler
2002-03-25  7:33       ` Jeremy Drake
2002-03-25 10:42       ` Thibaut VARENE
2002-03-25 17:00         ` Jeremy Drake
2002-03-24 17:33   ` Jeremy Drake
2002-03-25  0:33 ` [parisc-linux] " Randolph Chung
2002-03-25  3:01   ` Jeremy Drake
2002-03-25  4:10     ` Grant Grundler
2002-03-25 17:44 ` Jeremy Drake
2002-03-25 17:44 ` Jeremy Drake
2002-03-25 18:00   ` Jeremy Drake
2002-03-26  5:26     ` Jeremy Drake

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=20020324081432.82653483C@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=debian-hppa@lists.debian.org \
    --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 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.