Sorry wrong bug report.
** Also affects: linux-raspi2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-raspi2 (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
This bug was fixed in the package linux-raspi2 - 4.4.0-1044.51
---
linux-raspi2 (4.4.0-1044.51) xenial; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1667422
* Boot into emergency mode on RPi2 with proposed kernel 4.4.0-1043.50 after
syste
Switch to 4.4.0-1042-raspi2 and reboot 10 times. I could always boot
into the system successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665280
Title:
Boot into emergency mode on RPi2 with
log dumped by
"udevadm trigger --type=subsystems --action=add --verbose"
with 4.4.0-1042-raspi2
http://paste.ubuntu.com/24013536/
** Attachment added: "4.4.0-1042-raspi2_udevadm.log"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1665280/+attachment/4820791/+files/4.4.0-1042-rasp
I keep rebooting the system. The reproducing rate is now 6 out of 7.
** Description changed:
Hardware: RPi2
Image:
http://cdimage.ubuntu.com/ubuntu/releases/16.04/release/ubuntu-16.04-preinstalled-server-armhf+raspi2.img.xz
[Steps to Reproduce]
1. Install the image in an SD car
journalctl --unit=systemd-udev-trigger verbose log suggested as comment5
** Attachment added: "lp1665280-systemd-udev-trigger-verbose.log"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1665280/+attachment/4820711/+files/lp1665280-systemd-udev-trigger-verbose.log
--
You received
I can reproduce this issue. Reproducing rate: 5 out of 5.
This issue could reproduce via the following both ways:
* Download the image and apt-get update to the latest stack.
* apt-get update with an existing system.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665280
Title:
Boot into emergency mode on RPi2 with proposed kernel 4.4.0-1043.50
after system update
To manage notific
Hi, Taihsiang Ho.
Can you reproduce the problem, or did it happen only once? That way, we
can understand how easy it should be to reproduce, and if there is some
kind of race involved.
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
It looks like there is an oops when udevadm trigger writes "add" to some
module uevent. Can you edit /lib/systemd/system/systemd-udev-
trigger.service and add --verbose after subsystems?
The line would be like this:
ExecStart=/bin/udevadm trigger --type=subsystems --verbose --action=add
; /bin/ud
The following were collected by root in emergency mode:
/var/log/syslog http://paste.ubuntu.com/24006850/
dmesg http://paste.ubuntu.com/24006852/
journalctl -xb http://paste.ubuntu.com/24006861/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can you log in and run journalctl -xb?
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665280
Title:
Boot into emergency mode on RPi2 with proposed kernel 4.4.0-1043.50
after sys
Here you go the LCD screenshot of the term "Welcome to emergency mode".
** Attachment added: "2017-02-16 18.44.40.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1665280/+attachment/4820008/+files/2017-02-16%2018.44.40.jpg
--
You received this bug notification because you ar
There's no emergency mode in that image, what you exactly mean for
emergency mode?
Can you connect a serial cable or lcd screen and tell us what you see?
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you
14 matches
Mail list logo
