Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Jun 2017 22:00:37 -0700
From:      Gleb Smirnoff <glebius@FreeBSD.org>
To:        Andreas Tobler <andreast@FreeBSD.org>
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r319722 - in head: sys/cam/ctl sys/dev/iscsi sys/kern sys/netgraph sys/netgraph/bluetooth/socket sys/netinet sys/ofed/drivers/infiniband/core sys/ofed/drivers/infiniband/ulp/sdp sys/rpc...
Message-ID:  <20170615050037.GO50023@FreeBSD.org>
In-Reply-To: <bbdb2d2c-a84f-f6a2-34dc-5999c489a603@FreeBSD.org>
References:  <201706082130.v58LUY0j095589@repo.freebsd.org> <bbdb2d2c-a84f-f6a2-34dc-5999c489a603@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
  Hi,

On Wed, Jun 14, 2017 at 09:59:50AM +0200, Andreas Tobler wrote:
A> with this revision I get either a kernel panic or a hang. This happens 
A> on powerpc (32-bit). The powerpc64 looks stable.
A> 
A> Here you can see the backtrace in case of the panic:
A> https://people.freebsd.org/~andreast/r319722_ppc32_1.jpg
A> 
A> In the source code I see a comment with XXXGL...
A> Is this powerpc specific or do you think that there are some issues in 
A> the uipc_socket.c code?

The comment has nothing to do with arch or 32-bit. Is
it possible to understand what is the actual instruction
at soisconnected()+0x21c ?

-- 
Totus tuus, Glebius.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170615050037.GO50023>