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 the same. I have the last Kernel Panic as a picture here: > >> > >> http://dev.tequila.jp/clemens/R0010172.JPG > >> > >> 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 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_memory->...sysfs_d_iput->BUG > > > > BUG_ON(sd->s_dentry != dentry); > > > > 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 rewriting and I believe that we believe that this > > great rewrite will fix this bug. > > How were we gonna fix it? If it isn't too complex, I can cook up a > patch for -stable series. Do we actually understand the causes? > 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. - 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/