Kernel crash and reboot when accessing video device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-mako (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
lxc-android-config (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
While working on the container flip, we noticed that starting udev and calling udevadm trigger would cause the device to reboot instantly.
After some effort, we tracked this down to video4linux and specifically the 60-persistent-v4l rules file. Looking into it, we see it's calling v4l_id and that's what's causing the reboot.
Here's some basic reproducing step for saucy post-container flip:
root@android:/ # mv /lib/udev/
root@android:/ # start udev
udev start/running, process 1016
root@android:/ # start udevtrigger
udevtrigger stop/waiting
root@android:/ # cat /dev/video38
--- reboot ---
It looks like any attempt to open the video device causes the panic and reboot.
Unfortunately I don't have any way to get a console or any kernel debug information so all I can tell is that there's something very wrong going with that video device.
Changed in linux-mako (Ubuntu): | |
importance: | Undecided → High |
Status changed to 'Confirmed' because the bug affects multiple users.