Your message dated Thu, 01 May 2025 14:50:56 +0200 (CEST)
with message-id <20250501125056.9da0abe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1009350,
regarding linux-image-5.17.0-trunk-cloud-amd64: include i6300esb watchdog
driver for openstack/libvirt/kvm/qemu
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 ow...@bugs.debian.org
immediately.)
--
1009350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.17.1-1~exp1
Severity: normal
Dear Maintainer,
when working with linux-image-cloud-amd64's bullseye cousin,
I noticed that the watchdog dev (/dev/watchdog) was absent
from the VM and I'm unable to use the watchdog actions.
The OpenStack wiki says that only "i6300esb" makes sense:
<https://wiki.openstack.org/wiki/LibvirtWatchdog>
"KVM has a choice of two watchdog devices, but in reality
only the PCI i6300esb device makes sense, since the alternative
is a legacy ISA bus device."
Looking through the provided modules files for the kernels
/lib/modules/5.10.0-13-cloud-amd64/kernel/drivers/watchdog/
(and later /lib/modules/5.17.0-trunk-cloud-amd64/kernel/drivers/watchdog/
of linux-image-5.17.0-trunk-cloud-amd64. I did this because the reportbug
suggested that I also look at the experimental branch and I thought:
"hey, why not?!")
the available watchdog modules are (both 5.10.0-13 + 5.17.0-trunk):
mei_wdt.ko, ni903x_wdt.ko, nic7018_wdt.ko, softdog.ko, wdat_wdt.ko,
wdt_pci.ko and xen_wdt.ko
This makes sense, since in /boot/config-5.10.0-13-cloud-amd64 and
/boot/config-5.17.0-trunk-cloud-amd64 had the watchdog disabled:
| # CONFIG_I6300ESB_WDT is not set
Would it be possible to build the i6300esb as a module for future
releases?
Thanks,
Christian Lamparter
-- Package-specific info:
** Kernel log: boot messages should be attached
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, powerpc, mips, arm64
Kernel: Linux 5.17.0-wt+ (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages linux-image-5.17.0-trunk-cloud-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.141
ii kmod 29-1
ii linux-base 4.8
Versions of packages linux-image-5.17.0-trunk-cloud-amd64 recommends:
ii apparmor 3.0.4-2
ii firmware-linux-free 20200122-1
Versions of packages linux-image-5.17.0-trunk-cloud-amd64 suggests:
pn debian-kernel-handbook <none>
ii extlinux 3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii grub-efi-amd64 2.06-2
pn linux-doc-5.17 <none>
Versions of packages linux-image-5.17.0-trunk-cloud-amd64 is related to:
ii firmware-amd-graphics 20210818-1
ii firmware-atheros 20210818-1
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
ii firmware-brcm80211 20210818-1
pn firmware-cavium <none>
pn firmware-intel-sound <none>
pn firmware-intelwimax <none>
ii firmware-ipw2x00 20210818-1
pn firmware-ivtv <none>
ii firmware-iwlwifi 20210818-1
ii firmware-libertas 20210818-1
pn firmware-linux-nonfree <none>
ii firmware-misc-nonfree 20210818-1
pn firmware-myricom <none>
pn firmware-netxen <none>
pn firmware-qlogic <none>
ii firmware-realtek 20210818-1
pn firmware-samsung <none>
pn firmware-siano <none>
ii firmware-ti-connectivity 20210818-1
pn xen-hypervisor <none>
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "en_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
-- debsums errors found:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "en_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---
