From: James Hogan <james.hogan@imgtec.com>
To: Ezequiel Garcia <ezequiel.garcia@imgtec.com>,
<linux-mips@linux-mips.org>
Cc: Paul Martin <paul.martin@codethink.co.uk>,
"Maciej (LMO)" <macro@linux-mips.org>
Subject: Re: "BUG: using smp_processor_id() in preemptible" on v4.1-rc3
Date: Tue, 12 May 2015 13:27:09 +0100 [thread overview]
Message-ID: <5551F19D.10602@imgtec.com> (raw)
In-Reply-To: <555153F9.2020300@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
Hi Ezequiel,
Could you confirm whether your problem is the same as that described here?:
http://patchwork.linux-mips.org/patch/9830/
Cheers
James
On 12/05/15 02:14, Ezequiel Garcia wrote:
> Whenever I run a command, I get a "BUG: using smp_processor_id()
> in preemptible...". I'm running v4.1-rc3 with CONFIG_PREEMPT.
>
> Kernel log and config attached -- You can see the BUG during boot
> a few times as well.
>
> Not sure where's the smp_processor_id call in load_elf_binary, but
> it seems to be MIPS-related.
>
> # ls
> [ 14.881148] BUG: using smp_processor_id() in preemptible [00000000] code: sh/97
> [ 14.889499] caller is load_elf_binary+0x4cc/0x1320
> [ 14.894991] CPU: 0 PID: 97 Comm: sh Not tainted 4.1.0-rc3+ #134
> [ 14.901700] Stack : 00000000 00000000 81c90d52 00000033 666c655f 00000000 00000001 8049c350
> 8049c31c 80c20000 80b8e8c4 00000061 00000000 814e37f0 00000007 00000000
> 860bbcc8 8049c350 860bbcc8 80790fac 00000003 814d0000 80b8e8c4 860bbc2c
> 00000061 80a66e04 814e37f0 8042e1c8 00000000 00000000 860bbc2c dc8ba300
> 80c1f327 006cda88 00000000 00000000 00000000 00000000 00000000 00000000
> ...
> [ 14.942591] Call Trace:
> [ 14.945471] [<8040c1a4>] show_stack+0x6c/0xac
> [ 14.950475] [<80a67f3c>] dump_stack+0xc8/0x128
> [ 14.955628] [<807a366c>] check_preemption_disabled+0xec/0x118
> [ 14.962180] [<805f33c0>] load_elf_binary+0x4cc/0x1320
> [ 14.967978] [<80593594>] search_binary_handler+0xbc/0x214
> [ 14.974135] [<805f28e8>] load_script+0x288/0x2b0
> [ 14.979426] [<80593594>] search_binary_handler+0xbc/0x214
> [ 14.985587] [<80594460>] do_execveat_common+0x638/0xa74
> [ 14.991562] [<805948d4>] do_execve+0x38/0x44
> [ 14.996469] [<80414840>] handle_sys+0x160/0x184
> [ 15.001652] bin etc init lib32 media opt root sbin tmp var
> dev home lib linuxrc mnt proc run sys usr
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Ezequiel Garcia <ezequiel.garcia@imgtec.com>, linux-mips@linux-mips.org
Cc: Paul Martin <paul.martin@codethink.co.uk>,
"Maciej (LMO)" <macro@linux-mips.org>
Subject: Re: "BUG: using smp_processor_id() in preemptible" on v4.1-rc3
Date: Tue, 12 May 2015 13:27:09 +0100 [thread overview]
Message-ID: <5551F19D.10602@imgtec.com> (raw)
Message-ID: <20150512122709.wc_yq-1sAWp52CTxWnV6sOZaepVN25dmPaJsZVyTyIw@z> (raw)
In-Reply-To: <555153F9.2020300@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
Hi Ezequiel,
Could you confirm whether your problem is the same as that described here?:
http://patchwork.linux-mips.org/patch/9830/
Cheers
James
On 12/05/15 02:14, Ezequiel Garcia wrote:
> Whenever I run a command, I get a "BUG: using smp_processor_id()
> in preemptible...". I'm running v4.1-rc3 with CONFIG_PREEMPT.
>
> Kernel log and config attached -- You can see the BUG during boot
> a few times as well.
>
> Not sure where's the smp_processor_id call in load_elf_binary, but
> it seems to be MIPS-related.
>
> # ls
> [ 14.881148] BUG: using smp_processor_id() in preemptible [00000000] code: sh/97
> [ 14.889499] caller is load_elf_binary+0x4cc/0x1320
> [ 14.894991] CPU: 0 PID: 97 Comm: sh Not tainted 4.1.0-rc3+ #134
> [ 14.901700] Stack : 00000000 00000000 81c90d52 00000033 666c655f 00000000 00000001 8049c350
> 8049c31c 80c20000 80b8e8c4 00000061 00000000 814e37f0 00000007 00000000
> 860bbcc8 8049c350 860bbcc8 80790fac 00000003 814d0000 80b8e8c4 860bbc2c
> 00000061 80a66e04 814e37f0 8042e1c8 00000000 00000000 860bbc2c dc8ba300
> 80c1f327 006cda88 00000000 00000000 00000000 00000000 00000000 00000000
> ...
> [ 14.942591] Call Trace:
> [ 14.945471] [<8040c1a4>] show_stack+0x6c/0xac
> [ 14.950475] [<80a67f3c>] dump_stack+0xc8/0x128
> [ 14.955628] [<807a366c>] check_preemption_disabled+0xec/0x118
> [ 14.962180] [<805f33c0>] load_elf_binary+0x4cc/0x1320
> [ 14.967978] [<80593594>] search_binary_handler+0xbc/0x214
> [ 14.974135] [<805f28e8>] load_script+0x288/0x2b0
> [ 14.979426] [<80593594>] search_binary_handler+0xbc/0x214
> [ 14.985587] [<80594460>] do_execveat_common+0x638/0xa74
> [ 14.991562] [<805948d4>] do_execve+0x38/0x44
> [ 14.996469] [<80414840>] handle_sys+0x160/0x184
> [ 15.001652] bin etc init lib32 media opt root sbin tmp var
> dev home lib linuxrc mnt proc run sys usr
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-12 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 1:14 "BUG: using smp_processor_id() in preemptible" on v4.1-rc3 Ezequiel Garcia
2015-05-12 1:14 ` Ezequiel Garcia
2015-05-12 12:27 ` James Hogan [this message]
2015-05-12 12:27 ` James Hogan
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=5551F19D.10602@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=ezequiel.garcia@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=paul.martin@codethink.co.uk \
/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.