From: Keerthy <j-keerthy@ti.com>
To: <linux-omap@vger.kernel.org>, <rmk+kernel@armlinux.org.uk>,
<tony@atomide.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
<netdev@vger.kernel.org>, Sekhar Nori <nsekhar@ti.com>,
<nm@ti.com>
Subject: Re: AM43x boot broken on linux-next
Date: Wed, 10 Jan 2018 15:47:14 +0530 [thread overview]
Message-ID: <07c3e621-7f4a-0574-a8e9-76ffe519456e@ti.com> (raw)
In-Reply-To: <b79af9ad-e238-50ec-ef85-62957b267de8@ti.com>
On Tuesday 09 January 2018 03:22 PM, Keerthy wrote:
> On Tuesday 09 January 2018 02:03 PM, Keerthy wrote:
>> Hi,
>
> Adding netdev@vger.kernel.org
>
>>
>> Seems like AM437x boot is broken on latest linux-next.
>> Log here:
>>
>> https://pastebin.ubuntu.com/26351906/
Git bisect pointed me to this patch:
commit fea23fb591cce99546baca043d2a068228e87a79
Author: Russell King <rmk+kernel@armlinux.org.uk>
Date: Tue Jan 2 10:58:58 2018 +0000
net: phy: convert read-modify-write to phy_modify()
I saw that there was a double negation issue there and i moved to
Russell's fix patch:
commit f102852f980eac250855504c18f195900616deec
Author: Russell King <rmk+kernel@armlinux.org.uk>
Date: Fri Jan 5 16:07:10 2018 +0000
net: phy: fix wrong masks to phy_modify()
Even with this fix commit i am seeing issues.
I reverted the fix and the original patch on linux-next and that solves
the issue.
So there is more to fix in the original patch IMHO.
>>
>> "Unable to handle kernel paging request at virtual address 000013e8
>> [ 2.367045] pgd = c0350bf7
>> [ 2.370019] [000013e8] *pgd=00000000
>> [ 2.373823] Internal error: Oops: 5 [#1] SMP ARM
>> [ 2.378709] Modules linked in:
>> [ 2.381949] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
>> 4.15.0-rc6-next-20180108-38410-g895c0dd #4
>> [ 2.391242] Hardware name: Generic AM43 (Flattened Device Tree)
>> [ 2.397523] PC is at phy_attached_print+0xc/0x10c
>> [ 2.402506] LR is at cpsw_slave_open+0x16c/0x258"
>>
>> Regards,
>> Keerthy
>>
next prev parent reply other threads:[~2018-01-10 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bf1fc3d2-b882-7850-4afd-c1e753e2a1a7@ti.com>
2018-01-09 9:52 ` AM43x boot broken on linux-next Keerthy
2018-01-10 10:17 ` Keerthy [this message]
2018-01-10 10:38 ` Keerthy
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=07c3e621-7f4a-0574-a8e9-76ffe519456e@ti.com \
--to=j-keerthy@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox