I took a look and was able to repro on Arale with the latest rc-proposed
but it's difficult.

In my instance of the crash, I did not see the PVR kernel logs reported
by Simon in comment #7. (Also, I don't see them in the logs attached by
Dave and Victor). How were they obtained?

>From the logs I obtained, I saw a couple of lines spewed out by the PVR
kernel side :

./logs/logs:Mar 17 17:51:36 ubuntu-phablet kernel: [  688.646227] 
PVR_K:(Error): 104: RGXGetDeviceHealthStatus: KCCB for DM2 has not progressed 
(ROFF=10 WOFF=11) [0, ]
./logs/logs:Mar 17 20:55:38 ubuntu-phablet kernel: [ 2670.497641] 
PVR_K:(Error): 105: RGXGetDeviceHealthStatus: KCCB for DM0 has not progressed 
(ROFF=1 WOFF=2) [0, ]

but not when the crash happened. So I don't think they are related.

I did notice a constant stream of the following messages, but they seem to 
happen even when the camera is seemingly working normally. And sometimes, they 
don't happen.
...
./logs/logs:Mar 17 21:04:59 ubuntu-phablet kernel: [    7.331986] 
[mt-i2c]ERROR,454: id=0,addr: 10, transfer error
./logs/logs:Mar 17 21:04:59 ubuntu-phablet kernel: [    7.363560] 
[mt-i2c]ERROR,454: id=0,addr: 10, transfer error
./logs/logs:Mar 17 21:04:59 ubuntu-phablet kernel: [    7.363701] 
[mt-i2c]ERROR,454: id=0,addr: 10, transfer error
...

I can investigate the GL (PVR) driver side of things more if I someone
can tell me how/when PVRSRV related logs appear and how to collect them?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1551811

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Telegram app:
  Invalid
Status in mir package in Ubuntu:
  New

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1551811/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to