From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752254Ab3K3PHH (ORCPT ); Sat, 30 Nov 2013 10:07:07 -0500 Received: from mail-wi0-f171.google.com ([209.85.212.171]:38427 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751413Ab3K3PHE (ORCPT ); Sat, 30 Nov 2013 10:07:04 -0500 Message-ID: <5299FF38.7060203@gmail.com> Date: Sat, 30 Nov 2013 16:07:36 +0100 From: Francis Moreau User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Thomas Gleixner CC: Jingoo Han , "'Wei WANG'" , "'Samuel Ortiz'" , "'Chris Ball'" , "Rafael J. Wysocki" , "'Borislav Petkov'" , "'LKML'" Subject: Re: 3.12: kernel panic when resuming from suspend to RAM (x86_64) References: <20131117195358.GO27323@pd.tnic> <4523614.I5MBhorHFt@vostro.rjw.lan> <5292FF5D.1050304@gmail.com> <1821758.2MoNI3h1Mv@vostro.rjw.lan> <52985041.5050000@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Thomas, Sorry for the delay. On 11/29/2013 10:02 AM, Thomas Gleixner wrote: > On Fri, 29 Nov 2013, Francis Moreau wrote: >> Since it seems to be related to rtsx driver or its upper layer, could >> the folks involved in this area have a look to this issue please ? > > I'm not involved, but looking at the debug objects backtrace it's > related to the delayed work in rtsx. > > Does the untested patch below cure the issue? > It seems it does since I can't see the debug object trace anymore however Ican see this now: [ 64.498270] irq 16: nobody cared (try booting with the "irqpoll" option) [ 64.498314] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.0-rc2-ARCH #65 [ 64.498316] Hardware name: CLEVO CO. W55xEU /W55xEU , BIOS 4.6.5 03/05/2013 [ 64.498317] ffff8804078bd38c ffff88041e203e48 ffffffff81459fe9 ffff8804078bd300 [ 64.498320] ffff88041e203e70 ffffffff810d8632 ffff8804078bd300 0000000000000010 [ 64.498322] 0000000000000000 ffff88041e203eb0 ffffffff810d8a58 ffffffff8136a882 [ 64.498324] Call Trace: [ 64.498325] [] dump_stack+0x54/0x8d [ 64.498334] [] __report_bad_irq+0x32/0xd0 [ 64.498337] [] note_interrupt+0x138/0x1f0 [ 64.498340] [] ? cpuidle_enter_state+0x52/0xc0 [ 64.498343] [] handle_irq_event_percpu+0xf9/0x250 [ 64.498345] [] handle_irq_event+0x3d/0x60 [ 64.498347] [] handle_fasteoi_irq+0x5a/0x100 [ 64.498350] [] handle_irq+0x1e/0x30 [ 64.498353] [] do_IRQ+0x4d/0xc0 [ 64.498355] [] common_interrupt+0x6d/0x6d [ 64.498356] [] ? cpuidle_enter_state+0x52/0xc0 [ 64.498360] [] ? cpuidle_enter_state+0x48/0xc0 [ 64.498362] [] cpuidle_idle_call+0xc9/0x280 [ 64.498365] [] arch_cpu_idle+0xe/0x30 [ 64.498368] [] cpu_startup_entry+0x257/0x2d0 [ 64.498370] [] rest_init+0x84/0x90 [ 64.498373] [] start_kernel+0x414/0x420 [ 64.498375] [] ? repair_env_string+0x5c/0x5c [ 64.498377] [] ? early_idt_handlers+0x120/0x120 [ 64.498379] [] x86_64_start_reservations+0x2a/0x2c [ 64.498381] [] x86_64_start_kernel+0x108/0x117 [ 64.498382] handlers: [ 64.498402] [] usb_hcd_irq [usbcore] [ 64.498422] Disabling IRQ #16 So I don't think it completely solve the problem but it's a good start. Thank you.