It would seem that you have two alternatives:
1) Port the DLKM driver to Linux STREAMS (LiS) -- assuming you have source.
2) Use the LiS LDL driver to interface to an existing Linux network driver.
Alternative #1 could be a good-sized project.
Alternative #2 would be possible if the following conditions hold (at minimum):
a) The DLKM driver is a STREAMS DLPI driver.
b) The panicked Linux kernel is alive enough to run its own network drivers.
c) The panic is not within the kernel's network sub system.
That's about all the light that I can shed on this. If you get it working, let me know since it sounds like a really cool debugging setup. (BTW, I was the one who ported the original KGDB stubs to the Linux kernel via async links. This is now being maintained by Amit Kale.)
-- Dave
At 11:48 PM 8/29/2003 Friday, Saravanan wrote:
Hi,
This is the question related to kwdb. I need some clarrification points from you.
There are two kinds of STREAMS DLKM modules available.
1) DLKM module. ( Dynamically configured into the kernel )
2) DLKM module ( Statically configured into the kernel )
Example,
1) For Dynamically configured module
kmsystem -c y -l y modulename
2) For statically configured module
kmsystem -c y -l n modulename
I am following the kwdb 2.1 guide . It suggests only for DLKM modules ( Dynamically configured modules). I need information for the statically configured modules.
Is it the only available guide for kwdb? Else further documents are available?. Is there a procedure available to debug the DLKM module which is statically configured & linked with the kernel?.
It will be great when you provide some document on STREAMS module debugging (DLKM modules).
Thanks & Regards,
Saravanan
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.410 / Virus Database: 231 - Release Date: 10/31/2002
