Reading from /sys/devices/system/cpaccess/cpaccess0/cp_rw crashes the Nexus 4
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Canonical System Image |
Undecided
|
Unassigned | ||
| | linux-mako (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
I noticed that my Nexus 4 crashed while doing a
grep "1" -r /
in an adb shell as user phablet. After narrowing it down, it looks like I can reliably crash my device by just doing a
cat /sys/devices/
as a normal user. After doing it about three times, all aspects of the device still work as expected, but it no longer identifies itself via USB, not even when in recovery mode. This might be a different issue, but it has never happened before, so I do think it might have been caused by the crashes.
| Sturm Flut (sturmflut) wrote : | #1 |
| Sturm Flut (sturmflut) wrote : | #2 |
I did some research and noticed that this only seems to happen on the Nexus 4. On the Nexus 5 (Android 4.4.4), reading the same sysfs file actually yields a result:
shell@hammerhead:/ $ cat /sys/devices/
512f06f0
| Launchpad Janitor (janitor) wrote : | #3 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in linux-mako (Ubuntu): | |
| status: | New → Confirmed |
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → John McAleely (john.mcaleely) |
| milestone: | none → backlog |
| status: | New → Confirmed |
| Changed in canonical-devices-system-image: | |
| assignee: | John McAleely (john.mcaleely) → nobody |
The USB port luckily came back to life after fully draining the battery.