Feedback on the Dell Precision M6500

Asked by Nick Rudnick on 2011-04-13

SOS...

You wrote (http://www.ubuntu.com/certification/hardware/201004-5601):
"A special image of Ubuntu is available via the computer manufacturer designed for this specific computer. It takes advantage of hardware features for these systems and may include proprietary software and codecs. Please contact the computer manufacturer for access to that specific Ubuntu operating system version."

Having a Dell Precision M6500 now, I just had to find out that my Dell pro support doesn't know anything about this -- meanwhile, I was supplied with a link to an ISO named ubuntu-10.10-i386-dell_A00.iso, which actually is 32 bit(!) and failed at installation.

At the standard installation of Ubuntu, there are problems like failing hibernation. So my hopes lie the 64bit 10.10 ISO mentioned by you.

Who is your the at Dell? Can you help me? Or is the page obsolete or invalid?

Thank you very much in advance, Nick

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu-Certification Edit question
Assignee:
No assignee Edit question
Last query:
2011-04-15
Last reply:
2011-05-01

Hi Nick,

Did you by the system with Ubuntu installed, or did it have something else. Either way, it's interesting you managed to get an actual image from them. We can perhaps check whether that is the image that the system was certified with. If it was than we'll need to figure out why it's not installing.

The page saying that the system is certified is not obsolete or void.

Brendan Donegan suggests this article as an answer to your question:
FAQ #1523: “Where can I find a Pre-install/Manufacturer image”.

Nick Rudnick (nick-rudnick) said : #3

Hi Brendan,

The link I was given by Dell is:

http://linux.dell.com/files/ubuntu/.

It contains only on 10.10 ISO:

http://support.dell.com/support/downloads/download.aspx?c=us&cs=08W&l=en&s=bsdv&releaseid=R284592&SystemID=LAT2120&servicetag=&os=WN104&osl=en&deviceid=26290&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=0&libid=58&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=421648
 ,

which is 32 bit, while you reported a 64 bit version.

My Notebook has 7 preinstalled, but I have two disks, so I could hang out
the first and boot from the second.

Thanks a lot, Nick

2011/4/13 Brendan Donegan <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Status: Open => Answered
>
> Brendan Donegan proposed the following answer:
> Hi Nick,
>
> Did you by the system with Ubuntu installed, or did it have something
> else. Either way, it's interesting you managed to get an actual image
> from them. We can perhaps check whether that is the image that the
> system was certified with. If it was than we'll need to figure out why
> it's not installing.
>
> The page saying that the system is certified is not obsolete or void.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Hi Nick,

What the FAQ is basically saying is that the machine was certified with a custom image that was created for Dell by Canonical. They would usually pre-install this image and it might be they only do this in some markets. The link you have provided is not for this image, so they have misinterpreted your request.

Would you be willing to try the latest 11.04 beta to see how that works? By this stage the fixes that were in Dells special image should have made it into the stock Ubuntu release.

Thanks,

Victor Tuson Palau (vtuson) said : #5

Hi Nick,

To add to what Brendan says, our test of the M6500 with the Natty image shows that it works fine. I would strongly encourage you to try it:
http://www.ubuntu.com/testing/natty/beta

Clearly there is always the possibility that the one you have has different components to hours, but I think is worth a try either way

Thanks,

Victor

Nick Rudnick (nick-rudnick) said : #6

Hi Victor,

[?]... Natty was what I tried first! But it was Xubuntu -- having tried quite
a lot after this I am not completely sure whether I *might* have missed
*Ubuntu Natty*, so I will give it a try again... thanks for the hint.

The most exciting question for me at the moment: Did you succeed in using
suspend to disk/RAM? If yes, with a Nvidia Quadro FX 3800M or similar?

This is the point, where I am stuck at the moment with the installation.

Thanks a lot for your interest, Nick

2011/4/13 Victor Tuson Palau <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Victor Tuson Palau proposed the following answer:
> Hi Nick,
>
> To add to what Brendan says, our test of the M6500 with the Natty image
> shows that it works fine. I would strongly encourage you to try it:
> http://www.ubuntu.com/testing/natty/beta
>
> Clearly there is always the possibility that the one you have has
> different components to hours, but I think is worth a try either way
>
> Thanks,
>
> Victor
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=4
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Well, that's just your problem there. We certified even the pre-install system with a ATI FirePro M7740. So even if you got the pre-install image it still may not work - and Natty still may not work.

Victor Tuson Palau (vtuson) said : #8

Hi,

Suspends work fine, but the system that we are testing has ATI Technologies Inc M97 GL [ATI FirePro M7740] graphics card.

Victor Tuson Palau (vtuson) said : #9

Nick,

Did you try installing the Nvidia driver from the "additional drivers" utility?

Nick Rudnick (nick-rudnick) said : #10

Yes, Victor,

and its presence at calling hibernate leads to a

   Some modules failed to unload: nvidia

warning, though I cannot say at the moment whether this causes the problem.

Cheers, Nick

2011/4/13 Victor Tuson Palau <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Victor Tuson Palau proposed the following answer:
> Nick,
>
> Did you try installing the Nvidia driver from the "additional drivers"
> utility?
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=8
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Victor Tuson Palau (vtuson) said : #11

we have not certified that model , so not much we can help you with really.

Nick Rudnick (nick-rudnick) said : #12

Hi Victor,

you refer to the Nvidia Quadro FX 3800M when you say you have not certified
that model?

Having about 10 years of experience with Linux and being literate with C/C++
-- would you encourage me to get such a certification of the FX3800 done
myself, once it turns out necessary? Could I eventually expect support from
Nvidia in this case?

Cheers, Nick

2011/4/13 Victor Tuson Palau <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Status: Open => Answered
>
> Victor Tuson Palau proposed the following answer:
> we have not certified that model , so not much we can help you with
> really.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=10
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Hi Nick,

The NVidia vs ATI graphics is the most obvious difference, but there may be others. I would still recommend you try Natty before continuing with anything else, as it may work.

Thanks,

Nick Rudnick (nick-rudnick) said : #14

Hi Brendan,

thanks for the recommendation -- what I did is the following:

I installed Ubuntu Natty with a 20GB swap partition on the second drive,
then I hang out the proprietary Nvidia graphics driver.

As a result, the nvidia related message does not show up again -- the
overall behaviour, however, stayed the same.

Hibernate all the time throws a warning, maybe it is more important than I
originally thought:

    hibernate:Warning: Tuxonice binary signature file not found.

The -v 3 version is:
= 8< =======================================
# hibernate -v 3
hibernate:Warning: Tuxonice binary signature file not found.
hibernate: Trying method in suspend2.conf...
hibernate: Trying method in disk.conf...
hibernate: Trying method in ususpend-disk.conf...
hibernate: Including configuration from common.conf
hibernate: [01] Executing CheckLastResume ...
hibernate: [01] Executing CheckRunlevel ...
hibernate: [01] Executing LockFileGet ...
hibernate: [01] Executing NewKernelFileCheck ...
hibernate: [10] Executing EnsureUSuspendCapable ...
hibernate: [11] Executing XHacksSuspendHook1 ...
hibernate: [59] Executing RemountXFSBootRO ...
hibernate: [89] Executing SaveKernelModprobe ...
Saved /proc/sys/kernel/modprobe is /sbin/modprobe
hibernate: [91] Executing ModulesUnloadBlacklist ...
Unloading blacklisted modules listed /etc/hibernate/blacklisted-modules
Module version for ipw2100 is 2
Module version for ipw2200 is 2
Module version for snd_bt_sco is
Module version for ndiswrapper is 0
Unloading blacklisted module mac80211 (and dependencies)
Unloading iwlagn ...
Removing modules with rmmod.
Unloading iwlcore ...
Unloading mac80211 ...
Unloading blacklisted module uvcvideo (and dependencies)
Unloading uvcvideo ...
hibernate: [95] Executing XHacksSuspendHook2 ...
xhacks: changing console from 1 to 15
hibernate: [98] Executing CheckRunlevel ...
hibernate: [99] Executing DoUSuspend ...
hibernate: Running /usr/sbin/s2disk ...
hibernate: [90] Executing ModulesLoad ...
Loading module iwlagn (from auto)...
Loading module iwlcore (from auto)...
Loading module mac80211 (from auto)...
Loading module uvcvideo (from auto)...
hibernate: [89] Executing RestoreKernelModprobe ...
hibernate: [85] Executing XHacksResumeHook2 ...
xhacks: changing console back to 1
hibernate: [70] Executing ClockRestore ...
hibernate: [59] Executing RemountXFSBootRW ...
hibernate: [11] Executing XHacksResumeHook1 ...
hibernate: [01] Executing NoteLastResume ...
hibernate: [01] Executing LockFilePut ...
= 8< =======================================

Is there additional information I could give which might be interesting?

Thanks a lot for your interest, Nick

2011/4/13 Brendan Donegan <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Status: Open => Answered
>
> Brendan Donegan proposed the following answer:
> Hi Nick,
>
> The NVidia vs ATI graphics is the most obvious difference, but there may
> be others. I would still recommend you try Natty before continuing with
> anything else, as it may work.
>
> Thanks,
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=12
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Daniel Manrique (roadmr) said : #15

Nick,

Can you confirm whether suspend to RAM works? instead of "hibernate" choose "suspend".

Hibernation requires writing the contents of memory to a swap file and shutting down the system altogether, and is somewhat sensitive to disk/partition configuration issues. The error message you show suggests a configuration problem, rather than an actual hardware incompatibility.

If suspend to RAM works fine, it would mean that the underlying hardware support is essentially working fine, and perhaps some tweaking of the configuration is necessary to get hibernate to work.

In any case, I'd appreciate if you could check and report on whether suspend to RAM works.

Thanks!

Nick Rudnick (nick-rudnick) said : #16

I am sorry, Daniel,

but it is up to me to thank you ;-))

Suspend from the desktop menu leads to no action (there is a screen lock
afterwards), from the user terminal it makes the terminal hang up, and from
the terminal as root it kills the root session, letting the terminal return
to the normal user session.

Is there anything more I can do?

Cheers, Nick

2011/4/13 Daniel Manrique <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Status: Open => Needs information
>
> Daniel Manrique requested for more information:
> Nick,
>
> Can you confirm whether suspend to RAM works? instead of "hibernate"
> choose "suspend".
>
> Hibernation requires writing the contents of memory to a swap file and
> shutting down the system altogether, and is somewhat sensitive to
> disk/partition configuration issues. The error message you show suggests
> a configuration problem, rather than an actual hardware incompatibility.
>
> If suspend to RAM works fine, it would mean that the underlying hardware
> support is essentially working fine, and perhaps some tweaking of the
> configuration is necessary to get hibernate to work.
>
> In any case, I'd appreciate if you could check and report on whether
> suspend to RAM works.
>
> Thanks!
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Daniel Manrique (roadmr) said : #17

