Bug#988688: found in recent kernels
found 988688 5.10-158-2 6.1.8-1 thanks Note that the two kernels I've tried so far are built from src:linux-signed-amd64 not src:linux as per this bug; I'm not sure how you folks handle that discrepancy across the BTS. I doubt signing is relevant, I've got secure boot off atm.
Bug#988688: linux-source-5.10: Lenovo ThinkPad Yoga 260 fails to suspend and resume
I have the same problem on the same laptop: Thinkpad 260 Yoga. Machine goes into suspend, but cannot be woken up. I've tried the power button and WOL packets. Fresh install of current Bookworm using debian installer netinst with firmware nightly, from 2022-02-15: 604f09ff97b5faddacff2d43f8710c564d4138d8807d74985f56ab5b76fcdb88 firmware-testing-amd64-netinst.iso minimal install. Kernel is linux-image-6.1.0-3-amd64 (6.1.8-1) On Mon, May 24, 2021 at 08:59:01AM -0400, Kenichiro MATOHARA wrote: $ sudo mount -o remount,sync / $ sync $ logger SUSPEND; systemctl suspend Relevant logs from me doing the same (don't look useful sadly) Feb 16 11:56:53 debian login[841]: ROOT LOGIN on '/dev/tty1' Feb 16 12:00:24 debian kernel: EXT4-fs (dm-1): re-mounted. Quota mode: none. Feb 16 12:00:32 debian root[849]: SUSPEND Feb 16 12:00:32 debian systemd-logind[664]: The system will suspend now! Feb 16 12:00:32 debian systemd[1]: Reached target sleep.target - Sleep. Feb 16 12:00:32 debian systemd[1]: Starting systemd-suspend.service - System Suspend... Feb 16 12:00:32 debian systemd-sleep[851]: Entering sleep state 'suspend'... Feb 16 12:00:32 debian kernel: PM: suspend entry (deep) -- 👱🏻 Jonathan Dowland
help wanted: Pi3 video works w/ upstream build, fails with Debian build
Hi, I'm emailing to seek some advice. In short, when I build a kernel using the Debian package sources, adding CONFIG_FB_SIMPLE and PROC_IKCONFIG, but using the upstream build process from that point onwards, the resulting kernel has working video on a Raspberry Pi 3. If I try to do the same using the Debian kernel build process as outlined in the handbook, then the resulting kernel does NOT have working video on the same hardware. I've really no idea why there is a difference. We've had independent confirmation that building the upstream sources with CONFIG_FB_SIMPLE results in working video. I've put up my working kernel here (that's the debian kernel sources with the patches applied etc but built with the upstream build process) https://jmtd.net/tmp/pi3/vmlinuz-4.11.6 modules: https://jmtd.net/tmp/pi3/4.11.6.tar.xz (46M) (there's an initramfs in there too) I've also put up the not-working .debs (https://jmtd.net/tmp/pi3/) And a dmesg output from running the .debs which seems to include some kind of backtrace which is probably relevant. https://jmtd.net/tmp/pi3/dmesg.txt -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄⠀
Bug#701656: cloning 701656 ..., reassign -1 to base-installer ...
Hi all, I hit this last week. I was doing an expert mode install of jessie onto a PowerPC Mac Mini. I had a USB keyboard attached during install time and I did not remove it. However, I was doing both an expert-mode install and using the remote console via ssh feature of the installer (not sure if that has any bearing). I opted for targetted thinking "why not?" when asked by the installer. Some notes, following up on a few points from the various threads for this bug 1) I saw some comment hoping this would be resolved in time for 7.0: sadly, it wasn't, and is present in 8.0. 2) as mentioned above, the issue is not just whether given hardware is present or not at kernel install time. My USB keyboard was attached, and yet targetted did not include the necessary drivers for boot-time passphrase entering. I imagine that the targetted prompt doesn't show up for normal installs, but if it does, I would suggest not showing it if the user has opted for an encrypted disk during the partman stages. Obviously the prompt will appear during expert-mode installs, so I'd echo some of the previous comments that it should be re-worded. I'm not sure whether different wording could be offered depending on whether encryption was selected during the partman stages? I think there still remains an actual bug in the targetted module selection logic relating to USB devices on the PowerPC Mac Mini. -- Jonathan Dowland
Bug#705635: found 705635 in 3.2.41-2+deb7u2
Hi folks, this was hitting me quite hard with 3.2.41-2+deb7u2. I had four hang ups yesterday. lowriter 1:4.0.3-3 seemed to be the most reliable way to trigger the bug (under gnome-shell 3.4.2-7). So far 3.8-2-amd64 seems fine. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130530082530.ga21...@ubik.ncl.ac.uk
