Bug 112102 - External screen died with 'pipe state doesn't match'
Summary: External screen died with 'pipe state doesn't match'
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-22 14:21 UTC by Daniels Umanovskis
Modified: 2019-11-29 19:43 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg at crash (13.98 KB, text/x-log)
2019-10-23 09:24 UTC, Daniels Umanovskis
no flags Details
dmesg before the crash (3.97 KB, text/x-log)
2019-10-23 09:36 UTC, Daniels Umanovskis
no flags Details

Description Daniels Umanovskis 2019-10-22 14:21:33 UTC
I have a Dell Latitude 5500 connected through a docking station to two external screens. Occasionally, when they're in power saving mode and I wake the laptop, one of the screens fails to come back up. There's a 'pipe state doesn't match' error in dmesg at the corresponding time.

Oct 22 15:56:40 midgard kernel: [516468.781351] ------------[ cut here ]------------
Oct 22 15:56:40 midgard kernel: [516468.781352] pipe state doesn't match!
Oct 22 15:56:40 midgard kernel: [516468.781412] WARNING: CPU: 2 PID: 928 at drivers/gpu/drm/i915/intel_display.c:11888 intel_atomic_commit_tail+0xcc9/0xd40 [i915]
Oct 22 15:56:40 midgard kernel: [516468.781412] Modules linked in: ctr ccm rfcomm cmac arc4 snd_hda_codec_hdmi bnep intel_rapl binfmt_misc x86_pkg_temp_thermal intel_powerclamp mei_wdt coretemp dell_rbtn nls_ascii nls_cp437 kvm_intel vfat fat snd_soc_skl kvm snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core irqbypass crct10dif_pclmul snd_hda_codec_realtek iwlmvm dell_wmi crc32_pclmul dell_laptop btusb snd_hda_codec_generic snd_compress btrtl btbcm ghash_clmulni_intel dell_smbios dcdbas btintel efi_pstore mac80211 dell_wmi_descriptor intel_cstate wmi_bmof serio_raw joydev bluetooth snd_hda_intel dell_smm_hwmon snd_hda_codec snd_usb_audio uvcvideo intel_uncore snd_hda_core snd_usbmidi_lib iwlwifi snd_hwdep intel_rapl_perf snd_rawmidi videobuf2_vmalloc videobuf2_memops
Oct 22 15:56:40 midgard kernel: [516468.781431]  snd_seq_device videobuf2_v4l2 videobuf2_common snd_pcm cdc_ether videodev usbnet snd_timer rtsx_pci_ms r8152 media snd iTCO_wdt tpm_crb mii efivars drbg iTCO_vendor_support pcc_cpufreq memstick cfg80211 pcspkr soundcore ansi_cprng mei_me tpm_tis tpm_tis_core squashfs mei ecdh_generic tpm hid_multitouch ucsi_acpi idma64 rng_core rfkill zstd_decompress typec_ucsi processor_thermal_device xxhash typec intel_soc_dts_iosf intel_pch_thermal battery evdev int3403_thermal int340x_thermal_zone dell_smo8800 int3400_thermal intel_hid ac acpi_thermal_rel sparse_keymap acpi_pad dptf_power loop parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb hid_logitech_hidpp hid_logitech_dj usbhid hid_generic i915 crc32c_intel rtsx_pci_sdmmc mmc_core
Oct 22 15:56:40 midgard kernel: [516468.781453]  i2c_algo_bit drm_kms_helper psmouse nvme xhci_pci drm xhci_hcd aesni_intel rtsx_pci aes_x86_64 e1000e crypto_simd cryptd usbcore glue_helper thunderbolt nvme_core i2c_i801 i2c_hid intel_lpss_pci intel_lpss hid usb_common wmi thermal button video
Oct 22 15:56:40 midgard kernel: [516468.781463] CPU: 2 PID: 928 Comm: Xorg Not tainted 4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u1
Oct 22 15:56:40 midgard kernel: [516468.781463] Hardware name: Dell Inc. Latitude 5500/0M14W7, BIOS 1.0.1 04/09/2019
Oct 22 15:56:40 midgard kernel: [516468.781491] RIP: 0010:intel_atomic_commit_tail+0xcc9/0xd40 [i915]
Oct 22 15:56:40 midgard kernel: [516468.781492] Code: 0e 00 00 8d 71 41 48 c7 c7 50 c6 b2 c0 75 6c e8 3d 9b dc ff e9 7c fb ff ff e8 5d e4 fd e3 0f 0b e9 7c fd ff ff e8 51 e4 fd e3 <0f> 0b e9 44 fa ff ff e8 45 e4 fd e3 0f 0b 0f b6 44 24 18 e9 76 f9
Oct 22 15:56:40 midgard kernel: [516468.781492] RSP: 0018:ffffbd8e022cbba0 EFLAGS: 00010286
Oct 22 15:56:40 midgard kernel: [516468.781493] RAX: 0000000000000000 RBX: ffff9c049f147000 RCX: 0000000000000006
Oct 22 15:56:40 midgard kernel: [516468.781494] RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff9c04ac2966b0
Oct 22 15:56:40 midgard kernel: [516468.781495] RBP: ffff9c03cb303000 R08: 000000000000064f R09: 0000000000000004
Oct 22 15:56:40 midgard kernel: [516468.781495] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9c03cb304000
Oct 22 15:56:40 midgard kernel: [516468.781495] R13: ffff9c03cb302800 R14: ffff9c04a0a48368 R15: ffff9c04a0a48370
Oct 22 15:56:40 midgard kernel: [516468.781496] FS:  00007fb344e35f00(0000) GS:ffff9c04ac280000(0000) knlGS:0000000000000000
Oct 22 15:56:40 midgard kernel: [516468.781497] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 22 15:56:40 midgard kernel: [516468.781497] CR2: 0000129866496000 CR3: 000000045f332002 CR4: 00000000003606e0
Oct 22 15:56:40 midgard kernel: [516468.781498] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 22 15:56:40 midgard kernel: [516468.781498] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 22 15:56:40 midgard kernel: [516468.781499] Call Trace:
Oct 22 15:56:40 midgard kernel: [516468.781516]  intel_atomic_commit+0x2a7/0x2e0 [i915]
Oct 22 15:56:40 midgard kernel: [516468.781528]  drm_mode_atomic_ioctl+0x81a/0x940 [drm]
Oct 22 15:56:40 midgard kernel: [516468.781537]  ? drm_atomic_set_property+0x690/0x690 [drm]
Oct 22 15:56:40 midgard kernel: [516468.781543]  drm_ioctl_kernel+0xa1/0xf0 [drm]
Oct 22 15:56:40 midgard kernel: [516468.781550]  drm_ioctl+0x205/0x3a0 [drm]
Oct 22 15:56:40 midgard kernel: [516468.781558]  ? drm_atomic_set_property+0x690/0x690 [drm]
Oct 22 15:56:40 midgard kernel: [516468.781561]  ? __switch_to_asm+0x35/0x70
Oct 22 15:56:40 midgard kernel: [516468.781562]  ? __switch_to_asm+0x41/0x70
Oct 22 15:56:40 midgard kernel: [516468.781563]  ? __switch_to_asm+0x35/0x70
Oct 22 15:56:40 midgard kernel: [516468.781565]  ? __switch_to_asm+0x41/0x70
Oct 22 15:56:40 midgard kernel: [516468.781566]  ? __switch_to_asm+0x35/0x70
Oct 22 15:56:40 midgard kernel: [516468.781567]  ? __switch_to_asm+0x41/0x70
Oct 22 15:56:40 midgard kernel: [516468.781568]  ? __switch_to_asm+0x35/0x70
Oct 22 15:56:40 midgard kernel: [516468.781569]  ? __switch_to_asm+0x41/0x70
Oct 22 15:56:40 midgard kernel: [516468.781570]  ? __switch_to_asm+0x35/0x70
Oct 22 15:56:40 midgard kernel: [516468.781573]  do_vfs_ioctl+0xa4/0x630
Oct 22 15:56:40 midgard kernel: [516468.781574]  ? __schedule+0x2aa/0x870
Oct 22 15:56:40 midgard kernel: [516468.781575]  ? vfs_read+0x119/0x140
Oct 22 15:56:40 midgard kernel: [516468.781577]  ksys_ioctl+0x60/0x90
Oct 22 15:56:40 midgard kernel: [516468.781578]  __x64_sys_ioctl+0x16/0x20
Oct 22 15:56:40 midgard kernel: [516468.781580]  do_syscall_64+0x53/0x110
Oct 22 15:56:40 midgard kernel: [516468.781582]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Oct 22 15:56:40 midgard kernel: [516468.781583] RIP: 0033:0x7fb345565427
Oct 22 15:56:40 midgard kernel: [516468.781584] Code: 00 00 90 48 8b 05 69 aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 aa 0c 00 f7 d8 64 89 01 48
Oct 22 15:56:40 midgard kernel: [516468.781585] RSP: 002b:00007ffc26e6d1c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Oct 22 15:56:40 midgard kernel: [516468.781586] RAX: ffffffffffffffda RBX: 0000556f7bac5300 RCX: 00007fb345565427
Oct 22 15:56:40 midgard kernel: [516468.781586] RDX: 00007ffc26e6d210 RSI: 00000000c03864bc RDI: 000000000000000e
Oct 22 15:56:40 midgard kernel: [516468.781587] RBP: 00007ffc26e6d210 R08: 0000556f7bac4cb0 R09: 0000000000000002
Oct 22 15:56:40 midgard kernel: [516468.781587] R10: 0000000000000002 R11: 0000000000000246 R12: 00000000c03864bc
Oct 22 15:56:40 midgard kernel: [516468.781588] R13: 000000000000000e R14: 0000000000000000 R15: 0000556f7bac4de0
Oct 22 15:56:40 midgard kernel: [516468.781589] ---[ end trace 46b67cc3a8b0f04b ]---
Oct 22 15:58:37 midgard kernel: [516585.249684] ------------[ cut here ]------------

