Linaro Linux17.04.1 is rebooted


#1

Hi

Could you please teach me about how to disable reboot.

Now,I use Linaro Linux 17.04.1 image.

But I think that the same problem as discussed 17.04 release topic is occurring.

This issue was happened at no working for a little time(maybe 10 min).

The log at that is here;

[ 2284.679853] msm 1a00000.mdss: vblank time out, crtc=0
[ 2284.739865] msm 1a00000.mdss: vblank time out, crtc=0
[ 3080.274545] msm 1a00000.mdss: vblank time out, crtc=0
[ 3080.334517] msm 1a00000.mdss: vblank time out, crtc=0
[ 3083.854643] Bad mode in Error handler detected on CPU0, code 0xbf000000 – SError
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic

If someone knows how to solve it please teach me.
And if you need all log,I will take it.

I will create demo to working for long time(8 hour).
So i want to solve this.

Best regards,


#2

hi,

i am definitely not seeing that… my board has been running with this build for several days by now. and the display has been going on and off several times.

The ‘bad mode’ error indicates that something fundamentally wrong happened… what were you doing on the board before it crashed?

cheers


#3

Hi @ndec

Thank you for quick reply.

When I made a post earlier I was moving ”package install","Internet of Chromium"and working gstreamer.

The log at that time is here;

