On 06/29/2007 03:12 PM, Satyam Sharma wrote:
> Hi Clemens,
>
> [ Cc:'ing Andrew, original thread at http://lkml.org/lkml/2007/5/15/354 ]
>
> On 6/29/07, Clemens Schwaighofer <[EMAIL PROTECTED]> wrote:
>> On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote:
>> > Hi,
>>
>> I had my system running up
Hi Clemens,
[ Cc:'ing Andrew, original thread at http://lkml.org/lkml/2007/5/15/354 ]
On 6/29/07, Clemens Schwaighofer <[EMAIL PROTECTED]> wrote:
On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote:
> Hi,
I had my system running up for about one month without any issues, and
then it happened ag
On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote:
> Hi,
I had my system running up for about one month without any issues, and
then it happened again, same kernel oops, panic, end.
So I have upgraded to 2.6.22-rc4-mm2 in hope it might fix it, but I just
got another oops (uptime 4d) [see attache
Andrew Morton wrote:
On Wed, 16 May 2007 17:40:53 +0200 Tejun Heo <[EMAIL PROTECTED]> wrote:
I see. I thought there was different approach on fixing the problem.
I'll try to backport the synchronization fix but am afraid it can be too
risky for -stable. If it seems too risky, I'll send a patc
On Wed, 16 May 2007 17:40:53 +0200 Tejun Heo <[EMAIL PROTECTED]> wrote:
> I see. I thought there was different approach on fixing the problem.
> I'll try to backport the synchronization fix but am afraid it can be too
> risky for -stable. If it seems too risky, I'll send a patch to disable
> rec
Tejun Heo wrote:
>>> The safest approach I can think of is making
>>> dentries for attributes unreclaimable but those are made reclaimable for
>>> good reasons. :-(
>> Yeah, that was the google workaround. It's OK unless you happen to have
>> thousands of disks on an ia32 box.
>
> I see. I tho
Andrew Morton wrote:
>>> a number of people have hit that, on and off.
>> Yeah, I've been seeing that one. It should have been fixed with the big
>> fat patchset.
>
> Great - fingers crossed.
>
>>> We were close to having a fix, I think, but then we decided that great
>>> chunks of sysfs needed
On Wed, 16 May 2007 13:05:19 +0200 Tejun Heo <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Andrew Morton wrote:
> > On Wed, 16 May 2007 09:24:54 +0900 Clemens Schwaighofer <[EMAIL PROTECTED]>
> > wrote:
> >
> >> I have re-occurring oopses and panics in those above kernels. The error
> >> is always th
Hello,
Andrew Morton wrote:
> On Wed, 16 May 2007 09:24:54 +0900 Clemens Schwaighofer <[EMAIL PROTECTED]>
> wrote:
>
>> I have re-occurring oopses and panics in those above kernels. The error
>> is always the same. I have the last Kernel Panic as a picture here:
>>
>> http://dev.tequila.jp/cleme
On Wed, 16 May 2007 11:46:00 +0900 Clemens Schwaighofer <[EMAIL PROTECTED]>
wrote:
> On 05/16/2007 10:53 AM, Andrew Morton wrote:
>
> > How frequently do you see these failures? If it's repeatable with any
> > reliability
> > then it'd be great if you could test a patchset for us. It's at:
>
On 05/16/2007 10:53 AM, Andrew Morton wrote:
> How frequently do you see these failures? If it's repeatable with any
> reliability
> then it'd be great if you could test a patchset for us. It's at:
>
> http://userweb.kernel.org/~akpm/cs.gz
>
> that's a single patch against 2.6.21-rc1, contain
On 05/16/2007 10:53 AM, Andrew Morton wrote:
>
>> I think it started with 2.6.19.2, I cannot remember I had any of those
>> problems before. The box can work fine for about a week or more, or it
>> looks up several times a day. I run a memtest for 10 h, but I had no errors.
>
> shrink_dcache_memor
On Wed, 16 May 2007 09:24:54 +0900 Clemens Schwaighofer <[EMAIL PROTECTED]>
wrote:
> I have re-occurring oopses and panics in those above kernels. The error
> is always the same. I have the last Kernel Panic as a picture here:
>
> http://dev.tequila.jp/clemens/R0010172.JPG
>
> The oops have the
On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote:
> The oops have the same error style like this Panic. I tried to capture
> one, but right after copying it into vim, I got a Panic. So next time I
> try to.
I just got a oops and I could record it, the followed Kernel Panic
didn't send out any P
14 matches
Mail list logo
