Re: 2.6.13-mm1: swsusp problem (was: PCMCIA problem)

Rafael J. Wysocki
2005-09-02T12:17:26Z

On Friday, 2 of September 2005 13:45, Rafael J. Wysocki wrote:
> On Friday, 2 of September 2005 13:09, Andrew Morton wrote:
> > Pavel Machek <pavel@suse.cz> wrote:
> > >
> > > > One more piece of information. This is the one that loops:
> > > >
> > > > echo 30 > /sys/class/firmware/timeout
> > >
> > > Try echo -n ...
> >
> > Or revert gregkh-driver-sysfs-strip_leading_trailing_whitespace.patch.
> > Obviously if you write 30\n and the write returns 2 then the shell will
> > then try to write the \n. That returns zero and the shell tries again, ad
> > infinitum.
> >
> > Rant. It took me two full days to weed out and fix all the crap people
> > sent me to get -mm1 into a state where it vaguely compiled and booted. And
> > it's untested nonsense like this which wrecks the whole effort for many
> > testers.
> >
> > I suppose this is as good as anything....
>
> Thanks for the fix. :-)
>
> Now, (using the fact that Pavel already is in the CC list ;-)) there's another
> issue I have with swsusp, which is broken in a funny way. Namely, after
> resuming from disk the box immediately goes into standby from which it
> can be woken up by pressing the power button, but then it oopses,
> goes into standby (or something similar) again, and hangs solid (unfortunately
> I can't get the traces right now).

Sorry for the noise. This problem has been fixed by the same patch (ie suspend
is initiated by writing a string to a file on sysfs etc.).

Greetings,
Rafael

--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"