From: Matt R Hall <mhcomputing@gmail.com>
To: sparclinux@vger.kernel.org
Subject: Re: Ultra 2 Enterprise: All 2.6.xx SMP kernels hardlock
Date: Tue, 21 Sep 2004 09:41:29 +0000 [thread overview]
Message-ID: <703d4eaa04092102416077e882@mail.gmail.com> (raw)
In-Reply-To: <703d4eaa04092018404389859@mail.gmail.com>
I specifically tested _every single_ kernel version since 2.6.0. It
took me an excruciating period of several weeks to cycle through this
number of dot releases. The stable, working uniprocessor kernel is
2.6.9-rc2. 2.6.9-rc2 specifically failed in SMP mode, but, it worked
in 2.4.xx.
I would not mind that only 2.4.xx works, but I am making a public
acccess UNIX server so I want a clear upgrade path, and the newer
better packet matching support so I can do some sophisticated egress
filtering to prevent abuse. Also, I seek a dependable upgrade path
into the future, which is something 2.4.xx cannot offer for the long
term.
On Mon, 20 Sep 2004 23:34:10 -0700, David S. Miller <davem@davemloft.net> wrote:
> On Mon, 20 Sep 2004 18:40:39 -0700
> Matt R Hall <mhcomputing@gmail.com> wrote:
>
> > I filed a report about this in kernel.org's bugzilla and it has not
> > received any comments.
>
> Because the sparc64 kernel maintainer, me, doesn't look at
> kernel.org's bugzilla ever. :-)
>
> Can you make sure 2.6.9-rc2 has the same problem?
>
> I don't have any of my SBUS SMP systems active in my array
> of machines lately which is why stability on them has fallen
> on the way side, they're just too damn slow to work with :(
>
next prev parent reply other threads:[~2004-09-21 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 1:40 Ultra 2 Enterprise: All 2.6.xx SMP kernels hardlock Matt R Hall
2004-09-21 6:34 ` David S. Miller
2004-09-21 9:41 ` Matt R Hall [this message]
2004-09-21 12:01 ` Jason Wever
2004-09-21 13:00 ` Meelis Roos
2004-09-21 13:24 ` Stephen P. Becker
2004-09-22 3:08 ` Jason Wever
2004-09-22 3:20 ` David S. Miller
2004-09-23 0:26 ` Jason Wever
2004-09-23 4:46 ` David S. Miller
2004-09-24 20:44 ` David S. Miller
2004-09-24 22:56 ` Jason Wever
2004-09-27 12:03 ` Jason Wever
2004-09-27 18:17 ` David S. Miller
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=703d4eaa04092102416077e882@mail.gmail.com \
--to=mhcomputing@gmail.com \
--cc=sparclinux@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.