I am trying to debug a kernel module (thinkpad_acpi in this case). I know that because it is in the kernel I cannot just hook up a debugger or anything without UML or a second machine kind-of-thing which will probably take too much time for me at the moment.
I tried recompiling the kernel with the THINKPAD_ACPI_DEBUG=y and was expecting that to turn on a load of prink's that I would see in my debug log or syslog Running this new debug-enabled kernel and module has not produced anything extra in my logs - Do I need to set a global flag somewhere for the kernel config to enable extra debug messages? Or is there normally some magic flag I have to set when loading the module to make it happen. (As background information I am trying to work out why the CPU scaling on my T43p forces the slowest scaling when on battery power - I was hoping the thinkpad_acpi module might alert me to some internal values as the system is running that might tell me why the kernel has decided that the only sensible speed is 800mhz whenever on battery - perhaps cpu temperature or similar) Anton -- Anton Piatek email: an...@piatek.co.uk blog/photos: http://www.strangeparty.com pgp: [0xB307BAEF] (http://www.strangeparty.com/anton.asc) fingerprint: 116A 5F01 1E5F 1ADE 78C6 EDB3 B9B6 E622 B307 BAEF No trees were destroyed in the sending of this message, however, a significant number of electrons were terribly inconvenienced. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
