From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
Debian PowerPC List <debian-powerpc@lists.debian.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.21-ben2 issues: RTC, Thermal and RTAS
Date: Mon, 19 Jan 2004 10:25:47 +1100 [thread overview]
Message-ID: <1074468347.813.33.camel@gaston> (raw)
In-Reply-To: <Pine.GSO.4.58.0401181310240.2808@waterleaf.sonytel.be>
> To my surprise, genrtc in 2.4.23 does not work on my LongTrail!
> The kernel crashes in init/do_mounts.c:mount_block_root() right after the call
> to sys_chdir(), because current->fs is a NULL pointer. Weird, and it doesn't
> really look genrtc-related, although the same source tree works fine if I
> disable genrtc and build in rtc.
>
> I also tried 2.6.0, and there it works fine, both in the builtin and modular
> case: the kernel got the correct time, and hwclock works.
Debuggin that would be useful... memory corruption caused by genrtc ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-01-18 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030823171845.GA1963@dat.etsit.upm.es>
[not found] ` <20031217011849.GA26643@iliana>
[not found] ` <Pine.GSO.4.58.0312171042530.24864@waterleaf.sonytel.be>
[not found] ` <20031217095241.GD2283@iliana>
[not found] ` <Pine.GSO.4.58.0312171056030.24864@waterleaf.sonytel.be>
[not found] ` <20031217100358.GA2655@iliana>
[not found] ` <Pine.GSO.4.58.0312171112040.24864@waterleaf.sonytel.be>
2004-01-13 15:12 ` 2.4.21-ben2 issues: RTC, Thermal and RTAS Sven Luther
2004-01-13 17:09 ` Geert Uytterhoeven
2004-01-13 17:16 ` Sven Luther
2004-01-18 12:14 ` Geert Uytterhoeven
2004-01-18 12:17 ` Sven Luther
2004-01-18 12:31 ` Geert Uytterhoeven
2004-01-18 23:25 ` Benjamin Herrenschmidt [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=1074468347.813.33.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sven.luther@wanadoo.fr \
/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;
as well as URLs for NNTP newsgroup(s).