The referenced patch landed in 3.7, so let's assume that this bug is
fixed.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The patch will be included in v3.8 and applied back into v3.7 stable:
http://thread.gmane.org/gmane.linux.kernel/1397985
I'll mark this bug back to triaged for now. It would be great if you
can test once this patch lands and report back if it fixes this bug for
you.
Thanks again for the great
That's great news, Anders. I responded to the thread you posted in
comment #16 to see if this patch will be submitted for v3.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079534
Title:
[LENOVO
The bug seems config-dependent, since if I compile Ubuntu-3.7.0-3.9 with
defconfig, the resulting kernel can successfully suspend from the
initramfs, while linux-image-3.7.0-3-generic cannot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I started randomly hybridizing the working and failing .configs, and
bisected the problem down to this difference:
--- bad42012-11-27 07:52:28.535253255 -0500
+++ good6 2012-11-27 07:35:58.376369630 -0500
@@ -3850,6 +3850 @@
-CONFIG_LOCKUP_DETECTOR=y
-CONFIG_HARDLOCKUP_DETECTOR=y
-#
Thanks for testing and providing this information.
I see that CONFIG_LOCKUP_DETECTOR is enabled in Precise(12.04) and
Quantal(12.10) as well as Raring(13.04). Do you also see this bug on
those releases?
However, I do see that Raring is the only release that has
CONFIG_HARDLOCKUP_DETECTOR
I’m in the middle of a commit bisect now, and one of the suspicious commits is
the same one mentioned here:
http://thread.gmane.org/gmane.linux.kernel/1397985
which has a reply with a patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Confirmed that bcd951cf10f24e341defcd002c15a1f4eea13ddb is the first bad
commit, that tglx’s patch in the above LKML thread fixes it, and that
removing nmi_watchdog=0 from my kernel command line is a workaround
(oops).
--
You received this bug notification because you are a member of Ubuntu
Sure.
linux-image-3.6.0-030600-generic_3.6.0-030600.201211202050_amd64.deb FAILS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079534
Title:
[LENOVO 4313CTO] suspend/resume failure
To manage
I started a kernel bisect between upstream v3.6 and v3.7-rc1. The bisect will
require testing of about 10 - 12 kernels. I built the first test kernel,
which is up to commit:
24d7b40a60cf19008334bcbcbd98da374d4d9c64
This kernel is available from:
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
--
You received this bug
@Andres Kaseorg,
Yes the wont fix status was due to an error.
** Changed in: linux (Ubuntu)
Status: Won't Fix = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079534
Title:
I assume the “Won’t Fix” status is due to an error in the automated
script, can you please remove it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079534
Title:
[LENOVO 4313CTO] suspend/resume
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.7 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
I'd also like to perform a bisect to figure out what commit caused this
regression. It would be very helpful to know the earliest kernel where
the issue started happening as well as the latest kernel that did not
have this issue.
Can you test the following kernels and report back? We are looking
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Seems to be an upstream bug introduced somewhere between v3.6 and
v3.7-rc3:
linux-image-3.5.0-18-generic_3.5.0-18.29_amd64.deb works
linux-image-3.5.7-030507-generic_3.5.7-030507.201210130556_amd64.deb works
linux-image-3.6.0-030600-generic_3.6.0-030600.201209302035_amd64.deb works
linux-image-3.6.6-030606-generic_3.6.6-030606.201211050512_amd64.deb works
linux-image-3.7.0-030700rc1-generic_3.7.0-030700rc1.201210220602_amd64.deb
FAILS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
19 matches
Mail list logo
