Milind,
Thanks for the information. Can you just give more information
regarding why kgdbwait is deprecated? and are there any patches which
can enable it? How much effort will it require to enable it?
As currently I can not use KGDB over serial line, I am trying to
extract maximum out of kgdboe.
Your suggestions will be valuable.
Thanks and regards,
Rupesh.
Milind Dumbare wrote:
>
>
> On Thu, Jun 5, 2008 at 6:07 PM, Rupesh Gujare
> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
>
> Milind,
>
> I was following the discussions, and I have some questions
> for you.
>
> 1) Why we cant give "kgdbwait" as a kernel parameter while using
> "kgdboe"?
>
> As kgdbwait is deprecated.
>
>
> 2) I am trying on ARM board, if I give kgdbwait as kernel
> parameter, and tries to attach remote gdb, kernel crashes.
> While if I dont give kgdbwait, and try to connect remote gdb
> after kernel boots up, it works fine. Can you explain why it is so?
>
> Above point answers this.
>
> and if i wanna debug kernel initialization part how can I do it
> using kgdb?
>
> In this case go for KGDB over serial line, it (kgdbos) has kgdbwait
> supported.
>
>
>
> Thanks in advance,
>
> Regards,
> Rupesh.
>
>
> Milind Dumbare wrote:
>> Well, building kernel is not discussed on this list. Be specific to KGDB
>> questions. Read the kernel's documentation for building kernel.
>>
>> -Miline
>> On Thu, Jun 5, 2008 at 3:45 PM, Bhagwat <[EMAIL PROTECTED]>
>> <mailto:[EMAIL PROTECTED]>
>> wrote:
>>
>>
>>> Hi Milind
>>>
>>>
>>>
>>> I will check with that, but do I need to do any more steps or is it
>>> enough
>>> With reference to your quick start document
>>> http://kgdb.linsyssoft.com/downloads/kgdb-2/kgdbquickstart-2.4.pdf I
>>> have
>>> done make bzImage and copied the kernel to target machine, it is not
>>> booting
>>> up, Do I need to do $ make module then $ make module_install
>>>
>>> Someone suggested me to do $ make modules and make module_install since
>>> kernel is not booting up. Do I need to do this, as it is not mentioned
>>> in
>>> kgdb-quick start docs.
>>>
>>> Thanks
>>>
>>> Bhagwat
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> *From:* Milind Dumbare [mailto:[EMAIL PROTECTED]
>>> *Sent:* Thursday, June 05, 2008 2:58 PM
>>> *To:* Bhagwat Masalkar
>>> *Cc:* KGDB Mailing List
>>> *Subject:* Re: how to chk dmesg on remote machine, as it is not booted
>>> up?
>>>
>>>
>>>
>>> It seems you have given the grub entry in wrong way.
>>> The kgdboe line in your grub should be on Kernel (third)line following
>>> "rhgb quiet" and not on separate line.
>>>
>>> On Thu, Jun 5, 2008 at 2:36 PM, Bhagwat <[EMAIL PROTECTED]>
>>> <mailto:[EMAIL PROTECTED]>
>>> wrote:
>>>
>>> HI Milind
>>>
>>>
>>>
>>> Thanks for your light speed reply,
>>>
>>>
>>>
>>> In my grub entry I did't added "kgdbwait", still it is not booting up,
>>>
>>>
>>>
>>> My grup entry is_
>>>
>>> title Bhagwat Kernel
>>>
>>> root (hd0,5)
>>>
>>> kernel /vmlinuz-2.6.15-kgdb ro root=LABEL=/ rhgb quiet
>>>
>>> initrd /initrd-2.6.15-kgdb.img
>>>
>>> [EMAIL PROTECTED]/eth1 <mailto:[EMAIL PROTECTED]/eth1>
>>> 00:00:E2:78:ED:8D,@*MailScanner warning: numerical links are often
>>> malicious:* 192.168.2.26/ <http://192.168.2.26/>
>>>
>>> console=ttyS0,115200
>>>
>>>
>>>
>>> As target machine *MailScanner warning: numerical links are often
>>> malicious:* 192.168.2.117 <http://192.168.2.117> is mapped to eth1 not to
>>> eth0.
>>>
>>> With reference to your quick start document
>>> http://kgdb.linsyssoft.com/downloads/kgdb-2/kgdbquickstart-2.4.pdf I
>>> have
>>> done make bzImage and copied the kernel to target machine, it is not
>>> booting
>>> up, Do I need to do $ make module then $ make module_install
>>>
>>>
>>>
>>> Thanks
>>>
>>> Bhagwat
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> *From:* Milind Dumbare [mailto:[EMAIL PROTECTED]
>>> *Sent:* Thursday, June 05, 2008 12:27 PM
>>> *To:* Bhagwat Masalkar; KGDB Mailing List
>>> *Subject:* Re: how to chk dmesg on remote machine, as it is not booted
>>> up?
>>>
>>>
>>>
>>> Hi Bhagwat,
>>> In KGDBoE (KGDB over ethernet) we don't add "kgdbwait" on kernel command
>>> line (grub entry) so the kgdb machine should not wait for connection
>>> from
>>> remote gdb while booting and should boot like a normal machine. So when
>>> it
>>> boots up you see the dmesg see if KGDBoE is configured properly and its
>>> up
>>> and running, and then try connecting from remote gdb.
>>>
>>> -Miline
>>>
>>> On Thu, Jun 5, 2008 at 12:15 PM, Bhagwat <[EMAIL PROTECTED]>
>>> <mailto:[EMAIL PROTECTED]>
>>> wrote:
>>>
>>> Hi milind,
>>>
>>>
>>>
>>> I have seen ur response at
>>>
>>> http://www.mail-archive.com/[email protected]/msg00067.html
>>>
>>>
>>>
>>> I am also facing same problem, like
>>>
>>>
>>>
>>> I am trying to setup kgdb with ethernet. I have downloaded *MailScanner
>>> warning: numerical links are often malicious:* 2.6.15.5 <http://2.6.15.5>
>>>
>>>
>>>> kernel and 2.4 kgdb patch for *MailScanner warning: numerical links
>>>> are often malicious:* 2.6.15.5 <http://2.6.15.5> kernel release. I
>>>> successfully
>>>>
>>>> applied the following patches
>>>>
>>>> core-lite.patch
>>>>
>>>> i386-lite.patch
>>>>
>>>> 8250.patch
>>>>
>>>> eth.patch
>>>>
>>>> core.patch
>>>>
>>>> i386.patch
>>>>
>>>> and configured with ethernet support for kgdb with make menuconfig.
>>>>
>>>> then i gave make bzImage command and placed both System.map and
>>>>
>>>> bzImage to the target machine's boot directory. Then I have made an
>>>>
>>>> entry in grub.conf file to be able to boot with newly copied bzImage
>>>>
>>>> and specified parameters as
>>>>
>>>> kgdboe = @*MailScanner warning: numerical links are often malicious:*
>>>> 192.168.0.1/ <http://192.168.0.1/> , @*MailScanner warning: numerical
>>>> links are often malicious:* 192.168.0.2/ <http://192.168.0.2/>
>>>>
>>>> then I have started gdb at development machine by issuing the command
>>>>
>>>> gdb ./vmlinux.
>>>>
>>>> now at gdb prompt, i have given the command target remote
>>>>
>>>> udp:*MailScanner warning: numerical links are often malicious:*
>>>> 192.168.0.2:6443 <http://192.168.0.2:6443>. At this stage, I am getting an
>>>> error that "host
>>>>
>>>> is not reachable and ignoring packet error".
>>>>
>>> I have done target remote udp:*MailScanner warning: numerical links are
>>> often malicious:* 192.168.0.1:6443 <http://192.168.0.1:6443> also, but no
>>> success getting same msg, like host is not reachable ignoring packet error.
>>>
>>>
>>>
>>> Also as you suggested, See "dmesg" output of kgdb machine for more
>>> help. look for "kgdboe"
>>>
>>> messages in it.
>>>
>>> But on KGDB running machine, it is not booted up, and its waiting for
>>> connection from host, how to chk dmesg.
>>>
>>>
>>>
>>> Please share your experience.
>>>
>>>
>>>
>>> Thanks
>>>
>>> Bhagwat
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> The information contained in this email and any attachments is
>>> confidential
>>> and may be subject to copyright or other intellectual property
>>> protection.
>>> If you are not the intended recipient, you are not authorized to use or
>>> disclose this information, and we request that you notify us by reply
>>> mail
>>> or telephone and delete the original message from your mail system.
>>>
>>>
>>>
>>>
>>> --
>>> Milind Dumbare
>>> Sr. Systems Engg.
>>> Linsyssoft Technologies.
>>>
>>>
>>> ------------------------------
>>>
>>> The information contained in this email and any attachments is
>>> confidential
>>> and may be subject to copyright or other intellectual property
>>> protection.
>>> If you are not the intended recipient, you are not authorized to use or
>>> disclose this information, and we request that you notify us by reply
>>> mail
>>> or telephone and delete the original message from your mail system.
>>>
>>>
>>>
>>>
>>> --
>>> Milind Dumbare
>>> Sr. Systems Engg.
>>> Linsyssoft Technologies.
>>>
>>> ------------------------------
>>> The information contained in this email and any attachments is
>>> confidential
>>> and may be subject to copyright or other intellectual property
>>> protection.
>>> If you are not the intended recipient, you are not authorized to use or
>>> disclose this information, and we request that you notify us by reply
>>> mail
>>> or telephone and delete the original message from your mail system.
>>>
>>>
>>
>
>
>
>
> --
> Milind Dumbare
> Sr. Systems Engg.
> Linsyssoft Technologies.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