Hi Nick,

The behavior you're seeing indeed suggests inability to enter any kind of suspension mode (as in, the suspend process gets started and then interrupted because a hardware driver didn't enter suspend mode - I'm guessing it's the nvidia driver). That's when you get left in a locked screen again, it means the system preparing to suspend by locking the screen, then failing in one of the suspend steps, and resuming everything the way it was.

You could look at /var/log/syslog and track the suspend process, you'll probably see an error along the lines of "failed to suspend" for a particular driver.

It looks like a case of your system's actual hardware being different from that in the sample system that was certified. Unfortunately, as Dell "reuses" model numbers for systems with potentially different specs, there's no way to determine that from the model number alone. See this FAQ:

https://answers.launchpad.net/ubuntu-certification/+faq/1536

I apologize for the confusion, but the conclusion here appears to be that, even though it shares a model number with a certified system, your particular computer is not exactly the same, thus it can't actually be considered "certified". Work is being done to make this situation clearer.

I would encourage you to submit a bug report, from your Natty installation, with the behavior you're seeing (if possible, use the command "apport-bug linux" as this appears to be a suspend/resume problem and involves kernel drivers so it's a good starting point). This is probably the best starting point to continue this in a way that could eventually solve the problem you're having.

Thanks again!

- Daniel

Nick Rudnick (nick-rudnick) said : #18

Hi Daniel,

:) I think I might have a first trace: Might USB3 an issue??

/var/log/syslog gives,

doing suspend,
= 8< =================================
Apr 13 21:00:56 weg kernel: [14359.768920] PM: Syncing filesystems ... done.
Apr 13 21:00:56 weg kernel: [14359.780597] PM: Preparing system for mem
sleep
Apr 13 21:00:56 weg kernel: [14359.780843] Freezing user space processes ...
(elapsed 0.01 seconds) done.
Apr 13 21:00:56 weg kernel: [14359.794113] Freezing remaining freezable
tasks ... (elapsed 0.02 seconds) done.
Apr 13 21:00:56 weg kernel: [14359.814119] PM: Entering mem sleep
Apr 13 21:00:56 weg kernel: [14359.814133] Suspending console(s) (use
no_console_suspend to debug)
Apr 13 21:00:56 weg kernel: [14359.923994] PM: suspend of drv:ieee80211
dev:phy5 complete after 109.689 msecs
Apr 13 21:00:56 weg kernel: [14360.043854] PM: suspend of drv:psmouse
dev:serio2 complete after 119.895 msecs
Apr 13 21:00:56 weg kernel: [14360.043993] whci-hcd 0000:0d:00.0-1:
wusbhc_rh_suspend (ffff8803f837b800 [ffff8803f837b800]) UNIMPLEMENTED
Apr 13 21:00:56 weg kernel: [14360.044032] pm_op(): usb_dev_suspend+0x0/0x20
returns -38
Apr 13 21:00:56 weg kernel: [14360.044036] PM: Device usb3 failed to suspend
async: error -38
Apr 13 21:00:56 weg kernel: [14360.064081] PM: Some devices failed to
suspend
Apr 13 21:00:56 weg kernel: [14360.064247] hub 3-0:1.0: activate --> -22
Apr 13 21:00:56 weg kernel: [14360.213820] PM: resume of drv:pcmcia_socket
dev:pcmcia_socket0 complete after 149.770 msecs
Apr 13 21:00:56 weg kernel: [14360.213979] PM: resume of devices complete
after 149.955 msecs
Apr 13 21:00:56 weg kernel: [14360.214079] PM: resume devices took 0.150
seconds
Apr 13 21:00:56 weg kernel: [14360.214091] PM: Finishing wakeup.
Apr 13 21:00:56 weg kernel: [14360.214092] Restarting tasks ... done.
= 8< =================================

doing hibernate,
= 8< =================================
Apr 13 20:51:01 weg kernel: [13765.039818] whci-hcd 0000:0d:00.0-1:
wusbhc_rh_suspend (ffff8803f837b800 [ffff8803f837b800]) UNIMPLEMENTED
Apr 13 20:51:01 weg kernel: [13765.039846] pm_op(): usb_dev_freeze+0x0/0x20
returns -38
Apr 13 20:51:01 weg kernel: [13765.039851] PM: Device usb3 failed to freeze
async: error -38
Apr 13 20:51:01 weg kernel: [13765.110952] hub 3-0:1.0: activate --> -22
Apr 13 20:51:01 weg kernel: [13765.259891] PM: restore of drv:pcmcia_socket
dev:pcmcia_socket0 complete after 149.067 msecs
Apr 13 20:51:01 weg kernel: [13765.259992] PM: restore of devices complete
after 149.194 msecs
Apr 13 20:51:01 weg kernel: [13765.260204] snapshot_ioctl: ioctl '4004330c'
is deprecated and will be removed soon, update your suspend-to-disk
utilities
Apr 13 20:51:01 weg kernel: [13765.260206] Restarting tasks ... done.
= 8< =================================

Thank you very much for your involvement,

    Nick

2011/4/13 Daniel Manrique <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Status: Open => Answered
>
> Daniel Manrique proposed the following answer:
> Hi Nick,
>
> The behavior you're seeing indeed suggests inability to enter any kind
> of suspension mode (as in, the suspend process gets started and then
> interrupted because a hardware driver didn't enter suspend mode - I'm
> guessing it's the nvidia driver). That's when you get left in a locked
> screen again, it means the system preparing to suspend by locking the
> screen, then failing in one of the suspend steps, and resuming
> everything the way it was.
>
> You could look at /var/log/syslog and track the suspend process, you'll
> probably see an error along the lines of "failed to suspend" for a
> particular driver.
>
> It looks like a case of your system's actual hardware being different
> from that in the sample system that was certified. Unfortunately, as
> Dell "reuses" model numbers for systems with potentially different
> specs, there's no way to determine that from the model number alone. See
> this FAQ:
>
> https://answers.launchpad.net/ubuntu-certification/+faq/1536
>
> I apologize for the confusion, but the conclusion here appears to be
> that, even though it shares a model number with a certified system, your
> particular computer is not exactly the same, thus it can't actually be
> considered "certified". Work is being done to make this situation
> clearer.
>
> I would encourage you to submit a bug report, from your Natty
> installation, with the behavior you're seeing (if possible, use the
> command "apport-bug linux" as this appears to be a suspend/resume
> problem and involves kernel drivers so it's a good starting point). This
> is probably the best starting point to continue this in a way that could
> eventually solve the problem you're having.
>
> Thanks again!
>
> - Daniel
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=16
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Daniel Manrique (roadmr) said : #19

Hi Nick,

That's great, and it turns out there are (or have been, it was supposed to be fixed) problems with suspend/hibernate and USB3.

Could you please take a look at these bug reports and see if the workarounds suggested in their comment sections (mainly removing xhci module before trying to suspend) help with your problem?

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998 (check comment #28 in this bug for a quick, temporary way to disable the module and test whether it helps you).

https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/562484

Nick Rudnick (nick-rudnick) said : #20

[?][?][?]...

Sorry... I fell asleep... just an unintended effect of hibernate...

suspend works, just by adding the file

/etc/pm/config.d/unload_modules

with content
= 8< =========================
SUSPEND_MODULES="whci_hcd"
= 8< =========================
(Just needed to follow /var/log/syslog,

Apr 13 21:00:56 weg kernel: [14360.043993] *whci-hcd* 0000:0d:00.0-1:
wusbhc_rh_suspend (ffff8803f837b800 [ffff8803f837b800]) UNIMPLEMENTED

)

Now comes hibernate... Thanks a lot, Nick

2011/4/13 Daniel Manrique <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Status: Open => Answered
>
> Daniel Manrique proposed the following answer:
> Hi Nick,
>
> That's great, and it turns out there are (or have been, it was supposed
> to be fixed) problems with suspend/hibernate and USB3.
>
> Could you please take a look at these bug reports and see if the
> workarounds suggested in their comment sections (mainly removing xhci
> module before trying to suspend) help with your problem?
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998 (check
> comment #28 in this bug for a quick, temporary way to disable the module
> and test whether it helps you).
>
> https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/562484
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=18
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Nick Rudnick (nick-rudnick) said : #21

Dear all,

what is the proper way to commit a fix? I never did this before...

Thanks a lot in advance, Nick

2011/4/14 Nick Rudnick <email address hidden>

> Your question #152640 on Ubuntu-Certification changed:
> https://answers.launchpad.net/ubuntu-certification/+question/152640
>
> Status: Answered => Open
>
> You are still having a problem:
> [?][?][?]...
>
> Sorry... I fell asleep... just an unintended effect of hibernate...
>
> suspend works, just by adding the file
>
> /etc/pm/config.d/unload_modules
>
> with content
> = 8< =========================
> SUSPEND_MODULES="whci_hcd"
> = 8< =========================
> (Just needed to follow /var/log/syslog,
>
> Apr 13 21:00:56 weg kernel: [14360.043993] *whci-hcd* 0000:0d:00.0-1:
> wusbhc_rh_suspend (ffff8803f837b800 [ffff8803f837b800]) UNIMPLEMENTED
>
> )
>
> Now comes hibernate... Thanks a lot, Nick
>
> 2011/4/13 Daniel Manrique <email address hidden>
>
> > Your question #152640 on Ubuntu-Certification changed:
> > https://answers.launchpad.net/ubuntu-certification/+question/152640
> >
> > Status: Open => Answered
> >
> > Daniel Manrique proposed the following answer:
> > Hi Nick,
> >
> > That's great, and it turns out there are (or have been, it was supposed
> > to be fixed) problems with suspend/hibernate and USB3.
> >
> > Could you please take a look at these bug reports and see if the
> > workarounds suggested in their comment sections (mainly removing xhci
> > module before trying to suspend) help with your problem?
> >
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998 (check
> > comment #28 in this bug for a quick, temporary way to disable the module
> > and test whether it helps you).
> >
> > https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/562484
> >
> > --
> > If this answers your question, please go to the following page to let us
> > know that it is solved:
> >
> >
> https://answers.launchpad.net/ubuntu-certification/+question/152640/+confirm?answer_id=18
> >
> > If you still need help, you can reply to this email or go to the
> > following page to enter your feedback:
> > https://answers.launchpad.net/ubuntu-certification/+question/152640
> >
> > You received this question notification because you are a direct
> > subscriber of the question.
> >
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>

Nick Rudnick (nick-rudnick) said : #22

Dear all,