[ 1003.718086] mmc1: error -110 whilst initialising SD card
[ 1003.821672] mmc1: Reset 0x1 never completed.
[ 1003.821722] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 1003.825026] sdhci: Sys addr: 0x00000000 | Version: 0x00002e02
[ 1003.830668] sdhci: Blk size: 0x00004000 | Blk cnt: 0x00000000
[ 1003.836483] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[ 1003.842301] sdhci: Present: 0x01f80000 | Host ctl: 0x00000000
[ 1003.848115] sdhci: Power: 0x00000000 | Blk gap: 0x00000000
[ 1003.853931] sdhci: Wake-up: 0x00000000 | Clock: 0x00000003
[ 1003.859746] sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
[ 1003.865563] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[ 1003.871380] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1003.877195] sdhci: Caps: 0x322dc8b2 | Caps_1: 0x00008007
[ 1003.882999] sdhci: Cmd: 0x00000000 | Max curr: 0x00000000
[ 1003.888814] sdhci: Host ctl2: 0x00000000
[ 1003.894630] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
[ 1003.898712] sdhci: ===========================================
[ 1004.287062] mmc1: new ultra high speed SDR104 SDHC card at address 0007
[ 1004.288861] mmcblk1: mmc1:0007 SD08G 7.42 GiB
[ 1004.294002] mmcblk1: p1
[ 1051.871046] mmc1: card 0007 removed
[ 1121.045253] mmc1: new ultra high speed SDR104 SDHC card at address 0007
[ 1121.048368] mmcblk1: mmc1:0007 SD08G 7.42 GiB
[ 1121.056436] mmcblk1: p1
[ 1273.255815] ------------[ cut here ]------------
[ 1273.255906] WARNING: CPU: 0 PID: 4482 at …/drivers/media/v4l2-core/videobuf2-v4l2.c:149 vb2_warn_zero_bytesused.isra.11.part.12+0x1c/0x80 [videobuf2_v4l2]
[ 1273.259521] Modules linked in: ctr ccm rfcomm cmac bnep btqcomsmd btqca arc4 wcn36xx mac80211 bluetooth cfg80211 venus_enc venus_dec qcom_wcnss_pil msm_rng rng_core venus_core mdt_loader qcom_camss v4l2_mem2mem qcom_cci videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_core ip_tables x_tables
[ 1273.299864]
[ 1273.299962] CPU: 0 PID: 4482 Comm: m:sink Tainted: G W 4.9.30-linaro-lt-qcom #1
[ 1273.301525] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[ 1273.309946] task: ffff8000275f4e00 task.stack: ffff800015b9c000
[ 1273.316652] PC is at vb2_warn_zero_bytesused.isra.11.part.12+0x1c/0x80 [videobuf2_v4l2]
[ 1273.322295] LR is at __fill_vb2_buffer+0x428/0xb38 [videobuf2_v4l2]
[ 1273.330258] pc : [] lr : [] pstate: 20000145
[ 1273.336506] sp : ffff800015b9fac0
[ 1273.344140] x29: ffff800015b9fac0 x28: ffff000000a5f300
[ 1273.352469] x27: 0000000000000030 x26: ffff800029870600
[ 1273.357764] x25: ffff80000cfcf818 x24: ffff800029870600
[ 1273.363058] x23: 0000000000000000 x22: ffff80000cfcf818
[ 1273.368353] x21: 0000000000000000 x20: ffff80000cfcf800
[ 1273.373649] x19: ffff80000cfcf800 x18: 0000000000000000
[ 1273.378944] x17: 0000ffff9b466590 x16: ffff0000081f5fc8
[ 1273.384238] x15: 4434480e3d100626 x14: 00000001000003b6
[ 1273.389533] x13: 0000000000000000 x12: 0000000000000000
[ 1273.394829] x11: 000000000009b5fb x10: 000000000000001f
[ 1273.400123] x9 : 0000000000000001 x8 : 0000000000000000
[ 1273.405419] x7 : 0000000000000000 x6 : 0000000000000000
[ 1273.410715] x5 : ffff80000cfcf860 x4 : 000000000017bb80
[ 1273.416009] x3 : 0000000000000000 x2 : 0000000000000001
[ 1273.421306] x1 : ffff000000a5f300 x0 : ffff80000cfcf800
[ 1273.426598]
[ 1273.426776] —[ end trace 1a1d7f70afc50457 ]—
[ 1273.428343] Call trace:
[ 1273.432945] Exception stack(0xffff800015b9f8f0 to 0xffff800015b9fa20)
[ 1273.435121] f8e0: ffff80000cfcf800 0001000000000000
[ 1273.441722] f900: ffff800015b9fac0 ffff000000a5d464 0000000000000001 0000000000000001
[ 1273.449534] f920: 0000000000000000 0000000000000001 ffff800015b9f940 ffff0000083948b0
[ 1273.457348] f940: ffff800015b9f970 ffff0000080f2ec8 ffff000008fb7000 ffff80000a133018
[ 1273.465159] f960: 0000000000000000 0000000000000000 ffff800015b9faa0 ffff0000080f38fc
[ 1273.472973] f980: 000000010003b769 ffff000008fb7000 ffff80000cfcf800 ffff000000a5f300
[ 1273.480784] f9a0: 0000000000000001 0000000000000000 000000000017bb80 ffff80000cfcf860
[ 1273.488596] f9c0: 0000000000000000 0000000000000000 0000000000000000 0000000000000001
[ 1273.496408] f9e0: 000000000000001f 000000000009b5fb 0000000000000000 0000000000000000
[ 1273.504222] fa00: 00000001000003b6 4434480e3d100626 ffff0000081f5fc8 0000ffff9b466590
[ 1273.512054] [] vb2_warn_zero_bytesused.isra.11.part.12+0x1c/0x80 [videobuf2_v4l2]
[ 1273.519867] [] __fill_vb2_buffer+0x428/0xb38 [videobuf2_v4l2]
[ 1273.528735] [] __buf_prepare+0xf4/0x188 [videobuf2_core]
[ 1273.536025] [] vb2_core_qbuf+0x12c/0x208 [videobuf2_core]
[ 1273.542957] [] vb2_qbuf+0x68/0xa8 [videobuf2_v4l2]
[ 1273.549812] [] v4l2_m2m_qbuf+0x28/0x48 [v4l2_mem2mem]
[ 1273.556408] [] v4l2_m2m_ioctl_qbuf+0x14/0x20 [v4l2_mem2mem]
[ 1273.562734] [] v4l_qbuf+0x44/0x58
[ 1273.570019] [] __video_do_ioctl+0x23c/0x2a8
[ 1273.574707] [] video_usercopy+0x344/0x478
[ 1273.580607] [] video_ioctl2+0x14/0x20
[ 1273.585987] [] v4l2_ioctl+0x110/0x118
[ 1273.591202] [] do_vfs_ioctl+0xa4/0x748
[ 1273.596408] [] SyS_ioctl+0x8c/0xa0
[ 1273.601963] [] el0_svc_naked+0x24/0x28
[ 1273.607911] use of bytesused == 0 is deprecated and will be removed in the future,
[ 1273.612264] use VIDIOC_DECODER_CMD(V4L2_DEC_CMD_STOP) instead.
[ 2010.866575] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[ 2284.679853] msm 1a00000.mdss: vblank time out, crtc=0
[ 2284.739865] msm 1a00000.mdss: vblank time out, crtc=0
[ 3080.274545] msm 1a00000.mdss: vblank time out, crtc=0
[ 3080.334517] msm 1a00000.mdss: vblank time out, crtc=0
[ 3083.854643] Bad mode in Error handler detected on CPU0, code 0xbf000000 – SError

