From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6.24-rc1: au1xxx and clocksource
Date: Thu, 25 Oct 2007 18:59:14 +0100 [thread overview]
Message-ID: <20071025175914.GB27616@linux-mips.org> (raw)
In-Reply-To: <20071024183135.GA23096@roarinelk.homelinux.net>
On Wed, Oct 24, 2007 at 08:31:35PM +0200, Manuel Lauss wrote:
> Hi everyone,
>
> > So time to check how your favorite platform is doing and fix what broke!
>
> I let it loose on my Au1200, but unfortunately the new time code is b0rked
> ina way I don't understand.
>
> Following call chain:
>
> start_kernel()
> time_init()
> init_mips_clocksource()
> mips_clockevent_init()
> clockevents_register_device()
> clockevents_do_notify()
> notifier_call_chain():
>
> It dies here, line 69, in kernel/notifier.c:
> ret = nb->notifier_call(nb, val, v);
What sort of death? Please describe all sympthoms of the patient.
> Maybe my debug method is faulty (homebrew putstring() with au1200 uart
> banging) but the last debug output is before this line.
It is consistent with another bug report on IP27.
The function tick_notify has been installed as notifier, so that is what
I think nb->notifier_call() should be pointing at. So it should be
called like this:
tick_notify(&tick_notifier, CLOCK_EVT_NOTIFY_ADD, dev)
So things are likely going wrong somewhere in there.
Ralf
next prev parent reply other threads:[~2007-10-25 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 18:31 2.6.24-rc1: au1xxx and clocksource Manuel Lauss
2007-10-25 17:59 ` Ralf Baechle [this message]
2007-10-25 18:18 ` Manuel Lauss
2007-10-26 6:18 ` Manuel Lauss
2007-10-26 11:24 ` Manuel Lauss
2007-10-26 11:56 ` Sergei Shtylyov
2007-10-26 12:12 ` Ralf Baechle
2007-10-26 11:57 ` Ralf Baechle
2007-10-26 11:55 ` Ralf Baechle
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=20071025175914.GB27616@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.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