From: "Stephen P. Becker" <geoman@gentoo.org>
To: sparclinux@vger.kernel.org
Subject: Re: Ultra 2 Enterprise: All 2.6.xx SMP kernels hardlock
Date: Tue, 21 Sep 2004 13:24:02 +0000 [thread overview]
Message-ID: <41502B72.1050205@gentoo.org> (raw)
In-Reply-To: <703d4eaa04092018404389859@mail.gmail.com>
For what it's worth, I used to have 2x200 UltraSPARCI processors in my
Ultra2. I could not get it to boot via nfsroot using a 2.6.7 kernel
(HME started resetting itself over and over just as it mounted the
nfsroot) unless I disabled SMP. I didn't have any such problems once I
got my 2x300mhz UltraSPARCII processors.
Steve
Matt R Hall wrote:
> I filed a report about this in kernel.org's bugzilla and it has not
> received any comments. I would appreciate it if people could read this
> and provide input. Here is a shortened version of the full report:
>
> Distribution: Debian Unstable (Sid) 2004-09-20
> Hardware Environment:
> Sun Ultra Enterprise II
> 2x200 mHz UltraSPARC I Processor
> 512MB RAM
> 2x4.3GB 7200RPM SCSI Disc
> Toshiba SCSI CD-ROM
>
> Kernel configuration and dmesg output are pasted below for reference purposes.
>
> Software Environment:
> Standard Debian Unstable System
>
> Problem Description:
> Sun Ultra Enterprise 2 was hardlocking in 2.6.xx. Never responded to keyboard
> input. Sometimes would respond to pings and SSH connections for a while, but
> would always lock hard eventually with no errors. Note that this exact same
> system works perfectly in 2.4.xx. I reiterate, SMP functions correctly there.
> Obviously something has changed and caused functionality to break, hence why I
> have marked this bug high severity. IMHO, "stable" kernel series should not
> result in a step back in hardware compatibility.
>
> Disabling SMP resulted in a working system.
>
> Steps to reproduce:
> Compile with the following kernel configuration, except add the SMP option.
> Witness the machine fail to continue functioning.
> -
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2004-09-21 13:24 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
2004-09-21 12:01 ` Jason Wever
2004-09-21 13:00 ` Meelis Roos
2004-09-21 13:24 ` Stephen P. Becker [this message]
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=41502B72.1050205@gentoo.org \
--to=geoman@gentoo.org \
--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.