From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] net: fec: fix crash at mx53 qsb board
Date: Thu, 21 Feb 2013 13:04:49 -0500 (EST) [thread overview]
Message-ID: <20130221.130449.868185028543115848.davem@davemloft.net> (raw)
In-Reply-To: <1361408848-14118-1-git-send-email-Frank.Li@freescale.com>
From: Frank Li <Frank.Li@freescale.com>
Date: Thu, 21 Feb 2013 09:07:28 +0800
> Unable to handle kernel NULL pointer dereference at virtual address 00000002
> pgd = 80004000
> [00000002] *pgd=00000000
> Internal error: Oops: 5 [#1] SMP ARM
> Modules linked in:
> CPU: 0 Not tainted (3.8.0-rc7-next-20130215+ #346)
> PC is at fec_enet_interrupt+0xd0/0x348
> LR is at fec_enet_interrupt+0xb8/0x348
> pc : [<80372b7c>] lr : [<80372b64>] psr: 60000193
> sp : df855c20 ip : df855c20 fp : df855c74
> r10: 00000516 r9 : 1c000000 r8 : 00000000
> r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : df9b7800
> r3 : df9b7df4 r2 : 00000000 r1 : 00000000 r0 : df9b7d34
>
> It is possible that issue a irq between request_irq and fec_enet_init.
> Irq handle will be called but driver data structure is not ready yet.
>
> Signed-off-by: Frank Li <Frank.Li@freescale.com>
You must fix this by making sure all of the necessary software
datastructures are initialized fully before request_irq() is
invoked.
You absolutely cannot control pending interrupts the chip is already
signalling and which have been queued up in the interrupt controller
already, which will be emitted precisely when you request_irq()
regardless of how you program the chip during this time.
I'm not applying this, fix the bug correctly, thanks.
prev parent reply other threads:[~2013-02-21 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 1:07 [PATCH 1/1] net: fec: fix crash at mx53 qsb board Frank Li
2013-02-21 2:19 ` Fabio Estevam
2013-02-21 18:04 ` David Miller [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=20130221.130449.868185028543115848.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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