And now,I had a second encounter with the message.
This time,I didn’t work DragonBoard.

This log is here;
[ 2156.517172] mmcblk1: mmc1:0007 SD08G 7.42 GiB
[ 2156.519882] mmcblk1: p1
[ 2156.885572] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 2764.464394] msm 1a00000.mdss: vblank time out, crtc=0
[ 2764.520402] msm 1a00000.mdss: vblank time out, crtc=0
[ 3025.809839] wlan0: deauthenticated from 94:b4:0f:c6:06:62 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[ 3025.909626] wcn36xx: ERROR hal_remove_bsskey response failed err=16
[ 3033.736351] wlan0: authenticate with 94:b4:0f:c6:06:62
[ 3033.775962] wlan0: send auth to 94:b4:0f:c6:06:62 (try 1/3)
[ 3033.778695] wlan0: authenticated
[ 3033.788340] wlan0: associate with 94:b4:0f:c6:06:62 (try 1/3)
[ 3033.797888] wlan0: RX AssocResp from 94:b4:0f:c6:06:62 (capab=0x431 status=0 aid=1)
[ 3033.833976] wlan0: associated
[ 4767.252397] msm 1a00000.mdss: vblank time out, crtc=0
[ 4767.308409] msm 1a00000.mdss: vblank time out, crtc=0
[ 4769.903979] Bad mode in Error handler detected on CPU0, code 0xbf000000 – SError

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic

May I change other DragonBoards?

Best regards,


#4

in both cases the very first error comes the SD card. what is on the SD card? can you reproduce the error when you are not using the SD card? What type of SD card is inserted?


#5

@ndec

OK,now,I try to work without SD card.

SD card is SDHC card(8GB).But it was reformat.So it may be an error.…


#6

Now,Not rebboted!

Maybe SDcard is the cause as you said …

BTW,the following massage is displayed.
This massage is not bad?

Please teach me about its mean.

[ 450.959198] wlan0: associate with 26:f0:94:59:b9:9b (try 1/3)
[ 450.962964] wlan0: RX AssocResp from 26:f0:94:59:b9:9b (capab=0x411 status=0 aid=1)
[ 450.996846] wlan0: associated
[ 1739.714438] msm 1a00000.mdss: vblank time out, crtc=0
[ 1739.774507] msm 1a00000.mdss: vblank time out, crtc=0

Best regards,


#7

I’m sorry…

After all it rebooted.

