Thanks for following up. I think you are right, these two old MacMinis gets into a weird state where apt is affected by the kernel usercopy problem, i.e. apt is not causing the problem itself. Both behave the same with bookworm 6.1 kernel. No problems on the bullseye 5.10 kernel. Please close this case since it is not an apt issue.
$ /usr/lib/apt/methods/http < /tmp/testrequest 100 Capabilities Send-URI-Encoded: true Send-Config: true Pipeline: true Version: 1.2 102 Status Message: Connecting to ftp-nyc.osuosl.org URI: http://ftp.us.debian.org/debian/dists/bookworm/InRelease 102 Status Message: Connecting to ftp-nyc.osuosl.org (64.50.233.100) URI: http://ftp.us.debian.org/debian/dists/bookworm/InRelease 102 Status Message: Connected to ftp-nyc.osuosl.org (64.50.233.100) URI: http://ftp.us.debian.org/debian/dists/bookworm/InRelease GET /debian/dists/bookworm/InRelease HTTP/1.1 Host: ftp.us.debian.org Accept: text/* User-Agent: Debian APT-HTTP/1.3 (2.6.1) 102 Status Message: Waiting for headers URI: http://ftp.us.debian.org/debian/dists/bookworm/InRelease Answer for: http://ftp.us.debian.org/debian/dists/bookworm/InRelease HTTP/1.1 200 OK Date: Tue, 21 Nov 2023 21:54:35 GMT Server: Apache Last-Modified: Sat, 07 Oct 2023 09:49:42 GMT ETag: "24dfd-6071d46c1efad" Accept-Ranges: bytes Content-Length: 151037 200 URI Start Last-Modified: Sat, 07 Oct 2023 09:49:42 +0000 Size: 151037 URI: http://ftp.us.debian.org/debian/dists/bookworm/InRelease 201 URI Done Checksum-FileSize-Hash: 151037 SHA512-Hash: 10437f8f2ab4e1c45494d46096c753110b9b4b19a706087537ff77c951ccc30185a4e829456c926cae1d1a89052127f97aab5d4c828ef1f120fea8a5fb39badc SHA256-Hash: f4339999d996ac53bab13e33631c6c250b8a7216692c56a2da61194bdd944bf7 SHA1-Hash: 1ff2370064bd97104a10a73578f6c75c6bebfc13 MD5Sum-Hash: bc85d0cdcc061129196e9caac8311995 MD5-Hash: bc85d0cdcc061129196e9caac8311995 Last-Modified: Sat, 07 Oct 2023 09:49:42 +0000 Size: 151037 Filename: /dev/null URI: http://ftp.us.debian.org/debian/dists/bookworm/InRelease On Tue, Nov 21, 2023 at 3:54 PM David Kalnischkies <da...@kalnischkies.de> wrote: > > Control: reassign -1 src:linux 6.1.38-4 > Control: forcemerge 1051643 -1 > Control: affects -1 apt > > Hi, > > On Tue, Nov 21, 2023 at 11:04:18AM -0500, js1 wrote: > > Running apt-get update causes kernel BUG as reported in 1051643. apt-get > > update hangs: > > If that is as you describe, that the bug is in the kernel, we as apt > maintainers can do nothing about it. > > We have also no other reports to that effect here or as far as I can see > in Launchpad (= Ubuntu) against apt, so this might be highly dependent > on your/specific hardware. > > So, keeping the bug open here seems to serve no purpose in my eyes and > hence I am merging it with the existing one – but I tag it as affecting > apt, so that it appears in its bug list should other users encounter > this with apt (which I suppose was your intend). > > > Beside you running apt I don't see any apt code in the trace, but from > the apt output produced I suppose its triggering somewhere in the > download step, so the following might help to simplify the reproducer > a bit – if you can reproduce it that way of course as a lot of > complexity is stripped away which might trigger it… > > $ cat > /tmp/testrequest <<EOF > 601 Configuration > Config-Item: Debug::Acquire::http=1 > Config-Item: Debug::Acquire::https=1 > Config-Item: Acquire::http::DependOnSTDIN=0 > Config-Item: Acquire::https::DependOnSTDIN=0 > > 600 URI Acquire > URI: http://ftp.us.debian.org/debian/dists/bookworm/InRelease > Filename: /dev/null > > EOF > $ /usr/lib/apt/methods/http < /tmp/testrequest > > (yes, you can and are encouraged to run this as non-root user. > While creating the testrequest file make sure copy everything between > the two EOF. Especially the ending empty line. A successful run ends > with a block starting with "201 URI Done". Your apt output suggests > it triggers somewhere between "102 Status" and "200 URI Start".) > > Before giving up on this try using a real Filename and/or different URI > in the testrequest (if you want to use a https URI, make sure to call > the https method!). > > > Hope that helps & good luck finding the cause & solution. > > Best regards > > David Kalnischkies -- Jiann-Ming Su
