Reading from /sys/devices/system/cpaccess/cpaccess0/cp_rw crashes the Nexus 4

Bug #1425290 reported by Sturm Flut
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
Undecided
Unassigned
linux-mako (Ubuntu)
Confirmed
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/system/cpaccess/cpaccess0/cp_rw

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.

Revision history for this message
Sturm Flut (sturmflut) wrote :

The USB port luckily came back to life after fully draining the battery.

Revision history for this message
Sturm Flut (sturmflut) wrote :

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/system/cpaccess/cpaccess0/cp_rw
512f06f0

Revision history for this message
Launchpad Janitor (janitor) wrote :

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.