From: Ingo Molnar <mingo@elte.hu>
To: Oliver Bock <o.bock@fh-wolfenbuettel.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Realtime: vanilla 2.6.19 with 2.6.19-rt11 patch doesn't boot
Date: Mon, 11 Dec 2006 14:43:54 +0100 [thread overview]
Message-ID: <20061211134354.GB8219@elte.hu> (raw)
In-Reply-To: <200612092001.01542.o.bock@fh-wolfenbuettel.de>
* Oliver Bock <o.bock@fh-wolfenbuettel.de> wrote:
> Hi Ingo,
>
> I tried to boot a vanilla 2.6.19 kernel with your 2.6.19-rt11 patch
> but without success. However, the patch applied without a single error
> and the vanilla kernel (without the patch) works fine so far. As my
> screen just stays black and as there's no HD activity after selecting
> the kernel in grub, I suppose that it might be related to the new
> Areca RAID driver I use (compiled in because all my partitions reside
> on a RAID volume) in conjunction with your patch...
do you have HPET enabled in your .config by any chance?
Ingo
next prev parent reply other threads:[~2006-12-11 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 19:01 Realtime: vanilla 2.6.19 with 2.6.19-rt11 patch doesn't boot Oliver Bock
2006-12-11 13:43 ` Ingo Molnar [this message]
2006-12-11 16:42 ` Oliver Bock
2006-12-11 18:59 ` Ingo Molnar
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=20061211134354.GB8219@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=o.bock@fh-wolfenbuettel.de \
/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