The last two aarch64, RPI3 kernels have been causing kernel panics for me.
The latest kernel 4.12.10-1 this morning again caused the issue but worse than last kernel.
I'm running the machine headless (no keyboard or HDMI) over ssh. I installed the kernel, rebooted, and
after it was up I logged in. I got the prompt for the password/key, hit return and don't get any further.
This happened with previous kernel as well. With that kernel I simply unplugged device and tried again, and got logged in.
This time multiple power downs didn't help. I tried a keyboard and mouse and was able to log in ok, and connect via ssh.
HOWEVER I suspect headless is not a factor, as I've been able to reproduce what happens with the HDMI and keyboard connected multiple times.
Basically, after the system boots, the last thing it does BEFORE the console login prompt is say the link is up (I'm using DHCP which is quite slow). If everything works you then get the login prompt, and you can also login via ssh. MOST boots however show a kernel panic instead of the login prompt. This scrolls by too fast to read, I tried videoing it but still can't read it.The logs are corrupted, so no help there.
The last part of the kernel dump (manually transcribed) is: (note n_tty_receive_buf..., may be m_tty_recvive_buf, can't tell from video)
$this->bbcode_second_pass_code('', '
[<ffff0000086f1520>] n_tty_receive_buf_common+0x60/0xa20
[<ffff0000086f1f18>] n_tty_receive_buf2+0x40/0x50
[<ffff0000086f4d14>] tty_ldisc_receive_buf+0x44/0x90
[<ffff0000086f58d4>] tty_port_default_receive_buf+0x54/0xa0
[<ffff0000086f4f94>] flush_to_ldisc+0xa4/0xc0
[<ffff0000080ee63c>] process_one_work+0x19c/0x3f0
[<ffff0000080ee8dc>] worker_thread+0x4c/0x420
[<ffff0000080f5100>] kthread+0x138/0x140
[<ffff0000080833b0>] ret_from_fork+0x10/0x20
Code: 912f62e0 f9004ba0 d2044c01 8b010260 (c0dffc03)
')
The log files also contain lots of lines thus:
$this->bbcode_second_pass_code('', '
Aug 31 09:04:00 alarm systemd[1]: Started User Manager for UID 1000.
Aug 31 09:04:06 alarm kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out
Aug 31 09:04:17 alarm kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out
Aug 31 09:04:39 alarm kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out
Aug 31 09:05:01 alarm kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out
Aug 31 09:05:03 alarm sshd[389]: Accepted publickey for alarm from 192.168.1.45
')
Also other strange things in logs:
$this->bbcode_second_pass_code('', '
journalctl -b0
...
Aug 16 13:19:33 alarm kernel: Hierarchical RCU implementation.
Aug 16 13:19:33 alarm kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
Aug 16 13:19:33 alarm kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Aug 16 13:19:33 alarm kernel: NR_IRQS:64 nr_irqs:64 0
Aug 16 13:19:33 alarm kernel: arch_timer: WARNING: Invalid trigger for IRQ2, assuming level low
Aug 16 13:19:33 alarm kernel: arch_timer: WARNING: Please fix your firmware
Aug 16 13:19:33 alarm kernel: arch_timer: cp15 timer(s) running at 19.20MHz (phy
s).
...
')
Is the firmware/devicetree in sync with the kernel version?
Andrew