Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Suspend/resume broken on mx5/mx6 running 4.16
Date: Mon, 4 Aug 2014 19:11:06 +0100	[thread overview]
Message-ID: <20140804181106.GI30282@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOMZO5BN9H-4__2s9yyGiuOBsLO0gf9LOQ0_N1552P8LWJTxCg@mail.gmail.com>

On Mon, Aug 04, 2014 at 02:53:42PM -0300, Fabio Estevam wrote:
> Unable to handle kernel NULL pointer dereference at virtual address 0000002c
> pgd = bcd14000
> [0000002c] *pgd=4d9e0831, *pte=00000000, *ppte=00000000
> Internal error: Oops: 17 [#1] SMP ARM
> Modules linked in:
> CPU: 0 PID: 617 Comm: sh Not tainted 3.16.0 #17
> task: bc0c4e00 ti: bceb6000 task.ti: bceb6000
> PC is at fec_suspend+0x10/0x70
> LR is at dpm_run_callback.isra.7+0x34/0x6c
> pc : [<803f8a98>]    lr : [<80361f44>]    psr: 600f0013
> sp : bceb7d70  ip : bceb7d88  fp : bceb7d84
> r10: 8091523c  r9 : 00000000  r8 : bd88f478
> r7 : 803f8a88  r6 : 81165988  r5 : 00000000  r4 : 00000000
> r3 : 00000000  r2 : 00000000  r1 : bd88f478  r0 : bd88f478

Right, so the code which oopsed was:

   0:   e1a0c00d        mov     ip, sp
   4:   e92dd818        push    {r3, r4, fp, ip, lr, pc}
   8:   e24cb004        sub     fp, ip, #4
   c:   e5904088        ldr     r4, [r0, #136]  ; 0x88
  10:   e594302c        ldr     r3, [r4, #44]   ; 0x2c

and from the above, we can see that r4 was NULL.

fec_suspend(struct device *dev)
{
        struct net_device *ndev = dev_get_drvdata(dev);

which would make ndev NULL.  I don't see how that could happen though,
as we set the driver data in the probe function.  Any patches on top of
3.16?

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2014-08-04 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 17:53 Suspend/resume broken on mx5/mx6 running 4.16 Fabio Estevam
2014-08-04 18:11 ` Russell King - ARM Linux [this message]
2014-08-04 18:21   ` Fabio Estevam
2014-08-05  2:33     ` Fabio Estevam
2014-08-05  6:06 ` fugang.duan at freescale.com
2014-08-05  6:16   ` Shawn Guo
2014-08-05  6:52     ` fugang.duan at freescale.com
2014-08-05  9:21     ` Russell King - ARM Linux
2014-08-05 18:52       ` Greg KH

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=20140804181106.GI30282@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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