From: Andreas Franck <afranck@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Mike Galbraith <mikeg@wen-online.de>
Subject: Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots
Date: Sun, 24 Dec 2000 01:21:44 +0100 [thread overview]
Message-ID: <00122401214400.17931@dg1kfa.ampr.org> (raw)
In-Reply-To: <Pine.Linu.4.10.10012231826350.645-100000@mikeg.weiden.de>
In-Reply-To: <Pine.Linu.4.10.10012231826350.645-100000@mikeg.weiden.de>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
The story continues, citing myself:
> Hmm, would have been nice, but it crashes here with 20001222, nevertheless.
> For which CPU do you have your kernel configured? It might be a CPU
> specific issue, I'll try to compile for Pentium I and 486, now, and report
> my results.
It does not seem CPU specific, breaks for both 486 and Pentium with the same
error.
> It would also be nice to know if this is a gcc issue or a kernel issue - if
> I knew which precise file was responsible for the crash, I could compare
> the assembly output for stable and snapshot GCC. My suspect is
> kernel/sched.c, but this might be wrong, as the story begins on the launch
> of kupdate in fs/buffer.c.
And this is where everything seems to go wrong: When I compile buffer.c with
2.95.2, and link everything together, the kernel magically boots without any
complaints; later on something starts crashing badly, but this might be other
issues that can be investigated later on.
> But now I have almost no clue what really goes wrong
... and now I have a bit more, and the suspection that something broke the
way in which the kernel_thread function (arch/i386/kernel/process.c) wants to
start the kernel threads, here bdflush and kupdate. I don't understand all
issues completely, but something seems to have changed.
Attached are the relevant (?) portions of the assembly output for buffer.c:
kupdate, bdflush and bdflush_init, compiled with 2.95.2 and 2.97,
respectively. Perhaps someone could look over it?
Thanks and happy hacking,
Andreas
--
->>>----------------------- Andreas Franck --------<<<-
---<<<---- Andreas.Franck@post.rwth-aachen.de --->>>---
->>>---- Keep smiling! ----------------------------<<<-
[-- Attachment #2: buffer-2.95.2.S --]
[-- Type: application/x-troff, Size: 4144 bytes --]
[-- Attachment #3: buffer-2.97.S --]
[-- Type: application/x-troff, Size: 4271 bytes --]
next prev parent reply other threads:[~2000-12-24 0:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 11:34 Andreas Franck
2000-12-23 17:33 ` Mike Galbraith
2000-12-23 19:14 ` Andreas Franck
2000-12-24 16:13 ` Mike Galbraith
2000-12-24 0:21 ` Andreas Franck [this message]
2000-12-24 22:49 ` Andreas Franck
2000-12-25 5:09 ` Mike Galbraith
2000-12-25 12:29 ` Andreas Franck
2000-12-25 17:45 ` Mike Galbraith
2000-12-25 16:12 ` Andreas Franck
2000-12-25 18:00 ` Mike Galbraith
2000-12-25 20:40 ` Thorsten Kranzkowski
2000-12-26 7:03 ` Paul Laufer
[not found] <Pine.Linu.4.10.10012271823370.471-100000@mikeg.weiden.de>
[not found] ` <00122801060000.00534@dg1kfa.ampr.org>
2000-12-28 0:26 ` Andreas Franck
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=00122401214400.17931@dg1kfa.ampr.org \
--to=afranck@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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
all inboxes | Powered by JetHome®