while suspend-to-RAM succeeds with hanging out whci-hcd as reported, the
behaviour after calling suspend-to-disk/hibernate is somewhat miraculous --
seemingly, the process of stopping the system is interrupted, and the system
returns to normal operation again, with a locked screen (see below).

Grateful for any hint, Nick

Apr 15 21:37:17 weg NetworkManager[810]: <info> sleep requested (sleeping:
no enabled: yes)
Apr 15 21:37:17 weg NetworkManager[810]: <info> sleeping or disabling...
Apr 15 21:37:17 weg NetworkManager[810]: <info> (wlan0): now unmanaged
Apr 15 21:37:17 weg NetworkManager[810]: <info> (wlan0): device state
change: 8 -> 1 (reason 37)
Apr 15 21:37:17 weg NetworkManager[810]: <info> (wlan0): deactivating device
(reason: 37).
Apr 15 21:37:17 weg NetworkManager[810]: <info> (wlan0): canceled DHCP
transaction, DHCP client pid 2656
Apr 15 21:37:17 weg kernel: [ 774.865370] wlan0: deauthenticating from
00:15:0c:19:66:16 by local choice (reason=3)
Apr 15 21:37:18 weg kernel: [ 775.188544] cfg80211: All devices are
disconnected, going to restore regulatory settings
Apr 15 21:37:18 weg kernel: [ 775.188552] cfg80211: Restoring regulatory
settings
Apr 15 21:37:18 weg kernel: [ 775.188565] cfg80211: Calling CRDA to update
world regulatory domain
Apr 15 21:37:18 weg kernel: [ 775.193539] cfg80211: Ignoring regulatory
request Set by core since the driver uses its own custom regulatory domain
Apr 15 21:37:18 weg kernel: [ 775.193548] cfg80211: World regulatory domain
updated:
Apr 15 21:37:18 weg kernel: [ 775.193551] cfg80211: (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 15 21:37:18 weg kernel: [ 775.193556] cfg80211: (2402000 KHz -
2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 15 21:37:18 weg kernel: [ 775.193561] cfg80211: (2457000 KHz -
2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 15 21:37:18 weg kernel: [ 775.193565] cfg80211: (2474000 KHz -
2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 15 21:37:18 weg kernel: [ 775.193569] cfg80211: (5170000 KHz -
5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 15 21:37:18 weg kernel: [ 775.193573] cfg80211: (5735000 KHz -
5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 15 21:37:18 weg wpa_supplicant[1048]: CTRL-EVENT-DISCONNECTED
bssid=00:00:00:00:00:00 reason=0
Apr 15 21:37:18 weg avahi-daemon[806]: Withdrawing address record for
192.168.178.22 on wlan0.
Apr 15 21:37:18 weg avahi-daemon[806]: Leaving mDNS multicast group on
interface wlan0.IPv4 with address 192.168.178.22.
Apr 15 21:37:18 weg avahi-daemon[806]: Interface wlan0.IPv4 no longer
relevant for mDNS.
Apr 15 21:37:18 weg NetworkManager[810]: <info> (wlan0): cleaning up...
Apr 15 21:37:18 weg NetworkManager[810]: <info> (wlan0): taking down device.
Apr 15 21:37:18 weg avahi-daemon[806]: Interface wlan0.IPv6 no longer
relevant for mDNS.
Apr 15 21:37:18 weg avahi-daemon[806]: Leaving mDNS multicast group on
interface wlan0.IPv6 with address fe80::224:d7ff:fe92:2028.
Apr 15 21:37:18 weg avahi-daemon[806]: Withdrawing address record for
fe80::224:d7ff:fe92:2028 on wlan0.
Apr 15 21:37:18 weg NetworkManager[810]: <info> (eth0): now unmanaged
Apr 15 21:37:18 weg NetworkManager[810]: <info> (eth0): device state change:
2 -> 1 (reason 37)
Apr 15 21:37:18 weg NetworkManager[810]: <info> (eth0): cleaning up...
Apr 15 21:37:18 weg NetworkManager[810]: <info> (eth0): taking down device.
Apr 15 21:37:18 weg anacron[2850]: Anacron 2.3 started on 2011-04-15
Apr 15 21:37:18 weg anacron[2850]: Normal exit (0 jobs run)
Apr 15 21:37:20 weg kernel: [ 777.264997] whci-hcd 0000:0d:00.0-1: remove,
state 1
Apr 15 21:37:20 weg kernel: [ 777.265009] usb usb3: USB disconnect, address
1
Apr 15 21:37:20 weg kernel: [ 777.324831] whci-hcd 0000:0d:00.0-1: USB bus
3 deregistered
------------------------------------------------------------------
UNTIL HERE IDENTICAL TO SUSPEND-TO-RAM
------------------------------------------------------------------
Apr 15 21:37:20 weg anacron[3240]: Anacron 2.3 started on 2011-04-15
Apr 15 21:37:20 weg anacron[3240]: Normal exit (0 jobs run)
Apr 15 21:37:20 weg kernel: [ 777.754841] whci-hcd 0000:0d:00.0-1: Wireless
host controller
Apr 15 21:37:20 weg kernel: [ 777.754946] whci-hcd 0000:0d:00.0-1: new USB
bus registered, assigned bus number 3
------------------------------------------------------------------
AFTER HERE IDENTICAL TO SUSPEND-TO-RAM AFTER RESTARTING
------------------------------------------------------------------
Apr 15 21:37:20 weg NetworkManager[810]: <info> wake requested (sleeping:
yes enabled: yes)
Apr 15 21:37:20 weg NetworkManager[810]: <info> waking up and re-enabling...
Apr 15 21:37:20 weg NetworkManager[810]: <info> (wlan0): now managed
Apr 15 21:37:20 weg NetworkManager[810]: <info> (wlan0): device state
change: 1 -> 2 (reason 2)
Apr 15 21:37:20 weg NetworkManager[810]: <info> (wlan0): bringing up device.
Apr 15 21:37:20 weg kernel: [ 777.834854] whci-hcd 0000:0d:00.0-1: irq 46,
io base 0x00000000
Apr 15 21:37:20 weg kernel: [ 777.835091] hub 3-0:1.0: USB hub found
Apr 15 21:37:20 weg kernel: [ 777.835101] hub 3-0:1.0: 15 ports detected
Apr 15 21:37:20 weg NetworkManager[810]: <info> (wlan0): preparing device.
Apr 15 21:37:20 weg NetworkManager[810]: <info> (wlan0): deactivating device
(reason: 2).
Apr 15 21:37:20 weg NetworkManager[810]: <info> Unmanaged Device found;
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Apr 15 21:37:20 weg NetworkManager[810]: <info> Unmanaged Device found;
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Apr 15 21:37:20 weg kernel: [ 777.983802] ADDRCONF(NETDEV_UP): wlan0: link
is not ready
Apr 15 21:37:20 weg NetworkManager[810]: <info> (eth0): now managed
Apr 15 21:37:20 weg NetworkManager[810]: <info> (eth0): device state change:
1 -> 2 (reason 2)
Apr 15 21:37:20 weg NetworkManager[810]: <info> (eth0): bringing up device.
Apr 15 21:37:20 weg kernel: [ 778.015038] tg3 0000:09:00.0: irq 49 for
MSI/MSI-X
Apr 15 21:37:21 weg NetworkManager[810]: <info> (eth0): preparing device.
Apr 15 21:37:21 weg NetworkManager[810]: <info> (eth0): deactivating device
(reason: 2).
Apr 15 21:37:21 weg kernel: [ 778.697486] ADDRCONF(NETDEV_UP): eth0: link
is not ready
Apr 15 21:37:21 weg NetworkManager[810]: <info> (wlan0): supplicant
interface state: starting -> ready
Apr 15 21:37:21 weg NetworkManager[810]: <info> (wlan0): device state
change: 2 -> 3 (reason 42)
Apr 15 21:37:21 weg anacron[3405]: Anacron 2.3 started on 2011-04-15
Apr 15 21:37:21 weg anacron[3405]: Normal exit (0 jobs run)
Apr 15 21:37:22 weg wpa_supplicant[1048]: Failed to initiate AP scan.
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) starting
connection 'Auto oldwill'
Apr 15 21:37:24 weg NetworkManager[810]: <info> (wlan0): device state
change: 3 -> 4 (reason 0)
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) scheduled...
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) started...
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) scheduled...
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) complete.
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) starting...
Apr 15 21:37:24 weg NetworkManager[810]: <info> (wlan0): device state
change: 4 -> 5 (reason 0)
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0/wireless):
access point 'Auto oldwill' has security, but secrets are required.
Apr 15 21:37:24 weg NetworkManager[810]: <info> (wlan0): device state
change: 5 -> 6 (reason 0)
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) complete.
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) scheduled...
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) started...
Apr 15 21:37:24 weg NetworkManager[810]: <info> (wlan0): device state
change: 6 -> 4 (reason 0)
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) scheduled...
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 1
of 5 (Device Prepare) complete.
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) starting...
Apr 15 21:37:24 weg NetworkManager[810]: <info> (wlan0): device state
change: 4 -> 5 (reason 0)
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0/wireless):
connection 'Auto oldwill' has security, and secrets exist. No new secrets
needed.
Apr 15 21:37:24 weg NetworkManager[810]: <info> Config: added 'ssid' value
'oldwill'
Apr 15 21:37:24 weg NetworkManager[810]: <info> Config: added 'scan_ssid'
value '1'
Apr 15 21:37:24 weg NetworkManager[810]: <info> Config: added 'key_mgmt'
value 'WPA-PSK'
Apr 15 21:37:24 weg NetworkManager[810]: <info> Config: added 'psk' value
'<omitted>'
Apr 15 21:37:24 weg NetworkManager[810]:
nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X
(setting)' failed
Apr 15 21:37:24 weg NetworkManager[810]:
nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X
(setting)' failed
Apr 15 21:37:24 weg NetworkManager[810]: <info> Activation (wlan0) Stage 2
of 5 (Device Configure) complete.
Apr 15 21:37:24 weg NetworkManager[810]: <info> Config: set interface
ap_scan to 1
Apr 15 21:37:24 weg NetworkManager[810]: <info> (wlan0): supplicant
connection state: inactive -> scanning
Apr 15 21:37:28 weg wpa_supplicant[1048]: Trying to associate with
00:15:0c:19:66:16 (SSID='oldwill' freq=2412 MHz)
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): supplicant
connection state: scanning -> associating
Apr 15 21:37:28 weg kernel: [ 785.249661] wlan0: authenticate with
00:15:0c:19:66:16 (try 1)
Apr 15 21:37:28 weg kernel: [ 785.251954] wlan0: authenticated
Apr 15 21:37:28 weg kernel: [ 785.252151] wlan0: associate with
00:15:0c:19:66:16 (try 1)
Apr 15 21:37:28 weg kernel: [ 785.255145] wlan0: RX AssocResp from
00:15:0c:19:66:16 (capab=0x471 status=0 aid=3)
Apr 15 21:37:28 weg kernel: [ 785.255151] wlan0: associated
Apr 15 21:37:28 weg wpa_supplicant[1048]: Associated with 00:15:0c:19:66:16
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): supplicant
connection state: associating -> associated
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): supplicant
connection state: associated -> 4-way handshake
Apr 15 21:37:28 weg kernel: [ 785.261997] ADDRCONF(NETDEV_CHANGE): wlan0:
link becomes ready
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): supplicant
connection state: 4-way handshake -> group handshake
Apr 15 21:37:28 weg wpa_supplicant[1048]: WPA: Key negotiation completed
with 00:15:0c:19:66:16 [PTK=CCMP GTK=CCMP]
Apr 15 21:37:28 weg wpa_supplicant[1048]: CTRL-EVENT-CONNECTED - Connection
to 00:15:0c:19:66:16 completed (auth) [id=0 id_str=]
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): supplicant
connection state: group handshake -> completed
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0/wireless)
Stage 2 of 5 (Device Configure) successful. Connected to wireless network
'oldwill'.
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 3
of 5 (IP Configure Start) scheduled.
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 3
of 5 (IP Configure Start) started...
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): device state
change: 5 -> 7 (reason 0)
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Beginning
DHCPv4 transaction (timeout in 45 seconds)
Apr 15 21:37:28 weg NetworkManager[810]: <info> dhclient started with pid
3434
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 3
of 5 (IP Configure Start) complete.
Apr 15 21:37:28 weg dhclient: Internet Systems Consortium DHCP Client
4.1.1-P1
Apr 15 21:37:28 weg dhclient: Copyright 2004-2010 Internet Systems
Consortium.
Apr 15 21:37:28 weg dhclient: All rights reserved.
Apr 15 21:37:28 weg dhclient: For info, please visit
https://www.isc.org/software/dhcp/
Apr 15 21:37:28 weg dhclient:
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): DHCPv4 state
changed nbi -> preinit
Apr 15 21:37:28 weg dhclient: Listening on LPF/wlan0/00:24:d7:92:20:28
Apr 15 21:37:28 weg dhclient: Sending on LPF/wlan0/00:24:d7:92:20:28
Apr 15 21:37:28 weg dhclient: Sending on Socket/fallback
Apr 15 21:37:28 weg dhclient: DHCPREQUEST of 192.168.178.22 on wlan0 to
255.255.255.255 port 67
Apr 15 21:37:28 weg dhclient: DHCPACK of 192.168.178.22 from 192.168.178.1
Apr 15 21:37:28 weg dhclient: bound to 192.168.178.22 -- renewal in 409413
seconds.
Apr 15 21:37:28 weg NetworkManager[810]: <info> (wlan0): DHCPv4 state
changed preinit -> reboot
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 4
of 5 (IP4 Configure Get) scheduled...
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 4
of 5 (IP4 Configure Get) started...
Apr 15 21:37:28 weg NetworkManager[810]: <info> address 192.168.178.22
Apr 15 21:37:28 weg NetworkManager[810]: <info> prefix 24 (255.255.255.0)
Apr 15 21:37:28 weg NetworkManager[810]: <info> gateway 192.168.178.1
Apr 15 21:37:28 weg NetworkManager[810]: <info> nameserver '192.168.178.1'
Apr 15 21:37:28 weg NetworkManager[810]: <info> Scheduling stage 5
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 5
of 5 (IP Configure Commit) scheduled...
Apr 15 21:37:28 weg NetworkManager[810]: <info> Done scheduling stage 5
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 4
of 5 (IP4 Configure Get) complete.
Apr 15 21:37:28 weg NetworkManager[810]: <info> Activation (wlan0) Stage 5
of 5 (IP Configure Commit) started...
Apr 15 21:37:28 weg avahi-daemon[806]: Joining mDNS multicast group on
interface wlan0.IPv4 with address 192.168.178.22.
Apr 15 21:37:28 weg avahi-daemon[806]: New relevant interface wlan0.IPv4 for
mDNS.
Apr 15 21:37:28 weg avahi-daemon[806]: Registering new address record for
192.168.178.22 on wlan0.IPv4.
Apr 15 21:37:29 weg NetworkManager[810]: <info> (wlan0): device state
change: 7 -> 8 (reason 0)
Apr 15 21:37:29 weg NetworkManager[810]: <info> Policy set 'Auto oldwill'
(wlan0) as default for IPv4 routing and DNS.
Apr 15 21:37:29 weg NetworkManager[810]: <info> Activation (wlan0)
successful, device activated.
Apr 15 21:37:29 weg NetworkManager[810]: <info> Activation (wlan0) Stage 5
of 5 (IP Configure Commit) complete.
Apr 15 21:37:30 weg avahi-daemon[806]: Joining mDNS multicast group on
interface wlan0.IPv6 with address fe80::224:d7ff:fe92:2028.
Apr 15 21:37:30 weg avahi-daemon[806]: New relevant interface wlan0.IPv6 for
mDNS.
Apr 15 21:37:30 weg avahi-daemon[806]: Registering new address record for
fe80::224:d7ff:fe92:2028 on wlan0.*.

