From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423247AbWJYKn1 (ORCPT ); Wed, 25 Oct 2006 06:43:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423256AbWJYKn1 (ORCPT ); Wed, 25 Oct 2006 06:43:27 -0400 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:31413 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S1423247AbWJYKn0 (ORCPT ); Wed, 25 Oct 2006 06:43:26 -0400 Date: Wed, 25 Oct 2006 12:43:18 +0200 From: Pavel Machek To: Andrew Morton Cc: "Rafael J. Wysocki" , kernel list , Greg KH Subject: swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms)) Message-ID: <20061025104318.GA1743@elf.ucw.cz> References: <20061009213359.7f2806b6.akpm@osdl.org> <200610132231.08643.rjw@sisk.pl> <20061013140000.329e8854.akpm@osdl.org> <200610132307.47162.rjw@sisk.pl> <20061014002504.1ab10ee9.akpm@osdl.org> <20061014004046.670ddd76.akpm@osdl.org> <20061014082237.GA3818@elf.ucw.cz> <20061014083227.GA3868@elf.ucw.cz> <20061014015109.0ff2c52f.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061014015109.0ff2c52f.akpm@osdl.org> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.11+cvs20060126 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > > (cc-ed to public list) > > > > > > > Andrew Morton 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? CONFIG_PCI_MULTITHREAD_PROBE is the setting responsible, and IIRC that's Greg's code. Now... what is the recommended way to wait for hard disks to become online? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html