Bug 4244 - [Bealgeboard xM] Kernel networking broken/missing
Summary: [Bealgeboard xM] Kernel networking broken/missing
Status: VERIFIED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: 1.4
Hardware: Beagleboard arm
: Medium+ major
Target Milestone: 1.4 M6
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-04-11 08:06 UTC by Ning Zhang
Modified: 2013-04-24 09:17 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ning Zhang 2013-04-11 08:06:18 UTC
poky:         dylan         adb63ca02348af72a30cef2f20de2234b74a7200
image download from http://autobuilder.yoctoproject.org/pub/nightly/20130410-1
core image use: core-image-sato-sdk-beagleboard-20130410221122.rootfs.tar.bz2

The X server could not start. This is a regression issue than 20130403 edition.

Set boot env as below to print some debug info:
setenv bootcmd 'mmc rescan 0; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000' 
setenv bootargs 'console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro' 
boot

The serial output:

Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
musb-hdrc musb-hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
 gadget: Mass Storage Function, version: 2009/09/11
 gadget: Number of LUNs=1
 lun0: LUN: removable file: (no medium)
 gadget: Mass Storage Gadget, version: 2009/09/11
 gadget: userspace failed to provide iSerialNumber
 gadget: g_mass_storage ready
musb-hdrc musb-hdrc: MUSB HDRC host driver
musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
twl_rtc twl_rtc: Power up reset detected.
twl_rtc twl_rtc: Enabling TWL-RTC
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
cpuidle: using governor ladder
cpuidle: using governor menu
usb 1-2: new high-speed USB device number 2 using ehci-omap
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
OMAP3 Beagle/Devkit8000 SoC init
soc-audio soc-audio: ASoC machine omap3beagle should use snd_soc_register_card()
twl4030-codec twl4030-codec: ASoC: Failed to create Capture debugfs file
asoc: twl4030-hifi <-> omap-mcbsp.2 mapping ok
oprofile: hardware counters not available
oprofile: using timer interrupt.
pktgen: Packet Generator for packet performance testing. Version: 2.74
NET: Registered protocol family 15
8021q: 802.1Q VLAN Support v1.8
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
sr_init: No PMIC hook to init smartreflex
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
SmartReflex Class3 initialized
clock: disabling unused clocks to save power
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 5 ports detected
Console: switching to colour frame buffer device 210x65
omapdss DPI: Could not find exact pixel clock. Requested 146262 kHz, got 144000 kHz
VDAC: incomplete constraints, leaving on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
ALSA device list:
  #0: omap3beagle
Waiting for root device /dev/mmcblk0p2...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.63 GiB 
 mmcblk0: p1 p2
EXT3-fs (mmcblk0p2): recovery required on readonly filesystem
EXT3-fs (mmcblk0p2): write access will be enabled during recovery
usb 1-2.1: new high-speed USB device number 3 using ehci-omap
smsc95xx v1.0.4
smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, f2:1a:16:78:5d:07
usb 1-2.2: new high-speed USB device number 4 using ehci-omap
hub 1-2.2:1.0: USB hub found
hub 1-2.2:1.0: 7 ports detected
usb 1-2.2.5: new low-speed USB device number 5 using ehci-omap
input: Dell Dell USB Keyboard as /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.2/1-2.2.5/1-2.2.5:1.0/input/input0
generic-usb 0003:413C:2003.0001: input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-ehci-omap.0-2.2.5/input0
usb 1-2.2.6: new low-speed USB device number 6 using ehci-omap
input: USB Optical Mouse as /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.2/1-2.2.6/1-2.2.6:1.0/input/input1
generic-usb 0003:0461:4D15.0002: input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-ehci-omap.0-2.2.6/input0
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 179:2.
devtmpfs: mounted
Freeing init memory: 244K
INIT: version 2.88 booting
mount: wrong fs type, bad option, bad superblock on tmpfs,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
Starting udev
udevd[96]: error getting socket: Address family not supported by protocol

error initializing udev control socketudevd[96]: error initializing udev control socket
error getting socket: Address family not supported by protocol
udevadm[97]: error getting socket: Address family not supported by protocol

