skcasb
Posts: 18
Joined: Wed Jul 11, 2018 12:46 pm

Raspberry PI 3B+ with kernel 4.19.66-v7+ - hdmi issue ?

Tue Sep 10, 2019 9:12 am

Hi all,

I normally use pi-gen a tool used to create the raspberrypi.org Raspbian stretch images, the current kernel version downloaded from repository is 4.19.66-v7+

in config.txt we have set a custom HDMI mode:

Code: Select all

hdmi_group=2
hdmi_mode=87
hdmi_cvt=800 480 60 3 0 0 0
We had notice a strange behaviour, no image on the display and if we issue the following command:

Code: Select all

tvservice -s

it responds with an incorrect value
state 0x40000 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced
instead of
state 0x120006 [DVI DMT (87) RGB full 16:9], 800x480 @ 59.00Hz, progressive

dmesg contains a kernel exception

Code: Select all

[    7.429029] Unable to handle kernel NULL pointer dereference at virtual address 0000001c
[    7.437286] pgd = 6b49adaa
[    7.440022] [0000001c] *pgd=1d1fb835, *pte=00000000, *ppte=00000000
[    7.446429] Internal error: Oops: 17 [#1] SMP ARM
[    7.451161] Modules linked in: joydev evdev vc4 snd_usb_audio snd_hwdep snd_usbmidi_lib sg snd_rawmidi snd_seq_device ftdi_sio drm_kms_helper hid_multitouch usbserial cdc_acm drm uas drm_panel_orientation_quirks snd_soc_core snd_bcm2835(C) snd_compress snd_pcm_dmaengine syscopyarea snd_pcm sysfillrect bcm2835_codec(C) sysimgblt fb_sys_fops v4l2_mem2mem bcm2835_v4l2(C) snd_timer bcm2835_mmal_vchiq(C) v4l2_common raspberrypi_hwmon hwmon snd videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common i2c_bcm2835 videodev media vc_sm_cma(C) uio_pdrv_genirq uio fixed rtc_pcf2127 i2c_dev ip_tables x_tables ipv6
[    7.507534] CPU: 2 PID: 178 Comm: plymouthd Tainted: G         C        4.19.66-v7+ #1253
[    7.515730] Hardware name: BCM2835
[    7.519412] PC is at drm_mode_object_get_properties+0x88/0x138 [drm]
[    7.526021] LR is at drm_mode_getconnector+0x3a4/0x470 [drm]
[    7.531689] pc : [<7f3ed63c>]    lr : [<7f3ec4fc>]    psr: 20000113
[    7.537964] sp : 9d19fcd8  ip : 05c3edc4  fp : 9d19fd24
[    7.543196] r10: 00000000  r9 : 00000000  r8 : af2ab054
[    7.548429] r7 : 9d19fe48  r6 : 00000000  r5 : 00000004  r4 : 00000005
[    7.554970] r3 : af2ab154  r2 : 00000000  r1 : 00000000  r0 : af2ab140
[    7.561511] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[    7.568669] Control: 10c5383d  Table: 1d22406a  DAC: 00000055
[    7.574437] Process plymouthd (pid: 178, stack limit = 0x7994596b)
[    7.580631] Stack: (0x9d19fcd8 to 0x9d1a0000)
[    7.584999] fcc0:                                                       9d19fd04 80d04d48
[    7.593202] fce0: 00000000 9d19e018 00000000 00000000 9d2aad60 05c3edc4 9d19fd24 9d2aad60
[    7.601404] fd00: af2ab054 9e6b6a00 9d19fe24 00000001 af2ab094 af2ab094 9d19fdc4 9d19fd28
[    7.609605] fd20: 7f3ec4fc 7f3ed5c0 9d19fe48 9d19fd38 808367e4 af2ab2e0 00000000 80d04d48
[    7.617806] fd40: 9d2aac00 9d2aad4c 9d19fd48 9d19fd48 00000000 00000000 00000000 00000000
[    7.626006] fd60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    7.634206] fd80: 00000000 00000000 00000000 00000000 00000000 05c3edc4 9d19fde4 80d04d48
[    7.642407] fda0: 9d2aac00 9e6b6a00 00000010 7f3ec158 9d19fe24 00000050 9d19fdf4 9d19fdc8
[    7.650609] fdc0: 7f3d3aec 7f3ec164 00000000 05c3edc4 80d04d48 7f3fdf30 00000050 9d19fe24
[    7.658810] fde0: 00000050 9e6b6a00 9d19fed4 9d19fdf8 7f3d3ed4 7f3d3a44 00000001 7f40dac0
[    7.667011] fe00: 8024c500 80276098 9d19fe24 9d19fe24 9ddf6240 000000a7 7eec88a0 c05064a7
[    7.675210] fe20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    7.683410] fe40: 00000000 00000000 00000000 00000001 00000000 00000033 00000005 00000001
[    7.691610] fe60: 00000001 00000000 00000000 00000000 00000000 00000001 9d19e000 802bc970
[    7.699811] fe80: 9d19ff44 9d19fe90 802bc970 802b5b30 9e77b210 9e1182a8 1dfe86fb 00000005
[    7.708012] fea0: 9e6a7019 05c3edc4 00000000 80d04d48 7eec88a0 9c5d88a0 9ddf6240 0000000a
[    7.716213] fec0: 9d19e000 00000036 9d19ff6c 9d19fed8 802bf870 7f3d3cb0 80836af8 802a8408
[    7.724413] fee0: af0cec00 af0cec18 00000000 80d04d48 00020002 802bb9ac 00000001 9ddf6248
[    7.732615] ff00: 9e6a7000 9e6a7000 80d04d48 9ddf6240 9e6a7000 9ddf6248 9c5d88a0 00000020
[    7.740815] ff20: 9d19ff44 9d19ff30 802bb9ac 80295e08 af0cec54 0000000a 9d19ff94 05c3edc4
[    7.749017] ff40: 802a843c 9ddf6240 7eec88a0 9ddf6240 c05064a7 0000000a 9d19e000 00000036
[    7.757217] ff60: 9d19ff94 9d19ff70 802bfffc 802bf7c0 00000000 00000001 7eec88a0 c05064a7
[    7.765418] ff80: 00000036 801011c4 9d19ffa4 9d19ff98 802c003c 802bffc4 00000000 9d19ffa8
[    7.773619] ffa0: 80101000 802c0030 00000001 7eec88a0 0000000a c05064a7 7eec88a0 00000000
[    7.781819] ffc0: 00000001 7eec88a0 c05064a7 00000036 00000002 7eec88a0 0000000a 00f1d520
[    7.790020] ffe0: 76bb708c 7eec887c 76b9e950 76e29c7c 20000010 0000000a 00000000 00000000
[    7.798754] [<7f3ed63c>] (drm_mode_object_get_properties [drm]) from [<7f3ec4fc>] (drm_mode_getconnector+0x3a4/0x470 [drm])
[    7.810381] [<7f3ec4fc>] (drm_mode_getconnector [drm]) from [<7f3d3aec>] (drm_ioctl_kernel+0xb4/0xf0 [drm])
[    7.820610] [<7f3d3aec>] (drm_ioctl_kernel [drm]) from [<7f3d3ed4>] (drm_ioctl+0x230/0x3cc [drm])
[    7.829746] [<7f3d3ed4>] (drm_ioctl [drm]) from [<802bf870>] (do_vfs_ioctl+0xbc/0x804)
[    7.837695] [<802bf870>] (do_vfs_ioctl) from [<802bfffc>] (ksys_ioctl+0x44/0x6c)
[    7.845117] [<802bfffc>] (ksys_ioctl) from [<802c003c>] (sys_ioctl+0x18/0x1c)
[    7.852278] [<802c003c>] (sys_ioctl) from [<80101000>] (ret_fast_syscall+0x0/0x28)
[    7.859865] Exception stack(0x9d19ffa8 to 0x9d19fff0)
[    7.864930] ffa0:                   00000001 7eec88a0 0000000a c05064a7 7eec88a0 00000000
[    7.873130] ffc0: 00000001 7eec88a0 c05064a7 00000036 00000002 7eec88a0 0000000a 00f1d520
[    7.881327] ffe0: 76bb708c 7eec887c 76b9e950 76e29c7c
[    7.886396] Code: e1530004 da000021 e0803104 e593a004 (e59a301c) 
[    7.892624] ---[ end trace 256fe1910b568ee7 ]---
it seems that this firmware/kernel version does not read the HDMI parameters in the config.txt file.

