All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick J. LoPresti" <patl@users.sourceforge.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Atul.Mukker@lsil.com, linux-scsi@vger.kernel.org
Subject: Re: Linux 2.6.8.1 + megaraid-2.20.3.0 == Oops
Date: 21 Aug 2004 13:00:21 -0400	[thread overview]
Message-ID: <s5gr7q0sa2w.fsf@patl=users.sf.net> (raw)
In-Reply-To: <20040820160802.7b74cfa3.rddunlap@osdl.org>

"Randy.Dunlap" <rddunlap@osdl.org> writes:

> Looks like mraid_mm_init() hasn't done the
> 	INIT_LIST_HEAD(&adapters_list_g);
> yet.  You might be able to verify that by using
> "initcall_debug" on the kernel boot/command line.

Oh, I see now.  Yes, the initicall_debug trace shows that
mraid_mm_init() is not being called.  But megaraid_init() is, which
ultimately leads to the crash.

Is there some way to tell Linux about this dependency when the drivers
are non-modular?

 - Pat

  parent reply	other threads:[~2004-08-21 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 16:22 Linux 2.6.8.1 + megaraid-2.20.3.0 == Oops Patrick J. LoPresti
2004-08-20 23:08 ` Randy.Dunlap
2004-08-21 16:54   ` Patrick J. LoPresti
2004-08-21 17:00   ` Patrick J. LoPresti [this message]
2004-08-21 18:07     ` Randy.Dunlap
2004-08-22 19:12       ` Patrick J. LoPresti
2004-08-22 21:31         ` Randy.Dunlap

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='s5gr7q0sa2w.fsf@patl=users.sf.net' \
    --to=patl@users.sourceforge.net \
    --cc=Atul.Mukker@lsil.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.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.