Nick Rudnick (nick-rudnick) said : #23

Dear all,

below I attached how (intact) suspend-to-RAM continues the process of
shutting down and restart.

Cheers, Nick

------------------------------------------------------------------
UNTIL HERE IDENTICAL TO SUSPEND-TO-DISK
------------------------------------------------------------------
Apr 15 21:50:06 weg acpid: client 1080[0:0] has disconnected
Apr 15 21:50:06 weg kernel: [ 1146.076679] PM: Syncing filesystems ... done.
Apr 15 21:50:06 weg kernel: [ 1146.093396] PM: Preparing system for mem
sleep
Apr 15 21:50:06 weg kernel: [ 1146.093677] Freezing user space processes ...
(elapsed 0.01 seconds) done.
Apr 15 21:50:06 weg kernel: [ 1146.111167] Freezing remaining freezable
tasks ... (elapsed 0.01 seconds) done.
Apr 15 21:50:06 weg kernel: [ 1146.131163] PM: Entering mem sleep
Apr 15 21:50:06 weg kernel: [ 1146.131177] Suspending console(s) (use
no_console_suspend to debug)
Apr 15 21:50:06 weg kernel: [ 1146.250043] PM: suspend of drv:psmouse
dev:serio2 complete after 118.693 msecs
Apr 15 21:50:06 weg kernel: [ 1146.261093] sd 2:0:0:0: [sdb] Synchronizing
SCSI cache
Apr 15 21:50:06 weg kernel: [ 1146.262255] sd 0:0:0:0: [sda] Synchronizing
SCSI cache
Apr 15 21:50:06 weg kernel: [ 1146.262389] sd 2:0:0:0: [sdb] Stopping disk
Apr 15 21:50:06 weg kernel: [ 1146.263543] sd 0:0:0:0: [sda] Stopping disk
Apr 15 21:50:06 weg kernel: [ 1146.303292] [drm] nouveau 0000:01:00.0:
Disabling fbcon acceleration...
Apr 15 21:50:06 weg kernel: [ 1146.303295] [drm] nouveau 0000:01:00.0:
Unpinning framebuffer(s)...
Apr 15 21:50:06 weg kernel: [ 1146.303314] ACPI handle has no context!
Apr 15 21:50:06 weg kernel: [ 1146.303327] [drm] nouveau 0000:01:00.0:
Evicting buffers...
Apr 15 21:50:06 weg kernel: [ 1146.303377] tifm_7xx1 0000:03:01.2: PCI INT A
disabled
Apr 15 21:50:06 weg kernel: [ 1146.303379] ACPI handle has no context!
Apr 15 21:50:06 weg kernel: [ 1146.303396] ACPI handle has no context!
Apr 15 21:50:06 weg kernel: [ 1146.303453] ACPI handle has no context!
Apr 15 21:50:06 weg kernel: [ 1146.303462] sdhci-pci 0000:03:01.3: PCI INT A
disabled
Apr 15 21:50:06 weg kernel: [ 1146.303469] ACPI handle has no context!
Apr 15 21:50:06 weg kernel: [ 1146.340906] ehci_hcd 0000:00:1a.0: PCI INT A
disabled
Apr 15 21:50:06 weg kernel: [ 1146.380830] PM: suspend of drv:usb dev:2-1
complete after 118.804 msecs
Apr 15 21:50:06 weg kernel: [ 1146.400856] ehci_hcd 0000:00:1d.0: PCI INT A
disabled
Apr 15 21:50:06 weg kernel: [ 1146.411972] HDA Intel 0000:00:1b.0: PCI INT A
disabled
Apr 15 21:50:06 weg kernel: [ 1146.430836] PM: suspend of drv:HDA Intel
dev:0000:00:1b.0 complete after 127.441 msecs
Apr 15 21:50:06 weg kernel: [ 1146.596019] [drm] nouveau 0000:01:00.0:
Idling channels...
Apr 15 21:50:06 weg kernel: [ 1146.596324] [drm] nouveau 0000:01:00.0:
Suspending GPU objects...
Apr 15 21:50:06 weg kernel: [ 1147.818507] [drm] nouveau 0000:01:00.0: And
we're gone!
Apr 15 21:50:06 weg kernel: [ 1147.818531] nouveau 0000:01:00.0: PCI INT A
disabled
Apr 15 21:50:06 weg kernel: [ 1147.830374] PM: suspend of drv:nouveau
dev:0000:01:00.0 complete after 1527.729 msecs
Apr 15 21:50:06 weg kernel: [ 1147.830449] PM: suspend of drv:pcieport
dev:0000:00:03.0 complete after 1527.604 msecs
Apr 15 21:50:06 weg kernel: [ 1147.830483] PM: suspend of drv:
dev:pci0000:00 complete after 1527.528 msecs
Apr 15 21:50:06 weg kernel: [ 1147.830509] PM: suspend of devices complete
after 1699.837 msecs
Apr 15 21:50:06 weg kernel: [ 1147.830514] PM: suspend devices took 1.700
seconds
Apr 15 21:50:06 weg kernel: [ 1147.890489] PM: late suspend of devices
complete after 59.996 msecs
Apr 15 21:50:06 weg kernel: [ 1147.891038] ACPI: Preparing to enter system
sleep state S3
Apr 15 21:50:06 weg kernel: [ 1147.931084] PM: Saving platform NVS memory
Apr 15 21:50:06 weg kernel: [ 1147.931086] Disabling non-boot CPUs ...
Apr 15 21:50:06 weg kernel: [ 1147.950782] Broke affinity for irq 41
Apr 15 21:50:06 weg kernel: [ 1148.060276] CPU 1 is now offline
Apr 15 21:50:06 weg kernel: [ 1148.240690] Broke affinity for irq 42
Apr 15 21:50:06 weg kernel: [ 1148.350097] CPU 2 is now offline
Apr 15 21:50:06 weg kernel: [ 1148.490505] Broke affinity for irq 16
Apr 15 21:50:06 weg kernel: [ 1148.490527] Broke affinity for irq 43
Apr 15 21:50:06 weg kernel: [ 1148.599982] CPU 3 is now offline
Apr 15 21:50:06 weg kernel: [ 1148.760289] Broke affinity for irq 44
Apr 15 21:50:06 weg kernel: [ 1148.869875] CPU 4 is now offline
Apr 15 21:50:06 weg kernel: [ 1149.139752] CPU 5 is now offline
Apr 15 21:50:06 weg kernel: [ 1149.409682] CPU 6 is now offline
Apr 15 21:50:06 weg kernel: [ 1149.549578] CPU 7 is now offline
Apr 15 21:50:06 weg kernel: [ 1149.549861] Extended CMOS year: 2000
Apr 15 21:50:06 weg kernel: [ 1149.550216] Back to C!
Apr 15 21:50:06 weg kernel: [ 1149.550219] PM: Restoring platform NVS memory
Apr 15 21:50:06 weg kernel: [ 1149.550498] CPU0: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1149.550558] Extended CMOS year: 2000

