mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Franck <afranck@gmx.de>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots
Date: Sat, 23 Dec 2000 20:14:49 +0100	[thread overview]
Message-ID: <00122320144900.00517@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>

Hi Mike, hello linux-kernel audience,

> I had the same, with the last few snapshots I tried, but 20001218 seems
> to work ok.
> dmesg|head -1
> Linux version 2.4.0-test13ikd (root@el-kaboom) (gcc version gcc-2.97
> 20001218 (experimental)) #18 Sat Dec 23 17:43:29 CET 2000

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 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.

But now I have almost no clue what really goes wrong.

Geetings and a nice christmas to everybody!
Andreas

-- 
->>>----------------------- Andreas Franck --------<<<-
---<<<---- Andreas.Franck@post.rwth-aachen.de --->>>---
->>>---- Keep smiling! ----------------------------<<<-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-23 19:41 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 [this message]
2000-12-24 16:13     ` Mike Galbraith
2000-12-24  0:21   ` Andreas Franck
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=00122320144900.00517@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®