On Wed, Jul 10, 2013 at 07:52:00PM +0100, Russell King - ARM Linux wrote:
> On Wed, Jul 10, 2013 at 05:34:11PM +0100, Will Deacon wrote:
> > Ok, I've finally got to the bottom of this, but I'm not sure on the best way
> > to fix it.
>
> I don't think you have! You need to look back at the older A
On Wed, Jul 10, 2013 at 05:34:11PM +0100, Will Deacon wrote:
> Ok, I've finally got to the bottom of this, but I'm not sure on the best way
> to fix it.
I don't think you have! You need to look back at the older ARM kernels
to really get to the bottom of this...
> The issue is that libc expects
On Wed, Jul 10, 2013 at 05:34:11PM +0100, Will Deacon wrote:
> On Wed, Jul 10, 2013 at 11:42:25AM +0100, Ashish Sangwan wrote:
> > Any heads up on this?
> >
> > or could someone just advice what can we do to debug this?
> >
> > The ret_from_fork currently looks like following:
> > /*
> > * This
On Wed, Jul 10, 2013 at 11:42:25AM +0100, Ashish Sangwan wrote:
> Any heads up on this?
>
> or could someone just advice what can we do to debug this?
>
> The ret_from_fork currently looks like following:
> /*
> * This is how we return from a fork.
> */
> ENTRY(ret_from_fork)
> bl
Any heads up on this?
or could someone just advice what can we do to debug this?
The ret_from_fork currently looks like following:
/*
* This is how we return from a fork.
*/
ENTRY(ret_from_fork)
bl schedule_tail
cmp r5, #0
movne r0, r4
adrne lr, BSYM
Forget to mention, we are using ARM
On Mon, Jul 8, 2013 at 10:45 AM, Ashish Sangwan
wrote:
> On kernel version 3.8.13, when we try to execute a statically compiled
> binary from kernel, it is giving segfault:
>
> insmod /mnt/module2.ko
> [ 35.56] sample.static: unhandled page fault (11) at
On kernel version 3.8.13, when we try to execute a statically compiled
binary from kernel, it is giving segfault:
insmod /mnt/module2.ko
[ 35.56] sample.static: unhandled page fault (11) at 0x,
code 0x8007
[ 36.44] Pid: 257, comm:sample.static
[ 36.444000] CPU: 3
7 matches
Mail list logo