From: Adrian Bunk <bunk@stusta.de>
To: Patrick McFarland <diablod3@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>,
David Howells <dhowells@redhat.com>,
Neil Brown <neilb@cse.unsw.edu.au>,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
linux-kernel@vger.kernel.org, alex@hausnet.ru, mingo@redhat.com
Subject: Re: [Bugme-new] [Bug 7495] New: Kernel periodically hangs.
Date: Sun, 12 Nov 2006 17:47:16 +0100 [thread overview]
Message-ID: <20061112164716.GB3382@stusta.de> (raw)
In-Reply-To: <200611121059.55454.diablod3@gmail.com>
On Sun, Nov 12, 2006 at 10:59:55AM -0500, Patrick McFarland wrote:
>...
> Socket A CPUs are also ungodly common. They're as common as slot 1/socket 370
> Pentium 3s, and, at least with my old P3 board, trying to use APIC on UP
> caused lockups. My Duron 1ghz laptop also does the same thing. (Booting
> either with noapic fixes it).
>...
It might depend on the age of your computer.
Microsoft mandates the presence of an APIC implemented per MADT and all
hardware interrupts connected to an IOAPIC for all servers and desktops
with a "Designed for Windows XP" sticker.
This implies more or less that a working APIC is present in all
non-laptop x86 UP systems manufactured during the last 5 years.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-11-12 16:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611111129.kABBTWgp014081@fire-2.osdl.org>
2006-11-11 18:00 ` [Bugme-new] [Bug 7495] New: Kernel periodically hangs Andrew Morton
2006-11-11 18:10 ` Arjan van de Ven
2006-11-11 18:19 ` Andrew Morton
2006-11-12 11:50 ` Arjan van de Ven
2006-11-12 12:53 ` Adrian Bunk
2006-11-12 13:16 ` Arjan van de Ven
2006-11-12 13:37 ` Adrian Bunk
2006-11-12 13:57 ` Arjan van de Ven
2006-11-12 14:10 ` Adrian Bunk
2006-11-12 14:16 ` Arjan van de Ven
2006-11-12 15:21 ` Adrian Bunk
2006-11-12 15:50 ` Arjan van de Ven
2006-11-12 15:59 ` Patrick McFarland
2006-11-12 16:07 ` Arjan van de Ven
2006-11-12 16:47 ` Adrian Bunk [this message]
2006-11-12 21:45 ` Dave Jones
2006-11-13 2:07 ` Andi Kleen
2006-11-12 19:18 ` Ingo Oeser
2006-11-12 19:34 ` Andrew Morton
2006-11-12 20:32 ` Arjan van de Ven
2006-11-13 6:42 ` Neil Brown
2006-11-13 11:22 ` David Howells
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=20061112164716.GB3382@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=alex@hausnet.ru \
--cc=arjan@infradead.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dhowells@redhat.com \
--cc=diablod3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
/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