From: Andrew Morton <akpm@osdl.org>
To: "S. Anderson" <sa@xmission.com>
Cc: sa@xmission.com, pavel@xal.co.uk, linux-kernel@vger.kernel.org,
adaplas@pol.net
Subject: Re: OOPS 2.6.0-test2, modprobe i810fb
Date: Mon, 28 Jul 2003 22:59:14 -0700 [thread overview]
Message-ID: <20030728225914.4f299586.akpm@osdl.org> (raw)
In-Reply-To: <20030728231812.A20738@xmission.xmission.com>
"S. Anderson" <sa@xmission.com> wrote:
>
> Thanks, that fixes the oops Pavel reported!
>
> But I now realize the oops I am getting is different...
>
> It happens only if any of these "i810fb, i810_audio or intel-agp"
> are compiled in the kernel or insterted as modules.
>
> i810fb, i810_audio or intel-agp load up fine and seem to all work
> properly. I only get the oops when I put a card into my cardbus slot.
>
> this is what i think happens, when I put the card in, it sets off some
> functions that will try to get a driver for the card I just inserted.
> when it gets to the pci_bus_match function, my cards vendor and device
> numbers are tested against a drivers id_table. when that driver is
> "i810fb, i810_audio or intel-agp" (and i810fb, i810_audio or intel-agp
> is allready loaded) the id_table is at an address that cant be handled,
> thus cauing the oops. I am having trouble figuring out why
> pci_drv->id_table isnt valid in this case.
Everything seems happy here:
vmm:/home/akpm> lsmod
Module Size Used by
i810fb 31572 0
cfbcopyarea 4700 1 i810fb
vgastate 10660 1 i810fb
cfbimgblt 4068 1 i810fb
cfbfillrect 4820 1 i810fb
intel_agp 16940 1
agpgart 32496 1 intel_agp
i810_audio 34208 0
ac97_codec 18932 1 i810_audio
rtc 15744 0
Can you do modprobe-by-hand, see which one causes the oops?
next prev parent reply other threads:[~2003-07-29 5:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 17:18 OOPS 2.6.0-test2, modprobe i810fb Pavel Rabel
2003-07-29 2:19 ` S. Anderson
2003-07-29 3:26 ` Andrew Morton
2003-07-29 5:18 ` S. Anderson
2003-07-29 5:32 ` Andrew Morton
2003-07-30 2:56 ` Bill Davidsen
2003-07-30 20:56 ` Michael Driscoll
2003-07-29 5:59 ` Andrew Morton [this message]
2003-07-29 7:24 ` S. Anderson
2003-07-29 7:54 ` Andrew Morton
2003-07-29 8:18 ` S. Anderson
2003-07-29 12:00 ` Alan Cox
2003-07-29 19:59 ` Andrew Morton
2003-07-29 23:04 ` S. Anderson
2003-07-29 9:34 ` Pavel Rabel
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=20030728225914.4f299586.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adaplas@pol.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@xal.co.uk \
--cc=sa@xmission.com \
/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.