public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andrew Morton" <morton@nortelnetworks.com>
To: "Boerner, Brian" <Brian_Boerner@adaptec.com>
Cc: Keith Owens <kaos@ocs.com.au>,
	"'linux-kernel@vger.redhat.com'" <linux-kernel@vger.kernel.org>
Subject: Re: aacraid for 2.4.0
Date: Mon, 04 Dec 2000 23:34:16 +0000	[thread overview]
Message-ID: <3A2C29F8.D8D57F92@asiapacificm01.nt.com> (raw)
In-Reply-To: Your message of "Mon, 04 Dec 2000 17:31:04 CDT." <E9EF680C48EAD311BDF400C04FA07B612D4D71@ntcexc02.ntc.adaptec.com> <1119.975970561@kao2.melbourne.sgi.com>

Keith Owens wrote:
> 
> On Mon, 4 Dec 2000 17:31:04 -0500 ,
> "Boerner, Brian" <Brian_Boerner@adaptec.com> wrote:
> >The driver
> >is generating a segmentation fault and produces and oops. I have included
> >Code: 00 00 00 00 00 00 00 00 b8 00 00 00 83 ec 34 68 00 2c 82 c8
> 
> That code looks bad.  I suspect you are using an old modutils on
> current kernels.  modutils < 2.3.15 incorrectly load modules on recent
> kernels, you should be running modutils 2.3.21 for 2.4 kernels.

This can happen if you get your __devinit and __devinitdata declarations
tangled up.  If you have a table which is declared __devinit instead of
__devinitdata then subsequently declared functions end up with their
text being placed in the rodata section.  You only find out about this
because the assembler pads .align statements with nulls.  Hard to find.

So if the modutils upgrade doesn't help, remove all `init' thingies and
see if the problem goes away.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-12-05  0:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-04 22:31 aacraid for 2.4.0 Boerner, Brian
2000-12-04 22:49 ` Andi Kleen
2000-12-04 22:58   ` Russell King
2000-12-04 22:56 ` Keith Owens
2000-12-04 23:34   ` Andrew Morton [this message]

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=3A2C29F8.D8D57F92@asiapacificm01.nt.com \
    --to=morton@nortelnetworks.com \
    --cc=Brian_Boerner@adaptec.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox