[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <adaei8k8ubh.fsf@cisco.com>
Date: Mon, 10 Jan 2011 10:52:50 -0800
From: Roland Dreier <rdreier@...co.com>
To: "J.H." <warthog9@...nel.org>
Cc: David Brown <davidb@...eaurora.org>, sedat.dilek@...il.com,
LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
ftpadmin@...nel.org, webmaster@...nel.org
Subject: Re: patchwork.kernel.org down
> > More excitement from https://bugzilla.kernel.org/show_bug.cgi?id=20702
> >
> > Anyone want to take a stab at it? I know I'd be appreciative. I am
> > running a debug kernel with everything I could find and enable I even
> > remotely thought might prove helpful. Nothing has jumped out yet though.
>
> A little late, but perhaps running with the patch below might help us
> make a bit of progress. The idea is to dump the last /proc/net file
> opened and closed, so we can at least have a clue as to where the crash
> is coming from. This should add lines like
>
> last procfs open: /proc/2443/net/arp
> last procfs close: /proc/2443/net/arp
>
> to the oops output, so maybe we can zero in on things after you get a
> crash with this applied.
Just curious -- did you get a chance to run with this patch applied?
Did you collect any oopses yet?
- R.
--
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