public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chris Pringle <chris.pringle@miranda.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serial driver 8250 hangs the kernel with the VIA Nehemiah...
Date: Fri, 11 Aug 2006 13:02:08 +0100	[thread overview]
Message-ID: <1155297728.24077.52.camel@localhost.localdomain> (raw)
In-Reply-To: <44DC6524.4000401@miranda.com>

Ar Gwe, 2006-08-11 am 12:08 +0100, ysgrifennodd Chris Pringle:
> > Unlikely as it would affect both. More likely would be that the ISA bus
> > clock is generated off the PCI bus clock and you have one of the
> > multipliers wrong or too high for the board.
> >   
> Thats interesting, but wouldn't this produce strange side affects for 
> the 2.4 kernel as well? 2.4 works fine on both VIAs and Celerons.

That I wonder about. The power management stuff and some other things
that matter for timing are different however.

> I'll give the interrupt disabling a go...

Its just a guess but if you have low latency stuff, you have pre-empt
enabled and you actually depend upon the semantics of inb_p/outb_p
giving delays reliably then I'm not convinced are guarantees are strong
enough

Specifically we don't have any pre-empt protection between the I/O delay
and the I/O so we could violate it as we don't have pre-empt disables in
inb_p/outb_p and if your CPU context switch is quick enough it could
trigger a problem.

Alan


  reply	other threads:[~2006-08-11 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 11:08 Serial driver 8250 hangs the kernel with the VIA Nehemiah Chris Pringle
2006-08-11 12:02 ` Alan Cox [this message]
2006-08-11 15:45   ` Chris Pringle
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11  8:52 Chris Pringle
2006-08-11 10:36 ` 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=1155297728.24077.52.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=chris.pringle@miranda.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