All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.H." <warthog9@kernel.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: David Brown <davidb@codeaurora.org>,
	sedat.dilek@gmail.com, LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org, ftpadmin@kernel.org,
	webmaster@kernel.org
Subject: Re: patchwork.kernel.org down
Date: Mon, 10 Jan 2011 12:04:31 -0800	[thread overview]
Message-ID: <4D2B664F.7050106@kernel.org> (raw)
In-Reply-To: <adaei8k8ubh.fsf@cisco.com>

On 01/10/2011 10:52 AM, Roland Dreier wrote:
>  >  > 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?

Not yet, I'm adding it in this afternoon.  I did the upgrade to Fedora
14 (and thus 2.6.35.10) and seem to be getting, if not the same bug, a
darned similar one:

http://pastebin.osuosl.org/36644

I haven't added it to 20702 yet as I haven't had time to confirm if it's
the same issue, but at first glance it looks it.  My plan is to compile
up a mainline kernel, with the above patch, and with debugging turned on
and to capture as much as I can from that.

- John 'Warthog9' Hawley

  reply	other threads:[~2011-01-10 20:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 20:12 patchwork.kernel.org down Sedat Dilek
2010-12-20 20:49 ` David Brown
2010-12-21  1:00   ` J.H.
2011-01-05 22:52     ` Roland Dreier
2011-01-05 23:48       ` Randy Dunlap
2011-01-06  2:58         ` Roland Dreier
2011-01-10 18:52       ` Roland Dreier
2011-01-10 20:04         ` J.H. [this message]
2011-01-10 20:33           ` Roland Dreier
2011-01-11  0:45             ` J.H.
2011-01-10 20:53           ` Roland Dreier
2011-03-30 14:30 Sedat Dilek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D2B664F.7050106@kernel.org \
    --to=warthog9@kernel.org \
    --cc=davidb@codeaurora.org \
    --cc=ftpadmin@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdreier@cisco.com \
    --cc=sedat.dilek@gmail.com \
    --cc=webmaster@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.