|
From: Geert U. <ge...@li...> - 2003-12-15 09:31:35
|
On Sun, 14 Dec 2003, Andreas [ISO-8859-1] W=FCst wrote:
> On Sun, 2003-12-14 at 04:20, Kulwant Bhogal wrote:
> > > If it doesn't work yet, you could also rename the hwclockfirst.sh c=
all,
> > > although it doesn't seem to write to the clock.
> >
> > > # cd etc/rcS.6/
> > > # mv S18hwclockfirst.sh offS18hwclockfirst.sh
> >
> > > But I would heavily advise against it, because then nothing is sett=
ing
> > > the system clock (system clock !=3D hardware clock), which could le=
ad to
> > > strange behaviour of the system.
> >
> > Well, I did try that (because all else before that had failed) and I =
got:
> >
> > Congratulations, You have successfully installed
>
> Yeah, so we've got one step further! :)
>
> > and after the message about how to revisit the setup process (by runn=
ing
> > /usr/sbin/base-config) I got another kernel panic:
> >
> > Loading /etc/console/boottime.kmap.gz
> >
> > kernel access of bad area pc c00dca04 lr c00de9f8 address 70 tsk hwcl=
ock/230
^^
Looks like a NULL-pointer struct dereference.
Do you have a System.map? Can you look up the label (closest before) for
c00dca04 and c00de9f8?
> > task =3D c65dc000[230] 'hwclock'
>
> So you really seem to have a major problem with the hw clock!
>
> Is the contact between the ppc board and the motherboard ok? Where does
> the clock actually reside (motherboard or ppc)? Is it some strange
> non-standard chip?
How does the kernel detect your clock? A2000 or A3000 style?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org
In personal conversations with technical people, I call myself a hacker. =
But
when I'm talking to journalists I just say "programmer" or something like=
that.
-- Linus Torvalds
|