Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Pentium bug and Solaris 2.5.1 SMP

Posted on 1997-11-13
1
Medium Priority
?
336 Views
Last Modified: 2013-12-27
Hi,

some days before it was a discussion about Pentium bug
(lock cmpxchg8b qword ptrax -  F0 0F C7 C8) which hangs the machine.

I've tested it on several configurations and it is really very bad.

But what I'd like to know is why it happens on 2xPentium Solaris 2.5.1

I'm not a specialist in Solaris kernel and multitasking, but I have a
question which may be stupid.

If I execute the command I hang one of my two processors. Why the system
can't work on the rest one performing normal (or emergency) shutdown or
notifying sysadmin about the problem? Am I right that such a command is
executed only on one processor or not?

If yes then is it a bug in Solaris OS?

Is it a problem in Solaris or it is the problem of the SMP architecture on Intel platform (bus lock, etc.)?

Thanks in advance

Vitali

0
Comment
Question by:korostel
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 1

Accepted Solution

by:
Belar earned 100 total points
ID: 2007767
Well, to answer your first question. It happens on all pentium or pentium MMX. Pentium Pro and Pentium II are unaffected. For example it crashes my linux SMP so it is not OS related.

About your second answer, yes, indeed only one of the CPU is halted. It might be possible with the appropriate code for the second CPU to "reboot" the first. I actually saw a discussion about this exact issue in the linux-kernel mailing list. The only problem with this "fix" is that if an attacker just do : crash&crash&. It will hang both CPUs without giving time to them to reboot their peer. As for why, there is no notification that one of your cpu is halted. It is simple. I think Solaris or any other OS vendors didn't think it was possible to do such an event.

3) Solaris is not buggy. It is Intel that screwed up.

For more info on the bug go at www.x86.org (or is it com?) The exploit is pretty well documented there.
0

Featured Post

What’s Wrong with Your Cloud Strategy ?

Even as many CIOs are embracing a cloud-first strategy, the reality is that moving to the cloud is a lengthy process and the end-state is likely to be a blend of multiple clouds—public and private. Learn why multicloud solutions matter in this webinar by Nimble Storage.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Hello fellow BSD lovers, I've created a patch process for patching openjdk6 for BSD (FreeBSD specifically), although I tried to keep all BSD versions in mind when creating my patch. Welcome to OpenJDK6 on BSD First let me start with a little …
When you do backups in the Solaris Operating System, the file system must be inactive. Otherwise, the output may be inconsistent. A file system is inactive when it's unmounted or it's write-locked by the operating system. Although the fssnap utility…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
Suggested Courses

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question