Re: 2.6.16-rc4: known regressions

[Adrian Bunk]

On Wed, Feb 22, 2006 at 02:55:10PM +0800, Yu, Luming wrote:
> > >Subject    : S3 sleep hangs the second time - 600X
> >> >References : http://bugzilla.kernel.org/show_bug.cgi?id=5989
> >> >Submitter  : Sanjoy Mahajan <sanjoy@xxxxxxxxxxxxxx>
> >> >Status     : problematic commit identified,
> >> >             further discussion is in the bug
> >> 
> >> The real problem is there are some bugs hidden by ec_intr=0.
> >> ec_intr=1 just get these bug  just exposed, and we need to fix them. 
> >
> >From a users' point of view, these are regressions from 
> >2.6.15, and not 
> >all of them might be fixed in time for 2.6.16.
> >
> >What is a possible short term solution/workaround for 2.6.16?
> 
> ec_intr=0 is a reasonable workaround for this box,
> if we couldn't root-cause and fix the real problem on time.
> 
> >Can we go back to default to polling mode in 2.6.16?
> 
> No, don't do this.  There are other laptops need this. And I didn't
> get regression report that is root-caused to enabling ec_intr=1 by
> default. If you argue bug 5989, 6075 could be,  I think
> the truth is, for 5989, we need to fix thermal and processor driver
> issue.

We do both agree that defaulting to polling mode is not a long term 
solution.

The question is what to do until it's resolved - assuming that issues 
like 5989 might not be fixed in time for 2.6.16.

Breaking setups working with the defaults under 2.6.15 in 2.6.16 doesn't 
sound that good.

> for 6075, we need to fix interrupt issue.

As far as I understand 6075, the submitter already tried ec_intr=0 
without success.

> So far, I don't think we need o fall back.
> 
> Thanks,
> Luming

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/