[patch] Fix some problem between kdb and kdump
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Takenori Nagano (on Fri, 01 Jun 2007 10:49:21 +0900) wrote: >Hi Keith, > >I agree with your opinion. >But we can't choose LKCD after 2.6.18. > >LKCD maintainer Troy said >> On 04/25/07 19:23, S=C3=A9bastien CRAMATTE wrote: >>> > how can I use lkcd with kernel >=3D 2.6.18 >>=20 >> The general suggestion is to use KDUMP which is already included in >> stock kernel >=3D 2.6.18. See Documentation/kdump/kdump.txt in your >> kernel source tree for more information about kdump. >>=20 >> Troy > >Kdump has many problems, but we can't choose other choices after 2.6.18. >IMHO, we have to modify kdb that we can use both kdb and kdump after 2.6.= >18. > >Keith, do you have any idea to resolve this? kexec developers should provide a simple kexec_dump() routine that anybody can call. All the complexity that is in your patch to KDB has to be replicated and maintained for every debugger that wants to cause a dump. This is wrong, the code should be in one place and maintained by the kexec people. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.