Re: 2.6.21-rc1: known regressions (v2) (part 2)

2007-02-27 Thread Mike Galbraith
On Tue, 2007-02-27 at 09:33 +0100, Ingo Molnar wrote: > * Michal Piotrowski <[EMAIL PROTECTED]> wrote: > > > Thomas Gleixner napisał(a): > > > Adrian, > > > > > > On Mon, 2007-02-26 at 23:05 +0100, Adrian Bunk wrote: > > >> Subject: kernel BUG at kernel/time/tick-sched.c:168 (CONFIG_NO_HZ) >

Re: 2.6.21-rc1: known regressions (v2) (part 2)

2007-02-27 Thread Ingo Molnar
* Michal Piotrowski <[EMAIL PROTECTED]> wrote: > Thomas Gleixner napisał(a): > > Adrian, > > > > On Mon, 2007-02-26 at 23:05 +0100, Adrian Bunk wrote: > >> Subject: kernel BUG at kernel/time/tick-sched.c:168 (CONFIG_NO_HZ) > >> References : http://lkml.org/lkml/2007/2/16/346 > >> Submitter

Re: 2.6.21-rc1: known regressions (v2) (part 2)

2007-02-27 Thread Michal Piotrowski
Michal Piotrowski napisał(a): > Thomas Gleixner napisał(a): >> Adrian, >> >> On Mon, 2007-02-26 at 23:05 +0100, Adrian Bunk wrote: >>> Subject: kernel BUG at kernel/time/tick-sched.c:168 (CONFIG_NO_HZ) >>> References : http://lkml.org/lkml/2007/2/16/346 >>> Submitter : Michal Piotrowski <[EMA

Re: 2.6.21-rc1: known regressions (v2) (part 2)

2007-02-27 Thread Michal Piotrowski
Thomas Gleixner napisał(a): > Adrian, > > On Mon, 2007-02-26 at 23:05 +0100, Adrian Bunk wrote: >> Subject: kernel BUG at kernel/time/tick-sched.c:168 (CONFIG_NO_HZ) >> References : http://lkml.org/lkml/2007/2/16/346 >> Submitter : Michal Piotrowski <[EMAIL PROTECTED]> >> Handled-By : Thomas

Re: 2.6.21-rc1: known regressions (v2) (part 2)

2007-02-27 Thread Thomas Gleixner
Adrian, On Mon, 2007-02-26 at 23:05 +0100, Adrian Bunk wrote: > Subject: kernel BUG at kernel/time/tick-sched.c:168 (CONFIG_NO_HZ) > References : http://lkml.org/lkml/2007/2/16/346 > Submitter : Michal Piotrowski <[EMAIL PROTECTED]> > Handled-By : Thomas Gleixner <[EMAIL PROTECTED]> > Status

2.6.21-rc1: known regressions (v2) (part 2)

2007-02-26 Thread Adrian Bunk
This email lists some known regressions in 2.6.21-rc1 compared to 2.6.20 that are not yet fixed in Linus' tree. If you find your name in the Cc header, you are either submitter of one of the bugs, maintainer of an affectected subsystem or driver, a patch of you caused a breakage or I'm considering