Nothing interesting before that in dmesg, a bit more relevant trace right after.

Oct 22 15:58:37 midgard kernel: [516585.249684] vblank wait timed out on crtc 2
Oct 22 15:58:37 midgard kernel: [516585.249719] WARNING: CPU: 3 PID: 928 at drivers/gpu/drm/drm_vblank.c:1084 drm_wait_one_vblank+0x15a/0x170 [drm]
Oct 22 15:58:37 midgard kernel: [516585.249720] Modules linked in: ctr ccm rfcomm cmac arc4 snd_hda_codec_hdmi bnep intel_rapl binfmt_misc x86_pkg_temp_thermal intel_powerclamp mei_wdt coretemp dell_rbtn nls_ascii nls_cp437 kvm_intel vfat fat snd_soc_skl kvm snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core irqbypass crct10dif_pclmul snd_hda_codec_realtek iwlmvm dell_wmi crc32_pclmul dell_laptop btusb snd_hda_codec_generic snd_compress btrtl btbcm ghash_clmulni_intel dell_smbios dcdbas btintel efi_pstore mac80211 dell_wmi_descriptor intel_cstate wmi_bmof serio_raw joydev bluetooth snd_hda_intel dell_smm_hwmon snd_hda_codec snd_usb_audio uvcvideo intel_uncore snd_hda_core snd_usbmidi_lib iwlwifi snd_hwdep intel_rapl_perf snd_rawmidi videobuf2_vmalloc videobuf2_memops
Oct 22 15:58:37 midgard kernel: [516585.249739]  snd_seq_device videobuf2_v4l2 videobuf2_common snd_pcm cdc_ether videodev usbnet snd_timer rtsx_pci_ms r8152 media snd iTCO_wdt tpm_crb mii efivars drbg iTCO_vendor_support pcc_cpufreq memstick cfg80211 pcspkr soundcore ansi_cprng mei_me tpm_tis tpm_tis_core squashfs mei ecdh_generic tpm hid_multitouch ucsi_acpi idma64 rng_core rfkill zstd_decompress typec_ucsi processor_thermal_device xxhash typec intel_soc_dts_iosf intel_pch_thermal battery evdev int3403_thermal int340x_thermal_zone dell_smo8800 int3400_thermal intel_hid ac acpi_thermal_rel sparse_keymap acpi_pad dptf_power loop parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb hid_logitech_hidpp hid_logitech_dj usbhid hid_generic i915 crc32c_intel rtsx_pci_sdmmc mmc_core
Oct 22 15:58:37 midgard kernel: [516585.249760]  i2c_algo_bit drm_kms_helper psmouse nvme xhci_pci drm xhci_hcd aesni_intel rtsx_pci aes_x86_64 e1000e crypto_simd cryptd usbcore glue_helper thunderbolt nvme_core i2c_i801 i2c_hid intel_lpss_pci intel_lpss hid usb_common wmi thermal button video
Oct 22 15:58:37 midgard kernel: [516585.249769] CPU: 3 PID: 928 Comm: Xorg Tainted: G        W         4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u1
Oct 22 15:58:37 midgard kernel: [516585.249769] Hardware name: Dell Inc. Latitude 5500/0M14W7, BIOS 1.0.1 04/09/2019
Oct 22 15:58:37 midgard kernel: [516585.249776] RIP: 0010:drm_wait_one_vblank+0x15a/0x170 [drm]
Oct 22 15:58:37 midgard kernel: [516585.249777] Code: e4 0f 0b e9 39 ff ff ff 48 89 e6 4c 89 f7 e8 fd af 25 e4 45 85 e4 0f 85 1b ff ff ff 89 ee 48 c7 c7 b8 c8 88 c0 e8 60 25 21 e4 <0f> 0b e9 06 ff ff ff e8 4a 22 21 e4 66 2e 0f 1f 84 00 00 00 00 00
Oct 22 15:58:37 midgard kernel: [516585.249777] RSP: 0018:ffffbd8e022cbab8 EFLAGS: 00010286
Oct 22 15:58:37 midgard kernel: [516585.249778] RAX: 0000000000000000 RBX: ffff9c04a0a48000 RCX: 0000000000000006
Oct 22 15:58:37 midgard kernel: [516585.249779] RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffff9c04ac2d66b0
Oct 22 15:58:37 midgard kernel: [516585.249779] RBP: 0000000000000002 R08: 0000000000000685 R09: 0000000000000004
Oct 22 15:58:37 midgard kernel: [516585.249780] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
Oct 22 15:58:37 midgard kernel: [516585.249780] R13: 00000000009ec2a9 R14: ffff9c049f1402e8 R15: ffff9c03da2c3000
Oct 22 15:58:37 midgard kernel: [516585.249781] FS:  00007fb344e35f00(0000) GS:ffff9c04ac2c0000(0000) knlGS:0000000000000000
Oct 22 15:58:37 midgard kernel: [516585.249782] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 22 15:58:37 midgard kernel: [516585.249782] CR2: 00007f79bd9d3e5c CR3: 000000045f332006 CR4: 00000000003606e0
Oct 22 15:58:37 midgard kernel: [516585.249782] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 22 15:58:37 midgard kernel: [516585.249783] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 22 15:58:37 midgard kernel: [516585.249783] Call Trace:
Oct 22 15:58:37 midgard kernel: [516585.249788]  ? finish_wait+0x80/0x80
Oct 22 15:58:37 midgard kernel: [516585.249802]  skl_update_crtcs+0x1e5/0x320 [i915]
Oct 22 15:58:37 midgard kernel: [516585.249804]  ? complete+0x21/0x50
Oct 22 15:58:37 midgard kernel: [516585.249818]  intel_atomic_commit_tail+0x35d/0xd40 [i915]
Oct 22 15:58:37 midgard kernel: [516585.249831]  intel_atomic_commit+0x2a7/0x2e0 [i915]
Oct 22 15:58:37 midgard kernel: [516585.249839]  drm_mode_atomic_ioctl+0x81a/0x940 [drm]
Oct 22 15:58:37 midgard kernel: [516585.249846]  ? drm_atomic_set_property+0x690/0x690 [drm]
Oct 22 15:58:37 midgard kernel: [516585.249852]  drm_ioctl_kernel+0xa1/0xf0 [drm]
Oct 22 15:58:37 midgard kernel: [516585.249858]  drm_ioctl+0x205/0x3a0 [drm]
Oct 22 15:58:37 midgard kernel: [516585.249865]  ? drm_atomic_set_property+0x690/0x690 [drm]
Oct 22 15:58:37 midgard kernel: [516585.249867]  ? __switch_to_asm+0x35/0x70
Oct 22 15:58:37 midgard kernel: [516585.249868]  ? __switch_to_asm+0x41/0x70
Oct 22 15:58:37 midgard kernel: [516585.249869]  ? __switch_to_asm+0x35/0x70
Oct 22 15:58:37 midgard kernel: [516585.249870]  ? __switch_to_asm+0x41/0x70
Oct 22 15:58:37 midgard kernel: [516585.249871]  ? __switch_to_asm+0x35/0x70
Oct 22 15:58:37 midgard kernel: [516585.249872]  ? __switch_to_asm+0x41/0x70
Oct 22 15:58:37 midgard kernel: [516585.249873]  ? __switch_to_asm+0x35/0x70
Oct 22 15:58:37 midgard kernel: [516585.249874]  ? __switch_to_asm+0x41/0x70
Oct 22 15:58:37 midgard kernel: [516585.249875]  ? __switch_to_asm+0x35/0x70
Oct 22 15:58:37 midgard kernel: [516585.249876]  do_vfs_ioctl+0xa4/0x630
Oct 22 15:58:37 midgard kernel: [516585.249878]  ? __schedule+0x2aa/0x870
Oct 22 15:58:37 midgard kernel: [516585.249879]  ksys_ioctl+0x60/0x90
Oct 22 15:58:37 midgard kernel: [516585.249880]  __x64_sys_ioctl+0x16/0x20
Oct 22 15:58:37 midgard kernel: [516585.249882]  do_syscall_64+0x53/0x110
Oct 22 15:58:37 midgard kernel: [516585.249883]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Oct 22 15:58:37 midgard kernel: [516585.249885] RIP: 0033:0x7fb345565427
Oct 22 15:58:37 midgard kernel: [516585.249885] Code: 00 00 90 48 8b 05 69 aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 aa 0c 00 f7 d8 64 89 01 48
Oct 22 15:58:37 midgard kernel: [516585.249886] RSP: 002b:00007ffc26e6dcb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Oct 22 15:58:37 midgard kernel: [516585.249887] RAX: ffffffffffffffda RBX: 0000556f7abbc9f0 RCX: 00007fb345565427
Oct 22 15:58:37 midgard kernel: [516585.249887] RDX: 00007ffc26e6dd00 RSI: 00000000c03864bc RDI: 000000000000000e
Oct 22 15:58:37 midgard kernel: [516585.249888] RBP: 00007ffc26e6dd00 R08: 0000556f7a6741a0 R09: 0000000000000001
Oct 22 15:58:37 midgard kernel: [516585.249888] R10: 0000000000000001 R11: 0000000000000246 R12: 00000000c03864bc
Oct 22 15:58:37 midgard kernel: [516585.249888] R13: 000000000000000e R14: 0000000000000000 R15: 0000556f7b643b30
Oct 22 15:58:37 midgard kernel: [516585.249889] ---[ end trace 46b67cc3a8b0f04c ]---

