[opensuse] frequent hard locks on a hp laptop.
Hello, I am experiencing frequent and very annoying hard locks on my hp tx1000 series laptop.. few (~ 4) times a week. I have disabled all power management (when using it, the hard locks were even more frequent). And no, I have not blocked the ventilation. .. and the processor ventilation fan is not running at maximum speed when the hard locks occur. Is there any way to debug a problem like this? I suppose it will leave no trace into the log files..? Is there any other operating system that would be more stable on my laptop.. like vis..? no!, just kidding. ;) I am running 32-bit version of suse 10.3 and update it quite frequently. Regards, Sampsa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sampsa Riikonen wrote:
Hello,
I am experiencing frequent and very annoying hard locks on my hp tx1000 series laptop.. few (~ 4) times a week.
I have disabled all power management (when using it, the hard locks were even more frequent). And no, I have not blocked the ventilation. .. and the processor ventilation fan is not running at maximum speed when the hard locks occur.
Is there any way to debug a problem like this? I suppose it will leave no trace into the log files..? Is there any other operating system that would be more stable on my laptop.. like vis..? no!, just kidding. ;)
I am running 32-bit version of suse 10.3 and update it quite frequently.
Regards,
Sampsa
Yes you can debug it, but you have Not provided enough information. I don't know what a hp tx1000 has in it. What is the processor? What kernel parameters are you using to boot? (post /boot/grub/menu.lst) What video driver do you have installed? Any errors suggested by dmesg? Any errors captured in /var/log/messages? Running any specific app when it dies? Those would be good starters if you want a meaningful response. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 24 Apr 2008 09:39:37 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
Sampsa Riikonen wrote:
I am experiencing frequent and very annoying hard locks on my hp tx1000 series laptop.. few (~ 4) times a week.
I have disabled all power management (when using it, the hard locks were even more frequent). And no, I have not blocked the ventilation. .. and the processor ventilation fan is not running at maximum speed when the hard locks occur.
Is there any way to debug a problem like this? I suppose it will leave no trace into the log files..? Is there any other operating system that would be more stable on my laptop.. like vis..? no!, just kidding. ;)
I am running 32-bit version of suse 10.3 and update it quite frequently.
Yes you can debug it, but you have Not provided enough information. I don't know what a hp tx1000 has in it. What is the processor? What kernel parameters are you using to boot? (post /boot/grub/menu.lst) What video driver do you have installed? Any errors suggested by dmesg? Any errors captured in /var/log/messages? Running any specific app when it dies?
In addition, are the lockups related to the kernel or the GUI. The Display Manager (KDM, GDM, XDM ...) has control of the keyboard and mouse. Over the years I have witnessed many cases in Linux (SuSE, Red Hat, Commercial Unix ...) where the "lockup" is caused by the GUI (et. al.) where the OS runs fine. When the system locks up, are you able to ping the system? Can you try to log in with ssh (assuming you have an ssh daemon). It is also possible that the lockups are caused by the Nvidia graphics driver. You might want to boot with some or all of these kernel parameters to see if it changes anything: apm=off acpi=off noapic Also take a look at dmesg to see if you can spot anything out of the ordinary, such as a spurious interrupt. Note that "dmesg -c" will clear the dmesg buffer. You can do this prior to a reboot, so the next time you lock up, it will reflect messages back to the last reboot. -- -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
On Thu, 2008-04-24 at 09:39 -0500, David C. Rankin wrote:
Sampsa Riikonen wrote:
Hello,
I am experiencing frequent and very annoying hard locks on my hp tx1000 series laptop.. few (~ 4) times a week.
I have disabled all power management (when using it, the hard locks were even more frequent). And no, I have not blocked the ventilation. .. and the processor ventilation fan is not running at maximum speed when the hard locks occur.
Is there any way to debug a problem like this? I suppose it will leave no trace into the log files..? Is there any other operating system that would be more stable on my laptop.. like vis..? no!, just kidding. ;)
I am running 32-bit version of suse 10.3 and update it quite frequently.
Regards,
Sampsa
Yes you can debug it, but you have Not provided enough information. I don't know what a hp tx1000 has in it. What is the processor? What kernel parameters are you using to boot? (post /boot/grub/menu.lst) What video driver do you have installed? Any errors suggested by dmesg? Any errors captured in /var/log/messages? Running any specific app when it dies?
Those would be good starters if you want a meaningful response.
Thank you for the comments.. .. I just experienced another hard lock. It happened around 18:00 today, so I put the all the /var/log/messages from 17:00-18:00 and 18:00=> into the files www.iki.fi/sampsa.riikonen/1700.txt www.iki.fi/sampsa.riikonen/1800.txt .. to my newbie eyes, everything looks quite cryptic, but I think there is nothing suspicious? /boot/grub/menu.lst looks the following: ----------------------------------------------------------------- # Modified by YaST2. Last modification on Sun Feb 24 01:21:04 EET 2008 default 0 timeout 8 gfxmenu (hd0,5)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 - 2.6.22.17-0.1 root (hd0,5) kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/scsi-SATA_ST9160821AS_5MA6DMFC-part6 vga=0x317 resume=/dev/sda5 splash=silent showopts initrd /boot/initrd-2.6.22.17-0.1-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 - 2.6.22.17-0.1 root (hd0,5) kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/scsi-SATA_ST9160821AS_5MA6DMFC-part6 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /boot/initrd-2.6.22.17-0.1-default ---------------------------------------------------------------------- The hard locks do not happen when running any specific application.. they happen quite randomly.. although I think (maybe my imagination) that they have (sometimes) some correlation with the OpenOffice. HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09 I also put the dmesg output into file www.iki.fi/sampsa.riikonen/dmesg.txt Regards, Sampsa
-- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sampsa Riikonen wrote:
On Thu, 2008-04-24 at 09:39 -0500, David C. Rankin wrote:
Sampsa Riikonen wrote:
Hello,
I am experiencing frequent and very annoying hard locks on my hp tx1000 series laptop.. few (~ 4) times a week.
I have disabled all power management (when using it, the hard locks were even more frequent). And no, I have not blocked the ventilation. .. and the processor ventilation fan is not running at maximum speed when the hard locks occur.
Is there any way to debug a problem like this? I suppose it will leave no trace into the log files..? Is there any other operating system that would be more stable on my laptop.. like vis..? no!, just kidding. ;)
I am running 32-bit version of suse 10.3 and update it quite frequently.
Regards,
Sampsa
Yes you can debug it, but you have Not provided enough information. I don't know what a hp tx1000 has in it. What is the processor? What kernel parameters are you using to boot? (post /boot/grub/menu.lst) What video driver do you have installed? Any errors suggested by dmesg? Any errors captured in /var/log/messages? Running any specific app when it dies?
Those would be good starters if you want a meaningful response.
Thank you for the comments..
.. I just experienced another hard lock. It happened around 18:00 today, so I put the all the /var/log/messages from 17:00-18:00 and 18:00=> into the files
www.iki.fi/sampsa.riikonen/1700.txt
www.iki.fi/sampsa.riikonen/1800.txt
Nothing of significance captured. If this persists, it might be worth installing the mcechklog package to help capture the kernel reporting of Machine Check Events (MCE) before the time of death.
The hard locks do not happen when running any specific application.. they happen quite randomly.. although I think (maybe my imagination) that they have (sometimes) some correlation with the OpenOffice.
This usually screams RAM, have you run memtest86+ on your current Gig of RAM to confirm that the memory is 100% good?
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
I also put the dmesg output into file
www.iki.fi/sampsa.riikonen/dmesg.txt
There are a few hints to be gleaned from the dmesg output. Specifically: Nvidia board detected. Ignoring ACPI timer override. If you got timer trouble try acpi_use_timer_override What I would like to try passing a few kernel parameters on boot and see what effect it has on your system. When you get to the grub boot menu, type the following on the blank line: nohpet nolapic noapic apic=verbose acpi_use_time_override As you can see from the dmesg, there is s known timing issue with some of those chipsets and that could certainly be a cause of sporadic lockkups. The other simply force the irq handling to be done without as much automagix sharing of irq resources. Give that a try and report back with you next dmesg. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2008-04-27 at 03:14 -0500, David C. Rankin wrote:
Sampsa Riikonen wrote:
On Thu, 2008-04-24 at 09:39 -0500, David C. Rankin wrote:
Sampsa Riikonen wrote:
Hello,
I am experiencing frequent and very annoying hard locks on my hp tx1000 series laptop.. few (~ 4) times a week.
I have disabled all power management (when using it, the hard locks were even more frequent). And no, I have not blocked the ventilation. .. and the processor ventilation fan is not running at maximum speed when the hard locks occur.
Is there any way to debug a problem like this? I suppose it will leave no trace into the log files..? Is there any other operating system that would be more stable on my laptop.. like vis..? no!, just kidding. ;)
I am running 32-bit version of suse 10.3 and update it quite frequently.
Regards,
Sampsa
Yes you can debug it, but you have Not provided enough information. I don't know what a hp tx1000 has in it. What is the processor? What kernel parameters are you using to boot? (post /boot/grub/menu.lst) What video driver do you have installed? Any errors suggested by dmesg? Any errors captured in /var/log/messages? Running any specific app when it dies?
Those would be good starters if you want a meaningful response.
Thank you for the comments..
.. I just experienced another hard lock. It happened around 18:00 today, so I put the all the /var/log/messages from 17:00-18:00 and 18:00=> into the files
www.iki.fi/sampsa.riikonen/1700.txt
www.iki.fi/sampsa.riikonen/1800.txt
Nothing of significance captured. If this persists, it might be worth installing the mcechklog package to help capture the kernel reporting of Machine Check Events (MCE) before the time of death.
The hard locks do not happen when running any specific application.. they happen quite randomly.. although I think (maybe my imagination) that they have (sometimes) some correlation with the OpenOffice.
This usually screams RAM, have you run memtest86+ on your current Gig of RAM to confirm that the memory is 100% good?
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
I also put the dmesg output into file
www.iki.fi/sampsa.riikonen/dmesg.txt
There are a few hints to be gleaned from the dmesg output. Specifically:
Nvidia board detected. Ignoring ACPI timer override. If you got timer trouble try acpi_use_timer_override
What I would like to try passing a few kernel parameters on boot and see what effect it has on your system. When you get to the grub boot menu, type the following on the blank line:
nohpet nolapic noapic apic=verbose acpi_use_time_override
Dear David, I Experienced (another) lock few days ago.. Although it seems that after turning the hw accelereration off in OpenOffice, things are getting slightly better (fewer locks). Since I am degugging this "statistically", I don't want to type those grub parameters each time I boot my computer. Is there any way (config file, etc.?) to force those parameter automatically each time my laptop boots. .. I was looking in yast => bootloader (grub), but at first glance, I could not find any suitable line for typing those parameters in. Cheers, Sampsa
As you can see from the dmesg, there is s known timing issue with some of those chipsets and that could certainly be a cause of sporadic lockkups. The other simply force the irq handling to be done without as much automagix sharing of irq resources.
Give that a try and report back with you next dmesg.
-- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, May 5, 2008 at 1:56 AM, Sampsa Riikonen <sampsa.riikonen@iki.fi> wrote:
Since I am degugging this "statistically", I don't want to type those grub parameters each time I boot my computer. Is there any way (config file, etc.?) to force those parameter automatically each time my laptop boots. .. I was looking in yast => bootloader (grub), but at first glance, I could not find any suitable line for typing those parameters in.
/boot/grub/menu.lst Just hard code the parms you want. You should always leave a safe mode option in there incase you fat-finger the keyboard or something. You can also replicate any menu option that works, title it as you please, modify it to suit. thereby leave the original suse generated one alone. When you have one that works, just put it in the first position. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2008-05-05 at 11:14 -0700, John Andersen wrote:
On Mon, May 5, 2008 at 1:56 AM, Sampsa Riikonen <sampsa.riikonen@iki.fi> wrote:
Since I am degugging this "statistically", I don't want to type those grub parameters each time I boot my computer. Is there any way (config file, etc.?) to force those parameter automatically each time my laptop boots. .. I was looking in yast => bootloader (grub), but at first glance, I could not find any suitable line for typing those parameters in.
/boot/grub/menu.lst
Just hard code the parms you want. You should always leave a safe mode option in there incase you fat-finger the keyboard or something.
You can also replicate any menu option that works, title it as you please, modify it to suit. thereby leave the original suse generated one alone.
When you have one that works, just put it in the first position.
Here goes the summa summarum of the "frequent hard locks on a hp laptop" for my part.. First, following the advice of Carlos, I turned off the hw graphics acceleration in OpenOffice and it seemed that there were fewer hard locks.. although they did not completely disappear. Then I started using the following parameters in /boot/grub/menu.lst that David recommended: nohpet nolapic noapic apic=verbose acpi_use_time_override Since then I have not experienced a single hard lock. I have even started using KPowersave again. Everything works smoothly. Hooray! .. but I am sure, that, according to Murphy, after writing this message I will get a hard lock again. ;) Thanks to everyone. Cheers, Sampsa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sampsa Riikonen wrote:
On Mon, 2008-05-05 at 11:14 -0700, John Andersen wrote:
On Mon, May 5, 2008 at 1:56 AM, Sampsa Riikonen <sampsa.riikonen@iki.fi> wrote:
Since I am degugging this "statistically", I don't want to type those grub parameters each time I boot my computer. Is there any way (config file, etc.?) to force those parameter automatically each time my laptop boots. .. I was looking in yast => bootloader (grub), but at first glance, I could not find any suitable line for typing those parameters in. /boot/grub/menu.lst
Just hard code the parms you want. You should always leave a safe mode option in there incase you fat-finger the keyboard or something.
You can also replicate any menu option that works, title it as you please, modify it to suit. thereby leave the original suse generated one alone.
When you have one that works, just put it in the first position.
Here goes the summa summarum of the "frequent hard locks on a hp laptop" for my part..
First, following the advice of Carlos, I turned off the hw graphics acceleration in OpenOffice and it seemed that there were fewer hard locks.. although they did not completely disappear.
Then I started using the following parameters in /boot/grub/menu.lst that David recommended:
nohpet nolapic noapic apic=verbose acpi_use_time_override
Since then I have not experienced a single hard lock.
I have even started using KPowersave again. Everything works smoothly.
Hooray! .. but I am sure, that, according to Murphy, after writing this message I will get a hard lock again. ;)
Thanks to everyone.
Cheers,
Sampsa
Good to know! One addendum. You can remove the "acpi_use_time_override" boot parameter as it isn't being used. I had a typo. It should have been: acpi_use_timer_override ^^^^^ Glad to hear it is working for you now. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sampsa Riikonen wrote:
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
There is a bug in the 1xx.xx nvidia drivers that causes random lock-ups with dual core processors. Try an older driver or look here:- http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 for relevent threads. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 10 May 2008 05:55, Michael Ayers wrote:
Sampsa Riikonen wrote:
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
There is a bug in the 1xx.xx nvidia drivers that causes random lock-ups with dual core processors. Try an older driver or look here:- http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 for relevent threads.
It's got to be a narrow set of conditions than just "dual core processors," 'cause I'm running 169.12 and run fair amount of 3D software: Google Earth, Celestia, Stellarium and Second Life. SL crashes a lot, but I believe that's mostly 'cuase I always run release candidates and their quality varies from very unstable to pretty reliable (the current one being a bit of a mess). But the machine overall has been quite solid. Only when I overdo the overclocking have I had any stability problems. I've backed way off on that, these days, since I have to support other users on that machine.
Mike
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 10 May 2008 07:44, Randall R Schulz wrote:
On Saturday 10 May 2008 05:55, Michael Ayers wrote:
Sampsa Riikonen wrote:
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
There is a bug in the 1xx.xx nvidia drivers that causes random lock-ups with dual core processors. Try an older driver or look here:- http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 for relevent threads.
It's got to be a narrow set of conditions than just "dual core processors," 'cause I'm running 169.12 and run fair amount of 3D software: Google Earth, Celestia, Stellarium and Second Life. SL crashes a lot, but I believe that's mostly 'cuase I always run release candidates and their quality varies from very unstable to pretty reliable (the current one being a bit of a mess).
But the machine overall has been quite solid. Only when I overdo the overclocking have I had any stability problems. I've backed way off on that, these days, since I have to support other users on that machine.
And of course, I should have indicated: - Core2 Duo - openSUSE 10.3 - x11-video-nvidiaG01-169.12-0.1 - nvidia-gfxG01-kmp-bigsmp-169.12_2.6.22.17_0.1-0.1 - kernel-bigsmp-2.6.22.17-0.1 Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 10 May 2008 16:55:32 Randall R Schulz wrote:
On Saturday 10 May 2008 07:44, Randall R Schulz wrote:
On Saturday 10 May 2008 05:55, Michael Ayers wrote:
Sampsa Riikonen wrote:
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
There is a bug in the 1xx.xx nvidia drivers that causes random lock-ups with dual core processors. Try an older driver or look here:- http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 for relevent threads.
It's got to be a narrow set of conditions than just "dual core processors," 'cause I'm running 169.12 and run fair amount of 3D software: Google Earth, Celestia, Stellarium and Second Life. SL crashes a lot, but I believe that's mostly 'cuase I always run release candidates and their quality varies from very unstable to pretty reliable (the current one being a bit of a mess).
But the machine overall has been quite solid. Only when I overdo the overclocking have I had any stability problems. I've backed way off on that, these days, since I have to support other users on that machine.
And of course, I should have indicated:
- Core2 Duo - openSUSE 10.3 - x11-video-nvidiaG01-169.12-0.1 - nvidia-gfxG01-kmp-bigsmp-169.12_2.6.22.17_0.1-0.1 - kernel-bigsmp-2.6.22.17-0.1
Randall Schulz
Really, truly, honestly, dual core processors and the 1xx.xx drivers cause lockups. I spent hours trolling through the nvnews site and found that there are work arounds such as "maxcpus=1" or adding "options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x2222"" to /etc/modprobe.d/nvidia which works for me with 171.06,also when I went back to 100.14.23 all problems stopped. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-04-26 at 18:25 +0300, Sampsa Riikonen wrote: ...
The hard locks do not happen when running any specific application.. they happen quite randomly.. although I think (maybe my imagination) that they have (sometimes) some correlation with the OpenOffice.
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
OOo and nvidia... Try this: in OOo, tools, options, OOo, View: disable both 3D and use HW accel. If that doesn't help, you could also try to "downgrade" to the open nvidia driver (you loose hw accel, but it is more stable). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIFFIktTMYHG2NR9URAtoJAJ9JyUMP7cspDs8LHIeBU1mVZRMJnACdH9UZ O3sYP+FLjIvovMHKcI8HKcU= =1+oq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The Saturday 2008-04-26 at 18:25 +0300, Sampsa Riikonen wrote:
...
The hard locks do not happen when running any specific application.. they happen quite randomly.. although I think (maybe my imagination) that they have (sometimes) some correlation with the OpenOffice.
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
OOo and nvidia... Try this: in OOo, tools, options, OOo, View: disable both 3D and use HW accel.
If that doesn't help, you could also try to "downgrade" to the open nvidia driver (you loose hw accel, but it is more stable).
-- Cheers, Carlos E. R. How is the progress with your hard locks? Following this thread because I have since some time also hard locks but with me on my desktop. First I thought it had something to do with my underpowered and old hardware. This thread gave me at least an unknown cli command dmesg -c in order to have fresh information about the machine. My hard locks happen when I use kmail to write email. In the middle of the writing a hard lock will often occur. More often than I like ;(. Another cause of my hard locks happen when I scroll with the mouse in Mozilla Firefox. That has changed my habit of using the mouse for scrolling. With
On Sunday 27 April 2008, Carlos E. R. wrote: page down and up no hard locks occur up to now. I know that my hardware is at the low end (noname Pentium II 400mHz with 378M memory running 10.3 and KDE) but I really like to proof myself that hardware is no big issue with Linux. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2008-04-29 at 08:57 +0700, Constant Brouerius van Nidek wrote:
The Saturday 2008-04-26 at 18:25 +0300, Sampsa Riikonen wrote:
...
The hard locks do not happen when running any specific application.. they happen quite randomly.. although I think (maybe my imagination) that they have (sometimes) some correlation with the OpenOffice.
HP tx1000 (I think mine is actually "tx3200") has a double core AMD Turion 64-bit processor. Video card is nvidia and the driver version is 169.09
OOo and nvidia... Try this: in OOo, tools, options, OOo, View: disable both 3D and use HW accel.
If that doesn't help, you could also try to "downgrade" to the open nvidia driver (you loose hw accel, but it is more stable).
-- Cheers, Carlos E. R. How is the progress with your hard locks? Following this thread because I have since some time also hard locks but with me on my desktop. First I thought it had something to do with my underpowered and old hardware. This thread gave me at least an unknown cli command dmesg -c in order to have fresh information about the machine. My hard locks happen when I use kmail to write email. In the middle of the writing a hard lock will often occur. More often than I like ;(. Another cause of my hard locks happen when I scroll with the mouse in Mozilla Firefox. That has changed my habit of using the mouse for scrolling. With
On Sunday 27 April 2008, Carlos E. R. wrote: page down and up no hard locks occur up to now. I know that my hardware is at the low end (noname Pentium II 400mHz with 378M memory running 10.3 and KDE) but I really like to proof myself that hardware is no big issue with Linux.
I am experimenting according to the "minimum effort principle". For the moment I have disabled graphics hw acceleration in OO as suggested and for few days have not experienced any hard locks. If (and when) they occur I will try out the other suggestions. Btw, do you have an nvidia graphics card and did you experience these hard locks with an older suse version? Are you running 64-bit? .Sampsa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 29 April 2008, Sampsa Riikonen wrote:
On Tue, 2008-04-29 at 08:57 +0700, Constant Brouerius van Nidek wrote:
On Sunday 27 April 2008, Carlos E. R. wrote:
The Saturday 2008-04-26 at 18:25 +0300, Sampsa Riikonen wrote:
My hard locks happen when I use kmail to write email. In the middle of the writing a hard lock will often occur. More often than I like ;(. Another cause of my hard locks happen when I scroll with the mouse in Mozilla Firefox. That has changed my habit of using the mouse for scrolling. With page down and up no hard locks occur up to now. I know that my hardware is at the low end (noname Pentium II 400mHz with 378M memory running 10.3 and KDE) but I really like to proof myself that hardware is no big issue with Linux.
I am experimenting according to the "minimum effort principle". For the moment I have disabled graphics hw acceleration in OO as suggested and for few days have not experienced any hard locks. If (and when) they occur I will try out the other suggestions.
Btw, do you have an nvidia graphics card and did you experience these hard locks with an older suse version? Are you running 64-bit?
.Sampsa
I am using a Nvidia Geforce 5500 on a 32 bit system. Up to 10.1 I hade no problems with the same hardware. And I had all versions from somewhere version 6.2 :) Will see what the graphics hw acceleration thingy will change. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 29 April 2008 2:36 am Sampsa Riikonen wrote:
I am experimenting according to the "minimum effort principle".
Sampsa, I have two Dell Inspiron laptops, an 1150 and a 1510,,, one is 32 bit, one is 64 bit. I had a random lockup on both til I played with the apm, apci and powersave stuff. I killed the powersave thing and turned apm off, and acpi=force in /boot/grub/menu.lst. In my Runlevel selections I disabled acpid and powersaved. After all that, no more hangs. Dont know it it will help you but worth a try. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 29 April 2008, Richard wrote:
On Tuesday 29 April 2008 2:36 am Sampsa Riikonen wrote:
I am experimenting according to the "minimum effort principle".
Sampsa, I have two Dell Inspiron laptops, an 1150 and a 1510,,, one is 32 bit, one is 64 bit. I had a random lockup on both til I played with the apm, apci and powersave stuff. I killed the powersave thing and turned apm off, and acpi=force in /boot/grub/menu.lst. In my Runlevel selections I disabled acpid and powersaved. After all that, no more hangs. Dont know it it will help you but worth a try.
Dear Richard, Sounds good. I have alraedy acpi=force as a standard input on this older desktop but will have a look at powersaved and acpid. Grub will see an extra apm=off Have no idea what these commands do anyhow but will google a bit at wiki ;) Constant -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Carlos E. R. -
Constant Brouerius van Nidek -
David C. Rankin -
Jerry Feldman -
John Andersen -
Michael Ayers -
Randall R Schulz -
Richard -
Sampsa Riikonen