Re: 2.6.16-mm1

["Rafael J. Wysocki" <rjw@sisk.pl>]

On Friday 24 March 2006 01:49, john stultz wrote:
> On Thu, 2006-03-23 at 16:04 -0800, Andrew Morton wrote:
> > "R. J. Wysocki" <Rafal.Wysocki@fuw.edu.pl> wrote:
> > >
> > > On Thursday 23 March 2006 10:40, Andrew Morton wrote:
> > > > 
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16/2.6.16-mm1/
> > > 
> > > On a uniprocessor AMD64 w/ CONFIG_SMP unset (2.6.16-rc6-mm2 works on this box
> > > just fine, .config attached):
> > 
> > hm, uniproc x86_64 seems to cause problems sometimes.  I should test it more.
> > 
> > > }-- snip --{
> > > PID hash table entries: 4096 (order: 12, 32768 bytes)
> > > time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.
> > > time.c: Detected 1795.400 MHz processor.
> > > disabling early console
> > > Console: colour dummy device 80x25
> > > time.c: Lost 103 timer tick(s)! rip 10:start_kernel+0x121/0x220
> > > last cli 0x0
> > > last cli caller 0x0
> > > time.c: Lost 3 timer tick(s)! rip 10:__do_softirq+0x44/0xc0
> > > last cli 0x0
> > > last cli caller 0x0
> > > time.c: Lost 3 timer tick(s)! rip 10:__do_softirq+0x44/0xc0
> 
> It seems report_lost_ticks has been set to one w/ 2.6.16-mm1, thus these
> debug messages will be shown.
> 
> Rafael: To properly compare, could you boot 2.6.16-rc6-mm2 w/ the
> "report_lost_ticks" boot option and see if the same sort of messages do
> not appear?

It looks similar but not the same:

}-- snip --{
Kernel command line: root=/dev/hdc6 vga=792 selinux=0 noapic resume=/dev/hdc3 console=ttyS0,57600 console=tty0 earlyprintk=serial,ttyS0,5760
0 debug report_lost_ticks init=/bin/bash
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.
time.c: Detected 1795.371 MHz processor.
disabling early console
Console: colour dummy device 80x25
time.c: Lost 104 timer tick(s)! rip start_kernel+0x11d/0x210)
time.c: Lost 2 timer tick(s)! rip __do_softirq+0x44/0xb0)
time.c: Lost 2 timer tick(s)! rip __do_softirq+0x44/0xb0)
time.c: Lost 1 timer tick(s)! rip __do_softirq+0x50/0xb0)
time.c: Lost 2 timer tick(s)! rip run_timer_softirq+0x0/0x1f0)
time.c: Lost 2 timer tick(s)! rip run_timer_softirq+0x1/0x1f0)
time.c: Lost 1 timer tick(s)! rip hrtimer_run_queues+0x1/0x120)
time.c: Lost 2 timer tick(s)! rip hrtimer_run_queues+0x43/0x120)
time.c: Lost 2 timer tick(s)! rip hrtimer_run_queues+0x58/0x120)
time.c: Lost 2 timer tick(s)! rip _spin_lock_irq+0x1/0x30)
time.c: Lost 2 timer tick(s)! rip _spin_lock_irq+0x1/0x30)
time.c: Lost 1 timer tick(s)! rip _spin_lock_irq+0x4/0x30)
time.c: Lost 2 timer tick(s)! rip _spin_unlock_irq+0xf/0x40)
time.c: Lost 2 timer tick(s)! rip _spin_unlock_irq+0x30/0x40)
time.c: Lost 1 timer tick(s)! rip hrtimer_run_queues+0x77/0x120)
time.c: Lost 2 timer tick(s)! rip hrtimer_run_queues+0x77/0x120)
time.c: Lost 2 timer tick(s)! rip _spin_lock_irq+0x8/0x30)
time.c: Lost 2 timer tick(s)! rip _spin_unlock_irq+0xf/0x40)
time.c: Lost 1 timer tick(s)! rip sub_preempt_count+0x26/0x60)
time.c: Lost 2 timer tick(s)! rip _spin_unlock_irq+0x31/0x40)
time.c: Lost 2 timer tick(s)! rip hrtimer_run_queues+0x112/0x120)
time.c: Lost 2 timer tick(s)! rip _spin_lock_irq+0x1/0x30)
time.c: Lost 1 timer tick(s)! rip _spin_unlock_irq+0xf/0x40)
time.c: Lost 2 timer tick(s)! rip run_timer_softirq+0x1da/0x1f0)
time.c: Lost 2 timer tick(s)! rip __do_softirq+0x44/0xb0)
time.c: Lost 2 timer tick(s)! rip __do_softirq+0x50/0xb0)
time.c: Lost 1 timer tick(s)! rip hrtimer_run_queues+0x58/0x120)
}-- cut --{

Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/