From: Rasmus Andersen <rasmus@jaquet.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: oops in 2.2.17, not in 2.2.14-5
Date: Tue, 14 Nov 2000 16:44:47 +0100 [thread overview]
Message-ID: <20001114164447.A4286@jaquet.dk> (raw)
In-Reply-To: <20001113180449.A652@jaquet.dk> <20001114135924.A3649@jaquet.dk>
In-Reply-To: <20001114135924.A3649@jaquet.dk>; from rasmus@jaquet.dk on Tue, Nov 14, 2000 at 01:59:24PM +0100
>
> OK, I tried with 2.2.16 and 2.2.18pre21 compiled with egcs-2.91.66
> (the kernels reported yesterday were compiled with 2.95.2).
>
> 2.2.16 oopsed faithfully (I could not get hold of the oops as several
> scrolled by and none made it to the log). 2.2.18pre21 does not oops.
> Bzip2 core dumps, but gzip makes it through. So it seems that my
> problem has been solved already and proactively :)
>
Eeek. Apparently I was a bit too early with the champagne... I was
away for an hour or so and when I came back it (2.2.18pre21) had
oopsed with multiple oops (i.e. the first offscreen) and hardlocked.
I'm now running 2.2.14-5 again, doing the exact same stuff and it
seems to hold up... (knock wood).
Barring someine suggestin a better solution I'll try to compile
a kernel with serial console and capture an oops that way.
Regards
Rasmus
-
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/
prev parent reply other threads:[~2000-11-14 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 17:04 oops in 2.2.17, not in 2.2.14-5 Rasmus Andersen
2000-11-14 12:59 ` Rasmus Andersen
2000-11-14 15:44 ` Rasmus Andersen [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=20001114164447.A4286@jaquet.dk \
--to=rasmus@jaquet.dk \
--cc=linux-kernel@vger.kernel.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