[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a44ae5cd0707072156y7d0c9e5am2ded3efdc036bcf7@mail.gmail.com>
Date: Sat, 7 Jul 2007 21:56:06 -0700
From: "Miles Lane" <miles.lane@...il.com>
To: "Tejun Heo" <htejun@...il.com>
Cc: "Andrew Morton" <akpm@...l.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.22-rc6-mm1 -- BUG - EIP: [<c01a77a1>] sysfs_addrm_finish+0x1c2/0x226 SS:ESP 0068:c5ff9db8
On 7/7/07, Tejun Heo <htejun@...il.com> wrote:
> Miles Lane wrote:
> >> Weird, that's unrelated path. It seems sd->s_parent is NULL in
> >> sysfs_link_sibling(), which doesn't make sense because it's being called
> >> from sysfs_create_link() which makes sure parent_sd isn't NULL &&
> >> sysfs_addrm_start() should have caused oops earlier as it deferences
> >> parent_sd.
> >>
> >> Can you please retry the test (test clean 2.6.22-rc6-mm1, apply patch,
> >> rebuild and test)?
> >
> > I downloaded linux-2.6.22-rc6.tar.bz2, applied 2.6.22-rc6-mm1 and then
> > applied your second patch. I still get the same OOPS I reported to you
> > and Andrew in the image I attached to my previous message.
>
> Thanks a lot. Just in case, if you remove the patch (patch -R -p1), the
> oops goes away, right?
I double-checked. I can boot fine after building without your patch.
Also, I reproduced the initial BUG I reported (triggered by
"modprobe -r ipw2200").
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists