On Thursday, 7 June 2007 17:20, David Greaves wrote: > Mark Lord wrote: > > Tejun Heo wrote: > >> > >> Can you setup serial console and/or netconsole (not sure whether this > >> would work tho)? > > > > Since he has good console output already, capturable by digicam, > > I think a better approach might be to provide a patch with extra > > instrumentation.. > > You know.. progress messages and the like, so we can see at what step > > things stop working. Or would that not help ? > > > > David, does scrollback work on your dead console? > > hmmmm, scrollback doesn't currently _do_ anything. > > But the messages didn't scroll there, they just appear (as the memory is > restored I assume). The same messages appear during the fail-to-suspend case too. > > Linus said at one point: > > Ok, it wasn't a hidden oops. The DISABLE_CONSOLE_SUSPEND=y thing sometimes > > shows oopses that are otherwise hidden, but at other times it just causes > > more problems (hard hangs when trying to display something on a device > > that is suspended, or behind a bridge that got suspended). > > > In your case, the screen output just shows normal resume output, and it > > apparently just hung for some unknown reason. It *may* be worth trying to > > do a SysRQ + 't' thing to see what tasks are running (or rather, not > > running), but since you won't be able to capture it, it's probably not > > going to be useful. > > So I've since removed DISABLE_CONSOLE_SUSPEND=y > Should I put it back? I would do that. Apart from this, your observations don't directly imply that XFS is to blame here. It might be involved somehow, but it's also possible that RAID6 alone would suffice to trigger the problem. Greetings, Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