error getting socket: Address family not supported by protocol
udevadm[99]: error getting socket: Address family not supported by protocol

Starting Bootlog daemon: bootlogd.
EXT3-fs (mmcblk0p2): using internal journal
ALSA: Restoring mixer settings...
Configuring network interfaces... Found hardware: "omap3beagle" "" "" "" ""
Hardware is initialized using a generic method
ifconfig: socket: Address family not supported by protocol
ifconfig: socket: Address family not supported by protocol
Starting rpcbind daemon...rpcbind: cannot create socket for local
rpcbind: cannot create socket for udp
rpcbind: cannot create socket for tcp
rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
done.
Wed Apr 10 23:32:00 UTC 2013
INIT: Entering runlevel: 5
Starting system message bus: Failed to start message bus: Failed to open socket: Address family not supported by protocol
Starting Connection Manager
Starting OpenBSD Secure Shell server: sshd
done.
Starting Xserver
Starting advanced power management daemon: apmd.
apmd[223]: apmd 3.2.1 interfacing with apm driver 1.13 and APM BIOS 1.2
Comment 1 Ross Burton 2013-04-11 08:28:10 UTC
udevd[96]: error getting socket: Address family not supported by protocol
udevadm[97]: error getting socket: Address family not supported by protocol
udevadm[99]: error getting socket: Address family not supported by protocol
ifconfig: socket: Address family not supported by protocol
ifconfig: socket: Address family not supported by protocol
rpcbind: cannot create socket for local
rpcbind: cannot create socket for udp
rpcbind: cannot create socket for tcp
rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
Failed to start message bus: Failed to open socket: Address family not supported by protocol

Networking is well and truly missing in this build.
Comment 2 Richard Purdie 2013-04-11 08:32:45 UTC
Its possible the kernel config was corrupted by http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=4c02dd5f6432c6e683a57d47b610f56433e9ca0d
Comment 3 Ross Burton 2013-04-11 08:35:16 UTC
Bruce, there was ARM kernel breakage that you just fixed: would that be the cause of this and therefore it's resolved in git?
Comment 4 Bruce Ashfield 2013-04-11 12:28:20 UTC
It is worth a re-test. The combination of that kern-tools fix + the KERNEL_EXTRA_FEATURES
only being applied to qemux86* would mean that netfilter and other useful options were being
dropped. 

