Bug#1035071: live-build: unable to boot Macs
I believe this can be closed. It worked for me after setting "--bootloaders syslinux,grub-efi". -- Confidentiality Notice: The material transmitted herein is intended only for the use of the addressee and may contain information that constitutes work product or is confidential and exempt from disclosure under applicable law. Distribution or copying of this communication or reliance upon its contents by unauthorized participants is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone or email.
Bug#1035068: linux-image-6.1.0-7-amd64: occasionally no trackpad/trackpoint on resume from hibernate
I think this can be closed. Looking good without the systemd script. On Mon, May 1, 2023 at 4:29 PM Diederik de Haas wrote: > On Monday, 1 May 2023 20:40:11 CEST Rusty Grove wrote: > > The script is something I did > > Can you test without that script then? > IMO the proper way to deal with suspend/resume should be done by the > system/ > kernel and it *could* be that your script is actually interfering with > that. > > > I'm not quite sure what you mean by the sequence being in reverse... > > if you do in pre: > unload A > unload B > > Then you should do in post: > load B > load A > > but your script did > load A > load B > > HTH -- Confidentiality Notice: The material transmitted herein is intended only for the use of the addressee and may contain information that constitutes work product or is confidential and exempt from disclosure under applicable law. Distribution or copying of this communication or reliance upon its contents by unauthorized participants is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone or email.
Bug#1035068: linux-image-6.1.0-7-amd64: occasionally no trackpad/trackpoint on resume from hibernate
Package: src:linux Version: 6.1.25-1 Followup-For: Bug #1035068 X-Debbugs-Cc: rgr...@rsu20.org I get mixed results in removing the systemd script. The trackpad looks good on multiple resumes, but I've lost the trackpoint on both of my test machines, the other running linux-image-6.1.0-7-amd64. Thanks -- Package-specific info: ** Version: Linux version 6.1.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.25-1 (2023-04-22) ** Command line: root=LABEL=root rw quiet splash loglevel=1 rootfstype=btrfs add_efi_memmap workqueue.power_efficient=true initrd=\EFI\Debian\initrd.img ** Not tainted ** Kernel log: [179995.203190] elan_i2c 14-0015: failed to read report data: -71 [179995.216999] elan_i2c 14-0015: failed to read report data: -71 [179995.223936] elan_i2c 14-0015: failed to read report data: -71 [179995.238153] elan_i2c 14-0015: failed to read report data: -71 [179995.244699] elan_i2c 14-0015: failed to read report data: -71 [179995.258890] elan_i2c 14-0015: failed to read report data: -71 [179995.265548] elan_i2c 14-0015: failed to read report data: -71 [179995.270830] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [179995.285774] wlp0s20f3: Limiting TX power to 36 (36 - 0) dBm as advertised by c8:b5:ad:5f:f9:f5 [179995.292975] elan_i2c 14-0015: failed to read report data: -71 [179995.307069] elan_i2c 14-0015: failed to read report data: -71 [179995.729556] elan_i2c 14-0015: failed to read report data: -71 [179995.874426] elan_i2c 14-0015: failed to read report data: -71 [179995.901949] elan_i2c 14-0015: failed to read report data: -71 [179996.033861] elan_i2c 14-0015: failed to read report data: -71 [17.723244] elan_i2c 14-0015: failed to read report data: -71 [17.737332] elan_i2c 14-0015: failed to read report data: -71 [17.744196] elan_i2c 14-0015: failed to read report data: -71 [17.751903] elan_i2c 14-0015: failed to read report data: -71 [17.771699] elan_i2c 14-0015: failed to read report data: -71 [180003.960083] elan_i2c 14-0015: failed to read report data: -71 [180003.994728] elan_i2c 14-0015: failed to read report data: -71 [180004.029347] elan_i2c 14-0015: failed to read report data: -71 [180004.063917] elan_i2c 14-0015: failed to read report data: -71 [180004.223466] elan_i2c 14-0015: failed to read report data: -71 [180004.230065] elan_i2c 14-0015: failed to read report data: -71 [180004.237131] elan_i2c 14-0015: failed to read report data: -71 [180004.250980] elan_i2c 14-0015: failed to read report data: -71 [180004.257827] elan_i2c 14-0015: failed to read report data: -71 [180004.271878] elan_i2c 14-0015: failed to read report data: -71 [180004.279561] elan_i2c 14-0015: failed to read report data: -71 [180004.286533] elan_i2c 14-0015: failed to read report data: -71 [180004.300450] elan_i2c 14-0015: failed to read report data: -71 [180004.307244] elan_i2c 14-0015: failed to read report data: -71 [180004.321301] elan_i2c 14-0015: failed to read report data: -71 [180004.328015] elan_i2c 14-0015: failed to read report data: -71 [180004.342220] elan_i2c 14-0015: failed to read report data: -71 [180004.348783] elan_i2c 14-0015: failed to read report data: -71 [180004.355784] elan_i2c 14-0015: failed to read report data: -71 [180004.369854] elan_i2c 14-0015: failed to read report data: -71 [180004.376599] elan_i2c 14-0015: failed to read report data: -71 [180004.390575] elan_i2c 14-0015: failed to read report data: -71 [180004.397392] elan_i2c 14-0015: failed to read report data: -71 [180004.404876] elan_i2c 14-0015: failed to read report data: -71 [180004.438931] elan_i2c 14-0015: failed to read report data: -71 [180004.445696] elan_i2c 14-0015: failed to read report data: -71 [180004.459539] elan_i2c 14-0015: failed to read report data: -71 [180004.487179] elan_i2c 14-0015: failed to read report data: -71 [180004.494323] elan_i2c 14-0015: failed to read report data: -71 [180004.508116] elan_i2c 14-0015: failed to read report data: -71 [180004.514950] elan_i2c 14-0015: failed to read report data: -71 [180004.528986] elan_i2c 14-0015: failed to read report data: -71 [180004.535680] elan_i2c 14-0015: failed to read report data: -71 [180004.549791] elan_i2c 14-0015: failed to read report data: -71 [180004.556494] elan_i2c 14-0015: failed to read report data: -71 [180004.563459] elan_i2c 14-0015: failed to read report data: -71 [180004.577342] elan_i2c 14-0015: failed to read report data: -71 [180004.584190] elan_i2c 14-0015: failed to read report data: -71 [180004.598268] elan_i2c 14-0015: failed to read report data: -71 [180004.604940] elan_i2c 14-0015: failed to read report data: -71 [180004.619025] elan_i2c 14-0015: failed to read report data: -71 [180004.625772] elan_i2c 14-0015: failed to read report data: -71 [180004.632765] elan_i2c 14-0015: failed to read report data: -71 [180004.646608] elan_i2c 14-0015: failed to read report data: -71
Bug#1035068: linux-image-6.1.0-7-amd64: occasionally no trackpad/trackpoint on resume from hibernate
Package: src:linux Version: 6.1.25-1 Followup-For: Bug #1035068 X-Debbugs-Cc: rgr...@rsu20.org Dear Maintainer, I have a couple of L13s I'm testing on. This one has the kernel from unstable. On resume from suspend (didn't reach hibernate), I have no trackpad/trackpoint this morning (systemd script still enabled). This report was done with neither trackpad/trackpoint working. I'll ditch the systemd script on both laptops and see how it goes. Thanks -- Package-specific info: ** Version: Linux version 6.1.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.25-1 (2023-04-22) ** Command line: root=LABEL=root rw quiet splash loglevel=1 rootfstype=btrfs add_efi_memmap workqueue.power_efficient=true initrd=\EFI\Debian\initrd.img ** Tainted: W (512) * kernel issued warning ** Kernel log: [63563.260556] PM: suspend entry (s2idle) [63563.277311] Filesystems sync: 0.016 seconds [63563.278079] Freezing user space processes [63563.279850] Freezing user space processes completed (elapsed 0.001 seconds) [63563.279854] OOM killer disabled. [63563.279856] Freezing remaining freezable tasks [63563.281092] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [63563.281096] printk: Suspending console(s) (use no_console_suspend to debug) [63563.342135] e1000e: EEE TX LPI TIMER: 0011 [63563.527367] ACPI: EC: interrupt blocked [67161.893202] ACPI: EC: interrupt unblocked [67162.417240] nvme nvme0: Shutdown timeout set to 8 seconds [67162.427479] nvme nvme0: 8/0/0 default/read/poll queues [67162.913674] OOM killer enabled. [67162.913679] Restarting tasks ... [67162.913678] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [67162.919662] done. [67162.919715] random: crng reseeded on system resumption [67162.929518] PM: suspend exit [67163.536574] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [67163.549626] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x0d. [67163.563027] psmouse serio1: elantech: Elan sample query result 00, 0d, a7 [67163.576056] psmouse serio1: elantech: Elan ic body: 0x11, current fw version: 0x4 [67163.656316] psmouse serio1: elantech: Trying to set up SMBus access [67163.663757] elan_i2c 14-0015: supply vcc not found, using dummy regulator [67163.673141] elan_i2c 14-0015: Elan Touchpad: Module ID: 0x000d, Firmware: 0x0001, Sample: 0x, IAP: 0x [67163.673442] input: Elan Touchpad as /devices/pci:00/:00:1f.4/i2c-14/14-0015/input/input248 [67163.673824] input: Elan TrackPoint as /devices/pci:00/:00:1f.4/i2c-14/14-0015/input/input249 [67164.070142] [ cut here ] [67164.070147] kernfs: can not remove '14-0015', no directory [67164.070157] WARNING: CPU: 7 PID: 22175 at fs/kernfs/dir.c:1625 kernfs_remove_by_name_ns+0xba/0xc0 [67164.070168] Modules linked in: elan_i2c psmouse(-) ctr ccm rfcomm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_seq snd_seq_device bnep btusb btrtl btbcm btintel btmtk bluetooth uvcvideo jitterentropy_rng wacom videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 drbg videobuf2_common ansi_cprng usbhid videodev ecdh_generic ecc crc16 mc qrtr binfmt_misc hid_sensor_accel_3d hid_sensor_trigger hid_sensor_iio_common nls_ascii industrialio_triggered_buffer kfifo_buf nls_cp437 squashfs industrialio vfat fat hid_sensor_custom hid_sensor_hub hid_generic intel_ishtp_hid hid x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_sof_pci_intel_tgl snd_hda_codec_hdmi iwlmvm snd_sof_intel_hda_common kvm soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp irqbypass crc32_pclmul mac80211 snd_sof snd_ctl_led snd_sof_utils ghash_clmulni_intel snd_soc_hdac_hda snd_hda_codec_realtek snd_hda_ext_core [67164.070255] snd_soc_acpi_intel_match sha512_ssse3 snd_soc_acpi sha512_generic snd_hda_codec_generic snd_soc_core snd_compress soundwire_bus libarc4 snd_hda_intel iwlwifi snd_intel_dspcfg aesni_intel snd_intel_sdw_acpi snd_hda_codec crypto_simd cryptd thinkpad_acpi snd_hda_core mei_hdcp rtsx_pci_sdmmc iTCO_wdt intel_pmc_bxt xhci_pci snd_hwdep rapl nvram iTCO_vendor_support mmc_core watchdog xhci_hcd mei_me snd_pcm intel_ish_ipc e1000e platform_profile i2c_i801 intel_cstate processor_thermal_device_pci_legacy cfg80211 intel_rapl_msr usbcore snd_timer pcspkr processor_thermal_device ledtrig_audio thunderbolt think_lmi ptp mei i2c_smbus snd processor_thermal_rfim firmware_attributes_class wmi_bmof rtsx_pci processor_thermal_mbox pps_core ucsi_acpi processor_thermal_rapl typec_ucsi roles intel_rapl_common intel_ishtp intel_uncore usb_common intel_soc_dts_iosf typec igen6_edac soundcore rfkill battery int3403_thermal int340x_thermal_zone ac soc_button_array intel_pmc_core int3400_thermal
Bug#1035068: linux-image-6.1.0-7-amd64: occasionally no trackpad/trackpoint on resume from hibernate
Thanks. I've installed 6.1.25-1 and will do further testing. The script is something I did, which in my (adminitingly unscientific) testing, seemed to work well with occasional cases of no trackpad/trackpoint input. I'm not quite sure what you mean by the sequence being in reverse... my thought was to remove the module before going to suspend and then load it again after resume. You're right, it's probably safe to remove the entry to load elan_i2c, as psmouse should pull it in. Not sure why I have it in there. On Fri, Apr 28, 2023 at 4:07 PM Diederik de Haas wrote: > Control: tag -1 moreinfo > > On Friday, 28 April 2023 20:15:46 CEST Harold Grove wrote: > > Package: src:linux > > Version: 6.1.20-2 > > Unstable now has version 6.1.25-1, could you try that? > > > I'm also seeing a possibly related kernel oops when unloading the psmouse > > module. The module is being unloaded via a script under > > /lib/systemd/system-sleep/ which contains: > > #!/bin/sh > > # Reload the trackpoint and trackpad drivers on L13 Yoga Gen 2 > > case $1 in > > pre) > > rmmod psmouse; > > sleep 1; > > rmmod elan_i2c; > > ;; > > post) > > modprobe psmouse; > > sleep 1; > > modprobe elan_i2c; > > ;; > > esac > > Did you create that yourself or is that some a package? > In any case, the sequence seems odd to me as I'd expect the 'post' > sequence to > be the reverse of the 'pre' sequence, thus first `modprobe elan_i2c` and > then > `modprobe psmouse`. > Also, if `psmouse` needs `elan_i2c` it should trigger the loading by > itself. -- Confidentiality Notice: The material transmitted herein is intended only for the use of the addressee and may contain information that constitutes work product or is confidential and exempt from disclosure under applicable law. Distribution or copying of this communication or reliance upon its contents by unauthorized participants is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone or email.
