[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-osp1 (Ubuntu Focal) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Changed in: linux-oem-osp1 (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
This bug was fixed in the package linux - 5.4.0-18.22 --- linux (5.4.0-18.22) focal; urgency=medium * focal/linux: 5.4.0-18.22 -proposed tracker (LP: #1866488) * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts * Add sysfs attribute to show remapped NVMe (LP: #1863621) - SAUCE: ata: ahci: Add sysfs attribute to show remapped NVMe device count * [20.04 FEAT] Compression improvements in Linux kernel (LP: #1830208) - lib/zlib: add s390 hardware support for kernel zlib_deflate - s390/boot: rename HEAP_SIZE due to name collision - lib/zlib: add s390 hardware support for kernel zlib_inflate - s390/boot: add dfltcc= kernel command line parameter - lib/zlib: add zlib_deflate_dfltcc_enabled() function - btrfs: use larger zlib buffer for s390 hardware compression - [Config] Introducing s390x specific kernel config option CONFIG_ZLIB_DFLTCC * [UBUNTU 20.04] s390x/pci: increase CONFIG_PCI_NR_FUNCTIONS to 512 in kernel config (LP: #1866056) - [Config] Increase CONFIG_PCI_NR_FUNCTIONS from 64 to 512 starting with focal on s390x * CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set (LP: #1865332) - [Config] CONFIG_IP_MROUTE_MULTIPLE_TABLES=y * Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware (LP: #1865962) - iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560 - iwlwifi: 22000: fix some indentation - iwlwifi: pcie: rx: use rxq queue_size instead of constant - iwlwifi: allocate more receive buffers for HE devices - iwlwifi: remove some outdated iwl22000 configurations - iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg * [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled (LP: #1861521) - Revert "USUNTU: SAUCE: drm/i915: Force DPCD backlight mode on Dell Precision 4K sku" - Revert "UBUNTU: SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel" - SAUCE: drm/dp: Introduce EDID-based quirks - SAUCE: drm/i915: Force DPCD backlight mode on X1 Extreme 2nd Gen 4K AMOLED panel - SAUCE: drm/i915: Force DPCD backlight mode for some Dell CML 2020 panels * [20.04 FEAT] Enable proper kprobes on ftrace support (LP: #1865858) - s390/ftrace: save traced function caller - s390: support KPROBES_ON_FTRACE * alsa/sof: load different firmware on different platforms (LP: #1857409) - ASoC: SOF: Intel: hda: use fallback for firmware name - ASoC: Intel: acpi-match: split CNL tables in three - ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names. * [UBUNTU 20.04] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal (LP: #1865452) - [Config] Enable CONFIG_NET_SWITCHDEV in kernel config for s390x starting with focal * Focal update: v5.4.24 upstream stable release (LP: #1866333) - io_uring: grab ->fs as part of async offload - EDAC: skx_common: downgrade message importance on missing PCI device - net: dsa: b53: Ensure the default VID is untagged - net: fib_rules: Correctly set table field when table number exceeds 8 bits - net: macb: ensure interface is not suspended on at91rm9200 - net: mscc: fix in frame extraction - net: phy: restore mdio regs in the iproc mdio driver - net: sched: correct flower port blocking - net/tls: Fix to avoid gettig invalid tls record - nfc: pn544: Fix occasional HW initialization failure - qede: Fix race between rdma destroy workqueue and link change event - Revert "net: dev: introduce support for sch BYPASS for lockless qdisc" - udp: rehash on disconnect - sctp: move the format error check out of __sctp_sf_do_9_1_abort - bnxt_en: Improve device shutdown method. - bnxt_en: Issue PCIe FLR in kdump kernel to cleanup pending DMAs. - bonding: add missing netdev_update_lockdep_key() - net: export netdev_next_lower_dev_rcu() - bonding: fix lockdep warning in bond_get_stats() - ipv6: Fix route replacement with dev-only route - ipv6: Fix nlmsg_flags when splitting a multipath route - ipmi:ssif: Handle a possible NULL pointer reference - drm/msm: Set dma maximum segment size for mdss - sched/core: Don't skip remote tick for idle CPUs - timers/nohz: Update NOHZ load in remote tick - sched/fair: Prevent unlimited runtime on throttled group - dax: pass NOWAIT flag to iomap_apply - mac80211: consider more elements in parsing CRC - cfg80211: check wiphy driver existence for drvinfo report - s390/zcrypt: fix card and queue total counter wrap - qmi_wwan: re-add DW5821e pre-production variant - qmi_wwan: unconditionally reject 2 ep interfaces - NFSv4: Fix races between open and dentry revalidation - perf/smmuv3: Use platform_get_irq_optional() for wired interrupt - perf/x86/intel: Add Elkhart Lake support - perf/x86/cstate: Add Tremont
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
This bug was fixed in the package linux - 4.15.0-88.88 --- linux (4.15.0-88.88) bionic; urgency=medium * bionic/linux: 4.15.0-88.88 -proposed tracker (LP: #1862824) * Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel (LP: #1862312) - Revert "mm/memory_hotplug: fix online/offline_pages called w.o. mem_hotplug_lock" - mm/memory_hotplug: fix online/offline_pages called w.o. mem_hotplug_lock linux (4.15.0-87.87) bionic; urgency=medium * bionic/linux: 4.15.0-87.87 -proposed tracker (LP: #1861165) * Bionic update: upstream stable patchset 2020-01-22 (LP: #1860602) - scsi: lpfc: Fix discovery failures when target device connectivity bounces - scsi: mpt3sas: Fix clear pending bit in ioctl status - scsi: lpfc: Fix locking on mailbox command completion - Input: atmel_mxt_ts - disable IRQ across suspend - iommu/tegra-smmu: Fix page tables in > 4 GiB memory - scsi: target: compare full CHAP_A Algorithm strings - scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices - scsi: csiostor: Don't enable IRQs too early - powerpc/pseries: Mark accumulate_stolen_time() as notrace - powerpc/pseries: Don't fail hash page table insert for bolted mapping - powerpc/tools: Don't quote $objdump in scripts - dma-debug: add a schedule point in debug_dma_dump_mappings() - clocksource/drivers/asm9260: Add a check for of_clk_get - powerpc/security/book3s64: Report L1TF status in sysfs - powerpc/book3s64/hash: Add cond_resched to avoid soft lockup warning - ext4: update direct I/O read lock pattern for IOCB_NOWAIT - jbd2: Fix statistics for the number of logged blocks - scsi: tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6) - scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow - f2fs: fix to update dir's i_pino during cross_rename - clk: qcom: Allow constant ratio freq tables for rcg - irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary - irqchip: ingenic: Error out if IRQ domain creation failed - fs/quota: handle overflows of sysctl fs.quota.* and report as unsigned long - scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences - scsi: ufs: fix potential bug which ends in system hang - powerpc/pseries/cmm: Implement release() function for sysfs device - powerpc/security: Fix wrong message when RFI Flush is disable - scsi: atari_scsi: sun3_scsi: Set sg_tablesize to 1 instead of SG_NONE - clk: pxa: fix one of the pxa RTC clocks - bcache: at least try to shrink 1 node in bch_mca_scan() - HID: logitech-hidpp: Silence intermittent get_battery_capacity errors - libnvdimm/btt: fix variable 'rc' set but not used - HID: Improve Windows Precision Touchpad detection. - scsi: pm80xx: Fix for SATA device discovery - scsi: ufs: Fix error handing during hibern8 enter - scsi: scsi_debug: num_tgts must be >= 0 - scsi: NCR5380: Add disconnect_mask module parameter - scsi: iscsi: Don't send data to unbound connection - scsi: target: iscsi: Wait for all commands to finish before freeing a session - gpio: mpc8xxx: Don't overwrite default irq_set_type callback - apparmor: fix unsigned len comparison with less than zero - scripts/kallsyms: fix definitely-lost memory leak - cdrom: respect device capabilities during opening action - perf script: Fix brstackinsn for AUXTRACE - perf regs: Make perf_reg_name() return "unknown" instead of NULL - s390/zcrypt: handle new reply code FILTERED_BY_HYPERVISOR - libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h - s390/cpum_sf: Check for SDBT and SDB consistency - ocfs2: fix passing zero to 'PTR_ERR' warning - kernel: sysctl: make drop_caches write-only - userfaultfd: require CAP_SYS_PTRACE for UFFD_FEATURE_EVENT_FORK - x86/mce: Fix possibly incorrect severity calculation on AMD - net, sysctl: Fix compiler warning when only cBPF is present - netfilter: nf_queue: enqueue skbs with NULL dst - ALSA: hda - Downgrade error message for single-cmd fallback - bonding: fix active-backup transition after link failure - perf strbuf: Remove redundant va_end() in strbuf_addv() - Make filldir[64]() verify the directory entry filename is valid - filldir[64]: remove WARN_ON_ONCE() for bad directory entries - netfilter: ebtables: compat: reject all padding in matches/watchers - 6pack,mkiss: fix possible deadlock - netfilter: bridge: make sure to pull arp header in br_nf_forward_arp() - inetpeer: fix data-race in inet_putpeer / inet_putpeer - net: add a READ_ONCE() in skb_peek_tail() - net: icmp: fix data-race in cmp_global_allow() - hrtimer: Annotate lockless access to timer->state - spi: fsl: don't map irq during probe - tty/serial: atmel: fix out of range clock divider handling - pinctrl: baytrail:
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
This bug was fixed in the package linux - 5.3.0-40.32 --- linux (5.3.0-40.32) eoan; urgency=medium * eoan/linux: 5.3.0-40.32 -proposed tracker (LP: #1861214) * No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof (LP: #1860248) - ASoC: SOF: Intel: fix HDA codec driver probe with multiple controllers * ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12) (LP: #1852122) - ocfs2: fix the crash due to call ocfs2_get_dlm_debug once less * QAT drivers for C3XXX and C62X not included as modules (LP: #1845959) - [Config] CRYPTO_DEV_QAT_C3XXX=m, CRYPTO_DEV_QAT_C62X=m and CRYPTO_DEV_QAT_DH895xCC=m * Eoan update: upstream stable patchset 2020-01-24 (LP: #1860816) - scsi: lpfc: Fix discovery failures when target device connectivity bounces - scsi: mpt3sas: Fix clear pending bit in ioctl status - scsi: lpfc: Fix locking on mailbox command completion - Input: atmel_mxt_ts - disable IRQ across suspend - f2fs: fix to update time in lazytime mode - iommu: rockchip: Free domain on .domain_free - iommu/tegra-smmu: Fix page tables in > 4 GiB memory - dmaengine: xilinx_dma: Clear desc_pendingcount in xilinx_dma_reset - scsi: target: compare full CHAP_A Algorithm strings - scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices - scsi: csiostor: Don't enable IRQs too early - scsi: hisi_sas: Replace in_softirq() check in hisi_sas_task_exec() - powerpc/pseries: Mark accumulate_stolen_time() as notrace - powerpc/pseries: Don't fail hash page table insert for bolted mapping - powerpc/tools: Don't quote $objdump in scripts - dma-debug: add a schedule point in debug_dma_dump_mappings() - leds: lm3692x: Handle failure to probe the regulator - clocksource/drivers/asm9260: Add a check for of_clk_get - clocksource/drivers/timer-of: Use unique device name instead of timer - powerpc/security/book3s64: Report L1TF status in sysfs - powerpc/book3s64/hash: Add cond_resched to avoid soft lockup warning - ext4: update direct I/O read lock pattern for IOCB_NOWAIT - ext4: iomap that extends beyond EOF should be marked dirty - jbd2: Fix statistics for the number of logged blocks - scsi: tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6) - scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow - f2fs: fix to update dir's i_pino during cross_rename - clk: qcom: Allow constant ratio freq tables for rcg - clk: clk-gpio: propagate rate change to parent - irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary - irqchip: ingenic: Error out if IRQ domain creation failed - fs/quota: handle overflows of sysctl fs.quota.* and report as unsigned long - scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences - PCI: rpaphp: Fix up pointer to first drc-info entry - scsi: ufs: fix potential bug which ends in system hang - powerpc/pseries/cmm: Implement release() function for sysfs device - PCI: rpaphp: Don't rely on firmware feature to imply drc-info support - PCI: rpaphp: Annotate and correctly byte swap DRC properties - PCI: rpaphp: Correctly match ibm, my-drc-index to drc-name when using drc- info - powerpc/security: Fix wrong message when RFI Flush is disable - scsi: atari_scsi: sun3_scsi: Set sg_tablesize to 1 instead of SG_NONE - clk: pxa: fix one of the pxa RTC clocks - bcache: at least try to shrink 1 node in bch_mca_scan() - HID: quirks: Add quirk for HP MSU1465 PIXART OEM mouse - HID: logitech-hidpp: Silence intermittent get_battery_capacity errors - ARM: 8937/1: spectre-v2: remove Brahma-B53 from hardening - libnvdimm/btt: fix variable 'rc' set but not used - HID: Improve Windows Precision Touchpad detection. - HID: rmi: Check that the RMI_STARTED bit is set before unregistering the RMI transport device - watchdog: Fix the race between the release of watchdog_core_data and cdev - scsi: pm80xx: Fix for SATA device discovery - scsi: ufs: Fix error handing during hibern8 enter - scsi: scsi_debug: num_tgts must be >= 0 - scsi: NCR5380: Add disconnect_mask module parameter - scsi: iscsi: Don't send data to unbound connection - scsi: target: iscsi: Wait for all commands to finish before freeing a session - gpio: mpc8xxx: Don't overwrite default irq_set_type callback - apparmor: fix unsigned len comparison with less than zero - scripts/kallsyms: fix definitely-lost memory leak - powerpc: Don't add -mabi= flags when building with Clang - cdrom: respect device capabilities during opening action - perf script: Fix brstackinsn for AUXTRACE - perf regs: Make perf_reg_name() return "unknown" instead of NULL - s390/zcrypt: handle new reply code FILTERED_BY_HYPERVISOR - libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h -
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1037.42 --- linux-oem-osp1 (5.0.0-1037.42) bionic; urgency=medium * bionic/linux-oem-osp1: 5.0.0-1037.42 -proposed tracker (LP: #1860784) * [Dell Vostro 5490] proposed linux-oem-osp1 suspend resume fails (LP: #1860642) - Revert "ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names." - Revert "ASoC: Intel: acpi-match: split CNL tables in three" - Revert "ASoC: SOF: Intel: hda: use fallback for firmware name" -- Timo Aaltonen Fri, 24 Jan 2020 15:02:03 +0200 ** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1037.42 --- linux-oem-osp1 (5.0.0-1037.42) bionic; urgency=medium * bionic/linux-oem-osp1: 5.0.0-1037.42 -proposed tracker (LP: #1860784) * [Dell Vostro 5490] proposed linux-oem-osp1 suspend resume fails (LP: #1860642) - Revert "ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names." - Revert "ASoC: Intel: acpi-match: split CNL tables in three" - Revert "ASoC: SOF: Intel: hda: use fallback for firmware name" -- Timo Aaltonen Fri, 24 Jan 2020 15:02:03 +0200 ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Changed in: linux (Ubuntu Disco) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1858761 SRU: https://lists.ubuntu.com/archives/kernel-team/2020-January/106727.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Disco) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Tags added: oem-priority originate-from-1850265 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
