From: Pavel Machek <pavel@ucw.cz>
To: Will Dinkel <wdinkel@atipa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64 interrupts handled by CPU0 only
Date: Sat, 10 May 2003 22:47:01 +0200 [thread overview]
Message-ID: <20030510204701.GB577@elf.ucw.cz> (raw)
In-Reply-To: <1052326953.22518.184.camel@zappa>
Hi!
> I see this behavior on systems using either the MSI or Tyan dual-opteron
> boards. I also see it on RedHat's preview x86_64 distribution (kernel
> version 2.4.20-9.2).
>
> I'm still trying to get 2.5.69 to boot correctly, so I don't have
> results there yet. On RedHat it hangs after "Booting the kernel..."
> (and yes, I have CONFIG_VT, and CONFIG_VT_CONSOLE on). Any ideas?
Turn *on* CONFIG_HUGETLB_PAGE or how is it called.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-05-10 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 17:02 x86_64 interrupts handled by CPU0 only Will Dinkel
2003-05-07 20:46 ` Arjan van de Ven
2003-05-10 20:47 ` Pavel Machek [this message]
[not found] <1052326953.22518.184.camel@zappa.suse.lists.linux.kernel>
2003-05-07 21:12 ` Andi Kleen
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=20030510204701.GB577@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=wdinkel@atipa.com \
/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