From: Ricardo Galli <gallir@uib.es>
To: linux-kernel@vger.kernel.org
Subject: Issues with 2.4.20/2.4.21-rc1[-ac3] and 2.5.68 on a Dell laptop
Date: Tue, 29 Apr 2003 23:35:51 +0200 [thread overview]
Message-ID: <200304292335.51962.gallir@uib.es> (raw)
Hi Alan,
first of all, thanks for you -acX, it solved several issues in my Dell
X200, the inclusion of XFS is great, and dri/drm with xfree 4.3 works
perfectly with the i830M (thanks).
But there still several problems (with APM enabled, no framebuffer):
- With cpufreq enabled, the kernel hangs if you change the CPU speed
_after_ a suspend/resume via the old interface (/proc/sys/cpu/0/speed,
(also repeatable in a vanilla or -rc1 kernel)). It doesn't happen if my
governor program uses /proc/cpufreq instead. I saw this bug also with the
original cpufreq patch and also with 2.5.68.
- cat /proc/i8k produces a long kernel lock, everything gets locked for a
few seconds. If you are playing a music, you must restart the program in
order the get alsa sync'd again.
- After suspend/resume, the kernel hangs during a shutdown (just like the
infamous w98se shutdown bug :-), it happens after all processes have been
TERMed. Sometimes the screen goes white (it happens also with Marcelo
tree). I tried this with almost every different version and bios
workaround in APM kernel options. I also happens with 2.5.68.
- The kernel hangs/lock hard if IO-APIC is enabled and you try to change
the screen brightness (<Fn><[UP][DOWN]-Arrow>). It also happens with
2.5.68.
- ACPI doesn't see the battery, the shutdown buttons just turn down with
notifying the kernel, suspend doesn't work. Also seen with ACPI original
patches and 2.5.68.
- Only happens with -ac3 version: the poweroff button turns the machine
off inmediately, it doesn't wait for a few seconds, as previous versions.
Regards,
--
ricardo galli GPG id C8114D34
next reply other threads:[~2003-04-29 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 21:35 Ricardo Galli [this message]
[not found] <E19AcoY-0006Wj-00@cetus>
2003-04-30 6:46 ` Justin Pryzby
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=200304292335.51962.gallir@uib.es \
--to=gallir@uib.es \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®