All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kristian Grønfeldt Sørensen" <kriller@vkr.dk>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: "BUG:" when resuming from suspend-to-ram
Date: Tue, 27 Feb 2007 23:23:49 +0100	[thread overview]
Message-ID: <1172615029.4865.7.camel@localhost.localdomain> (raw)
In-Reply-To: <200702272304.01756.rjw@sisk.pl>

On Tue, 2007-02-27 at 23:04 +0100, Rafael J. Wysocki wrote:
> Hi,
> 
> On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> > Hi.
> > 
> > PROBLEM: "BUG:" when resumimg from suspend-to-ram 
> > 	
> > My laptop have a problem with resuming from suspend-to-ram. 
> > It does not occur every time - most of the time, resume works without
> > any problem.at all.
> > 
> > After it occurs, the laptop refuses to go into suspend-to-ram mode until
> > next reboot.
> 
> What do you mean by "refuses"?  

As in it does not suspend when i close the lid. It just stays on.

> Are there any suspicious messages in
> dmesg?

No: This what i get just after the stacktrace: 

video bus notify
video bus notify
video bus notify
video bus notify
video bus notify
video bus notify
video bus notify
video bus notify
DEV: Unregistering device. ID = 'vcs7'
PM: Removing info for No Bus:vcs7
device_create_release called for vcs7
DEV: Unregistering device. ID = 'vcsa7'
PM: Removing info for No Bus:vcsa7
device_create_release called for vcsa7
DEV: registering device: ID = 'vcs7'
PM: Adding info for No Bus:vcs7
DEV: registering device: ID = 'vcsa7'
PM: Adding info for No Bus:vcsa7
DEV: Unregistering device. ID = 'vcs7'
PM: Removing info for No Bus:vcs7
device_create_release called for vcs7
DEV: Unregistering device. ID = 'vcsa7'
PM: Removing info for No Bus:vcsa7
device_create_release called for vcsa7


The "video bus notify" lines is from attempts to suspend the machine
once again, but as I described above, nothing happens - the computer
stays on.
The rest is from switches between VT's and X.

> > The system is a Debian unstable running with a self-compiled 2.6.20
> > kernel downloaded from kernel.org. 
> > 
> > I've only tried suspend-to-ram on 2.6.20 so I don't know whether or not
> > other versions might have the same problem.
> > 
> > I'm not subscribed to the list. Please CC me.
> 
> I guess one of the drivers you use goes awry at some point.  Please provide
> us with more information (like dmesg output after a failing resume).

See the above dmesg snippet.

/Kristian


  reply	other threads:[~2007-02-27 22:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 18:45 PROBLEM: "BUG:" when resuming from suspend-to-ram Kristian Grønfeldt Sørensen
2007-02-27 22:04 ` Rafael J. Wysocki
2007-02-27 22:23   ` Kristian Grønfeldt Sørensen [this message]
2007-02-27 22:34     ` Rafael J. Wysocki
2007-02-27 23:12       ` Kristian Grønfeldt Sørensen
2007-02-28  0:05         ` Rafael J. Wysocki
2007-02-28  0:33           ` Kristian Grønfeldt Sørensen
2007-02-27 22:30   ` Rafael J. Wysocki
2007-02-27 22:30     ` Rafael J. Wysocki
2007-02-28  0:27     ` Kristian Grønfeldt Sørensen
2007-02-28 12:45       ` Rafael J. Wysocki
2007-03-01  5:36         ` Dmitry Torokhov
2007-03-01 14:55           ` Kristian Grønfeldt Sørensen
2007-03-01 15:01             ` Dmitry Torokhov
2007-03-01 16:23               ` Kristian Grønfeldt Sørensen
2007-03-01 20:04           ` Kristian Grønfeldt Sørensen
2007-03-01 20:25             ` Dmitry Torokhov
2007-03-01 20:34               ` Kristian Grønfeldt Sørensen
2007-03-05 14:44                 ` Dmitry Torokhov
2007-03-05 18:32                   ` Rafael J. Wysocki
2007-03-05 20:51                     ` Kristian Grønfeldt Sørensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1172615029.4865.7.camel@localhost.localdomain \
    --to=kriller@vkr.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.