From: amruth <amruth_pv@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@suse.de, Will Newton <will.newton@imgtec.com>,
linux-usb@vger.kernel.org, leoli@freescale.com,
Will Newton <will.newton@gmail.com>
Subject: KGDB kernel panic no init found in linux 2.6.26 after booting KGDB enabled
Date: Wed, 13 Aug 2008 22:35:24 -0700 (PDT) [thread overview]
Message-ID: <263918.13912.qm@web45216.mail.sp1.yahoo.com> (raw)
In-Reply-To: <1218551957-17091-12-git-send-email-will.newton@imgtec.com>
Hi
All
I am configuring linux 2.6.26 kernel in laptop and transferring image to desktop.
My desktop is IDE drive. I am getting kernel panic try init= option error after booting the kernel.
I am trying to setup KGDB on linux 2.6.26 kernel between dev machine and test machine. I have issues and it is not working.
I can get the kgdb to communicate but I cannot start init images to start. I am using Redhat grub configuration.
Do we need apply any patch for 2.6.26 kernel. I am using 2.4.15.5-kgdb patch. I can get communication to work after applying patches.
The system gets into kernel panic after the connection is made because of corrupted initram image.
Can anybody please give me sample grub entry so that I can try.
Should we use init-2.6-kgdb.img or not. If yes how to create it, what about modules in /lib/modules/2.6.../
Can you please let me know how to fix this issue.
After KGDB is enabled the kernel gets into panic mode otherwise it works fine.Can anybody please let me know why KGDB crashes the system.
Thanks
Amruth p.v
next prev parent reply other threads:[~2008-08-14 5:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 14:39 [PATCH 00/11] fsl_usb2_udc: A number of bug fixes and cleanups Will Newton
2008-08-12 14:39 ` [PATCH 01/11] fsl_usb2_udc: Make dr_ep_setup function static Will Newton
2008-08-12 14:39 ` [PATCH 02/11] fsl_usb2_udc: Remove check for udc == NULL in dr_controller_setup Will Newton
2008-08-12 14:39 ` [PATCH 03/11] fsl_usb2_udc: Fix some sparse warnings and remove redundant code Will Newton
2008-08-12 14:39 ` [PATCH 04/11] fsl_usb2_udc: Clean up whitespace in errors and warnings Will Newton
2008-08-12 14:39 ` [PATCH 05/11] fsl_usb2_udc: Clean up whitespace in /proc debugging output Will Newton
2008-08-12 14:39 ` [PATCH 06/11] fsl_usb2_udc: Initialize spinlock earlier Will Newton
2008-08-12 14:39 ` [PATCH 07/11] fsl_usb2_udc: Rename the arguments of the fsl_writel macro Will Newton
2008-08-12 14:39 ` [PATCH 08/11] fsl_usb2_udc: Uninline udc_reset_ep_queue Will Newton
2008-08-12 14:39 ` [PATCH 09/11] fsl_usb2_udc: Make fsl_queue_td return type void Will Newton
2008-08-12 14:39 ` [PATCH 10/11] fsl_usb2_udc: Add a wmb before priming endpoint Will Newton
2008-08-12 14:39 ` [PATCH 11/11] fsl_usb2_udc: Fix oops on probe failure Will Newton
2008-08-14 5:35 ` amruth [this message]
2008-08-14 5:35 ` KGDB kernel panic no init found in linux 2.6.26 after booting KGDB enabled amruth
2008-08-20 20:41 ` [PATCH 05/11] fsl_usb2_udc: Clean up whitespace in /proc debugging output Greg KH
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=263918.13912.qm@web45216.mail.sp1.yahoo.com \
--to=amruth_pv@yahoo.com \
--cc=gregkh@suse.de \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=will.newton@gmail.com \
--cc=will.newton@imgtec.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 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®