From: Christian Kujau <evil@g-house.de>
To: maneesh@in.ibm.com
Cc: linux-kernel@vger.kernel.org, trond.myklebust@fys.uio.no,
Andrew Morton <akpm@osdl.org>
Subject: Re: probably NFS related Oops during shutdown with 2.6.12-rc3-mm3
Date: Mon, 16 May 2005 14:55:52 +0200 [thread overview]
Message-ID: <42889858.1040009@g-house.de> (raw)
In-Reply-To: <20050516063136.GB13091@in.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Maneesh Soni wrote:
> Could you try configuring kdump and get a crashdump when the system
> crashes(oops). Please refer to Documentation/kdump.txt in -mm kernel tree.
> You might also want to set /proc/sys/kernel/panic_on_oops to 1, so as to
> initiate kernel panic during oops.
i've done so, but..hmm...no panic was triggered, because the Oops is gone.
but it *was* there, i swear ;-)
http://nerdbynature.de/bits/prinz/2.6.12-rc3-mm3/prinz-nc_2.6.12-rc4-mm1.log
(but this time with a tainted kernel)
now i can boot 2.6.12-rc4-mm1 (tainted/not tainted), but the oops does not
show up anymore.
but thanks for the hint, i'll keep that in mind next time [1]
Christian.
[1] when will it be? even the -mm kernel is pretty rock-solid for me.
great job!
- --
BOFH excuse #415:
Maintenance window broken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCiJhY+A7rjkF8z0wRAqJbAJ9zIhAoIGfzLqrNgewmgqR7FafdSQCeOQMM
U6VPMiAOlofUVPl64lf7HdM=
=T0dN
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-05-16 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 0:03 probably NFS related Oops during shutdown with 2.6.12-rc3-mm3 Christian Kujau
2005-05-15 0:26 ` Trond Myklebust
2005-05-15 17:17 ` Christian
[not found] ` <20050516063136.GB13091@in.ibm.com>
2005-05-16 12:55 ` Christian Kujau [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=42889858.1040009@g-house.de \
--to=evil@g-house.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=trond.myklebust@fys.uio.no \
/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