Your message dated Sun, 22 Mar 2026 04:39:05 +0100
with message-id <[email protected]>
and subject line Re: Bug#1126682: dpkg: machine reboots immediately with some
deb files
has caused the Debian Bug report #1126682,
regarding dpkg: machine reboots immediately with some deb files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1126682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126682
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.21.22
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
while upgrading Debian 11 to 12 on PowerEdge 860 server, it rebooted suddenly.
All attempts to continue upgrade ended with reboots.
Tracked it down to dpkg. Running dpkg-deb -c on some packages causes immediate
reboot, e.g.:
firmware-misc-nonfree_20230210-5_all.deb
intel-microcode_3.20251111.1~deb12u1_amd64.deb
Tried various dpkg versions (from snapshot.debian.org). The first bad version
is 1.21.13. I suspect that it's caused by multithread liblzma decompression
support that was enabled in this version but haven't confirmed that.
Looks like a HW problem - but WTF? CPU bug? The server is:
DELL PowerEdge 860, 2GB RAM, Xeon 3050 (dual core), SAS 5/iR RAID
It was running all Debian versions from 5 to 11 without any problems.
Now it's running 12 with dpkg 1.20.13 from Debian 11. No other problems.
We're running Debian 12 on many other servers without any problems, including
another PowerEdge 860 (but only 1 GB RAM, Celeron D, no HW RAID).
-- Package-specific info:
System tainted due to merged-usr-via-aliased-dirs.
-- System Information:
Debian Release: 12.13
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-42-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.8-5+b1
ii libc6 2.36-9+deb12u13
ii liblzma5 5.4.1-1
ii libselinux1 3.4-1+b6
ii tar 1.34+dfsg-1.2+deb12u1
ii zlib1g 1:1.2.13.dfsg-1
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 2.6.1
pn debsig-verify <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
On Thu, 2026-02-19 at 03:21:02 +0100, Guillem Jover wrote:
> On Fri, 2026-01-30 at 16:09:10 +0100, Ondrej Zary wrote:
> > Package: dpkg
> > Version: 1.21.22
> > Severity: important
> > X-Debbugs-Cc: [email protected]
>
> > while upgrading Debian 11 to 12 on PowerEdge 860 server, it rebooted
> > suddenly.
> > All attempts to continue upgrade ended with reboots.
> >
> > Tracked it down to dpkg. Running dpkg-deb -c on some packages causes
> > immediate
> > reboot, e.g.:
> > firmware-misc-nonfree_20230210-5_all.deb
> > intel-microcode_3.20251111.1~deb12u1_amd64.deb
> >
> > Tried various dpkg versions (from snapshot.debian.org). The first bad
> > version
> > is 1.21.13. I suspect that it's caused by multithread liblzma decompression
> > support that was enabled in this version but haven't confirmed that.
> >
> > Looks like a HW problem - but WTF? CPU bug? The server is:
> > DELL PowerEdge 860, 2GB RAM, Xeon 3050 (dual core), SAS 5/iR RAID
> >
> > It was running all Debian versions from 5 to 11 without any problems.
> > Now it's running 12 with dpkg 1.20.13 from Debian 11. No other problems.
> >
> > We're running Debian 12 on many other servers without any problems,
> > including
> > another PowerEdge 860 (but only 1 GB RAM, Celeron D, no HW RAID).
>
> Hmm, this indeed seems very weird, and I'm afraid not very actionable
> from this side. To me a reboot would be an indicator of either a hw or
> a kernel issue. I guess you could try a debugger and stepping over the
> code at least to see what instruction might be triggering the problem,
> but that might be tedious. Otherwise and unfortunately I'm not sure
> there's much to be done here from the dpkg side, so I'm inclined to
> close this in a bit, unless there being some indication this could
> actually be a problem with dpkg.
I'm closing this now. Please, feel free to reopen or file a new report
if more information comes forward that would indicate a problem in
dpkg.
Thanks,
Guillem
--- End Message ---
