Re: [1/2] 2.6.22-git: known regressions

From: Gabriel C
Date: Thu Jul 19 2007 - 13:17:22 EST


Satyam Sharma wrote:
> On 7/19/07, Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:
>
>
>> Subject : Section mismatch: reference to .init.data:cpu_llc_id (between 'set_cpu_sibling_map' and 'initialize_secondary')
>> References : http://lkml.org/lkml/2007/7/19/202
>> Last known good : ?
>> Submitter : Gabriel C <nix.or.die@xxxxxxxxxxxxxx>
>> Caused-By : Jeremy Fitzhardinge <jeremy@xxxxxxxxxxxxx>
>> commit c70df74376c1e29a04e07e23dd3f4c384d6166dd
>> Handled-By : ?
>> Status : unknown
>>
>
> Fixed by Jeremy Fitzhardinge, see:
>
> http://lkml.org/lkml/2007/7/18/410
>
> Dunno if it's in latest git.
>

No is not.

>
>> Subject : Oops while modprobing phy fixed module
>> References : http://lkml.org/lkml/2007/7/14/63
>> Last known good : ?
>> Submitter : Gabriel C <nix.or.die@xxxxxxxxxxxxxx>
>> Caused-By : Tejun Heo <htejun@xxxxxxxxx>
>> commit 3007e997de91ec59af39a3f9c91595b31ae6e08b
>> Handled-By : Satyam Sharma <satyam.sharma@xxxxxxxxx>
>> Tejun Heo <htejun@xxxxxxxxx>
>> Status : unknown
>>
>
>
> This thread consisted of two unrelated/different oops stack traces :-)
>
> One of them was fixed by Tejun,
> a1da4dfe35bc36c3bc9716d995c85b7983c38a76
>
> The other is SLUB related, I think.
>
>

Yes SLAB/SLUB traces.

I will test the SLAB fix ( noone told me is fixed ) and I'll test the
same with SLUB to see whatever is fixed in current git , later.

>> Block layer
>>
>> Subject : broken {sd,hd}parm
>> References : http://lkml.org/lkml/2007/7/16/389
>> Last known good : ?
>> Submitter : Gabriel C <nix.or.die@xxxxxxxxxxxxxx>
>> Caused-By : ?
>> Handled-By : FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
>> Status : problem is being debugged
>>
>
> James Bottomley posted a patch for it just now, Gabriel seems
> to be happy with it
>
>


Yes :)

http://lkml.org/lkml/diff/2007/7/19/357/1

Everything works again with this patch.


Gabriel

-
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/