From: Ankita Garg <ankita@in.ibm.com>
To: kexec@lists.infradead.org
Cc: Darren Hart <dvhltc@us.ibm.com>,
Sripathi Kodi <sripathik@in.ibm.com>,
Chirag Jog <chirag@linux.vnet.ibm.com>,
"Sachin P. Sant" <sachinp@in.ibm.com>,
Maneesh Soni <maneesh@in.ibm.com>,
Dinakar Guniguntala <dino@in.ibm.com>
Subject: RT-based kdump kernel hangs on multiple hardware
Date: Wed, 30 Jul 2008 17:30:26 +0530 [thread overview]
Message-ID: <20080730120026.GA30011@in.ibm.com> (raw)
Hi,
We have been facing a number of kdump issues on quite a few of our
hardware. These are with RT kernel as the kdump kernel. Inorder to keep
discussion about each hardware separate, sending separate mails for each
as part of the same thread.
Pl let me know if I need to provide more information. Any ideas on what
could be going wrong or how it can be fixed?
--
Regards,
Ankita Garg (ankita@in.ibm.com)
Linux Technology Center
IBM India Systems & Technology Labs,
Bangalore, India
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2008-07-30 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 12:00 Ankita Garg [this message]
2008-07-30 12:01 ` kdump kernel hangs on 4-way Opteron Blade Ankita Garg
2008-07-30 12:15 ` kdump kernel hangs on 2-way AMD Opteron Intellistation Ankita Garg
2008-07-30 12:32 ` kdump kernel hangs on 4-way AMD Opteron rack mounted box Ankita Garg
2008-07-31 13:46 ` kdump kernel hangs on 2-way AMD Opteron Intellistation Vivek Goyal
2008-07-31 13:46 ` Vivek Goyal
2008-08-01 6:46 ` Ankita Garg
2008-08-01 6:46 ` Ankita Garg
2008-08-01 12:13 ` Ankita Garg
2008-08-01 12:13 ` Ankita Garg
2008-07-31 13:41 ` kdump kernel hangs on 4-way Opteron Blade Vivek Goyal
2008-07-31 13:48 ` Vivek Goyal
2008-07-31 13:48 ` Vivek Goyal
2008-08-04 4:39 ` Ankita Garg
2008-08-04 4:39 ` Ankita Garg
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=20080730120026.GA30011@in.ibm.com \
--to=ankita@in.ibm.com \
--cc=chirag@linux.vnet.ibm.com \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=maneesh@in.ibm.com \
--cc=sachinp@in.ibm.com \
--cc=sripathik@in.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.