[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=+=2GEiC_WASfxC2u_xeTe4xdrZzLBs5Q1j3b7@mail.gmail.com>
Date: Sat, 14 Aug 2010 17:40:55 +0200
From: Sedat Dilek <sedat.dilek@...glemail.com>
To: Greg KH <gregkh@...e.de>
Cc: LKML <linux-kernel@...r.kernel.org>, wylda@...ny.cz
Subject: Re: Call traces w/ 2.6.35.2 (not w/ 2.6.35.1 plus 2.6.35.2-rc1)
On Sat, Aug 14, 2010 at 3:42 PM, Greg KH <gregkh@...e.de> wrote:
> On Sat, Aug 14, 2010 at 08:20:26AM +0200, Sedat Dilek wrote:
>> Hi Greg,
>>
>> looks like 2.6.35.2 misses some fixes from 2.6.35.2-rc1?
>
> Huh? I don't understand what you are trying to show here at all.
>
>> sd@...x:~/src/linux-2.6/patches/upstream$ cat patch-2.6.35.1
>> patch-2.6.35.2-rc1 > new.patch
>>
>> sd@...x:~/src/linux-2.6/patches/upstream$ grep "diff --git" new.patch | wc -l
>> 132
>>
>> sd@...x:~/src/linux-2.6/patches/upstream$ grep "diff --git"
>> patch-2.6.35.2 | wc -l
>> 128
>>
>> Unfortunately, a kernel patched w/ 2.6.35.2 causes Call traces here.
>
> And these are also showing up on Linus's tree right now as well? Have
> you reported them?
>
Shall I open a separate BR for 2.6.35-gitX?
I can confirm the problem occured in the first time in git12 (saw it
in git14 and git15).
As I have currently a slow system, I won't do a bisect or X-times
kernel-builds, sorry for that.
Each build takes me around 2hrs.
- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists