archive mirror
 help / color / mirror / Atom feed
From: Jan Kasprzak <>
Cc: Mark Hahn <>,,
	Petr Konecny <>,
	"Bruno A. Crespo" <>,
	Denis Vlasenko <>,
	Alan Cox <>
Subject: AMD 768 erratum 10 (solved: AMD 760MPX DMA lockup)
Date: Wed, 25 Sep 2002 15:24:22 +0200	[thread overview]
Message-ID: <> (raw)

	Hello, all!

two weeks ago I've posted to the LKML the following message:

: my dual athlon box is unstable in some situations. I can consistently
: lock it up by running the following code:
: fd = open("/dev/hda3", O_RDWR);
: for (i=0; i<1024*1024; i++) {
:         read(fd, buffer, 8192);
:         lseek(fd, -8192, SEEK_CUR);
:         write(fd, buffer, 8192);
: }

	I think I have been hit by AMD 768 southbridge erratum number 10.
After plugging in the PS/2 mouse, the server is able to run 10 iterations
of bonnie++ without any problem (w/o PS/2 mouse it locks up in first
or second iterations).

	I want to ask everyone who replied to me that the above code
works for him on the 760MPX-based system to re-run the above code
(or run bonnie++ benchmark several times in a loop), but _without_
the PS/2 mouse connected?

	Since this is an official AMD errata, we should have a work-around
for this, or at least the big fat warning during boot, when the 768
southbridge is detected - something like the following:

WARNING: Using the system with AMD 768 southbridge without the PS/2
WARNING: mouse plugged in can cause instabilities. See the AMD 768 erratum #10

	The AMD 768 Revision Guide is at the following URL:

the erratum #10 is described on page 7 (pstotext output, manually edited):

: 10	Multiprocessor System May Hang While in FULL APIC Mode
: 	and IOAPIC Interrupt is Masked
: Products Affected. B1, B2
: Normal Specified Operation. The AMD-768 peripheral bus controller is
: designed to support FULL APIC mode in multiprocessor systems for system
: management events. If an interrupt is masked in the APIC controller of
: the AMD-768, then the corresponding interrupt message should not be
: sent to the processor via the 3-wire APIC bus.
: Non-conformance. The AMD-768 peripheral bus controller will send an
: interrupt message via the 3-wire APIC bus regardless if the interrupt
: is masked or not.
: Potential Effect on System. Since the processor had previously masked
: the APIC interrupt, it is not expecting to receive future APIC messages
: for the masked interrupt. The APIC controller will continuously send
: the interrupt message via the 3-wire bus until a processor accepts the
: message, causing the system to hang.
: A system hang has been observed when executing a server shutdown
: command in Novell Netware versions 5.0 or 5.1 while using a serial
: mouse. During the server shutdown sequence, software writes an invalid
: CPU ID to the IOAPIC redirection table, and the system does not
: complete the shutdown.
: Note: No failure has been observed when using a PS/2 mouse.
: Suggested Workaround. None.
: Resolution Status: No fix planned.

| Jan "Yenya" Kasprzak  <kas at { - work | - private}> |
| GPG: ID 1024/D3498839      Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
|   Czech Linux Homepage: |
|----------- If you want the holes in your knowledge showing up -----------|
|----------- try teaching someone.                  -- Alan Cox -----------|

             reply	other threads:[~2002-09-25 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 13:24 Jan Kasprzak [this message]
2002-09-26 15:08 ` AMD 768 erratum 10 (solved: AMD 760MPX DMA lockup) Alan Cox
2002-09-26 15:34   ` Dave Jones
2002-09-26 16:51     ` Alan Cox
2002-09-26 16:08 Manfred Spraul
2002-09-27  6:46 ` Jan Kasprzak
2002-09-30 21:47   ` Maxwell Spangler
2002-09-27 14:24 Bruno A. Crespo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).