** Changed in: acpi
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75174
Title:
runaway kacpi_notify
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
I just got this on an up-to-date 10.10, on an Alienware R17x (intel
quad-core) when the AC power went out for 2 seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/75174
Title:
runaway kacpi_noti
Still a problem with Ubuntu 10.10 with fglrx 10.11 too. Was the same in
9.10 with fglrx >= 10.1 and 10.04 with all versions. kacpi_notify
becomes unresponsive after going from AC to battery and after not more
than minute the computer freezes.
--
You received this bug notification because you are
Still a problem with Kubutu 9.10 on my Dual Opteron 64-bit system.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Brett Alton wrote:
> This still effects my HP Pavillion 503n and a200n using Ubuntu 8.04.4.
>
> 'kacpid' and 'kacpi_notify' need to be killed using 'sudo killall' while
> grub needs to load the kernel with the 'acpi=off' and 'apm=off' flags.
In my case, this turned out to be a motherboard bios b
This still effects my HP Pavillion 503n and a200n using Ubuntu 8.04.4.
'kacpid' and 'kacpi_notify' need to be killed using 'sudo killall' while
grub needs to load the kernel with the 'acpi=off' and 'apm=off' flags.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this b
Not really fixed in Intrepid. I'm still seeing it with kernel
2.6.27-9-generic running on a Dell D630.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This appears to be fixed in latest intrepid.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Jos and Christian, I think this is a new bug. The symptoms are the same
with kacpid or kacpi_notify consuming all CPU but it appears after
resuming from suspend (to ram or disk) and not while running the system.
It is also interesting that at all three of us have Dell laptops. I
filed a new report
I use hardy with Kernel and have the problem with both kernels linux-
image-2.6.24-19-386 and linux-image-2.6.24-19-generic.
The problem happens sporadically but mostly when some process is using
the harddisk or the CPU "more than just a bit". The problem also
disappears sporadically - to come bac
i have this bug too. after resume kacpi_notify consumes all cpu :(
in hardy suspend/resume works fine, but after dist-upgrade to intrepid i have
this bug. i use a dell d620 core duo with 32bit.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification becau
I have this bug every time I resume from suspend on a dell latitude D820
(core duo). Hardy on same laptop did not have this problem. Intrepid
current 2.6.27-3 kernel.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubunt
This bug happened for me on an Acer desktop machine: Veriton 7200 (mobo
S81M, even after upgrading to latest bios revision: R01-F3).
The machine has Debian on its hard drive, and Debian's 2.6.18-6-686 doesn't
have the problem.
Debian's 2.6.24-etchnhalf.1-686 _does_ have the problem. It's very re
** Changed in: acpi
Status: Incomplete => Invalid
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
** Changed in: acpi
Status: Confirmed => Incomplete
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
** Changed in: acpi
Status: In Progress => Confirmed
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
** Changed in: acpi
Status: Confirmed => In Progress
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
** Changed in: acpi
Status: Incomplete => Confirmed
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
A really quick workaround is to issue:
sudo killall klogd
This will stop the hard drive grinding (if you experience that), but
that still doesn't fix the infinite loop (most likely) in kacpi_notify
which hogs a lot of CPU power. You can renice it to priority 19 to make
it not as bad.
If you don
** Changed in: acpi (upstream)
Status: Confirmed => Incomplete
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
There are two workarounds:
1. Disable acpi. Add acpi=off to the kernel line in /boot/grub/menu.lst
2. Downgrade the kernel. I only suffer the bug in 2.6.20-16-generic, but NOT in
2.6.17-10-generic.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification
Just one question: why is this "undecided" are you not going to fix
that?? Under edgy everything was alright but with this bug feisty starts
to get totally unuseable. Try to download a torrent and watch a movie:
kacpi_notify gets 98% the cpu heats and the system makes a security
shutdown :( really
** Changed in: acpi (upstream)
Status: Unknown => Confirmed
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I have exactly the same behavior as the one described by Akkana Peck.
My system is a "Compaq Presario 2805 EA" laptop running Feisty. The bug was
also present with Dapper or Edgy.
The only workaround I have is to manually set the CPU Frequency to its lowest
value (1.2GHz instead of 1.4GHz) usin
Akkan, I sat the watch to #6944 because I thought that was the real bug.
But it seems like #6944 and #8274 are duplicates and #6944 is rejected
for some reason, so I changed the watch to #8274. The only workaround I
know of is to give the kernel the argument acpi=off when it boots which
disables po
** Changed in: acpi (upstream)
Status: Unknown => Invalid
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
Does anyone know of a workaround, when the bug is already there? I.e.,
when acpi is hogging my CPU, how do I fix that without rebooting the
computer?
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is
See also kernel bug http://bugzilla.kernel.org/show_bug.cgi?id=8274 (how
do I set a remote bug watch on that?)
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
** Bug watch added: Linux Kernel Bug Tracker #6944
http://bugzilla.kernel.org/show_bug.cgi?id=6944
** Also affects: acpi (upstream) via
http://bugzilla.kernel.org/show_bug.cgi?id=6944
Importance: Unknown
Status: Unknown
** Changed in: acpi (Ubuntu)
Status: New => Confirmed
I have the same problem, but I'm using a stationary computer.
Compiling emacs seems to be what triggered it. Even after the heavy task
is done, acpi is still making the whole computer sluggish and almost
unusable.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bu
This problem has gotten worse with feisty, because kacpid and
kacpid_notify aren't killable. I tried getting rid of /etc/init.d/acpid,
and that stopped kacpi_notify from running, but kacpid was still there
and still runs out of control whenever I run a long cpu-intensive
process like a long compile
I've had it (35% acpid) when heavily loaded, but just now I got it by
accidentally clicking the undock button on my docking station.
dmesg-c says:
[91067.276000] ACPI Exception (pci_bind-0299): AE_NOT_FOUND, Unable to get data
from device DCKS [20060707]
[91067.276000] ACPI: undocking
Needless
Turning off dynamic CPUFreq seems to have eliminated the lockups for me
for the moment , I just set it to performance or powersave using
powersave.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
More data: It isn't logging in that causes it for me, but starting
kpilot. If kpilot doesn't start, kacpid doesn't start using all my CPU.
If kpilot starts, then kacpid uses all my CPU.
--
runaway kacpi_notify
https://bugs.launchpad.net/bugs/75174
You received this bug notification because you
For me it is kacpid that is a runaway using 95% of a cpu and
kacpi_notify uses only 5%. It seems to happen even if I don't run
anything CPU intensive--just loggign in to KDE starts it. I guess I
should try logging in to a console and see what happens.
--
runaway kacpi_notify
https://bugs.launch
I have just observed this with a fresh Feisty install on a Sun Java
Workstation (w1100z).
I started a remote scp transfer to my desktop system and the desktop
appeared to lock up. I ended up killing my X session and discovering
that kapci_notify was consuming half of the CPU resources.
--
runaw
i have the same problem on my latitude notebook. the process
kacpi_notify take 99% of the cpu. the problem happens when the notebook
is running for a long time and the temperature is staying high.
--
runaway kacpi_notify
https://launchpad.net/bugs/75174
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Answering my own plea: it looks like killing acpid before starting
anything CPU intensive prevents the runaway kacpi_notify process. At
least, I made it through a complete gimp build, which is a lot farther
than I ever got when acpid was running.
I'd welcome suggestions as to how to pin this down
38 matches
Mail list logo
