On Tue, 27 Jun 2006 19:23:53 +0200, Roman Zippel said: I finished bisecting - the problem code is somewhere in fix-and-optimize-clock-source-update.patch (which should narrow things down a bunch). > Could you please try the patch below? This should better locate which of > the values goes wrong. > + if (ts->tv_nsec < 0 || nsecs < 0) > + printk("unexpected nsec: %ld,%Ld\n", ts->tv_nsec, nsecs); > timespec_add_ns(ts, nsecs); I changed it slightly to also do a dump_stack() in case that mattered. I get: [ 22.562394] Time: tsc clocksource has been installed. (Does the clocksource matter here?) [ 25.241589] audit(1151434000.4294965869:2): policy loaded auid=4294967295 [ 25.260931] audit(1151434020.4294967250:3): avc: granted { load_policy } for pid=1 comm="init" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:object_r:security_t:s0 tclass=security [ 25.326263] unexpected nsec: -925155963,1574943831 [ 25.346995] <c01031ff> show_trace_log_lvl+0x54/0x174 <c01037bd> show_trace+0xd/0x10 [ 25.368300] <c010385a> dump_stack+0x19/0x1b <c011a4f6> getnstimeofday+0x99/0xd0 [ 25.389785] <c0125428> ktime_get_ts+0x14/0x3f <c0110ba2> copy_process+0x39f/0x10d8 [ 25.411587] <c0111b17> do_fork+0x8d/0x16a <c0100a24> kernel_thread+0x6c/0x74 [ 25.433731] <c011fc35> __call_usermodehelper+0x2b/0x44 <c0120186> run_workqueue+0x94/0xe9 [ 25.456400] <c0120668> worker_thread+0xe1/0x115 <c0122ace> kthread+0xb0/0xdc [ 25.479234] <c01006c5> kernel_thread_helper+0x5/0xb [ 25.551830] unexpected nsec: -347554993,1412474976 [ 25.574337] <c01031ff> show_trace_log_lvl+0x54/0x174 <c01037bd> show_trace+0xd/0x10 [ 25.597459] <c010385a> dump_stack+0x19/0x1b <c011a4f6> getnstimeofday+0x99/0xd0 [ 25.620925] <c0125428> ktime_get_ts+0x14/0x3f <c0110ba2> copy_process+0x39f/0x10d8 [ 25.644923] <c0111b17> do_fork+0x8d/0x16a <c0100998> sys_clone+0x25/0x2a [ 25.669118] <c010224d> sysenter_past_esp+0x56/0x79 [ 25.693213] unexpected nsec: -1276931327,751175871 [ 25.717404] <c01031ff> show_trace_log_lvl+0x54/0x174 <c01037bd> show_trace+0xd/0x10 [ 25.742269] <c010385a> dump_stack+0x19/0x1b <c011a4f6> getnstimeofday+0x99/0xd0 [ 25.767382] <c0125428> ktime_get_ts+0x14/0x3f <c0110ba2> copy_process+0x39f/0x10d8 [ 25.792768] <c0111b17> do_fork+0x8d/0x16a <c0100998> sys_clone+0x25/0x2a [ 25.818386] <c010224d> sysenter_past_esp+0x56/0x79 [ 74.653939] Real Time Clock Driver v1.12ac (Later on, during udev processing, we get: [ 92.087113] ACPI: CPU0 (power states: C1[C1] C2[C2]) [ 92.087122] ACPI: Processor [CPU0] (supports 8 throttling states) [ 92.120270] ACPI: Thermal Zone [THM] (70 C) [ 72.242000] Time: acpi_pm clocksource has been installed. and the timestamps steps back about 20 seconds.... That help any?
Attachment:
pgplDJd5L3qjL.pgp
Description: PGP signature
- Follow-Ups:
- Re: 2.6.17-mm2 hrtimer code wedges at boot?
- From: john stultz <[email protected]>
- Re: 2.6.17-mm2 hrtimer code wedges at boot?
- References:
- 2.6.17-mm2
- From: Andrew Morton <[email protected]>
- 2.6.17-mm2 hrtimer code wedges at boot?
- From: [email protected]
- Re: 2.6.17-mm2 hrtimer code wedges at boot?
- From: Roman Zippel <[email protected]>
- Re: 2.6.17-mm2 hrtimer code wedges at boot?
- From: [email protected]
- Re: 2.6.17-mm2 hrtimer code wedges at boot?
- From: Roman Zippel <[email protected]>
- Re: 2.6.17-mm2 hrtimer code wedges at boot?
- From: Roman Zippel <[email protected]>
- 2.6.17-mm2
- Prev by Date: Re: 2GB or 4GB SD support for Linux 2.6.17?
- Next by Date: Re: [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated on i386
- Previous by thread: Re: 2.6.17-mm2 hrtimer code wedges at boot?
- Next by thread: Re: 2.6.17-mm2 hrtimer code wedges at boot?
- Index(es):