linux-kernel - Re: [PATCH] Re: Sleep problems with kernels >= 2.6.21 on powerpc

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:	Wed, 05 Sep 2007 20:24:14 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Rogério Brito <rbrito@...il.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Tim Teulings <rael@...e.ping.de>,
	michal.k.k.piotrowski@...il.com, linux-kernel@...r.kernel.org,
	linuxppc-dev@...abs.org, debian-powerpc@...ts.debian.org,
	rjw@...k.pl, linux-pm@...ts.linux-foundation.org,
	Kristian Høgsberg 
	<krh@...hat.com>
Subject: Re: [PATCH] Re: Sleep problems with kernels >= 2.6.21 on powerpc

Rogério Brito wrote on 2007-08-27:
> If things progress well, I will incrementally include features on the
> kernel that I need (I left out, for instance, the Firewire subsystem, so
> that compilation wouldn't take more than an hour here, despite the fact
> that I do need Firewire support on the kernel) and see the point where
> things are not normal.

The trivial pci_set_power_state issue aside, resume is currently
defective with the new firewire-ohci driver:
  - The version in Linus' tree doesn't restore a certain detail of
    IEEE 1394 state during resume, hence some protocols like SBP-2 don't
    work after resume unless you unload and reload the drivers.
  - The version in -mm restores everything but panics soon after resume
    on an APM notebook in combination with some SBP-2 targets.  I have
    yet to try netconsole or so to gather more information.
-- 
Stefan Richter
-=====-=-=== =--= --=-=
http://arcgraph.de/sr/
-
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/