[linux-pm] [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > > > But it's not the root cause of the problem either.  The same problem appears if
> > > > the device holding the resume partition gets forced into this "broken suspend"
> > > > state.
> > > 
> > > Well, IMO the state may or may not be broken depending on the device,
> > > so we should not assume it will always be broken.
> > 
> > Not so.  See my previous emails.  The "broken suspend" state is broken
> > by definition.  Maybe you're referring to a different issue ... whether
> > or not its driver would notice that bug.
> 
> It is a bug from your point of view, and I was referring to the fact that it
> apparently doesn't matter for many drivers.

That is, to "whether driver notices".  It's clearly a bug with respect to
how the FREEZE state is defined.  Not all drivers need to notice all bugs.

- Dave


[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux