mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: ganzinger@mvista.com
Cc: greg kh <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Calibration issues with USB disc present.
Date: Fri, 11 Nov 2005 13:57:07 -0800	[thread overview]
Message-ID: <1131746228.2542.11.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <43750EFD.3040106@mvista.com>

On Fri, 2005-11-11 at 13:37 -0800, George Anzinger wrote:
> John,
> 
> Have you run into this.  One of the USB disc controllers has the ability to boot the system, 
> however, it needs SMM code to do this.  This SMM code, somehow, causes SMI interrupts (which are 
> higher priority than NMI interrutps and not maskable) which it needs to do its thing.
> 
> Problem is that if one of these occurs while calibrating the TSC or the delay code, it can cause a 
> wrong result.  We have seen both a too long and a too short result (depending on where the interrut 
> happens).
> 
> They have found the root cause of TSC calibration problem.
> Now they ask for the fix or workaround.
> 
> That is the BIOS is periodically interrupted by USB controller and the CPU
> waits during the processing of these interrupts.
> Their experiments say the interrupt interval is 260mSec and the BIOS needs
> 150uSec - 200uSec for processing.
> It is proved that the problem doesn't reproduce by masking such SMI in BIOS.
> They say SMI is for BIOS emulation for connecting legacy devices to USB.
> Without such an emulation it's impossible to boot from USB-FD for instance,
> they say too.

Hmmm. I haven't heard of this issue specifically, but yes, I'm quite
familiar with the pain BIOS SMIs can cause and I'm not surprised that it
would affect the TSC/delay calibration code.

Is this still an issue w/ 2.6.14? I know the new TSC based delay
calibration code is supposed to be SMI resilient, but I haven't really
played with it closely.

Not sure what the best method to move forward would be. I suspect
disabling the SMI code early in boot (I thought the usb legacy handoff
stuff already did this?) would help. Then the actual Linux USB drivers
can take over before we switch from the initrd to the root filesystem.

Greg, do you have a suggestion?

thanks
-john


  reply	other threads:[~2005-11-11 21:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 21:37 George Anzinger
2005-11-11 21:57 ` john stultz [this message]
2005-11-12  5:05   ` Greg KH
2005-11-12 16:06     ` George Anzinger
2005-11-12 21:33       ` Greg KH
2005-11-14 18:56         ` George Anzinger
2005-11-14 18:49           ` Greg KH
2005-11-14 19:46             ` Brad Campbell
2005-11-14 19:43               ` Greg KH
2005-11-14 19:58             ` john stultz
2005-11-14 21:52               ` George Anzinger
2005-11-17  0:03                 ` Max Krasnyansky
2005-11-17  0:30                   ` Lee Revell
2005-11-17 17:43                     ` Max Krasnyansky

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=1131746228.2542.11.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=ganzinger@mvista.com \
    --cc=greg@kroah.com \
    --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

all inboxes | Powered by JetHome®