linux-kernel - Re: [Regression] firewire_ohci causes system resume to fail

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 17 Dec 2010 00:47:56 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"Linux-pm mailing list" <linux-pm@...ts.linux-foundation.org>,
	Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: [Regression] firewire_ohci causes system resume to fail

On Sunday, December 05, 2010, Stefan Richter wrote:
> On Dec 05 Stefan Richter wrote:
> > On Dec 05 Rafael J. Wysocki wrote:
> > > There is a regression I can reproduce 100% of the time on a AMD-based desktop
> > > box that resume from hibernation (or suspend) fails because of the firewire_ohci
> > > module.  The box just hangs when firewire_ohci resume runs, apparently, and it
> > > is sufficient to do:
> > > 
> > > # echo devices > /sys/power/pm_test
> > > # echo disk > /sys/power/state
> > > 
> > > to reproduce the issue.
> > 
> > Do you have anything attached to the FireWire bus?  What controller do
> > you have?
> 
> I just now tested the above on an Intel Mac mini, running
> unmodified 2.6.37-rc4 x86-32, without and with a camera on the FireWire
> port, and could not reproduce the problem.  I also got an AMD based PC
> here with an array of different FireWire controllers which I shall make
> available to the same test...

I'm unable to reproduce the problem with 2.6.37-rc6, so presumably this was
a temporary glitch with the particular kernel build.

Thanks,
Rafael
--
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/