Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.bugs.dist    |    Ohh some weird Debian bug report thing    |    28,835 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 28,138 of 28,835    |
|    Guillem Jover to Ondrej Zary    |
|    Bug#1126682: dpkg: machine reboots immed    |
|    19 Feb 26 03:30:01    |
      XPost: linux.debian.maint.dpkg       From: guillem@debian.org              Hi!              On Fri, 2026-01-30 at 16:09:10 +0100, Ondrej Zary wrote:       > Package: dpkg       > Version: 1.21.22       > Severity: important       > X-Debbugs-Cc: zary@gsystem.sk              > 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.              Thanks,       Guillem              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca