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:	Sun, 11 Oct 2009 17:59:45 +0200
From:	Robert Jarzmik <robert.jarzmik@...e.fr>
To:	Pavel Machek <pavel@....cz>
Cc:	rpurdie@...ys.net, lenz@...wisc.edu,
	kernel list <linux-kernel@...r.kernel.org>,
	Dirk@...er-Online.de, arminlitzel@....de,
	Cyril Hrubis <metan@....cz>, thommycheck@...il.com,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	dbaryshkov@...il.com, omegamoon@...il.com, eric.y.miao@...il.com,
	utx@...guin.cz
Subject: Re: zaurus suspend saga: 2.6.32-rc3

Pavel Machek <pavel@....cz> writes:

> Hi!
>
> I'm using patch similar to this for debugging:
>
> ...and good news is that it blinks after pressing of power button.
>
> ...core > pm_test also works.
>
> I also verified that end of pxa_pm_enter() is reached (with similar
> blinking patch). End of corgi_pxa_pm_enter() seems to be reached, too.
>
> Any ideas what to try next?
> 								Pavel

For the Mitac MIO A701 board, with a similar problem, I had :
 - removed almost all drivers (except screen and USB for control)
 - realized that the culprit was amongst drivers (which resumed in a loop in
 that time, should be the same now)
 - added some way to find which one failed (in my case, I chose morse code
 through the buzzer to "speak" the device's name)
 - found out the driver faulty code
 - fixed it
 - retried, cheered.

As soon as you reach a resumed screen, it becomes easier :)

That's a very tedious and long fight, good luck.

Cheers

--
Robert
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