[Solved] Debugging in QtCreator in "c++" & "qml" modes simultaneously

Sorry for my English.
It seems that last upgrade breaks my QtCreator or gdb.
When I try to launch my program under QtCreator in debug mode the program starts but I doesn't see GUI.
"ps aux" tells that program was started.
QtCreator writes next output:
Could not load shared library symbols for linux-gate.so.1. Do you need "set solib-search-path" or "set sysroot".
But this message was also before upgrading and all was fine.
Important note: if debug option is "c++" or "qml" (on Project page) then program starts fine and I can debug,
but if both options are set simultaneously then I can't see GUI of the program and any breakpoint leads to hanging of the debugger.
Help me, I need both debugger options "c++" and "qml" simultaneously!
Last edited by yerdnas (2014-06-06 11:09:08)

I have the same issue. Perhaps we should file a bug report?
Thanks for the disable qml debugging tip, I'll at least be able to get some work done now.

Similar Messages

Router NME IPS - use promiscuous and inline mode simultaneous

Hi all,
we are using the IPS module NME-IPS-K9 on a Cisco 2951 router. We like to use the IPS in promiscuous and inline mode simultaneous. For example traffic from a client to a server should pass through the IPS. But the IPS should only recieve a copy of the VoIP traffic.
In the interface configuration mode the following command is set.
     ids-service-module monitoring promiscuous access-list 101
If I try to set a interface to inline mode I get the following message:
     "Only either Inline or Promiscuous
     monitoring is supported on the router at one time.
     Please remove Promiscuous monitoring on all interfaces
     before configuring Inline monitoring. Only either Inline or Promiscuous
     monitoring is supported on the router at one time.
     Please remove Promiscuous monitoring on all interfaces
     before configuring Inline monitoring."
Is there any way to use promiscuous and inline monitoring at the same time? Is there a firmware update available which includes this feature? Any other idears?
IOS version of the router: 15.0(1)M4
IPS version: 7.0(2)E4
Kind Regards

In promiscuous mode your sensor doesn't affect the traffic but it only listen and analyze it.
In inline mode you direct all your traffic on this network segment you want to protect to IPS and it analyze it and block some actions according to your settings.
It is the main difference. Which mode to prefer must be your decision.

Jdeveloper 10.1.3 open a page in design and source mode simultaneously

I want to open a page editor in design and source mode simultaneously on the same file.
Kind of stupid question, but I could not find the answer in the help..

OK ignore this message.
For those who want to know - it is simple - right click on the tab with a a page name and select "Split Document" - I knew it was easy :)

[SOLVED] Having trouble dual booting Windows: normal.mod not found

