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

Alan Cox wrote:
> 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.
>   
We don't use any kind of power management (not compiled in) as our 
systems are always on... Is there any timing related options in the 
kernel config you'd recommend I look at?
>   
>> 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
>
> -
> 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/
>   
Okay, I've tried disabling both preemption and interrupts (separately, 
and together) and its still hanging...

I've had the Celeron systems being thrashed for well over 4 days now, 
and they are working fine... Why would the VIA system be any different? 
They have a slightly different CPU speed (the VIAs are 1000MHz, whereas 
the Celerons are 850MHz), but I would expect them to be fully compatible 
otherwise... unless its a microcode bug?

Any more ideas? Do you think writing to port 0x80 could be causing issues?

Thanks,
Chris

-- 

______________________________
Chris Pringle
Software Engineer

Miranda Technologies Ltd.
Hithercroft Road
Wallingford
Oxfordshire OX10 9DG
UK

Tel. +44 1491 820206
Fax. +44 1491 820001
www.miranda.com


  reply	other threads:[~2006-08-11 15:45 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
2006-08-11 15:45   ` Chris Pringle [this message]
  -- 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=44DCA631.9040505@miranda.com \
    --to=chris.pringle@miranda.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.