linux-kernel - Re: [REGRESSION]: hibernate/sleep regression w/ bisection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Nov 2011 08:59:56 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Andrew Watts <akwatts@...il.com>, linux-kernel@...r.kernel.org,
	linux-pm@...ts.linux-foundation.org
Subject: Re: [REGRESSION]: hibernate/sleep regression w/ bisection

Hello,

On Wed, Nov 02, 2011 at 09:31:09AM -0700, Dmitry Torokhov wrote:
> On Wed, Nov 02, 2011 at 11:02:09AM -0500, Andrew Watts wrote:
> > On Tue, Nov 01, 2011 at 10:46:58PM -0700, Dmitry Torokhov wrote:
> > > 
> > > Are you hibernating from text console or X? Can you try plugging in USB
> > > keyboard and see if you are getting input? What about ssh into the box?
> > 
> > Forgot to answer a few of your questions. Plugging in a USB keyboard does
> > not help.
> 
> OK, it looks like you do have input, what you do not have is X
> functioning.
> 
> I am not sure why radeon reports lockup with that patch; serio uses
> system_long_wq to schedule its long-playing works and the only other
> user of system_long_wq seems to be sata, but then concurrency management
> should take care of them sharing the workqueue.
> 
> Tejun, do you have any ideas here?

Not at all.  Dang, I was feeling pretty sure that it was some missing
queue_work somewhere.  So, input is working fine but X locks up
because of that change?  That's just odd.

Andrew, just in case, can you please double check that you're
reverting only that single commit (not all the ones afterwards) and
the test results?  If they're all okay, can you please trigger the
problem, wait a while, trigger sysrq-t and attach the kernel log?

Thank you.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/