public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: stunnel@attglobal.net
Cc: linux-scsi@vger.kernel.org, linux-box <bo.yang@lsi.com>
Subject: Re: LSI MegaRAID not recognised correctly in 64-bit.  2.6.29.6
Date: Thu, 17 Sep 2009 09:59:07 -0600	[thread overview]
Message-ID: <1253203147.7845.11.camel@mulgrave.site> (raw)
In-Reply-To: <4AB1A60A.5080702@attglobal.net>

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



  reply	other threads:[~2009-09-17 15:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:18 LSI MegaRAID not recognised correctly in 64-bit. 2.6.29.6 Eddie
2009-09-16 16:31 ` James Bottomley
2009-09-16 16:54   ` Eddie
2009-09-17  2:58     ` Eddie
2009-09-17  2:59     ` Eddie
2009-09-17 15:59       ` James Bottomley [this message]
2009-09-17 16:09         ` Eddie
2009-09-17 18:39           ` James Bottomley
2009-09-17 20:28             ` James Bottomley
2009-09-18 13:00               ` FUJITA Tomonori
2009-09-18 14:11                 ` Matthew Wilcox
2009-09-18 14:18                   ` FUJITA Tomonori
2009-09-19  7:03                     ` Eddie
2009-09-19  7:55                       ` FUJITA Tomonori
2009-09-19 15:24                         ` Eddie
2009-09-21 13:51                           ` FUJITA Tomonori
2009-09-21 15:34                             ` James Bottomley
2009-09-21 15:37                               ` Yang, Bo

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=1253203147.7845.11.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=bo.yang@lsi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stunnel@attglobal.net \
    /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