If you find that Powertweak misbehaves, you can register a bug report by
sending as much information as possible to the developers. The list below
contains some of the information which could prove to be beneficial in
tracking down your problem. You should try to include as much of it as
possible, although some points may not be relevant (#8 for example)

1. The file /var/log/powertweak/powertweak.log contains messages from each of
   the powertweak subsystems which can show where things are going wrong.
   It also logs warning messages.

2. The output of 'lspci -xxx'
   This shows the configuration space area of the PCI devices in your system.
   Send outputs of this command before and after Powertweak runs.

3. A brief note explaining the hardware in your system. (CPU, RAM, Motherboard
   chipset, PCI cards, etc.)

4. Mention the version of Powertweak you were trying to run.

5. Run the command 'strace -o pt.strace ./powertweak', and sending the
   pt.strace output to the developers.

6. Mention the output of gcc -v

7. Mention the version of libc and the kernel you are using.

8. If powertweak generated a core file, send it, and the powertweak executable.

9. If you are having problems compiling Powertweak, mention exactly what
   you did to try to build it, and the last few lines of compiler output.

Note, some of the files requested above can be quite large.
It will be appreciated if you can copy all these files to a directory
(for example debug), and then run these commands:

    tar -c debug >debug.tar
    bzip2 -9 debug.tar

Next, instead of flooding a large binary file to the mailing list, and filling
peoples mailboxes, it is preferred if you can put this in webspace or on an ftp
server somewhere, and send a note to the list telling where the file is.
Of course if you don't have the means to do this, then sending directly to the
developer/mailing list directly as a last resort is no problem.
