From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755330AbbGTNAi (ORCPT ); Mon, 20 Jul 2015 09:00:38 -0400 Received: from mx4-phx2.redhat.com ([209.132.183.25]:57770 "EHLO mx4-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753018AbbGTNAg (ORCPT ); Mon, 20 Jul 2015 09:00:36 -0400 Date: Mon, 20 Jul 2015 09:00:35 -0400 (EDT) From: Kamil Paral To: linux-kernel@vger.kernel.org Message-ID: <1903109583.729928.1437397235777.JavaMail.zimbra@redhat.com> In-Reply-To: <1713223047.709326.1437396468276.JavaMail.zimbra@redhat.com> Subject: bug: deadlock in smp.c at on_each_cpu/smp_call_function_many MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.40.204.45] X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF39 (Linux)/8.0.6_GA_5922) Thread-Topic: deadlock in smp.c at on_each_cpu/smp_call_function_many Thread-Index: 5TgC5n+rtG/Wh9OJ3Wvg58+Y01Ry5w== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, I've experienced a kernel panic, the screenshots are here: https://bugs.freedesktop.org/attachment.cgi?id=117026 https://bugs.freedesktop.org/attachment.cgi?id=117027 It happened with kernel-4.0.7-300.fc22.x86_64 on Fedora 22. Originally I reported it against the radeon driver [1], but I was told that it seems to be a deadlock in on_each_cpu/smp_call_function_many (which seems to be in smp.c) and that I should report it into an appropriate mailing list. I'd report it to bugzilla, but I wasn't sure which product/component to file it against. Please advise what steps I should take in order to have this properly reported, or whether random panics which are not reproducible at will are not worth reporting, because the traces don't provide enough clues to resolve them. I have no experience in this matter, so I don't really know. Thanks for pointers, Kamil Paral [1] https://bugs.freedesktop.org/show_bug.cgi?id=91291