public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: Li Shaohua <shaohua.li@intel.com>,
	"Antonino A. Daplas" <adaplas@pol.net>,
	linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net,
	len.brown@intel.com, zwane@linuxpower.ca,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 6/6]suspend/resume SMP support
Date: Sun, 24 Apr 2005 00:41:55 +0200	[thread overview]
Message-ID: <20050423224154.GG1884@elf.ucw.cz> (raw)
In-Reply-To: <20050423153501.5286b6c6.akpm@osdl.org>

Hi!

> > > Code: d2 74 bd fc 8b 44 24 28 b9 0e 00 00 00 8b 74 24 14 01 c6 b8 0e
> > > 00 00 00 89 74 24 1c 8b 74 24 30 89 44 24 10 8b 7c 24 1c 83 c6 10 <f3>
> > > a5 8b 74 24 24 8b 44 24 1c 89 4c 24 10 01 ee f7 d5 21 ee 89
> > >  <0>Kernel panic - not syncing: Attempted to kill the idle task!
> > >  Stuck ??
> > > Inquiring remote APIC #0...
> > > ... APIC #0 ID: 00000000
> > > ... APIC #0 VERSION: 00040011
> > > ... APIC #0 SPIV: 000000ff
> > > root@hobit:/sys/devices/system/cpu/cpu1#
> > Andrew,
> > Below patch fixed Pavel's oops. But strange is the 'system_state' check
> > is added for CPU hotplug by Rusty. This really makes me confused. Could
> > you please look at it.
> 
> Well as the comment says, if this CPU isn't online yet, and if the system
> has not yet reached SYSTEM_RUNNING state then we bale out of the printk
> because this cpu's per-cpu resources may not yet be fully set up.
> 
> 
> > This can be reproduced 100% with radeonfb driver load. Attached is the
> > dmesg of an oops. It seems the 'objp' parameter for
> > 'cache_alloc_debugcheck_after' is invalid.
> > 
> > --- a/kernel/printk.c	2005-04-12 10:12:19.000000000 +0800
> > +++ b/kernel/printk.c	2005-04-13 17:22:40.912897328 +0800
> > @@ -624,8 +624,7 @@ asmlinkage int vprintk(const char *fmt, 
> >  			log_level_unknown = 1;
> >  	}
> >  
> > -	if (!cpu_online(smp_processor_id()) &&
> > -	    system_state != SYSTEM_RUNNING) {
> > +	if (!cpu_online(smp_processor_id())) {
> >  		/*
> >  		 * Some console drivers may assume that per-cpu resources have
> >  		 * been allocated.  So don't allow them to be called by this
> > 
> 
> That being said, I don't see why your patch should fix the oops.  The test
> (system_state != SYSTEM_RUNNING) should be returning true at this time.

We were booting CPU on running system. system_state was definitely
SYSTEM_RUNNING, but we were trying to bring CPU#1 online...

Check is wrong. If cpu is not yet online, we may not printk on
it... It does not really depend on system_state...

								Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.

  reply	other threads:[~2005-04-23 22:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  5:31 [PATCH 6/6]suspend/resume SMP support Li Shaohua
2005-04-12  9:43 ` Pavel Machek
2005-04-12 10:51 ` Pavel Machek
2005-04-12 12:40   ` Li Shaohua
2005-04-13  8:32     ` Pavel Machek
2005-04-14  8:27       ` Li Shaohua
2005-04-14  8:40         ` Li Shaohua
2005-04-23 22:35         ` Andrew Morton
2005-04-23 22:41           ` Pavel Machek [this message]
2005-04-25  0:49           ` Li Shaohua
2005-05-26  2:58         ` Hotplug CPU printk issue Shaohua Li
2005-05-26  3:48           ` Andrew Morton
2005-05-26  5:43             ` Shaohua Li
2005-05-26  5:52               ` Andrew Morton
2005-05-26 19:32                 ` David Mosberger
2005-05-27  2:08                   ` Rusty Russell
2005-04-28  7:22 ` [PATCH 6/6]suspend/resume SMP support Andrew Morton
2005-04-28  7:28   ` Li Shaohua
2005-04-28  7:41     ` Andrew Morton
2005-04-28  8:29       ` Li Shaohua
2005-04-28  8:35         ` Pavel Machek
2005-04-28  9:04           ` [ACPI] " Rafael J. Wysocki
2005-04-28  7:35   ` Li Shaohua
2005-04-28  7:42     ` Pavel Machek
2005-04-28  8:11       ` [ACPI] " Yu, Luming
2005-04-28  8:20         ` Pavel Machek
2005-04-28  8:34           ` Yu, Luming

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=20050423224154.GG1884@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=zwane@linuxpower.ca \
    /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