[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJKOXPdHhUGoQmrX8_23MfbibozipkAzXA_5woVSFJSK9BvbXw@mail.gmail.com>
Date: Fri, 18 Jan 2019 09:39:28 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Heiner Kallweit <hkallweit1@...il.com>,
Andrew Lunn <andrew@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Stefan Agner <stefan@...er.ch>
Subject: [BUG bisect] Missing Micrel driver on VF50 (net: phy: check return
code when requesting PHY driver module)
Hi,
On today's next (next-20190118) my Colibri VF50 board fails to boot up
from network (DHCP, NFSv4 root). Looks like missing network adapter.
Expected:
[ 3.041773] Micrel KSZ8041 400d1000.ethernet-1:00: attached PHY driver
[Micrel KSZ8041] (mii_bus:phy_addr=400d1000.ethernet-1:00, irq=POLL)
Result:
[ 15.614964] Root-NFS: no NFS server address
[ 15.619353] VFS: Unable to mount root fs via NFS, trying floppy.
[ 15.626762] VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6
[ 15.634252] Please append a correct "root=" boot option; here are the
available partitions:
[ 15.642791] 0100 16384 ram0
[ 15.642804] (driver?)
[ 15.649076] Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(2,0)
[ 15.657423] ---[ end Kernel panic - not syncing: VFS: Unable to mount
root fs on unknown-block(2,0) ]---
Bisect pointed to:
net: phy: check return code when requesting PHY driver module
Full log and defconfig attached.
Board:
- Toradex Colibri VF50 on Iris board
ARMv7, UP, Cortext-A5, NXP VF500, 128 MB RAM, 128 MB NAND
Systemd: v232
DHCP, NFSv4 root
Best regards,
Krzysztof
View attachment "serial_console.txt" of type "text/plain" (28540 bytes)
Download attachment "bisect_vf_defconfig" of type "application/octet-stream" (6264 bytes)
Powered by blists - more mailing lists