public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Guy Martin <gmsoft@tuxicoman.be>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 64bit kernel not booting with CONFIG_PRINTK_TIME=y
Date: Sat, 19 Jul 2008 17:54:59 -0400	[thread overview]
Message-ID: <20080719215459.GA2550@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080717190502.74c238d5@bleh.bxl.tuxicoman.be>

On Thu, Jul 17, 2008 at 07:05:02PM +0200, Guy Martin wrote:
> 
> Recompiling with CONFIG_PRINTK_TIME=n makes it works straight away.
>

The problem is kernel/printk.c around line 731.

t = jiffies * (NSEC_PER_SEC / HZ);
do_div(t, 10000000000); is doing some badness (which is hard as hell to
debug since printk isn't working.)

It's doing some sort of bollocks when jiffies is between 9 and 10...

do_div being:

# define do_div(n,base) ({                                      \
        uint32_t __base = (base);                               \
        uint32_t __rem;                                         \
        __rem = ((uint64_t)(n)) % __base;                       \
        (n) = ((uint64_t)(n)) / __base;                         \
        __rem;                                                  \
 })

I'm *guessing* that umoddi3 or udivdi3 is doing an xmpyu or something,
which since this is probably before fpu init, is trapping, which is
trying to printk, which is recursively exploding.

regards, Kyle

       reply	other threads:[~2008-07-19 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080717190502.74c238d5@bleh.bxl.tuxicoman.be>
2008-07-19 21:54 ` Kyle McMartin [this message]
2008-07-19 23:04   ` 64bit kernel not booting with CONFIG_PRINTK_TIME=y Kyle McMartin
2008-07-20  9:23     ` Guy Martin
2008-07-29  4:29       ` Kyle McMartin
2008-07-29 17:42         ` Guy Martin
2008-07-16 18:45 Guy Martin
2008-07-16 18:56 ` Kyle McMartin
2008-07-17 18:33   ` Kyle McMartin
  -- strict thread matches above, loose matches on Subject: below --
2008-07-16 17:58 Guy Martin

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=20080719215459.GA2550@phobos.i.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=gmsoft@tuxicoman.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    /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