Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kernel 4.14 problems #2376

Closed
mypiandrew opened this issue Feb 12, 2018 · 10 comments
Closed

Kernel 4.14 problems #2376

mypiandrew opened this issue Feb 12, 2018 · 10 comments

Comments

@mypiandrew
Copy link

mypiandrew commented Feb 12, 2018

Hi

We're running a CM3 on a custom carrier board we've had for a few years now.

Has been running quite happily up to 4.9.75, no problems. All Solid.

I've just done a rpi-update running on Jessie to test out the new 4.14 kernel and the system hangs on next boot up :

https://gist.github.com/anonymous/55a8bacdb888a87380ac83b3f61db1c1

These look more interesting from a "going bang" perspective :

https://gist.github.com/anonymous/16b43d4e873c930b2b223f046169804a
https://gist.github.com/anonymous/b36a2fb2af2adf2cdea3e3ffc0584462

Adding these to the cmdline.txt file doesn't help

dwc_otg.lpm_enable=0 dwc_otg.speed=1

I did have other issues with the system way back on 4.4 with #1633 but I doesn't look the same to me as it's not even getting as far as systemd by the looks of it here

What can I do to assist with debugging this?

Andrew

@6by9
Copy link
Contributor

6by9 commented Feb 12, 2018

(Duplicate of https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=197689&start=25#p1272277)

Full contents of config.txt please, and details of all peripherals connected to the device.
Booting off EMMC?
What's in /etc/fstab too? You appear to have an SD card exporting /dev/sda, so is that being mounted correctly?

@6by9
Copy link
Contributor

6by9 commented Feb 12, 2018

/etc/modules too for any extra modules you're loading.

@mypiandrew
Copy link
Author

mypiandrew commented Feb 12, 2018

Yes it's a CM3

I was just taking a cut and paste of the config.txt line and noticed and old overlay

I had this line still in ( I can't remember why off hand, wasn't there an issue with this at one point?)
dtoverlay=mmc

Removed it, and it's booting nicely now

Would that have caused other issues?

https://gist.github.com/mypiandrew/ae93c668844d086491efcaf4b81b7b4d

@6by9
Copy link
Contributor

6by9 commented Feb 12, 2018

Would that have caused other issues?

Without details of your custom system, it could be anything.

@mypiandrew
Copy link
Author

Hmm.. on removing the forced usb slowdown mods to cmdline.txt I am still getting a USB error that sounds awfully like what I saw before

Let me gather some info for you

@mypiandrew
Copy link
Author

root@raspberrypi:~# lsusb
Bus 001 Device 007: ID 1e0e:9001 Qualcomm / Option
Bus 001 Device 006: ID 0424:2240 Standard Microsystems Corp.
Bus 001 Device 004: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 005: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 003: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

@mypiandrew
Copy link
Author

mypiandrew commented Feb 12, 2018

root@raspberrypi:~# grep -v # /boot/config.txt
dtdebug=on
dtoverlay=uart0,txd0_pin=32,rxd0_pin=33
dtoverlay=uart1,txd1_pin=14,rxd1_pin=15
dtoverlay=uart_swap
enable_uart=1
dtparam=i2c1=on
dtparam=i2c1=on,i2c1_baudrate=180000
dtoverlay=i2c-rtc,ds1307
core_freq=250

cat /boot/cmdline.txt
console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait maxcpus=4

@mypiandrew
Copy link
Author

mypiandrew commented Feb 12, 2018

root@raspberrypi:~# lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M
|__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
|__ Port 3: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 4: Dev 7, If 1, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 7, If 6, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 7, If 4, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 7, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 7, If 0, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 7, If 5, Class=Vendor Specific Class, Driver=qmi_wwan, 480M
|__ Port 4: Dev 7, If 3, Class=Vendor Specific Class, Driver=option, 480M

Wired :

GL850G
-> LAN9512
-> FT230X
-> USB2240
-> MPCIE (SIM7100)

@mypiandrew
Copy link
Author

This shows the system with a boot that has the mysterious error 71 on it

https://gist.github.com/mypiandrew/5c4ab7e6f915319179ae3af6e860e950

@mypiandrew
Copy link
Author

OK scratch the -71 error, I think there must have been a intermittent contact on the mPCIe card I was using to test. Given the edge contacts a clean and screwed the card in fully and it's booting AOK for the last 10 tries in a row.

Nice work, and thanks for the hand holding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants