> Quoting Michael S. Tsirkin <[EMAIL PROTECTED]>: > Subject: Re: [2/6] 2.6.21-rc2: known regressions > > > Quoting Ingo Molnar <[EMAIL PROTECTED]>: > > Subject: Re: [2/6] 2.6.21-rc2: known regressions > > > > > > Michael, > > > > * Michael S. Tsirkin <[EMAIL PROTECTED]> wrote: > > > > > > > 2. First disk access after resume takes a couple of minutes > > > > > (seemed instant with 2.6.20) during this time no new messages show > > > > > on console > > > > > > > > Yeah, there is some problem with SATA resume. It would be beautiful if > > > > the > > > > people who actually see this could narrow it down with bisection. "It > > > > works for me" is clearly the case for many people, but not all. > > > > > > Problem is, there seem to be multiple problems some of which got fixed > > > between rc2 and rc3. With rc2 I didn't get as far as getting to > > > console. > > > > a quick ping: on your box that doesnt resume - if you can log in over > > the network after resume (or somehow run shell commands), does 'date' > > advance properly or not? (or do you not get that far to be able to > > tell?) > > > > Ingo > > I just retested - 'date' does not advance after resume for me. > This is with NO_HZ *not* set. > Sorry it took so long.
Update: just re-tested with 2.6.21-rc4, same behaviour: date does not advance after resume from ram. -- MST - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
