From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp APIC oopsen (was Re: swsusp ooms)
Date: Sat, 14 Oct 2006 01:51:09 -0700 [thread overview]
Message-ID: <20061014015109.0ff2c52f.akpm@osdl.org> (raw)
In-Reply-To: <20061014083227.GA3868@elf.ucw.cz>
On Sat, 14 Oct 2006 10:32:27 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> On Sat 2006-10-14 10:22:37, Pavel Machek wrote:
> > Hi!
> >
> > (cc-ed to public list)
> >
> > > Andrew Morton <akpm@osdl.org> wrote:
> > >
> > > > and I'm not having much luck. See
> > > >
> > > > http://userweb.kernel.org/~akpm/s5000340.jpg and
> > > > http://userweb.kernel.org/~akpm/s5000339.jpg
> > >
> > > Running an UP kernel and disabling local APIC avoided the oopses and
> > > allowed me to confirm that it was leaking. whoops.
> >
> > I wonder why everyone but me sees those APIC problems?
> >
> > Anyway, there's one more problem in -rc1: boot order changed, and (at
> > least with paralel boot options), swsusp gets initialized *after*
> > swsusp => bad, but should be easy to fix.
>
> Sorry, I meant:
>
> "sata is initialized *after* swsusp => bad".
Which patch made this change, and why?
next prev parent reply other threads:[~2006-10-14 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061009213359.7f2806b6.akpm@osdl.org>
[not found] ` <200610132231.08643.rjw@sisk.pl>
[not found] ` <20061013140000.329e8854.akpm@osdl.org>
[not found] ` <200610132307.47162.rjw@sisk.pl>
[not found] ` <20061014002504.1ab10ee9.akpm@osdl.org>
[not found] ` <20061014004046.670ddd76.akpm@osdl.org>
2006-10-14 8:22 ` swsusp APIC oopsen (was Re: swsusp ooms) Pavel Machek
2006-10-14 8:32 ` Pavel Machek
2006-10-14 8:51 ` Andrew Morton [this message]
2006-10-25 10:43 ` swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms)) Pavel Machek
2006-10-25 15:46 ` Andrew Morton
2006-10-25 16:51 ` Pavel Machek
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=20061014015109.0ff2c52f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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