From: Ken Brownfield <brownfld@irridia.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 Kernel - ASUS CUV4X-DLS Question
Date: Thu, 3 May 2001 14:50:48 -0700 [thread overview]
Message-ID: <200105032150.QAA11098@asooo.flowerfire.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10105031614270.4386-100000@coffee.psychology.mcmaster.ca>
The failure mode I'm seeing is that the timer interrupt disappears.
Hard to schedule processes at that point. I'm not seeing the IRQ issues
personally.
HP's LP1000r machine uses ServerWorks, but still shows the problem. I
only have access to HP SMP hardware currently, but they all have the
same issue. I've heard of Tyan and Asus issues (not just the one
recently posted), though I have an LX machine that has been okay with
2.4.
I've seen the VIA issues, but they aren't related from what I can tell.
--
Ken.
On Thursday, May 3, 2001, at 01:17 PM, Mark Hahn wrote:
>> I just wanted to throw in my two cents and say that there appear to be
>> widespread issues with the APIC code in 2.4.x. I'm tempted to stick my
>
> are there any known problems on non-VIA boards? BX seems to work fine,
> and I haven't heard of any problems from serverworks people.
>
> I'm guessing (wag) that there's some VIA-specific thing that needs
> to be done to get the PIT timer working with io-apic. no real problem
> with apic/ioapic, just some little divergence on VIA's part.
>
>> from APICitis. I realize there are different failure modes and I
>> assume
>> different issues are involved within the APIC code.
>
> are there? I haven't heard anything except "hangs on boot except with
> noapic".
next parent reply other threads:[~2001-05-03 21:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10105031614270.4386-100000@coffee.psychology.mcmaster.ca>
2001-05-03 21:50 ` Ken Brownfield [this message]
2001-05-03 17:51 2.4.4 Kernel - ASUS CUV4X-DLS Question David A. Neal
2001-05-03 18:03 ` Alan Cox
2001-05-03 19:51 ` Ken Brownfield
2001-05-03 20:36 ` Alan Cox
2001-05-03 21:24 ` Hugh Dickins
2001-05-03 21:56 ` Alan Cox
2001-05-03 22:07 ` Ken Brownfield
2001-05-03 22:23 ` Alan Cox
2001-05-03 22:52 ` Ken Brownfield
2001-05-09 1:57 ` J. S. Connell
2001-05-09 8:47 ` 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=200105032150.QAA11098@asooo.flowerfire.com \
--to=brownfld@irridia.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