Hello every one, I'm a Gentoo user who wants to try something different. So I thought I'd install Arch on my new laptop.
Anyhow, this is my first proper UEFI install on real hardware. So I might be doing something stupid here, but I've searched all over the forums and the internet and can't seem to find anything similar about it. So please excuse me if there is already a similar or very similar topic
Since I'm new to Arch I followed the Beginner's guide. Everything went fine, install was very quick compared to Gentoo phew... anyhow there came the tricky part, the bootloader install, as I am a real total noob with EFI. I followed the instructions carefully.
The result is: I now have 4 entries in my GRUB menu, 2 are Arch and its fallback, one is Windows 8 detected by osprober, and one is my custom Windows 8 with the usual chain loading setup that i've always used (with some fixes found on the 'net). Arch boots fine, but Windows doesn't; I get booted down to the recovery console, with an error that GRUB cannot find /boot/grub/x86_64-efi/normal.mod. Even though the file is of course existing. I tried to "insmod part_gpt" and others, and it couldn't find any of them, except part_msdos. Yeah I know, it's weird. Unfortunately I need to use Windows sometimes for some programs like Guitar Rig which need a good native audio connection.
My opinion is that there must be some place where the paths are not correct. But I keep looking at the config files and I can't find anything wrong with them...
The system had a Linux Mint 14 install on it previously but it bricked itself while updating to Mint 15. And I only really had Mint on there because of the automatic bootloader setup. Which worked well up to when I got rid of Mint (it was on /dev/sda8, where Arch is now). I hope it doesn't complicate the matter.
My EFI system partition is /dev/sda2. There are so many partitions because it's a Samsung laptop and there's a partition for samsung recovery, one for windows 8 recovery, and so on... The only "real" partitions are /dev/sda2 for EFI, /dev/sda4 for Windows, and /dev/sda8 for Arch.
Here are some command outputs to show you what my system is like. I hope they are helpful. If there's anything missing I shall supplement it of course!
Thanks in advance
sudo efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0001,0006,0003,0000
Boot0000* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* linuxmint HD(2,fa000,96000,f718c38a-c1d8-4c72-9b59-e098594840a2)File(\EFI\linuxmint\grubx64.efi)
Boot0002* arch_grub HD(2,fa000,96000,f718c38a-c1d8-4c72-9b59-e098594840a2)File(\EFI\arch_grub\grubx64.efi)
Boot0003* Windows Boot Manager HD(2,fa000,96000,f718c38a-c1d8-4c72-9b59-e098594840a2)File(\EFI\Microsoft\Boot\bootmgfw.efi)
Boot0006* Windows Boot Manager HD(6,3a186001,200000,d41549d3-0b93-40ef-4173-636c65706975)File(\EFI\Microsoft\Boot\bootmgfw.efi)
mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=2997764k,nr_inodes=749441,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda8 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/sda2 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
[james@James-Laptop ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 499M 0 part
├─sda2 8:2 0 300M 0 part /boot
├─sda3 8:3 0 128M 0 part
├─sda4 8:4 0 342.4G 0 part
├─sda5 8:5 0 23.8G 0 part
├─sda6 8:6 0 1G 0 part
├─sda7 8:7 0 977K 0 part
├─sda8 8:8 0 91.8G 0 part /
└─sda9 8:9 0 5.9G 0 part [SWAP]
[james@James-Laptop ~]$ cat /boot/grub/grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt8 --hint-efi=hd0,gpt8 --hint-baremetal=ahci0,gpt8 7e2ee467-3fd3-41b3-8c1f-62cc45f2d098
else
search --no-floppy --fs-uuid --set=root 7e2ee467-3fd3-41b3-8c1f-62cc45f2d098
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_GB
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-7e2ee467-3fd3-41b3-8c1f-62cc45f2d098' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
else
search --no-floppy --fs-uuid --set=root ECB7-2436
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=7e2ee467-3fd3-41b3-8c1f-62cc45f2d098 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-7e2ee467-3fd3-41b3-8c1f-62cc45f2d098' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
else
search --no-floppy --fs-uuid --set=root ECB7-2436
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=7e2ee467-3fd3-41b3-8c1f-62cc45f2d098 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-ECB7-2436' {
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
else
search --no-floppy --fs-uuid --set=root ECB7-2436
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Windows 8" {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ECB7-2436
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Last edited by jabonz2048 (2013-09-19 15:07:34)

Hello cfr,
Thanks for your reply!
Yes, I had /dev/sda2, my EFI partition, mounted at /boot when I did grub-install and grub-mkconfig. I also had the efivars filesystem unmounted, and ran rmmod plus modprobe on efivars as written.
umount /sys/firmware/efi/efivars
# modprobe -r efivars
# modprobe efivars
My command was exactly the same as the beginner's guide, and it was
grub-install --efi-directory=/boot --bootloader-id=arch_grub --recheck
Now looking at that command, I am wondering, should it have been "--efi-directory=/boot/EFI" or something similar like that? But the fact that Arch boots and runs fine kind of shows the bootloader did indeed install correctly... Or partially at least.
Maybe an ls -l of some of my /boot directories might be useful. Thanks!
ls -l /boot
total 16352
drwxr-xr-x 39 root root 4096 Nov 17 2012 Boot
-r-xr-xr-x 1 root root 398156 Jul 25 2012 bootmgr
-rwxr-xr-x 1 root root 1 Jun 2 2012 BOOTNXT
drwxr-xr-x 6 root root 4096 Aug 26 15:28 EFI
drwxr-xr-x 6 root root 4096 Aug 26 17:39 grub
-rwxr-xr-x 1 root root 10351180 Aug 26 14:19 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root 2185900 Aug 26 14:18 initramfs-linux.img
-rwxr-xr-x 1 root root 3782368 Aug 21 11:53 vmlinuz-linux
[james@James-Laptop teamviewer]$ ls -l /boot/EFI
total 16
drwxr-xr-x 2 root root 4096 Aug 26 15:28 arch_grub
drwxr-xr-x 2 root root 4096 May 22 20:53 Boot
drwxr-xr-x 2 root root 4096 May 22 20:53 linuxmint
drwxr-xr-x 3 root root 4096 Nov 17 2012 Microsoft
[james@James-Laptop teamviewer]$ ls -l /boot/grub/
total 48
drwxr-xr-x 2 root root 4096 Aug 26 15:28 fonts
-rwxr-xr-x 1 root root 4767 Aug 26 17:39 grub.cfg
-rwxr-xr-x 1 root root 4063 Aug 26 14:22 grub.cfg.example
-rwxr-xr-x 1 root root 1024 Aug 26 15:28 grubenv
drwxr-xr-x 2 root root 4096 Aug 26 15:28 locale
drwxr-xr-x 3 root root 4096 Aug 26 15:28 themes
drwxr-xr-x 2 root root 20480 Aug 26 15:28 x86_64-efi

Cannot Debug SSIS packages in 64 bit mode.

Hi,
To anyone who may be able to help. We are using SQL server 2014 Enterprise addition. Visual studio 2013, SSDT latest version installed, all 64 bit tools installed. I have tried to run my packages with the "Run64bitRuntime"
set to true ( project properties-->Debugging-->Run64BitRuntime = True). Initially I thought it an issues with my package (we migrated them from SSIS 2008R2, they run fine with no issues within the 32 bit memory constraints) so I created
a super simple package with VS 2013 in the SSIS 2014 environment from scratch, a lookup and an OLEDB Data source that's it. Same problem. No matter what I do when I debug in SSIS the 32 bit process (DtsDebugHost.exe (32 bit)) fires up,
even though I have selected debug in 64 bit runtime I cannot get the 64 bit version of DtsDebugHost to run. This is an issue because I am debugging projects that will utilise more than 4GB of memory for say a particular set of lookups. Curiously
when I schedule the projects to run in the scheduler, it fires up a 64 bit process, and the package executes successfully, however if I can't debug in 64 bit mode and leverage the extra memory at the design stage,
this is useless. I have checked obvious things like the path environment variable, thinking perhaps SSIS debug doesn't know where the 64 bit exe is, but it is all fine paths are as they should be. All 64 bit tools/dll's are installed. I
have tested this directly on the server, and on the client machine that I use and the issue is the same. If no one can help me here I guess I can log a support ticket.
thanks in advance.

Hi des_77,
According to your description, you can only debug your SSIS package in 32 bit mode.
Based on my research, I think the issue is caused by 64bit SSIS runtime is not installed on your machine. We can verify the issue by seeing if DtsDebugHost.exe under <Installation Drive>\Program Files\Microsoft SQL Server\120\DTS\Binn or not.
To fix this issue, please install SQL Server and select Integration Services for installation, Setup installs all available 64-bit Integration Services features and tools. Then we can set the Debug Options property Run64BitRuntime to “True”, view the processes
in Windows Task Manager to verify the version of DTDebugHost.exe when debugging the package.
Besides, if the issue still existed, it is my pleasure to help you to reflect your recommendation to the proper department for their consideration. Please feel free to submit your situation on our product to the following link
https://connect.microsoft.com/SQLServer/. Your feedback is valuable for us to improve our products and increase the level of service provided.
References:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2014/05/22/ssis-packages-executed-from-visual-studio-business-intelligence-development-studio-bids-design-time-on-a-64bit-development-server-goes-to-unresponsive-state-during-package-execution.aspx
http://dougbert.com/blog/post/64-bit-considerations-for-sql-server-integration-services-final.aspx
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

[Solved] Problem with LOV and 'enter query' mode

Hi all,
I'm kind of new to Forms and I'm having some problems that I'm not being able to resolve. I already search it on the net, but nothing relevant came up. If anyone could help me I appreciated it.
In my form I have some fields, and in one of them I have a LOV, and almost everything works fine. I inserted data, changed it, deleted it and all it's ok.
But when I change to 'enter query' mode, when I try to search for data on the LOV field it ignores what I write.
That is, for it, it's the same if I make F11 -> write 'aaaa' -> ctrl + F11 or if I make F11 -> '%' -> ctrl + F11.
It behaves the same way, shows me all the records.
Probably I'm missing something basic, but I'm not getting it...
Thanks,
Ana

when you create a lov by wizard the lov and record group have always the same name..
the problem is that the item is NOT based in the tabe.
what kind of query do you execute if you choose something from a love which is not based on the db?
i mean, this item has no influence on the query of the table, so whatever you choose it's like a "select * from table"
i hope i was clear

How to solve NX7009 vPC member port in suspend mode?

I'm deploying a pair of new NX7009 (Sup2, F2 series 48-port 10G modules) and bunch of NX5548 (with expansion module). Connectivity between pair of NX7009 and pair of NX5548 is straight forward: 4 meshed 10G connections in between in vPC. vPC domains and all vPC port-channels are fine except one vPC port-channel between NX7009 pair and one NX5548 pair. One of the NX7009 port in the bundle is put in suspend mode every time it's enabled. The port is configured the same as any other bundled NX7009 ports and the NX5548 port on the other side of the port-channel is also configured the same as any other vPC ports.
Ports can be suspended if incompatibility exists in a port-channel. But in this case, I couldn't find any incompability about this particular NX7009 port.
Any advices? Thanks a lot

Thanks for the reply. vPC is double sided. The ports that were suspended was not physically cabled on one side. After physical connectivity came up, the ports were fine from that point on.
So it was not caused by any LACP misconfiguration. That's good to learn.
Thanks again.

[SOLVED] Recent package update borks DWM tile mode modkey switching...

...and the menu bar changed from red to blue!
[2014-07-06 17:58] [PACMAN] upgraded dwm (6.0-1 -> 6.0-2)
After my last update DWM's menu color change right away, but didn't notice some features had stopped working with key commands, because I don't use them all the time.
Alt+Shift+Return works to spawn new window, but some broken features include,
Alt+[c, t, f, w, m, e] do not work to switch tile modes (but Alt+p works to open dmenu, and Alt+[1,2,3,4,5,6,7,8,9] still works to change to different view.)
Alt+[h,j,k,l] do not work to resize the master window tile
Looking at the date in the last line of the previous update shows a keyboard update. I don't have need to customize the system's keyboard mappings, so I don't know whether this is relevant to the issue.
[2014-06-15 10:17] [PACMAN] upgraded xkeyboard-config (2.11-2 -> 2.12-1)
I'm not sure where to begin troubleshooting...rebuild the DWM package? or, change the modkey? or, troubleshoot keymappings?
Here is the pacman.log file for my last two updates, 6-16 and 7-6
[2014-06-15 10:08] [PACMAN] Running 'pacman -Syu emacs'
// UPDATE. I've removed the pacman.log output because searching for a completely different issue, I found my own post!! These blanket log outputs really don't serve any purpose after the question has been answered. There should be an expiration date.
Last edited by xtian (2014-09-21 19:57:45)

You can put your customized packages in IgnorePkg.
https://wiki.archlinux.org/index.php/Dwm#Configuring

[Solved]SSD x25-m not in DMA mode, kernel issue?

Is DMA mode enabled in the kernel? (For HDD)
Last edited by sveinemann (2010-03-28 19:08:31)

It is, I checked with hdparam -i /dev/sda and it told me that udma6 is enabled.

Laptop-mode-tools/cpufrequtils Questions [SOLVED]

I am running a Sony Vaio VGN-FW480J and am trying to optimize these two tools to save battery life and hard drive life span. I have added @laptop-mode to my daemon array and acpi-cpufreq to modules. A few issues I immediately notice:
1) cpufreq doesn't revert back to higher frequencies if I unplug and plug power source back in (before unplugging: CPU 0 - 800 MHz, CPU 1 - 2.00 GHz; after both are 800 and won't change if I plug power source back in)
2) I believe the hard disk is actually spinning down more frequently (and fan is almost always on, even when no work is being done). Here are the relevant files/the ones that I have altered.
laptop-mode.conf
# Configuration for Laptop Mode Tools
# There is a "system" to the configuration setting names:
# CONTROL_something=0/1 Determines whether Laptop Mode Tools controls
# something
# LM_something=value Value of "something" when laptop mode is active
# NOLM_something=value Value of "something" when laptop mode is NOT
# active
# AC_something=value Value of "something" when the computer is running
# on AC power
# BATT_something=value Value of "something when the computer is running
# on battery power
# There can be combinations of LM_/NOLM_ and AC_/BATT_ prefixes, but the
# available prefixes are different for each setting. The available ones are
# documented in the manual page, laptop-mode.conf(8). If there is no LM_/
# NOLM_ in a setting name, then the value is used independently of laptop
# mode state, and similarly, if there is no AC_/BATT_, then the value is used
# independently of power state.
# Some options only work on ACPI systems. They are marked ACPI-ONLY.
# Note that this configuration file is a fragment of shell script: you
# can use all the features of the shell scripting language to achieve your
# desired configuration.
# Modules
# Laptop Mode Tools modules have separate configuration files, that can be
# found in /etc/laptop-mode/conf.d. Please look through these configuration
# files as well, there are many useful power saving tools in there!
# Enable/Disable laptop-mode-tools execution
# Set it to 0 to completely disable laptop-mode-tools from running
ENABLE_LAPTOP_MODE_TOOLS=1
# Configuration debugging
# Set this to 1 if you want to see a lot of information when you start/stop
# laptop_mode.
VERBOSE_OUTPUT=0
# Set this to 1 if you want to log messages to syslog
LOG_TO_SYSLOG=1
# Run in shell debug mode
# Enable this if you would like to execute the entire laptop-mode-tools program
# in shell debug mode. Warning: This will create a lot of text output
# If you are debugging an individual module, perhaps you would want to enable
# each module specific debug mode (available in module conf files)
DEBUG=0
# When to enable laptop mode
# "Laptop mode" is the mode in which laptop mode tools makes the computer
# consume less power. This includes the kernel "laptop_mode" feature, which
# allows your hard drives to spin down, as well as various other settings which
# can be tweaked by laptop mode tools. You can enable or disable all of these
# settings using the CONTROL_... options further down in this config file.
# Enable laptop mode when on battery power.
ENABLE_LAPTOP_MODE_ON_BATTERY=1
# Enable laptop mode when on AC power.
ENABLE_LAPTOP_MODE_ON_AC=1
# Enable laptop mode when the laptop's lid is closed, even when we're on AC
# power? (ACPI-ONLY)
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0
# Enable all simple zero-configuration auto modules
# This option enables all simple modules (listed below) without requiring
# the user to enable each module individually
# List of modules which can be automatically enabled with this setting are:
# ac97-powersave
# cpufreq
# dpms-standby
# eee-superhe
# ethernet
# exec-commands
# hal-polling
# hdparm
# intel-hda-powersave
# intel-sata-powermgmt
# runtime-pm
# sched-mc-power-savings
# sched-smt-power-savings
# terminal-blanking
# usb-autosuspend
# wireless-ipw-power
# wireless-iwl-power
# wireless-power
# Set this to 1 to enable all simple zero-configuration auto modules listed above.
# NOTE: You can explicitly enable/disable any of the above modules by changing their
# values in the individual settings file
ENABLE_AUTO_MODULES=1
# When to enable data loss sensitive features
# When data loss sensitive features are disabled, laptop mode tools acts as if
# laptop mode were disabled, for those features only.
# Data loss sensitive features include:
# - laptop_mode (i.e., delayed writes)
# - hard drive write cache
# All of the options that follow can be set to 0 in order to prevent laptop
# mode tools from using them to stop data loss sensitive features. Use this
# when you have a battery that reports the wrong information, that confuses
# laptop mode tools.
# Disabling data loss sensitive features is ACPI-ONLY, and it only works if
# your battery gives off frequent ACPI events to indicate a change in battery
# level.
# NOTE: If your battery does NOT give off battery events often enough, you can
# enable the battery-level-polling module to make this work. Look at the
# file /etc/laptop-mode/conf.d/battery-level-polling.conf for more information.
# Disable all data loss sensitive features when the battery level (in % of the
# battery capacity) reaches this value.
MINIMUM_BATTERY_CHARGE_PERCENT=3
# Disable data loss sensitive features when the battery reports its state
# as "critical".
DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
# Controlled hard drives and partitions
# For spinning down your hard drives, laptop mode will remount file systems and
# adjust hard drive spindown timeouts. These parameters specify which
# devices and partitions are affected by laptop mode.
# The drives that laptop mode controls.
# Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
# wildcard, which will get you all your IDE and SCSI/SATA drives.
HD="/dev/[hs]d[abcdefgh]"
# The partitions (or mount points) that laptop mode controls.
# Separate the values by spaces. Use "auto" to indicate all partitions on drives
# listed in HD. You can add things to "auto", e.g. "auto /dev/hdc3". You can
# also specify mount points, e.g. "/mnt/data".
PARTITIONS="auto /dev/mapper/*"
# If this is enabled, laptop mode tools will assume that SCSI drives are
# really SATA drives that only _look_ like SCSI drives, and will use hdparm
# to control them. Set this to 0 if you have /dev/sd devices and you want
# laptop mode tools to use the "sdparm" command to control them.
ASSUME_SCSI_IS_SATA=1
# Hard drive behaviour settings
# These settings specify how laptop mode tools will adjust the various
# parameters of your hard drives and file systems.
# Maximum time, in seconds, of work that you are prepared to lose when your
# system crashes or power runs out. This is the maximum time that Laptop Mode
# will keep unsaved data waiting in memory before spinning up your hard drive.
LM_BATT_MAX_LOST_WORK_SECONDS=600
LM_AC_MAX_LOST_WORK_SECONDS=360
# Should laptop mode tools control readahead?
CONTROL_READAHEAD=1
# Read-ahead, in kilobytes. You can spin down the disk while playing MP3/OGG
# by setting the disk readahead to a reasonable size, e.g. 3072 (3 MB).
# Effectively, the disk will read a complete MP3 at once, and will then spin
# down while the MP3/OGG is playing. Don't set this too high, because the
# readahead is applied to _all_ files that are read from disk.
LM_READAHEAD=3072
NOLM_READAHEAD=128
# Should laptop mode tools add the "noatime" option to the mount options when
# laptop mode is enabled?
CONTROL_NOATIME=0
# Should laptop use relatime instead of noatime? The "relatime" mount option has
# more standards-compliant semantics, and allows more applications to work,
# while retaining a low level of atime updates (i.e., disk writes).
USE_RELATIME=0
# Should laptop mode tools control the hard drive idle timeout settings?
CONTROL_HD_IDLE_TIMEOUT=1
# Idle timeout values. (hdparm -S)
# Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
# for battery and for AC with laptop mode on.
LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
NOLM_HD_IDLE_TIMEOUT_SECONDS=7200
# Should laptop mode tools control the hard drive power management settings?
# Set to 0 to disable
CONTROL_HD_POWERMGMT="auto"
# Power management for HD (hdparm -B values)
BATT_HD_POWERMGMT=128
LM_AC_HD_POWERMGMT=254
NOLM_AC_HD_POWERMGMT=254
# Should laptop mode tools control the hard drive write cache settings?
CONTROL_HD_WRITECACHE=0
# Write cache settings for HD (hdparm -W values)
NOLM_AC_HD_WRITECACHE=1
NOLM_BATT_HD_WRITECACHE=0
LM_HD_WRITECACHE=0
# Settings you probably don't want to touch
# It is usually not necessary to change these parameters. They are included
# for completeness' sake.
# Change mount options on partitions in PARTITIONS? You don't really want to
# disable this. If you do, then your hard drives will probably not spin down
# anymore.
CONTROL_MOUNT_OPTIONS=1
# Dirty synchronous ratio. At this percentage of dirty pages the process
# which calls write() does its own writeback.
LM_DIRTY_RATIO=60
NOLM_DIRTY_RATIO=40
# Allowed dirty background ratio, in percent. Once DIRTY_RATIO has been
# exceeded, the kernel will wake pdflush which will then reduce the amount
# of dirty memory to dirty_background_ratio. Set this nice and low, so once
# some writeout has commenced, we do a lot of it.
LM_DIRTY_BACKGROUND_RATIO=1
NOLM_DIRTY_BACKGROUND_RATIO=10
# kernel default settings -- don't touch these unless you know what you're
# doing.
DEF_UPDATE=5
DEF_XFS_AGE_BUFFER=15
DEF_XFS_SYNC_INTERVAL=30
DEF_XFS_BUFD_INTERVAL=1
DEF_MAX_AGE=30
# This must be adjusted manually to the value of HZ in the running kernel
# on 2.4, until the XFS people change their 2.4 external interfaces to work in
# centisecs. This can be automated, but it's a work in progress that still
# needs some fixes. On 2.6 kernels, XFS uses USER_HZ instead of HZ for
# external interfaces, and that is currently always set to 100. So you don't
# need to change this on 2.6.
XFS_HZ=100
# Seconds laptop mode has to to wait after the disk goes idle before doing
# a sync.
LM_SECONDS_BEFORE_SYNC=2
cpufreq.conf
# Configuration file for Laptop Mode Tools module cpufreq.
# For more information, consult the laptop-mode.conf(8) manual page.
# CPU frequency scaling and throttling
# Laptop mode tools can automatically adjust your kernel CPU frequency
# settings. This includes upper and lower limits and scaling governors.
# There is also support for CPU throttling, on systems that don't support
# frequency scaling.
# This feature only works on 2.6 kernels.
# IMPORTANT: In versions 1.36 and earlier, these settings were included in the
# main laptop-mode.conf configuration file. If they are still present, they
# overrule the settings in this file. To fix this, simply delete the settings
# from the main config file.
# Enable debug mode for this module
# Set to 1 if you want to debug this module
DEBUG=0
# Should laptop mode tools control the CPU frequency settings?
# Set to 0 to disable
CONTROL_CPU_FREQUENCY="auto"
# Legal values are "slowest" for the slowest speed that your
# CPU is able to operate at, "fastest" for the fastest speed,
# "medium" for some value in the middle, or any value listed in
# /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
# The "governor" can be any governor installed on your system, this usually
# includes "ondemand", "conservative", and "performance". The
# "IGNORE_NICE_LOAD" setting specifies that background programs that have
# a low priority ("nice level") should not cause the CPU frequency to
# be increased. (You generally want this to be enabled in battery mode.)
BATT_CPU_MAXFREQ=fastest
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=ondemand
NOLM_AC_CPU_IGNORE_NICE_LOAD=0
# Should laptop mode tools control the CPU throttling? This is only useful
# on processors that don't have frequency scaling.
# (Only works when you have /proc/acpi/processor/CPU*/throttling.)
# This is only useful on older P4 processors that do not support frequency
# scaling. On such processors, this is the only way to reduce power consumption
# but at the cost of higher performance penalty.
# Enable this only if you have a processor that does not support frequency scaling
# On most new processors, you might want to disable it.
# Set to 0 to disable.
CONTROL_CPU_THROTTLING=0
# Legal values are "maximum" for the maximum (slowest) throttling level,
# "minimum" for minimum (fastest) throttling level, "medium" for a value
# somewhere in the middle (this is usually 50% for P4s), or any value listed
# in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
# this may be _very_ slow (in fact, with P4s it slows down the processor
# by a factor 8).
BATT_CPU_THROTTLING=medium
LM_AC_CPU_THROTTLING=medium
NOLM_AC_CPU_THROTTLING=minimum
battery-level-polling.conf
# Configuration file for Laptop Mode Tools module battery-level-polling.
# For more information, consult the laptop-mode.conf(8) manual page.
# Battery level polling settings
# This module allows laptop mode to react to battery level changes, even if the
# battery does not send out frequent ACPI events for such battery level changes.
# Note that this does NOT make ACPI-only features work on non-ACPI hardware.
# Enable debug mode for this module
# Set to 1 if you want to debug this module
DEBUG=0
# Enable this setting to enable battery level polling.
ENABLE_BATTERY_LEVEL_POLLING=1
hal-polling.conf
# Configuration file for Laptop Mode Tools module hal-polling.
# For more information, consult the laptop-mode.conf(8) manual page.
# HAL polling settings
# If you enable this module, laptop mode tools will control the polling of
# your CD/DVD drives by HAL. Disabling polling saves a considerable amount of
# power, but for some older CD/DVD drives it means that inserted CDs are no
# longer autodetected. In such cases, you must turn this option off.
# Alternatively, you can configure laptop mode tools to turn HAL polling on only
# when the laptop is running on AC power. This would mean that CDs are not
# autodetected while the laptop is running on battery power, but the power
# savings may be worth the extra manual labour when you insert a CD.
# Enable debug mode for this module
# Set to 1 if you want to debug this module
DEBUG=0
# Control HAL polling?
# Set to 0 to disablei, vs "auto".
CONTROL_HAL_POLLING=0
# Disable HAL polling on battery?
BATT_DISABLE_HAL_POLLING=0
# Disable HAL polling on AC?
AC_DISABLE_HAL_POLLING=0
# Drives to apply HAL polling settings to
HAL_POLLING_DEVICES="/dev/scd?"
Please let me know if you require any additional information. Thank you in advance for any help.
Last edited by Aesir (2011-04-14 14:35:09)

