Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269803AbUJMUU5 (ORCPT ); Wed, 13 Oct 2004 16:20:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269806AbUJMUU5 (ORCPT ); Wed, 13 Oct 2004 16:20:57 -0400 Received: from fire.osdl.org ([65.172.181.4]:7362 "EHLO fire-1.osdl.org") by vger.kernel.org with ESMTP id S269803AbUJMUUx (ORCPT ); Wed, 13 Oct 2004 16:20:53 -0400 Message-ID: <416D8C33.9080401@osdl.org> Date: Wed, 13 Oct 2004 13:12:35 -0700 From: "Randy.Dunlap" Organization: OSDL User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brad Fitzpatrick CC: Jeff Garzik , linux-kernel@vger.kernel.org Subject: Re: [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB References: <416D8999.7080102@pobox.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2442 Lines: 75 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) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/