From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f69.google.com (mail-pa0-f69.google.com [209.85.220.69]) by kanga.kvack.org (Postfix) with ESMTP id 0DEFB828E1 for ; Thu, 9 Jun 2016 15:10:50 -0400 (EDT) Received: by mail-pa0-f69.google.com with SMTP id ug1so65634344pab.3 for ; Thu, 09 Jun 2016 12:10:50 -0700 (PDT) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com. [2607:f8b0:400e:c00::242]) by mx.google.com with ESMTPS id t6si8890710paz.29.2016.06.09.12.10.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Jun 2016 12:10:49 -0700 (PDT) Received: by mail-pf0-x242.google.com with SMTP id 66so1561768pfy.1 for ; Thu, 09 Jun 2016 12:10:49 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code] From: Nadav Amit In-Reply-To: Date: Thu, 9 Jun 2016 12:10:47 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <50F437E3-85F7-4034-BAAE-B2558173A2EA@gmail.com> References: Sender: owner-linux-mm@kvack.org List-ID: To: iommu@lists.linux-foundation.org, Adam Morrison , M G Berberich Cc: USB list , linux-mm@kvack.org, Alan Stern Alan Stern wrote: > On Thu, 9 Jun 2016, M G Berberich wrote: >=20 >> Hello, >>=20 >> With 4.7-rc2, after detecting a USB Mass Storage device >>=20 >> [ 11.589843] usb-storage 4-2:1.0: USB Mass Storage device detected >>=20 >> a constant flow of kernel-BUGS is reported (several per second). >>=20 >> [ 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] [] dump_stack+0x4f/0x72 >> [ 11.599231] [] = check_preemption_disabled+0xd6/0xe0 >> [ 11.599233] [] debug_smp_processor_id+0x17/0x20 >> [ 11.599235] [] alloc_iova_fast+0xb6/0x210 >> [ 11.599238] [] ? __wait_on_bit+0x6f/0x90 >> [ 11.599240] [] intel_alloc_iova+0x9d/0xd0 >> [ 11.599241] [] __intel_map_single+0x93/0x190 >> [ 11.599242] [] intel_map_page+0x34/0x40 >>=20 >> Please see https://bugzilla.kernel.org/show_bug.cgi?id=3D119801 for a >> more complete kernel-log >=20 > This looks like a bug in the memory management subsystem. It should = be=20 > reported on the linux-mm mailing list (CC'ed). This bug is IOMMU related (mailing list CC=E2=80=99ed) and IIUC already = fixed. Regards, Nadav -- 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: email@kvack.org