linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Tim Teulings" <rael@edge.ping.de>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: michal.k.k.piotrowski@gmail.com, rbrito@gmail.com,
	linux-kernel@vger.kernel.org, rjw@sisk.pl,
	linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
	linux-pm@lists.linux-foundation.org
Subject: Re: Sleep problems with kernels >= 2.6.21 on powerpc
Date: Wed, 5 Sep 2007 10:07:54 -0700	[thread overview]
Message-ID: <20070905100754.57ab4e3e.akpm@linux-foundation.org> (raw)
In-Reply-To: <46D72BC6.3020809@edge.ping.de>

> On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <rael@edge.ping.de> wrote:
> Hello!
> 
> > I don't have traces at hand and due to lack of time cannot reproduce it 
> > up to tomorrow. However this hint may speed up your analysis!
> 
> Sorry for the delay, but my desktop PC had an urgent hard disk problem I 
> had to fix ASASP.
> 
> So here is the output from dmesg that suggested to me that firewire 
> might be a problem:

Straightforward regression, two reporters, nothing happening.

> > usb_endpoint usbdev2.2_ep81: PM: suspend 0->2, parent 2-1:1.0 already 2
> > usb_device usbdev1.1: PM: suspend 0->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
> > hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2
> > eth2: Airport entering sleep mode
> > eth0: suspending, WakeOnLan disabled
> > pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> > firewire_ohci: pci_set_power_state failed with -22<3>pci_device_suspend(): pci_suspend+0x0/0x9c [firewire_ohci]() returns -22
> > suspend_device(): pci_device_suspend+0x0/0x98() returns -22
> > Could not suspend device 0002:20:0e.0: error -22
> > eth0: resuming
> > PHY ID: 4061e4, addr: 0
> > eth2: Airport waking up
> > eth2: New link status: Connected (0001)
> > hda: Enabling Ultra DMA 2
> > eth0: Link is up at 100 Mbps, full-duplex.
> > eth0: Pause is disabled
> > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> > hdb: Enabling Ultra DMA 2
> > usb_endpoint usbdev1.1_ep00: PM: resume from 0, parent usb1 still 2
> > usb_endpoint usbdev1.1_ep81: PM: resume from 0, parent 1-0:1.0 still 2
> > usb_device usbdev1.1: PM: resume from 0, parent usb1 still 2
> > Driver sleep failed
> > Sleep rejected by devices
> > adb: starting probe task...
> > adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
> > ADB keyboard at 2, handler 1
> > ADB mouse at 3, handler set to 4 (trackpad)
> > adb: finished probe task...
> > usb_device usbdev1.1: PM: suspend 0->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep81: PM: suspend 0->2, parent 1-0:1.0 already 2
> > hub 1-0:1.0: PM: suspend 2->2, parent usb1 already 2
> > usb_endpoint usbdev1.1_ep00: PM: suspend 0->2, parent usb1 already 2
> > eth2: Airport entering sleep mode
> > eth0: suspending, WakeOnLan disabled
> > Trying to free already-free IRQ 40
> > pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> > firewire_ohci: pci_set_power_state failed with -22<3>pci_device_suspend(): pci_suspend+0x0/0x9c [firewire_ohci]() returns -22

I grepped the whole tree for firewire_ohci and came up blank.  What is it?

But yes, a failed pci_set_power_state() will hurt.  Perhaps this is
a result of some recently-added return-value checking fix but as I
cannot find the dang code I cannot tell.

> > suspend_device(): pci_device_suspend+0x0/0x98() returns -22
> > Could not suspend device 0002:20:0e.0: error -22
> > eth0: resuming
> > PHY ID: 4061e4, addr: 0
> > eth2: Airport waking up
> > eth2: New link status: Connected (0001)
> > hda: Enabling Ultra DMA 2
> > hdb: Enabling Ultra DMA 2
> > eth0: Link is up at 100 Mbps, full-duplex.
> > eth0: Pause is disabled
> 
> The problem wa sinitiated by closing the lid. The iBook then seems to 
> permanetly try to go to sleep (I can hear the cd-rom drive get 
> periodically initialized). So above contains more than one iteration.
> 
> The kernel is:
> > Linux kismet 2.6.22-1-powerpc #1 Sun Jul 29 13:58:06 CEST 2007 ppc GNU/Linux
> 
> The relveant debian package:
> > linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb
> 
> I'm running a mixture of debian testing/unstable.
> 
> The firewire and the USB connector were unused, the network connector 
> was used.
> 
> If there are questions regarding other packages, or somebody wants me to 
> test a fix (I would prever a debian package), don't hesitate - I would 
> like to get the bug fixed :-)
> 

  reply	other threads:[~2007-09-05 17:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26  2:37 Sleep problems with kernels >= 2.6.21 on powerpc Rogério Brito
2007-08-26 23:21 ` Michal Piotrowski
2007-08-27  6:52   ` Rogério Brito
2007-08-27  7:14     ` Tim Teulings
2007-08-30 20:42       ` Tim Teulings
2007-09-05 17:07         ` Andrew Morton [this message]
2007-09-05 17:28           ` Randy Dunlap
2007-09-05 17:43             ` Stefan Richter
2007-09-05 17:58               ` Randy Dunlap
2007-09-05 17:47           ` Stefan Richter
2007-09-05 18:06             ` [PATCH] " Stefan Richter
2007-09-05 18:24               ` Stefan Richter
2007-09-05 19:01             ` firewire in prebuilt kernel packages (was Re: Sleep problems with kernels >= 2.6.21 on powerpc) Stefan Richter
2007-09-05 19:44             ` Sleep problems with kernels >= 2.6.21 on powerpc Andrew Morton
2007-09-05 20:12               ` Stefan Richter
2007-09-06  7:50                 ` [PATCH update] " Stefan Richter
2007-08-27  8:37     ` Michel Dänzer
2007-08-27  9:55     ` Pavel Machek

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=20070905100754.57ab4e3e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=rael@edge.ping.de \
    --cc=rbrito@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=stefanr@s5r6.in-berlin.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).