Beware the IDEs of Intel

Beware the IDEs of Intel

Post by Bill Campbe » Wed, 16 Aug 1995 04:00:00



There was an article in the Info World I received yesterday telling of
problems with IDE controllers sold with many Intel main boards, and
that this would cause data corruption PARTICULARLY WITH 32 BIT
MULTITASKING OPERATING SYSTEMS.

I don't have the article here at the office so I can't post the name
of the particular IDE controller vendor.

The article claimed that Intel admits knowing about this for over a
year now and hasn't said anything.  Let's see now.  First we hear of
the floating point math bugs (which Intel claims really weren't bugs).
Then it's the Triton chipset which doesn't allow parity checking
memory (which Intel says we don't need because errors are rare (and
not parity checking saves them money)).  Now we have data corruption
with IDE controllers.  All this sure makes Sparcs look better to me.

This is Yet Another Reason to use SCSI for Unix systems.

Bill
--

UUCP:              camco!bill   2835 82nd Avenue S.E. S-100
FAX:           (206) 232-9186   Mercer Island, WA 98040; (206) 947-5591
http://www.celestial.com/
SPEED COSTS MONEY -- HOW FAST DO YOU WANT TO GO?

 
 
 

Beware the IDEs of Intel

Post by Lawrence Kirb » Thu, 17 Aug 1995 04:00:00




Quote:>There was an article in the Info World I received yesterday telling of
>problems with IDE controllers sold with many Intel main boards, and
>that this would cause data corruption PARTICULARLY WITH 32 BIT
>MULTITASKING OPERATING SYSTEMS.

>I don't have the article here at the office so I can't post the name
>of the particular IDE controller vendor.

PC Tech RZ1000 used on Intel Plato/Premiere motherboards (possibly others but
not the latest Triton based ones).

Quote:>The article claimed that Intel admits knowing about this for over a
>year now and hasn't said anything.  Let's see now.  First we hear of
>the floating point math bugs (which Intel claims really weren't bugs).
>Then it's the Triton chipset which doesn't allow parity checking
>memory (which Intel says we don't need because errors are rare (and
>not parity checking saves them money)).  Now we have data corruption
>with IDE controllers.  All this sure makes Sparcs look better to me.

This is being discussed on various newsgroups like comp.sys.intel. There
was a list posted of OSs which did and didn't exhibit problems. Unixware
was listed but not SCO. I hope SCO are looking into the problem.

A possible workaround is to disable the IDE prefetch buffers in the system
BIOS. According to the OS/2 guy who posted this it results in about a 1%
performance decrease so the bug may not be all that disasterous.

Quote:>This is Yet Another Reason to use SCSI for Unix systems.

It looks that way!

--
-----------------------------------------


-----------------------------------------

 
 
 

Beware the IDEs of Intel

Post by Dave Edmondso » Fri, 18 Aug 1995 04:00:00


after reading information about the problem we have
determined that neither open desktop 3.0 nor open server 5.0
are affected by the intel ide chipset bug.

dave.

 
 
 

1. Beware, beware when munging around /var/mail...

A short war story which happened to yours truly this past weekend... Let's
say this was a learning experience ;)

Our campus mail server had been running out of space for the incoming mail
for a while now, so I took advantage of the Mexican Independence holiday
to shut it down and rearrange things.

There I go, merrily defining a new partition, dumping all inboxes onto it
and mounting it in it's place. No errors so far and I was happy as a clam.
To be on the safe side, I decided to get a backup of the whole machine
before letting the users loose on it.

When the machine reboots following the backup, and goes back to runlevel
3, all mail-hell broke loose. Unbeknownst to me (yeah, I know, I SHOULD
have double-checked), the /var/mail mount point had switched group, from
mail to sys, but retaining 1775 permissions. As a result, sendmail was
correctly placing the incoming letters on temp files in /tmp, but mail was
unable to deliver them since it had no write permissions.

By the time I caught it, there were over 1,700 temp mailfiles and very
mystified users who were not receiving mail. A quick chgrp remedied the
operation, but I was still left with MUCHOS undelivered mailfiles. I am
still wondering why the change of group.

Also, after the experience, I checked out three Sol 2.4 hosts I had
recently installed and was surprised to find that /var/mail had 1777
permissions !! It did correctly belong to mail/mail, though. Since I had
just reinstalled one of them from CD, I can only assume this was the
default. Fortunately, there was no security leak here, since these
machines do not receive mail (MX points elsewhere) but this really looks
like something to check into.

Also, in order to clean up /tmp and deliver the bunch of undelivereds, I
whipped up a quick Perl script. It is definitely not a work of art and
Larry Wall would probably find it hilariously funny, but I can either post
it here or send it to anyone in a similar predicament.

Just for the record, all this happened  on a SS20, with Sol 2.3, Perl
5.001m and sendmail v8.6.12.

--


Campus Queretaro

2. lpr daemon in OSF 4.0D

3. *BEWARE* The Hylandertroll aka john gagon of Houston Texas is trolling again *BEWARE*, as evidenced here he has stalked me and my family BEware of Criminal John Gagon

4. Mjordomo error 5

5. lilo lockup with one ide disk on intel 815 motherboard

6. Rebuilding Apache and PHP - ARRRGH!

7. 2.4.19: no DMA for IDE with Intel i845e

8. dlopen and library dependencies

9. FORMATMATING IDE DISKS ON INTEL SOLARIS 2.7

10. Any IDE CDRW supported by Solaris 8 Intel ?

11. Linux 2.0.30 + Intel 440LX Chipst = IDE problem

12. ide problem w/ quantum lct20 & intel 815 mb

13. C++ IDEs for intel versions of UNIX