From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>
Subject: Re: ktime_get_ts64() splat during resume
Date: Fri, 17 Jun 2016 15:29:43 +0200 [thread overview]
Message-ID: <20160617132943.GA3336@nazgul.tnic> (raw)
In-Reply-To: <alpine.DEB.2.11.1606171351390.5839@nanos>
On Fri, Jun 17, 2016 at 01:53:53PM +0200, Thomas Gleixner wrote:
> It must be initialized otherwise you won't reach suspend. I have no idea how
> that can happen.
Btw, there's one other thing I'm seeing in the boot kernel, while it suspends.
It hardly is related though:
[ 42.046585] kvm: exiting hardware virtualization
[ 42.062446] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0010 address=0x0000000020001000 fl]
[ 42.255531] sd 3:0:0:0: [sdd] Synchronizing SCSI cache
[ 42.263159] sd 3:0:0:0: [sdd] Stopping disk
[ 43.090022] irq 16: nobody cared (try booting with the "irqpoll" option)
[ 43.099122] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.7.0-rc3+ #4
[ 43.107784] Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 EVO R2.0, BIOS 1503 01/16/23
[ 43.120143] 0000000000000000 ffff88043dd83e68 ffffffff812aacf3 ffff88003790e400
[ 43.130145] ffff88003790e49c ffff88043dd83e90 ffffffff810a5c3e ffff88003790e400
[ 43.140118] 0000000000000000[ 43.140201] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[ 43.140592] sd 2:0:0:0: [sdc] Stopping disk
[ 43.157217] 0000000000000010 ffff88043dd83ec8 ffffffff810a5fe7
[ 43.168302] Call Trace:
[ 43.173210] <IRQ> [<ffffffff812aacf3>] dump_stack+0x67/0x94
[ 43.181481] [<ffffffff810a5c3e>] __report_bad_irq+0x3e/0xd0
[ 43.189626] [<ffffffff810a5fe7>] note_interrupt+0x257/0x2a0
[ 43.197797] [<ffffffff810a32b9>] handle_irq_event_percpu+0xa9/0x1f0
[ 43.206655] [<ffffffff810a3440>] handle_irq_event+0x40/0x70
[ 43.214776] [<ffffffff810a68d6>] handle_fasteoi_irq+0xb6/0x170
[ 43.223166] [<ffffffff8101911a>] handle_irq+0x1a/0x30
[ 43.230748] [<ffffffff8168c7a6>] do_IRQ+0x66/0x100
[ 43.238045] [<ffffffff8168ac46>] common_interrupt+0x86/0x86
[ 43.246135] <EOI> [<ffffffff8133c7e8>] ? acpi_safe_halt+0x24/0x2c
[ 43.254884] [<ffffffff8133c7e6>] ? acpi_safe_halt+0x22/0x2c
[ 43.262987] [<ffffffff8133c810>] acpi_idle_do_entry+0x20/0x30
[ 43.271298] [<ffffffff8133cce1>] acpi_idle_enter+0x1dc/0x1fc
[ 43.279462] [<ffffffff8154ac2e>] cpuidle_enter_state+0x10e/0x300
[ 43.287980] [<ffffffff8154ae57>] cpuidle_enter+0x17/0x20
[ 43.295799] [<ffffffff8108f51a>] call_cpuidle+0x2a/0x40
[ 43.303528] [<ffffffff8108f94d>] cpu_startup_entry+0x2dd/0x3c0
[ 43.304279] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 43.306109] sd 1:0:0:0: [sdb] Stopping disk
[ 43.325777] [<ffffffff8103872a>] start_secondary+0x13a/0x150
[ 43.333868] handlers:
[ 43.338471] [<ffffffff8158d200>] azx_interrupt
[ 43.345298] Disabling IRQ #16
[ 43.848595] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 43.858068] sd 0:0:0:0: [sda] Stopping disk
[ 44.052892] pcieport 0000:00:04.0: System wakeup enabled by ACPI
[ 44.075715] ACPI: Preparing to enter system sleep state S5
[ 44.083818] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query honored via cmdline
[ 44.092258] reboot: Power down
[ 44.096326] acpi_power_off called
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2016-06-17 13:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 10:54 Borislav Petkov
2016-06-17 11:53 ` Thomas Gleixner
2016-06-17 13:29 ` Borislav Petkov [this message]
2016-06-17 14:33 ` Borislav Petkov
2016-06-17 15:28 ` Rafael J. Wysocki
2016-06-17 16:12 ` Borislav Petkov
2016-06-17 21:03 ` Rafael J. Wysocki
2016-06-18 1:11 ` Rafael J. Wysocki
2016-06-20 14:38 ` Rafael J. Wysocki
2016-06-20 18:29 ` Linus Torvalds
2016-06-20 21:15 ` Rafael J. Wysocki
2016-06-21 0:05 ` Rafael J. Wysocki
2016-06-21 1:22 ` Rafael J. Wysocki
2016-06-21 4:35 ` Logan Gunthorpe
2016-06-21 11:36 ` Rafael J. Wysocki
2016-06-21 18:04 ` Kees Cook
2016-06-21 23:29 ` Rafael J. Wysocki
2016-06-27 14:24 ` [PATCH v3] x86/power/64: Fix kernel text mapping corruption during image restoration (was: Re: ktime_get_ts64() splat during resume) Rafael J. Wysocki
2016-06-27 20:08 ` Borislav Petkov
2016-06-27 23:33 ` [PATCH v3] x86/power/64: Fix kernel text mapping corruption during image restoration Logan Gunthorpe
2016-06-29 14:48 ` Kees Cook
2016-06-30 1:52 ` Logan Gunthorpe
2016-06-30 2:20 ` Rafael J. Wysocki
2016-06-30 2:55 ` Rafael J. Wysocki
2016-06-30 3:56 ` Logan Gunthorpe
2016-06-30 12:16 ` Rafael J. Wysocki
2016-06-30 9:45 ` Borislav Petkov
2016-06-30 11:27 ` Rafael J. Wysocki
2016-06-30 13:17 ` [PATCH v4] " Rafael J. Wysocki
2016-06-30 15:05 ` Borislav Petkov
2016-06-30 15:17 ` Rafael J. Wysocki
2016-06-30 15:24 ` Andy Lutomirski
2016-06-30 15:29 ` Rafael J. Wysocki
2016-06-30 17:23 ` Andy Lutomirski
2016-06-30 16:11 ` [PATCH v5] " Rafael J. Wysocki
2016-06-30 17:02 ` Borislav Petkov
2016-06-30 21:47 ` Logan Gunthorpe
2016-06-20 8:17 ` ktime_get_ts64() splat during resume chenyu
2016-06-20 12:21 ` Rafael J. Wysocki
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=20160617132943.GA3336@nazgul.tnic \
--to=bp@alien8.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®