Pavel Machek wrote: > Hi! > >>>> So if you have reported a regression in the 2.6.21-rc >>>> series, please check 2.6.21-rc5, and update your >>>> report as appropriate (whether fixed or "still >>>> problems with xyzzy"). >>> [just got back from vacation, or would have sent this >>> earlier] >>> >>> FWIW, I'm still leaning towards disabling libata ACPI >>> support by default for 2.6.21. >>> >>> Upstream has Alan's fix for the worst PATA problems, >>> but for different reasons, I think PATA ACPI and SATA >>> ACPI support in libata does not feel quite ready for >>> prime time in 2.6.21. >>> >>> Scream now, or hold your peace until 2.6.22... :) >> I second disabling ACPI for 2.6.21. > > Ugh.. does that mean we'll have 'regression reports' as in 'it worked > ok in -rc5, broken in final? > > Well, suspend is currently so broken that we'll be flooded by reports, > anyway, but.... could we get at least define in code so that we can > tell users to flip it?
Just the default value for libata.noacpi is changed to 1, so user can easily reenable it by passing boot/module parameter. -- tejun - 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/
