Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
On Thursday, 19 January 2023 13:19:32 CET Diederik de Haas wrote: > It generally takes me a few *seconds* to spot the issue. One reason for that is that the cause and the solution of the issue tends to be the same, pretty much every single time. Namely a new kernel version with which their dkms module is not made compatible yet, so we could be extra helpful by pointing that out and request they contact the maintainer of their dkms module to make it compatible with the new kernel version. signature.asc Description: This is a digitally signed message part.
Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
On 19 January 2023 10:32:04 CET, Andreas Beckmann wrote: >On 17/01/2023 18.27, Diederik de Haas wrote: >> It seems fine to print (in all caps afaic) that there is an issue. > >That tends to get overlooked ... in the middle of a thousand packages being upgraded ... I said ALL CAPS and there are more ways to decorate it which make it REALLY stands out. Does that mean that someone will still miss it? Yes. And that would be entirely their fault. The number of times I've seen people on #debian-next break their Sid system is truly mindboggling. And every time it's because they couldn't be arsed to read the feedback the system gave them. "This action* will remove your entire DE. Do you want to continue?" *) usually dist-upgrade "Hey! I just did an upgrade and now my DE is broken! What should I do?" "Downgrade to the version in Testing" "No. I run Sid, not Testing" "Yeah. You probably shouldn't bc you apparently don't know how to do that. Still, the solution is to downgrade to the Testing version. Alternatively you can get the older version from snapshot.d.o, but getting them from Testing tends to be much easier" "I'm not going to do that, because I run Sid!" "Enjoy your broken Sid system then. Sid, where if it breaks you get to keep all the pieces." I really wish this was some fictional story I pulled out of my arse. But no, this is a paraphrasing of several actual conversations I had in the last few weeks. And yesterday someone's Sid system was broken because of some (aufs) dkms module whose source needs to be updated for the brand new kernel that was uploaded to Sid. So this problem only occurs to people who run Sid, but REALLY shouldn't. And it would be good if they actually end up with a broken system as that's likely the only way they'll learn. btw: upgrading a *1000* packages is not a realistic scenario. It might happen when people dist-upgrade from one Stable release to the next. And then the following 2 things are also true: - The dkms module should be compatible for a while now as the Stable kernel version exists for a while - They do such an upgrade without looking for potential issues ?!? >We must not silently create an unbootable system. Agreed. Hence my suggestion to use ALL CAPS so the issue is shouted at them. ** * WARNING:* * Potentially UNBOOTABLE issue occurred: * * * ** And IMO for those l33t h@xx0rs who're running Sid, because running a Rolling Release is what their fellow Reddit-l33r-h@xx0rs do too, really are best served with an unbootable system (in this case). Recovering from that is a really useful exercise and they should learn to actually read the (generally very clear) feedback the system gives them. It generally takes me a few *seconds* to spot the issue. My 0.02 signature.asc Description: This is a digitally signed message part.
Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
On Thu, Jan 19, 2023 at 10:32:04AM +0100, Andreas Beckmann wrote: > > But it should not cause the kernel package install/upgrade to fail. > > And that does seem in dkms' control afaict. > We must not silently create an unbootable system. Please stop failing the installation. I will NMU that in a few days if not fixed, or add a conflict to the kernel. Bastian -- Madness has no purpose. Or reason. But it may have a goal. -- Spock, "The Alternative Factor", stardate 3088.7
Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
On 17/01/2023 18.27, Diederik de Haas wrote: It seems fine to print (in all caps afaic) that there is an issue. That tends to get overlooked ... in the middle of a thousand packages being upgraded ... A possible noticeable notification scheme could be a debconf error being presented (with the option to inspect the make.log) and these options: * ignore the failure for this module once * ignore failures for this module always * fail (in order to fix it up manually and manually resume configuration afterwards) There could be an additional preseedable debconf template (defaulting to false) to ignore *any* dkms build failures. (For those knowing what they are doing.) But it should not cause the kernel package install/upgrade to fail. And that does seem in dkms' control afaict. We must not silently create an unbootable system. module-assistant shows an error and halts the upgrade process by reading a line from stdin ... that behavior possibly even predates debconf. (policy now mandates any prompting to be done via debconf). Andreas PS: I'm not going to implement the debconf bits due to -ENOTIME.
Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
On Tuesday, 17 January 2023 18:12:30 CET Andreas Beckmann wrote: > On Tue, 17 Jan 2023 10:56:33 +0100 Bastian Blank wrote: > > > Error! Bad return status for module build on kernel: 6.0.0-6-amd64 > > > (x86_64) > > > Consult /var/lib/dkms/anbox-binder/1/build/make.log for more > > > information. > > That does not look like a module packaged in Debian ... These kind of issues get regularly filed against the Debian kernel and it does not matter whether the dkms module is packaged in Debian or not. If the dkms module is packaged in Debian, we assign it to the specific dkms package. > > dkms fails the installation if anything it tries to build does not work. > > This must go, reassigning accordingly. > > What should dkms do instead? Out-of-tree modules break frequently on new > kernel upstream major versions, that is completely out of dkms' control. > > There are two points in time where these errors could show up: > * ) at package installation/upgrade time because building the module > failed (there is a small chance of the build succeeding ater reboot > if a badly packaged module only supports building against the > running kernel) > * ) at reboot due to a missing kernel module > > A failing module could build be 'harmless' if it's e.g. just the > soundcard driver missing (unless you depend on text-to-speech) but in > the worst case it's the root file system that is not supported... It seems fine to print (in all caps afaic) that there is an issue. But it should not cause the kernel package install/upgrade to fail. And that does seem in dkms' control afaict. signature.asc Description: This is a digitally signed message part.
Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
On Tue, 17 Jan 2023 10:56:33 +0100 Bastian Blank wrote: > Error! Bad return status for module build on kernel: 6.0.0-6-amd64 (x86_64) > Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. That does not look like a module packaged in Debian ... dkms fails the installation if anything it tries to build does not work. This must go, reassigning accordingly. What should dkms do instead? Out-of-tree modules break frequently on new kernel upstream major versions, that is completely out of dkms' control. There are two points in time where these errors could show up: * ) at package installation/upgrade time because building the module failed (there is a small chance of the build succeeding ater reboot if a badly packaged module only supports building against the running kernel) * ) at reboot due to a missing kernel module A failing module could build be 'harmless' if it's e.g. just the soundcard driver missing (unless you depend on text-to-speech) but in the worst case it's the root file system that is not supported... Andreas
Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
Control: reassign -1 dkms - breaks kernel installation Control: severity -1 grave On Tue, Jan 17, 2023 at 09:36:26AM +0100, Stefano Simonucci wrote: > Package: src:linux > Version: 6.0.12-1 > Severity: critical > Justification: breaks the whole system No, it does not. The kernel is the system and you always have an old one. > in the last upgrade I got this errors: > Building module: > Cleaning build area... > make -j8 KERNELRELEASE=6.0.0-6-amd64 all > KERNEL_SRC=/lib/modules/6.0.0-6-amd64/build...(bad exit status: 2) > Error! Bad return status for module build on kernel: 6.0.0-6-amd64 (x86_64) > Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. dkms fails the installation if anything it tries to build does not work. This must go, reassigning accordingly. Bastian -- You're dead, Jim. -- McCoy, "The Tholian Web", stardate unknown
Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors
Package: src:linux Version: 6.0.12-1 Severity: critical Justification: breaks the whole system Dear Maintainer, in the last upgrade I got this errors: Building module: Cleaning build area... make -j8 KERNELRELEASE=6.0.0-6-amd64 all KERNEL_SRC=/lib/modules/6.0.0-6-amd64/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.0.0-6-amd64 (x86_64) Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.0.0-6-amd64.postinst line 11. Then the package remains unconfigured, but installed. The next reboot gives a kernel panic, so I must boot previous kernels. Thanks Best regards Stefano -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUS product_name: All Series product_version: System Version chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: 2202 board_vendor: ASUSTeK COMPUTER INC. board_name: Z97-K board_version: Rev X.0x ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eth1 iface eth1 inet dhcp auto dsl-provider iface dsl-provider inet ppp pre-up /bin/ip link set eth1 up # line maintained by pppoeconf provider dsl-provider ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor DRAM Controller [1043:8534] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: hsw_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [1043:8534] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1] (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family USB xHCI Controller [1043:8534] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba] Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family ME Interface [1043:8534] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad] (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family USB EHCI Controller [1043:8534] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0] Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family HD Audio Controller [1043:8616] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0) (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family PCI Express Root Port 1 [1043:8534] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
