All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	gustavo@padovan.org, johan.hedberg@gmail.com
Subject: 3.4.0-rc7 regression: bluetooth vs. s2ram
Date: Tue, 15 May 2012 15:14:57 +0200	[thread overview]
Message-ID: <20120515131453.GA1936@elf.ucw.cz> (raw)

Hi!

In 3.4-rc7, if I suspend while bnep0 over btusb is connected, then
resume, system dies with a backtrace. (Unfortunately, it is not
exactly easy to capture).

If I suspend without bnep0 active, resume works. 

(This has worked before, but "before" may mean 3.2 in this case).

Can someone test/reproduce this? Ideas?

									Pavel

PS: Under normal suspend/resume, I see these warnings in the
log. Maybe relevant?

ehci_hcd 0000:00:1d.7: GetStatus port:7 status 003002 0  ACK POWER OWNER sig=se0 CSC
usb 5-2: finish reset-resume
uhci_hcd 0000:00:1d.3: port 1 portsc 0093,00
usb 5-1: finish reset-resume
usb 5-2: reset full-speed USB device number 3 using uhci_hcd
usb 5-2: ep0 maxpacket = 8
usb 5-1: reset full-speed USB device number 2 using uhci_hcd
btusb 5-1:1.0: no reset_resume for driver btusb?
btusb 5-1:1.1: no reset_resume for driver btusb?
btusb 5-1:1.0: forced unbind
usb usb2: suspend_rh (auto-stop)
usb usb3: suspend_rh (auto-stop)
usb usb4: suspend_rh (auto-stop)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

             reply	other threads:[~2012-05-15 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 13:14 Pavel Machek [this message]
2012-05-15 13:29 ` 3.4.0-rc7 regression: bluetooth vs. s2ram Oliver Neukum
2012-05-15 18:01   ` Pavel Machek
2012-05-16  9:03     ` Oliver Neukum

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=20120515131453.GA1936@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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.