From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eddie Subject: Re: LSI MegaRAID not recognised correctly in 64-bit. 2.6.29.6 Date: Thu, 17 Sep 2009 09:09:45 -0700 Message-ID: <4AB25F49.4060201@attglobal.net> References: <4AB10FC2.1080900@attglobal.net> <1253118717.4842.13.camel@mulgrave.site> <4AB1185E.1050208@attglobal.net> <4AB1A60A.5080702@attglobal.net> <1253203147.7845.11.camel@mulgrave.site> Reply-To: stunnel@attglobal.net Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from kcout01.prserv.net ([12.154.55.31]:57329 "EHLO kcout01.prserv.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753441AbZIQQJ6 (ORCPT ); Thu, 17 Sep 2009 12:09:58 -0400 In-Reply-To: <1253203147.7845.11.camel@mulgrave.site> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: James Bottomley Cc: linux-scsi@vger.kernel.org, linux-box James Bottomley wrote: > On Wed, 2009-09-16 at 19:59 -0700, Eddie wrote: > >>>> How much memory does your system have? >>>> >>>> Best guess in the 64 bit case is that the physical memory the kernel is >>>> doing DMA to isn't within the range of the card. You might be able to >>>> test this by booting with the max_addr=4G parameter in the 64 bit case. >>>> >>>> If it is, we'll have to get the DMA mask for this thing set up >>>> correctly. >>>> >>>> James >>>> >>>> >>> James, >>> >>> It's got 8Gig. >>> >>> I'll try your suggestion tonight, when I get home. >>> >>> Cheers, >>> Eddie >>> >>> >> OK, adding addappend = " max_addr=4G" to my lilo.conf made no >> difference. It still booted with all 8G. :( >> >> But, changing it to addappend = " mem=4G" seemed to do the trick. >> >> And, your guess might be correct. I now see the correct messages for >> the MegaRAID: >> >> scsi 4:4:0:0: Direct-Access MegaRAID LD 0 RAID5 1430G N661 PQ: 0 ANSI: 2 >> sd 4:4:0:0: [sda] 2930307072 512-byte hardware sectors: (1.50 TB/1.36 TiB) >> sd 4:4:0:0: [sda] Write Protect is off >> sd 4:4:0:0: [sda] Mode Sense: 00 00 00 00 >> sd 4:4:0:0: [sda] Asking for cache data failed >> sd 4:4:0:0: [sda] Assuming drive cache: write through >> sd 4:4:0:0: [sda] 2930307072 512-byte hardware sectors: (1.50 TB/1.36 TiB) >> sd 4:4:0:0: [sda] Write Protect is off >> sd 4:4:0:0: [sda] Mode Sense: 00 00 00 00 >> sd 4:4:0:0: [sda] Asking for cache data failed >> sd 4:4:0:0: [sda] Assuming drive cache: write through >> sda: sda1 >> sd 4:4:0:0: [sda] Attached SCSI disk >> sd 4:4:0:0: Attached scsi generic sg1 type 0 >> > > Hmm, so the driver looks to do this correctly. By default it sets a 32 > bit DMA mask but it raises it to 64 bits for certain boards which can > support that (based on the PCI ids). Can you do an lspci -n -v and send > the output? That will tell me whether the board got a 64 bit mask. > > Thanks, > > James > > James, This is when booted with the "mem=4G" override still in place. If you need it without that, when it fails to "see" the device, let me know, and I'll re-boot tonight to gather it: 01:04.0 0104: 101e:1960 (rev 02) Subsystem: 101e:0511 Flags: bus master, fast Back2Back, medium devsel, latency 64, IRQ 19 Memory at b8000000 (32-bit, prefetchable) [size=64K] [virtual] Expansion ROM at b8010000 [disabled] [size=32K] Capabilities: [80] Power Management version 2 Kernel driver in use: megaraid Kernel modules: megaraid_mbox Cheers, Eddie