public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Etchemaite <petchema@concept-micro.com>
To: Tim Moore <timothymoore@bigfoot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD thunderbird oops
Date: Sun, 01 Jul 2001 13:06:35 +0200 (CEST)	[thread overview]
Message-ID: <XFMail.20010701130635.petchema@concept-micro.com> (raw)
In-Reply-To: <3B3B8C47.D1363D6F@bigfoot.com>


On 28-Jun-2001 Tim Moore wrote:
>> (I wrote)
>> Some ASUS boards (mostly P3B-F) would either freeze or self reboot
>> when using PhotoShop 5. Everything else would run perfectly.
>> 
>> Disabling MMX optimizations in this software would "solve" the
>> problem.  Another solution found on the web (sorry, I don't have
>> the URL at hand) is to add two or three additionnal capacitors on
>> the back of the board, to solve the electric instabilities that
>> cause the reboots.
> 
> This is incorrect information.  Abit BP6 early revs suffered under load
> from a 100uF cap (EC10, between the CPU sockets) that should have been
> 1500uF.  This was compounded by a weak or otherwise inadequate power
> supply.
> 
> Having run literally 7 P3F-Fs and 6 of their P2B-F predecessors, not a
> single one had any problems.  They were the premiere overclocking boards
> of their day.

Don't get me wrong, I like ASUS boards, and BX chipset boards were a
very safe choice at the time, that's why this problem was very
disturbing when I experienced it on 2 or 3 boards (out of more than 100,
but I guess many never ran Photoshop since then).

I digged my archives.

Adobe Knowledgebase article about the problem
(http://www.adobe.com/support/techdocs/2256a.htm) mentions spontaneous
reboots with Dell Optiplex GX1, ASUS P2B-F and ASUS P3B-F.

I could not find anything about the problem on ASUS websites at the
time.

(unofficial) P2B-(L)S fixing is documented here:
http://www.turbotech.ch/articles2000/000815-p2bls_rework-01.html

(unofficial) CUBX fixing (some of those are also affected):
http://members.ams.chello.nl/mgherard/html/photoshop.html

Best regards,
Pierre.

  reply	other threads:[~2001-07-01 11:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 14:06 AMD thunderbird oops Alex Deucher
2001-06-26 15:07 ` Alan Cox
2001-06-26 15:26   ` Alex Deucher
2001-06-26 15:33     ` Alan Cox
2001-06-26 15:52       ` Dave Jones
2001-07-06 22:35       ` 2.4.6-ac1 will not build, 2.4.6 ok Tom Diehl
2001-07-07  1:00         ` Steven Cole
2001-06-28 12:55     ` AMD thunderbird oops Pierre Etchemaite
2001-06-28 19:57       ` Tim Moore
2001-07-01 11:06         ` Pierre Etchemaite [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-27 20:06 joeja
2001-06-28 20:33 ` Tim Moore
2001-06-26 13:22 Thomas Foerster
2001-06-26 13:45 ` Alan Cox
2001-06-26  8:26 Thomas Foerster
2001-06-26  9:09 ` Luigi Genoni
2001-06-25 16:24 joeja
2001-06-25 16:35 ` Keith Owens
2001-06-25  3:17 joeja
2001-06-25  6:55 ` Alan Cox
2001-06-25  7:05   ` Alexander V. Bilichenko
2001-06-25 20:33   ` Dan Hollis
2001-06-26  7:39   ` Thomas Kotzian
2001-06-25  9:40 ` Luigi Genoni

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=XFMail.20010701130635.petchema@concept-micro.com \
    --to=petchema@concept-micro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timothymoore@bigfoot.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox