From: Francis Moreau <francis.moro@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jingoo Han <jg1.han@samsung.com>,
"'Wei WANG'" <wei_wang@realsil.com.cn>,
"'Samuel Ortiz'" <sameo@linux.intel.com>,
"'Chris Ball'" <cjb@laptop.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"'Borislav Petkov'" <bp@alien8.de>,
"'LKML'" <linux-kernel@vger.kernel.org>
Subject: Re: 3.12: kernel panic when resuming from suspend to RAM (x86_64)
Date: Sat, 30 Nov 2013 16:07:36 +0100 [thread overview]
Message-ID: <5299FF38.7060203@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311290958560.30673@ionos.tec.linutronix.de>
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] <IRQ> [<ffffffff81459fe9>] dump_stack+0x54/0x8d
[ 64.498334] [<ffffffff810d8632>] __report_bad_irq+0x32/0xd0
[ 64.498337] [<ffffffff810d8a58>] note_interrupt+0x138/0x1f0
[ 64.498340] [<ffffffff8136a882>] ? cpuidle_enter_state+0x52/0xc0
[ 64.498343] [<ffffffff810d6439>] handle_irq_event_percpu+0xf9/0x250
[ 64.498345] [<ffffffff810d65cd>] handle_irq_event+0x3d/0x60
[ 64.498347] [<ffffffff810d95ca>] handle_fasteoi_irq+0x5a/0x100
[ 64.498350] [<ffffffff81004a6e>] handle_irq+0x1e/0x30
[ 64.498353] [<ffffffff8146aafd>] do_IRQ+0x4d/0xc0
[ 64.498355] [<ffffffff8146116d>] common_interrupt+0x6d/0x6d
[ 64.498356] <EOI> [<ffffffff8136a882>] ? cpuidle_enter_state+0x52/0xc0
[ 64.498360] [<ffffffff8136a878>] ? cpuidle_enter_state+0x48/0xc0
[ 64.498362] [<ffffffff8136a9b9>] cpuidle_idle_call+0xc9/0x280
[ 64.498365] [<ffffffff8100bf6e>] arch_cpu_idle+0xe/0x30
[ 64.498368] [<ffffffff810a1287>] cpu_startup_entry+0x257/0x2d0
[ 64.498370] [<ffffffff8144d404>] rest_init+0x84/0x90
[ 64.498373] [<ffffffff818d9ee1>] start_kernel+0x414/0x420
[ 64.498375] [<ffffffff818d98d6>] ? repair_env_string+0x5c/0x5c
[ 64.498377] [<ffffffff818d9120>] ? early_idt_handlers+0x120/0x120
[ 64.498379] [<ffffffff818d95be>] x86_64_start_reservations+0x2a/0x2c
[ 64.498381] [<ffffffff818d96c8>] x86_64_start_kernel+0x108/0x117
[ 64.498382] handlers:
[ 64.498402] [<ffffffffa00168f0>] 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.
next prev parent reply other threads:[~2013-11-30 15:07 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 9:42 3.12: kernel panic when resuming from suspend to RAM (x86_64) Francis Moreau
2013-11-17 13:25 ` Borislav Petkov
2013-11-17 15:50 ` Francis Moreau
2013-11-17 16:01 ` Borislav Petkov
2013-11-17 18:02 ` Francis Moreau
2013-11-17 19:53 ` Borislav Petkov
2013-11-17 20:49 ` Francis Moreau
2013-11-17 22:06 ` Borislav Petkov
2013-11-17 22:34 ` Rafael J. Wysocki
2013-11-17 22:46 ` Borislav Petkov
2013-11-18 12:21 ` Francis Moreau
2013-11-18 12:20 ` Francis Moreau
2013-11-18 0:33 ` Kevin Easton
2013-11-18 1:04 ` Borislav Petkov
2013-11-18 2:43 ` Kevin Easton
2013-11-18 12:19 ` Francis Moreau
2013-11-18 13:32 ` Borislav Petkov
2013-11-19 10:01 ` Francis Moreau
2013-11-19 10:15 ` Borislav Petkov
2013-11-20 9:45 ` Francis Moreau
2013-11-20 11:15 ` Borislav Petkov
2013-11-21 8:22 ` Francis Moreau
2013-11-21 10:12 ` Borislav Petkov
2013-11-21 11:17 ` Jingoo Han
2013-11-21 13:07 ` Francis Moreau
2013-11-22 7:43 ` Francis Moreau
2013-11-22 9:57 ` Francis Moreau
2013-11-22 12:54 ` Rafael J. Wysocki
2013-11-22 21:36 ` Francis Moreau
2013-11-22 22:08 ` Rafael J. Wysocki
2013-11-22 22:27 ` Thomas Gleixner
2013-11-24 9:39 ` Francis Moreau
2013-11-24 13:31 ` Borislav Petkov
2013-11-24 21:06 ` Rafael J. Wysocki
2013-11-25 7:42 ` Francis Moreau
2013-11-25 10:47 ` Rafael J. Wysocki
2013-11-29 8:28 ` Francis Moreau
2013-11-29 9:02 ` Thomas Gleixner
2013-11-30 15:07 ` Francis Moreau [this message]
2013-11-30 20:17 ` Rafael J. Wysocki
2013-12-01 10:11 ` Francis Moreau
2013-12-01 19:26 ` Francis Moreau
2013-12-02 10:49 ` Thomas Gleixner
2013-12-02 11:20 ` Thomas Gleixner
2013-12-03 8:14 ` Francis Moreau
2013-12-09 19:33 ` Francis Moreau
2013-12-09 22:27 ` Samuel Ortiz
2013-12-09 22:17 ` Samuel Ortiz
2013-12-10 1:39 ` wwang
2013-12-10 1:56 ` micky
2013-12-10 8:29 ` Samuel Ortiz
2014-01-10 7:26 ` Francis Moreau
2014-01-10 9:16 ` micky
2014-01-10 9:52 ` Samuel Ortiz
2014-01-10 10:07 ` Francis Moreau
2013-12-10 10:50 ` Francis Moreau
2013-12-17 8:03 ` Francis Moreau
2013-12-18 4:05 ` micky
2013-12-18 8:12 ` Francis Moreau
2013-12-20 1:30 ` micky
2013-12-20 2:28 ` Jingoo Han
2013-12-10 10:49 ` Francis Moreau
2013-11-24 9:42 ` Francis Moreau
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=5299FF38.7060203@gmail.com \
--to=francis.moro@gmail.com \
--cc=bp@alien8.de \
--cc=cjb@laptop.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sameo@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=wei_wang@realsil.com.cn \
/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.