public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: resume regression in 2.6.37
Date: Thu, 13 Jan 2011 18:33:41 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1101131827080.2678@localhost6.localdomain6> (raw)
In-Reply-To: <1294938961.10740.24.camel@sven>

On Thu, 13 Jan 2011, Sven Neumann wrote:
> On Thu, 2011-01-13 at 17:28 +0100, Thomas Gleixner wrote:
> > On Thu, 13 Jan 2011, Sven Neumann wrote:
> > > Any idea on how to proceed from here? I don't think I can just revert
> > > this commit and expect things to work, right?
> > 
> > Well, I somehow doubt, that this is the real culprit. The patch does
> > not change anything of the set_wake() functionality. It's a functional
> > equivivalent wrapper, nothing else.
> > 
> > Can you revert it on top of 2.6.37 and verify that it helps ?
> 
> I've done that now and while it doesn't solve the problem completely, I
> can definitely say that reverting the change does make a difference. 

Hmm. I have to admit that this confuses the hell out of me.

> Without the revert there is absolutely no sign of resume. With the
> change reverted I can see that the PXA powers up again, there's an LED
> showing that the USB controller has power again. Unfortunately there's
> seems to be another problem and the resume doesn't complete. I've tried
> to get console output by using no_console_suspend, but there's just
> gibberish on the console after resume :(
> 
> Any idea on how to proceed from here? I could perhaps ask our hardware
> engineer to try find out where exactly we are stuck in the resume. But
> I'd like to avoid that if possible.

Can you stick a printk into the set_wake() function of that irq chip
and print the irq and on arguments and the return value . Run that
with both stock 2.6.37 and the patch reverted.

Thanks,

	tglx

  reply	other threads:[~2011-01-13 17:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 15:44 resume regression in 2.6.37 Sven Neumann
2011-01-13 16:28 ` Thomas Gleixner
2011-01-13 17:16   ` Sven Neumann
2011-01-13 17:33     ` Thomas Gleixner [this message]
2011-01-17 10:36       ` Sven Neumann
2011-01-17 12:40         ` Thomas Gleixner
2011-01-17 14:04           ` Sven Neumann
2011-01-17 18:41             ` Thomas Gleixner
2011-01-17 19:24           ` Lars-Peter Clausen
2011-01-17 19:59             ` Lars-Peter Clausen
2011-01-18  8:16               ` Sven Neumann
2011-01-18  8:18                 ` [PATCH] pxa3xx: fix PXA GPIO IRQ handling Sven Neumann
2011-01-18 11:06                   ` Uwe Kleine-König
2011-01-18 11:47                   ` Lars-Peter Clausen
2011-01-18 12:29                     ` [PATCH] ARM: pxa: fix " Sven Neumann
2011-01-18 16:15                     ` [PATCH] pxa3xx: fix PXA " Eric Miao
2011-01-18 16:20                       ` Lennert Buijtenhek
2011-01-18 21:49                       ` Sven Neumann
2011-01-20 18:48                         ` Eric Miao
2011-01-20 18:55                           ` Eric Miao
2011-01-18  8:19             ` resume regression in 2.6.37 Thomas Gleixner

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=alpine.LFD.2.00.1101131827080.2678@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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