Mailinglist Archive: opensuse (2532 mails)

< Previous Next >
Re: [opensuse] frequent hard locks on a hp laptop.
  • From: Sampsa Riikonen <sampsa.riikonen@xxxxxx>
  • Date: Mon, 05 May 2008 11:56:15 +0300
  • Message-id: <1209977775.4225.8.camel@xxxxxxxxxxxxxxxxxx>

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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >