From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Brad Fitzpatrick <brad@danga.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB
Date: Wed, 13 Oct 2004 13:12:35 -0700 [thread overview]
Message-ID: <416D8C33.9080401@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0410131302190.31327@danga.com>
Brad Fitzpatrick wrote:
> On Wed, 13 Oct 2004, Jeff Garzik wrote:
>
>
>>Brad Fitzpatrick wrote:
>>
>>>I'm reporting an oops. Details follow.
>>>
>>>I have two of these machines. I will happily be anybody's guinea pig
>>>to debug this. (more details, access to machine, try patches, kernels...)
>>>Machines aren't in production.
>>>
>>>- Brad
>>>
>>>
>>>Kernel: 2.6.9-rc4 vanilla (.config below)
>>>
>>>Hardware: IBM eServer 325, Dual Opteron 8GB ram (more info below)
>>>
>>>Pre-crash and crash:
>>>
>>>a1:~# mke2fs /dev/mapper/raid10-data
>>>mke2fs 1.35 (28-Feb-2004)
>>>Filesystem label=
>>>OS type: Linux
>>>Block size=4096 (log=2)
>>>Fragment size=4096 (log=2)
>>>25608192 inodes, 51200000 blocks
>>>2560000 blocks (5.00%) reserved for the super user
>>>First data block=0
>>>1563 block groups
>>>32768 blocks per group, 32768 fragments per group
>>>16384 inodes per group
>>>Superblock backups stored on blocks:
>>> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
>>> 4096000, 7962624, 11239424, 20480000, 23887872
>>>
>>>Writing inode tables: 1091/1563
>>>Message from syslogd@localhost at Wed Oct 13 11:46:01 2004 ...
>>>localhost kernel: Oops: 0000 [1] SMP
>>>
>>>Message from syslogd@localhost at Wed Oct 13 11:46:01 2004 ...
>>>localhost kernel: CR2: 0000000000001770
>>
>>
>>What's your block device configuration? What block devices are sitting
>>on top of what other block devices?
>
>
> /dev/mapper/raid10-data is a LV taking 200GB of a 280GB VG ("raid10") with
> a single PV in it: /dev/sdb1 -- ips driver, IBM ServeRAID 6M card,
> representing a RAID 10 atop 8 SCSI disks.
>
> I just made a new kernel without NUMA and made a filesystem on /dev/sdb1
> directly instead of using LVM and it worked fine, if not a little slowly.
>
> Now that I know it /can/ work, I'll try and narrow down whose fault it is:
> NUMA or LVM.
Very similar to
http://marc.theaimsgroup.com/?l=linux-kernel&m=109328505204081&w=2
and its follow-up:
http://marc.theaimsgroup.com/?l=linux-kernel&m=109330259511819&w=2
but no solutions there.
--
~Randy
MOTD: Always include version info.
(Again. Sometimes I think ln -s /usr/src/linux/.config .signature)
next prev parent reply other threads:[~2004-10-13 20:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 19:11 [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB Brad Fitzpatrick
2004-10-13 20:01 ` Jeff Garzik
2004-10-13 20:09 ` Brad Fitzpatrick
2004-10-13 20:12 ` Randy.Dunlap [this message]
2004-10-13 20:32 ` Brad Fitzpatrick
2004-10-13 20:34 ` Randy.Dunlap
2004-10-13 21:21 ` Andi Kleen
2004-10-14 6:07 ` Brad Fitzpatrick
2004-10-14 18:29 ` Brad Fitzpatrick
2004-10-14 18:40 ` Andi Kleen
2004-10-13 20:45 ` Jeff Garzik
2004-10-13 20:49 ` Brad Fitzpatrick
2004-10-13 20:50 ` Jeff Garzik
2004-10-13 20:38 ` Gnome-2.8 stoped working on kernel-2.6.9-rc4-mm1 Stef van der Made
2004-10-13 20:47 ` Radoslaw Szkodzinski
2004-10-13 21:16 ` Stef van der Made
2004-10-13 22:08 ` Buddy Lucas
2004-10-13 23:07 ` Jon Masters
2004-10-13 21:13 ` Jesse Stockall
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=416D8C33.9080401@osdl.org \
--to=rddunlap@osdl.org \
--cc=brad@danga.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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