linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Kathy Frazier <kfrazier@mdc-dayton.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: RE: Interrupt doesn't make it to the 8259 on a ASUS P4PE mobo
Date: Tue, 15 Jul 2003 11:31:17 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307151125400.15686@chaos> (raw)
In-Reply-To: <PMEMILJKPKGMMELCJCIGOEKNCCAA.kfrazier@mdc-dayton.com>

On Tue, 15 Jul 2003, Kathy Frazier wrote:

> Thanks for your reply, Andi.
>
> >> We have a proprietary PCI board installed in a (UP) system with an ASUS
> P4PE
> >> motherboard (uses Intel 845PE chipset). This system is running Red Hat
> 9.0
>
> >Have you checked the 845 errata sheets on the Intel website?
> >Perhaps it is some known hardware bug.
>
> >One thing you could try is to use Local APIC / IO APIC interrupt processing
> >instead of 8259.
>
> Our hardware engineer has combed the Intel and ASUS websites, but found
> nothing.  I'll give the APIC a try and see if I get different results and
> let you know.
>
> >>
> >> /* start timer */
> >> dmatimer.expires = jiffies + 0.5*HZ;
>
> >That's a serious bug. You cannot use floating point in the kernel.
> >It will corrupt the FP state of the user process.
>
> HZ on the INTEL platform is 100, so this should simply add 50 to the current
> value of jiffies.  Besides, assigning the value to the unsigned int field
> (expires) will truncate it to an integer anyway.  Is there a more
> appropriate way to handle a short timeout?

It will truncate it at runtime.

I suggest

	dmatimer.expires = jiffies + HZ/2;

Also, you you need to use the time_before() macro, like

	while ( time_before(jiffies, dmatimer.expires) )
            do_something();

... so you don't have a timer-wrap problem during jiffie rollover if
you haven't already done so (I don't have your source here).

>
> Thanks,
> Kathy


Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


  reply	other threads:[~2003-07-15 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3el0stw23.fsf@averell.firstfloor.org>
2003-07-15 16:14 ` Kathy Frazier
2003-07-15 15:31   ` Richard B. Johnson [this message]
2003-07-15 15:58     ` SCSI ATA driver in 2.4.22 ? Jeff Mock
2003-07-15 16:14       ` Jeff Garzik
2003-07-15 17:06   ` Interrupt doesn't make it to the 8259 on a ASUS P4PE mobo Brian Gerst
2003-07-15 17:43     ` Jamie Lokier
2003-07-15 17:59     ` Luciano Miguel Ferreira Rocha
2003-07-15 18:24       ` Brian Gerst
2003-07-15 18:44         ` Alan Cox
2003-07-15 19:44           ` Jamie Lokier
2003-07-20 21:04           ` Riley Williams
2003-07-20 22:25             ` Jeremy Fitzhardinge
     [not found] <Pine.LNX.4.53.0307141833190.4354@chaos>
2003-07-15 16:52 ` Kathy Frazier
2003-07-14 21:35 Kathy Frazier

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.53.0307151125400.15686@chaos \
    --to=root@chaos.analogic.com \
    --cc=ak@muc.de \
    --cc=kfrazier@mdc-dayton.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='RE: Interrupt doesn'\''t make it to the 8259 on a ASUS P4PE mobo' \
    /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

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).