From: jc254@newton.cam.ac.uk (Jonathan H N Chin)
To: linux-kernel@vger.kernel.org
Subject: Re: IO-APIC -- lockup on machine if enabled
Date: Wed, 13 Mar 2002 15:58:29 GMT [thread overview]
Message-ID: <200203131558.g2DFwT118218@edge.newton.cam.ac.uk> (raw)
In-Reply-To: <20020313083422.3262cb35.fryman@cc.gatech.edu> <20020313083422.3262cb35.fryman@cc.gatech.edu> <20020313151024.G7658@suse.de>
Dave Jones <davej@suse.de> writes:
>On Wed, Mar 13, 2002 at 08:34:22AM -0500, Josh Fryman wrote:
> > i have a new laptop (Dell Latitude C610) running 2.4.18-rc4. when i built the
> > new kernel, i thought i would amuse myself by turning on IO-APIC.
> "Don't do that" 8-)
Unfortunately, at least on my C800 here, not using it breaks IEEE1394:
kernel: ohci1394_0: Waking dma ctx=2 ... processing is probably too slow
and communication breaks down shortly after (have to unload/reload the
modules to make it work again). On the other hand, with IO-APIC + Local
APIC enabled (APM and ACPI disabled) firewire works fine.
I note that W2K on the same machine appears to have no trouble using
both IEEE1394 and power management together. (I have booted W2K less
than ten times though versus half a year of linux use, so this may be
a false impression.)
-jonathan
--
Jonathan H N Chin, 1 dan | deputy computer | Newton Institute, Cambridge, UK
<jc254@newton.cam.ac.uk> | systems mangler | tel/fax: +44 1223 335986/330508
"respondeo etsi mutabor" --Rosenstock-Huessy
next prev parent reply other threads:[~2002-03-13 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 13:34 Josh Fryman
2002-03-13 14:10 ` Dave Jones
2002-03-13 15:58 ` Jonathan H N Chin [this message]
2002-03-13 20:52 Mikael Pettersson
2002-03-13 22:41 ` Alan Cox
2002-03-15 10:05 ` Matthias Andree
2002-03-15 13:07 ` Mikael Pettersson
2002-03-13 20:53 Mikael Pettersson
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=200203131558.g2DFwT118218@edge.newton.cam.ac.uk \
--to=jc254@newton.cam.ac.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 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®