From: Frans Pop <elendil@planet.nl>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [2.6.23-rc8-mm2] System hangs (loops?) during boot
Date: Mon, 1 Oct 2007 02:07:33 +0200 [thread overview]
Message-ID: <200710010207.34430.elendil@planet.nl> (raw)
In-Reply-To: <20071001000037.475473bd@laptop.hypervisor.org>
On Monday 01 October 2007, you wrote:
> On Sun, 30 Sep 2007 23:50:29 +0200 Frans Pop (FP) wrote:
> > I'm not sure what you mean. I fetched the branch I think you referred
> > to [1], but when I did a merge of that on top of v2.6.23-rc8-mm2 I
> > got "Already up-to-date", so AFAICT that branch is fully merged into mm
> > and I'm already running with you latest code...
>
> I was suggesting to download 2.6.23-rc8 and applying the -hrt patchset at
> http://www.kernel.org/pub/linux/kernel/people/tglx/hrtimers/2.6.23-rc8/
> on top of it.
Ah, OK. I'm afraid that was not at all clear from your previous message :-/
During 'make oldconfig' I got a config question about "CPU idle support",
which does not seem to be in rc8-mm2; is that correct? I answered N.
> That excludes all the extra stuff in -mm and should give us a good hint
> whether HPET is really at fault.
The system does boot with rc8 + hrt1.
Andrew: any suggestions on how to trace the "real" culprit for the hang?
Udo: I did see one issue during boot with this rc8 + hrt1 kernel.
System is Debian unstable.
Setting the system clock..
select() to /dev/rtc to wait for clock tick timed out
Also, if the patchset really is not the same as in mm, then that at least
partially invalidates this test.
Relevant lines from dmesg diff:
-Linux version 2.6.23-rc6 [...]
+Linux version 2.6.23-rc8-hrt1 [...]
[...]
+hpet clockevent registered
+hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
+hpet0: 3 64-bit timers, 14318180 Hz
ACPI: RTC can wake from S4
Time: tsc clocksource has been installed.
[...]
-Marking TSC unstable due to: possible TSC halt in C2.
-Time: acpi_pm clocksource has been installed.
[...]
-Clocksource tsc unstable (delta = -473964036 ns)
[...]
Real Time Clock Driver v1.12ac
[...]
+Marking TSC unstable due to: cpufreq changes.
+Time: hpet clocksource has been installed.
+Clocksource tsc unstable (delta = -125526392 ns)
# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
hpet acpi_pm pit jiffies tsc
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
hpet
I noted that acpi_pm is no longer mentioned in dmesg, but is still present.
Cheers,
FJP
next prev parent reply other threads:[~2007-10-01 0:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 20:25 [2.6.23-rc8-mm2] System hangs (loops?) during boot Frans Pop
2007-09-29 0:32 ` Frans Pop
2007-09-29 8:37 ` Andrew Morton
[not found] ` <200709292140.23593.elendil@planet.nl>
2007-09-29 20:02 ` Andrew Morton
2007-09-30 13:44 ` Udo A. Steinberg
2007-09-30 21:50 ` Frans Pop
2007-09-30 22:00 ` Udo A. Steinberg
2007-10-01 0:07 ` Frans Pop [this message]
2007-10-01 0:44 ` Udo A. Steinberg
2007-10-01 1:12 ` Frans Pop
2007-10-01 2:24 ` Andrew Morton
2007-09-29 22:15 ` [2.6.23-rc8-mm2] kernel BUG at mm/slab.c:591! | invalid opcode: 0000 [#1] SMP Frans Pop
2007-09-30 10:45 ` Andrew Morton
2007-09-30 22:30 ` Miklos Szeredi
2007-09-30 22:59 ` [2.6.23-rc8-mm2] Fails to resume from s2mem (was:kernel BUG at mm/slab.c:591! ...) Frans Pop
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=200710010207.34430.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=us15@os.inf.tu-dresden.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