From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: Mark Hounschell <dmarkh@cfl.rr.com>,
Mark Hounschell <markh@compro.net>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
john stultz <johnstul@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor
Date: Tue, 27 Jan 2009 19:33:54 -0500 [thread overview]
Message-ID: <497FA7F2.3060709@cfl.rr.com> (raw)
In-Reply-To: <497FA725.7020503@cfl.rr.com>
Mark Hounschell wrote:
> Borislav Petkov wrote:
>> On Mon, Jan 26, 2009 at 01:26:58PM -0500, Mark Hounschell wrote:
>>
>> [.. ]
>>
>>> If there is anything else I can try, I'm at your disposal.
>> Ok, I just boot-tested a 1000 HZ kernel here and I can't reproduce
>> your problem. Can you please send the failing .config. And also where
>> exactly does your kernel hang during the boot process, can you capture
>> any output and/or enable SysRq to dump backtrace on all cores (SysRq-T)
>> if possible. Finally, what does 'cat /proc/timer_list' on the working
>> kernel say?
>>
>> Thanks.
>>
>
>
> You test booted using a Phenom-II?
>
> The config file is attached. The timer_list while running the 250 Hz 2.6.26.8
> kernel output is below. When it happens I have no keyboard at all. SysRq is not
> functional at this time. Sorry.
>
> Sorry it took so long. I was out of town today.
>
> Timer List Version: v0.3
> HRTIMER_MAX_CLOCK_BASES: 2
> now at 675544989236 nsecs
>
> cpu: 0
> clock 0:
> .index: 0
> .resolution: 1 nsecs
> .get_time: ktime_get_real
> .offset: 1233101890018929078 nsecs
> active timers:
> clock 1:
> .index: 1
> .resolution: 1 nsecs
> .get_time: ktime_get
> .offset: 0 nsecs
> active timers:
> #0: <f31ffec0>, tick_sched_timer, S:01, tick_setup_sched_timer, swapper/0
> # expires at 675548000000 nsecs [in 3010764 nsecs]
> .expires_next : 675548000000 nsecs
> .hres_active : 1
> .nr_events : 170138
> .nohz_mode : 0
> .idle_tick : 0 nsecs
> .tick_stopped : 0
> .idle_jiffies : 0
> .idle_calls : 0
> .idle_sleeps : 0
> .idle_entrytime : 0 nsecs
> .idle_waketime : 0 nsecs
> .idle_exittime : 0 nsecs
> .idle_sleeptime : 0 nsecs
> .last_jiffies : 0
> .next_jiffies : 0
> .idle_expires : 0 nsecs
> jiffies: 93886
>
> cpu: 1
> clock 0:
> .index: 0
> .resolution: 1 nsecs
> .get_time: ktime_get_real
> .offset: 1233101890018929078 nsecs
> active timers:
> clock 1:
> .index: 1
> .resolution: 1 nsecs
> .get_time: ktime_get
> .offset: 0 nsecs
> active timers:
> #0: <f31ffec0>, tick_sched_timer, S:01, tick_setup_sched_timer, swapper/0
> # expires at 675548500000 nsecs [in 3510764 nsecs]
> #1: <f31ffec0>, it_real_fn, S:01, do_setitimer, ntpd/4446
> # expires at 676081032589 nsecs [in 536043353 nsecs]
> #2: <f31ffec0>, hrtimer_wakeup, S:01, futex_wait, nscd/4456
> # expires at 683136927993 nsecs [in 7591938757 nsecs]
> #3: <f31ffec0>, hrtimer_wakeup, S:01, do_nanosleep, cron/4539
> # expires at 711791265959 nsecs [in 36246276723 nsecs]
> #4: <f31ffec0>, it_real_fn, S:01, do_setitimer, qmgr/4549
> # expires at 1001716635269 nsecs [in 326171646033 nsecs]
> #5: <f31ffec0>, it_real_fn, S:01, do_setitimer, master/4517
> # expires at 1001716661669 nsecs [in 326171672433 nsecs]
> #6: <f31ffec0>, hrtimer_wakeup, S:01, futex_wait, nscd/4459
> # expires at 28868136987269 nsecs [in 28192591998033 nsecs]
> .expires_next : 675548500000 nsecs
> .hres_active : 1
> .nr_events : 169510
> .nohz_mode : 0
> .idle_tick : 0 nsecs
> .tick_stopped : 0
> .idle_jiffies : 0
> .idle_calls : 0
> .idle_sleeps : 0
> .idle_entrytime : 0 nsecs
> .idle_waketime : 0 nsecs
> .idle_exittime : 0 nsecs
> .idle_sleeptime : 0 nsecs
> .last_jiffies : 0
> .next_jiffies : 0
> .idle_expires : 0 nsecs
> jiffies: 93886
>
> cpu: 2
> clock 0:
> .index: 0
> .resolution: 1 nsecs
> .get_time: ktime_get_real
> .offset: 1233101890018929078 nsecs
> active timers:
> clock 1:
> .index: 1
> .resolution: 1 nsecs
> .get_time: ktime_get
> .offset: 0 nsecs
> active timers:
> #0: <f31ffec0>, tick_sched_timer, S:01, tick_setup_sched_timer, swapper/0
> # expires at 675549000000 nsecs [in 4010764 nsecs]
> #1: <f31ffec0>, it_real_fn, S:01, do_setitimer, Xorg/3325
> # expires at 675563416492 nsecs [in 18427256 nsecs]
> #2: <f31ffec0>, hrtimer_wakeup, S:01, do_nanosleep, kwrapper/4982
> # expires at 676109815468 nsecs [in 564826232 nsecs]
> #3: <f31ffec0>, hrtimer_wakeup, S:01, futex_wait, nscd/4458
> # expires at 683435589386 nsecs [in 7890600150 nsecs]
> #4: <f31ffec0>, it_real_fn, S:01, do_setitimer, pickup/4548
> # expires at 1001716659224 nsecs [in 326171669988 nsecs]
> .expires_next : 675549000000 nsecs
> .hres_active : 1
> .nr_events : 172253
> .nohz_mode : 0
> .idle_tick : 0 nsecs
> .tick_stopped : 0
> .idle_jiffies : 0
> .idle_calls : 0
> .idle_sleeps : 0
> .idle_entrytime : 0 nsecs
> .idle_waketime : 0 nsecs
> .idle_exittime : 0 nsecs
> .idle_sleeptime : 0 nsecs
> .last_jiffies : 0
> .next_jiffies : 0
> .idle_expires : 0 nsecs
> jiffies: 93886
>
> cpu: 3
> clock 0:
> .index: 0
> .resolution: 1 nsecs
> .get_time: ktime_get_real
> .offset: 1233101890018929078 nsecs
> active timers:
> clock 1:
> .index: 1
> .resolution: 1 nsecs
> .get_time: ktime_get
> .offset: 0 nsecs
> active timers:
> #0: <f31ffec0>, tick_sched_timer, S:01, tick_setup_sched_timer, swapper/0
> # expires at 675545500000 nsecs [in 510764 nsecs]
> #1: <f31ffec0>, sched_rt_period_timer, S:01, enqueue_task_rt, swapper/1
> # expires at 676000000000 nsecs [in 455010764 nsecs]
> #2: <f31ffec0>, hrtimer_wakeup, S:01, futex_wait, thunderbird-bin/5123
> # expires at 689314480389 nsecs [in 13769491153 nsecs]
> #3: <f31ffec0>, hrtimer_wakeup, S:01, futex_wait, thunderbird-bin/5209
> # expires at 689361744389 nsecs [in 13816755153 nsecs]
> #4: <f31ffec0>, hrtimer_wakeup, S:01, futex_wait, nscd/4457
> # expires at 3668136917342 nsecs [in 2992591928106 nsecs]
> .expires_next : 675545500000 nsecs
> .hres_active : 1
> .nr_events : 171267
> .nohz_mode : 0
> .idle_tick : 0 nsecs
> .tick_stopped : 0
> .idle_jiffies : 0
> .idle_calls : 0
> .idle_sleeps : 0
> .idle_entrytime : 0 nsecs
> .idle_waketime : 0 nsecs
> .idle_exittime : 0 nsecs
> .idle_sleeptime : 0 nsecs
> .last_jiffies : 0
> .next_jiffies : 0
> .idle_expires : 0 nsecs
> jiffies: 93886
>
>
> Tick Device: mode: 1
> Clock Event Device: hpet
> max_delta_ns: 2147483647
> min_delta_ns: 5000
> mult: 61496114
> shift: 32
> mode: 3
> next_event: 9223372036854775807 nsecs
> set_next_event: hpet_legacy_next_event
> set_mode: hpet_legacy_set_mode
> event_handler: tick_handle_oneshot_broadcast
> tick_broadcast_mask: 00000000
> tick_broadcast_oneshot_mask: 00000000
>
>
> Tick Device: mode: 1
> Clock Event Device: lapic
> max_delta_ns: 671091850
> min_delta_ns: 1200
> mult: 53686828
> shift: 32
> mode: 3
> next_event: 675548000000 nsecs
> set_next_event: lapic_next_event
> set_mode: lapic_timer_setup
> event_handler: hrtimer_interrupt
>
> Tick Device: mode: 1
> Clock Event Device: lapic
> max_delta_ns: 671091850
> min_delta_ns: 1200
> mult: 53686828
> shift: 32
> mode: 3
> next_event: 675548500000 nsecs
> set_next_event: lapic_next_event
> set_mode: lapic_timer_setup
> event_handler: hrtimer_interrupt
>
> Tick Device: mode: 1
> Clock Event Device: lapic
> max_delta_ns: 671091850
> min_delta_ns: 1200
> mult: 53686828
> shift: 32
> mode: 3
> next_event: 675549000000 nsecs
> set_next_event: lapic_next_event
> set_mode: lapic_timer_setup
> event_handler: hrtimer_interrupt
>
> Tick Device: mode: 1
> Clock Event Device: lapic
> max_delta_ns: 671091850
> min_delta_ns: 1200
> mult: 53686828
> shift: 32
> mode: 3
> next_event: 675545500000 nsecs
> set_next_event: lapic_next_event
> set_mode: lapic_timer_setup
> event_handler: hrtimer_interrupt
>
>
>
> Regards
> Mark
>
Oh I Forgot. The last thing I see on the screen is.
Checking if this processor honours the WP bit even in hypervisor mode... OK.
SLUB: Genslabs=12, HWalign=64, Order=0,3, MinObjects=0, CPUs=4, Nodes=1
Mark
next prev parent reply other threads:[~2009-01-28 0:34 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 12:38 PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor Mark Hounschell
2009-01-19 8:48 ` Mark Hounschell
2009-01-19 12:41 ` Bartlomiej Zolnierkiewicz
2009-01-19 14:45 ` Mark Hounschell
2009-01-19 23:05 ` Mark Hounschell
2009-01-19 14:22 ` Borislav Petkov
2009-01-19 14:54 ` Mark Hounschell
2009-01-19 23:14 ` Mark Hounschell
2009-01-20 0:25 ` john stultz
2009-01-20 9:08 ` Mark Hounschell
2009-01-20 9:37 ` Andreas Herrmann
2009-01-20 21:08 ` Mark Hounschell
2009-01-23 9:34 ` Mark Hounschell
2009-01-23 13:04 ` Andreas Herrmann
2009-01-23 14:47 ` Borislav Petkov
2009-01-23 22:24 ` Mark Hounschell
2009-01-23 22:46 ` Mark Hounschell
2009-01-26 18:26 ` Mark Hounschell
2009-01-27 16:38 ` Borislav Petkov
2009-01-28 0:30 ` Mark Hounschell
2009-01-28 0:33 ` Mark Hounschell [this message]
2009-01-31 9:15 ` Mark Hounschell
2009-02-02 17:05 ` Borislav Petkov
2009-02-03 9:17 ` Mark Hounschell
2009-02-03 15:11 ` Borislav Petkov
2009-02-03 19:15 ` Mark Hounschell
2009-02-05 17:19 ` Mark Hounschell
2009-02-06 13:52 ` Borislav Petkov
2009-02-06 14:11 ` Mark Hounschell
2009-02-06 17:55 ` Mark Hounschell
2009-02-06 22:20 ` Mark Hounschell
2009-02-09 14:18 ` Borislav Petkov
2009-02-09 15:29 ` Mark Hounschell
2009-02-18 13:11 ` Mark Hounschell
2009-02-18 14:18 ` Borislav Petkov
2009-02-18 16:57 ` Mark Hounschell
2009-02-18 17:42 ` Borislav Petkov
2009-02-18 21:16 ` Mark Hounschell
2009-02-19 10:37 ` Mark Hounschell
2009-02-19 14:11 ` Andreas Herrmann
2009-02-19 15:16 ` Mark Hounschell
2009-02-19 15:19 ` Borislav Petkov
2009-02-19 15:54 ` Mark Hounschell
2009-02-20 11:53 ` Andreas Herrmann
2009-02-20 12:34 ` Ingo Molnar
2009-02-20 21:51 ` Andreas Herrmann
2009-02-20 15:43 ` Mark Hounschell
2009-02-20 16:08 ` Andreas Herrmann
2009-02-20 16:38 ` Andreas Herrmann
2009-02-20 17:09 ` Mark Hounschell
2009-02-20 17:40 ` Mark Hounschell
2009-02-20 18:22 ` Andreas Herrmann
2009-02-20 18:28 ` Mark Hounschell
2009-02-20 19:54 ` Mark Hounschell
2009-02-20 20:27 ` Mark Hounschell
2009-02-20 22:28 ` Andreas Herrmann
2009-02-21 1:14 ` Mark Hounschell
2009-02-21 13:20 ` Mark Hounschell
2009-02-20 17:06 ` Mark Hounschell
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=497FA7F2.3060709@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=andreas.herrmann3@amd.com \
--cc=borislav.petkov@amd.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).