Dear Maintainer, Up to now I worked with Linux 6.1.0-7-amd64, without any trouble. I just installed Linux 6.1.0-7-amd64 and I get a kernel panic when launching it. Here is a transcription of what appears on the screen (OCR on a screen picture, I hope there are no remaining errors). ---- [ 0.117782] Kernel panic — not syncing: timer doesn’t work through Interrupt- remapped I0-APIC [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 Debian 6.1.20-1 [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020 [ 0.117982] Call Trace: [ 0.118634] <TASK> [ 0.118685] dump_stack_lvl+0x44/0x5c [ 0.118143] panic+0x118/0x2ed [ 0.118198] panic_if_irq_remap.cold+0x5/0x5 [ 0.118256] setup_I0_APIC+0x3db/0x64b [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40 [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240 [ 0.118429] apic_intr_node_init+0x101/0x106 [ 0.118485] x86_late_time_init+0x20/0x34 [ 0.118542] start_kerne1+0x667/0x727 [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb [ 0.118658] </TASK> [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through Interrupt-remapped IO-APIC J--- ---- Hope it helps. Thanks in advance for your help. Best regards.
Guy Durrieu <guy.durrieu@cegetel.net> writes: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b Bjørn
Hello, Thanks for your answer ! Before receiving it I tried to update my BIOS to the last available version (F51h). Without any effect. I am not sure I understand everything that is said in your link, except I must wait for the next updates... Right ? Best regards.
the issue and Bjørn thinks it's the one referenced. To test whether that's indeed the case, there's a procedure here: https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.1 These are preliminary steps to the actual one which is para 4.2.2 and I have attached a patch which reverts the referenced commit and that .patch file is what you give as an argument to `bash debian/bin/test-patches`. If you could try that to see if that indeed fixes the issue, that would be very helpful. HTH
Hi Guy, AFAIK there is no commit upstream with fixes tag on that commit. But Bjorn suspects that might be the suspicious commit introducing the issue. Would you be able to build a kernel 6.1.20 with that patch reverted on top and see if it resolved your issue? Regards, Salvatore
Hello, This is something I have never done, but I can try. However some time ago, for solving a previous issue, a guy from Debian compiled for me an unofficial release including the patch to be tested, along with some credentials. I know this is not the recommended procedure :) but it worked. Best regards,
Salvatore Bonaccorso <carnil@debian.org> writes: Yes, I noticed that, so I could very well be wrong... But it stood out as the only change to any x86 IOAPIC stuff since Linux 6.1.0-6-amd64. That's of course not any guarantee. But worth testing. Bjørn
Hi, Seems there was a race on responding. If you look at the documentation referenced by Diederik there are instructions on how to do it with a single patch applied on top. If you run into trouble let us know though. Regards, Salvatore
Thanks for your help ! There is something not clear for me in the section 4.2.2. Simple patching and building... I ran apt-get install devscripts but I can't find any debian directory nor patches. Is it sufficient to apply the patch given by Diederik de Haas ? Regards.
I'm guessing you forgot to do the Preparation from 4.2.1
I am in trouble... I first did "Obtaining the kernel source", and at the end I got a /root/linux-source-6.1/ directory. Then I did "Rebuilding official Debian kernel packages" and "Preparation", and then I got among others a /root/linux-source-6.1/linux-6.1.20 the content of which is similar to the parent one, and where I can find, by the way, a debian directory. It seems strange to me, is it correct? If it is correct, in what order to do the patches (debian patches and the revert patch)? Thanks in advance for your help ! Best regards. <guy.durrieu@cegetel.net> wrote: >> Thanks for your help ! >> >> There is something not clear for me in the section 4.2.2. Simple >> patching and building... >> >> I ran apt-get install devscripts but I can't find any debian >> directory nor patches. Is it sufficient to apply the patch given by >> Diederik de Haas ? > > I'm guessing you forgot to do the Preparation from 4.2.1 > >> Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit : >>> Hi, >>> >>> On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote: >>>> Hello, >>>> >>>> This is something I have never done, but I can try. >>>> >>>> However some time ago, for solving a previous issue, a guy from >>>> Debian compiled for me an unofficial release including the >>>> patch to be tested, along with some credentials. I know this is >>>> not the recommended procedure :) but it worked. >>> Seems there was a race on responding. If you look at the >>> documentation referenced by Diederik there are instructions on >>> how to do it with a single patch applied on top. If you run into >>> trouble let us know though. >>> >>> Regards, Salvatore >> >
we can improve the documentation :-) With "Preparation" I meant paragraph 4.2.1 and you don't need to follow 4.1. Also worth noting is that command prefixed by `#` should be done as root, but the commands prefixed by `$` should be done as (normal) user. So this is what you need to do: # apt-get install build-essential fakeroot # apt-get build-dep linux While we're 'root', do this too: # apt-get install devscripts And then (as user): $ apt-get source linux $ cd linux-6.1.20 If you then do ``ls -lh`` you will see a ``debian`` directory. So now you can run this: $ bash debian/bin/test-patches <path-to-the-patch-file> And now it should build a patched kernel for you. When you look at the output of the ``apt-get source linux`` you'll see it download the linux source code and (automatically) applies the debian patches which are always applied when building a debian kernel. This is excluding the patch I send earlier, but that gets applied when you run the ``bash debian/bin/test-patches`` command. HTH, Diederik
Thanks for your help ! That was more or less my conclusion, but it would indeed be useful to clarify that 4.1 and 4.21. are mutually exclusive. And I must admit that the # vs $ steps had escaped me :( Best regards.
Thanks for your help ! That was more or less my conclusion, but it would indeed be useful to clarify that 4.1 and 4.21. are mutually exclusive. And I must admit that the # vs $ steps had escaped me :( Best regards.
Hello everybody, I just finished to build the patched kernel. After installing it, the system 6.1.0-7 boots again and run fine. Thus the source was well identified by Bjørn Mork. I just had problems trying to install linux-headers-6.1.0-7-amd64_6.1.20-1a~test_amd64.deb, for dependencies reasons not so clear for me. It is not mandatory anyway. Thanks a lot to all of you for your help ! What next ? Best regards.
Control: tag -1 upstream Well done! This is great :-) Yeah, there are some improvements to be made for the procedure. You're welcome and thanks for doing this. kernel :-D 2) The commit that Bjørn identified also contained a "Link:" tag: https://lore.kernel.org/r/20230105041059.39366-1-kvijayab@amd.com The best thing to do is to respond to that thread and explain the issue you ran into. At the bottom of the page you can find instructions on how to do that. The To/CC list is quite large, but don't be alarmed by that, that's rather common with kernel development. It's probably a good idea to add 1033732@bugs.debian.org to that list. The instructions also contain this part: "Avoid top-posting and favor interleaved quoting" That's what I've been doing and is considered rather important, so try your best to do that too. In your reply you should put the following things: 1) Your system worked find with kernel 6.1.15, but stopped booting after upgrading to 6.1.20 and resulted in a kernel panic 2) Copy the part between "----" from your initial report so that it shows the kernel panic, your motherboard info and the stack trace 3) Indicate that Bjørn identified ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b from the linux-6.1.y branch as the likely culprit 4) After building a 6.1.20 kernel with just that commit reverted, your system booted normally again. 5) You reported that all to https://bugs.debian.org/1033732 and were asked to report the issue 'upstream' (which is what that mail is). It could be that they'll ask you to test a patch. If it's just a simple/single patch you should be able to try that with the same procedure as you've already done, but replace the patch I provided with one they provide. If you don't understand what they're asking or f.e. the kernel build is/seems too complicated, feel free to ask for help in (just) this bug. Good luck and thanks in advance :-)
If you feel 'uncomfortable' or something like that, we can do this part too. If/when a new patch arrives, we will need your help in testing that though.
Le 05/01/2023 à 05:10, Kishon Vijay Abraham I a écrit : Hello everyone, My system worked fine with kernel 6.1.15, but stopped booting after upgrading to 6.1.20 and resulted in a kernel panic:--- [ 0.117782] Kernel panic — not syncing: timer doesn’t work through Interrupt-remapped IO-APIC [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 Debian 6.1.20-1 [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020 [ 0.117982] Call Trace: [ 0.118634] <TASK> [ 0.118685] dump_stack_lvl+0x44/0x5c [ 0.118143] panic+0x118/0x2ed [ 0.118198] panic_if_irq_remap.cold+0x5/0x5 [ 0.118256] setup_I0_APIC+0x3db/0x64b [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40 [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240 [ 0.118429] apic_intr_node_init+0x101/0x106 [ 0.118485] x86_late_time_init+0x20/0x34 [ 0.118542] start_kerne1+0x667/0x727 [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb [ 0.118658] </TASK> [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through Interrupt-remapped IO-APIC J--- --- I tried an update of the BIOS up to F51h without any effect. I sent a bug report to Debian Bug Tracking System. In reply Bjørn Mork identified ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b from the linux-6.1.y branch as the likely culprit. After building a 6.1.20 kernel with just that commit reverted, my system boots normally again. I reported that all tohttps://bugs.debian.org/1033732 and were asked to report the issue 'upstream' (which is what that mail is). Hope it will help! Best regards.
Does this fix it: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent Thx.
I sent the requested report. And indeed received a new patch to be tested. In progress... Le 02/04/2023 à 10:30, Diederik de Haas a écrit :
Le 02/04/2023 à 12:57, Borislav Petkov a écrit : Yes it does. Regards.
Hi Guy, https://salsa.debian.org/kernel-team/linux/-/merge_requests/692 Thanks for your time put in debugging the issue. Regards, Salvatore
Thanks for testing.
We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1033732@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Salvatore Bonaccorso <carnil@debian.org> (supplier of updated linux package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 08 Apr 2023 17:36:24 +0200
Source: linux
Architecture: source
Version: 6.1.20-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Salvatore Bonaccorso <carnil@debian.org>
Closes: 925424 1019118 1030200 1031180 1032136 1032948 1033566 1033732
Changes:
linux (6.1.20-2) unstable; urgency=medium
.
[ Hans van Kranenburg ]
* d/t/control.tools-unversioned.in: version rtla build deps
.
[ Helmut Grohne ]
* Fix FTCBFS: Supply the host pkg-config to the rtla build. (Closes: #1019118)
.
[ Francesco Dolcini ]
* [armhf] Add support for NXP i.MX7 SOC (Closes: #1031180)
.
[ Martyn Welch ]
* [arm64] ti: am62x: Enable support for am625-sk eval board
* d/salsa-ci.yml: Increase timeout of CI build stage to 3 hours
.
[ наб ]
* Re-instate "KEYS: Make use of platform keyring for module signature verify"
(Closes: #1030200)
.
[ Vincent Blut ]
* drivers/input/touchscreen: Enable TOUCHSCREEN_SILEAD as module
(Closes: #925424)
* [x86] drivers/platform/x86: Enable TOUCHSCREEN_DMI
* drivers/scsi/mpi3mr: Enable SCSI_MPI3MR as module (Closes: #1033566)
.
[ Diederik de Haas ]
* [arm64,armhf] Enable DRM_PANEL_FEIYANG_FY07024DI26A30D as module
.
[ Cyril Brulebois ]
* udeb: add intel_lpss* (optional) to kernel-image (Closes: #1032136)
Many laptops have their touchpad accessible over I2C, only visible
if LPSS is available in the installer.
.
[ Salvatore Bonaccorso ]
* [x86] acpi/boot: Correct acpi_is_processor_usable() check (Closes: #1033732)
* usb: ucsi: Fix NULL pointer deref in ucsi_connector_change()
(Closes: #1032948)
* usb: ucsi_acpi: Increase the command completion timeout (Closes: #1032948)
* [arm64] hwmon: (xgene) Fix use after free bug in xgene_hwmon_remove due to
race condition (CVE-2023-1855)
* net/sched: act_mirred: better wording on protection against excessive stack
growth
* act_mirred: use the backlog for nested calls to mirred ingress
(CVE-2022-4269)
* [x86] xirc2ps_cs: Fix use after free bug in xirc2ps_detach (CVE-2023-1670)
* Bluetooth: HCI: Fix global-out-of-bounds (CVE-2023-28866)
.
[ Henning Schild ]
* [x86] drivers/gpio: Enable GPIO_F7188X as module
Checksums-Sha1:
43988866bbba4b3078bd387019f8ea61af58a57e 276943 linux_6.1.20-2.dsc
c93d6989e7f5f70bfdbbe4c23c2a6c60bf745df3 4585780 linux_6.1.20-2.debian.tar.xz
89ac3cacc90d4bf1520933154ff544cd733d405a 6754 linux_6.1.20-2_source.buildinfo
Checksums-Sha256:
0770faca88ec9da5711fc0d5abdd150d188c56bf8dd19ae0120aa22f5fe69a3e 276943 linux_6.1.20-2.dsc
8fc1b579ed50f458975aa1d65ae3d513e64a8fd207d192ea8767a58e72dd09b6 4585780 linux_6.1.20-2.debian.tar.xz
03e4305c5b89cf7ef15affc35dcbaac4bca6df9fcdb58e42a1a02b34d970da85 6754 linux_6.1.20-2_source.buildinfo
Files:
73cd74091256a472038d9eba264ef69d 276943 kernel optional linux_6.1.20-2.dsc
d6be3828376d26b9e72d747e09c7439c 4585780 kernel optional linux_6.1.20-2.debian.tar.xz
28f64e24560ed3fe22e4e1b005963146 6754 kernel optional linux_6.1.20-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmQxirJfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EN50QAJD7Wy9uBqCRXZ6dJyC2tmM+fS8zxU/r
NqVhS3CzCKRhDWtRBKl9dzvMbXIKRJeMGvvYcmRGqBTGs3mdHgZ3li04zmcTGWo1
V+EcmFRN90MAdqcxAWC5wTJyxGMroPQVXFkW6IFd4tZQOzLmyc4vU2+f8z63I4XR
J7gLJ4mUfFyadSNq+BllK1F+YQJWwcMGhR6ZKWQ6uBUM+pjagm0ALjZ3j/bkzGvI
qIPhekny/XZ9tjDZ4bq93ddomYXDYH+P3gGfVEs9S5LOHKol6eU7SFnWB1g5aD5m
VatQNIU2Afpfc63uY7+zIsyojqq7rQNBnL4Yp24Cwpkw0ESjiOxeipjFgVQrq+c0
79j7Hyhdv/pnYyqeY8v9IEW9bZvrbhNiJ43UaWj5BmDlZSjeVFBDuAVC6ogWl/vy
nkQO9G6LKa8ZKcIBFlWz5nllCO3lG2dKeHLoRwMCE9gVCG9EuU9DI49KLLx6MDYC
uPyDntSVt5Wjj7ltN/3m8YFsTKpHxHh0F/ly96kH7A1aEv1VG1E5fp0sO3Hq5Z3b
cjbzObwRBjtxTlxOOtZYoteVI6n36T8xRSbN/SehBv1C3+XNe8vq93AxTbABJ1Ip
u9Nr8lGmNvYiTY3M9IBxqIhrPr4z/QHktfEHj4pJ6QnRlawdhdKO5yN/WifO15tf
wnmw9YRegy2j
=fmzO
-----END PGP SIGNATURE-----