I'm running a fairly standard Debian 10, kernel is 4.19.0-6-amd64, xorg-server version is xorg-server 2:1.20.4-1, xserver-xorg-video-intel is 2.99.917+git20180925-2.

I do not have a reliable way of reproducing the error, and it is rare, occurs once in three weeks or so. Seems very similar to #107625 from what I can see.
Comment 1 Ville Syrjala 2019-10-22 20:01:12 UTC
(In reply to Daniels Umanovskis from comment #0)
> I have a Dell Latitude 5500 connected through a docking station to two
> external screens. Occasionally, when they're in power saving mode and I wake
> the laptop, one of the screens fails to come back up. There's a 'pipe state
> doesn't match' error in dmesg at the corresponding time.
> 
> Oct 22 15:56:40 midgard kernel: [516468.781351] ------------[ cut here
> ]------------
> Oct 22 15:56:40 midgard kernel: [516468.781352] pipe state doesn't match!

The interesting details of what actually doesn't match should be in the log just before this.

Oh and please attach logs. The formatting goes down the toilet when copy pasting directly into a bugzilla comment.
Comment 2 Daniels Umanovskis 2019-10-23 09:24:15 UTC
Created attachment 145797 [details]
dmesg at crash
Comment 3 Daniels Umanovskis 2019-10-23 09:35:47 UTC
Previous attachment is the original log.

There's unfortunately nothing interesting in the log before this, the previous message is from 12 minutes before the crash, attaching that excerpt anyway. It's messages from the NetworkManager, and it matches what I was doing - some networking stuff, then I took a break long enough for the screen timeout to kick in (10 minutes) and got the crash when I came back.
Comment 4 Daniels Umanovskis 2019-10-23 09:36:08 UTC
Created attachment 145798 [details]
dmesg before the crash
Comment 5 Lakshmi 2019-10-24 07:48:10 UTC
(In reply to Daniels Umanovskis from comment #4)
> Created attachment 145798 [details]
> dmesg before the crash

Can you please attach the full dmesg with kernel parameters drm.debug=0x1e log_buf_len=4M?
Comment 6 Daniels Umanovskis 2019-10-24 08:04:42 UTC
Ok, I've updated the kernel parameters on the machine accordingly. I'll update this bug when the problem happens again, which will probably take a couple of weeks.
Comment 7 jelrein 2019-11-10 08:21:53 UTC
Don't you know that with the help of this writing service you can put behind you all your academic troubles and worries. These professionals will help you 
https://walmartone.me/
Comment 8 Martin Peres 2019-11-29 19:43:25 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/543.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.