From: Peter Clifton <pcjc2@cam.ac.uk>
To: trenn@suse.de
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: HP Compaq nc6320
Date: Thu, 12 Oct 2006 17:39:30 +0100 [thread overview]
Message-ID: <1160671170.13557.25.camel@pcjc2lap> (raw)
In-Reply-To: <1160671089.2096.225.camel@queen.suse.de>
[snip]
> I got several reports that compiling psmouse as module and unload it
> explicitly on shutdown helps to fix things on newer HPs.
>
> E.g. this report:
> About the fan and battery issue, there are three workaround:
> - Turn off the machine and quit battery, Place the battery again.
> - Next time you turn on the machine, turn it off during post.
> - "modprobe -r psmouse" (after compiling psmouse as a module) before
> shutdown the machine.
> Next time you turn on the machine, battery status is working. Not sure
> about the fans...
My fans seemed to work ok most of the time before, it was the battery
status which hung, and the speedstep would never go to full speed.
Everything is happy with Ubuntu's kernel 2.6.17-10 and when unloading
psmouse as part of the shutdown and reboot scripts.
I did dig though psmouse a little, but being a non-expert, couldn't see
anything odd.
It could be the synaptics driver part I guess, as most people have
laptops.
It could be that psmouse keeps a serial driver of some sort alive, or a
bus active. Perhaps it is still receiving and processing interrupts as
the bios tries to reboot? Does someone need to open a kernel bug for
this, and where should it go?
Regards
Peter Clifton.
next prev parent reply other threads:[~2006-10-12 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 22:08 HP Compaq nc6320 Peter Clifton
2006-10-11 22:17 ` Peter Clifton
2006-10-11 23:53 ` Peter Clifton
2006-10-12 0:08 ` Peter Clifton
2006-10-12 14:53 ` Rafael J. Wysocki
2006-10-12 16:38 ` Thomas Renninger
2006-10-12 16:39 ` Peter Clifton [this message]
2006-10-12 21:08 ` Rafael J. Wysocki
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=1160671170.13557.25.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=trenn@suse.de \
--cc=vojtech@suse.cz \
/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