Wandboard new kernel

This forum is for supported devices using an ARMv7 Freescale SoC.

Re: Wandboard new kernel

Postby d42b » Sat May 17, 2014 12:47 am

Thanks for identifying and fixing the problem with the SD names. pacman -Syu now results in a working system running 3.10.17-2.

I have to confirm however that `reboot`-ing is no longer possible. The board needs a hard powercycle to come up again.
d42b
 
Posts: 4
Joined: Wed May 07, 2014 10:52 pm

Re: Wandboard new kernel

Postby kmihelich » Sat May 17, 2014 7:00 pm

I can't reproduce any issues rebooting the system.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: Wandboard new kernel

Postby andrenam » Mon May 19, 2014 10:43 pm

I just tested a new rootfs downloaded at 2014-05-20 00:06 UTC+1 with the latest u-boot and a spare sdcard. Can't reboot the system.

btw: may be totally unrelated, but at the end of the poweroff, I get a kernel panic. Doesn't happen when rebooting, though:
$this->bbcode_second_pass_code('', '[root@alarm ~]# poweroff
[ OK ] Stopped target Sound Card.
Stopping User Manager for Stopping Getty on tty1...
Stopping Serial Getty on ttymxc0...
Stopping Login Service...
Stopping D-Bus System Message Bus...
Starting Generate shutdown-ramfs...
[ OK ] Stopped Login Service.
[ OK ] Stopped D-Bus System Message Bus.
[ OK ] Stopped Entropy Harvesting Daemon.
[ OK ] Stopped Automatic wired network connection using netctl profiles.
[ OK ] Stopped Getty on tty1.
[ OK ] Stopped Serial Getty on ttymxc0.
[ OK ] Stopped User Manager for UID 0.
[ OK ] Stopped OpenSSH Daemon.
Stopping SSH Key Generation...
[ OK ] Stopped SSH Key Generation.
[ OK ] Removed slice user-0.slice.
[ OK ] Removed slice system-serial\x2dgetty.slice.
[ OK ] Removed slice system-getty.slice.
Stopping Permit User Sessions...
[ OK ] Removed slice system-netctl\x2difplugd.slice.
[ OK ] Started Generate shutdown-ramfs.
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Slices.
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Paths.
[ OK ] Stopped target Timers.
[ OK ] Stopped target Sockets.
[ OK ] Closed Device-mapper event daemon FIFOs.
[ OK ] Closed LVM2 metadata daemon socket.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped target System Initialization.
Stopping Load/Save RF Kill Switch Status of rfkill1...
Stopping Load/Save RF Kill Switch Status of rfkill0...
Stopping Load/Save Random Seed...
Stopping Apply Kernel Variables...
[ OK ] Stopped Apply Kernel Variables.
Stopping Setup Virtual Console...
[ OK ] Stopped Setup Virtual Console.
[ OK ] Stopped target Encrypted Volumes.
Stopping Update UTMP about System Boot/Shutdown...
[ OK ] Stopped target Swap.
[ OK ] Stopped target Remote File Systems.
[ OK ] Stopped Load/Save RF Kill Switch Status of rfkill1.
[ OK ] Stopped Load/Save RF Kill Switch Status of rfkill0.
[ OK ] Stopped Load/Save Random Seed.
[ OK ] Stopped Update UTMP about System Boot/Shutdown.
Stopping Create Volatile Files and Directories...
[ OK ] Stopped Create Volatile Files and Directories.
[ OK ] Stopped target Local File Systems.
Unmounting /run/user/0...
Unmounting Temporary Directory...
[ OK ] Removed slice system-systemd\x2drfkill.slice.
[ OK ] Unmounted /run/user/0.
[ OK ] Unmounted Temporary Directory.
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped target Local File Systems (Pre).
Stopping Remount Root and Kernel File Systems...
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
systemd-shutdown[1]: Sending SIGTERM to remaining processes...
systemd-journald[164]: Received SIGTERM from PID 1 (systemd-shutdow).
systemd-shutdown[1]: Sending SIGKILL to remaining processes...
systemd-shutdown[1]: Unmounting file systems.
systemd-shutdown[1]: Unmounting /sys/kernel/debug.
systemd-shutdown[1]: Unmounting /sys/fs/fuse/connections.
systemd-shutdown[1]: Unmounting /dev/mqueue.
EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
systemd-shutdown[1]: All filesystems unmounted.
systemd-shutdown[1]: Deactivating swaps.
systemd-shutdown[1]: All swaps deactivated.
systemd-shutdown[1]: Detaching loop devices.
systemd-shutdown[1]: All loop devices detached.
systemd-shutdown[1]: Detaching DM devices.
systemd-shutdown[1]: All DM devices detached.
systemd-shutdown[1]: Storage is finalized.
systemd-shutdown[1]: Successfully changed into root pivot.
systemd-shutdown[1]: Returning to initrd...
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)

Unmounting /oldroot/sys/fs/cgroucgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
p/perf_event.
cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
Unmounting /oldroot/sys/fs/cgroupcgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
/blkio.
Unmounting /oldroot/sys/cgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
fs/cgroup/freezer.
Unmounting /ocgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
ldroot/sys/fs/cgroup/devices.
Uncgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
mounting /oldroot/sys/fs/cgroup/mcgroup: option changes via remount are deprecated (pid=1 comm=shutdown)
emory.
Unmounting /oldroot/sys/fs/cgroup/cpu,cpuacct.
Unmounting /oldroot/sys/fs/cgroup/cpuset.
Unmounting /oldroot/sys/fs/cgroup/systemd.
Unmounting /oldroot/sys/fs/cgroup.
Unmounting /oldroot/run.
Unmounting /oldroot/EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
dev/pts.
Unmounting /oldroot/dev/shm.
Unmounting /oldroot/sys/kernel/security.
Unmounting /oldroot/sys.
Unmounting /oldroot/proc.
Unmounting /oldroot/dev.
Unmounting /oldroot.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All loop devices detached.
Detaching DM devices.
All DM devices detached.
Storage is finalized.
Powering off.
Power down.
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000

CPU: 0 PID: 1 Comm: shutdown Not tainted 3.10.17-1-ARCH #1
[<80013c4c>] (unwind_backtrace+0x0/0xe0) from [<80010d58>] (show_stack+0x10/0x14)
[<80010d58>] (show_stack+0x10/0x14) from [<806ac7a4>] (panic+0x84/0x1cc)
[<806ac7a4>] (panic+0x84/0x1cc) from [<8002e5e8>] (do_exit+0x47c/0x8c0)
[<8002e5e8>] (do_exit+0x47c/0x8c0) from [<8003af94>] (SyS_reboot+0x12c/0x1bc)
[<8003af94>] (SyS_reboot+0x12c/0x1bc) from [<8000d900>] (ret_fast_syscall+0x0/0x30)')
andrenam
 
Posts: 14
Joined: Sat May 03, 2014 11:48 pm

Re: Wandboard new kernel

Postby h0tw1r3 » Fri May 23, 2014 1:21 am

Can someone confirm bluetooth working with this kernel?

I've been trying for an hour, but brcm_patchram_plus just loops writing the hcd.

I would downgrade to an older kernel to test myself, but I don't know how to get old package versions (I just installed so it came with 3.10.17-2).
h0tw1r3
 
Posts: 7
Joined: Fri May 23, 2014 1:09 am

Re: Wandboard new kernel

Postby pepedog » Fri May 23, 2014 7:14 am

@andrenam, nothing to worry about as all unmounted

@hotw1r3, how are you running patchram? systemctl, the start script, or manually?
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Wandboard new kernel

Postby Yenal » Fri May 23, 2014 10:38 am

@andrenam: I dont know if this is handled as a minor bug, but I can tell that I'm having the exact same error. With the new kernel the board cant be rebooted softly. I always need to turn the psu off and on. As far as I remember reboot strangely only worked when initiated via serial console
Yenal
 
Posts: 18
Joined: Wed Jan 29, 2014 6:31 pm

Re: Wandboard new kernel

Postby h0tw1r3 » Fri May 23, 2014 1:37 pm

$this->bbcode_second_pass_quote('pepedog', '@')hotw1r3, how are you running patchram? systemctl, the start script, or manually?


I've tried systemctl (brcm43xx service) and manually. I patched the brcm43xx service script (changed ttymxc3 to ttymxc2).

$this->bbcode_second_pass_code('', '
[root@wandboard scripts]# /usr/bin/brcm_patchram_plus -d --patchram /usr/lib/firmware/brcm/bcm4329.hcd --baudrate 3000000 --use_baudrate_for_download /dev/ttymxc2 --enable_hci
option patchram with arg /usr/lib/firmware/brcm/bcm4329.hcd
option baudrate with arg 3000000
option use_baudrate_for_download
option enable_hci
/dev/ttymxc2
writing
01 03 0c 00
writing
01 03 0c 00
writing
01 03 0c 00
^C
')
h0tw1r3
 
Posts: 7
Joined: Fri May 23, 2014 1:09 am

Re: Wandboard new kernel

Postby andrenam » Fri May 23, 2014 1:52 pm

@h0tw1r3: you can use adminempire's archlinuxarm rollback machine to download an older kernel package, if you want to test that. See viewtopic.php?f=8&t=6544
@pepedog: okay, good.
@Yenal: I had that issue too, when I tried to reboot via serial console, not only ssh.
andrenam
 
Posts: 14
Joined: Sat May 03, 2014 11:48 pm

Re: Wandboard new kernel

Postby pepedog » Fri May 23, 2014 2:09 pm

@hotw1r3
Can you build and try crawx/crux version
https://github.com/CrawX/PKGBUILDs/tree ... -bluetooth
I should point out firmware upload is a one-time-per-boot thing, 2nd attempts fail even if 1st attempt is good
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Wandboard new kernel

Postby h0tw1r3 » Fri May 23, 2014 4:49 pm

$this->bbcode_second_pass_quote('pepedog', 'C')an you build and try crawx/crux version


Same result.

Downgraded kernel to 3.0.35-7 and patchram worked and the hci came up as expected.
This thread indicates cubox-i4 users are having a similar problem after upgrading to 3.10.
h0tw1r3
 
Posts: 7
Joined: Fri May 23, 2014 1:09 am

PreviousNext

Return to Freescale

Who is online

Users browsing this forum: No registered users and 18 guests