linux-mips
[Top] [All Lists]

Re: 2.6.24-rc1: au1xxx and clocksource

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: 2.6.24-rc1: au1xxx and clocksource
From: Manuel Lauss <mano@roarinelk.homelinux.net>
Date: Thu, 25 Oct 2007 20:18:00 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <20071025175914.GB27616@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20071024183135.GA23096@roarinelk.homelinux.net> <20071025175914.GB27616@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.16 (2007-06-09)
> > > 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.

Well it does nothing. Unfortunately the only JTAG probe we have 
is always in use by the WinCE people so can't be more specific than that.
 
> > 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)

That's a great hint, I'll debug it some more.

Thank you!

        Manuel Lauss

<Prev in Thread] Current Thread [Next in Thread>