From: Kaoru Fukui <k_fukui@highway.ne.jp>
To: Kaoru Fukui <k_fukui@highway.ne.jp>, <Jean-Jacques.Levy@inria.fr>,
<benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: __divdi3 unresolved + X pointer blocks
Date: Wed, 11 Jul 2001 01:41:36 +0900 [thread overview]
Message-ID: <20010711014136.Postino-029152@smtp01.highway.ne.jp> (raw)
In-Reply-To: <20010711010133.Postino-018213@smtp01.highway.ne.jp>
> From: Jean-Jacques Levy <Jean-Jacques.Levy@inria.fr>
> To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Subject: Re: __divdi3 unresolved + X pointer blocks
> 2.4.6-pre6. It didn't boot. Open Firmware answer (called
> by yaboot): DEFAULT CATCH! code = 300 %SRR0 01016cf8 $SRR! 00003030
> I cannot decipher OF msgs.
Hi! Ben and JJ.
I also got same problem at kernel-2.4.7.pre boot which kernel be compiled
with gcc-3.0.1cvs,
But I tried kenel compilation continusly with kernel-2.2.19
when it needed the patch.
So I could take bootable kernel-2.2.19 which using gcc-3.0.1cvs.
Please look my dmesg
I think boot problem which is in the kernel-2.4.x's source.
Please look the problem in kernel-2.4.x.
My using gcc-3.0.1 here is
ftp://ftp.linuxppc.org/users/kfukui/glibc-2.2.x-room/RPMS/
Thanks
Kaoru
------ dmesg ----------------
device tree used 41060 bytes
Total memory = 256MB; using 1024kB for hash table (at c0400000)
Linux version 2.2.19-0a (root@g4mpKFUKUI) (gcc version 3.0.1 20010707 (prerelease))
#1 Wed Jul 11 00:39:55 JST 2001
PMU driver initialized for Core99
xmon uses screen and keyboard
PCI bus 0 controlled by pci at f0000000
PCI buses 0..1 controlled by pci at f2000000
PCI bus 0 controlled by pci at f4000000
Uni-N revision: 8, KeyLargo revision: 3
------- the patch to kernel-2.2.19 --------
diff -urN base/kernel/sched.c fixed/kernel/sched.c
--- base/kernel/sched.c Tue Jun 26 07:12:15 2001
+++ fixed/kernel/sched.c Wed Jul 11 00:29:08 2001
@@ -49,7 +49,7 @@
long tick = (1000000 + HZ/2) / HZ; /* timer interrupt period */
/* The current time */
-volatile struct timeval xtime __attribute__ ((aligned (16)));
+struct timeval xtime __attribute__ ((aligned (16)));
/* Don't completely fail for HZ > 500. */
int tickadj = 500/HZ ? : 1; /* microsecs */
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-07-10 16:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010711010133.Postino-018213@smtp01.highway.ne.jp>
2001-07-10 16:41 ` Kaoru Fukui [this message]
2001-07-02 20:31 __divdi3 unresolved + X pointer blocks Jean-Jacques Levy
2001-07-02 14:51 ` Kaoru Fukui
2001-07-05 1:06 ` Jean-Jacques Levy
2001-07-04 20:05 ` Benjamin Herrenschmidt
2001-07-08 22:34 ` Jean-Jacques Levy
2001-07-04 22:22 ` David Edelsohn
2001-07-04 22:24 ` Kaoru Fukui
2001-07-04 22:45 ` Kaoru Fukui
2001-07-04 23:18 ` David Edelsohn
2001-07-05 8:13 ` Geert Uytterhoeven
2001-07-05 8:44 ` Kaoru Fukui
2001-07-05 11:48 ` Holger Bettag
2001-07-05 15:29 ` David Edelsohn
2001-07-05 16:55 ` Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 14:55 Kaoru Fukui
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=20010711014136.Postino-029152@smtp01.highway.ne.jp \
--to=k_fukui@highway.ne.jp \
--cc=Jean-Jacques.Levy@inria.fr \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).