New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 779122 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

chrome crashes with "V4L2DecoderThre[23694]: segfault at 0 ip 0000026b9d52a152 sp 00007da7db9d6690 error 4"

Project Member Reported by mzhuo@chromium.org, Oct 27 2017

Issue description

Guado running R61-9765.86.0
1. enrolled in crasprqa4.com
2. have autozoom turned on in cpanel.

what steps will reproduce the problem?
(1)join meeting
(2)mute/unmute camera and microphone
(3)change volume
Repeat 1-3 in loop

What is the expected result?
No crash

What happens instead?
chrome crash

kernel log
----------
2017-10-27T09:55:12.381237-07:00 ERR kernel: [240947.317741] go2001 0000:03:00.0: go2001_dec_g_fmt_cap:1574 Frame info not available yet
2017-10-27T09:55:12.398116-07:00 DEBUG kernel: [240947.335013] delay: estimated 288, actual 0
2017-10-27T09:55:12.398126-07:00 DEBUG kernel: [240947.335030] delay: estimated 288, actual 48
2017-10-27T09:55:12.431949-07:00 INFO kernel: [240947.369163] V4L2DecoderThre[23694]: segfault at 0 ip 0000026b9d52a152 sp 00007da7db9d6690 error 4 in chrome[26b9c554000+7f2b000]
2017-10-27T09:55:12.441255-07:00 WARNING crash_reporter[24235]: [user] Received crash notification for chrome[15696] sig 11, user 1000 (developer build - not testing - always dumping)
2017-10-27T09:55:12.442257-07:00 INFO crash_reporter[24235]: State of crashed process [15696]: D (disk sleep)
2017-10-27T09:55:12.449248-07:00 WARNING crash_reporter[24237]: Received crash notification for chrome[15696] user 1000 (called directly)
2017-10-27T09:55:12.450462-07:00 ERR crash_reporter[24252]: Could not create /var/spool/crash/chrome.20171027.095512.15696.chrome.txt: Permission denied
2017-10-27T09:55:12.450613-07:00 INFO crash_reporter[24237]: Log command "  for f in $(ls -1rt /var/log/chrome/chrome_[0-9]* | tail -2)     $(ls -1rt /home/chronos/u-*/log/chrome_[0-9]* 2>/dev/null | tail -2); do     echo "===$f (tail)===";     tail -20 $f;     echo EOF;     echo;   done;   echo "===session_manager (tail)===";   awk '$3 ~ "^session_manager\[" { print }' /var/log/messages | tail -20;   echo "===dma-buf-mmap debug===";   grep -C 5 'dma-buf-mmap:' /var/log/messages | tail -200;   echo EOF" exited with 127
2017-10-27T09:55:12.463536-07:00 ERR crash_reporter[24237]: Could not write file /var/spool/crash/chrome.20171027.095512.15696.i915_error_state.log.xz Written: -1 Len: 84
2017-10-27T09:55:12.463642-07:00 ERR crash_reporter[24237]: Unable to write /var/spool/crash/chrome.20171027.095512.15696.meta
2017-10-27T09:55:12.801444-07:00 INFO crash_reporter[24235]: Stored minidump to /var/spool/crash/chrome.20171027.095512.15696.dmp
2017-10-27T09:55:12.801585-07:00 INFO crash_reporter[24235]: Leaving core file at /var/spool/crash/chrome.20171027.095512.15696.core due to developer image

GOOGLE_RELEASE=9765.86.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=guado
CHROMEOS_RELEASE_BUILD_NUMBER=9765
CHROMEOS_RELEASE_BRANCH_NUMBER=86
CHROMEOS_RELEASE_CHROME_MILESTONE=61
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=9765.86.0 (Official Build) dev-channel guado test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=9765.86.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
localhost crash # uptime
 10:07:28 up 2 days, 19:04,  0 users,  load average: 0.29, 0.43, 1.18
localhost crash # generate_logs 
[1027/100904:INFO:generate_logs.cc(86)] Gathering logs, please wait
cd /sp	[1027/100906:INFO:generate_logs.cc(91)] Logs saved to /tmp/debug-logs_20171027-100904.tgz

drwxr-xr-x 5 root root      4096 Oct 20 00:20 ..
-rw-r--r-- 1 root root     12081 Oct 27 09:55 chrome.20171027.095512.15696.log
-rw-r--r-- 1 root root 296312832 Oct 27 09:55 chrome.20171027.095512.15696.core
-rw-r--r-- 1 root root       170 Oct 27 09:55 chrome.20171027.095512.15696.meta
-rw------- 1 root root    320456 Oct 27 09:55 chrome.20171027.095512.15696.dmp

 

Comment 1 by mzhuo@chromium.org, Oct 27 2017

core files and debug log file are uploaded to https://drive.google.com/corp/drive/u/0/folders/1h_GCK5wcVIPRVC3pT0krDf7A5tHSI3Uw.

Comment 2 by mzhuo@chromium.org, Oct 27 2017

Test log
----------
11:55:08 INFO | autoserv| 100.107.146.17: Start Test: 9, meets: 9, muted/unmuted/volume change from Hotrod: 35
11:55:08 INFO | autoserv| Checking usb devices in usb kernel: ['2bd9:0011', '18d1:8001', '17e9:016b', '266e:0110']
11:55:09 INFO | autoserv| check device 2bd9:0011
11:55:09 INFO | autoserv| check device 18d1:8001
11:55:09 INFO | autoserv| check device 17e9:016b
11:55:09 INFO | autoserv| check device 266e:0110
11:55:11 INFO | autoserv| 100.107.146.17: meet uqt-gegm-cyj joined
11:55:11 INFO | autoserv| Checking devices after joining meeting
11:55:11 INFO | autoserv| Check video on 100.107.146.17 for meet uqt-gegm-cyj:video should not be muted upon joining meeting
11:55:11 INFO | autoserv| Checking camera
11:55:12 INFO | autoserv| Checking speaker
11:55:12 INFO | autoserv| Hotrod volume is 60 for Bluestreak 100.107.146.17
11:55:12 INFO | autoserv| Volume in BlueStreak and cras are sync for node 9? cfm: 60, cras: 60
11:55:12 INFO | autoserv| Checking usb devices in usb kernel: ['2bd9:0011', '18d1:8001', '17e9:016b', '266e:0110']
11:55:13 INFO | autoserv| check device 2bd9:0011
11:55:13 INFO | autoserv| check device 18d1:8001
11:55:13 INFO | autoserv| check device 17e9:016b
11:55:13 INFO | autoserv| check device 266e:0110
11:55:31 INFO | autoserv| Checking periphreal devices during meeting
11:55:32 INFO | autoserv| Hotrod volume is 60 for Bluestreak 100.107.146.17
11:55:32 INFO | autoserv| Volume in BlueStreak and cras are sync for node 9? cfm: 60, cras: 60
11:55:34 INFO | autoserv| Great news, no error found in log
11:55:34 INFO | autoserv| Checking usb devices in usb kernel: ['2bd9:0011', '18d1:8001', '17e9:016b', '266e:0110']
11:55:35 INFO | autoserv| check device 2bd9:0011
11:55:35 INFO | autoserv| check device 18d1:8001
11:55:35 INFO | autoserv| check device 17e9:016b
11:55:35 INFO | autoserv| check device 266e:0110
11:55:35 INFO | autoserv| Start to mute camera for Bluestreak 100.107.146.17
11:55:37 INFO | autoserv| Start to mute microphone for Bluestreak 100.107.146.17
11:55:39 INFO | autoserv| Start to change volume for Bluestreak 100.107.146.17
11:55:41 INFO | autoserv| Checking periphreal devices during meeting
11:55:42 INFO | autoserv| Hotrod volume is 56 for Bluestreak 100.107.146.17
11:55:42 INFO | autoserv| Volume in BlueStreak and cras are sync for node 9? cfm: 56, cras: 56
11:55:44 INFO | autoserv| Great news, no error found in log
11:56:12 INFO | autoserv| Checking periphreal devices during meeting
11:56:14 INFO | autoserv| Hotrod volume is 56 for Bluestreak 100.107.146.17
11:56:14 INFO | autoserv| Volume in BlueStreak and cras are sync for node 9? cfm: 56, cras: 56
11:56:15 INFO | autoserv| Great news, no error found in log
11:56:15 INFO | autoserv| Checking usb devices in usb kernel: ['2bd9:0011', '18d1:8001', '17e9:016b', '266e:0110']
11:56:16 INFO | autoserv| check device 2bd9:0011
11:56:16 INFO | autoserv| check device 18d1:8001
11:56:16 INFO | autoserv| check device 17e9:016b
11:56:16 INFO | autoserv| check device 266e:0110
11:56:16 INFO | autoserv| Start to unmute camera for Bluestreak 100.107.146.17
11:56:19 INFO | autoserv| Start to unmute microphone for Bluestreak 100.107.146.17
11:56:21 INFO | autoserv| Start to change volume for Bluestreak 100.107.146.17
11:56:23 INFO | autoserv| Checking periphreal devices during meeting
11:56:24 INFO | autoserv| Hotrod volume is 93 for Bluestreak 100.107.146.17
11:56:24 INFO | autoserv| Volume in BlueStreak and cras are sync for node 9? cfm: 93, cras: 93
11:56:26 INFO | autoserv| Great news, no error found in log
11:56:53 INFO | autoserv| Checking periphreal devices during meeting
11:56:54 INFO | autoserv| Hotrod volume is 93 for Bluestreak 100.107.146.17
11:56:54 INFO | autoserv| Volume in BlueStreak and cras are sync for node 9? cfm: 93, cras: 93
11:56:56 INFO | autoserv| Great news, no error found in log
11:56:56 INFO | autoserv| Checking usb devices in usb kernel: ['2bd9:0011', '18d1:8001', '17e9:016b', '266e:0110']
11:56:57 INFO | autoserv| check device 2bd9:0011
11:56:57 INFO | autoserv| check device 18d1:8001
11:56:57 INFO | autoserv| check device 17e9:016b
11:56:57 INFO | autoserv| check device 266e:0110
11:56:57 INFO | autoserv| Start to mute camera for Bluestreak 100.107.146.17
11:56:59 INFO | autoserv| Start to mute microphone for Bluestreak 100.107.146.17
11:57:01 INFO | autoserv| Start to change volume for Bluestreak 100.107.146.17
11:57:03 INFO | autoserv| Checking periphreal devices during meeting
11:57:05 INFO | autoserv| Hotrod volume is 76 for Bluestreak 100.107.146.17
11:57:05 INFO | autoserv| Volume in BlueStreak and cras are sync for node 9? cfm: 76, cras: 76
11:57:07 INFO | autoserv| Great news, no error found in log
11:57:26 INFO | autoserv| Great news, no error found in log
11:57:28 INFO | autoserv| 100.107.146.17: meet uqt-gegm-cyj ended
11:57:47 INFO | autoserv| Checking usb devices in usb kernel: ['2bd9:0011', '18d1:8001', '17e9:016b', '266e:0110']
11:57:48 INFO | autoserv| check device 2bd9:0011
11:57:48 INFO | autoserv| check device 18d1:8001
11:57:48 INFO | autoserv| check device 17e9:016b
11:57:48 INFO | autoserv| check device 266e:0110
11:57:50 INFO | autoserv| Great news, no error found in log
11:57:50 INFO | autoserv| >>>> Test result for test 100.107.146.17 on 9: PASS!!!
11:57:50 INFO | autoserv| Bluestreak 100.107.146.17 joins/leaves meeting uqt-gegm-cyj, duration 136 sec total duration: 26 min.
11:57:50 INFO | autoserv| ===>Guado: 100.107.146.17, device: Huddly GO.
11:57:50 INFO | autoserv| ===>Guado: 100.107.146.17, device: Hangouts Meet speakermic.
11:57:50 INFO | autoserv| ===>Guado: 100.107.146.17, device: DisplayLink.
11:57:50 INFO | autoserv| ===>Guado: 100.107.146.17, device: SiS HID Touch Controller.
11:57:50 INFO | autoserv| 
11:57:50 INFO | autoserv| 
11:57:50 INFO | autoserv| ********************Test Summary****************************************
11:57:50 INFO | autoserv| Number of tests: 9
11:57:50 INFO | autoserv| Number of times peripherals checked in USB kernel stack: 66
11:57:50 INFO | autoserv| Number of times camera failed to be enumerated: 0
11:57:50 INFO | autoserv| Number of times camera failed to initialize interface: 0
11:57:50 INFO | autoserv| Number of time camera failed to initialize v4l2 interface: 0
11:57:50 INFO | autoserv| Number of times camera checked: 83
11:57:50 INFO | autoserv| Number of times speaker failed to be enumerated: 0
11:57:50 INFO | autoserv| Number of times speaker failed to initialize interface: 0
11:57:50 INFO | autoserv| Number of times speaker checked: 83
11:57:50 INFO | autoserv| Number of times displaylink failed to be enumerated: 0
11:57:50 INFO | autoserv| Number of times displaylink failed to initialize interface: 0
11:57:50 INFO | autoserv| Number of times touch panel failed to be enumerated: 0
11:57:50 INFO | autoserv| Number of times touch panel failed to initialize interface: 0
11:57:50 INFO | autoserv| 
11:57:50 INFO | autoserv| >>>>> Total Meetings/Duration: 9, 26 min
11:57:50 INFO | autoserv| Total mute/unmute camera/mic and changing volume: 38
11:57:50 INFO | autoserv| Number of failure for v4l2 interface: 0
11:57:50 INFO | autoserv| Number of failure for v4l2 detaching from chrome: 0
11:57:50 INFO | autoserv| Number of failure for v4l2 attaching from chrome: 0
11:57:50 INFO | autoserv| Number of failure for muting camera: 0
11:57:50 INFO | autoserv| Number of failure for unmuting camera: 0
11:57:50 INFO | autoserv| Number of times camera checked: 83
11:57:50 INFO | autoserv| Number of failure for preferred speaker setting failure: 0
11:57:50 INFO | autoserv| Number of failure for preferred mic setting failure: 0
11:57:50 INFO | autoserv| Number of failure for muting mic: 0
11:57:50 INFO | autoserv| Number of failure for audio streaming failure when mic is muted: 0
11:57:50 INFO | autoserv| Number of failure for unmuting mic: 0
11:57:50 INFO | autoserv| Number of failure for audio streaming failure when mic is unmuted: 0
11:57:50 INFO | autoserv| Number of failure for setting volume failure: 0
11:57:50 INFO | autoserv| Number of times speaker checked: 83
11:57:50 INFO | autoserv| 
11:57:50 INFO | autoserv| >>>>> Log file scanning report for test 9:
11:57:50 INFO | autoserv| Kernel error: 0
11:57:50 INFO | autoserv| USB Kernel error: 0
11:57:50 INFO | autoserv| USB device flap error: 0
11:57:50 INFO | autoserv| Chrome error: 0
11:57:50 INFO | autoserv| Kernel uvcvideo error: 0
11:57:50 INFO | autoserv| Kernel audio error: 0
11:57:50 INFO | autoserv| Atrus error: 0
11:57:50 INFO | autoserv| Number of process crashing detected: 0
11:57:50 INFO | autoserv| **********************************************************************
11:57:50 INFO | autoserv| 
11:57:50 INFO | autoserv| 
11:57:50 INFO | autoserv| There is process crashed on 100.107.146.17.
 

Comment 3 by mzhuo@chromium.org, Oct 27 2017

Cc: mattfrazier@chromium.org bmayer@chromium.org

Comment 4 by mzhuo@chromium.org, Oct 27 2017

Cc: -denniswu@chromium.org

Comment 5 by mzhuo@chromium.org, Oct 27 2017

Checked log files on 9 setups. Found it has happened a few times with and without autozoom turned on. 

Without autozoom on:
1.  100.123.170.8
/var/log/messages.1:2017-10-26T15:10:23.617202-07:00 INFO kernel: [173405.086385] V4L2DecoderThre[22725]: segfault at 0 ip 00000c98850ab152 sp 000077f916b7f690 error 4 in chrome[c98840d5000+7f2b000]
localhost ~

2. 100.107.146.14
/var/log/messages.1:2017-10-25T20:38:22.742628-07:00 INFO kernel: [106630.201673] V4L2DecoderThre[21733]: segfault at 0 ip 0000021b39f69152 sp 00007a5a24ddf690 error 4 in chrome[21b38f93000+7f2b000]

3. 100.107.146.14
/var/log/messages.2:2017-10-25T14:37:37.965662-07:00 INFO kernel: [84968.937145] V4L2DecoderThre[25753]: segfault at 0 ip 0000035b80647152 sp 0000721d81b4d690 error 4 in chrome[35b7f671000+7f2b000]

4.100.107.146.17
/var/log/messages.1:2017-10-26T18:19:34.810952-07:00 INFO kernel: [184764.399690] V4L2DecoderThre[7623]: segfault at 0 ip 0000008fe4758152 sp 00007632a9815690 error 4 in chrome[8fe3782000+7f2b000]

With autozoom on:
================
5. 100.107.146.17
var/log/messages.1:2017-10-27T09:55:12.431949-07:00 INFO kernel: [240947.369163] V4L2DecoderThre[23694]: segfault at 0 ip 0000026b9d52a152 sp 00007da7db9d6690 error 4 in chrome[26b9c554000+7f2b000]

6.100.123.174.2
2017-10-27T10:39:23.684450-07:00 INFO kernel: [243629.107834] V4L2DecoderThre[9811]: segfault at 0 ip 0000055f47538152 sp 000075bac338c690 error 4 in chrome[55f46562000+7f2b000]
localhost ~ # check guado: 100.123.175.190

checked kerneal log for above 2 cases on 100.107.146.14, during the time there is no huddly flapping. 
localhost ~ # grep 5T20:3 /var/log/messages.1 | grep -v autotest | grep -E "segfault|usb 2-|USB disconnect|Huddly"
2017-10-25T20:38:22.742628-07:00 INFO kernel: [106630.201673] V4L2DecoderThre[21733]: segfault at 0 ip 0000021b39f69152 sp 00007a5a24ddf690 error 4 in chrome[21b38f93000+7f2b000]
2017-10-25T20:38:29.266637-07:00 INFO kernel: [106636.730576] Media[1156]: segfault at 0 ip 00000e6f1e279591 sp 00007d1c279047a0 error 6 in chrome[e6f1a600000+60b1000]
localhost ~ # grep 25T14:3 /var/log/messages.2 | grep -v autotest | grep -E "segfault|usb 2-|USB disconnect|Huddly"
2017-10-25T14:37:37.965662-07:00 INFO kernel: [84968.937145] V4L2DecoderThre[25753]: segfault at 0 ip 0000035b80647152 sp 0000721d81b4d690 error 4 in chrome[35b7f671000+7f2b000]
localhost ~ # 


Cc: egemih@chromium.org bhthompson@chromium.org wuchengli@chromium.org
+others 

min - how often does this occur? can we bisect and understand when this started?

Sign in to add a comment