From: Matt R Hall <mhcomputing@gmail.com>
To: ultralinux@vger.kernel.org
Subject: Kernel.org Bugzilla Bug: Ultra 2 Enterprise: All 2.6.xx SMP kernels hardlock
Date: Tue, 21 Sep 2004 01:38:13 +0000 [thread overview]
Message-ID: <703d4eaa0409201838768c0ff4@mail.gmail.com> (raw)
http://bugme.osdl.org/show_bug.cgi?id428
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.
reply other threads:[~2004-09-21 1:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=703d4eaa0409201838768c0ff4@mail.gmail.com \
--to=mhcomputing@gmail.com \
--cc=ultralinux@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.