I've upreved the beagleboard to 3.8 here, and networking works, so this is worth a retest on 3.4 now.
Comment 5 Ross Burton 2013-04-11 12:33:57 UTC
Ok, marking as needinfo.  Ning Zhang, please re-test.
Comment 6 Ning Zhang 2013-04-12 06:06:28 UTC
(In reply to comment #5)
> Ok, marking as needinfo.  Ning Zhang, please re-test.

Hi, i retested it on 20130411-3 images. It has the same issue. Still "Failed to open socket" 

Poky: poky dylan dab237bc6a7679dfeaa981c14736aedc7b04ecb9
Download image from: http://autobuilder.yoctoproject.org/pub/nightly/20130411-3/machines/beagleboard/
I used below bootfiles:
core-image-sato-sdk-beagleboard-20130411161536.rootfs.tar.bz2
MLO-beagleboard-1.5.0+gitAUTOINC+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0
u-boot-beagleboard-v2011.06+gitAUTOINC+b1af6f532e0d348b153d5c148369229d24af361a-r3.bin
uImage--3.4.36+gitAUTOINC+80b4b5110dca5184b57e85f1e775fb006a2e85ad_c994390cfa28339cbc1ec3b56eeec83a5fa75bb7-r4.3-beagleboard-20130411161536.bin



Test Log:

Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
musb-hdrc musb-hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
 gadget: Mass Storage Function, version: 2009/09/11
 gadget: Number of LUNs=1
 lun0: LUN: removable file: (no medium)
 gadget: Mass Storage Gadget, version: 2009/09/11
 gadget: userspace failed to provide iSerialNumber
 gadget: g_mass_storage ready
musb-hdrc musb-hdrc: MUSB HDRC host driver
musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
twl_rtc twl_rtc: Power up reset detected.
twl_rtc twl_rtc: Enabling TWL-RTC
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
cpuidle: using governor ladder
cpuidle: using governor menu
usb 1-2: new high-speed USB device number 2 using ehci-omap
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
OMAP3 Beagle/Devkit8000 SoC init
soc-audio soc-audio: ASoC machine omap3beagle should use snd_soc_register_card()
twl4030-codec twl4030-codec: ASoC: Failed to create Capture debugfs file
asoc: twl4030-hifi <-> omap-mcbsp.2 mapping ok
oprofile: hardware counters not available
oprofile: using timer interrupt.
pktgen: Packet Generator for packet performance testing. Version: 2.74
NET: Registered protocol family 15
8021q: 802.1Q VLAN Support v1.8
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
hub 1-2:1.0: USB hub found
sr_init: No PMIC hook to init smartreflex
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
SmartReflex Class3 initialized
clock: disabling unused clocks to save power
hub 1-2:1.0: 5 ports detected
Console: switching to colour frame buffer device 210x65
omapdss DPI: Could not find exact pixel clock. Requested 146262 kHz, got 144000 kHz
VDAC: incomplete constraints, leaving on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
ALSA device list:
  #0: omap3beagle
Waiting for root device /dev/mmcblk0p2...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.63 GiB 
 mmcblk0: p1 p2
EXT3-fs (mmcblk0p2): recovery required on readonly filesystem
EXT3-fs (mmcblk0p2): write access will be enabled during recovery
usb 1-2.1: new high-speed USB device number 3 using ehci-omap
smsc95xx v1.0.4
smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, 7e:87:52:66:65:ea
usb 1-2.2: new high-speed USB device number 4 using ehci-omap
hub 1-2.2:1.0: USB hub found
hub 1-2.2:1.0: 7 ports detected
usb 1-2.2.5: new low-speed USB device number 5 using ehci-omap
input: Dell Dell USB Keyboard as /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.2/1-2.2.5/1-2.2.5:1.0/input/input0
generic-usb 0003:413C:2003.0001: input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-ehci-omap.0-2.2.5/input0
usb 1-2.2.6: new low-speed USB device number 6 using ehci-omap
input: USB Optical Mouse as /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.2/1-2.2.6/1-2.2.6:1.0/input/input1
generic-usb 0003:0461:4D15.0002: input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-ehci-omap.0-2.2.6/input0
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) readonly on device 179:2.
devtmpfs: mounted
Freeing init memory: 244K
INIT: version 2.88 booting
mount: wrong fs type, bad option, bad superblock on tmpfs,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
Starting udev
udevd[96]: error getting socket: Address family not supported by protocol

error initializing udev control socketudevd[96]: error initializing udev control socket
error getting socket: Address family not supported by protocol
udevadm[97]: error getting socket: Address family not supported by protocol

error getting socket: Address family not supported by protocol
udevadm[99]: error getting socket: Address family not supported by protocol

Starting Bootlog daemon: bootlogd.
EXT3-fs (mmcblk0p2): using internal journal
ALSA: Restoring mixer settings...
Configuring network interfaces... Found hardware: "omap3beagle" "" "" "" ""
Hardware is initialized using a generic method
ifconfig: socket: Address family not supported by protocol
ifconfig: socket: Address family not supported by protocol
Starting rpcbind daemon...rpcbind: cannot create socket for local
rpcbind: cannot create socket for udp
rpcbind: cannot create socket for tcp
rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
done.
Thu Apr 11 17:17:00 UTC 2013
INIT: Entering runlevel: 5
Starting system message bus: Failed to start message bus: Failed to open socket: Address family not supported by protocol
Starting Connection Manager
Starting OpenBSD Secure Shell server: sshd
done.
Starting Xserver
Starting advanced power management daemon: apmd.

