Christoph Lameter wrote:
> On Wed, 18 Jul 2007 14:51:14 +0900
> Tejun Heo <[EMAIL PROTECTED]> wrote:
>
>> Okay, successfully reproduced here. Will hunt down.
>
> Next time simply boot with "slub_debug". It will save a lot of time.
Alright, thanks.
--
tejun
-
To unsubscribe from this list: sen
On Mon, 16 Jul 2007 20:49:03 +0530
"Satyam Sharma" <[EMAIL PROTECTED]> wrote:
> I'm thoroughly mystified ... Christoph? Tejun? Someone?
It would help to boot with "slub_debug" to find out what corrupted the
data.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
On Wed, 18 Jul 2007 14:51:14 +0900
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Okay, successfully reproduced here. Will hunt down.
Next time simply boot with "slub_debug". It will save a lot of time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
Okay, successfully reproduced here. Will hunt down.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Gabriel C wrote:
> Gabriel C wrote:
>
>> Tejun Heo wrote:
>>
>>
>>> Satyam Sharma wrote:
>>>
>>>
>>>
On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
> Here the bisect result:
>
> 3007e997de91ec59af39a3f9c91595b31ae6e08b
Gabriel C wrote:
> Tejun Heo wrote:
>
>> Satyam Sharma wrote:
>>
>>
>>> On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>>>
>>>
Here the bisect result:
3007e997de91ec59af39a3f9c91595b31ae6e08b is first bad commit
commit 3007e997de91ec59af39a3f9c91595b31ae
Tejun Heo wrote:
> Satyam Sharma wrote:
>
>> On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>>
>>> Here the bisect result:
>>>
>>> 3007e997de91ec59af39a3f9c91595b31ae6e08b is first bad commit
>>> commit 3007e997de91ec59af39a3f9c91595b31ae6e08b
>>> Author: Tejun Heo <[EMAIL PROTECTED]>
>>>
Satyam Sharma wrote:
> On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>> Here the bisect result:
>>
>> 3007e997de91ec59af39a3f9c91595b31ae6e08b is first bad commit
>> commit 3007e997de91ec59af39a3f9c91595b31ae6e08b
>> Author: Tejun Heo <[EMAIL PROTECTED]>
>> Date: Thu Jun 14 04:27:23 2007 +0900
Folks,
I will have the fix and rework to the fixed phy posted by today/tomorrow.
You'll have to modify platform code a bit
Thanks,
-Vitaly
On Sun, 15 Jul 2007 19:42:44 +0200
Gabriel C <[EMAIL PROTECTED]> wrote:
> Satyam Sharma wrote:
> > Hi Gabriel,
> >
>
> Hi Satyam ,
>
> > On 7/14/07, G
Gabriel C wrote:
> Satyam Sharma wrote:
>
>> Hi Gabriel,
>>
>> On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> ( http://194.231.229.228/Oops.txt )
>>>
>>>
>>
>>
>>> I cannot reproduce this on plain 2.6.22 so I've started to bisect the
>>> problem.
>>>
Gabriel C wrote:
> Satyam Sharma wrote:
>
>> Hi Gabriel,
>>
>> On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> ( http://194.231.229.228/Oops.txt )
>>>
>>>
>>
>>
>>> I cannot reproduce this on plain 2.6.22 so I've started to bisect the
>>> problem.
>>>
Satyam Sharma wrote:
> Hi Gabriel,
>
> On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>
>
>> ( http://194.231.229.228/Oops.txt )
>>
>
>
>> I cannot reproduce this on plain 2.6.22 so I've started to bisect the
>> problem.
>>
>
> Could you reproduce this oops at will at the "bad" po
Hi Gabriel,
On 7/16/07, Gabriel C <[EMAIL PROTECTED]> wrote:
( http://194.231.229.228/Oops.txt )
I cannot reproduce this on plain 2.6.22 so I've started to bisect the
problem.
Could you reproduce this oops at will at the "bad" points? [ Note that
git-bisect isn't quite applicable to bugs t
Gabriel C wrote:
> Satyam Sharma wrote:
>
>> On 7/15/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>>
>>
> [...]
> doing a modprobe fixed the driver segfaults and I get this Oops:
>
> Jul 14 13:43:30 lara [ 157.953261] BUG: unable to handle kernel paging
> request at virt
Satyam Sharma wrote:
> On 7/15/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>
[...]
doing a modprobe fixed the driver segfaults and I get this Oops:
Jul 14 13:43:30 lara [ 157.953261] BUG: unable to handle kernel paging
request at virtual address 43b7a800
On 7/15/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>> [...]
>> doing a modprobe fixed the driver segfaults and I get this Oops:
>>
>> Jul 14 13:43:30 lara [ 157.953261] BUG: unable to handle kernel paging
>> request at virtual address 43b7a800
>>
>
> 43b7a800 looks suspicious, it could have been a
Gabriel C wrote:
> Satyam Sharma wrote:
>
>> Hi Gabriel,
>>
>>
>
> Hi Satyam ,
>
>
>> On 7/14/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Hi,
>>>
>>> doing a modprobe fixed the driver segfaults and I get this Oops:
>>>
>>>
>>> Jul 14 13:43:30 lara [ 157.952915] Fixed P
Satyam Sharma wrote:
> Hi Gabriel,
>
Hi Satyam ,
> On 7/14/07, Gabriel C <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> doing a modprobe fixed the driver segfaults and I get this Oops:
>>
>>
>> Jul 14 13:43:30 lara [ 157.952915] Fixed PHY: Registered new driver
>> Jul 14 13:43:30 lara [ 157.95
Hi Gabriel,
On 7/14/07, Gabriel C <[EMAIL PROTECTED]> wrote:
Hi,
doing a modprobe fixed the driver segfaults and I get this Oops:
Jul 14 13:43:30 lara [ 157.952915] Fixed PHY: Registered new driver
Jul 14 13:43:30 lara [ 157.953010] Device '[EMAIL PROTECTED]:1' does not have a
release() fun
Gabriel C wrote:
> Hi,
>
> doing a modprobe fixed the driver segfaults and I get this Oops:
>
>
> Jul 14 13:43:30 lara [ 157.952915] Fixed PHY: Registered new driver
[...]
God , tbird sucks ..
There the dmesg with the Oops :
http://194.231.229.228/kern.log
Should be better to read.
Regards,
20 matches
Mail list logo