Apr 15 21:50:06 weg kernel: [ 1149.550590] Enabling non-boot CPUs ...
Apr 15 21:50:06 weg kernel: [ 1149.550689] Booting Node 0 Processor 1 APIC
0x1
Apr 15 21:50:06 weg kernel: [ 1149.710135] CPU1: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1149.740181] Switched to NOHz mode on CPU #1
Apr 15 21:50:06 weg kernel: [ 1149.740247] hpet: hpet3 irq 41 for MSI
Apr 15 21:50:06 weg kernel: [ 1149.740266] CPU1 is up
Apr 15 21:50:06 weg kernel: [ 1149.740368] Booting Node 0 Processor 2 APIC
0x2
Apr 15 21:50:06 weg kernel: [ 1149.900054] CPU2: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1149.930056] Switched to NOHz mode on CPU #2
Apr 15 21:50:06 weg kernel: [ 1150.000115] hpet: hpet4 irq 42 for MSI
Apr 15 21:50:06 weg kernel: [ 1150.000187] CPU2 is up
Apr 15 21:50:06 weg kernel: [ 1150.000290] Booting Node 0 Processor 3 APIC
0x3
Apr 15 21:50:06 weg kernel: [ 1150.159945] CPU3: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1150.190011] Switched to NOHz mode on CPU #3
Apr 15 21:50:06 weg kernel: [ 1150.300089] hpet: hpet5 irq 43 for MSI
Apr 15 21:50:06 weg kernel: [ 1150.300159] CPU3 is up
Apr 15 21:50:06 weg kernel: [ 1150.300592] Booting Node 0 Processor 4 APIC
0x4
Apr 15 21:50:06 weg kernel: [ 1150.459863] CPU4: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1150.489887] Switched to NOHz mode on CPU #4
Apr 15 21:50:06 weg kernel: [ 1150.599928] hpet: hpet6 irq 44 for MSI
Apr 15 21:50:06 weg kernel: [ 1150.599993] CPU4 is up
Apr 15 21:50:06 weg kernel: [ 1150.600443] Booting Node 0 Processor 5 APIC
0x5
Apr 15 21:50:06 weg kernel: [ 1150.759686] CPU5: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1150.789735] Switched to NOHz mode on CPU #5
Apr 15 21:50:06 weg kernel: [ 1150.889863] CPU5 is up
Apr 15 21:50:06 weg kernel: [ 1150.890344] Booting Node 0 Processor 6 APIC
0x6
Apr 15 21:50:06 weg kernel: [ 1151.049670] CPU6: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1151.079566] Switched to NOHz mode on CPU #6
Apr 15 21:50:06 weg kernel: [ 1151.179708] CPU6 is up
Apr 15 21:50:06 weg kernel: [ 1151.180243] Booting Node 0 Processor 7 APIC
0x7
Apr 15 21:50:06 weg kernel: [ 1151.339442] CPU7: Thermal monitoring handled
by SMI
Apr 15 21:50:06 weg kernel: [ 1151.369550] Switched to NOHz mode on CPU #7
Apr 15 21:50:06 weg kernel: [ 1151.489856] CPU7 is up
Apr 15 21:50:06 weg kernel: [ 1151.493616] ACPI: Waking up from system sleep
state S3
Apr 15 21:50:06 weg kernel: [ 1151.770434] pci 0000:00:00.0: restoring
config space at offset 0x3 (was 0x0, writing 0x10)
Apr 15 21:50:06 weg kernel: [ 1151.770464] pcieport 0000:00:03.0: restoring
config space at offset 0xf (was 0x80100, writing 0x1a0100)
Apr 15 21:50:06 weg kernel: [ 1151.770476] pcieport 0000:00:03.0: restoring
config space at offset 0x9 (was 0x10001, writing 0xeff1e001)
Apr 15 21:50:06 weg kernel: [ 1151.770478] pcieport 0000:00:03.0: restoring
config space at offset 0x8 (was 0x0, writing 0xf6e0f200)
Apr 15 21:50:06 weg kernel: [ 1151.770481] pcieport 0000:00:03.0: restoring
config space at offset 0x7 (was 0x20000000, writing 0xd0d0)
Apr 15 21:50:06 weg kernel: [ 1151.770483] pcieport 0000:00:03.0: restoring
config space at offset 0x6 (was 0x0, writing 0x10100)
Apr 15 21:50:06 weg kernel: [ 1151.770487] pcieport 0000:00:03.0: restoring
config space at offset 0x3 (was 0x10000, writing 0x10010)
Apr 15 21:50:06 weg kernel: [ 1151.770490] pcieport 0000:00:03.0: restoring
config space at offset 0x1 (was 0x100000, writing 0x100107)
Apr 15 21:50:06 weg kernel: [ 1151.770512] pci 0000:00:08.0: restoring
config space at offset 0x3 (was 0x800000, writing 0x800010)
Apr 15 21:50:06 weg kernel: [ 1151.770530] pci 0000:00:08.1: restoring
config space at offset 0x3 (was 0x800000, writing 0x800010)
Apr 15 21:50:06 weg kernel: [ 1151.770549] pci 0000:00:08.2: restoring
config space at offset 0x3 (was 0x800000, writing 0x800010)
Apr 15 21:50:06 weg kernel: [ 1151.770562] pci 0000:00:08.3: restoring
config space at offset 0x3 (was 0x800000, writing 0x800010)
Apr 15 21:50:06 weg kernel: [ 1151.770574] pci 0000:00:10.0: restoring
config space at offset 0x3 (was 0x800000, writing 0x800010)
Apr 15 21:50:06 weg kernel: [ 1151.770586] pci 0000:00:10.1: restoring
config space at offset 0x3 (was 0x800000, writing 0x800010)
Apr 15 21:50:06 weg kernel: [ 1151.770605] ehci_hcd 0000:00:1a.0: restoring
config space at offset 0xf (was 0x100, writing 0x105)
Apr 15 21:50:06 weg kernel: [ 1151.770622] ehci_hcd 0000:00:1a.0: restoring
config space at offset 0x4 (was 0x0, writing 0xfed1d000)
Apr 15 21:50:06 weg kernel: [ 1151.770631] ehci_hcd 0000:00:1a.0: restoring
config space at offset 0x1 (was 0x2900000, writing 0x2900102)
Apr 15 21:50:06 weg kernel: [ 1151.770657] HDA Intel 0000:00:1b.0: restoring
config space at offset 0xf (was 0x100, writing 0x103)
Apr 15 21:50:06 weg kernel: [ 1151.770672] HDA Intel 0000:00:1b.0: restoring
config space at offset 0x4 (was 0x4, writing 0xf6ffc004)
Apr 15 21:50:06 weg kernel: [ 1151.770679] HDA Intel 0000:00:1b.0: restoring
config space at offset 0x3 (was 0x0, writing 0x10)
Apr 15 21:50:06 weg kernel: [ 1151.770687] HDA Intel 0000:00:1b.0: restoring
config space at offset 0x1 (was 0x100004, writing 0x100102)
Apr 15 21:50:06 weg kernel: [ 1151.770716] pcieport 0000:00:1c.0: restoring
config space at offset 0xf (was 0x100, writing 0x20100)
Apr 15 21:50:06 weg kernel: [ 1151.770727] pcieport 0000:00:1c.0: restoring
config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Apr 15 21:50:06 weg kernel: [ 1151.770734] pcieport 0000:00:1c.0: restoring
config space at offset 0x8 (was 0x0, writing 0xfff0)
Apr 15 21:50:06 weg kernel: [ 1151.770742] pcieport 0000:00:1c.0: restoring
config space at offset 0x7 (was 0x20000000, writing 0x200000f0)
Apr 15 21:50:06 weg kernel: [ 1151.770749] pcieport 0000:00:1c.0: restoring
config space at offset 0x6 (was 0x0, writing 0xb0b00)
Apr 15 21:50:06 weg kernel: [ 1151.770758] pcieport 0000:00:1c.0: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.770766] pcieport 0000:00:1c.0: restoring
config space at offset 0x1 (was 0x100000, writing 0x100107)
Apr 15 21:50:06 weg kernel: [ 1151.770793] pcieport 0000:00:1c.1: restoring
config space at offset 0xf (was 0x200, writing 0x20200)
Apr 15 21:50:06 weg kernel: [ 1151.770805] pcieport 0000:00:1c.1: restoring
config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Apr 15 21:50:06 weg kernel: [ 1151.770812] pcieport 0000:00:1c.1: restoring
config space at offset 0x8 (was 0x0, writing 0xf1f0f1f0)
Apr 15 21:50:06 weg kernel: [ 1151.770819] pcieport 0000:00:1c.1: restoring
config space at offset 0x7 (was 0x0, writing 0xf0)
Apr 15 21:50:06 weg rtkit-daemon[1551]: The canary thread is apparently
starving. Taking action.
Apr 15 21:50:06 weg rtkit-daemon[1551]: Demoting known real-time threads.
Apr 15 21:50:06 weg rtkit-daemon[1551]: Successfully demoted thread 1611 of
process 1549 (n/a).
Apr 15 21:50:06 weg rtkit-daemon[1551]: Successfully demoted thread 1605 of
process 1549 (n/a).
Apr 15 21:50:06 weg rtkit-daemon[1551]: Successfully demoted thread 1549 of
process 1549 (n/a).
Apr 15 21:50:06 weg rtkit-daemon[1551]: Demoted 3 threads.
Apr 15 21:50:06 weg kernel: [ 1151.770826] pcieport 0000:00:1c.1: restoring
config space at offset 0x6 (was 0x0, writing 0xc0c00)
Apr 15 21:50:06 weg kernel: [ 1151.770835] pcieport 0000:00:1c.1: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.770843] pcieport 0000:00:1c.1: restoring
config space at offset 0x1 (was 0x100000, writing 0x100107)
Apr 15 21:50:06 weg kernel: [ 1151.770870] pcieport 0000:00:1c.2: restoring
config space at offset 0xf (was 0x300, writing 0x20300)
Apr 15 21:50:06 weg kernel: [ 1151.770881] pcieport 0000:00:1c.2: restoring
config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Apr 15 21:50:06 weg kernel: [ 1151.770889] pcieport 0000:00:1c.2: restoring
config space at offset 0x8 (was 0x0, writing 0xf1e0f1e0)
Apr 15 21:50:06 weg kernel: [ 1151.770896] pcieport 0000:00:1c.2: restoring
config space at offset 0x7 (was 0x0, writing 0xc0c0)
Apr 15 21:50:06 weg kernel: [ 1151.770903] pcieport 0000:00:1c.2: restoring
config space at offset 0x6 (was 0x0, writing 0xd0d00)
Apr 15 21:50:06 weg kernel: [ 1151.770912] pcieport 0000:00:1c.2: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.770920] pcieport 0000:00:1c.2: restoring
config space at offset 0x1 (was 0x100000, writing 0x100107)
Apr 15 21:50:06 weg kernel: [ 1151.770947] pcieport 0000:00:1c.3: restoring
config space at offset 0xf (was 0x400, writing 0x20400)
Apr 15 21:50:06 weg kernel: [ 1151.770958] pcieport 0000:00:1c.3: restoring
config space at offset 0x9 (was 0x10001, writing 0xf011f001)
Apr 15 21:50:06 weg kernel: [ 1151.770965] pcieport 0000:00:1c.3: restoring
config space at offset 0x8 (was 0x0, writing 0xf1d0f1c0)
Apr 15 21:50:06 weg kernel: [ 1151.770973] pcieport 0000:00:1c.3: restoring
config space at offset 0x7 (was 0x20000000, writing 0xb0b0)
Apr 15 21:50:06 weg kernel: [ 1151.770980] pcieport 0000:00:1c.3: restoring
config space at offset 0x6 (was 0x0, writing 0xf0e00)
Apr 15 21:50:06 weg kernel: [ 1151.770989] pcieport 0000:00:1c.3: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.770997] pcieport 0000:00:1c.3: restoring
config space at offset 0x1 (was 0x100000, writing 0x100007)
Apr 15 21:50:06 weg kernel: [ 1151.771024] pcieport 0000:00:1c.4: restoring
config space at offset 0xf (was 0x100, writing 0x20100)
Apr 15 21:50:06 weg kernel: [ 1151.771035] pcieport 0000:00:1c.4: restoring
config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Apr 15 21:50:06 weg kernel: [ 1151.771043] pcieport 0000:00:1c.4: restoring
config space at offset 0x8 (was 0x0, writing 0xfff0)
Apr 15 21:50:06 weg kernel: [ 1151.771050] pcieport 0000:00:1c.4: restoring
config space at offset 0x7 (was 0x20000000, writing 0x200000f0)
Apr 15 21:50:06 weg kernel: [ 1151.771057] pcieport 0000:00:1c.4: restoring
config space at offset 0x6 (was 0x0, writing 0x101000)
Apr 15 21:50:06 weg kernel: [ 1151.771066] pcieport 0000:00:1c.4: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.771074] pcieport 0000:00:1c.4: restoring
config space at offset 0x1 (was 0x100000, writing 0x100107)
Apr 15 21:50:06 weg kernel: [ 1151.771101] pcieport 0000:00:1c.5: restoring
config space at offset 0xf (was 0x200, writing 0x20200)
Apr 15 21:50:06 weg kernel: [ 1151.771112] pcieport 0000:00:1c.5: restoring
config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Apr 15 21:50:06 weg kernel: [ 1151.771119] pcieport 0000:00:1c.5: restoring
config space at offset 0x8 (was 0x0, writing 0xf1b0f1b0)
Apr 15 21:50:06 weg kernel: [ 1151.771127] pcieport 0000:00:1c.5: restoring
config space at offset 0x7 (was 0x0, writing 0xf0)
Apr 15 21:50:06 weg kernel: [ 1151.771134] pcieport 0000:00:1c.5: restoring
config space at offset 0x6 (was 0x0, writing 0x90900)
Apr 15 21:50:06 weg kernel: [ 1151.771143] pcieport 0000:00:1c.5: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.771151] pcieport 0000:00:1c.5: restoring
config space at offset 0x1 (was 0x100000, writing 0x100007)
Apr 15 21:50:06 weg kernel: [ 1151.771178] pcieport 0000:00:1c.6: restoring
config space at offset 0xf (was 0x300, writing 0x20300)
Apr 15 21:50:06 weg kernel: [ 1151.771189] pcieport 0000:00:1c.6: restoring
config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Apr 15 21:50:06 weg kernel: [ 1151.771196] pcieport 0000:00:1c.6: restoring
config space at offset 0x8 (was 0x0, writing 0xf1a0f1a0)
Apr 15 21:50:06 weg kernel: [ 1151.771203] pcieport 0000:00:1c.6: restoring
config space at offset 0x7 (was 0x0, writing 0x200000f0)
Apr 15 21:50:06 weg kernel: [ 1151.771211] pcieport 0000:00:1c.6: restoring
config space at offset 0x6 (was 0x0, writing 0x111100)
Apr 15 21:50:06 weg kernel: [ 1151.771219] pcieport 0000:00:1c.6: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.771228] pcieport 0000:00:1c.6: restoring
config space at offset 0x1 (was 0x100000, writing 0x100107)
Apr 15 21:50:06 weg kernel: [ 1151.771255] pcieport 0000:00:1c.7: restoring
config space at offset 0xf (was 0x400, writing 0x20400)
Apr 15 21:50:06 weg kernel: [ 1151.771266] pcieport 0000:00:1c.7: restoring
config space at offset 0x9 (was 0x10001, writing 0x1fff1)
Apr 15 21:50:06 weg kernel: [ 1151.771273] pcieport 0000:00:1c.7: restoring
config space at offset 0x8 (was 0x0, writing 0xfff0)
Apr 15 21:50:06 weg kernel: [ 1151.771281] pcieport 0000:00:1c.7: restoring
config space at offset 0x7 (was 0x20000000, writing 0x200000f0)
Apr 15 21:50:06 weg kernel: [ 1151.771288] pcieport 0000:00:1c.7: restoring
config space at offset 0x6 (was 0x0, writing 0x121200)
Apr 15 21:50:06 weg kernel: [ 1151.771297] pcieport 0000:00:1c.7: restoring
config space at offset 0x3 (was 0x810000, writing 0x810010)
Apr 15 21:50:06 weg kernel: [ 1151.771305] pcieport 0000:00:1c.7: restoring
config space at offset 0x1 (was 0x100000, writing 0x100107)
Apr 15 21:50:06 weg kernel: [ 1151.771332] ehci_hcd 0000:00:1d.0: restoring
config space at offset 0xf (was 0x100, writing 0x105)
Apr 15 21:50:06 weg kernel: [ 1151.771349] ehci_hcd 0000:00:1d.0: restoring
config space at offset 0x4 (was 0x0, writing 0xfed1c000)
Apr 15 21:50:06 weg kernel: [ 1151.771359] ehci_hcd 0000:00:1d.0: restoring
config space at offset 0x1 (was 0x2900000, writing 0x2900102)
Apr 15 21:50:06 weg kernel: [ 1151.771389] pci 0000:00:1e.0: restoring
config space at offset 0x7 (was 0x2280e0f0, writing 0x22802020)
Apr 15 21:50:06 weg kernel: [ 1151.771397] pci 0000:00:1e.0: restoring
config space at offset 0x6 (was 0x300, writing 0x20070300)
Apr 15 21:50:06 weg kernel: [ 1151.771439] pci 0000:00:1f.0: restoring
config space at offset 0x1 (was 0x2100007, writing 0x2100107)
Apr 15 21:50:06 weg kernel: [ 1151.771461] ahci 0000:00:1f.2: restoring
config space at offset 0xf (was 0x400, writing 0x40a)
Apr 15 21:50:06 weg kernel: [ 1151.771478] ahci 0000:00:1f.2: restoring
config space at offset 0x1 (was 0x2b00007, writing 0x2b00407)
Apr 15 21:50:06 weg kernel: [ 1151.771511] pci 0000:00:1f.3: restoring
config space at offset 0xf (was 0x200, writing 0x20a)
Apr 15 21:50:06 weg kernel: [ 1151.771526] pci 0000:00:1f.3: restoring
config space at offset 0x4 (was 0x4, writing 0xf6ffb004)
Apr 15 21:50:06 weg kernel: [ 1151.771534] pci 0000:00:1f.3: restoring
config space at offset 0x1 (was 0x2800001, writing 0x2800103)
Apr 15 21:50:06 weg kernel: [ 1151.771554] nouveau 0000:01:00.0: restoring
config space at offset 0xf (was 0x100, writing 0x10b)
Apr 15 21:50:06 weg kernel: [ 1151.771561] nouveau 0000:01:00.0: restoring
config space at offset 0xc (was 0x0, writing 0xf6e00000)
Apr 15 21:50:06 weg kernel: [ 1151.771568] nouveau 0000:01:00.0: restoring
config space at offset 0x9 (was 0x1, writing 0xdf01)
Apr 15 21:50:06 weg kernel: [ 1151.771574] nouveau 0000:01:00.0: restoring
config space at offset 0x7 (was 0x4, writing 0xf2000004)
Apr 15 21:50:06 weg kernel: [ 1151.771580] nouveau 0000:01:00.0: restoring
config space at offset 0x5 (was 0xc, writing 0xe000000c)
Apr 15 21:50:06 weg kernel: [ 1151.771586] nouveau 0000:01:00.0: restoring
config space at offset 0x4 (was 0x0, writing 0xf5000000)
Apr 15 21:50:06 weg kernel: [ 1151.771592] nouveau 0000:01:00.0: restoring
config space at offset 0x3 (was 0x0, writing 0x10)
Apr 15 21:50:06 weg kernel: [ 1151.771598] nouveau 0000:01:00.0: restoring
config space at offset 0x1 (was 0x100000, writing 0x100007)
Apr 15 21:50:06 weg kernel: [ 1151.771877] iwlagn 0000:0c:00.0: restoring
config space at offset 0xf (was 0x100, writing 0x10a)
Apr 15 21:50:06 weg kernel: [ 1151.772162] iwlagn 0000:0c:00.0: restoring
config space at offset 0x4 (was 0x4, writing 0xf1ffe004)
Apr 15 21:50:06 weg kernel: [ 1151.772219] iwlagn 0000:0c:00.0: restoring
config space at offset 0x3 (was 0x0, writing 0x10)
Apr 15 21:50:06 weg kernel: [ 1151.772298] iwlagn 0000:0c:00.0: restoring
config space at offset 0x1 (was 0x100000, writing 0x100106)
Apr 15 21:50:06 weg kernel: [ 1151.772816] whci 0000:0d:00.0: restoring
config space at offset 0xf (was 0x1ff, writing 0x10b)
Apr 15 21:50:06 weg kernel: [ 1151.772832] whci 0000:0d:00.0: restoring
config space at offset 0x8 (was 0x1, writing 0xce01)
Apr 15 21:50:06 weg kernel: [ 1151.772840] whci 0000:0d:00.0: restoring
config space at offset 0x7 (was 0x1, writing 0xcd01)
Apr 15 21:50:06 weg kernel: [ 1151.772848] whci 0000:0d:00.0: restoring
config space at offset 0x6 (was 0x1, writing 0xcc01)
Apr 15 21:50:06 weg kernel: [ 1151.772858] whci 0000:0d:00.0: restoring
config space at offset 0x4 (was 0x4, writing 0xf1eff004)
Apr 15 21:50:06 weg kernel: [ 1151.772866] whci 0000:0d:00.0: restoring
config space at offset 0x3 (was 0x0, writing 0x10)
Apr 15 21:50:06 weg kernel: [ 1151.772875] whci 0000:0d:00.0: restoring
config space at offset 0x1 (was 0x100000, writing 0x100503)
Apr 15 21:50:06 weg kernel: [ 1151.773138] tg3 0000:09:00.0: restoring
config space at offset 0x3 (was 0x0, writing 0x10)
Apr 15 21:50:06 weg kernel: [ 1151.773148] tg3 0000:09:00.0: restoring
config space at offset 0x1 (was 0x100000, writing 0x100106)
Apr 15 21:50:06 weg kernel: [ 1151.773186] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0xf (was 0x7c001ff, writing 0x5c001ff)
Apr 15 21:50:06 weg kernel: [ 1151.773194] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0xe (was 0x0, writing 0x24fc)
Apr 15 21:50:06 weg kernel: [ 1151.773202] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0xd (was 0x0, writing 0x2400)
Apr 15 21:50:06 weg kernel: [ 1151.773210] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0xc (was 0x0, writing 0x20fc)
Apr 15 21:50:06 weg kernel: [ 1151.773218] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0xb (was 0x0, writing 0x2000)
Apr 15 21:50:06 weg kernel: [ 1151.773226] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0xa (was 0x0, writing 0xf0bff000)
Apr 15 21:50:06 weg kernel: [ 1151.773234] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0x9 (was 0x0, writing 0xf0800000)
Apr 15 21:50:06 weg kernel: [ 1151.773241] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0x8 (was 0x0, writing 0xf07ff000)
Apr 15 21:50:06 weg kernel: [ 1151.773249] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0x7 (was 0x0, writing 0xf0400000)
Apr 15 21:50:06 weg kernel: [ 1151.773257] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0x6 (was 0x20000000, writing 0xb0070403)
Apr 15 21:50:06 weg kernel: [ 1151.773266] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0x4 (was 0x0, writing 0xf1900000)
Apr 15 21:50:06 weg kernel: [ 1151.773274] yenta_cardbus 0000:03:01.0:
restoring config space at offset 0x3 (was 0x820000, writing 0x82a810)
Apr 15 21:50:06 weg kernel: [ 1151.773308] firewire_ohci 0000:03:01.1:
restoring config space at offset 0xf (was 0x4020100, writing 0x402010a)
Apr 15 21:50:06 weg kernel: [ 1151.773325] firewire_ohci 0000:03:01.1:
restoring config space at offset 0x5 (was 0x0, writing 0xf19fc000)
Apr 15 21:50:06 weg kernel: [ 1151.773333] firewire_ohci 0000:03:01.1:
restoring config space at offset 0x4 (was 0x0, writing 0xf19f9000)
Apr 15 21:50:06 weg kernel: [ 1151.773341] firewire_ohci 0000:03:01.1:
restoring config space at offset 0x3 (was 0x800000, writing 0x804010)
Apr 15 21:50:06 weg kernel: [ 1151.773350] firewire_ohci 0000:03:01.1:
restoring config space at offset 0x1 (was 0x2100000, writing 0x2100116)
Apr 15 21:50:06 weg kernel: [ 1151.773369] tifm_7xx1 0000:03:01.2: restoring
config space at offset 0xf (was 0x40701ff, writing 0x407010a)
Apr 15 21:50:06 weg kernel: [ 1151.773387] tifm_7xx1 0000:03:01.2: restoring
config space at offset 0x4 (was 0x0, writing 0xf19fa000)
Apr 15 21:50:06 weg kernel: [ 1151.773395] tifm_7xx1 0000:03:01.2: restoring
config space at offset 0x3 (was 0x800000, writing 0x804010)
Apr 15 21:50:06 weg kernel: [ 1151.773403] tifm_7xx1 0000:03:01.2: restoring
config space at offset 0x1 (was 0x2100000, writing 0x2100106)
Apr 15 21:50:06 weg kernel: [ 1151.773422] sdhci-pci 0000:03:01.3: restoring
config space at offset 0xf (was 0x40701ff, writing 0x407010a)
Apr 15 21:50:06 weg kernel: [ 1151.773440] sdhci-pci 0000:03:01.3: restoring
config space at offset 0x4 (was 0x0, writing 0xf19fb000)
Apr 15 21:50:06 weg kernel: [ 1151.773448] sdhci-pci 0000:03:01.3: restoring
config space at offset 0x3 (was 0x800000, writing 0x804010)
Apr 15 21:50:06 weg kernel: [ 1151.773457] sdhci-pci 0000:03:01.3: restoring
config space at offset 0x1 (was 0x2100000, writing 0x2100106)
Apr 15 21:50:06 weg kernel: [ 1151.773651] PM: early resume of devices
complete after 3.275 msecs
Apr 15 21:50:06 weg kernel: [ 1151.773788] ehci_hcd 0000:00:1a.0: PCI INT A
-> GSI 20 (level, low) -> IRQ 20
Apr 15 21:50:06 weg kernel: [ 1151.773790] HDA Intel 0000:00:1b.0: PCI INT A
-> GSI 21 (level, low) -> IRQ 21
Apr 15 21:50:06 weg kernel: [ 1151.773799] ehci_hcd 0000:00:1a.0: setting
latency timer to 64
Apr 15 21:50:06 weg kernel: [ 1151.773800] HDA Intel 0000:00:1b.0: setting
latency timer to 64
Apr 15 21:50:06 weg kernel: [ 1151.773871] ehci_hcd 0000:00:1d.0: PCI INT A
-> GSI 20 (level, low) -> IRQ 20
Apr 15 21:50:06 weg kernel: [ 1151.773873] HDA Intel 0000:00:1b.0: irq 48
for MSI/MSI-X
Apr 15 21:50:06 weg kernel: [ 1151.773886] pci 0000:00:1e.0: setting latency
timer to 64
Apr 15 21:50:06 weg kernel: [ 1151.773888] ehci_hcd 0000:00:1d.0: setting
latency timer to 64
Apr 15 21:50:06 weg kernel: [ 1151.773899] ahci 0000:00:1f.2: setting
latency timer to 64
Apr 15 21:50:06 weg kernel: [ 1151.773907] [drm] nouveau 0000:01:00.0: We're
back, enabling device...
Apr 15 21:50:06 weg kernel: [ 1151.773956] nouveau 0000:01:00.0: PCI INT A
-> GSI 16 (level, low) -> IRQ 16
Apr 15 21:50:06 weg kernel: [ 1151.773963] pcieport 0000:00:1c.5: wake-up
capability disabled by ACPI
Apr 15 21:50:06 weg kernel: [ 1151.773994] nouveau 0000:01:00.0: setting
latency timer to 64
Apr 15 21:50:06 weg kernel: [ 1151.773996] tg3 0000:09:00.0: PME# disabled
Apr 15 21:50:06 weg kernel: [ 1151.774000] tifm_7xx1 0000:03:01.2: PCI INT A
-> GSI 19 (level, low) -> IRQ 19
Apr 15 21:50:06 weg kernel: [ 1151.774002] [drm] nouveau 0000:01:00.0:
POSTing device...
Apr 15 21:50:06 weg kernel: [ 1151.774004] whci 0000:0d:00.0: setting
latency timer to 64
Apr 15 21:50:06 weg kernel: [ 1151.774006] [drm] nouveau 0000:01:00.0:
Parsing VBIOS init table 0 at offset 0xD741
Apr 15 21:50:06 weg kernel: [ 1151.774014] sdhci-pci 0000:03:01.3: PCI INT A
-> GSI 19 (level, low) -> IRQ 19
Apr 15 21:50:06 weg kernel: [ 1151.774381] sd 0:0:0:0: [sda] Starting disk
Apr 15 21:50:06 weg kernel: [ 1151.775778] sd 2:0:0:0: [sdb] Starting disk
Apr 15 21:50:06 weg kernel: [ 1151.822768] dell-wmi: Received unknown WMI
event (0x11)
Apr 15 21:50:06 weg kernel: [ 1151.829545] firewire_core: skipped bus
generations, destroying all nodes
Apr 15 21:50:06 weg kernel: [ 1151.849580] [drm] nouveau 0000:01:00.0:
Parsing VBIOS init table 1 at offset 0xDCF6
Apr 15 21:50:06 weg kernel: [ 1151.949379] [drm] nouveau 0000:01:00.0:
Parsing VBIOS init table 2 at offset 0xEA6B
Apr 15 21:50:06 weg kernel: [ 1151.949417] [drm] nouveau 0000:01:00.0:
Parsing VBIOS init table 3 at offset 0xEB69
Apr 15 21:50:06 weg kernel: [ 1151.969522] [drm] nouveau 0000:01:00.0:
Parsing VBIOS init table 4 at offset 0xEDE2
Apr 15 21:50:06 weg kernel: [ 1151.969524] [drm] nouveau 0000:01:00.0:
Parsing VBIOS init table at offset 0xEE47
Apr 15 21:50:06 weg kernel: [ 1151.979381] PM: resume of drv:usb dev:1-1
complete after 205.187 msecs
Apr 15 21:50:06 weg kernel: [ 1151.979413] PM: resume of drv:hub dev:1-1:1.0
complete after 205.220 msecs
Apr 15 21:50:06 weg kernel: [ 1151.979432] PM: resume of drv: dev:ep_81
complete after 205.242 msecs
Apr 15 21:50:06 weg kernel: [ 1151.979465] PM: resume of drv: dev:ep_00
complete after 205.219 msecs
Apr 15 21:50:06 weg kernel: [ 1151.999381] [drm] nouveau 0000:01:00.0:
Restoring GPU objects...
Apr 15 21:50:06 weg kernel: [ 1152.059478] usb 1-1.3: reset high speed USB
device using ehci_hcd and address 3
Apr 15 21:50:06 weg kernel: [ 1152.109264] ata1: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Apr 15 21:50:06 weg kernel: [ 1152.139181] ata6: SATA link down (SStatus 0
SControl 300)
Apr 15 21:50:06 weg kernel: [ 1152.159173] ata5: SATA link down (SStatus 0
SControl 300)
Apr 15 21:50:06 weg kernel: [ 1152.175776] PM: resume of drv:usb dev:1-1.3
complete after 400.616 msecs
Apr 15 21:50:06 weg kernel: [ 1152.175785] PM: resume of drv: dev:ep_00
complete after 400.526 msecs
Apr 15 21:50:06 weg kernel: [ 1152.175802] PM: resume of drv:uvcvideo
dev:1-1.3:1.1 complete after 400.568 msecs
Apr 15 21:50:06 weg kernel: [ 1152.175847] PM: resume of drv:uvcvideo
dev:1-1.3:1.0 complete after 400.664 msecs
Apr 15 21:50:06 weg kernel: [ 1152.175867] PM: resume of drv: dev:ep_81
complete after 400.659 msecs
Apr 15 21:50:06 weg kernel: [ 1152.179172] ata3: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Apr 15 21:50:06 weg kernel: [ 1152.193660] [drm] nouveau 0000:01:00.0:
Reinitialising engines...
Apr 15 21:50:06 weg kernel: [ 1152.193768] [drm] nouveau 0000:01:00.0:
Restoring mode...
Apr 15 21:50:06 weg kernel: [ 1152.199223] ata2: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Apr 15 21:50:06 weg kernel: [ 1152.202363] PM: resume of drv:nouveau
dev:0000:01:00.0 complete after 428.639 msecs
Apr 15 21:50:06 weg kernel: [ 1152.204520] ata2.00: configured for UDMA/133
Apr 15 21:50:06 weg kernel: [ 1152.219213] ata4: SATA link down (SStatus 0
SControl 300)
Apr 15 21:50:06 weg kernel: [ 1152.247056] ata1.00: configured for UDMA/133
Apr 15 21:50:06 weg kernel: [ 1152.249452] usb 1-1.6: reset full speed USB
device using ehci_hcd and address 5
Apr 15 21:50:06 weg kernel: [ 1152.298195] ata3.00: configured for UDMA/133
Apr 15 21:50:06 weg kernel: [ 1152.329149] firewire_core: rediscovered
device fw0
Apr 15 21:50:06 weg kernel: [ 1152.397693] PM: resume of drv:sd dev:0:0:0:0
complete after 623.575 msecs
Apr 15 21:50:06 weg kernel: [ 1152.397715] PM: resume of drv:scsi_device
dev:0:0:0:0 complete after 623.414 msecs
Apr 15 21:50:06 weg kernel: [ 1152.397733] PM: resume of drv:scsi_disk
dev:0:0:0:0 complete after 532.595 msecs
Apr 15 21:50:06 weg kernel: [ 1152.433854] PM: resume of drv:sd dev:2:0:0:0
complete after 658.354 msecs
Apr 15 21:50:06 weg kernel: [ 1152.433934] PM: resume of drv:scsi_device
dev:2:0:0:0 complete after 658.368 msecs
Apr 15 21:50:06 weg kernel: [ 1152.439230] usb 1-1.4: reset full speed USB
device using ehci_hcd and address 4
Apr 15 21:50:06 weg kernel: [ 1152.558512] PM: resume of drv:usb dev:1-1.4
complete after 783.390 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558541] PM: resume of drv: dev:ep_00
complete after 783.275 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558565] PM: resume of drv:usb
dev:1-1.4:0.1 complete after 783.354 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558580] PM: resume of drv: dev:ep_02
complete after 783.341 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558593] PM: resume of drv:usb
dev:1-1.4:0.0 complete after 783.448 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558598] PM: resume of drv: dev:ep_86
complete after 783.340 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558618] PM: resume of drv: dev:ep_82
complete after 783.393 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558624] PM: resume of drv: dev:ep_81
complete after 783.454 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558629] PM: resume of drv: dev:ep_85
complete after 783.422 msecs
Apr 15 21:50:06 weg kernel: [ 1152.558646] PM: resume of drv: dev:ep_01
complete after 783.465 msecs
Apr 15 21:50:06 weg kernel: [ 1152.578920] PM: resume of drv:usb dev:1-1.6
complete after 803.646 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579024] PM: resume of drv:hub
dev:1-1.6:1.0 complete after 803.740 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579043] PM: resume of drv: dev:ep_00
complete after 803.730 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579052] PM: resume of drv: dev:ep_81
complete after 803.753 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579375] PM: resume of drv:usb dev:1-1.6.3
complete after 803.851 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579398] PM: resume of drv:usb
dev:1-1.6.3:1.2 complete after 803.764 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579415] PM: resume of drv: dev:ep_00
complete after 803.728 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579421] PM: resume of drv:usb
dev:1-1.6.3:1.3 complete after 803.744 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579436] PM: resume of drv:btusb
dev:1-1.6.3:1.0 complete after 803.899 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579455] PM: resume of drv: dev:ep_81
complete after 803.903 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579461] PM: resume of drv:btusb
dev:1-1.6.3:1.1 complete after 803.865 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579467] PM: resume of drv: dev:ep_82
complete after 803.903 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579477] PM: resume of drv: dev:ep_02
complete after 803.900 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579482] PM: resume of drv: dev:ep_83
complete after 803.873 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579503] PM: resume of drv: dev:ep_03
complete after 803.885 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579509] PM: resume of drv: dev:ep_84
complete after 803.859 msecs
Apr 15 21:50:06 weg kernel: [ 1152.579524] PM: resume of drv: dev:ep_04
complete after 803.866 msecs
Apr 15 21:50:06 weg kernel: [ 1152.594422] dell-wmi: Received unknown WMI
event (0x11)
Apr 15 21:50:06 weg kernel: [ 1152.659149] usb 1-1.6.1: reset full speed USB
device using ehci_hcd and address 6
Apr 15 21:50:06 weg kernel: [ 1152.771378] PM: resume of drv:usb dev:1-1.6.1
complete after 996.132 msecs
Apr 15 21:50:06 weg kernel: [ 1152.771407] PM: resume of drv: dev:ep_00
complete after 996.123 msecs
Apr 15 21:50:06 weg kernel: [ 1152.771540] PM: resume of drv:usbhid
dev:1-1.6.1:1.0 complete after 996.281 msecs
Apr 15 21:50:06 weg kernel: [ 1152.771561] PM: resume of drv: dev:ep_81
complete after 996.288 msecs
Apr 15 21:50:06 weg kernel: [ 1152.771619] PM: resume of drv:generic-usb
dev:0003:413C:8161.0001 complete after 374.024 msecs
Apr 15 21:50:06 weg kernel: [ 1152.849043] usb 1-1.6.2: reset full speed USB
device using ehci_hcd and address 7
Apr 15 21:50:06 weg kernel: [ 1152.938858] PM: resume of drv:pcmcia_socket
dev:pcmcia_socket0 complete after 148.221 msecs
Apr 15 21:50:06 weg kernel: [ 1152.961251] PM: resume of drv:usb dev:1-1.6.2
complete after 1186.031 msecs
Apr 15 21:50:06 weg kernel: [ 1152.961297] PM: resume of drv: dev:ep_00
complete after 1186.036 msecs
Apr 15 21:50:06 weg kernel: [ 1152.961329] PM: resume of drv:usb
dev:1-1.6.2:1.0 complete after 1186.095 msecs
Apr 15 21:50:06 weg kernel: [ 1152.961355] PM: resume of drv: dev:ep_81
complete after 1186.107 msecs
Apr 15 21:50:06 weg kernel: [ 1152.961382] PM: resume of devices complete
after 1188.207 msecs
Apr 15 21:50:06 weg kernel: [ 1152.961725] PM: resume devices took 1.190
seconds
Apr 15 21:50:06 weg kernel: [ 1152.961760] PM: Finishing wakeup.
Apr 15 21:50:06 weg bluetoothd[949]: HCI dev 0 down
Apr 15 21:50:06 weg bluetoothd[949]: Adapter /org/bluez/948/hci0 has been
disabled
Apr 15 21:50:06 weg kernel: [ 1152.961761] Restarting tasks ... done.
Apr 15 21:50:06 weg kernel: [ 1152.968985] video LNXVIDEO:00: Restoring
backlight state
Apr 15 21:50:06 weg kernel: [ 1152.969810] usb 1-1.6.3: USB disconnect,
address 8
Apr 15 21:50:06 weg acpid: client connected from 1080[0:0]
Apr 15 21:50:06 weg acpid: 1 client rule loaded
Apr 15 21:50:06 weg anacron[4108]: Anacron 2.3 started on 2011-04-15
Apr 15 21:50:06 weg anacron[4108]: Normal exit (0 jobs run)
Apr 15 21:50:06 weg kernel: [ 1153.048855] whci-hcd 0000:0d:00.0-1: Wireless
host controller
Apr 15 21:50:06 weg kernel: [ 1153.048916] whci-hcd 0000:0d:00.0-1: new USB
bus registered, assigned bus number 3
Apr 15 21:50:06 weg bluetoothd[949]: HCI dev 0 unregistered
Apr 15 21:50:06 weg bluetoothd[949]: Stopping hci0 event socket
Apr 15 21:50:06 weg bluetoothd[949]: Unregister path: /org/bluez/948/hci0
------------------------------------------------------------------
AFTER HERE IDENTICAL TO SUSPEND-TO-DISK AFTER RESTARTING
------------------------------------------------------------------

Launchpad Janitor (janitor) said : #24

This question was expired because it remained in the 'Open' state without activity for the last 15 days.