From: Alan Stern <stern@rowland.harvard.edu>
To: M G Berberich <berberic@fmi.uni-passau.de>
Cc: USB list <linux-usb@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code]
Date: Thu, 9 Jun 2016 14:14:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1606091410580.1353-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20160609172444.GB6277@invalid>
On Thu, 9 Jun 2016, M G Berberich wrote:
> Hello,
>
> With 4.7-rc2, after detecting a USB Mass Storage device
>
> [ 11.589843] usb-storage 4-2:1.0: USB Mass Storage device detected
>
> a constant flow of kernel-BUGS is reported (several per second).
>
> [ 11.599215] BUG: using smp_processor_id() in preemptible [00000000] code:
> systemd-udevd/389
> [ 11.599218] caller is debug_smp_processor_id+0x17/0x20
> [ 11.599220] CPU: 4 PID: 389 Comm: systemd-udevd Not tainted 4.7.0-rc2 #6
> [ 11.599220] Hardware name: Gigabyte Technology Co., Ltd. H87-HD3/H87-HD3,
> BIOS F10 08/18/2015
> [ 11.599223] 0000000000000000 ffff88080466b6c8 ffffffff813fc42d
> 0000000000000004
> [ 11.599224] ffffffff81cc1da3 ffff88080466b6f8 ffffffff8141a0f6
> 0000000000000000
> [ 11.599226] ffff880809fe8d98 0000000000000001 00000000000fffff
> ffff88080466b708
> [ 11.599226] Call Trace:
> [ 11.599229] [<ffffffff813fc42d>] dump_stack+0x4f/0x72
> [ 11.599231] [<ffffffff8141a0f6>] check_preemption_disabled+0xd6/0xe0
> [ 11.599233] [<ffffffff8141a117>] debug_smp_processor_id+0x17/0x20
> [ 11.599235] [<ffffffff814f0336>] alloc_iova_fast+0xb6/0x210
> [ 11.599238] [<ffffffff819ed64f>] ? __wait_on_bit+0x6f/0x90
> [ 11.599240] [<ffffffff814f388d>] intel_alloc_iova+0x9d/0xd0
> [ 11.599241] [<ffffffff814f7c33>] __intel_map_single+0x93/0x190
> [ 11.599242] [<ffffffff814f7d64>] intel_map_page+0x34/0x40
>
> Please see https://bugzilla.kernel.org/show_bug.cgi?id=119801 for a
> more complete kernel-log
This looks like a bug in the memory management subsystem. It should be
reported on the linux-mm mailing list (CC'ed).
Alan Stern
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2016-06-09 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160609172444.GB6277@invalid>
2016-06-09 18:14 ` Alan Stern [this message]
2016-06-09 19:10 ` Nadav Amit
2016-06-13 13:06 ` M G Berberich
2016-06-13 13:11 ` Adam Morrison
2016-06-14 9:08 ` M G Berberich
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=Pine.LNX.4.44L0.1606091410580.1353-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=berberic@fmi.uni-passau.de \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.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