linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: DevilKin-LKML <devilkin-lkml@blindguardian.org>
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
Date: Wed, 23 Apr 2003 20:43:41 +0100	[thread overview]
Message-ID: <20030423204341.A19573@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200304232050.41230.devilkin-lkml@blindguardian.org>; from devilkin-lkml@blindguardian.org on Wed, Apr 23, 2003 at 08:50:39PM +0200

On Wed, Apr 23, 2003 at 08:50:39PM +0200, DevilKin-LKML wrote:
> Unable to handle kernel paging request at virtual address d10545c0
>  printing eip:
> c01b0368
> *pde = 0fb66067
> *pte = 00000000
> Oops: 0000 [#1]
> CPU:    0
> EIP:    0060:[<c01b0368>]    Not tainted
> EFLAGS: 00010286
> EIP is at pci_bus_match+0x18/0xb0
> eax: 00000000   ebx: cf2a8800   ecx: d10545c0   edx: 00000000
> esi: cf2a884c   edi: ffffffed   ebp: c12d284c   esp: ce591e88
> ds: 007b   es: 007b   ss: 0068
> Process pcmcia/0 (pid: 388, threadinfo=ce590000 task=ce6f7300)
> Stack: d109edc8 c01d1abf cf2a884c d109edc8 d109edf8 cf2a884c c02d7ff8 c01d1b5f 
>        cf2a884c d109edc8 cf2a884c c02d7fa0 cf2a8888 c01d1d24 cf2a884c c0282ddf 
>        c02de000 cf2a884c 00000000 cf2a8888 c01d0ef0 cf2a884c cf2a8800 cffd08b4 
> Call Trace:
>  [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
>  [<c01d1abf>] bus_match+0x2f/0x80
>  [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
>  [<d109edf8>] m3_pci_driver+0x58/0xa0 [maestro3]
>  [<c01d1b5f>] device_attach+0x4f/0x90
>  [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]

I don't think this is PCMCIA related - something else is going on here.

My guess is we're trying to locate a driver for the card, and we get to
maestro3.  This works as expected, but the next driver on the chain
seems to be a module which was may have been removed but which left
its pci_driver structure behind (at 0xd10545c0.)

Decoding the attached x86 opcodes didn't reveal anything interesting to
me.

Anyone else?

-- 
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-04-23 19:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23  5:47 DevilKin
2003-04-23 11:12 ` Felipe Alfaro Solana
2003-04-23 12:54   ` DevilKin
2003-04-23 14:23     ` Felipe Alfaro Solana
2003-04-23 18:50       ` DevilKin-LKML
2003-04-23 19:43         ` Russell King [this message]
2003-04-24  7:40           ` DevilKin-LKML
2003-04-24  7:57             ` Russell King
2003-04-24 10:06               ` DevilKin
2003-04-24 10:11                 ` Russell King
2003-04-24 10:16                   ` DevilKin
2003-04-24 10:13                 ` DevilKin
2003-05-05  8:51               ` [FIXED 2.5.69] " DevilKin
2003-05-06 23:48                 ` Matthew Harrell
2003-05-07  5:19                   ` DevilKin
2003-04-23 22:14         ` Felipe Alfaro Solana

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=20030423204341.A19573@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=devilkin-lkml@blindguardian.org \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation' \
    /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

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).