linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Mario Mikocevic <mario.mikocevic@htnet.hr>, linux-kernel@vger.kernel.org
Subject: Re: OOPS 2.6.0-test4 repeatable
Date: Mon, 25 Aug 2003 15:06:08 +0100	[thread overview]
Message-ID: <20030825150608.A15816@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030825143034.D30952@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Mon, Aug 25, 2003 at 02:30:34PM +0100

On Mon, Aug 25, 2003 at 02:30:34PM +0100, Russell King wrote:
> > Aug 25 13:42:26 mozz-r40 kernel: pci_dev: 0000:03:00.0 driver: d090c400 name: acx100_pci table: d090c3a0 probe: d0823000
> > Aug 25 13:42:26 mozz-r40 kernel: Unable to handle kernel paging request at virtual address d0823000
> 
> It's probe function is at address 0xd0823000 which is where your OOPS
> is happening.  I suspect you'll find the acx100 pci probe function is
> marked with __init.  That's a bug - it must not be.

Well, here it is:

static int __init
acx100_probe_pci(struct pci_dev *pdev, const struct pci_device_id *id)

Please report this to the ACX people as a bug - the probe function must
/not/ be marked as __init.  If they want them to be discarded if hotplug
is disabled, they must be marked as __devinit.  However, in 2.6 kernels,
they must not be marked as __init nor __devinit in any case.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-08-25 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25  9:18 OOPS 2.6.0-test4 repeatable Mario Mikocevic
2003-08-25  9:40 ` Russell King
2003-08-25 10:25   ` Mario Mikocevic
2003-08-25 10:55     ` Russell King
2003-08-25 12:45       ` Mario Mikocevic
2003-08-25 13:30         ` Russell King
2003-08-25 14:06           ` Russell King [this message]
2003-08-25 13:07       ` OOPS 2.6.0-test4 (almost) repeatable Mario Mikocevic

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=20030825150608.A15816@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.mikocevic@htnet.hr \
    /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;
as well as URLs for NNTP newsgroup(s).