[Bug 719333] Re: CLVM not locking LV's properly even when set to exclusive
@tom: Manually AND with a selfcrafted initscript. It's working, and in the Logs of Openais i can see that some kind of info is being replicated through the cluster when i make changes to the LVM Metadata. @ante: it should have worked the way i did it, i know that i had no resources configured, coz it didn't let me go so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719333 Title: CLVM not locking LV's properly even when set to exclusive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719333] Re: CLVM not locking LV's properly even when set to exclusive
Nevermind, I realized that Ubuntu is no Cluster aware OS, and switched to another Platform. Sorry dudes, nearly one month of ignorance on such a heavy bug won't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719333 Title: CLVM not locking LV's properly even when set to exclusive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719333] Re: CLVM not locking LV's properly even when set to exclusive
Hey, no one cares? Hello?! Ubuntu LTS is a real thread for Clusters now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719333 Title: CLVM not locking LV's properly even when set to exclusive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719333] Re: CLVM not locking LV's properly even when set to exclusive
OK - so what can we do against it now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719333 Title: CLVM not locking LV's properly even when set to exclusive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719333] [NEW] CLVM not locking LV's properly even when set to exclusive
Public bug reported: Binary package hint: lvm2 Hello, i got Ubuntu Lucid Server + openais + lvm + clvm running on a central storage. Metadata updates are distributed properly: root@xen1:~# vgs VG #PV #LV #SN Attr VSize VFree vgsas11 5 0 wz--nc 1.36t 1.33t root@xen1:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-diskvgsas1 -wi-a- 4.00g root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi-a- 4.00g root@xen1:~# lvchange -an vgsas1/play1.xxx.net-disk root@xen1:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-diskvgsas1 -wi--- 4.00g NOW: Metadata obviously distributed correctly the xen2 root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi--- 4.00g root@xen1:~# lvchange -aey vgsas1/play1.xxx.net-disk root@xen1:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-diskvgsas1 -wi-a- 4.00g NOW: LV still shown as inactive on the second node. root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi--- 4.00g NOW: even better, i can activate it exclusive on the second node: root@xen2:~# lvchange -aey vgsas1/play1.xxx.net-disk root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi-a- 4.00g I can even mount it from both nodes: root@xen2:~# mount /dev/vgsas1/play1.xxx.net-disk /mnt/ root@xen2:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p1 57672700 9810272 44932816 18% / none525972 268525704 1% /dev none525972 9512516460 2% /dev/shm none52597272525900 1% /var/run none525972 0525972 0% /var/lock none525972 0525972 0% /lib/init/rw /dev/mapper/vgsas1-play1.xxx.net--disk 4128448754656 3164080 20% /mnt AND ON: root@xen1:~# !mou mount /dev/vgsas1/play1.xxx.net-disk /mnt/ root@xen1:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p1 24030076 14832148 7977272 66% / none525972 280525692 1% /dev none525972 9392516580 2% /dev/shm none52597284525888 1% /var/run none525972 0525972 0% /var/lock none525972 0525972 0% /lib/init/rw /dev/mapper/vgsas1-play1.xxx.net--disk 4128448754656 3164080 20% /mnt If that was no test setting but 2 vm's accessing one ext3 fs simultaneously, I would be in serious trouble now! btw, the Clvm was recompiled against openais to get rid of cman. root@xen1:~# dpkg --list|grep lvm ii clvm2.02.54-1ubuntu4.2 Cluster LVM Daemon for lvm2 ii lvm22.02.54-1ubuntu4.1 The Linux Logical Volume Manager root@xen1:~# crm status Last updated: Tue Feb 15 14:16:39 2011 Stack: openais Current DC: xen2 - partition with quorum Version: 1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd 2 Nodes configured, 2 expected votes 0 Resources configured. Online: [ xen1 xen2 ] What's wrong there? so long, Bastian ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719333 Title: CLVM not locking LV's properly even when set to exclusive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512937] Re: [MASTER] package firefox 3.6+nobinonly-0ubuntu1 failed to install/upgrade: update-alternatives: error: alternative path /usr/bin/firefox doesn't exist.
Same error here, method from #11 fixed it, too. I remember that I had similar problems getting firefox running after updating this particular installation from Hardy to Lucid Alpha Versions, but I can't remember installing any non ubuntu FF packages. -- [MASTER] package firefox 3.6+nobinonly-0ubuntu1 failed to install/upgrade: update-alternatives: error: alternative path /usr/bin/firefox doesn't exist. https://bugs.launchpad.net/bugs/512937 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 516684] Re: After upgrade from Karmic boot fails, mountall and udevd fail
Canonical doesn't make it easy for one to stand behind them, if again and again you get a Knife in your back. Upstart is not a solution aimed at Servers, hence it should be removed from the serveredition. It renders it totally unusable in Virtualized environments, where more dependencies exist.. What are Canonicals plans for that? -- After upgrade from Karmic boot fails, mountall and udevd fail https://bugs.launchpad.net/bugs/516684 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240071] Re: BUG: soft lockup - CPU#0 stuck for 11s!
Is Canonical about to drop Support completely for XEN? Now that Xensource has integrated pvops() and domU support is in the mainline? I was forced to build myself own .deb packages for 2.6.32.10, as well as xen-4.0.0 and xen-tools for Lucid, which lacks dom0 support completely. It took me kinda 5 hours to do everything and roll out (yet the packages wouldn't really conform official repositories) and so far it runs rock solid. What's so hard about it? greets, bastian -- BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/240071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562912] [NEW] munin-node plugin initialisation fails on ip_
Public bug reported: Binary package hint: munin When installing munin-node on Hardy-Server (i386 and x64), the plugin initialisation fails. Reproduceable with munin-node-configure --shell: r...@ncore:~# munin-node-configure --shell ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_0.0.0.0/0 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.1.0/24 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.2.0/23 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.6.0/24 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.7.0/24 (which have to fail, because of a / in the Filename. According to munin this is a misbehaviour in 1.2.5 and should be solved in 1.2.6. Will the packages in the repo be fixed please? ** Affects: munin (Ubuntu) Importance: Undecided Status: New -- munin-node plugin initialisation fails on ip_ https://bugs.launchpad.net/bugs/562912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 562912] Re: munin-node plugin initialisation fails on ip_, with netmasks present
Why is my Hardy still behaving that way?! It's apt-get update/upgraded! And I don't see munin in the SRU list for Hardy! -- munin-node plugin initialisation fails on ip_, with netmasks present https://bugs.launchpad.net/bugs/562912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 562912] [NEW] munin-node plugin initialisation fails on ip_
Public bug reported: Binary package hint: munin When installing munin-node on Hardy-Server (i386 and x64), the plugin initialisation fails. Reproduceable with munin-node-configure --shell: r...@ncore:~# munin-node-configure --shell ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_0.0.0.0/0 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.1.0/24 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.2.0/23 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.6.0/24 ln -s /usr/share/munin/plugins/ip_ /etc/munin/plugins/ip_192.168.7.0/24 (which have to fail, because of a / in the Filename. According to munin this is a misbehaviour in 1.2.5 and should be solved in 1.2.6. Will the packages in the repo be fixed please? ** Affects: munin (Ubuntu) Importance: Undecided Status: New -- munin-node plugin initialisation fails on ip_ https://bugs.launchpad.net/bugs/562912 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562912] Re: munin-node plugin initialisation fails on ip_, with netmasks present
Why is my Hardy still behaving that way?! It's apt-get update/upgraded! And I don't see munin in the SRU list for Hardy! -- munin-node plugin initialisation fails on ip_, with netmasks present https://bugs.launchpad.net/bugs/562912 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240071] Re: BUG: soft lockup - CPU#0 stuck for 11s!
A Backport of the Fix would be very cool. At the moment XEN isn't really usable with 8.04, if you use the XEN image from the repos. -- BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/240071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259487] Re: xen virtual Machines and Dom0 crashes with BUG: soft lockup - CPU#0, CPU#1, CPU#2, CPU#3 stuck for 11s!
I have the Same problem XEN/Hardy/i386: dom0: Linux dom0-1 2.6.24-19-xen #1 SMP Thu Aug 21 03:09:02 UTC 2008 i686 GNU/Linux domU: Linux nmail. 2.6.24-19-xen #1 SMP Thu Aug 21 03:09:02 UTC 2008 i686 GNU/Linux crash every night .. kern.log:Aug 28 11:33:56 nmail kernel: [55657.356419] BUG: soft lockup - CPU#1 stuck for 11s! [courierpop3logi:29319] kern.log:Aug 28 11:34:08 nmail kernel: [55668.995642] BUG: soft lockup - CPU#1 stuck for 11s! [courierpop3logi:29319] kern.log:Aug 28 11:34:19 nmail kernel: [55680.677142] BUG: soft lockup - CPU#1 stuck for 11s! [courierpop3logi:29319] meanwhile i installed a xen several times, as well i reinstalled the domU's, i used 3 different HP servers (one brandnew), so it must be a problem with hardy. obviously the xen-kernel shipped with hardy is totally unusable for production. i have plenty other XEN Systems running - reliable - but not with hardy. -- xen virtual Machines and Dom0 crashes with BUG: soft lockup - CPU#0,CPU#1,CPU#2,CPU#3 stuck for 11s! https://bugs.launchpad.net/bugs/259487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259487] Re: xen virtual Machines and Dom0 crashes with BUG: soft lockup - CPU#0, CPU#1, CPU#2, CPU#3 stuck for 11s!
Additional Crash Info (domU): Aug 28 12:14:08 nmail kernel: [ 1109.970322] smtpd invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0 Aug 28 12:14:09 nmail kernel: [ 1109.970328] Pid: 9500, comm: smtpd Not tainted 2.6.24-19-xen #1 Aug 28 12:14:09 nmail kernel: [ 1109.970335] [c01606ca] oom_kill_process+0x10a/0x120 Aug 28 12:14:09 nmail kernel: [ 1109.970344] [c0160ac7] out_of_memory+0x167/0x1a0 Aug 28 12:14:09 nmail kernel: [ 1109.970348] [c016313c] __alloc_pages+0x35c/0x390 Aug 28 12:14:09 nmail kernel: [ 1109.970352] [c016528d] __do_page_cache_readahead+0x11d/0x250 Aug 28 12:14:09 nmail kernel: [ 1109.970355] [c015d370] sync_page+0x0/0x40 Aug 28 12:14:09 nmail kernel: [ 1109.970359] [c01657cc] do_page_cache_readahead+0x4c/0x70 Aug 28 12:14:09 nmail kernel: [ 1109.970362] [c015fbc4] filemap_fault+0x2f4/0x420 Aug 28 12:14:09 nmail kernel: [ 1109.970366] [c016b9cf] __do_fault+0x6f/0x6b0 Aug 28 12:14:09 nmail kernel: [ 1109.970372] [c0170c69] handle_mm_fault+0x249/0x1350 Aug 28 12:14:09 nmail kernel: [ 1109.970377] [c0162456] __pagevec_free+0x26/0x30 Aug 28 12:14:09 nmail kernel: [ 1109.970381] [c0329346] do_page_fault+0x366/0xe90 Aug 28 12:14:09 nmail kernel: [ 1109.970387] [c01165fb] check_pgt_cache+0x1b/0x20 Aug 28 12:14:09 nmail kernel: [ 1109.970391] [c0173667] unmap_region+0x107/0x120 Aug 28 12:14:09 nmail kernel: [ 1109.970395] [c0174250] do_munmap+0x180/0x1f0 Aug 28 12:14:09 nmail kernel: [ 1109.970398] [c0328fe0] do_page_fault+0x0/0xe90 Aug 28 12:14:09 nmail kernel: [ 1109.970401] [c0327c85] error_code+0x35/0x40 Aug 28 12:14:09 nmail kernel: [ 1109.970405] [c032] vcc_getsockopt+0xc0/0x170 Aug 28 12:14:09 nmail kernel: [ 1109.970409] === Aug 28 12:14:09 nmail kernel: [ 1109.970410] Mem-info: Aug 28 12:14:09 nmail kernel: [ 1109.970412] DMA per-cpu: Aug 28 12:14:09 nmail kernel: [ 1109.970414] CPU0: Hot: hi:0, btch: 1 usd: 0 Cold: hi:0, btch: 1 usd: 0 Aug 28 12:14:09 nmail kernel: [ 1109.970416] CPU1: Hot: hi:0, btch: 1 usd: 0 Cold: hi:0, btch: 1 usd: 0 Aug 28 12:14:09 nmail kernel: [ 1109.970418] Normal per-cpu: Aug 28 12:14:09 nmail kernel: [ 1109.970420] CPU0: Hot: hi: 186, btch: 31 usd: 96 Cold: hi: 62, btch: 15 usd: 57 Aug 28 12:14:09 nmail kernel: [ 1109.970423] CPU1: Hot: hi: 186, btch: 31 usd: 130 Cold: hi: 62, btch: 15 usd: 50 Aug 28 12:14:09 nmail kernel: [ 1109.970424] HighMem per-cpu: Aug 28 12:14:09 nmail kernel: [ 1109.970426] CPU0: Hot: hi: 90, btch: 15 usd: 16 Cold: hi: 30, btch: 7 usd: 23 Aug 28 12:14:09 nmail kernel: [ 1109.970428] CPU1: Hot: hi: 90, btch: 15 usd: 82 Cold: hi: 30, btch: 7 usd: 9 Aug 28 12:14:09 nmail kernel: [ 1109.970432] Active:141460 inactive:105254 dirty:0 writeback:2 unstable:0 Aug 28 12:14:09 nmail kernel: [ 1109.970433] free:4339 slab:2328 mapped:10 pagetables:1966 bounce:0 Aug 28 12:14:09 nmail kernel: [ 1109.970436] DMA free:4088kB min:72kB low:88kB high:108kB active:4056kB inactive:3180kB present:16256kB pages_scanned:12705 all_unreclaimable? yes Aug 28 12:14:09 nmail kernel: [ 1109.970438] lowmem_reserve[]: 0 706 1008 1008 Aug 28 12:14:09 nmail kernel: [ 1109.970442] Normal free:12976kB min:3364kB low:4204kB high:5044kB active:345628kB inactive:88kB present:723392kB pages_scanned:1494031 all_unreclaimable? yes Aug 28 12:14:09 nmail kernel: [ 1109.970444] lowmem_reserve[]: 0 0 2413 2413 Aug 28 12:14:09 nmail kernel: [ 1109.970448] HighMem free:292kB min:300kB low:656kB high:1016kB active:216156kB inactive:84448kB present:308864kB pages_scanned:1060951 all_unreclaimable? yes Aug 28 12:14:09 nmail kernel: [ 1109.970451] lowmem_reserve[]: 0 0 0 0 Aug 28 12:14:09 nmail kernel: [ 1109.970453] DMA: 0*4kB 1*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 4088kB Aug 28 12:14:09 nmail kernel: [ 1109.970460] Normal: 144*4kB 50*8kB 12*16kB 9*32kB 8*64kB 2*128kB 0*256kB 3*512kB 1*1024kB 2*2048kB 1*4096kB = 12976kB Aug 28 12:14:09 nmail kernel: [ 1109.970466] HighMem: 17*4kB 0*8kB 2*16kB 0*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 292kB Aug 28 12:14:09 nmail kernel: [ 1109.970474] Swap cache: add 528366, delete 528366, find 5029/5406, race 0+0 Aug 28 12:14:09 nmail kernel: [ 1109.970475] Free swap = 0kB Aug 28 12:14:09 nmail kernel: [ 1109.970477] Total swap = 2097144kB Aug 28 12:14:09 nmail kernel: [ 1109.970478] Free swap:0kB Aug 28 12:14:09 nmail kernel: [ 1109.973038] 264192 pages of RAM Aug 28 12:14:09 nmail kernel: [ 1109.973040] 77824 pages of HIGHMEM Aug 28 12:14:09 nmail kernel: [ 1109.973042] 3894 reserved pages Aug 28 12:14:09 nmail kernel: [ 1109.973043] 540 pages shared Aug 28 12:14:09 nmail kernel: [ 1109.973044] 0 pages swap cached Aug 28 12:14:09 nmail kernel: [ 1109.973045] 0 pages dirty Aug 28 12:14:09 nmail kernel: [ 1109.973046] 2 pages writeback Aug 28 12:14:09 nmail kernel: [ 1109.973047] 10 pages
[Bug 238549] Re: xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s!
See https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/259487 (duplicate i think). This is really a bad problem and needs to be addressed very very soon.. -- xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/238549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63439] Re: Core2Duo powerstepping doesn't work
I think we strongly depend on a stable BIOS from HP. -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63439] Re: Core2Duo powerstepping doesn't work
Hmm, i remove the psmouse module on halt, so in /etc/init.d/halt, so it's unloaded when shutting down or rebooting. when the system comes up again, it's loaded ofcoz. Bastian -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63439] Re: Core2Duo powerstepping doesn't work
Hello, Hibernation doesn't work at all for me - when i try to suspend to disk it's going down and immidiately coming up again in a strange unstable state. i'm still investigating a solution for it :( Bastian -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 63439] Re: Core2Duo powerstepping doesn't work
atlas95 wrote: Thanks you very much ... BUT! :) When I have reboot the first time after read you and do the command, powernowd work very well ;), but after restart again, this don't work again. I must remove battery and psu every time i reboot? thanks ... :) do you use bios F17? and, are you sure, that the psmouse module gets unloaded b4 rebooting? that's what made it working for me without removing all psu's. otherwise - if that doesn't work - removing the psu's should will work for sure - but sucks. anyways, i expect hp to release a bios with a proper working acpi soon. greetings, Bastian -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 63439] Re: Core2Duo powerstepping doesn't work
atlas95 wrote: Yes I use F17 bios ;) The hdd is more noisy than my old laptop rahh : the noise is not really my problem, but the power consumption of the hdd check the /etc/laptop-mode/laptop-mode.conf, set hdd settings to /dev/sda. and see if it gets better.. Bastian -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 63439] Re: Core2Duo powerstepping doesn't work
atlas95 wrote: I have problem with gnome power manager too, it didn't detect if i use batterie or power Could you help me please :o) OK. To get my nx9420 working perfectly under Linux (Ubuntu-Edgy) the following was required: - make sure you use Bios Version F17 from September 2006 - put a line with rmmod psmouse in /etc/init.d/halt - put following in /etc/init.d/powernowd right aber the shebang: echo 1833000 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo 1833000 /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq echo ondemand /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor now shut down your computer, remove all power sources (battery and psu) for some seconds, boot linux and have a working and updating acpi as wenn as freq scaling. the rmmod psmouse avoids, that after one reboot your notebook comes back in a kind of bad state, which makes 1.8ghz unable to be used as well as a stuck battery monitor. greetings, Bastian -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63439] Re: Core2Duo powerstepping doesn't work
I just found out sth which makes my CPU work with F17 on 1.83 Ghz: Add the following to a startupscript: echo 1833000 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo 1833000 /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq echo ondemand /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor it seems that you have to set the governer again after setting the scaling_max_freq. cpufreq-info output is: [EMAIL PROTECTED]:/usr/src/linux-2.6.19.1# cpufreq-info cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: centrino CPUs which need to switch frequency at the same time: 0 hardware limits: 1000 MHz - 1.83 GHz available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 1000 MHz and 1.83 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.83 GHz (asserted by call to hardware). analyzing CPU 1: driver: centrino CPUs which need to switch frequency at the same time: 1 hardware limits: 1000 MHz - 1.83 GHz available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 1000 MHz and 1.83 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.83 GHz (asserted by call to hardware). sincerly, Bastian -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63439] Re: Core2Duo powerstepping doesn't work
Hi, HP has just give out F17 Bios. It makes speedstepping_centrino work again, but it fails to get the processor beyond 1.33Ghz. [EMAIL PROTECTED]:~# cat /var/lib/acpi-support/*-* 68YAF Ver. F.17 Hewlett-Packard HP Compaq nx9420 (ES444ET#ABD) F.17 Interessting anomalie: [EMAIL PROTECTED]:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq 1833000 [EMAIL PROTECTED]:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1333000 [EMAIL PROTECTED]:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq [EMAIL PROTECTED]:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1333000 which means, that even if i manually try to put the scaling_max up to what the cpu would be capable off - it simply doesn't allow setting the max-scaling freq up to 1.8ghz. strange, too: [EMAIL PROTECTED]:~# cpufreq-info cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: centrino CPUs which need to switch frequency at the same time: 0 hardware limits: 1000 MHz - 1.83 GHz available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 1000 MHz and 1.33 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.33 GHz (asserted by call to hardware). analyzing CPU 1: driver: centrino CPUs which need to switch frequency at the same time: 1 hardware limits: 1000 MHz - 1.83 GHz available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 1000 MHz and 1.33 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.33 GHz (asserted by call to hardware). so long, Bastian -- Core2Duo powerstepping doesn't work https://launchpad.net/bugs/63439 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
