** Changed in: linux
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/334644
Title:
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
To manage
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)
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/334644
Title:
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
--
ubuntu-bugs mailing
I had this issue resolved for me quite a while ago. I thought for some
reason intuitivenipple closed this. Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/334644
Title:
[MSI MS-7374]
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/334644
Title:
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
It's not working on 6100 chip
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/334644
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
Upstream now has a patch to fix the resume issue [PATCH] pci: apply
nv_msi_ht_cap_quirk on resume too originally posted at:
http://lkml.org/lkml/2009/7/8/32.
It isn't in upstream git yet but is so trivial we should have no issues
in using it
--
[MSI MS-7374] suspend/resume failure [non-free:
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/334644
You received this bug notification because you are a
Suspend to disk is still a nightmare. It takes about 1 minute (to turn
off). Resuming, well, I cannot enter into my bios so something worked?
*but* I do not see anything about a resume image, I see a bunch of
orphaned files get cleaned up, then back to the KDM screen. So, resume
isn't working (not
I finally got suspend to ram and suspend to disk working. For suspend to
ram, read above. for suspend to disk, I needed to add yet another kernel
parameter resume=/path/to/swap. Now. Just like above, the kickoff
options under the leave tab do *not* call pm-suspend and pm-hibernate
respectively and
I thought I chime in with some more goodies thats making my experience
on Jaunty a whole lot better when it comes to this stuff. The
application powerdevil just didn't want to work for me out of the box.
I did manage to get it working (somewhat) by installing cpufrequtils.
This definitely got When
The attached kern.log doesn't reveal any obvious suspend-to-RAM
attempts.
What sleep module is in use?
grep SLEEP_MODULE /etc/pm/config.d/00sleep_module
The log does however contain several hibernation cycles (suspend-to-
disk), such as:
Feb 28 10:46:24 box kernel: [ 229.128539] PM: Creating
This is what a true suspend-to-RAM looks like:
Suspend...
[12964.851509] PM: Preparing system for mem sleep
[12964.851512] Freezing user space processes ... (elapsed 0.00 seconds) done.
[12964.857033] Freezing remaining freezable tasks ... (elapsed 0.01 seconds)
done.
[12964.867857] PM:
I managed to save this dmesg *after* a failed resume. in it (I believe
around line 1283, you'll see my sda disk failure). I am attaching the
dmesg info to this bug.
** Attachment added: dmesg.2b
http://launchpadlibrarian.net/23313604/dmesg.2b
--
[MSI MS-7374] suspend/resume failure
attaching the result of $ ls -l /dev/disk/by-path/*
** Attachment added: res
http://launchpadlibrarian.net/23314273/res
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/334644
You received this bug notification because you are a member of Ubuntu
The problem appears to be that during suspend the Interrupt for the
Nvidia MCP78S (PCI 00:09.0) isn't being disabled, nor re-enabled on
resume (other AHCI-managed controllers are - see 07.00.0).
Start-up:
[1.364523] ahci :00:09.0: version 3.0
[1.364948] ahci :00:09.0: PCI INT A
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
Status: Incomplete = Confirmed
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/334644
You received this bug notification because you are a member of Ubuntu
Bugs,
I think I may have solved my suspend/resume woes with a short-term
solution. I mean short-term because although this works for me
(suspending to ram/resuming from ram) I have to add a kernel parameter
to grub def options and I've only tested it twice (both resumes 100%). I
simply added pci=nomsi
** Bug watch added: Linux Kernel Bug Tracker #12542
http://bugzilla.kernel.org/show_bug.cgi?id=12542
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12542
Importance: Unknown
Status: Unknown
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
** Changed in: linux
Status: Unknown = In Progress
--
[MSI MS-7374] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/334644
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Please do a shutdown/restart, suspend/resume test. Assuming the resume
fails restart afresh and then attach /var/log/kern.log which should
capture more information than the dmesg logs from the original report.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
I rebooted. logged in. suspended to ram. pretty quick shutdown. started
up and it took about 1 minute staring at a black screen until the
desktop appeared. everything looked great. the drive was dead (read
only). needed to cold reboot the system. uploaded kern.log.
** Attachment added:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/23136364/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/23136365/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23136366/Dependencies.txt
**
23 matches
Mail list logo
