Re: Call traces w/ 2.6.35.2 (not w/ 2.6.35.1 plus 2.6.35.2-rc1)

[Sedat Dilek]

On Sat, Aug 14, 2010 at 3:42 PM, Greg KH <gregkh@xxxxxxx> 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@tbox:~/src/linux-2.6/patches/upstream$ cat patch-2.6.35.1
>> patch-2.6.35.2-rc1 > new.patch
>>
>> sd@tbox:~/src/linux-2.6/patches/upstream$ grep "diff --git" new.patch | wc -l
>> 132
>>
>> sd@tbox:~/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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/