Aesir wrote:Can I make BATT_CPU_GOVERNOR=conservative even if it is not listed in the scaling_available_governors file?
If your governor isn't listed in scaling_available_governors, it won't work. See stqn's link for info on adding governors.
stqn wrote:Edit2: oh well, scrolling a bit up, the wiki says you don't need to add governors if you're using laptop-mode-tools... I don't know.
You do need governors if you're using laptop-mode-tools, because all laptop-mode-tools does is flip between them automatically.
If you're using cpufrequtils, you'll need the userspace governor for it to work properly. I don't use cpufrequtils personally, so I'm not sure how to get it to work in conjunction with laptop-mode-tools. You may have to disable frequency scaling in laptop-mode-tools by changing CONTROL_CPU_FREQUENCY to 0 in cpufreq.conf
Edit - now that I think about it, maybe laptop-mode-tools and cpufrequtils know how to load the modules themselves automatically. I guess try it and see if they can. You can check which governor is in use with:
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
You can also manually change governors by running (as root):
# echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Of course, substitue the governor you want.
Last edited by redden0t8 (2011-03-29 19:27:12)

DispatchEvent not working in debug mode

Hello,
I have a localconnection, and when I receive a message from
the local connection I dispatch an event. However, the dispatch
event does not work. I step into the code and go into some
Macromedia code for the "mx.events.EventDispatcher.dispatchEvent"
and "mx.events.EventDispatcher.dispatchQueue", and when I inspect
my variables the eventObj has both a target and a type set, but
when the code tries to access them through eventObj.target and
eventObj.type it returns null.
Also, this only happens in debug mode (Debug -> Debug
Movie) and not in test mode (Control -> Test Movie). In test
movie the exact same code works flawlessly.

Im not very sure just try to help but look this one
mx.utils.Delegate
i look for some issue with your problem and i think this can help
you.

Restart the server in debug mode: How to drop saved passwords?

In NWDS server pane, I entered a wrong password when trying to restart my SAP AS Java in debug mode. Now I only get exceptions "com.sap.enginemanagement.UnauthorizedException: Incorrect login information provided" without a chance of changing the entered credentials. Restarting NWDS didn't work.
Any ideas?
Thx,
Christoph

Hi Christoph,
are you talking about the "Java EE" perspective and the "Servers" view within it? I tried it out and it does not behave properly.
Try the "SAP Management" perspective. Within the left hand tree open your system, expand the instance starting with "J..", expand the "AS Java" node and select the "Process Table" node. In the right hand table select the server0 process and chose from the context menu "Start Debug Session".
The SAP JVM offers some extra debug options. Expand the "Expert Mode" in the modal dialog. If you want to debug web applications select "code isolation" and unselect all other options. A password dialog will appear and you must enter the credentials for the operating system user, not for the AS Java administrator.
One table column is labeled "Debug", there you can see the currrent debug port.
Either you start now a "Remote Java Application Debug" debug session or you have a Java EE project and can create a "SAP Application" debug session.
Anyway to see your application threads in the debugger you have to access your web application with a special debug URL.
If your URL looks like this: "http://localhost:50000/myapp" you have to insert a debug token beween host part and the path and the URL becomes "http://localhost:50000/@@@DEBUG@@@/myapp". If you miss to modify the URL you will not see any thread.
If you want to get a "normal" debug behaviour just deselect all options in the debug dialog. You will see all threads, you do not have to modify your URL, but the server will restart after you detached the debugger.
Hope this helps.
Best Regards, Stefan
Edited by: Stefan Bodenstein on Oct 1, 2008 12:00 PM

