public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Bryce Harrington <bryce@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	vatsa@in.ibm.com, torvalds@osdl.org,
	linux-kernel@vger.kernel.org, shaohua.li@intel.com,
	hotplug_sig@osdl.org, lhcs-devel@lists.sourceforge.net
Subject: Re: Status on CPU hotplug issues
Date: Sat, 7 Oct 2006 21:57:49 +0000	[thread overview]
Message-ID: <20061007215749.GC4277@ucw.cz> (raw)
In-Reply-To: <20061006231012.GH22139@osdl.org>

Hi!

> 1.  Oops offlining cpu twice on AMD64 (but not on EM64t)
>     with the 2.6.18-git22 kernel
> 
>     Reported to hotplug lists 10/05:
>       http://lists.osdl.org/pipermail/hotplug_sig/2006-October/000680.html
> 
>     To recreate: offline, online, and then offline a CPU, then oopses
>       http://crucible.osdl.org/runs/2397/sysinfo/amd01.console
>       http://crucible.osdl.org/runs/2397/sysinfo/amd01.2/proc/config
> 
>     Here's a snippet of the oops:
> 
> # echo 0 > /sys/devices/system/cpu/cpu1/online
> 
>  Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
>  [<ffffffff80255287>] __drain_pages+0x29/0x5f
> PGD 7e56d067 PUD 7ee80067 PMD 0
> Oops: 0000 [1] PREEMPT SMP
> CPU 0
> Modules linked in:
> Pid: 7203, comm: bash Tainted: G   M  2.6.18-git22 #1
                                 ~~~~~
kernel is unhappy here. Forced module unload?

-- 
Thanks for all the (sleeping) penguins.

  parent reply	other threads:[~2006-10-07 22:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16 17:44 [PATCH] Check for online cpus before bringing them up Srivatsa Vaddagiri
2006-03-17  1:08 ` Andrew Morton
2006-03-17  1:16   ` Shaohua Li
2006-03-17  8:46   ` Srivatsa Vaddagiri
2006-03-17  9:04     ` Andrew Morton
2006-03-17 14:13       ` Srivatsa Vaddagiri
2006-03-18 14:09         ` Ashok Raj
2006-03-21  1:08           ` Shaohua Li
2006-03-21  1:25             ` Ashok Raj
2006-03-21  1:36               ` Shaohua Li
2006-10-06 23:10       ` Status on CPU hotplug issues Bryce Harrington
2006-10-06 23:29         ` Andrew Morton
2006-10-07  0:00           ` Bryce Harrington
2006-10-07 10:35             ` Pavel Machek
2006-10-07 20:42               ` Bryce Harrington
2006-10-08 18:29                 ` Heiko Carstens
2006-10-08 19:14                   ` Pavel Machek
2006-10-11  1:08                     ` [BUG] 2.6.19-rc1-mm1: fs/file.c138 on ia64 Bryce Harrington
2006-10-11  1:15                       ` Andrew Morton
2006-10-11  5:38                         ` Bryce Harrington
2006-10-07 10:24           ` Status on CPU hotplug issues Pavel Machek
2006-10-07 20:25             ` Bryce Harrington
2006-10-08 19:13               ` Pavel Machek
2006-10-09  7:42                 ` Bryce Harrington
2006-10-07 21:57         ` Pavel Machek [this message]
2006-10-09 21:40           ` Randy Dunlap
2006-10-23 22:26             ` Bryce Harrington
2006-11-08  5:35               ` Randy Dunlap
2006-11-08  5:52                 ` Bryce Harrington
2006-03-17 12:21     ` [PATCH] Check for online cpus before bringing them up Ashok Raj
2006-03-17 13:59       ` Srivatsa Vaddagiri

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=20061007215749.GC4277@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=bryce@osdl.org \
    --cc=hotplug_sig@osdl.org \
    --cc=lhcs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=torvalds@osdl.org \
    --cc=vatsa@in.ibm.com \
    /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