Comment 18 for bug 1761729
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #18 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
------- Comment From <email address hidden> 2018-04-17 13:13 EDT-------
The logs show some "read_all" process - presumably part of the test suite - that is trying to read kernel text memory (via /dev/mem) and triggering the BUG. Not clear if the attempt should have been failed gracefully or not. I'd assume the expectation is that a illegal read from /dev/mem should return an error rather than panic.
Comment #21 shows a different panic, and since no logs or vmcore are provided I can't tell any more about it. If this latest panic is the only reason the bug is open, we need to move that to a new bugzilla as it is not the same issue.
------- Comment From <email address hidden> 2018-04-17 13:15 EDT-------
Comment #19 also shows a different issue than originally reported. So, it seems this bugzilla has deviated from the original problem.