On Wed, 4 Dec 2002 16:02:42 -0800 , "Raj, Ashok" <[EMAIL PROTECTED]> wrote: >Kernel 2.4.20 > >I applied the 2.4.19 patches (didn't see one for 2.4.20 in the downloads >area), only 2 files had minor issues, that were fixed by hand.
Which kdb patches? You have to be more specific. ftp://oss.sgi.com/projects/kdb/download contains lots of patches against various versions of 2.4.19. How am I supposed to guess which patches you applied? v2.1/kdb-v2.1-2.4.19-pre6-common-1.bz2 v2.3/kdb-v2.3-2.4.19-common-4.bz2 v2.4/kdb-v2.4-2.4.19-common-3.bz2 v2.1/kdb-v2.1-2.4.19-pre6-i386-1.bz2 v2.3/kdb-v2.3-2.4.19-i386-1.bz2 v2.4/kdb-v2.4-2.4.19-i386-1.bz2 v2.1/kdb-v2.1-2.4.19-pre6-sparc64-1.bz2 v2.3/kdb-v2.3-2.4.19-i386-2.bz2 v2.3/kdb-v2.3-2.4.19-i386-3.bz2 v2.4/kdb-v2.4-2.4.19-i386-2.bz2 v2.2/kdb-v2.2-2.4.19-rc1-common-1.bz2 v2.3/kdb-v2.3-2.4.19-i386-4.bz2 v2.4/kdb-v2.4-2.4.19-ia64-020821-1.bz2 v2.2/kdb-v2.2-2.4.19-rc1-i386-1.bz2 v2.3/kdb-v2.3-2.4.19-i386-5.bz2 v2.5/kdb-v2.5-2.4.19-common-1.bz2 v2.3/kdb-v2.3-2.4.19-common-1.bz2 v2.3/kdb-v2.3-2.4.19-ia64-020821-1.bz2 v2.5/kdb-v2.5-2.4.19-i386-1.bz2 v2.3/kdb-v2.3-2.4.19-common-2.bz2 v2.4/kdb-v2.4-2.4.19-common-1.bz2 v2.5/kdb-v2.5-2.4.19-ia64-020821-1.bz2 v2.3/kdb-v2.3-2.4.19-common-3.bz2 v2.4/kdb-v2.4-2.4.19-common-2.bz2 BTW, there are 2.4.20 patches v2.5/kdb-v2.5-2.4.20-common-1.bz2 v2.5/kdb-v2.5-2.4.20-rc1-common-1.bz2 v2.5/kdb-v2.5-2.4.20-i386-1.bz2 v2.5/kdb-v2.5-2.4.20-rc1-i386-1.bz2 >After I load my kernel module, I set a breakpoint in a kernel function, say > >Kdb> bp printk > >It shows me that the breakpoint#0 is set. > >Then I type > >Kdb> go > >When the driver or any kernel function calls printk, I notice the debugger >prompt. I can look at back trace etc at this time. Then I do "go" again, on >any future printk's I don't see the debugger break into and giving me a kdb >prompt. Works for me on 2.4.20 with kdb-v2.5-2.4.20-common-1 and kdb-v2.5-2.4.20-i386-1 applied. bp sys_query_module Instruction(i) BP #0 at 0xc011c630 (sys_query_module) is enabled globally adjust 1 [0]kdb> go [root@icy root]# lsmod Module Instruction(i) breakpoint #0 at 0xc011c630 (adjusted) Entering kdb (current=0xc5aa8000, pid 7468) on processor 1 due to Breakpoint @ 0xc011c630 [1]kdb> go Instruction(i) breakpoint #0 at 0xc011c630 (adjusted) 0xc011c630 sys_query_module: int3 Entering kdb (current=0xc5aa8000, pid 7468) on processor 1 due to Breakpoint @ 0xc011c630 [1]kdb> go Instruction(i) breakpoint #0 at 0xc011c630 (adjusted) 0xc011c630 sys_query_module: int3 etc.