How to debug smartform in display mode?

Hi,
How to debug smartforms program lines in display mode? Need help on this issue?
<MOVED BY MODERATOR TO THE CORRECT FORUM>
Edited by: Alvaro Tejada Galindo on Jan 12, 2010 11:32 AM
Moderator message - Cross post locked
Edited by: Rob Burbank on Jan 12, 2010 11:57 AM

Please search before posting
<< Cut and paste without attribution from http://it.toolbox.com/wiki/index.php/SAP_Smart_Forms removed >>
<< Please don't ask other to follow the forum rules and violate them yourself! >>
*In simple way---follow these steps:-
If you are in a non-modifiable client:
Display your SmartForm.
Go to Environment and copy the function module name.
Go to SE37 and display the function.
Go to Smartforms and copy the node name where you want to debugg.
Go to the function and search for the name in main program. Put a soft break point.*
Manas M
Edited by: Kumar Manas Mishra on Jan 12, 2010 12:05 PM
Edited by: Kumar Manas Mishra on Jan 12, 2010 12:06 PM
Edited by: Rob Burbank on Jan 12, 2010 11:52 AM

Debug and run time mode

Is there a way to turn DEBUG on when running in runtime mode without having the developer toolbar displayed?
Andy.

Andy,
Yes. The key is iin the URL which is appid:pageid:sessionid:request:debug...
So to turn it on the fifth value in the URL needs to be YES.
Regards,
Dan
http://danielmcghan.us
http://sourceforge.net/projects/tapigen
http://sourceforge.net/projects/plrecur
You can reward this reply by marking it as either Helpful or Correct ;-)

