From: Valdis.Kletnieks@vt.edu
To: Jiri Slaby <jirislaby@gmail.com>
Cc: tim.c.chen@linux.intel.com,
"David S. Miller" <davem@davemloft.net>,
ML netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [next] unix stream crashes
Date: Thu, 01 Sep 2011 20:49:19 -0400 [thread overview]
Message-ID: <3179.1314924559@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 01 Sep 2011 22:46:32 +0200." <4E5FEF28.60406@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Thu, 01 Sep 2011 22:46:32 +0200, Jiri Slaby said:
> Hi,
>
> my box 100% crashes when booting. It's both in unix socket recv and send
> paths. I've reverted 0856a30409 (Scm: Remove unnecessary pid &
> credential references in Unix socket's send and receive path) and it
> seems to help.
>
> The oops:
> http://www.fi.muni.cz/~xslaby/sklad/panics/af_unix_crash.png
I was seeing a 100% repeatable crash with the X server starting as well, but
wasn't able to get a traceback because my X server was doing the modeset before
it crashed (so all I got was a black screen) and netconsole is busticated for
me. I can confirm that reverting that one commit allows my box to boot and get
X up and running as well.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-09-02 0:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 20:46 Jiri Slaby
2011-09-02 0:49 ` Valdis.Kletnieks [this message]
2011-09-02 1:40 ` Tim Chen
2011-09-02 16:12 ` Valdis.Kletnieks
2011-09-02 23:55 ` Tim Chen
2011-09-03 4:32 ` Sedat Dilek
2011-09-03 5:35 ` Valdis.Kletnieks
2011-09-03 5:54 ` Sedat Dilek
2011-09-03 6:23 ` Jiri Slaby
2011-09-03 12:30 ` Yan, Zheng
2011-09-03 13:47 ` Sedat Dilek
2011-09-03 14:46 ` Sedat Dilek
2011-09-03 15:38 ` Yan, Zheng
2011-09-04 14:43 ` Valdis.Kletnieks
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=3179.1314924559@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=davem@davemloft.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tim.c.chen@linux.intel.com \
/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
all inboxes | Powered by JetHome®