From: Oliver Bock <o.bock@fh-wolfenbuettel.de>
To: Ingo Molnar <mingo@elte.hu>
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 17:42:30 +0100 [thread overview]
Message-ID: <200612111742.30838.o.bock@fh-wolfenbuettel.de> (raw)
In-Reply-To: <20061211134354.GB8219@elte.hu>
Hi Ingo,
Thanks for your reply. I tried -rt12 and could successfully boot my system.
However, now I find the following during boot:
registering clocksource pit
[<c0134a8f>] clocksource_register+0x2f/0x130
[<c0252ef4>] sysdev_register+0xf4/0x100
[<c03a0070>] init_pit_clocksource+0x60/0x70
[<c01003bf>] init+0x8f/0x310
[<c010311e>] ret_from_fork+0x6/0x1c
[<c0100330>] init+0x0/0x310
[<c0100330>] init+0x0/0x310
[<c0103d53>] kernel_thread_helper+0x7/0x14
=======================
registering clocksource tsc
[<c0134a8f>] clocksource_register+0x2f/0x130
[<c0124796>] __mod_timer+0x86/0xb0
[<c03a032d>] init_tsc_clocksource+0x18d/0x1f0
[<c01003bf>] init+0x8f/0x310
[<c010311e>] ret_from_fork+0x6/0x1c
[<c0100330>] init+0x0/0x310
[<c0100330>] init+0x0/0x310
[<c0103d53>] kernel_thread_helper+0x7/0x14
=======================
registering clocksource jiffies
[<c0134a8f>] clocksource_register+0x2f/0x130
[<c01a635a>] sysfs_create_file+0x3a/0x50
[<c03aaf7f>] init_jiffies_clocksource+0xf/0x20
[<c01003bf>] init+0x8f/0x310
[<c010311e>] ret_from_fork+0x6/0x1c
[<c0100330>] init+0x0/0x310
[<c0100330>] init+0x0/0x310
[<c0103d53>] kernel_thread_helper+0x7/0x14
=======================
[...]
registering clocksource acpi_pm
[<c0134a8f>] clocksource_register+0x2f/0x130
[<c03b707a>] init_acpi_pm_clocksource+0xba/0x130
[<c0255ede>] class_create+0x4e/0x70
[<c01003bf>] init+0x8f/0x310
[<c010311e>] ret_from_fork+0x6/0x1c
[<c0100330>] init+0x0/0x310
[<c0100330>] init+0x0/0x310
[<c0103d53>] kernel_thread_helper+0x7/0x14
=======================
This is my .config regarding HPET:
CONFIG_HPET_TIMER=y
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
Oliver
On Monday 11 December 2006 14:43, you wrote:
> * 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 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 19:01 Oliver Bock
2006-12-11 13:43 ` Ingo Molnar
2006-12-11 16:42 ` Oliver Bock [this message]
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=200612111742.30838.o.bock@fh-wolfenbuettel.de \
--to=o.bock@fh-wolfenbuettel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®