linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxwell Spangler <maxwax@speakeasy.net>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: AMD 768 erratum 10 (solved: AMD 760MPX DMA lockup)
Date: Mon, 30 Sep 2002 17:47:45 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0209301746350.10704-100000@tyan.doghouse.com> (raw)
In-Reply-To: <20020927084601.C25704@fi.muni.cz>


Does this mouse have to be actively used...

Could one plug a cheap ps/2 mouse into that port and yet continue to use a USB 
mouse if X is configured to use it?

What is actually happening that causes the ps/2 mouse to cure this or any 
other problem of this nature?

Curious.

On Fri, 27 Sep 2002, Jan Kasprzak wrote:

> Manfred Spraul wrote:
> : The errata is not PS/2 mouse specific:
> : it says that the io apic doesn't implement masking interrupts correctly.
> 
> 	Yes, but it says that problem has not been observed when running
> with PS/2 mouse. Which is exactly what I observe on my system.
> : 
> : Linux uses masking aggressively - disable_irq() is implemented by 
> : masking the interrupt in the io apic. I'm surprised that this doesn't 
> : cause frequent problems.
> 
> 	The errata does not say that the interrupt masking in the IO-APIC
> does not work in all situations. I read it as the lock-up (caused by
> nonfunctional IRQ masking) sometimes occurs, nobody knows when,
> and it has been observed on some Netware boxes w/o the PS/2 mouse.
> Maybe even AMD does not know exactly what is going on there.
> 
> : Regarding Jan's problem: I'm not sure if his problems are related to 
> : this errata. It says that using a PS/2 mouse instead of a serial mouse 
> : with Novell Netward avoids the hang during shutdown, probably because 
> : then netware doesn't mask the irq.
> 
> 	Yes, it may be a faulty board as well, but I think it is
> too close to this AMD errata.
> 
> -Yenya
> 
> -- 
> | Jan "Yenya" Kasprzak  <kas at {fi.muni.cz - work | yenya.net - private}> |
> | GPG: ID 1024/D3498839      Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
> | http://www.fi.muni.cz/~kas/   Czech Linux Homepage: http://www.linux.cz/ |
> |----------- If you want the holes in your knowledge showing up -----------|
> |----------- try teaching someone.                  -- Alan Cox -----------|
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- ----------------------------------------------------------------------------
Maxwell Spangler                                                
Program Writer                                              
Greenbelt, Maryland, U.S.A.                         
Washington D.C. Metropolitan Area 


  reply	other threads:[~2002-09-30 21:42 UTC|newest]

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

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=Pine.LNX.4.33.0209301746350.10704-100000@tyan.doghouse.com \
    --to=maxwax@speakeasy.net \
    --cc=kas@informatics.muni.cz \
    --cc=linux-kernel@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 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).