All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
Cc: "Ju, Seokmann" <Seokmann.Ju@engenio.com>,
	Andrew Morton <akpm@osdl.org>,
	"Kolli, Neela" <Neela.Kolli@engenio.com>,
	linux-scsi@vger.kernel.org,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 6080] New: New Megaraid Module Problem
Date: Fri, 17 Feb 2006 10:21:46 +0100	[thread overview]
Message-ID: <43F595AA.5090603@suse.de> (raw)
In-Reply-To: <9738BCBE884FDB42801FAD8A7769C265142091@NAMAIL1.ad.lsil.com>

Ju, Seokmann wrote:
> Hi,
> On Thursday, February 16, 2006 9:36 AM Seokmann Ju wrote:
>> I've verified the 'megaraid' driver that is available on GIT 
>> kernel (2.6.16-rc2).
>> The driver 'megaraid.ko' is working fine on the kernel.
>> However, I'm working on another issue related to this driver. 
>> On SuSE SLES 10 (kernel 2.6.16-rc1-git3-7), the kernel claims 
>> that the driver has loaded, but it won't detect the 
>> controller nor scan the drives.
>> Both kernel (GIT kernel and SLES10) have same 'megaraid' driver.
>> I'll update here for any progress on it.
> I've also test 'megaraid.ko' driver on latest GIT kernel 2.6.16-rc3.
> The driver works fine as expected. I've ran the basic I/O test after file system created on the device.
> 
Isn't the megaraid i960 based? Then it might well be that it collides
with the generic i2o modules which are loaded previously by default.

So check whether any of those i2o modules are loaded and unload them
before continuing.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-02-17  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 19:50 [Bugme-new] [Bug 6080] New: New Megaraid Module Problem Ju, Seokmann
2006-02-17  9:21 ` Hannes Reinecke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-17 17:24 Ju, Seokmann
2006-02-16 14:36 Ju, Seokmann
     [not found] <200602152214.k1FMEuhK012133@fire-2.osdl.org>
2006-02-15 22:32 ` Andrew Morton

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=43F595AA.5090603@suse.de \
    --to=hare@suse.de \
    --cc=Neela.Kolli@engenio.com \
    --cc=Seokmann.Ju@engenio.com \
    --cc=Seokmann.Ju@lsil.com \
    --cc=akpm@osdl.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.