mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Reuben Farrelly <reuben-lkml@reub.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-mm2
Date: Thu, 30 Mar 2006 01:43:41 -0800	[thread overview]
Message-ID: <20060330014341.18c53b0b.akpm@osdl.org> (raw)
In-Reply-To: <442BA46F.5040601@reub.net>

Reuben Farrelly <reuben-lkml@reub.net> wrote:
>
> 
> 
> On 28/03/2006 8:35 p.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16/2.6.16-mm2/
> > 
> > 
> > - It seems to compile.
> 
> I've just upgraded from an i386 to an x86_64.  It was an.... ordeal, but the 
> kernel was the least of the worries.  Userland upgrades were a pain.
> 
> Using the same config as on i386 apart from the differences that a 'make 
> oldconfig' threw up on the new architecture, I am now seeing some problems with 
> the x86_64 that I was not seeing on i386 on this release.
> 
> Kernel messages like this when booting up:
> 
> time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.
> time.c: Detected 3000.283 MHz processor.
> Console: colour VGA+ 80x25
> time.c: Lost 85 timer tick(s)! rip 10:start_kernel+0x14c/0x220
> last clier stext+0x7fdff0e8/0xe8 caller stext+0x7fdff0e8/0xe8
> time.c: Lost 5 timer tick(s)! rip 10:__do_softirq+0x5a/0xea
> last clier stext+0x7fdff0e8/0xe8 caller stext+0x7fdff0e8/0xe8
> Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
> time.c: Lost 2 timer tick(s)! rip 10:release_console_sem+0x1a5/0x228
> last clier _spin_lock_irqsave+0x16/0x26 caller release_console_sem+0x1a/0x228
> Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)

I don't know why the messages are mangled - it looks like there's some
problem with serial console (might be x86_64-specific).

But the messages you're seeing are due to some debug code, sorry - they
didn't happen on my test box.  You'll need to change report_lost_ticks
(arch/x86_64/kernel/time.c, line 66) to zero.


  reply	other threads:[~2006-03-30  9:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  8:35 2.6.16-mm2 Andrew Morton
2006-03-28 13:46 ` [PATCH 2.6.16-mm2] Kconfig SND_SEQUENCER_OSS help text fix Frederik Deweerdt
2006-03-28 22:23   ` Lee Revell
2006-03-29  7:36   ` Clemens Ladisch
2006-03-29  9:44     ` Frederik Deweerdt
2006-03-29 18:20       ` Takashi Iwai
2006-03-30  7:36         ` Frederik Deweerdt
2006-03-30  9:21           ` Rene Herman
2006-03-30 11:51             ` Frederik Deweerdt
2006-03-28 15:15 ` 2.6.16-mm2 bert hubert
2006-03-28 15:42 ` 2.6.16-mm2 Christoph Hellwig
2006-03-28 20:53   ` 2.6.16-mm2 Alan Cox
2006-03-28 18:16 ` 2.6.16-mm2 Badari Pulavarty
2006-03-28 19:11   ` 2.6.16-mm2 Andrew Morton
2006-03-28 19:38     ` 2.6.16-mm2 Andi Kleen
2006-03-28 19:59       ` 2.6.16-mm2 Badari Pulavarty
2006-03-28 21:52 ` 2.6.16-mm2 Kumar Gala
2006-03-28 22:05   ` 2.6.16-mm2 Russell King
2006-03-28 22:21     ` 2.6.16-mm2 Kumar Gala
2006-03-30  9:27 ` 2.6.16-mm2 Reuben Farrelly
2006-03-30  9:43   ` Andrew Morton [this message]
2006-03-31 14:56 ` [-mm patch] arch/i386/kernel/apic.c: make modern_apic() static Adrian Bunk
2006-03-31 15:02   ` Andi Kleen
2006-03-31 15:16     ` Adrian Bunk

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=20060330014341.18c53b0b.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reuben-lkml@reub.net \
    /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

Powered by JetHome