Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "wilbur.chan" <wilbur512@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: Problem in booting when calling calibrate_delay
Date: Mon, 2 Nov 2009 23:12:52 +0800	[thread overview]
Message-ID: <e997b7420911020712w74913c8dw86f19ebf04fc7bdc@mail.gmail.com> (raw)
In-Reply-To: <20091101071407.GC4551@linux-mips.org>

2009/11/1 Ralf Baechle <ralf@linux-mips.org>:
> On Thu, Oct 29, 2009 at 07:51:52AM +0800, wilbur.chan wrote:

> When something like this happens it is in most cases caused by timer
> interrupt not working.
>
>  Ralf
>

Today , I found that ,  the code never enter the do_timer function.

As a matter of fact, I'm testing kexec on mips64 smp.   In the end of
the first kernel , I' ve  used local_irq_disable

and jumped directly into second kernel. However it hang at calibrate_delay.

In a normal booting on mips64, I found that , do_timer was invoked
after console_init.

Here is my dump_stack of do_timer, in a successfully booting log:

0:Call Trace:
0:[ <834243cc>]0: dump_stack+0x8/0x34
0:[ <83451ee0>]0: do_timer+0x70/0xa8
0:[ <8342333c>]0: timer_interrupt+0x64/0x160
0:[ <834234b4>]0: ll_timer_interrupt+0x7c/0xd8
0:[ <8341d220>]0: ret_from_irq+0x0/0x4
0:[ <83443a64>]0: release_console_sem+0x1e0/0x328
0:[ <8377cf88>]0: serial8250_console_init+0x1c/0x2c
0:[ <8377ae58>]0: console_init+0x4c/0x6c
0:[ <83762dd8>]0: start_kernel+0x3e0/0x75c


So, I thought that , it might be release_console_sem being failed in
my second kernel of kexec when booting, but I don't know why

      parent reply	other threads:[~2009-11-02 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 23:51 Problem in booting when calling calibrate_delay wilbur.chan
2009-11-01  7:14 ` Ralf Baechle
2009-11-01 15:18   ` wilbur.chan
2009-11-02 15:12   ` wilbur.chan [this message]

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=e997b7420911020712w74913c8dw86f19ebf04fc7bdc@mail.gmail.com \
    --to=wilbur512@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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