From: Mikael Pettersson <mikpe@csd.uu.se>
To: arjanv@redhat.com, schierlm@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Local APIC bug?
Date: Mon, 5 Jan 2004 23:00:10 +0100 (MET) [thread overview]
Message-ID: <200401052200.i05M0AX0002410@harpo.it.uu.se> (raw)
On Sun, 28 Dec 2003 21:07:28 +0100, Michael Schierl wrote:
>>> However, I'd appreciate if someone had any idea why the kernel crashes
>>> when trying to resume. Deadlocks...?
>>
>>most bioses on laptops that I have seen don't actually restore the apic
>>state on resume (since they don't expect the apic to be used at all)
>>which results in entirely horked irq's on resume -> kernel crashes.
Our local APIC PM code saves the local APIC state and disables it
before suspend, and restores it and reenables the local APIC after
resume.
>Thanks. However, my laptop crashes on *suspend* when APIC is on and on
>*resume* when APIC is off...
>
>And on -test3 it did not crash.
>
>jftr: on 2.4.x it crashed on resume as well. Someone trying to prevent
>me to use stable kernels on my laptop? ;-(
Do you use APM? How do you suspend? With "apm --suspend" or by e.g.
closing the lid? In the latter case, does your APM BIOS post the
suspend event to us before actually suspending?
An APM BIOS that crashes in SMM code before posting the suspend event,
or that skips posting the event altogether, probably won't work with
an enabled local APIC. Not much we can do about that.
/Mikael
next reply other threads:[~2004-01-05 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 22:00 Mikael Pettersson [this message]
2004-01-05 22:17 ` Michael Schierl
[not found] <17ss4-23P-3@gated-at.bofh.it>
[not found] ` <17ss4-23P-5@gated-at.bofh.it>
[not found] ` <17ss5-23P-7@gated-at.bofh.it>
[not found] ` <17ss5-23P-9@gated-at.bofh.it>
[not found] ` <17ss5-23P-11@gated-at.bofh.it>
[not found] ` <17ss4-23P-1@gated-at.bofh.it>
[not found] ` <17sLs-2sN-1@gated-at.bofh.it>
2003-12-28 20:07 ` Michael Schierl
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=200401052200.i05M0AX0002410@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schierlm@gmx.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®