> Does this still occur with 2.6.30? yes > If so, can you pin down which init script triggers the failure? sure, as soon as I find the init script, I'll update the bug report.