If we try to downgrade the firmware/kernel to a previous version 4.19.42-v7+, solve the problem.

Did you also have the same problem?

How did you solve it?

Thank you.

skcasb
Posts: 18
Joined: Wed Jul 11, 2018 12:46 pm

Re: Raspberry PI 3B+ with kernel 4.19.66-v7+ - hdmi issue ?

Tue Sep 10, 2019 12:34 pm

Hi all,

It's always me.

How can I modify the pi-gen scripts to have a kernel/bootloader to a specific release in the resulting image ?

The resulting image must have the right version of kernel/bootloader.

Thank you again

skcasb
Posts: 18
Joined: Wed Jul 11, 2018 12:46 pm

Re: Raspberry PI 3B+ with kernel 4.19.66-v7+ - hdmi issue ?

Wed Sep 11, 2019 10:11 am

Hi all,

I think I understand that my problem depends on the following files.

Code: Select all

fixup.dat
fixup_x.dat
start.elf
start_x.elf
We use an LCD 800x480@60, for this reason we need to use a custom mode on config.txt file.
The latest stretch image created one week ago using pi-gen, doesn't show anything on LCD.

But If I overwrite the same files with older one of one month ago, LCD works fine.

Can you tell me when the raspberry stretch repository will be updated with new firmware version ?

Or any other solution it is welcome.

Thank you.

Return to “Troubleshooting”