All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Frans Pop <elendil@planet.nl>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately
Date: Tue, 16 Jun 2009 19:13:51 +0200	[thread overview]
Message-ID: <1245172431.6210.1.camel@localhost> (raw)
In-Reply-To: <alpine.LNX.2.00.0906161014550.7457@wotan.suse.de>

Am Dienstag, den 16.06.2009, 10:15 +0200 schrieb Jiri Kosina:
> On Mon, 15 Jun 2009, Thomas Meyer wrote:
> 
> > > > As for the mouse itself, I don't know.  I'm not even sure if it's 
> > > > possible at all (CCing Jiri).
> > > The main question is whether the mouse really is generating wakeup event 
> > > even if unused.
> > > Could you please provide usbmon dumps (Documentation/usb/usbmon.txt) from 
> > > the failing suspend session?
> > I tried and usbmon seems to kill my machine. See attached screenshot.
> 
> Unfortunately the trace is far from being complete -- most importantly, 
> the first lines of the oops/BUG are missing. Is there any chance you could 
> either set up a serial console, or choose a smaller console font, to catch 
> the whole thing?

Netconsole was able to catch this:

[ 8689.244202] BUG: unable to handle kernel paging request at ffff880020fb0e80
[ 8689.244235] IP: [<ffffffffa002d47f>] mon_dmapeek+0x68/0x8d [usbmon]
[ 8689.244265] PGD 202063 PUD 206063 PMD 20e001e2 
[ 8689.244293] Oops: 0000 [#1] PREEMPT SMP 
[ 8689.244318] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
[ 8689.244329] CPU 0 

That's all.

Is this useful for you?


  reply	other threads:[~2009-06-16 17:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 16:13 2.6.30: suspend-to-ram, second s2r wakes up immediately Thomas Meyer
2009-06-14 16:28 ` Rafael J. Wysocki
2009-06-14 16:44   ` Thomas Meyer
2009-06-14 17:01     ` Rafael J. Wysocki
2009-06-14 18:31       ` Frans Pop
2009-06-14 18:57         ` Rafael J. Wysocki
2009-06-15 15:37           ` Thomas Meyer
2009-06-14 19:07         ` Thomas Meyer
2009-06-14 19:29           ` Rafael J. Wysocki
2009-06-14 20:44             ` Alan Stern
2009-06-14 20:50             ` Jiri Kosina
2009-06-15 16:29               ` Thomas Meyer
2009-06-16  8:15                 ` Jiri Kosina
2009-06-16 17:13                   ` Thomas Meyer [this message]
2009-06-16 14:26                 ` Alan Stern
2009-06-16 17:47                   ` Thomas Meyer
2009-06-16 18:50                     ` Alan Stern
2009-06-17 21:50                       ` Thomas Meyer
2009-06-17 22:24                         ` Frans Pop
2009-06-29 17:30                           ` Thomas Meyer
2009-06-17 22:53                         ` Alan Stern
2009-06-29 18:13                           ` Thomas Meyer
2009-06-29 20:16                             ` Alan Stern

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=1245172431.6210.1.camel@localhost \
    --to=thomas@m3y3r.de \
    --cc=elendil@planet.nl \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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.