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 16:45:18 -0800 [thread overview]
Message-ID: <4D2BA81E.50600@kernel.org> (raw)
In-Reply-To: <ada1v4k8pnw.fsf@cisco.com>
On 01/10/2011 12:33 PM, Roland Dreier wrote:
> > 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
>
> Actually that looks pretty different; the trace is
>
> put_ldisc+0x8d/0xb4
> tty_ldisc_reinit+0x43/0x5c
> tty_ldisc_hangup+0x10d/0x19d
> do_tty_hangup+0x108/0x343
> ? __raw_local_irq_save+0x1d/0x23
> tty_vhangup_self+0x27/0x34
> sys_vhangup+0x22/0x29
> system_call_fastpath+0x16/0x1b
>
> which doesn't involve any /proc/net file being closed at all.
>
> Hmm...
My thoughts on why it was possibly similar is that it happens
[ 793.932076] kernel BUG at mm/slub.c:2834!
where as 20702 is
kernel BUG at mm/slub.c:2835!
the rest didn't line up, and like I said I haven't specifically dug into it.
As a note I did end up with a full panic in the last hour, but nothing
got recorded (sadly). I'm working on getting the kernel compiled up
with everything now so hopefully I'll start getting some additional data
to share.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2011-01-11 0:45 UTC|newest]
Thread overview: 11+ 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.
2011-01-10 20:33 ` Roland Dreier
2011-01-11 0:45 ` J.H. [this message]
2011-01-10 20:53 ` Roland Dreier
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=4D2BA81E.50600@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).