Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by cable2600 on Monday November 16, 2026 @01:36AM
(#50514713)
>Either that or Santa Altman came down the chimney during the night and swapped all their RAM sticks out for bad ones.
Back in the early 1990s, when they had PC Clone shops, some PC Clone shops would buy from others when RAM chips were in short supply. Sometimes they were bad RAM chips and were sold to sabotage the other PC Clone shop.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by walrus01 on Monday November 16, 2026 @01:29AM
(#50514679)
When people say "this is a VM on xen" I really wish they would provide on essential piece of troubleshooting data. As a domU, is it PV, PVH, full HVM, or HVM with PV drivers? There's a huge difference for how a modern xen dom0 handles the bootloader and kernel boot for those.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by walrus01 on Monday November 16, 2026 @01:47AM
(#50514763)
I would agree with you if trixie had just been released, but a lot of the rough edges have been worn off by now. Running the present branch of debian stable (as opposed to debian testing) is already an extremely conservative choice and gets you a lot of revisions of packages that are quite old compared to what ships in other distros...
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by walrus01 on Monday November 16, 2026 @02:49AM
(#50515117)
I'm not going to take seriously a single person's anecdote of "I upgraded to trixie, stuff broke" when I weigh it against the large number of people I know who run debian stable with very few operating-system-base caused problems for very serious production things.
Your comment is devoid of any useful technical detail on what broke or why, and quite frankly reads like a very linux noob complaint. Leading me to think you did something wrong in the upgrade process, or failed to manually handle any basic configuration files that you were prompted with diffs/merge/install/keep existing version in the upgrade process.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by LtWorf on Monday November 16, 2026 @02:59AM
(#50515176)
I mean, linux kernel broke userspace in a couple different instances between oldstable to stable. If his software happened to use those APIs it could crash. Just an example. But a normal person would fix their software (if they have the sources to do that!)
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by csdreamer7 on Monday November 16, 2026 @03:04AM
(#50515202)
> Your comment is devoid of any useful technical detail on what broke or why, and quite frankly reads like a very linux noob complaint. Leading me to think you did something wrong in the upgrade process, or failed to manually handle any basic configuration files that you were prompted with diffs/merge/install/keep existing version in the upgrade process.
Why is your first reaction is to assume the person broke something in the upgrade process or did something in the config files? The parent comment is devoid of useful technical detail, but assuming the user is at fault is terrible. Debian is very conservative between releases with not upgrading packages from upstream and keeps a lot out of tree patches. It is very possible something broke between the major versions.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by wrappajack on Monday November 16, 2026 @08:29AM
(#50517403)
It doesn’t appear the user is seeking help with the issue, they solved the problem themselves. They seem to be simply advising on their experience with the process.
Not sure how it’s any less valid than your anecdotal experience.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by nbernard on Monday November 16, 2026 @03:05AM
(#50515208)
Not GP, but I've been using Debian for 25+ years and, as a user, I still don't understand how to report a bug the right way when it is unclear what package is the cause for a regression...
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by LtWorf on Monday November 16, 2026 @03:24AM
(#50515300)
The proper way is to figure out which package is causing a regression.
As an alternative you can report a general bug that will end up on the debian-devel mailing list where someone might reassign it to the proper place. But low effort reports sent to generals are basically a waste of everyone's time.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by LoganDark on Monday November 16, 2026 @04:30AM
(#50515682)
This is only economical if you can afford the time wastage yourself. If you need a working system, you don't have the time to fix the bug yourself (hoping you won't find two more by the time you're done)
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by LtWorf on Monday November 16, 2026 @08:29AM
(#50517399)
Lol, everyone has a successful startup here but the second you suggest buying for a service (that unlike AI actually provides value) here come the downvotes.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by nbernard on Monday November 16, 2026 @02:59AM
(#50515180)
FYI, for the next time: with Debian, while rollback is not supported, it often works.
I had issues too with Trixie on a laptop (after upgrade everything became unbearably slow, probably due to an Intel graphic chip which was dropped by Mesa or some other library) and did a rollback to bookworm. IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by tremon on Monday November 16, 2026 @06:12AM
(#50516293)
> IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...
The problem with rollbacks is not the packages themselves, that usually works without issues. The problem is with configuration and data items: if a package changes configuration format on upgrade (e.g. move from pkg.conf to pkg.conf.d), a downgrade will not restore the old pkg.conf.
Also, apt will not downgrade packages without prodding. At the very least, you would need --allow-downgrades.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by jeroenhd on Monday November 16, 2026 @04:03AM
(#50515535)
OS rollback is possible if you've configured it. A combination of btrfs + timeshift has served me very well after a failed Ubuntu upgrade. You can just boot into the previous snapshot from Grub.
Although you can set this up after the fact (converting ext4 to btrfs is supported and you can update your mounts from any recovery distro), that's probably just something to keep in mind for your next fresh install. It's also extremely for any other kind of failed upgrade, though, not just full OS upgrades.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by walrus01 on Monday November 16, 2026 @07:46AM
(#50517038)
The hardware requirements of a base CLI only server trixie are not greater than the same base CLI environment of bookworm. we're talking like, 300MB RAM when system booted with full systemd and openssh and a few other standard things running. The only major difference is that 32-bit/i386 cpu support was dropped. If you have an original intel core duo (not core 2 duo) from 2006 that isn't 64-bit, or older, yeah I could see that being a problem... but otherwise,
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by mschuster91 on Monday November 16, 2026 @03:22AM
(#50515286)
> I would agree with you if trixie had just been released, but a lot of the rough edges have been worn off by now.
That doesn't help if you need to run a piece of software only certified to run under a certain Java version or, worse, a certain OS version. It's either "run on something really old" or "lose the ability for commercial support / you're on your own if shit happens".
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by mschuster91 on Monday November 16, 2026 @04:29AM
(#50515672)
eh I'd like a "just ubuntu" requirement much more than the usual "only RHEL is supported" slop...
Yeah I get it, vendors want to keep their support matrix small. But RHEL (and its bunch of derivatives) just plain suck ass. At least offer support for something based on Debian...
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by burnt-resistor on Monday November 16, 2026 @05:59AM
(#50516231)
Containers !~= VMs (except Kata Containers and similar). VMs ensure specific, isolated, supported compatible kernel versions in controlled environments because what's supported isn't the same as what's technically possible.
Containers seem lightweight and magical until the tyranny of the quirks of the kernel matters with some gotchas of supported configurations as opposed to unsupported gremlins running custom stuff that other vendors refuse to touch.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by currysausage on Monday November 16, 2026 @03:48AM
(#50515456)
To give an example, there is a rough edge called Dovecot 2.4 (new config syntax, Director removed, master/master replication removed) that will not wear off by itself. Upgrading to 2.4 could, depending on the complexity of your setup, require days to weeks of planning, testing and implementation.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by jeroenhd on Monday November 16, 2026 @03:58AM
(#50515508)
Upgrading complex setups is never easy, but people have had over a year to plan, test, and implement their upgrades.
These people will need to upgrade at some point, though that point will probably be at the very last moment midway through 2028 if they're still on oldstable today.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by harshreality on Monday November 16, 2026 @07:18AM
(#50516810)
If only there were some weeks — over a year of them, ideally, in which to plan and execute a dovecot upgrade while watching trixie's progress toward suitability — available between August 2025 and November 2026.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by currysausage on Monday November 16, 2026 @09:50AM
(#50518195)
> dovecot 2.3 containers for the desperate
"Last pushed: over 2 years", while Dovecot 2.3 in Debian Bookworm still receives security patches backported from 2.4 through Debian LTS [1]. Backporting (and LTS in general) certainly isn't bulletproof, but I would prefer it over an abandoned Docker image.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by j16sdiz on Monday November 16, 2026 @06:44AM
(#50516524)
In many case, many software runs on the same server.
Docker don't help much because the image can't build from dockerfile, because some dependency are not downloading.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by prmoustache on Monday November 16, 2026 @05:13AM
(#50515957)
Technologies such as the venerable chroot, schroot, lxc, lxd, docker, podman or systemd-nspawn have made sure that the applications component can always be independent of an unresolved compatibility across Debian versions.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by fl0ki on Monday November 16, 2026 @11:58AM
(#50519794)
Definitely not by choice, but sometimes I don't have physical access to a machine for years at a time, and don't want to risk losing my network access as well due to an upgrade hiccup.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update
by whisperenjoyer on Monday November 16, 2026 @08:57AM
(#50517649)
I was able to reproduce the ext4 issue with qemu/kvm guest using debian cloud bookworm qcow2 image. You just need to run stress-ng --class filesystem for some time. Definitely not network problem and not xen-specific one. I think most of ext4 users (at least with common mount options) are affected.
I couldn't understand which Debian ran this strange kernel version, until I realized my oldstable boxes run a backport kernel.
Phew.
Because oldstable was... pretty freaking old even when it was new.
Either that or Santa Altman came down the chimney during the night and swapped all their RAM sticks out for bad ones.
Back in the early 1990s, when they had PC Clone shops, some PC Clone shops would buy from others when RAM chips were in short supply. Sometimes they were bad RAM chips and were sold to sabotage the other PC Clone shop.
Often there are unresolved compatibility issues across Debian versions. Some are not necessarily tied to the kernel but other components.
"Just upgrade bro" can be a recipe for punishment.
Trixie is 14 months old now
I upgraded to Trixie. Stuff broke.
I rolled back to Bookworm, which was extremely painful, because unlike other OSes rollback is not possible and a reinstall is necessary.
Stuff worked again.
Maybe I'll give it another go in 2028 when it goes EOL. Or maybe not. I'm not under any obligation to keep trying.
Your comment is devoid of any useful technical detail on what broke or why, and quite frankly reads like a very linux noob complaint. Leading me to think you did something wrong in the upgrade process, or failed to manually handle any basic configuration files that you were prompted with diffs/merge/install/keep existing version in the upgrade process.
Why is your first reaction is to assume the person broke something in the upgrade process or did something in the config files? The parent comment is devoid of useful technical detail, but assuming the user is at fault is terrible. Debian is very conservative between releases with not upgrading packages from upstream and keeps a lot out of tree patches. It is very possible something broke between the major versions.
FWIW people use the very same words when they forgot to turn on the monitor or plug their desktop computer to an outlet.
The user who is just complaining without providing any sort of useful information that could be used to help them?
Not sure how it’s any less valid than your anecdotal experience.
Leaving hundreds of unpatched security vulnerabilities open hardly seems "solving"
If you don't report the bugs of what breaks (possibly while it's in testing) nobody can help you.
As an alternative you can report a general bug that will end up on the debian-devel mailing list where someone might reassign it to the proper place. But low effort reports sent to generals are basically a waste of everyone's time.
I had issues too with Trixie on a laptop (after upgrade everything became unbearably slow, probably due to an Intel graphic chip which was dropped by Mesa or some other library) and did a rollback to bookworm. IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...
The problem with rollbacks is not the packages themselves, that usually works without issues. The problem is with configuration and data items: if a package changes configuration format on upgrade (e.g. move from pkg.conf to pkg.conf.d), a downgrade will not restore the old pkg.conf.
Also, apt will not downgrade packages without prodding. At the very least, you would need --allow-downgrades.
Although you can set this up after the fact (converting ext4 to btrfs is supported and you can update your mounts from any recovery distro), that's probably just something to keep in mind for your next fresh install. It's also extremely for any other kind of failed upgrade, though, not just full OS upgrades.
(I guess tar czf would work)
https://clonezilla.org/
That doesn't help if you need to run a piece of software only certified to run under a certain Java version or, worse, a certain OS version. It's either "run on something really old" or "lose the ability for commercial support / you're on your own if shit happens".
Yeah I get it, vendors want to keep their support matrix small. But RHEL (and its bunch of derivatives) just plain suck ass. At least offer support for something based on Debian...
Containers seem lightweight and magical until the tyranny of the quirks of the kernel matters with some gotchas of supported configurations as opposed to unsupported gremlins running custom stuff that other vendors refuse to touch.
> "lose the ability for commercial support / you're on your own if shit happens"
is not something you can clever your way into. It's the vendors choice what support characteristics look like.
Both bookworm and trixie contain the obsolete OpenJDK v8 JRE for both amd64 and ppc64el as it's needed for nvidia-visual-profiler.
These people will need to upgrade at some point, though that point will probably be at the very last moment midway through 2028 if they're still on oldstable today.
Alternatively, if only there were a way to run a contained instance of dovecot 2.3, something like https://hub.docker.com/layers/dovecot/dovecot/2.3.21.1/image...
"Last pushed: over 2 years", while Dovecot 2.3 in Debian Bookworm still receives security patches backported from 2.4 through Debian LTS [1]. Backporting (and LTS in general) certainly isn't bulletproof, but I would prefer it over an abandoned Docker image.
[1] https://tracker.debian.org/news/1817828/accepted-dovecot-123...
And it has been the case for literally decades.
"It's inside our VPN, no customer accesses that server, what could happen?"
We upgraded only to be able to run a newer Java version.
https://worldstories.org.uk/reader/joha-and-his-donkey/engli...
> From: Salvatore Bonaccorso <[email protected]>
> I think this is this one: https://lore.kernel.org/linux-ext4/20261102-ext4-ntfs3-null-...
https://salsa.debian.org/kernel-team/linux/-/merge_requests/...
Seems people are happy with the proposed fix.
Its definitely getting ridiculous.
Might be a filesystem hiccup, and some firmware blobs went missing, or something? Just speculating here.
Might also be handy to save dmesg output from the kernel version that works fine, and lay output side-by-side.