From: Greg Norris <haphazard@kc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: lost interrupts with 2.4.1-rc6 and i875p chipset
Date: Sat, 7 Jun 2003 20:07:40 -0500 [thread overview]
Message-ID: <20030608010739.GA1889@glitch.localdomain> (raw)
In-Reply-To: <20030607192008.GA3345@jhereg.dmeyer.net>
On Sat, Jun 07, 2003 at 03:20:08PM -0400, dmeyer@dmeyer.net wrote:
> Followup to this: with 2.4.21-rc7-ac1, I get very different
> behavior. If I boot with noapic, my machine goes into an endless loop
> of
>
> APIC error on CPU0: 40(40)
>
> errors. If I boot regularly (APIC enabled), everything is fine. My
> machine has been up for almost a full day without a single lost
> interrupt message. This, BTW, is with ACPI enabled in both cases.
It looks like -ac1 works for me with apic enabled as well. I haven't
tried rebooting with noapic yet,,,
next prev parent reply other threads:[~2003-06-08 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 11:15 Greg Norris
2003-06-03 12:18 ` Alan Cox
2003-06-03 15:18 ` dmeyer
2003-06-07 19:20 ` dmeyer
2003-06-08 1:07 ` Greg Norris [this message]
[not found] ` <20030603234359.GA690@glitch.localdomain>
2003-06-04 0:29 ` lost interrupts with 2.4.21-rc6 " Greg Norris
2003-06-16 1:13 ` lost interrupts with 2.4.21 and i875p chipset -- resolved (maybe) Greg Norris
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=20030608010739.GA1889@glitch.localdomain \
--to=haphazard@kc.rr.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®