From: Borislav Petkov <bp@alien8.de>
To: vitalif@yourcmc.ru, Thomas Gleixner <tglx@linutronix.de>
Cc: Ben Hutchings <ben@decadent.org.uk>,
"Venkatesh Pallipadi (Venki)" <venki@google.com>,
700333@bugs.debian.org, LKML <linux-kernel@vger.kernel.org>,
Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Bug#700333: Stack trace
Date: Sun, 21 Apr 2013 00:55:16 +0200 [thread overview]
Message-ID: <20130420225516.GB4649@pd.tnic> (raw)
In-Reply-To: <cc9020446ea75ed733ec96c505039f2a@yourcmc.ru>
+ tglx.
On Sun, Apr 21, 2013 at 01:38:33AM +0400, vitalif@yourcmc.ru wrote:
> >>Stack trace picture is here:
> >>http://vmx.yourcmc.ru/var/pics/IMG_20130306_141045.jpg
> >
> >Vitaliy reported that his system crashes when suspending to disk.
> >This
> >was a regression from 3.2 to 3.7, and remains in 3.8. Some
> >details of
> >this system are in the bug log at <http://bugs.debian.org/700333>.
> >
> >The photo shows a BUG in hrtimer_interrupt() after making the
> >hibernation image and while resuming the non-boot CPUs. The HPET
> >interrupt handler was called immediately after it was registered
> >for CPU
> >2 (?), before the corresponding clock_event_device was registered.
> >
> >Seems like an obvious race condition, but then shouldn't the HPET
> >have
> >been stopped while the CPU was previously offlined? And it's strange
> >that this system apparently hits the race quite reliably.
>
> Anyone?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-04-20 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4bded8a24b0719d575f6ffa6b38aebb6@yourcmc.ru>
[not found] ` <1362490501.3768.409.camel@deadeye.wl.decadent.org.uk>
[not found] ` <1b81bc6219ee47a5b8e53d03e9944939@yourcmc.ru>
[not found] ` <20130305203952.GZ9079@decadent.org.uk>
[not found] ` <4e8c511dcfd811c0f2ab822adaf52e50@yourcmc.ru>
[not found] ` <1362536476.3768.416.camel@deadeye.wl.decadent.org.uk>
[not found] ` <15ec7b46ebd929a67caea0d80b324af9@yourcmc.ru>
2013-03-11 3:10 ` Bug#700333: Stack trace Ben Hutchings
2013-04-20 21:38 ` vitalif
2013-04-20 22:55 ` Borislav Petkov [this message]
2013-04-22 12:15 ` Thomas Gleixner
2013-04-25 9:41 ` Thomas Gleixner
2013-04-27 15:08 ` vitalif
2013-04-27 15:49 ` Borislav Petkov
2013-04-28 13:26 ` vitalif
2013-04-28 19:05 ` Borislav Petkov
2013-04-28 19:53 ` Thomas Gleixner
2013-04-30 21:04 ` vitalif
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=20130420225516.GB4649@pd.tnic \
--to=bp@alien8.de \
--cc=700333@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
--cc=vitalif@yourcmc.ru \
/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.