Bug#928923: linux-image-4.19.0-4-cloud-amd64: reports different NIC name than linux-image-amd64 on virtio-net
Package: src:linux Version: 4.19.28-2 Severity: normal Environment: Proxmox VE host, 5.4-1 KVM guest, Debian 10 testing virtio_net NIC With linux-image-4.19.0-4-cloud-amd64: # udevadm test-builtin net_id /sys/class/net/en* Load module index Parsed configuration file /usr/lib/systemd/network/99-default.link Created link configuration context. Using default interface naming scheme 'v240'. ID_NET_NAMING_SCHEME=v240 ID_NET_NAME_MAC=enxbe57fa7f6fb0 ID_NET_NAME_PATH=enp6s18 Unload module index Unloaded link configuration context. enp6s18 is used for NIC. With linux-image-4.19.0-4-amd64: +ID_NET_NAME_SLOT=ens18 ens18 is used for NIC. Changing NIC name on switching between kernel varient, IMHO, is not expected. -- Package-specific info: ** Version: Linux version 4.19.0-4-cloud-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-4-cloud-amd64 root=UUID=8782a6fc-9622-4d76-8ba0-a7c51dfc9b19 ro quiet ** Not tainted ** Kernel log: ** Model information [0.620425] pcieport :00:1c.0: Signaling PME with IRQ 24 [0.620484] pcieport :00:1c.1: Signaling PME with IRQ 25 [0.620542] pcieport :00:1c.2: Signaling PME with IRQ 26 [0.620599] pcieport :00:1c.3: Signaling PME with IRQ 27 [0.620659] pciehp :00:1c.0:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep- (with Cmd Compl erratum) [0.620816] pciehp :00:1c.1:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep- (with Cmd Compl erratum) [0.620949] pciehp :00:1c.2:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep- (with Cmd Compl erratum) [0.621082] pciehp :00:1c.3:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep- (with Cmd Compl erratum) [0.621261] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [0.621694] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 [0.622440] serio: i8042 KBD port at 0x60,0x64 irq 1 [0.622447] serio: i8042 AUX port at 0x60,0x64 irq 12 [0.622514] mousedev: PS/2 mouse device common for all mice [0.622763] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [0.623105] NET: Registered protocol family 10 [0.627774] Segment Routing with IPv6 [0.627790] mip6: Mobile IPv6 [0.627794] NET: Registered protocol family 17 [0.627820] mpls_gso: MPLS GSO support [0.627848] sched_clock: Marking stable (609989229, 14091148)->(634303071, -10222694) [0.627952] registered taskstats version 1 [0.627952] Loading compiled-in X.509 certificates [0.659562] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [0.659575] Loaded X.509 cert 'Debian Secure Boot Signer: 00a7468def' [0.659584] AppArmor: AppArmor sha1 policy hashing enabled [0.661077] Freeing unused kernel image memory: 1456K [0.672181] Write protecting the kernel read-only data: 16384k [0.673093] Freeing unused kernel image memory: 2028K [0.673655] Freeing unused kernel image memory: 1420K [0.673763] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.673764] x86/mm: Checking user space page tables [0.673781] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.673784] Run /init as init process [0.734305] PCI Interrupt Link [GSIF] enabled at IRQ 21 [0.734939] PCI Interrupt Link [GSIG] enabled at IRQ 22 [0.739958] cryptd: max_cpu_qlen set to 1000 [0.746752] AVX version of gcm_enc/dec engaged. [0.746752] AES CTR mode by8 optimization enabled [0.751777] PCI Interrupt Link [GSIH] enabled at IRQ 23 [0.772002] virtio_net virtio1 enp6s18: renamed from eth0 [0.772457] SCSI subsystem initialized [0.775114] scsi host0: Virtio SCSI HBA [0.776243] scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK2.5+ PQ: 0 ANSI: 5 [0.776500] scsi 0:0:0:1: Direct-Access QEMU QEMU HARDDISK2.5+ PQ: 0 ANSI: 5 [0.787717] random: fast init done [0.792775] sd 0:0:0:0: Power-on or device reset occurred [0.793199] sd 0:0:0:0: [sda] 1073741824 512-byte logical blocks: (550 GB/512 GiB) [0.793223] sd 0:0:0:0: [sda] Write Protect is off [0.793228] sd 0:0:0:0: [sda] Mode Sense: 63 00 00 08 [0.793271] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [0.794211] sd 0:0:0:0: [sda] Attached SCSI disk [0.794229] sd 0:0:0:1: Power-on or device reset occurred [0.794433] sd 0:0:0:1: [sdb] 31457280 512-byte logical blocks: (16.1 GB/15.0 GiB) [0.794462] sd 0:0:0:1: [sdb] Write Protect is off [0.794464] sd 0:0:0:1: [sdb] Mode Sense: 63 00 00 08 [0.794515] sd 0:0:0:1: [sdb] Write cache: enabled,
Processed: reassign 928891 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 928891 src:linux 4.19.28-2 Bug #928891 [linux-image-amd64] linux-image-amd64: Kernel crash when using any disk that uses reiserfs Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/104. Ignoring request to alter fixed versions of bug #928891 to the same values previously set Bug #928891 [src:linux] linux-image-amd64: Kernel crash when using any disk that uses reiserfs Marked as found in versions linux/4.19.28-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 928891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928891: linux-image-amd64: Kernel crash when using any disk that uses reiserfs
On Sun, 2019-05-12 at 18:34 +0200, Thanatermesis wrote: > Package: linux-image-amd64 > Version: 4.19+104 > Severity: important > > Dear Maintainer, > > When using any partition which uses reiserfs, the kernel crashes > > This happens very easily by just using the reiser (v3) filesystem, some > of my external hard disks uses it (so I cannot make use of them), or > partition mountpoints with reiserfs becomes totally unusable and > dangerous > > This bug is easily reproducible by creating a new reiserfs partition > (image file probably too) and start using it, so it looks like it > specially affects in RW operations > > I suggest to mark this bug as a serious one since there's so many people > using this filesystem, in desktops or servers. > > The package is the last one available on the buster branch reiserfs v3 is *not* widely used, and is barely maintained upstream. Debian hasn't supported installing to reiserfs for a while. It is quite possible that we will "fix" this by disabling reiserfs altogether. In any case, I strongly recommend that you switch to a better supported filesystem like ext4 or xfs. Ben. -- Ben Hutchings It is a miracle that curiosity survives formal education. - Albert Einstein signature.asc Description: This is a digitally signed message part
Bug#928891: linux-image-amd64: Kernel crash when using any disk that uses reiserfs
Package: linux-image-amd64 Version: 4.19+104 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, When using any partition which uses reiserfs, the kernel crashes This happens very easily by just using the reiser (v3) filesystem, some of my external hard disks uses it (so I cannot make use of them), or partition mountpoints with reiserfs becomes totally unusable and dangerous This bug is easily reproducible by creating a new reiserfs partition (image file probably too) and start using it, so it looks like it specially affects in RW operations I suggest to mark this bug as a serious one since there's so many people using this filesystem, in desktops or servers. The package is the last one available on the buster branch Thank you - -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-amd64 depends on: ii linux-image-4.19.0-4-amd64 4.19.28-2 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfeKOpqCfdgmEOvbZoseZv9/418IFAlzYSmYACgkQoseZv9/4 18LahhAAteYzza00P/QifDn3CbF5z3CHj3WDHJ9wj/CdIgUDEU7nvZpwTiF6WvwF 4Rjx2ZWXuaRDaBO2FnZQI/aANGm3wNNo7Y4Q3IzVC4OCO8uRbenHLzkViQbhBdLb aqsSyDrT4ryHgxWM6pF+Fg6shIhiOObEqUfmD0ZNoCGuk6iReYPSOYT2MebIEdKH QxBVwdCFfUuaZfp873joDblPTVly9ynvFyvhQ9xZG0yu7wrSFWSWt5fEMWatDhbW vVS5iFICh4HzYeYFkeMgBWc+SLPcnefwXEcZgBKtpNHCpfiq3Xow85QIK6/ec72A ay8fRWqiOMNU3GgyHfI/4olNm/K6vJ2ZL9m6N4lD5YN3WrRK9Qg0GWu7tfr35J6S VLRr+1a89vzqzS3piOUd5bVyakJueVCtLiwcDLfi36c1iEjr+GJwvvy8M5/QO2xS Q1khrBQui3lKNPxgxF3KGNX3qtvdIthrsGdO7Aoyzb3Fh3Xt6Tyl6shWWqK9mm9H 7fhmuORhnZQKSO35epRgNYhv35c1I9w5e4iHxNfbhTH4dlMZkCEJYLXnD+vtsWzz Op4nsYFuqDfB1XgrsvNfbeIy8szHKzHKDF4TAdtjsHd+AXJYnaQCR/Wq4y+RwaO8 Ff6gTBha4OKups3X0OL6e5/xUO+RREUYBtYEenXIYURvX4Kidh4= =kmLp -END PGP SIGNATURE-
Bug#928855: marked as done (CPU usage/freq periodically raises on amd64 (Kaby Lake))
Your message dated Sun, 12 May 2019 15:58:36 +0100 with message-id and subject line Re: Bug#928855: CPU usage/freq periodically raises on amd64 (Kaby Lake) has caused the Debian Bug report #928855, regarding CPU usage/freq periodically raises on amd64 (Kaby Lake) 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.) -- 928855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-4.19.0-4-amd64 To: mainto...@bugs.debian.org Subject: CPU usage/freq periodically raises on amd64 (Kaby Lake) Package: linux-image-4.19.0-4-amd64 Version: 4.19.28-2 amd64 Dear maintainers, In my amd64 Kaby Lake GNOME machine, CPU usage/freq periodically raises. Watching top as root with CPU time sort, I doubt kworker/0:2-events_power_efficient. It periodically wakes and has relatively a large number of CPU time usage. (It means, not power efficient) That is happening even in rescue.target. FYI: chkrootkit shows nothing interesting. Regards. --- End Message --- --- Begin Message --- This is a somewhat interesting observation, but I fail to see a bug. Ben. On Sun, 2019-05-12 at 17:11 +0900, hoxp18 wrote: > Package: linux-image-4.19.0-4-amd64 > To: mainto...@bugs.debian.org > Subject: CPU usage/freq periodically raises on amd64 (Kaby Lake) > Package: linux-image-4.19.0-4-amd64 > Version: 4.19.28-2 amd64 > > Dear maintainers, > > In my amd64 Kaby Lake GNOME machine, > CPU usage/freq periodically raises. > > Watching top as root with CPU time sort, > I doubt kworker/0:2-events_power_efficient. > > It periodically wakes and has relatively > a large number of CPU time usage. > (It means, not power efficient) > > That is happening even in rescue.target. > > FYI: chkrootkit shows nothing interesting. > > Regards. > -- Ben Hutchings It is a miracle that curiosity survives formal education. - Albert Einstein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#928855: CPU usage/freq periodically raises on amd64 (Kaby Lake)
Package: linux-image-4.19.0-4-amd64 To: mainto...@bugs.debian.org Subject: CPU usage/freq periodically raises on amd64 (Kaby Lake) Package: linux-image-4.19.0-4-amd64 Version: 4.19.28-2 amd64 Dear maintainers, In my amd64 Kaby Lake GNOME machine, CPU usage/freq periodically raises. Watching top as root with CPU time sort, I doubt kworker/0:2-events_power_efficient. It periodically wakes and has relatively a large number of CPU time usage. (It means, not power efficient) That is happening even in rescue.target. FYI: chkrootkit shows nothing interesting. Regards.
