On Wed, Feb 19, 2025 at 6:00 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:linux package:
>
> #966291: linux-image-5.6.0-0.bpo.2-amd64: SSD failure on
> linux-image-5.6.0-0.bpo.2-amd64
>
Package: src:linux
Version: 6.9.7-1
Severity: normal
Dear Maintainer,
Using fuse-overlayfs on tmpfs (/dev/shm/[folder]) causing system to
freeze during suspend / resume cycle. With kernel message:
[60730.265604] task:systemd-sleep state:D stack:0 pid:88748 ppid:1
flags:0x4002
[60730.267
Duplicate of:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982956
I have exactly the same issues and 'bisected' to the same problematic
commit you are referring to.
-- AK
Just created kernel bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=214933
-- AK
Building a recent kernel without a bugous patch makes a working machine!
[v5.10.70] + [debian patches 5.10.70-1_bpo10+1] + [revert 69a74aef8]
Suspend / resume works!
-- AK
git bisect pinpoint the following commit:
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[69a74aef8a18eef20fb0044b5e164af41b84db21] e100: use generic power
management
Author: Vaibhav Gupta
Date: Mon Jun 29 14:59:43 2020 +0530
e100: use generic power management
With
I've tested following:
v5.0.2
v5.2.17
v5.3.15
v5.4.19
with debian patches applied, and compiled for Pentium M CPU - suspend /
resume working fine!
compiling:
v5.10.70
v5.10.1
makes 'task blocked for..." appear. Seems like this is 5.10 kernel issue.
I'm trying kernel git 'bisect' for the first
I checked again vmlinuz-4.19.0-14-686 kernel and it works fine. Note sure
why it failed back then (maybe my mistake). But all recent kernels from
'bullseye', 'bookworm' and 'sid' failed. Last tested from 'bookworm' failed:
linux-image-5.14.0-1-686_5.14.6-2_i386.deb
-- AK
I've tested suspend / resume with 'linux-image-5.13.0-trunk-686
(5.13.12-1~exp1)' - not working!
Kernel freezes with the same error. Full logs at:
https://linux-hardware.org/?probe=04307947ae
(dmesg.1 logs for 'task blocked')
I'm using Debian 11 clean installation with Debian 10 kernel (Buster,
Thank you Ben for your review!
I did move back to non pae kernel - same issue. If you check full logs
(dmesg.1) from my previous email, you will see a lot more "task blocked"
not just for ping. And it does indeed block my wifi connection restoration
after resume, but it also block all windows from
Hello!
vmlinuz-5.10.0-7-686-pae has know issue related to suspend / resume i915
video card bug.
https://gitlab.freedesktop.org/drm/intel/-/issues/2905
Suspend / resume and notebook stop responding with a lot of "task
blocked for more ... seconds"
Jun 4 17:48:14 m3n kernel: [ 605.618305] INFO
Debian 9 issue fixed for 4.19.0-16-686-pae.
Debian 10 issue still presents in vmlinuz-5.10.0-7-686-pae
-- AK
I did rebuild debian kernel (linux-source-5.4 == 5.4.19-1~bpo10+1) with
ubuntu 5.4.0-26-generic and it works again. And tested kernel for a few
days - no corruption!
Looks like something wrong with original debian config which causes random
data loss on my SSD. Attaching diffconfig's.
config-5.4.
I've tried ubuntu kernel + debian os (full os with only ubuntu kernel as
external package) and try to use it for a few days. It works! I can say it
is a debian kernel issue and not a package base issue.
Debian 10.6 + Ubuntu kernel 5.4.0-26-generic
'diffconfig debian ubuntu' attached.
-- AK
dif
>From 26 Jul 2020 to 14 Aug I used to run Ubuntu 20.04. And have no issues
with 'debsums -c' nor 'Path of Exile' self check. Then I reinstall debian
completely (clean super duper install) using debootstrap and keep it
running since. Two days later. On a day (today) 16 aug I ran booth debsums
and PO
Filesystem got corrupted on the first day of using debian and
5.4.0-0.bpo.4-amd64. It probably somehow related to debian kernel patches?
I'll keep using debian 5.4 until next crash. Then I'll get back to ubuntu
for longer period of time.
-- AK
Package: src:linux
Version: 5.2.9-2
Severity: normal
Hello,
How to reproduce:
1. set up zram with mem_limit that we can hit, like 10MB or so
2. get system to start swapping there, for example put a large random file in
tmpfs and attempt to lock large portion of memory with memtester
System freez
, pacemaker and dlm.
--
Best Regards,
Alexey 'Alexxy' Shvetsov
://datatracker.ietf.org/doc/draft-eromenko-ipff-udp/
The Linux kernel has so many IPv4 modules, that I don't know even
where to start... But the general idea is to take existing IPv4 code
and modify it according to IP-FF specification.
Would you like to help me implement it on Linux ?
--
-Alexey Ero
I just merge my debian and upstream branches to new branch. And then I
successfully built from it.
I think this is abnormal situation.
Thanks for attention.
I still think this is a bug in source package.
Your build log showed me nothing.
I have separate branches for debian folder and upstream sources and
building them with git-buildpackage command. And I think that you merged
debian and upstream branches that is the reason you have no trouble with
>Why would it be good for this to be exposed inside a container?
So that applications know, if they can use advanced features such as
AppArmor or not. And to give more complete environment for the admins.
Plus, to debug problems inside debian-installer. (it lacks /boot/config),
like bug # 783982,
ture, and there is no downside from
enabling it.
+General setup
[*] Kernel .config support
[*] Enable access to .config through /proc/config.gz
Original article:
http://superuser.com/questions/287371/obtain-kernel-config-from-currently-running-linux-system
Thanks in advance,
--
-Alexey Eromenko &
Package: src:linux
Version: 3.16.5-1
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
When I close the lid on my laptop, it goes to sleep (suspend).
ssie" BETA, kernel Linux version
3.16-2-amd64 Debian 3.16.3-2 (2014-09-20)
--
-Alexey Eromenko "Technologov", 28.Oct.2014.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archiv
Package: src:linux
Version: 3.10.7-1
Severity: important
Tags: upstream
Dear Maintainer,
A new problem appeared after upgrading the kernel on my machine. Connecting to
the encrypted network has quite a big chance to cause a deadlock. Even if there
is no deadlock, the following errors appear:
Aug
Package: linux-2.6
Version: 2.6.32-30
Severity: normal
Once in a while, about once or twice a week, my X server freezes. No
predictable pattern; nothing in particular that could seem to trigger
the freeze.
I can ssh into the machine, but can't kill X or even reboot because the
radeon module is st
Package: linux-image-2.6-686
Version: 2.6.32+28
Computer: Fujitsu-Siemens AMILO L7300
The fact that acpi-cpufreq is not working properly with Dothan CPU's.
FATAL: Error inserting acpi_cpufreq: No such device
cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : I
.32-3-686/postinst/depmod-error-initrd-2.6.32-3-686: false
linux-image-2.6.32-3-686/postinst/bootloader-test-error-2.6.32-3-686:
linux-image-2.6.32-3-686/postinst/missing-firmware-2.6.32-3-686:
linux-image-2.6.32-3-686/prerm/removing-running-kernel-2.6.32-3-686: true
--
Alexey Feldgendler
[I
a new old hard drive and spend some time
reproducing that bug on my old hardware (which I still own) but it's
really low-priority for me :) anyway it's always easy to reopen bug if
necessary.
Alexey
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a sub
I'll tell you that right after the reboot :) In few days, I think.
Alexey
On 8/31/09, Moritz Muehlenhoff wrote:
> On Wed, Jun 10, 2009 at 08:49:09PM +0700, Alexey Salmin wrote:
>> This bug is reproducable, but this time I closed googleearth I've
>> slightly different
So is the answer that V4L1 is simply no longer supported? If so, then it's
understandable. However, if something is still supported it's supposed to
work.
--
Alexey Feldgendler
[ICQ: 115226275] http://feldgendler.livejournal.com
--
To UNSUBSCRIBE, email to debian-k
This bug is reproducable, but this time I closed googleearth I've
slightly different syslog messages:
Jun 10 17:02:44 salmin kernel: [82713.786255] [drm:radeon_cp_idle]
*ERROR* radeon_cp_idle called without lock held, held 0 owner
8800780a02c0 8800780a05c0
Jun 10 17:02:44 salmin kernel: [
I have same problem on latest kernel:
# uname -a
Linux sip 2.6.26-2-686 #1 SMP Thu May 28 15:39:35 UTC 2009 i686 GNU/Linux
--
Alexey Goloschapov
ISP Ukrcom | CIO | Tel (0552)420069 | GAS91-RIPE
--
To UNSUBSCRIBE, email to debian-kernel-requ
Package: fglrx-modules-2.6.26-2-686
Version: 2.6.26+8-12-2+lenny1
Severity: grave
File: /lib/modules/2.6.26-2-686/nonfree/fglrx/fglrx.ko
I've got both fglrx-modules-2.6.26-2-686 and fglrx-driver (1:9-2-2)
from testing.
From the X11 log:
(II) fglrx(0): Kernel Module Version Information:
(II) fgl
Package: linux-image-2.6.16-2-amd64-k8-smp
Version: 2.6.16-18
Severity: important
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Not updating initrd symbolic links since we are being
updated/reinstalled
(2.6.16-17 was configured last, according to dpk
36 matches
Mail list logo
