lkml.org 
[lkml]   [2008]   [Jun]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Oops report for the week preceding June 16th, 2008

* David Miller <davem@davemloft.net> wrote:

> From: Ingo Molnar <mingo@elte.hu>
> Date: Tue, 17 Jun 2008 17:33:56 +0200
>
> > v2.6.24 was no doubt a huge step in the right direction but it came
> > too late and we are still suffering from the fallout today as we
> > have not reached test cycle equilibrium yet: by the time mainline
> > gets the patches a new large batch comes up, invalidating much of
> > mainline's role and forcing distros to gamble with (much untested
> > and thus detached from reality) experimental branches.
> >
> > That's my main point: when we mess up and dont merge OSS driver code
> > that was out there in time - and we messed up big time with wireless
> > - we should admit the screwup and swallow the bitter pill.
>
> Your point seems to be that, even though we've acknowledged and
> entirely corrected the problem now, you still will whack us over the
> head and complain because it took in your opinion too long to get to
> that point.

from the discussion it was not at all clear to me that you appear to
agree with me - all i saw really was that you tried to ridicule my
position.

> How nice. That makes the wireless folks feel great I imagine.

my only worry was about the current situation, which, according to
kerneloops.org, with 17442 oopses reported against v2.6.25, isnt
anything to feel too great about. (And that's not limited to wireless in
any way - there is a rather prominent tick_broadcast_oneshot_control()
soft lockup entry as well that we are trying to figure out.)

It will all get better i'm sure - we now finally have objective
visibility of bugs as they happen to users.

Ingo


\
 
 \ /
  Last update: 2008-06-19 02:25    [from the cache]
©2003-2011 Jasper Spaans