No problem still in 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
[Fujitsu LIFEBOOK AH530] BUG: soft lockup - CPU#0 stuck for 22s!
To manage notifications about this bug go to
The soft lockup bug has manifested itself in the
Linux 3.2.0-126-generic-pae
kernel just one time with opening lid resume - on
4 18 17
I cannot, with this machine, now, troubleshoot it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
The bug has not happened since the last reported incident. This old
machine, additionally, does not feel like troubleshooting it.
Linux GPD 3.2.0-116-generic-pae #158
Dec 12 2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
The soft lockup resume/suspend bug has returned.
Linux 3.2.0-110-generic-pae #151
Sep 25 2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
[Fujitsu LIFEBOOK AH530] BUG: soft lockup
Suspend/Resume from the drop down menu or closing the lid then using the
power button or opening the lid is working very well since the
installation of the linux 3.2.0-68-generic-pae kernel.
Suspend/Resume invoked too often can wear the computer out, thus I have
not done suspend/resume extensively
For the last several months, the suspend/resume bug has only occurred
when resuming from suspend by opening the lid of the computer. It has
not occurred when resuming using the power button.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Tags removed: kernel-bug-exists-upstream needs-upstream-testing
** Tags added: kernel-fixed-upstream-v3.12-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
[Fujitsu LIFEBOOK AH
I did not fix this bug. It makes little sense that I should be asked to
do the SRU process for this bug. It was fixed upstream by whomever fixes
bugs of the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I was instructed to test the latest development release (14.04) to
determine whether a bug (soft lockup bug), which still exists in 12.04
LTS, is in the development release and/or the mainline kernel for the
development release.
My tests suggest that the bug is fixed in 14.04 (the development
rele
Suspended/resumed 540 times. The soft lockup bug did not occur.
Upgrade install 12.04 to 14.04 (Latest development release):
S/R 250 times (204
using dropdown menu, 46 with lid).
Installed updates. Bugs compelled a reinstall...
Installed
The latest development release (13.10) is now installed.
Thus far, after 35 suspend/resumes (25 using the drop down menu and 10 using
lid closure), suspend/resume is working just fine. That's not a thorough test
yet, after my experience with 12.04.
However, internet connectivity (wireless and et
Linux 3.2.0-54-generic-pae
Installed: 9 28 13
soft lockup:
Oct 7, 2013CPU#0
Oct 19, 2013CPU#0
Oct 21, 2013CPU#0
Oct 25, 2013CPU#0
Replaced by 3.2.0-55 10 27 13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Linux 3.2.0-53-generic-pae
Installed: 9 7 13
soft lockup:
Sep 27, 2013 CPU#0
Replaced by 3.2.0-54 9 28 13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
[Fujitsu LIFEBOOK AH530
Linux 3.2.0-52-generic-pae
Installed: 8 21 13
soft lockup
Aug 26, 2013 CPU#0
Aug 30, 2013 CPU#0
Sep 6, 2013 Password screen locked up on resume - mouse cursur and text
cursur would not move.
Replaced by 3.2.0-53 9 7 13
Still going to test.
--
You received this bug notification beca
kernel linux 3.2.0-49-generic-pae
Installed: 7 25 13
soft lockup:
July 25, 2013CPU#0
July 26, 2013CPU#0
July 29, 2013CPU#0
July 30, 2013CPU#0
Aug 1, 2013 CPU#0
Aug 7, 2013 CPU#0
Aug 9, 2013 CPU#0
Aug 10, 2013 CPU#0
Aug 12, 2013 CPU#0
Replaced 8 21 13 by ker
3.2.0-48-generic-pae:
soft lockup:
1June 15
2June 15
3July 7
4July 14
5July 16
6July 17
Fixing recursive fault but reboot is needed!:
June 23
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
3.2.0-45-generic-pae - soft lockup on cpu #0 on June 2 and June 5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
BUG: soft lockup - CPU#0 stuck for 22s!
To manage notifications about
The 3.2.0-44-generic-pae kernel had a soft lockup on cpu #0 on May 25 (as
already stated above) and
another kind of crash on resume which created a trace which ended "Fixing
recursive fault but reboot is needed!" on May 26. Most of the trace could not
be seen. Pressing the power button and reboo
Thus far the 38, 40, and 42 kernels did not crash with a soft or hard
lockup.
The 3.2.0-43-generic-pae had soft lockups on cpu #0 on May 18 and May 24
2013. The 3.2.0-44-generic-pae had a soft lockup on cpu #0 just now on
May 25 2013.
--
You received this bug notification because you are a membe
The crash did not happen at all with the 3.2.0-40-generic-pae kernel.
It has begun again with the 3.2.0-41-generic-pae kernel.
There was a hard LOCKUP: Watchdog detected hard LOCKUP on cpu 3: on May 6
2013.
There was a soft lockup on cpu#0 on May 9 2013.
The
"dpm_run_callback(): acpi_button_r
Soft lockup bug did not occur at all with the 3.2.0-38-generic-pae kernel.
It has begun again with the recent update to the 3.2.0-39-generic-pae kernel.
It has happened three times in the last week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Soft lockup bug has not occured in more than a month.
Above mentioned messages happen every once in a while.
Present kernel is Linux 3.2.0-38-generic-pae.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Soft lockup bug occurs about twice a month.
Above mentioned messages happen every once in a while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
BUG: soft lockup - CPU#0 stuck for 22s
soft lockup bug has not occured in almost one month. HARD lockup occured about
three weeks ago once.
Beginning about 2 weeks ago the
"dpm_run_callback(): acpi_button_resume+0x0/0x21 returns -19
PM: Device PNP0C0D:00 failed to resume: error -19"
messages no longer appear upon resume. In fact no m
The soft lockup bug is happening once every 2 weeks now.
The other suspend-resume problems occur about 9 percent of the time.
Most of the time the "returns -19" and "...resume: error -19" messages flash
briefly and then the password insertion box appears and suspend proceeds
normally.
--
You re
The "BUG: soft lockup-CPU#0 stuck for 22s!" event has diminished in
frequency. It happens about 25 percent of the time. The other resume
failures are also noticeably less frequent although they are still
happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Attachment added: "This is the latest syslog after the last "BUG: soft
lockup - CPU#0 stuck for 22s!" crash happened."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1036456/+attachment/3299786/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bu
Tried "resume-trace" debugging procedure for finding buggy drivers with:
sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend".
It hasn't crashed this way. There were no "hash matches" lines in dmesg.txt.
There's not much else to say.
--
You received this bug notification because you are a
Upstream kernel has been uninstalled.
Before uninstall the "Soft Lockup" bug occured twice:
once it was CPU#0
once it was CPU#3
(and the HARD lockup for CPU#2 previously mentioned)
Additionally suspend invoked from the drop down menu with the upstream kernal
installed would display two randomly al
There was no "needs-upstream-testing" tag.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
BUG: soft lockup - CPU#0 stuck for 22s!
To manage notifications about this bug go to:
https:/
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
BUG: soft lockup - CPU#0
One more thing: the Computer Janitor lists the v3.6 image extra package
to be removed (it is unsupported). It does not list the other three v3.6
packages. Could this be a problem with the installation?
Is there anything more to testing the upstream kernel? Please advise.
This is brand new stuff. P
The 4 v3.6-rc1-quantal packages have been installed using:
sudo dpkg -i Downloads/*.deb
(with a capital "D" - not lowercase "d")
instead of:
sudo dpkg -i *.deb
"The BUG: soft lockup - CPU#0 stuck for 22s!" error occurred once in 52
suspend/resumes performed since the install.
There are, howev
It should be added that the above mentioned "bug" still happens about
60% of the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036456
Title:
BUG: soft lockup - CPU#0 stuck for 22s!
To manage
New information:
About 10% of the time suspend resumes to a blank screen with blinking cursur
that does not respond.
The mouse cursur moves but does not affect anything.
Reboot with power button is the only solution.
About 1% of the time the cursur doesn't blink.
About 5% of the time the above me
The 4 v3.5 packages have been downloaded.
sudo dpkg -i *.deb does not install them.
Message:
dpkg: error processing *.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
Please advise.
--
You received this bug notification because you ar
** Attachment added: "Including syslog which shows messages that appear."
https://bugs.launchpad.net/bugs/1036456/+attachment/3260184/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036
Public bug reported:
60% of the time computer will not resume from suspend when lid is opened.
Display begins with ACPI errors and Device PNP0C0D:00 errors and
then a cycle of text after the "BUG: soft lockup - CPU#0 stuck for 22s!" error.
Additionally,
yelp process consumed 100% of each of the
38 matches
Mail list logo
