Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

hardlocks in 8-CURRENT

2 views
Skip to first unread message

Matthias Apitz

unread,
Mar 8, 2010, 9:20:05 AM3/8/10
to freebsd...@freebsd.org

Hello,

If you go with your laptop to some meeting, you just take it with you and
normally not even the power-supply; when you return to your desk, normally
you put your laptop on the table, plug-in power and open the lid...

from time to time I encounter that the laptop after opening the lid is
just locked, i.e. hardlocked and does not even respond on ping from other
places; I did tests to see when it crashes, i.e. if it is based on the
movement, of WLAN AP re-connect or whatever; I now always first open it, work a
while across WLAN and then plug-in the power; the lock occurs only on
the plug-in of the power-supply;

any idea what to do next for debugging this? thanks

matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <gu...@unixarea.de> - w http://www.unixarea.de/
Solidarity with the imperialistic Israel? Not in my name!
�Solidaridad con el imperialismo de Israel? �No en mi nombre!

Matthias Apitz

unread,
Mar 9, 2010, 3:54:49 AM3/9/10
to Peter Jeremy, freebsd...@freebsd.org
El d�a Tuesday, March 09, 2010 a las 07:16:35PM +1100, Peter Jeremy escribi�:

> On 2010-Mar-08 15:20:05 +0100, Matthias Apitz <gu...@unixarea.de> wrote:
> >from time to time I encounter that the laptop after opening the lid is
> >just locked, i.e. hardlocked and does not even respond on ping from other
> >places; I did tests to see when it crashes, i.e. if it is based on the
> >movement, of WLAN AP re-connect or whatever; I now always first open it, work a
> >while across WLAN and then plug-in the power; the lock occurs only on
> >the plug-in of the power-supply;
> >
> >any idea what to do next for debugging this? thanks

Hello Peter,

Thanks for your reply;

>
> Firstly, 8-current means you're running a build more than 3 months old.

do be more exactly: it is a 8-CURRENT based on CVS checkout from end of
May 2009;

> Have you considered upgrading?

this is at the moment no option because it is my laptop to do real work
all day;

> When the lockup occurs, are you in X11 or on a VTY? If the latter, is
> there anything relevant on the console? Does the keyboard work at all
> (Caps-lock and/or Ctrl-Alt-ESC)?

When the lock occurs I'm in X11 (KDE 3.5.x); the only key which works is
pressing power-button for some seconds, i.e. full power-off;

> What (if any) power management are you running? Do you have acpi_throttle
> enabled - if so, you could try disabling it.

Is this to be done in rc.conf or via sysctl? I have nothing set about
acpi_throttle;

>
> Finally, some more details of your system would be handy.

$ kldstat
Id Refs Address Size Name
1 43 0xc0400000 cb20f8 kernel
2 1 0xc10b3000 1b7b8 snd_hda.ko
3 2 0xc10cf000 52b18 sound.ko
4 1 0xc1122000 b2ec umass.ko
5 1 0xc112e000 59b0 acpi_video.ko
6 1 0xc1134000 988964 nvidia.ko
7 3 0xc1abd000 2e404 linux.ko
8 1 0xc1aec000 42a4 atapicam.ko
9 1 0xc1af1000 3cc8 ubsa.ko
10 1 0xc1af5000 11d9c pwc.ko
11 1 0xc81cd000 8000 linprocfs.ko
12 1 0xc81fa000 37000 ipl.ko

What else would be handy?
Thanks for your reply in any case.

Peter Jeremy

unread,
Mar 9, 2010, 5:15:12 AM3/9/10
to Matthias Apitz, freebsd...@freebsd.org
On 2010-Mar-09 09:54:49 +0100, Matthias Apitz <gu...@unixarea.de> wrote:
>do be more exactly: it is a 8-CURRENT based on CVS checkout from end of
>May 2009;

OK.

>When the lock occurs I'm in X11 (KDE 3.5.x); the only key which works is
>pressing power-button for some seconds, i.e. full power-off;

Can you try switching to a VTY0 before connecting power and see if
anything shows up.

>> What (if any) power management are you running? Do you have acpi_throttle
>> enabled - if so, you could try disabling it.
>
>Is this to be done in rc.conf or via sysctl? I have nothing set about
>acpi_throttle;

acpi_throttle would be enabled in the kernel config or via kld.
Power management is enabled with something like the following in rc.conf:
powerd_enable="YES"
performance_cx_lowest="HIGH" # Online CPU idle state
performance_cpu_freq="HIGH" # Online CPU frequency
economy_cx_lowest="LOW" # Offline CPU idle state
economy_cpu_freq="LOW" # Offline CPU frequency

>What else would be handy?

Hardware details, output from sysctl's dev.cpu and hw.acpi, dmesg,
output from kenv. If possible, dev.cpu.*.freq just before it hangs (I
realise this may be difficult).

--
Peter Jeremy

Peter Jeremy

unread,
Mar 9, 2010, 3:16:35 AM3/9/10
to Matthias Apitz, freebsd...@freebsd.org
On 2010-Mar-08 15:20:05 +0100, Matthias Apitz <gu...@unixarea.de> wrote:
>from time to time I encounter that the laptop after opening the lid is
>just locked, i.e. hardlocked and does not even respond on ping from other
>places; I did tests to see when it crashes, i.e. if it is based on the
>movement, of WLAN AP re-connect or whatever; I now always first open it, work a
>while across WLAN and then plug-in the power; the lock occurs only on
>the plug-in of the power-supply;
>
>any idea what to do next for debugging this? thanks

Firstly, 8-current means you're running a build more than 3 months old.
Have you considered upgrading?

When the lockup occurs, are you in X11 or on a VTY? If the latter, is
there anything relevant on the console? Does the keyboard work at all
(Caps-lock and/or Ctrl-Alt-ESC)?

What (if any) power management are you running? Do you have acpi_throttle


enabled - if so, you could try disabling it.

Finally, some more details of your system would be handy.

--
Peter Jeremy

David Wolfskill

unread,
Mar 9, 2010, 11:33:43 AM3/9/10
to Matthias Apitz, freebsd...@freebsd.org
On Tue, Mar 09, 2010 at 09:54:49AM +0100, Matthias Apitz wrote:
> ...

> What else would be handy?
> ....

What type of video adaptor is in your laptop? (I have a Radeon in mine,
and have occasional lock-ups just trying to start X if I have DRI
enabled. Come to think of it, whether or not you have DRI enabled in
your xorg.conf might be relevant, as well. IIRC, it's generally enabled
by default.)

Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

Rui Paulo

unread,
Mar 11, 2010, 1:54:42 AM3/11/10
to Matthias Apitz, Peter Jeremy, freebsd...@freebsd.org
On 9 Mar 2010, at 17:54, Matthias Apitz wrote:

> El día Tuesday, March 09, 2010 a las 07:16:35PM +1100, Peter Jeremy
> escribió:

I think that it's not expected for CURRENT to be very stable and it's
more less expected that you are able to follow current because sooner
or later you'll have problems like the one you have. I suggest you
run STABLE.

That aside, hardlocks are hard to debug, specially while on X. My
first try would be to remove drivers one by one.

--
Rui Paulo

vol...@vwsoft.com

unread,
Mar 11, 2010, 4:24:27 PM3/11/10
to Matthias Apitz, freebsd...@freebsd.org
On 01/-10/63 20:59, Matthias Apitz wrote:
> Hello,
>
> If you go with your laptop to some meeting, you just take it with you and
> normally not even the power-supply; when you return to your desk, normally
> you put your laptop on the table, plug-in power and open the lid...
>
> from time to time I encounter that the laptop after opening the lid is
> just locked, i.e. hardlocked and does not even respond on ping from other
> places; I did tests to see when it crashes, i.e. if it is based on the
> movement, of WLAN AP re-connect or whatever; I now always first open it, work a
> while across WLAN and then plug-in the power; the lock occurs only on
> the plug-in of the power-supply;
>
> any idea what to do next for debugging this? thanks
>
> matthias

Matthias,

just a shot in the dark, but I bet keying "res" ENTER (w/o the quotes)
in while your system seems to be dead will give you 'back' (well, kind
of) your system. Can you try that the next time, please?

If that works (reboots your system) we can see if you're able to get a
core dump out of your box.

Volker

Matthias Apitz

unread,
Mar 23, 2010, 4:38:05 AM3/23/10
to vol...@vwsoft.com, freebsd...@freebsd.org

Some days ago I catched this (or better: I was catched by this) while
still in ASCII mode short after the re-boot. There was no message on the
screen and keying "res<ENTER>" did nothing, not even any char of "res"
was echoed.

matthas

Matthias Apitz

unread,
Apr 1, 2010, 3:47:22 AM4/1/10
to vol...@vwsoft.com, freebsd...@freebsd.org
El día Thursday, March 11, 2010 a las 10:24:27PM +0100, vol...@vwsoft.com escribió:

We can close this issue, it is not FreeBSD related. Today morning I
plugged in the power while the laptop was still in pre-boot menu to
choose between FreeBSD and Vista partition, and this menu was locked as
well and no other ways as power-cycle to bring it up again.

I will contact Dell.

0 new messages