I have a Ubuntu 7.4 system (2.6.20-17.39 kernel). The processor is adual-core T7300 and 4GB memory. The kernel has kdb patched to it.After the device was rebooted, it entered the kdb prompt because ofNULL pointer access in kernel space. So that's good -- it's what Iexpected.

One problem confusing me is the inconsistent stack traces from "bt"command and "dmesg" command. They should be showing the same stacktrace, if I understand them correctly.

Another question is that I do not see the function "shrink_all_memory"was invoked from "filp_close". Could that function "shrink_all_memory"come from kdb?

not quite experienced with kdb on linux... So will appreciate yourfeedback if any.