[SOLVED] Overheating MacBook Pro on AC power

Hi,
I'm coming over from OSX, dual-booting my MBP (2013, 11,1 model) with Arch and, I have to say, I'm loving it. After a couple of weeks of tinkering, I'm getting towards a really useable minimal system (dwm, uzbl-browser, urxvt, mutt - etc) but I have a really annoying outstanding problem: the machine overheats when plugged into a/c power.
On battery:
$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +54.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +54.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +52.0°C (high = +100.0°C, crit = +100.0°C)
applesmc-isa-0300
Adapter: ISA adapter
Right Side : 2211 RPM (min = 2200 RPM, max = 6199 RPM)
TA0P: +40.5°C
TB0T: +35.8°C
TB1T: +35.8°C
TB2T: +34.5°C
TBXT: +35.8°C
TC0C: +53.0°C
TC0E: +54.0°C
TC0F: +54.5°C
TC0P: +50.0°C
TC1C: +52.0°C
TCGC: +52.0°C
TCSA: +50.0°C
TCXC: +54.0°C
TH0A: +41.8°C
TH0B: +41.8°C
TH0C: -127.0°C
TH0F: -39.2°C
TH0R: -39.2°C
TH0V: +39.5°C
TH0a: +41.8°C
TH0b: +41.8°C
TH0c: -127.0°C
THSP: -127.0°C
TM0P: +44.5°C
TMLB: -127.0°C
TPCD: +55.0°C
TW0P: -127.0°C
Th1H: +41.8°C
Ts0P: +33.0°C
Ts0S: +38.8°C
Ts1S: +37.2°C
Plug in AC and within five seconds:
$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +69.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +69.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +69.0°C (high = +100.0°C, crit = +100.0°C)
applesmc-isa-0300
Adapter: ISA adapter
Right Side : 4130 RPM (min = 4125 RPM, max = 6199 RPM)
TA0P: +41.0°C
TB0T: +35.5°C
TB1T: +35.5°C
TB2T: +34.5°C
TBXT: +35.5°C
TC0C: +68.0°C
TC0E: +68.8°C
TC0F: +69.5°C
TC0P: +58.5°C
TC1C: +69.0°C
TCGC: +61.0°C
TCSA: +63.0°C
TCXC: +69.0°C
TH0A: +41.8°C
TH0B: +41.8°C
TH0C: -127.0°C
TH0F: -39.2°C
TH0R: -39.2°C
TH0V: +40.0°C
TH0a: +41.8°C
TH0b: +41.8°C
TH0c: -127.0°C
THSP: -127.0°C
TM0P: +47.8°C
TMLB: -127.0°C
TPCD: +66.0°C
TW0P: -127.0°C
Th1H: +45.2°C
Ts0P: +33.2°C
Ts0S: +40.0°C
Ts1S: +38.0°C
For around a week, before I installed macfanctl, the fan wasn't coming on at all and sensors was reporting 100 deg C. Scary. Now unless I'm compiling or watching video, it at least doesn't get higher than 70 deg C, but it's annoying and I'm sure unnecessary to have the fan on all the time with the power plugged in. Plus the laptop is pretty warm at this temp.
I'm using laptop-mode-tools but this problem still happens when laptop-mode-tools is disabled. However, for the record, when running, the laptop-mode config is as follows:
$ cat /etc/laptop-mode/laptop-mode.conf
# Configuration for Laptop Mode Tools
# There is a "system" to the configuration setting names:
# CONTROL_something=0/1 Determines whether Laptop Mode Tools controls
# something
# LM_something=value Value of "something" when laptop mode is active
# NOLM_something=value Value of "something" when laptop mode is NOT
# active
# AC_something=value Value of "something" when the computer is running
# on AC power
# BATT_something=value Value of "something when the computer is running
# on battery power
# There can be combinations of LM_/NOLM_ and AC_/BATT_ prefixes, but the
# available prefixes are different for each setting. The available ones are
# documented in the manual page, laptop-mode.conf(8). If there is no LM_/
# NOLM_ in a setting name, then the value is used independently of laptop
# mode state, and similarly, if there is no AC_/BATT_, then the value is used
# independently of power state.
# Some options only work on ACPI systems. They are marked ACPI-ONLY.
# Note that this configuration file is a fragment of shell script: you
# can use all the features of the shell scripting language to achieve your
# desired configuration.
# Modules
# Laptop Mode Tools modules have separate configuration files, that can be
# found in /etc/laptop-mode/conf.d. Please look through these configuration
# files as well, there are many useful power saving tools in there!
# Enable/Disable laptop-mode-tools execution
# Set it to 0 to completely disable laptop-mode-tools from running
ENABLE_LAPTOP_MODE_TOOLS=1
# Configuration debugging
# Set this to 1 if you want to see a lot of information when you start/stop
# laptop_mode.
VERBOSE_OUTPUT=0
# Set this to 1 if you want to log messages to syslog
LOG_TO_SYSLOG=1
# Run in shell debug mode
# Enable this if you would like to execute the entire laptop-mode-tools program
# in shell debug mode. Warning: This will create a lot of text output
# If you are debugging an individual module, perhaps you would want to enable
# each module specific debug mode (available in module conf files)
DEBUG=0
# When to enable laptop mode
# "Laptop mode" is the mode in which laptop mode tools makes the computer
# consume less power. This includes the kernel "laptop_mode" feature, which
# allows your hard drives to spin down, as well as various other settings which
# can be tweaked by laptop mode tools. You can enable or disable all of these
# settings using the CONTROL_... options further down in this config file.
# Enable laptop mode when on battery power.
ENABLE_LAPTOP_MODE_ON_BATTERY=1
# Enable laptop mode when on AC power.
ENABLE_LAPTOP_MODE_ON_AC=1
# Enable laptop mode when the laptop's lid is closed, even when we're on AC
# power? (ACPI-ONLY)
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0
# Enable all simple zero-configuration auto modules
# This option enables all simple modules (listed below) without requiring
# the user to enable each module individually
# List of modules which can be automatically enabled with this setting are:
# ac97-powersave
# cpufreq
# dpms-standby
# eee-superhe
# ethernet
# exec-commands
# hal-polling
# hdparm
# intel-hda-powersave
# intel-sata-powermgmt
# nmi-watchdog
# pcie-aspm
# runtime-pm
# sched-mc-power-savings
# sched-smt-power-savings
# terminal-blanking
# wireless-ipw-power
# wireless-iwl-power
# wireless-power
# Set this to 1 to enable all simple zero-configuration auto modules listed above.
# NOTE: You can explicitly enable/disable any of the above modules by changing their
# values in the individual settings file
ENABLE_AUTO_MODULES=1
# When to enable data loss sensitive features
# When data loss sensitive features are disabled, laptop mode tools acts as if
# laptop mode were disabled, for those features only.
# Data loss sensitive features include:
# - laptop_mode (i.e., delayed writes)
# - hard drive write cache
# All of the options that follow can be set to 0 in order to prevent laptop
# mode tools from using them to stop data loss sensitive features. Use this
# when you have a battery that reports the wrong information, that confuses
# laptop mode tools.
# Disabling data loss sensitive features is ACPI-ONLY, and it only works if
# your battery gives off frequent ACPI events to indicate a change in battery
# level.
# NOTE: If your battery does NOT give off battery events often enough, you can
# enable the battery-level-polling module to make this work. Look at the
# file /etc/laptop-mode/conf.d/battery-level-polling.conf for more information.
# Disable all data loss sensitive features when the battery level (in % of the
# battery capacity) reaches this value.
MINIMUM_BATTERY_CHARGE_PERCENT=3
# Disable data loss sensitive features when the battery reports its state
# as "critical".
DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
# Ignore the alarm value reported by your batteries. In some instances a
# a battery will report an abnormally high alarm value, resulting in data-loss
# sensitive features being disabled prematurely.
DISABLE_BATTERY_ALARM_CHECK=0
# Controlled hard drives and partitions
# For spinning down your hard drives, laptop mode will remount file systems and
# adjust hard drive spindown timeouts. These parameters specify which
# devices and partitions are affected by laptop mode.
# The drives that laptop mode controls.
# Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
# wildcard, which will get you all your IDE and SCSI/SATA drives.
HD="/dev/[hs]d[abcdefgh]"
# The partitions (or mount points) that laptop mode controls.
# Separate the values by spaces. Use "auto" to indicate all partitions on drives
# listed in HD. You can add things to "auto", e.g. "auto /dev/hdc3". You can
# also specify mount points, e.g. "/mnt/data".
PARTITIONS="auto /dev/mapper/*"
# If this is enabled, laptop mode tools will assume that SCSI drives are
# really SATA drives that only _look_ like SCSI drives, and will use hdparm
# to control them. Set this to 0 if you have /dev/sd devices and you want
# laptop mode tools to use the "sdparm" command to control them.
ASSUME_SCSI_IS_SATA=1
# Hard drive behaviour settings
# These settings specify how laptop mode tools will adjust the various
# parameters of your hard drives and file systems.
# Maximum time, in seconds, of work that you are prepared to lose when your
# system crashes or power runs out. This is the maximum time that Laptop Mode
# will keep unsaved data waiting in memory before spinning up your hard drive.
LM_BATT_MAX_LOST_WORK_SECONDS=600
LM_AC_MAX_LOST_WORK_SECONDS=360
# Should laptop mode tools control readahead?
CONTROL_READAHEAD=1
# Read-ahead, in kilobytes. You can spin down the disk while playing MP3/OGG
# by setting the disk readahead to a reasonable size, e.g. 3072 (3 MB).
# Effectively, the disk will read a complete MP3 at once, and will then spin
# down while the MP3/OGG is playing. Don't set this too high, because the
# readahead is applied to _all_ files that are read from disk.
LM_READAHEAD=3072
NOLM_READAHEAD=128
# Should laptop mode tools add the "noatime" option to the mount options when
# laptop mode is enabled?
CONTROL_NOATIME=0
# Should laptop use relatime instead of noatime? The "relatime" mount option has
# more standards-compliant semantics, and allows more applications to work,
# while retaining a low level of atime updates (i.e., disk writes).
USE_RELATIME=1
# Should laptop mode tools control the hard drive idle timeout settings?
CONTROL_HD_IDLE_TIMEOUT=1
# Idle timeout values. (hdparm -S)
# Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
# for battery and for AC with laptop mode on.
LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
#NOLM_HD_IDLE_TIMEOUT_SECONDS=7200
NOLM_HD_IDLE_TIMEOUT_SECONDS=600
# Should laptop mode tools control the hard drive power management settings?
# Set to 0 to disable
#CONTROL_HD_POWERMGMT="auto"
CONTROL_HD_POWERMGMT=1
# Power management for HD (hdparm -B values)
BATT_HD_POWERMGMT=1
LM_AC_HD_POWERMGMT=1
NOLM_AC_HD_POWERMGMT=1
#LM_AC_HD_POWERMGMT=254
#NOLM_AC_HD_POWERMGMT=254
# Should laptop mode tools control the hard drive write cache settings?
CONTROL_HD_WRITECACHE=0
# Write cache settings for HD (hdparm -W values)
NOLM_AC_HD_WRITECACHE=1
NOLM_BATT_HD_WRITECACHE=0
LM_HD_WRITECACHE=0
# Settings you probably don't want to touch
# It is usually not necessary to change these parameters. They are included
# for completeness' sake.
# Change mount options on partitions in PARTITIONS? You don't really want to
# disable this. If you do, then your hard drives will probably not spin down
# anymore.
CONTROL_MOUNT_OPTIONS=1
# Dirty synchronous ratio. At this percentage of dirty pages the process
# which calls write() does its own writeback.
LM_DIRTY_RATIO=60
NOLM_DIRTY_RATIO=40
# Allowed dirty background ratio, in percent. Once DIRTY_RATIO has been
# exceeded, the kernel will wake pdflush which will then reduce the amount
# of dirty memory to dirty_background_ratio. Set this nice and low, so once
# some writeout has commenced, we do a lot of it.
LM_DIRTY_BACKGROUND_RATIO=1
NOLM_DIRTY_BACKGROUND_RATIO=10
# kernel default settings -- don't touch these unless you know what you're
# doing.
DEF_UPDATE=5
DEF_XFS_AGE_BUFFER=15
DEF_XFS_SYNC_INTERVAL=30
DEF_XFS_BUFD_INTERVAL=1
DEF_MAX_AGE=30
# This must be adjusted manually to the value of HZ in the running kernel
# on 2.4, until the XFS people change their 2.4 external interfaces to work in
# centisecs. This can be automated, but it's a work in progress that still
# needs some fixes. On 2.6 kernels, XFS uses USER_HZ instead of HZ for
# external interfaces, and that is currently always set to 100. So you don't
# need to change this on 2.6.
XFS_HZ=100
# Seconds laptop mode has to to wait after the disk goes idle before doing
# a sync.
LM_SECONDS_BEFORE_SYNC=2
I've done a lot of Googling but have drawn a blank. The fan comes on and off so quickly and the sensors reading changes so quickly, I'm convinced it's a software issue (something is being triggered on plug/unplug, rather than it being the hardware gradually cooling or heating) but I don't know where else to look.
Any advice would be much appreciated.
Thanks!
Last edited by shelgy (2014-11-06 22:33:18)

UPDATE:
Did some digging around in laptop-mode.
In /etc/laptop-mode/config.d/intel_pstate.conf, changed the following line:
LM_AC_INTEL_PSTATE_PERF_MAX_PCT=100 # Maximum performance, in percent
to:
LM_AC_INTEL_PSTATE_PERF_MAX_PCT=50 # Maximum performance, in percent
Now been running on AC power for 10 minutes and sensor data the same as on the battery.
Fingers crossed, but it looks like this is solved. Hope this is useful for others. Been pulling my hair out!
Thanks all for considering.

[Solved] Debugging in QtCreator in "c++" & "qml" modes simultaneously

Similar Messages

Maybe you are looking for