[ 39.827802] wlan0: RX AssocResp from 94:b4:0f:c7:01:c2 (capab=0x431 status=0 aid=1)
[ 39.860289] wlan0: associated
[ 145.738018] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[ 145.741490] wlan0: disconnect from AP 94:b4:0f:c7:01:c2 for new auth to 94:b4:0f:c6:06:62
[ 145.765956] wlan0: authenticate with 94:b4:0f:c6:06:62
[ 145.811541] wlan0: send auth to 94:b4:0f:c6:06:62 (try 1/3)
[ 145.819592] wlan0: authenticated
[ 145.831221] wlan0: associate with 94:b4:0f:c6:06:62 (try 1/3)
[ 145.836698] wlan0: RX AssocResp from 94:b4:0f:c6:06:62 (capab=0x431 status=0 aid=1)
[ 145.869037] wlan0: associated
[ 303.806508] random: crng init done
[ 429.845295] wlan0: deauthenticating from 94:b4:0f:c6:06:62 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 429.885560] wcn36xx: ERROR hal_remove_bsskey response failed err=16
[ 450.891274] wlan0: authenticate with 26:f0:94:59:b9:9b
[ 450.937529] wlan0: send auth to 26:f0:94:59:b9:9b (try 1/3)
[ 450.939297] wlan0: authenticated
[ 450.959198] wlan0: associate with 26:f0:94:59:b9:9b (try 1/3)
[ 450.962964] wlan0: RX AssocResp from 26:f0:94:59:b9:9b (capab=0x411 status=0 aid=1)
[ 450.996846] wlan0: associated
[ 1739.714438] msm 1a00000.mdss: vblank time out, crtc=0
[ 1739.774507] msm 1a00000.mdss: vblank time out, crtc=0
[ 2236.938208] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[ 2553.160605] msm 1a00000.mdss: vblank time out, crtc=0
[ 2553.216588] msm 1a00000.mdss: vblank time out, crtc=0
[ 2555.566873] Bad mode in Error handler detected on CPU0, code 0xbf000000 – SError

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic


#8

hi,

i think we were able to reproduce a similar crash on our side. we are debugging and will keep you posted!

cheers


#9

Hi

I’m debugging DB410 with connecting to Wi-Fi via smartphone and AP for 3 days.

DB410 that is connecting Wi-Fi via smartphone rebooted only one time.

Perhaps it happens when the network is unstable…
But I could not clarify the reproducibility.

log is here;
[183036.985052] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[183937.077452] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[184539.516115] msm 1a00000.mdss: vblank time out, crtc=0
[184539.572133] msm 1a00000.mdss: vblank time out, crtc=0
[185258.105261] msm 1a00000.mdss: vblank time out, crtc=0
[185258.161198] msm 1a00000.mdss: vblank time out, crtc=0
[186518.044366] msm 1a00000.mdss: vblank time out, crtc=0
[186518.100336] msm 1a00000.mdss: vblank time out, crtc=0
[188717.044182] msm 1a00000.mdss: vblank time out, crtc=0
[188717.100168] msm 1a00000.mdss: vblank time out, crtc=0
[188721.736850] Bad mode in Error handler detected on CPU0, code 0xbf000000 – SError

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic


#10

Hi @ndec ,

I just meet the same issue on OE-RPB 17.06. Is this issue fixed in the latest version?

[  619.902041] msm 1a00000.mdss: vblank time out, crtc=0
[  619.958040] msm 1a00000.mdss: vblank time out, crtc=0
[  637.148632] Bad mode in Error handler detected on CPU0, code 0xbf000000 -- SError

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00286

Thanks,
Daniel


#11

Hello,
I can see the crushes on Debian 17.06 only when the Wi-Fi signal is very weak.
The problem can be easily repeated running iperf in UDP mode.


#12

hi,

we’ve been working on that issue for quite some time. We’ve done some good progress lately, and we should have an updated patchset to fix these issues later this week.


#13

Hello ndec,

Is there any progress on the weak Wi-Fi signal issue?
Our customer is waiting for an updated patchset.
Please update the status.