On Tue, Aug 06, 2013 at 02:02:24PM -0700, Kent Overstreet wrote: > On Tue, Aug 06, 2013 at 01:56:50PM -0700, Darrick J. Wong wrote: > > Ok, I've narrowed it down a little bit -- > > > > It's not caused by any of the fixes that went into 3.10.[1-5]. It doesn't > > seem > > to be specific to any particular storage bus, controller, disk, or even > > cache > > set -- the same bcache'd usb stick will crash my laptop and not crash my > > test > > box. The 4k/512b sector thing was a red herring; you can ignore that. > > Ok, that makes more sense... > > > The test box is a boring old Core2 box; the laptop is an Ivy Bridge. I'll > > try > > to enable more verbose PM debugging to see if I can determine what exactly's > > going on at sleep time. (Again, shooting in the dark...) > > I just looked at the code and it appears there was a freezer fix that > didn't make it into 3.10 and should have. Can you try the > bcache-for-3.11 branch and see if that fixes it? If so, I'll get that > patch sent out for stable.
The suspend problem seems to be gone with the for-3.11 branch. The branch seems to be based off 3.10-rc7... is that correct? Also, is there any way to figure out how much of a cache device is actively holding cached data? --D -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