apmd[223]: apmd 3.2.1 interfacing with apm driver 1.13 and APM BIOS 1.2
Starting Distributed Compiler Daemon: distcc/etc/rc5.d/S20distcc: start failed with error code 102
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/beagleboard:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet
_XSERVTransOpen: transport open failed for inet/beagleboard:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet
_XSERVTransSocketOpenCOTSServer: Unable to open socket for local
_XSERVTransOpen: transport open failed for local/beagleboard:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for local
_XSERVTransSocketOpenCOTSServer: Unable to open socket for unix
_XSERVTransOpen: transport open failed for unix/beagleboard:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for unix

Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
(EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
Server terminated with error (1). Closing log file.
Starting syslogd/klogd: done
 * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
xinit: giving up
xinit: unable to connect to X server: Address family not supported by protocol
xinit: server error
Timeout reached while wating for return value
 *[fail]t receive return value from daemon process.
Starting Telephony daemon
Starting Linux NFC daemon
Starting OProfileUI server
Starting tcf-agent: 
** (oprofile-server:260): ERROR **: Could not open server socket: Address family not supported by protocol
OK
Stopping Bootlog daemon: bootlogd.

Poky 9.0 (Yocto Project 1.4 Reference Distro) 1.4 beagleboard ttyO2

beagleboard login: root
root@beagleboard:~# ifconfig
ifconfig: error: no inet socket available: Address family not supported by protocol
root@beagleboard:~# more /var/log/Xorg.0.log
[4195988.202] _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
[4195988.203] _XSERVTransOpen: transport open failed for inet6/beagleboard:0
[4195988.203] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for
 inet6
[4195988.204] _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet
[4195988.204] _XSERVTransOpen: transport open failed for inet/beagleboard:0
[4195988.205] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for
 inet
[4195988.205] _XSERVTransSocketOpenCOTSServer: Unable to open socket for local
[4195988.205] _XSERVTransOpen: transport open failed for local/beagleboard:0
[4195988.206] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for
 local
[4195988.206] _XSERVTransSocketOpenCOTSServer: Unable to open socket for unix
[4195988.206] _XSERVTransOpen: transport open failed for unix/beagleboard:0
[4195988.207] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for
 unix
[4195988.207] 
Fatal server error:
[4195988.208] Cannot establish any listening sockets - Make sure an X server isn
't already running
[4195988.208] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[4195988.209] (EE) Please also check the log file at "/var/log/Xorg.0.log" for a
dditional information.
[4195988.209] (EE) 
[4195988.215] Server terminated with error (1). Closing log file.
root@beagleboard:~# 
root@beagleboard:~# date
Thu Apr 11 17:25:17 UTC 2013
root@beagleboard:~# uname -a
Linux beagleboard 3.4.36-yocto-standard #1 Thu Apr 11 16:25:58 GMT 2013 armv7l GNU/Linux
root@beagleboard:~#
Comment 7 Bruce Ashfield 2013-04-12 12:50:51 UTC
The kernel configuration should be fine then. Has anything else changed in the X area ?
I have a beagleboard here, but no display, so I can't test this myself.
Comment 8 Ross Burton 2013-04-12 12:57:07 UTC
X failing is just the final error, everything else that touches sockets fails earlier - notice udevd failing too.
Comment 9 Richard Purdie 2013-04-12 13:01:46 UTC
Bruce, looking at the startup errors, you'd see problems even just with console startup. It looks like networking support (unix domain sockets?) are missing from the kernel...
Comment 10 Bruce Ashfield 2013-04-12 13:05:42 UTC
My beagle isn't displaying anything but junk to the console. so I need to debug infrastructure before I can see 
any boot messages at all :(
Comment 11 Bruce Ashfield 2013-04-12 13:08:56 UTC
My serial console is fixed. I'll do a new build of a kernel and see what my bootload looks like.
Comment 12 Bruce Ashfield 2013-04-12 13:50:59 UTC
I've found the missing options. A fix is forthcoming, I'll take care of this after confirming the fsl-mpc NFS root issues.
Comment 13 Bruce Ashfield 2013-04-12 15:57:04 UTC
Patch is in Richard's hands for this issue.
Comment 15 Yi Zhao 2013-04-24 09:17:16 UTC
Verified with dylan branch: 789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4