From: Andrew Morton <akpm@osdl.org>
To: Miguelanxo Otero Salgueiro <miguelanxo@telefonica.net>
Cc: linux-kernel@vger.kernel.org, Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: 2.6.11: suspending laptop makes system randomly unstable
Date: Wed, 2 Mar 2005 13:43:42 -0800 [thread overview]
Message-ID: <20050302134342.4c9cc488.akpm@osdl.org> (raw)
In-Reply-To: <422618F0.3020508@telefonica.net>
Miguelanxo Otero Salgueiro <miguelanxo@telefonica.net> wrote:
>
> I just compiled 2.6.11 from a 2.6.10 configuration for a desktop machine
> (with kernel preemption activated).
> Doing a make oldconfig bring some new options. I selected the default
> value (for my system) for them, so I keep configuring "make great kernel
> lock preemtive" to true (complete kernel configuration follows).
>
> Apart from the ALPS touchpad thing (see "2.6.11: touchpad
> unresponsive"), the new kernel keeps:
>
> - Setting randomly "last battery full charge" to a huge value
> (example: 400 Ah when max battery capacity is 38 Ah) so I get random
> charging/discharging timing patterns
That's an ACPI problem, I assume?
> - Locking "softly" the system: for example, preventing new proceses
> from spawning. For example, if I suspend the laptop while in Xwindows,
> resuming will keep X but new proceses can't be started. Changing to a
> virtual console doesn't get past the login step, as a new shell can't be
> started.
Is there no oops trace?
Could you switch to a vc, hit alt-sysrq-t and reboot, see if you get an
all-task backtrace in the kernel logs and of so, send it?
> - Disabling/enabling double-clicks in the synaptic touchpad. Randomly.
> All of these symthoms are more or less randomly. As far as I can tell,
> everything is ok before suspending but does Random Nasty Things(tm)
> after coming out from suspension.
next prev parent reply other threads:[~2005-03-02 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 19:50 2.6.11: suspending laptop makes system randomly unstable Miguelanxo Otero Salgueiro
2005-03-02 21:43 ` Andrew Morton [this message]
2005-03-04 9:23 ` Romano Giannetti
2005-03-04 9:43 ` Andrew Morton
2005-03-03 8:13 ` Romano Giannetti
2005-03-04 14:11 ` Pavel Machek
2005-03-21 22:10 ` Andrew Morton
2005-03-22 9:39 ` Miguelanxo Otero Salgueiro
2005-03-22 9:55 ` Andrew Morton
2005-03-22 10:03 ` Arjan van de Ven
2005-03-22 10:19 ` Miguelanxo Otero Salgueiro
2005-03-22 19:11 ` touchpad dragging problem Peter Osterlund
2005-03-22 20:13 ` Miguelanxo Otero Salgueiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050302134342.4c9cc488.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miguelanxo@telefonica.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox