On Mon, Nov 16, 2015 at 6:58 AM, Taceant Omnes <[email protected]> wrote:
> On 13 November 2015 at 17:49, Robert Nelson <[email protected]> wrote:
>
>> Yeah good point. ;)
>>
>> root@beaglebone:~# uname -r ; ls -l 
>> /sys/devices/system/cpu/cpu0/cpuidle/state0/
>> 4.1.13-ti-r29.4
>> total 0
>> -r--r--r-- 1 root root 4096 Nov 13 17:46 desc
>> -rw-r--r-- 1 root root 4096 Nov 13 17:46 disable
>> -r--r--r-- 1 root root 4096 Nov 13 17:46 latency
>> -r--r--r-- 1 root root 4096 Nov 13 17:46 name
>> -r--r--r-- 1 root root 4096 Nov 13 17:46 power
>> -r--r--r-- 1 root root 4096 Nov 13 17:46 residency
>> -r--r--r-- 1 root root 4096 Nov 13 17:46 time
>> -r--r--r-- 1 root root 4096 Nov 13 17:46 usage
>>
>> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/7df6a18cbcd567712edd1e1a4a774742d510dbe3
>
> [same message again, now to the mailing list]
>
> I did
> apt-get install linux-image-4.1.13-ti-r30
>
> It installed fine. Apt suggested that I install a firmware package
> (with 4.1.13-ti-r30 in the name). I did that - maybe I should not, it
> was the first time I installed a firmware package on the BBB.
>
> Anyway, now the BBB does not boot. I have been doing all my work using
> a MicroSD card. The log is below. Basically the boot process does not
> complete, and I see the asterisks at the last line moving right and
> left and the time in seconds being incremented continuously on the
> line "A start job is running for LSB:".
>
> My previous kernel, that worked very well, was 4.1.10-bone16.
>
> Any ideas?

What rootfs and distro?

cat /etc/dogtag

>
> -------------------------------------------------------------
>
> U-Boot SPL 2014.04-00015-gb4422bd (Apr 22 2014 - 13:24:29)
> reading args
> spl_load_image_fat_os: error reading image args, err - -1
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2014.04-00015-gb4422bd (Apr 22 2014 - 13:24:29)
>
> I2C:   ready
> DRAM:  512 MiB
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> *** Warning - readenv() failed, using default environment
>
> Net:   <ethaddr> not set. Validating first E-fuse MAC
> cpsw, usb_ether
> Hit any key to stop autoboot:  0
> gpio: pin 53 (gpio 53) value is 1
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> SD/MMC found on device 0
> 1179 bytes read in 8 ms (143.6 KiB/s)
> gpio: pin 55 (gpio 55) value is 1
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Checking if uenvcmd is set ...
> gpio: pin 56 (gpio 56) value is 1
> Running uenvcmd ...
> 1661 bytes read in 36 ms (44.9 KiB/s)
> debug: [/boot/vmlinuz-4.1.13-ti-r30] ...
> 8260280 bytes read in 503 ms (15.7 MiB/s)
> debug: [/boot/initrd.img-4.1.13-ti-r30] ...
> 4506906 bytes read in 304 ms (14.1 MiB/s)
> debug: [/boot/dtbs/4.1.13-ti-r30/am335x-boneblack.dtb] ...
> 59295 bytes read in 71 ms (815.4 KiB/s)
> debug: [console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1
> rootfstype=ext4 rootwait coherent_pool=1M quiet] ...
> debug: [bootz 0x82000000 0x88080000:44c51a 0x88000000] ...
> Kernel image @ 0x82000000 [ 0x000000 - 0x7e0ab8 ]
> ## Flattened Device Tree blob at 88000000
>    Booting using the fdt blob at 0x88000000
>    Using Device Tree in place at 88000000, end 8801179e
>
> Starting kernel ...
>
> [    3.371127] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
> [    3.744796] omap-sham 53100000.sham: initialization failed.
> [    3.767060] cpu cpu0: cpu0 clock notifier not ready, retry
> [    3.908242] bone_capemgr bone_capemgr: slot #0: No cape found
> [    3.968235] bone_capemgr bone_capemgr: slot #1: No cape found
> [    4.028233] bone_capemgr bone_capemgr: slot #2: No cape found
> [    4.088234] bone_capemgr bone_capemgr: slot #3: No cape found
> Loading, please wait...
> fsck from util-linux 2.25.2
> rootfs: recovering journal
> rootfs: clean, 37364/466560 files, 331056/1955328 blocks
> [FAILED] Failed to start Load Kernel Modules.
> See 'systemctl status systemd-modules-load.service' for details.
> [   13.815623] systemd[1]: Failed to start Load Kernel Modules.
> [  OK  ] Mounted POSIX Message Queue File System.
> [  OK  ] Started LSB: controls configuration of serial ports.
> [  OK  ] Started Remount Root and Kernel File Systems.
> [  OK  ] Started udev Coldplug all Devices.
>          Starting Load/Save Random Seed...
>          Mounting FUSE Control File System...
>          Mounting Configuration File System...
>          Starting Apply Kernel Variables...
>          Starting Create Static Device Nodes in /dev...
> [  OK  ] Listening on Syslog Socket.
>          Starting Journal Service...
> [  OK  ] Started Journal Service.
> [  OK  ] Mounted Configuration File System.
> [  OK  ] Mounted FUSE Control File System.
> [  OK  ] Started Load/Save Random Seed.
> [  OK  ] Started Apply Kernel Variables.
> [  OK  ] Started Create Static Device Nodes in /dev.
>          Starting udev Kernel Device Manager...
> [  OK  ] Reached target Local File Systems (Pre).
>          Mounting /sys/kernel/debug...
> [  OK  ] Started udev Kernel Device Manager.
> [  OK  ] Mounted /sys/kernel/debug.
> [  OK  ] Reached target Local File Systems.
>          Starting Create Volatile Files and Directories...
> [  OK  ] Reached target Remote File Systems.
>          Starting Trigger Flushing of Journal to Persistent Storage...
>          Starting LSB: controls configuration of serial ports...
>          Starting LSB: Raise network interfaces....
>          Starting Copy rules generated while the root was ro...
> [  OK  ] Started Create Volatile Files and Directories.
> [  OK  ] Started Copy rules generated while the root was ro.
> [   15.036404] Unable to handle kernel paging request at virtual
> address fee00005
> [   15.043713] pgd = ddba0000
> [   15.046439] [fee00005] *pgd=00000000
> [   15.050053] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
> [   15.055400] Modules linked in:
> [   15.058489] CPU: 0 PID: 219 Comm: setserial Not tainted 4.1.13-ti-r30 #1
> [   15.065231] Hardware name: Generic AM33XX (Flattened Device Tree)
> [   15.071362] task: ddba7480 ti: ddb9c000 task.ti: ddb9c000
> [   15.076810] PC is at io_serial_in+0x28/0x38
> [   15.081029] LR is at serial8250_do_startup+0xd0/0x668

odd, you lose serial here, might be a gcc bug depending on your distro

Jessie:

https://paste.debian.net/333026/

So let us know the base rootfs and distro and i'll try to replicate it

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to