For anyone finding this the problem has re-appeared with Ubuntu 20.04 on a
Fujitsu Lifebook A544 after upgrading to BIOS version 1.24 (or 1.25). It shows
itself as workers kacpid and acpid_notify hogging most of a core. the fix (or
workaround?) is to run
sudo sh -c 'echo "disable" > /sys/firmwa
@yonsy your problem is not caused by this bug, which completely prevents
booting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814555
Title:
Ubuntu boot failure. 4.18.0-14 boot stalls
It is not still open, it is marked as invalid.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/887793
Title:
[HP 6710b] Kworker constantly taking about 100% CPU
Status in linux package i
I believe the bug should not be affecting more people as it is not
present in current kernels. Also 17.10 goes end of life in a few weeks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/17
@Danny Vilca the repair method described in the bug description should
fix it. If not then ask for help on the Ubuntu Users mailing list.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734
The release notes for the 17.10 installer [1] linked to from the Desktop
download page [2] still have this issue in the Known Issues section at
the bottom. Possibly the release notes need to be updated accordingly
[1]
https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes?_ga=2.209410322.1075533256.
I can confirm that updating to BIOS 1.20 also fixes it for me (with SSD
drive). Strange that the problem only exhibited itself with certain
kernel versions. So it seems Joseph and myself have wasted our time
bisecting the kernel. Sorry Joseph. I learnt a lot in the process
however. I will clos
** Attachment added: "dmesg on re-boot after failure with current kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504420/+attachment/4525280/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
** Attachment added: "/proc/acpi/wakeup from current kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504420/+attachment/4525281/+files/wakeup.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
After several weeks running with the suspend command
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
with both the latest mainline kernel I was unable to make it fail. I reverted
to the current kernel and it still refused to fail. I then resorted to just
using pm_suspend (with c
Is anything happening on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
Status in Linux:
Unknow
Tested with mainline kernel 4.3.0 rc5 and got the same failure, though
it seemed to take longer before it failed. Likely just the statistics
working themselves out though.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.3.0-rc5
** Changed in: linux (Ubuntu)
Status:
** Description changed:
On resume the screens (laptop + external) showed windows as before
suspend but the machine was completely unresponsive.
+
+ This happens around 1 in 10 times I suspend. I am suspending using pm-
+ suspend or via the cog > Suspend.
ProblemType: KernelOops
Distr
Public bug reported:
On resume the screens (laptop + external) showed windows as before
suspend but the machine was completely unresponsive.
ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-14-generic 4.2.0-14.16
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491467/+attachment/4486870/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1
4.3-rc1 kernel (linux-
image-4.3.0-040300rc1-generic_4.3.0-040300rc1.201509160642_amd64.deb)
also exhibits the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwor
I think 4.3-rc1 kernel build has failed, at least there are no images
there. I will test it when they appear.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consu
OK. In case it is of interest I have determined that the problem was
originally fixed between mainline kernels 3.13.11.11-trusty and
3.14-rc1-trusty, before being reintroduced in 4.0.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Have I missed something or has it not arrived yet?
I have gone back and confirmed that afb5abc262e962089e was good and
0dc553652102c55a4 is bad, just in case I had made a mistake.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
0dc553652102c55a43eb1ab52e2049e478469f53
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509092055_amd64.deb
is BAD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
71ed848fd791bc0b53a1b7a04f29eb9e994c7cbb
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509091541_amd64.deb
is BAD
Only one, or two, to go :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
It may be of interest that another A544 running kernel 3.13 exhibits the
problem. It went away some time between then and 3.19 and came back in
4.0. The other machine does not have an SSD so that may not be a
factor, though comments in the upstream bug suggested that it was a
factor. Of course t
I don't think you have actually, there's nowt there :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
S
30fc8d138e9123f374a3c3867e7c7c5cd4004941
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081948_amd64.deb
is Bad
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
afb5abc262e962089ef2d7c2bbf71bb6f53a2a78
/home/colinl/Downloads/linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Can you confirm the repo please, I get
$ git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/
Cloning into 'linux'...
fatal: remote error: Repository '~ubuntu-kernel/ubuntu/+source/linux' not found.
Alternatively is it fundamentally the same (as far as this exercise is
concerned
875edad528cf29b382e82837e652e997aec16c49
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
As a matter of interest, which repository have you cloned from?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kworker consuming cpu due to GPE13 interrupt storm on Fujits
7b1ee96f074cc931a2c226b33607fe7a74d5cba3
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509050242_amd64.deb
is BAD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
ba4877b9ca51f80b5d30f304a46762f0509e1635
linux-image-3.19.0-031900-generic_3.19.0-031900.201509041408_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
d3f180ea1a44aecba1b0dab2a253428e77f906bf
linux-image-3.19.0-031900-generic_3.19.0-031900.201509032049_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
8cc748aa76c921d8834ef00f762f31acd2c93aa8
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031637_amd64.deb
is BAD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwor
b3d6524ff7956c5a898d51a18eaecb62a60a2b84
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031452_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
718749d56214aa97015fe01b76b6d6dd0c171796
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031253_amd64.deb
is GOOD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
kwo
c5ce28df0e7c01a1de23c36ebdefcd803f2b6cbb
linux-image-3.19.0-031900-generic_3.19.0-031900.201509022146_amd64.deb
is GOOD :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491467
Title:
02f1f2170d2831b3233e91091c60a66622f29e82
http://kernel.ubuntu.com/~jsalisbury/lp1491467
linux-image-3.19.0-031900-generic_3.19.0-031900.201509021605_amd64.deb
is BAD
that is it shows the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
I can confirm that
v3.19 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ does
not show the problem
4.0-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/
and
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/
both do show the problem
--
You received
By bisecting the kernel I have determined that the problem is not seen
on the last Ubuntu 3.19 kernel 3.19.8-vivid but is seen on the first
4.0 kernel that will build using fakeroot debian/rules binary-headers
binary-generic, which is
commit 636cdd7b2930ca2cdaf90eedd04fdb9fc7a8d5ec
Author: Stefan
Public bug reported:
On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker
takes 100% of one core of CPU due to GPE13 interrupt storm
See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071
The bug can be identified by repeatedly running
cat /sys/firmware/acpi/interrupt
*** This bug is a duplicate of bug 1459571 ***
https://bugs.launchpad.net/bugs/1459571
** This bug has been marked a duplicate of bug 1459571
Keyboard shortcuts stop working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
When running vivid booted with systemd kernel, shutdown consistently
takes around 90 seconds. With the normal kernel it is about 15 seconds.
In the log, shutdown started (from the cog) at 13:50:20, Mar 6th. The
purple Ubuntu screen with dots appears after a few seconds and
@Sander under what circumstances are you seeing that? I see a similar
message running stock Vivid on Fujitsu A544, but only if I close the lid
(for suspend) immediately after booting. It does not suspend
immediately, but if lid is left down it does suspend a couple of minutes
later and the page_f
Is this definitely a kernel problem? The same thing happened a few
Ubuntu versions ago and then I thought it was due to a decision in
upstream gnome somewhere that a laptop with external monitor should not
suspend when lid is closed, but that eventually got reverted, either
upstream or in Ubuntu,
Bug still present in kernel 4.0-rc1-vivid
** Tags removed: apport-bug
** Tags added: apport kernel-bug-exists-upstream-bug
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
Since update to Vivid, laptop does not suspend on lid close if an external
monitor is connected. The external monitor blanks briefly and then resumes.
It suspends ok using the menu and does suspend on lid close if the external
monitor is not connected.
On Utopic it suspende
@Christopher, no I can't I am afraid. The machine is now running 14.04 and the
problem is no longer seen. Even if I could, is work still being done to fix
non-critical Unity 2d bugs?
Possibly it is still affecting one of the other affected users.
--
You received this bug notification because
As noted in duplicate bug #1372967 a workaround appears to be to add boot
options
i8042.notimeout i8042.nomux
According to that report, however, this is only temporary, though it is working
ok fo me so far.
--
You received this bug notification because you are a member of Kernel
Packages, which
Present on Utopic release candidate. Kernel 3.16.0-23 64 bit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1372967
Title:
Touchpad not working and not recognized
Status in “linux” pa
@Davide for the future click on the yellow pen marker by Tags at the
bottom of the description. I have added the tag.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of
Christopher, this is no longer giving me a problem as bug 806032 has
been fixed. However I have checked with Trusty (kernel 3.12.0-7 32 bit)
and the problem described here does still exist. The bug is therefore
not invalid, but from my point of view it does not need fixing. I don't
know what the
This bug has been fixed, the 13.10 kernel should support this device
without a workaround. Anyone still seeing a problem should report a new
bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
51 matches
Mail list logo
