From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org
Cc: "bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
joachim.deguara@amd.com, Andi Kleen <ak@suse.de>
Subject: Re: [Bugme-new] [Bug 8814] New: PCI numa_node not set correctly
Date: Thu, 26 Jul 2007 10:57:31 -0700 [thread overview]
Message-ID: <20070726105731.f7dc2cae.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-8814-10286@http.bugzilla.kernel.org/>
On Thu, 26 Jul 2007 05:13:12 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8814
>
> Summary: PCI numa_node not set correctly
> Product: Platform Specific/Hardware
> Version: 2.5
> KernelVersion: 2.6.22-rc7-git4-ak-070710
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: x86-64
> AssignedTo: ak@suse.de
> ReportedBy: joachim.deguara@amd.com
>
>
> Most recent kernel where this bug did not occur:
> Distribution: SLES10 with -ak kernel
> Hardware Environment: Tyan 4985
> Software Environment:
> Problem Description:
>
> This hardware is a 4 socket Opteron with the normal I/O Hub hanging off of node
> 0 but also with a PCIe bridge and Networking attached to node 1. Looking
> through the code, the node of the pci device gets exported to sysfs and set by
> k8-bus.c. However looking at the value of numa_node for all devices in sysfs
> returned 0.
>
> Steps to reproduce:
> find /sys -name 'numa_node'|xargs cat
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
parent reply other threads:[~2007-07-26 17:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-8814-10286@http.bugzilla.kernel.org/>]
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=20070726105731.f7dc2cae.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=joachim.deguara@amd.com \
--cc=linux-mm@kvack.org \
/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