Bug#795991: /boot/vmlinuz-3.16.0-0.bpo.4-amd64: duplicate request cache is too small for NFS 4.1 servers
Hi Christoph, On Fri, Apr 30, 2021 at 05:32:43PM +0200, Christoph Martin wrote: > > > Am 30.04.21 um 14:32 schrieb Salvatore Bonaccorso: > > > > is this problem still relevant? > > > > I think so. My upstream request was never really considered. > You still have the problem that a kernel-nfs server with only few memory > runs out of sessions with a lot of clients. Ack thans for confirming. So either someone tries to bring that issue again to upstream or alternatively we could then close this bug marking (and possibly marking it wontfix). > > Side note that we would anyway not apply a patch which would not have > > been accepted upstream, likely unless there are very valid reasons. > > > > Yes I also think so. > > We changed to nfs-ganesha as a user level NFS server, which does not > have this restriction. Thanks for this additional comment. Thanks as well for your promt reply back! Regards, Salvatore
Bug#741663: marked as done (linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly)
Your message dated Sat, 1 May 2021 07:28:02 +0200 with message-id and subject line Re: G4 MDD report (finally) Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly has caused the Debian Bug report #741663, regarding linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly 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.) -- 741663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux-image-3.13-1-powerpc-smp Severity: normal Dear Maintainer, * What led up to the situation? After upgrade from linux-image-3.12-1-powerpc-smp I noticed the fan in my G4 PowerPC was making different noises than it had previously. I rmmod'ed the therm_windtunnel module and reloaded with modprobe. There were the usual "i2c i2c-7: therm_windtunnel: attach_adapter method is deprecated" message but no initialisation messages from the driver. Also, there are no temperature and fan speed statistics being shown in the kernel log. * What exactly did you do (or not do) that was effective (or ineffective)? I rebooted on linux-image-3.12-1-powerpc-smp * What was the outcome of this action? Fan and Temperature behaving normally * What outcome did you expect instead? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 3.12-1-powerpc-smp Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- On 5/1/21 7:22 AM, Rick Thomas wrote: > rbthomas@macswell:~$ cat /proc/version > Linux version 5.10.0-6-powerpc-smp (debian-kernel@lists.debian.org) (gcc-10 > (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) > #1 SMP Debian 5.10.28-1 (2021-04-09) > > rbthomas@macswell:~$ lsmod | grep wind > therm_windtunnel7229 0 > > The fans come on at low speed when I give the CPU a short workout. I haven't > tried a long-term CPU intensive task yet. OK, then it should be safe to close this report now. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913--- End Message ---
Bug#741663: G4 MDD report (finally) Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
Here's the data from the G4 MDD. Sorry for the delay getting it out! rbthomas@macswell:~$ cat /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 1416.61MHz revision: 3.3 (pvr 8001 0303) bogomips: 83.31 processor : 1 cpu : 7455, altivec supported clock : 1416.61MHz revision: 3.3 (pvr 8001 0303) bogomips: 83.31 total bogomips : 166.63 timebase: 41659125 platform: PowerMac model : PowerMac3,6 machine : PowerMac3,6 motherboard : PowerMac3,6 MacRISC3 Power Macintosh detected as : 129 (PowerMac G4 Windtunnel) pmac flags : 0010 L2 cache: 256K unified pmac-generation : NewWorld Memory : 2048 MB rbthomas@macswell:~$ cat /proc/version Linux version 5.10.0-6-powerpc-smp (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) rbthomas@macswell:~$ lsmod | grep wind therm_windtunnel7229 0 The fans come on at low speed when I give the CPU a short workout. I haven't tried a long-term CPU intensive task yet. Hope this helps! Rick On Tue, Apr 27, 2021, at 3:55 PM, Rick Thomas wrote: > > > On Tue, Apr 27, 2021, at 12:15 AM, John Paul Adrian Glaubitz wrote:> > > On 4/27/21 8:54 AM, Rick Thomas wrote: > > > I'll look around and see if I have any MDD (mirror drive door -- the type > > > in the > > > original bugreport) machines. If so, I'll try to find some time to > > > install Adrian's > > > latest and report back. > > > > OK, thank you. Maybe someone else with a machine that previously had > > this issue can also > > comment so that we can be sure the issue has been fixed. > > > > Rick, maybe you can check whether the windfarm module(s) get(s) loaded > > on your machine? > > > > # lsmod |grep windfarm > > On the G4 (which is _not_ the MDD) I get nothing from that > > On the G5 I get: > > rbthomas@kmac:~$ lsmod | grep wind > windfarm_smu_sat8626 0 > windfarm_ad7417_sensor 7755 0 > windfarm_fcu_controls12227 0 > windfarm_cpufreq_clamp 3881 0 > windfarm_pm72 14329 0 > windfarm_pid3256 1 windfarm_pm72 > windfarm_lm75_sensor 5350 0 > windfarm_max6690_sensor 4600 0 > windfarm_core 11920 7 > windfarm_cpufreq_clamp,windfarm_fcu_controls,windfarm_max6690_sensor,windfarm_smu_sat,windfarm_ad7417_sensor,windfarm_pm72,windfarm_lm75_sensor > > Hope that helps. > Rick > > PS: I do have a MDD, but I haven't yet tried Adrian's latest on it. > Maybe later today, maybe it'll have to wait for the weekend. >
Bug#922666: confirmed bug report
On 2021-04-30 21:04:29, Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > > Hi Tollef, Antoine, > > On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote: >> Control: forcemerge 922666 928189 >> Control: severity 922666 important >> Control: tags 922666 +patch +confirmed >> >> I also see a regression with touchpads and trackpoint on a Thinkpad E431 >> after upgrading from Debian stretch to buster. My research indicates >> this is a kernel regression, as yet to be fixed. >> >> This is the result of my research, as available online at: >> >> https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep >> >> On a Thinkpad E431, the entire mouse interface (touch, trackpoint) >> freezes after sleep. Keyboard still works but not mouse until a >> reboot. >> >> There's [bug 922666][] in Debian buster, without a fix. It also says >> it eventually recovers, which is not our experience. Possible dupe is >> [bug 928189][]. >> >> [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189 >> [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666 >> >> There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and >> which proposes the following workarounds: >> >> * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method >> disabled` >> >> * A .service file: >> >> # /etc/systemd/system/touchpad-sleep.service >> # restore touchpad on suspend >> >> [Unit] >> Description=Restore Touchpad on suspend >> Before=sleep.target >> StopWhenUnneeded=yes >> >> [Service] >> #Type=oneshot >> Type=idle >> RemainAfterExit=yes >> ExecStart=/bin/bash -c 'echo ":00:1f.4" > >> /sys/bus/pci/drivers/i801_smbus/unbind' >> ExecStop=/bin/bash -c 'echo ":00:1f.4" > >> /sys/bus/pci/drivers/i801_smbus/bind' >> >> [Install] >> WantedBy=sleep.target >> >> * "Maybe try xserver-xorg-input-evdev instead of >> xserver-xorg-input-libinput?" >> >> * reloading `psmouse`: >> >> sudo modprobe -r psmouse >> sudo modprobe psmouse >> >> * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to >> solve the issue." >> >> * whatever this is: >> >> # echo 1 > /sys/devices/rmi4-00/nosleep >> >> * "Anyone who still affected by touchpad issues after S3. Please >>switch back to suspend-to-idle in BIOS if s2idle is >>supported. ThinkPad Carbon 6th and Yoga 3rd do support >>suspend-to-idle in BIOS->config->power menu." >> >> [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427 >> >> There's also [bug 1442699][] in Fedora, which suggests those >> workarounds: >> >> * another module reload: >> >> sudo rmmod i2c_hid >> sudo modprobe i2c_hid >> >> * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing >>and this issue seems to have been resolved (for me)." >> >> * another `/proc` hack: >> >> echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl >> >> * "The `psmouse.synaptics_intertouch=0` workaround still works for me." >> >> [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699 >> >> Also related is this [libinput bug][] that's closed as "not our bug" >> because they claim it's a bug in the kernel. >> >> [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149 >> >> There are [two][] [patches][] on the Linux kernel which apparently fix the >> issue, still pending approval: >> >> [two]: https://lkml.org/lkml/2019/2/20/700 >> [patches]: https://lkml.org/lkml/2019/2/20/701 >> >> Possibly related: https://lkml.org/lkml/2016/8/18/134 >> >> [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A >> [pull request][] has been merged in mainline with two other fixes on >> the module./ [5.0.11][] also has fixes on the module. It's clearly a >> regression from Debian stretch (kernel 4.9) since it was working fine >> before. >> >> Possibly related, [two-finger scrolling bug in Ubuntu][], which >> identifies [this commit][] as the source of the regression. [Upstream >> kernel bug][], still open. >> >> [5.1rc7]: https://lkml.org/lkml/2019/4/28/270 >> [pull request]: https://lkml.org/lkml/2019/7/12/19 >> [5.0.11]: https://lkml.org/lkml/2019/5/2/287 >> [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719 >> [this commit]: >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738 >> [two-finger scrolling bug in Ubuntu]: >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478 >> >> I haven't tried any of those workarounds. I hope this helps! > > Can you confirm if this issue is still present with a recent kernel? e.g. buster-backports? -- The flesh you so fancifully fry Is not succulent, tasty or kind It's death for no reason And death for no reason is murder
Bug#987851: linux-version sort: argv and stdin behaviors differ
Package: linux-base
Version: 4.6
Severity: normal
Tags: patch
Using argv:
$ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k
5.8.0-50-generic
5.8.0-50-generic-64k
Using stdin:
$ cat versions.txt
5.8.0-50-generic
5.8.0-50-generic-64k
$ cat versions.txt | linux-version sort
5.8.0-50-generic-64k
5.8.0-50-generic
It seems the trailing "\n" is unexpectedly being used in the comparison.
Now, perl and I have never really gotten along, but this patch seems to work:
--- /usr/bin/linux-version.orig 2020-06-25 17:23:24.0 +
+++ /usr/bin/linux-version 2021-04-30 20:39:13.708560573 +
@@ -70,7 +70,7 @@
@versions = map({[$_, "\n"]} @_);
} else {
while () {
- /^([^ ]*)(.*\n?)$/ or die;
+ /^([^ \n]*)(.*\n?)$/ or die;
push @versions, [$1, $2];
}
}
-- System Information:
Debian Release: 11.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-base depends on:
ii debconf [debconf-2.0] 1.5.76
linux-base recommends no packages.
linux-base suggests no packages.
-- debconf information:
* linux-base/removing-running-kernel: true
linux-base/removing-title:
Processed: fixed 798512 in 4.1.3-1
Processing commands for cont...@bugs.debian.org:
> fixed 798512 4.1.3-1
Bug #798512 {Done: Moritz Mühlenhoff } [src:linux]
linux-image-3.16.0-4-amd64: e1000e hangs with Intel I217-LM
Marked as fixed in versions linux/4.1.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
798512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#802893: marked as done (linux-image-3.16.0-4-amd64: booting into graphical mode sometimes fails (console still works))
Your message dated Fri, 30 Apr 2021 21:42:50 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #802893, regarding linux-image-3.16.0-4-amd64: booting into graphical mode sometimes fails (console still works) 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.) -- 802893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1+deb8u5 Severity: important Dear developers! I have a amd richland APU and also a dedicated graphics card r9 290m. Im not using the fglrx drivers. Sometimes booting into the graphical mode stops before the xserver should come. im using gdm +gnome3 a.t.m. I add the kernel trace here (and hope its of any help for you): Oct 24 12:25:15 hugo6 kernel: [ 32.510519] [ cut here ] Oct 24 12:25:15 hugo6 kernel: [ 32.510646] invalid opcode: [#1] SMP Oct 24 12:25:15 hugo6 kernel: [ 32.510691] Modules linked in: bnep snd_hda_codec_realtek joydev snd_hda_codec_hdmi snd_hda_codec_generic rtl8723ae rtl8723_common rtl_pci rtlwifi radeon mac80211 snd_hda_intel ecb btusb msi_wmi snd_hda_controller bluetooth sparse_keymap psmouse cfg80211 evdev snd_hda_codec serio_raw kvm_amd snd_hwdep 6lowpan_iphc snd_pcm kvm rfkill pcspkr ttm snd_timer drm_kms_helper k10temp drm snd ac wmi i2c_algo_bit i2c_piix4 i2c_core soundcore shpchp battery video button acpi_cpufreq processor fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 algif_skcipher af_alg dm_crypt dm_mod hid_generic usbhid hid sg sd_mod crc_t10dif sr_mod crct10dif_generic cdrom ata_generic ohci_pci crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ohci_hcd ehci_pci xhci_hcd ehci_hcd alx mdio pata_atiixp sdhci_pci ahci sdhci libahci mmc_core libata scsi_mod usbcore usb_common th ermal thermal_sys Oct 24 12:25:15 hugo6 kernel: [ 32.511781] CPU: 1 PID: 701 Comm: Xorg Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt11-1+deb8u5 Oct 24 12:25:15 hugo6 kernel: [ 32.511855] Hardware name: Micro-Star International Co., Ltd. GX70 3CC/MS-176K, BIOS E176KAMS.10F 12/02/2013 Oct 24 12:25:15 hugo6 kernel: [ 32.511937] task: 8800884e32f0 ti: 8800884e8000 task.ti: 8800884e8000 Oct 24 12:25:15 hugo6 kernel: [ 32.511999] RIP: 0010:[] [] radeon_invalid_rreg+0x1c/0x20 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.512105] RSP: 0018:8800884eb730 EFLAGS: 00010282 Oct 24 12:25:15 hugo6 kernel: [ 32.512151] RAX: 004a RBX: 0005 RCX: 0006 Oct 24 12:25:15 hugo6 kernel: [ 32.512212] RDX: 0007 RSI: 0046 RDI: 0246 Oct 24 12:25:15 hugo6 kernel: [ 32.512272] RBP: 880235d67880 R08: R09: 81659ac0 Oct 24 12:25:15 hugo6 kernel: [ 32.512332] R10: 03f0 R11: 00aa R12: 8800884eb780 Oct 24 12:25:15 hugo6 kernel: [ 32.512391] R13: 0069 R14: 0005 R15: 0005 Oct 24 12:25:15 hugo6 kernel: [ 32.512452] FS: 7f3792522980() GS:88023ec8() knlGS: Oct 24 12:25:15 hugo6 kernel: [ 32.512520] CS: 0010 DS: ES: CR0: 80050033 Oct 24 12:25:15 hugo6 kernel: [ 32.512569] CR2: 7f61d2d97ed0 CR3: 000233242000 CR4: 000407e0 Oct 24 12:25:15 hugo6 kernel: [ 32.512629] Stack: Oct 24 12:25:15 hugo6 kernel: [ 32.512650] a06bb0b0 0001884eb7b0 8800884eb7e0 8800884eb7dc Oct 24 12:25:15 hugo6 kernel: [ 32.512726] 0072 0006 5f78 0005 Oct 24 12:25:15 hugo6 kernel: [ 32.512802] a06bc1e5 8800884eb780 f10f 0077 Oct 24 12:25:15 hugo6 kernel: [ 32.512877] Call Trace: Oct 24 12:25:15 hugo6 kernel: [ 32.512923] [] ? atom_get_src_int+0x70/0x7d0 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513000] [] ? atom_op_shr+0x85/0x210 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513074] [] ? atom_execute_table_locked+0x119/0x360 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513158] [] ? atom_op_calltable+0xb3/0x130 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513235] [] ? atom_execute_table_locked+0x119/0x360 [radeon] Oct 24 12:25:15 hugo6 kernel: [ 32.513306] [] ? acpi_ds_create_operands+0x62/0xb2 Oct 24 12:25:15 hugo6 kernel: [ 32.513380] [] ? atom_op_calltable+0xb3/0x130 [radeon] Oct 24 12:25:15 hugo6 kernel: [
Bug#801759: marked as done (linux-image-3.16.0-4-amd64: Screen goes black during boot when gma500_gfx module is loaded)
Your message dated Fri, 30 Apr 2021 21:42:39 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #801759, regarding linux-image-3.16.0-4-amd64: Screen goes black during boot when gma500_gfx module is loaded 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.) -- 801759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1+deb8u5 Severity: important Tags: d-i upstream Hi Just in the fist boot after installin Debian, grub neu is displayed, if you remove the silent option from the kernel yo can see that screens go black after loading DRM Problem is solved disabling gma500_gfx module echo "blacklist gma500_gfx" >> /etc/modprobe.d/fbdev-blacklist.conf update-initramfs -k all -u reboot -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=a6370feb-84d5-4ddb-9b96-37c7721b9740 ro quiet acpi_osi=Linux ** Not tainted ** Kernel log: [5.331503] usb 6-1: new low-speed USB device number 2 using uhci_hcd [5.508559] usb 6-1: New USB device found, idVendor=413c, idProduct=2107 [5.508566] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.508571] usb 6-1: Product: Dell USB Entry Keyboard [5.508575] usb 6-1: Manufacturer: Dell [5.514204] hidraw: raw HID events driver (C) Jiri Kosina [5.530880] usbcore: registered new interface driver usbhid [5.530885] usbhid: USB HID core driver [5.532584] input: Dell Dell USB Entry Keyboard as /devices/pci:00/:00:1d.2/usb6/6-1/6-1:1.0/0003:413C:2107.0001/input/input2 [5.532783] hid-generic 0003:413C:2107.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-:00:1d.2-1/input0 [5.623556] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [5.623902] ata2.00: ATA-8: KINGSTON SS200S330G, S8FM06.A, max UDMA/133 [5.623908] ata2.00: 58626288 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [5.624271] ata2.00: configured for UDMA/133 [5.624517] scsi 1:0:0:0: Direct-Access ATA KINGSTON SS200S3 06.A PQ: 0 ANSI: 5 [5.751590] usb 6-2: new low-speed USB device number 3 using uhci_hcd [5.926645] usb 6-2: New USB device found, idVendor=046d, idProduct=c03e [5.926651] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.926656] usb 6-2: Product: USB-PS/2 Optical Mouse [5.926660] usb 6-2: Manufacturer: Logitech [5.943278] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:1d.2/usb6/6-2/6-2:1.0/0003:046D:C03E.0002/input/input3 [5.943582] hid-generic 0003:046D:C03E.0002: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.2-2/input0 [5.943630] ata3: SATA link down (SStatus 0 SControl 300) [6.239809] Switched to clocksource tsc [6.263681] ata4: SATA link down (SStatus 0 SControl 300) [6.583743] ata5: SATA link down (SStatus 0 SControl 300) [6.903813] ata6: SATA link down (SStatus 0 SControl 300) [6.946696] sd 0:0:0:0: [sda] 58626288 512-byte logical blocks: (30.0 GB/27.9 GiB) [6.946872] sd 1:0:0:0: [sdb] 58626288 512-byte logical blocks: (30.0 GB/27.9 GiB) [6.947029] sd 0:0:0:0: [sda] Write Protect is off [6.947040] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [6.947142] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.947150] sd 1:0:0:0: [sdb] Write Protect is off [6.947157] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [6.947244] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.951026] sdb: sdb1 sdb2 sdb3 [6.951036] sda: sda1 sda2 sda3 [6.952478] sd 1:0:0:0: [sdb] Attached SCSI disk [6.952579] sd 0:0:0:0: [sda] Attached SCSI disk [6.953815] sd 0:0:0:0: Attached scsi generic sg0 type 0 [6.954026] sd 1:0:0:0: Attached scsi generic sg1 type 0 [6.993995] md: bind [6.997739] md: bind [7.001556] md: raid1 personality registered for level 1 [7.002250] md/raid1:md0: active with 2 out of 2 mirrors [7.002330] md0: detected capacity change from 0 to 28424798208 [7.003221] md0: unknown partition table [7.056937] PM: Starting manual resume from disk [7.056947] PM: Hibernation image partition 8:3 present [7.056951] PM: Looking for hibernation
Bug#801463: marked as done (BUG: unable to handle kernel NULL pointer dereference at 00000001 in smp_apic_timer_interrupt)
Your message dated Fri, 30 Apr 2021 21:42:20 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #801463, regarding BUG: unable to handle kernel NULL pointer dereference at 0001 in smp_apic_timer_interrupt 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.) -- 801463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1+deb8u4 Severity: important Dear Maintainer, * What led up to the situation? My kernel has started crashing every few days, since 2015-09-09. The system was upgraded to this kernel (linux-image-3.16.0-4-586 3.16.7-ckt11-1+deb8u4) on 2015-09-20, so it's not a regression in that particular version. I retrieved kernel output from the most recent crash, which replaces the kernel log section below. -- Package-specific info: ** Version: Linux version 3.16.0-4-586 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-586 root=/dev/sda3 ro console=ttyS0,115200n8 ** Not tainted ** Kernel log: [587090.909477] inbound: IN=eth2 OUT= MAC=00:04:a7:08:af:b0:00:1f:27:c0:08:01:08:00 SRC=221.3.105.106 DST=86.9.121.8 LEN=60 TOS=0x00 PREC=0x00 TTL=51 ID=62653 DF PROTO=TCP SPT=39416 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0 [587134.548195] BUG: unable to handle kernel NULL pointer dereference at 0001 [587134.548195] IP: [] smp_apic_timer_interrupt+0x24/0x50 [587134.548195] *pde = [587134.548195] Oops: 0002 [#1] [587134.548195] Modules linked in: tcp_diag inet_diag xt_nat xt_addrtype ipt_MASQUERADE ip6t_REJECT xt_multiport ipt_REJECT xt_LOG xt_limit xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack ip6table_mangle iptable_mangle ip6table_raw iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip6table_filter ip6_tables iptable_filter cpufreq_stats cpufreq_conservative ip_tables x_tables cpufreq_userspace cpufreq_powersave nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc sit tunnel4 ip_tunnel evdev iTCO_wdt iTCO_vendor_support video drm_kms_helper processor pcspkr serio_raw drm thermal_sys i2c_i801 i2c_algo_bit lpc_ich rng_core i2c_core shpchp w83627hf hwmon_vid bridge stp llc loop slip slhc tun fuse autofs4 ext4 crc16 mbcache jbd2 sg sd_mod crc_t10dif crct10dif_generic crct10dif_common ata_generic 8139too ata_piix ehci_pci uhci_hcd ahci libahci ehci_hcd libata scsi_mod 8139cp r8169 mii usbcore usb_common [587134.548195] CPU: 0 PID: 0 Comm: swapper Not tainted 3.16.0-4-586 #1 Debian 3.16.7-ckt11-1+deb8u4 [587134.548195] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080012 12/22/2008 [587134.548195] task: c1592500 ti: c1584000 task.ti: c1584000 [587134.548195] EIP: 0060:[] EFLAGS: 00210896 CPU: 0 [587134.548195] EIP is at smp_apic_timer_interrupt+0x24/0x50 [587134.548195] EAX: 0001 EBX: c158beec ECX: c1585f4c EDX: c1585f4c [587134.548195] ESI: c1584001 EDI: c1585fed EBP: c1585f94 ESP: c1585f48 [587134.548195] DS: 007b ES: 007b FS: GS: 00e0 SS: 0068 [587134.548195] CR0: 8005003b CR2: 0001 CR3: 34b8a000 CR4: 0790 [587134.548195] Stack: [587134.548195] c1425474 c1585fec c1584000 c1584000 c1585fec c1585f94 [587134.548195] 0002007b 08be007b 08be 00e0 ff10 c102f1a2 0060 00200246 [587134.548195] c1009d74 c1585fec c1584000 c1585f9c c100a54e c1585fd8 c1066b40 c1585fec [587134.548195] Call Trace: [587134.548195] [] ? apic_timer_interrupt+0x34/0x40 [587134.548195] [] ? native_safe_halt+0x2/0x10 [587134.548195] [] ? default_idle+0x14/0x90 [587134.548195] [] ? arch_cpu_idle+0xe/0x10 [587134.548195] [] ? cpu_startup_entry+0x230/0x370 [587134.548195] [] ? start_kernel+0x3f2/0x3f7 [587134.548195] [] ? set_init_arg+0x3f/0x45 [587134.548195] Code: ff ff eb 80 66 90 90 55 89 e5 53 3e 8d 74 26 00 8b 0d 00 ee 59 c1 31 d2 8b 1d 48 39 59 c1 a3 48 39 59 c1 b8 b0 00 00 00 ff 91 a4 <00> 00 00 e8 d4 a4 c1 ff e8 df f6 bf ff e8 2a a5 c1 ff 89 1d 48 [587134.548195] EIP: [] smp_apic_timer_interrupt+0x24/0x50 SS:ESP 0068:c1585f48 [587134.548195] CR2: 0001 [587134.548195] ---[ end trace c2ab876b17f6fd20 ]--- [587134.548195] Kernel panic - not syncing: Attempted to kill the idle task! [587134.548195] Kernel Offset: 0x0 from 0xc100 (relocation range: 0xc000-0xf7ffdfff) [587134.548195] Rebooting in 300 seconds.. ** Model information not available ** Loaded
Bug#801324: marked as done (linux-image-4.2.0-1-686-pae: System has frozen twice since upgrading to linux-image-4.2.0-1-686-pae)
Your message dated Fri, 30 Apr 2021 21:42:07 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #801324, regarding linux-image-4.2.0-1-686-pae: System has frozen twice since upgrading to linux-image-4.2.0-1-686-pae 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.) -- 801324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.2.1-2 Severity: grave Justification: renders package unusable "apt-get dist-upgrade" installed the kernel linux-image-4.2.0-1-686-pae (4.2.1-2) on Sun Oct 4 2015, 12:06:36. Since then, the system has frozen twice. When frozen, the system is completely unresponsive on both keyboard, mouse and on the network (doesn't even respond to ping). I need to hold in the power button for 5-10 seconds to let BIOS reboot it. I will try rebooting into the previous kernel, to see if that makes the system stop crashing. -- Package-specific info: ** Version: Linux version 4.2.0-1-686-pae (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2.1-2 (2015-09-27) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-686-pae root=UUID=c666ea19-ecb5-4300-b375-d9e2c748e97a ro quiet ** Not tainted ** Kernel log: [9.333445] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 11.390628] systemd[1]: Failed to insert module 'kdbus': Function not implemented [ 11.555676] systemd[1]: systemd 226 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) [ 11.555935] systemd[1]: Detected architecture x86. [ 11.566829] systemd[1]: Set hostname to . [ 14.518789] systemd[1]: rpcbind.target: Dependency Before=rpcbind.target dropped [ 15.354010] systemd[1]: accounts-daemon.service: Cannot add dependency job, ignoring: Unit accounts-daemon.service is masked. [ 15.355465] systemd[1]: Listening on udev Control Socket. [ 15.355839] systemd[1]: Created slice System Slice. [ 15.356048] systemd[1]: Created slice User and Session Slice. [ 15.356088] systemd[1]: Reached target Encrypted Volumes. [ 15.357369] systemd[1]: Starting Increase datagram queue length... [ 15.357712] systemd[1]: Listening on Journal Socket. [ 15.359418] systemd[1]: Mounting Huge Pages File System... [ 15.361372] systemd[1]: Mounting POSIX Message Queue File System... [ 15.361763] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 15.363522] systemd[1]: Starting Create list of required static device nodes for the current kernel... [ 15.363744] systemd[1]: Listening on fsck to fsckd communication Socket. [ 15.365509] systemd[1]: Starting LSB: Set keymap... [ 15.366323] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 15.366752] systemd[1]: Listening on Journal Audit Socket. [ 15.366827] systemd[1]: Reached target Slices. [ 15.366915] systemd[1]: Listening on Journal Socket (/dev/log). [ 15.367034] systemd[1]: Listening on udev Kernel Socket. [ 15.367167] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 15.367257] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 15.435947] systemd[1]: Starting Load Kernel Modules... [ 15.436510] systemd[1]: Created slice system-getty.slice. [ 15.436583] systemd[1]: Reached target Remote File Systems (Pre). [ 15.445534] systemd[1]: Created slice system-postgresql.slice. [ 15.446836] systemd[1]: Mounting Debug File System... [ 15.672228] systemd[1]: Started Create list of required static device nodes for the current kernel. [ 15.674067] systemd[1]: Starting Create Static Device Nodes in /dev... [ 16.090486] systemd[1]: Mounted POSIX Message Queue File System. [ 16.090582] systemd[1]: Mounted Huge Pages File System. [ 16.090627] systemd[1]: Mounted Debug File System. [ 16.924627] lp: driver loaded but no devices found [ 17.047346] ppdev: user-space parallel port driver [ 17.092383] parport_pc 00:03: reported by Plug and Play ACPI [ 17.092476] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP] [ 17.130410] systemd[1]: Started Create Static Device Nodes in /dev. [ 17.132446] systemd[1]: Starting udev Kernel Device Manager... [ 17.188289] lp0: using parport0 (interrupt-driven). [ 17.616267] loop: module loaded [ 17.617430] systemd[1]: Started Load Kernel Modules. [ 17.619178] systemd[1]: Starting
Bug#800842: marked as done (linux-image-4.2.0-1-amd64: Kernel Oops when irqbalance is enabled)
Your message dated Fri, 30 Apr 2021 21:40:23 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #800842, regarding linux-image-4.2.0-1-amd64: Kernel Oops when irqbalance is enabled 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.) -- 800842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.2.1-2 Severity: important Hi, when irqblanace (installed version 1.0.6-3) is enabled, linux-image-4.2.0-1-amd64 oopses ~15 seconds after boot) This Oops is new with linux-image-4.2.0-1-amd64: it did not happen with previous kernel versions. It happens on both (independent) installations on this machine. Disabling irqbalance seems to fix the issue. Since rebooting with irqbalance disenabled, no Oops occurred. The attached file give the dmesg information of the oops'ed kernel. Thanks for maintaining the Linux kenel in Debian Peter PS: I reported the bug against linux, because I think a kernel should never oops. Feeld free to re-assign as you think appropriate. -- Package-specific info: ** Version: Linux version 4.2.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2.1-2 (2015-09-27) ** Command line: BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 root=LABEL=root1 ro noapic quiet 3 ** Not tainted ** Kernel log: see attached dmesg log ** Model information sys_vendor: FUJITSU product_name: ESPRIMO P920 product_version: chassis_vendor: FUJITSU chassis_version: C$WX01 bios_vendor: FUJITSU // American Megatrends Inc. bios_version: V4.6.5.4 R1.10.0 for D3222-A1x board_vendor: FUJITSU board_name: D3222-A1 board_version: S26361-D3222-A1 ** Loaded modules: ecb rfcomm ebtable_filter ebtables binfmt_misc cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats bnep nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables xt_limit nf_log_ipv6 nf_log_common xt_LOG xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables ftdi_sio pl2303 usbserial uas uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core usb_storage snd_usb_audio v4l2_common snd_usbmidi_lib videodev snd_rawmidi snd_seq_device media btusb btrtl btbcm btintel bluetooth rfkill tpm_infineon deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx2 camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cbc cmac xcbc rmd160 sha512_ssse3 sha512_generic crypto_null af_key xfrm_algo x86_pkg_temp_thermal intel_powerclamp intel_rapl iosf_mbi kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel iTCO_wdt iTCO_vendor_support ppdev snd_hda_codec_hdmi sha256_ssse3 sha256_generic hmac drbg ansi_cprng aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd evdev psmouse snd_hda_codec_realtek snd_hda_codec_generic serio_raw pcspkr i2c_i801 sg i915 lpc_ich snd_hda_intel mfd_core snd_hda_codec shpchp snd_hda_core snd_hwdep drm_kms_helper snd_pcm drm snd_timer mei_me snd mei soundcore i2c_algo_bit fujitsu_laptop parport_pc parport 8250_fintek battery tpm_tis processor video tpm button hid_generic usbhid hid sch5636 sch56xx_common coretemp loop ecryptfs autofs4 ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod ahci libahci crc32c_intel libata xhci_pci ehci_pci xhci_hcd ehci_hcd scsi_mod e1000e usbcore ptp pps_core usb_common fan thermal thermal_sys ** Network interface configuration: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.2.0-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.57 ii initramfs-tools [linux-initramfs-tool] 0.120 ii kmod21-1 ii linux-base 4.0 Versions of packages linux-image-4.2.0-1-amd64 recommends: ii firmware-linux-free 3.4 ii irqbalance 1.0.6-3 Versions of packages linux-image-4.2.0-1-amd64 suggests: ii
Bug#800949: marked as done (linux-image-4.2.0-1-amd64: Staged driver r8192e_pci doesn't work in amd64 arch)
Your message dated Fri, 30 Apr 2021 21:41:01 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #800949, regarding linux-image-4.2.0-1-amd64: Staged driver r8192e_pci doesn't work in amd64 arch 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.) -- 800949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-4.2.0-1-amd64 Version: 4.2.1-2 Severity: important Tags: upstream Dear Maintainer, Recently I installed Debian testing (stretch) AMD64 in a Samsung R720H. This laptop comes with a RTL8192E/RTL8192SE Wireless LAN Controller. As described at: https://wiki.debian.org/rtl819x#r8192e_pci As described, I have also installed the package "firmware-realtek": https://wiki.debian.org/rtl819x#Installation The kernel module used is the staged r8192e_pci The module loads, finds networks and connects to the one I have configured with WPA-PSK. However, when starting to use the network it goes really slow and quick enough it gets stalled. The /var/log/syslog starts growing fast with lots of bogus messages from the driver. Rebooting doesn't help. Unloading the module and reloading it again doesn't help either. The situation is easily reproducible: 100%. I spent a lot of time looking for a solution to this problem, looking for alternative drivers, etc. No solution. The only tip I go was from an Ubuntu forum saying that the problem was solved when moving from AMD64 to i386. I did that. Wiped the computer and re-installed again with i386 as arch. The problem is solved. Current working package: linux-image-4.2.0-1-586 --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#800970: marked as done (linux: backport of r8169 driver)
Your message dated Fri, 30 Apr 2021 21:41:45 +0200 with message-id and subject line Re: linux: backport of r8169 driver has caused the Debian Bug report #800970, regarding linux: backport of r8169 driver 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.) -- 800970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux Version: 3.16.7-ckt11-1+deb8u4 Severity: important The current jessie kernel lacks proper support for the RTL8168/8111H onboard NICs Support for them was added in: commit 76e1d0b8988188956dac091441c1492a79a342666 commit a3bf5c429eb5f5ec4d364d51dfa8855efcc005f8 Please consider backporting support and the corresponding firmware for these devices to stable so that they can be used properly. Thanks, Markus --- End Message --- --- Begin Message --- Am Mon, Oct 05, 2015 at 04:02:35PM +0200 schrieb Markus Schade: > Package: linux > Version: 3.16.7-ckt11-1+deb8u4 > Severity: important > > The current jessie kernel lacks proper support for the RTL8168/8111H > onboard NICs > > Support for them was added in: > commit 76e1d0b8988188956dac091441c1492a79a342666 > commit a3bf5c429eb5f5ec4d364d51dfa8855efcc005f8 > > Please consider backporting support and the corresponding firmware for > these devices to stable so that they can be used properly. > Thanks, jessie is long out of support, closing. Cheers, Moritz--- End Message ---
Bug#800792: marked as done (linux-image-4.2.0-1-amd64 hangs during boot at network)
Your message dated Fri, 30 Apr 2021 21:40:13 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #800792, regarding linux-image-4.2.0-1-amd64 hangs during boot at network 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.) -- 800792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-4.2.0-1-amd64 Version: 4.2.1-2 Severity: important Dear maintainer-team, there is a very annoying problem, I discovered with all kernels since version 4.X. When the system boots up and the network shall be activated, the system hangs for a long time (about 2 minutes). Then the systemd-counter shows up and after the waiting time (about the mentioned 2 minutes), the system continous booting. On my slower EEEPC netbook, this waiting time is longer. I rechecked everything, and I can proove, that the latest 3.X kernel from debian does not show this behaviour. This behaviour appears since all kernels with version 4.0 and higher. Really, this is a really annoying bug, especially, when you have often to boot the system (in my case, because I walk from customer to customer with my netbook). I suppose, something has changed in the network device module between 3.16 and 4.X. It would be nice, if you could take a look at it. maybe this is easy to be fixed. Thank you very much for reading this and all your help. Best regards Hans-J. Ullrich --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#800899: marked as done (usbip isochronous usb microphone detaches on use)
Your message dated Fri, 30 Apr 2021 21:40:33 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #800899, regarding usbip isochronous usb microphone detaches on use 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.) -- 800899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: usbip Version: 2.0+4.2-1 Severity: important Dear Maintainer, I am trying to use a USB microphone with usbip, between two physical machines both running Linux 3.16.0-4-amd64. The machines are connected via gigabit ethernet. The USB device can be bound, attached, and it shows up in lsusb on the client machine, but as soon as I try to use it (or run "usbip port") the device disappears. A USB stick (not isochonous) works without issues. On the server side, I run # modprobe usbip-core && modprobe usbip-host # usbip list -l | grep 3-3.1.3 -A 2 - busid 3-3.1.3 (0d8c:016c) C-Media Electronics, Inc. : unknown product (0d8c:016c) # usbip -d bind -b 3-3.1.3 usbip: debug: usbip.c:141:[run_command] running command: `bind' usbip: info: bind device on busid 3-3.1.3: complete # usbipd -D On the client side, I run # modprobe usbip-core && modprobe usbip-host && modprobe vhci-hcd # lsusb | grep 'Bus 011' Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usbip attach -r 192.168.1.100 -b 3-3.1.3 # lsusb | grep 'Bus 011' Bus 011 Device 002: ID 0d8c:016c C-Media Electronics, Inc. # new device! Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usbip --debug port usbip: debug: .../src/usbip.c:141:[run_command] running command: `port' libusbip: debug: .../libsrc/vhci_driver.c:242:[usbip_vhci_driver_open] available ports: 7 libusbip: debug: .../libsrc/vhci_driver.c:71:[parse_status] port 0 status 6 speed 2 devid 30028 libusbip: debug: .../libsrc/vhci_driver.c:72:[parse_status] socket 8802019f2a40 lbusid 11-1 libusbip: debug: .../libsrc/vhci_driver.c:26:[imported_device_init] udev_device_new_from_subsystem_sysname failed: 11-1 libusbip: debug: .../libsrc/vhci_driver.c:91:[parse_status] imported_device_init failed usbip: error: open vhci_driver usbip: error: list imported devices # lsusb | grep 'Bus 011' Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # it's gone # In other words, the USB device disappears as soon as I try to query it. I'm pretty sure it has something to do with the fact that this is an isochronous USB device. I can share a Lexar USB stick with no issues, list the port, mount the filesystem on it, etc; here's what that looks like: # usbip port Imported USB devices Port 00: at High Speed(480Mbps) unknown vendor : unknown product (05dc:a81d) 11-1 -> usbip://192.168.1.133:3240/3-3.1.4 -> remote bus/dev 003/044 It's not just the "port" listing that fails with the microphone, if I try to use the device in any way the same thing happens. Note that this microphone works correctly if I plug it directly into the client system. The best clue I have for this bug is the server's dmesg, which has: [1898124.688515] vhci_hcd: module is from the staging directory, the quality is unknown, you have been warned. [1898124.689777] vhci_hcd vhci_hcd: USB/IP Virtual Host Controller [1898124.689781] vhci_hcd vhci_hcd: new USB bus registered, assigned bus number 5 [1898124.690751] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002 [1898124.690754] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1898124.690756] usb usb5: Product: USB/IP Virtual Host Controller [1898124.690759] usb usb5: Manufacturer: Linux 3.16.0-4-amd64 vhci_hcd [1898124.690761] usb usb5: SerialNumber: vhci_hcd [1898124.690919] hub 5-0:1.0: USB hub found [1898124.690928] hub 5-0:1.0: 8 ports detected [1898124.691151] vhci_hcd: USB/IP 'Virtual' Host Controller (VHCI) Driver v1.0.0 [1898128.327590] usbip-host 3-3.1.3: stub up [1898128.328428] usbip-host 3-3.1.3: recv a header, 0 [1898128.413139] usbip-host 3-3.1.3: reset full-speed USB device number 40 using xhci_hcd [1898128.513687] usbip-host 3-3.1.3: device reset [1898132.871792] usbip-host 3-3.1.3: stub up [1898133.231902] usbip-host 3-3.1.3: usb_set_interface done: inf 1 alt 1 [1898133.233559] usbip-host 3-3.1.3: usb_set_interface done: inf 1 alt 0 [1898133.234173] usbip-host 3-3.1.3: usb_set_interface done: inf 2 alt 1 [1898133.235850] usbip-host 3-3.1.3: usb_set_interface done: inf 2 alt 0 [1898133.237724] usbip-host 3-3.1.3: endpoint 0 is stalled [1898133.238363]
Bug#799838: marked as done (linux-image-3.16.0-4-amd64: NFS rename hangs for 15 seconds when target has been read on another machine)
Your message dated Fri, 30 Apr 2021 21:39:46 +0200
with message-id
and subject line Closing this bug
has caused the Debian Bug report #799838,
regarding linux-image-3.16.0-4-amd64: NFS rename hangs for 15 seconds when
target has been read on another machine
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.)
--
799838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt11-1+deb8u4
Severity: important
At my lab, with NFS accounts, some machines have been reinstalled
with Debian 8. and on these machines, NFS rename sometimes hangs
for 15 seconds (the NFS server isn't particularly loaded), while
this problem never occurs under Debian 7, and still doesn't occur
on a machine that still has Debian 7. So, this is a client-side
issue.
This can be seen at the end of strace -rt output of the mv command:
[...]
4133 0.000112 rename("global/mailcap", "/home/vlefevre/.mailcap") = 0
4133 15.054451 lseek(0, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
4133 0.000206 close(0)= 0
4133 0.000196 close(1)= 0
4133 0.97 munmap(0x7f00144b3000, 4096) = 0
4133 0.80 close(2)= 0
4133 0.000108 exit_group(0) = ?
4133 0.000311 +++ exited with 0 +++
Note: I've seen that there has been some change in the kernel about
rename and a 15-second timeout, at least:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8478eaa16e701ecfe054b62ec764bc1291b79e19
-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19)
** Command line:
root=/dev/nfs initrd=nfs/jessie/initrd.img-aufs aufs=/dev/sda1
nfsroot=140.77.14.15:/target_jessie ip=:eth0:dhcp rw
BOOT_IMAGE=nfs/jessie/vmlinuz
** Tainted: C (1024)
* Module from drivers/staging has been loaded.
** Kernel log:
[ 11.687283] EDAC amd64: MC: 6: 0MB 7: 0MB
[ 11.687404] EDAC amd64: using x8 syndromes.
[ 11.687508] EDAC amd64: MCT channel count: 2
[ 11.687647] EDAC amd64: CS0: Registered DDR3 RAM
[ 11.687753] EDAC amd64: CS1: Registered DDR3 RAM
[ 11.687858] EDAC amd64: CS2: Registered DDR3 RAM
[ 11.687966] EDAC amd64: CS3: Registered DDR3 RAM
[ 11.691377] EDAC MC4: Giving out device to module amd64_edac controller
F15h: DEV :00:1c.2 (INTERRUPT)
[ 11.691809] EDAC amd64: DRAM ECC enabled.
[ 11.692061] EDAC amd64: F15h detected (node 5).
[ 11.692307] EDAC MC: DCT0 chip selects:
[ 11.692312] EDAC amd64: MC: 0: 4096MB 1: 4096MB
[ 11.692421] EDAC amd64: MC: 2: 4096MB 3: 4096MB
[ 11.692539] EDAC amd64: MC: 4: 0MB 5: 0MB
[ 11.692654] EDAC amd64: MC: 6: 0MB 7: 0MB
[ 11.692764] EDAC MC: DCT1 chip selects:
[ 11.692767] EDAC amd64: MC: 0: 4096MB 1: 4096MB
[ 11.692879] EDAC amd64: MC: 2: 4096MB 3: 4096MB
[ 11.692990] EDAC amd64: MC: 4: 0MB 5: 0MB
[ 11.693103] EDAC amd64: MC: 6: 0MB 7: 0MB
[ 11.693216] EDAC amd64: using x8 syndromes.
[ 11.693328] EDAC amd64: MCT channel count: 2
[ 11.693478] EDAC amd64: CS0: Registered DDR3 RAM
[ 11.693596] EDAC amd64: CS1: Registered DDR3 RAM
[ 11.693708] EDAC amd64: CS2: Registered DDR3 RAM
[ 11.693813] EDAC amd64: CS3: Registered DDR3 RAM
[ 11.700187] EDAC MC5: Giving out device to module amd64_edac controller
F15h: DEV :00:1d.2 (INTERRUPT)
[ 11.700337] EDAC amd64: DRAM ECC enabled.
[ 11.700490] EDAC amd64: F15h detected (node 6).
[ 11.700744] EDAC MC: DCT0 chip selects:
[ 11.700749] EDAC amd64: MC: 0: 4096MB 1: 4096MB
[ 11.700854] EDAC amd64: MC: 2: 4096MB 3: 4096MB
[ 11.700959] EDAC amd64: MC: 4: 0MB 5: 0MB
[ 11.701108] EDAC amd64: MC: 6: 0MB 7: 0MB
[ 11.701258] EDAC MC: DCT1 chip selects:
[ 11.701262] EDAC amd64: MC: 0: 4096MB 1: 4096MB
[ 11.701419] EDAC amd64: MC: 2: 4096MB 3: 4096MB
[ 11.701581] EDAC amd64: MC: 4: 0MB 5: 0MB
[ 11.701690] EDAC amd64: MC: 6: 0MB 7: 0MB
[ 11.701795] EDAC amd64: using x8 syndromes.
[ 11.701906] EDAC amd64: MCT channel count: 2
[ 11.702064] EDAC amd64: CS0: Registered DDR3 RAM
[ 11.702167] EDAC amd64: CS1: Registered DDR3 RAM
[ 11.702273] EDAC amd64: CS2: Registered DDR3 RAM
[ 11.702398] EDAC amd64: CS3: Registered DDR3 RAM
[ 11.708243] EDAC MC6: Giving out device to module amd64_edac controller
F15h: DEV :00:1e.2 (INTERRUPT)
[ 11.708665] EDAC amd64: DRAM ECC enabled.
[ 11.708896] EDAC amd64:
Bug#798512: marked as done (linux-image-3.16.0-4-amd64: e1000e hangs with Intel I217-LM)
Your message dated Fri, 30 Apr 2021 21:38:46 +0200 with message-id and subject line Re: Bug#798512: linux-image-3.16.0-4-amd64: e1000e hangs with Intel I217-LM has caused the Debian Bug report #798512, regarding linux-image-3.16.0-4-amd64: e1000e hangs with Intel I217-LM 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.) -- 798512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1+deb8u3 Severity: important Hi, I'm encountering an issue with the current jessie kernel on a Dell Optiplex 9020 equipped with a 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04) The NIC hangs under some conditions. Those conditions are not completely clear: it occurs when downloading packages from this machine to several (5) machines, but I couldn't trigger it using simple nuttcp data transfers). I've confirmed that the backports kernel (4.1.3-1~bpo8+1) is _not_ affected. Dmesg output during the hangs: [ 876.069592] e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH <6> TDT <33> next_to_use <33> next_to_clean<1> buffer_info[next_to_clean]: time_stamp <10002311a> next_to_watch<6> jiffies <10002334d> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> [ 878.067868] e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH <6> TDT <33> next_to_use <33> next_to_clean<1> buffer_info[next_to_clean]: time_stamp <10002311a> next_to_watch<6> jiffies <100023541> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> [ 880.066139] e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH <6> TDT <33> next_to_use <33> next_to_clean<1> buffer_info[next_to_clean]: time_stamp <10002311a> next_to_watch<6> jiffies <100023735> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> [ 882.064406] e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH <6> TDT <33> next_to_use <33> next_to_clean<1> buffer_info[next_to_clean]: time_stamp <10002311a> next_to_watch<6> jiffies <100023929> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> [ 884.062675] e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH <6> TDT <33> next_to_use <33> next_to_clean<1> buffer_info[next_to_clean]: time_stamp <10002311a> next_to_watch<6> jiffies <100023b1d> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> [ 884.074285] [ cut here ] [ 884.074297] WARNING: CPU: 0 PID: 0 at /build/linux-ELRFVQ/linux-3.16.7-ckt11/net/sched/sch_generic.c:264 dev_watchdog+0x236/0x240() [ 884.074299] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out [ 884.074360] Modules linked in: xt_nat xt_mac xt_pkttype ipt_REJECT xt_tcpudp xt_conntrack xt_LOG iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables x_tables nfnetlink_queue nfnetlink_log nfnetlink bluetooth 6lowpan_iphc rfkill binfmt_misc hid_generic usbhid hid snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm_intel kvm crc32_pclmul ghash_clmulni_intel iTCO_wdt iTCO_vendor_support evdev snd_hda_codec_realtek snd_hda_codec_generic aesni_intel dcdbas aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse pcspkr serio_raw i2c_i801 lpc_ich snd_hda_intel drm_kms_helper mfd_core snd_hda_controller drm battery snd_hda_codec snd_hwdep i2c_algo_bit snd_pcm i2c_core snd_timer snd mei_me shpchp soundcore [ 884.074391] mei video processor button
Bug#799122: marked as done (xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes)
Your message dated Fri, 30 Apr 2021 21:39:34 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #799122, regarding xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes 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.) -- 799122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important A few minutes after starting a domU, network access is no longer possible from and to it. This does not always happen and is not easily reproducible, but seems to occur in all newly started domUs from some point in time on. However, also restarting the dom0 does not necessarily prevent the problem. At the moment when the network in the domU completely stops working, there is the error message [2178752.854380] vif vif-33-0 vif33.0: Guest Rx stalled visible in dmesg in the dom0. It is sometimes possible to for example ping the domU for a longer time than pinging any host from the domU. Also pings may still be possible for a few minutes, while SSH sessions do no longer work. We tested the current lenny kernel linux-image-3.16.0-4-amd64 as well as the backport linux-image-4.1.0-0.bpo.1-amd64 on the dom0 as well as the domU. The problem happens with newly created domUs via 'xen-create-image', as well as with older domUs which have been migrated from a debian wheezy dom0. It happens with the vif-route as well as the vif-bridge script in the domU configuration. When the network stops working, the ARP tables are no longer filled on dom0 and domU, for example: Address HWtype HWaddress Flags MaskIface x.y.z.v (incomplete) vif33.0 -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-0.bpo.1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) xen-hypervisor-4.4-amd64 depends on no packages. Versions of packages xen-hypervisor-4.4-amd64 recommends: ii xen-utils-4.4 4.4.1-9+deb8u1 xen-hypervisor-4.4-amd64 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#797748: marked as done (4.2.0-trunk:"AMD-Vi: Event logged Error".)
Your message dated Fri, 30 Apr 2021 21:37:43 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #797748, regarding 4.2.0-trunk:"AMD-Vi: Event logged Error". 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.) -- 797748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.2-1~exp1 Severity: important Dear Maintainer, Booting with linux-image-4.2.0-trunk-amd64, logged too many message beginning "AMD-Vi: Event logged Error" , occupied console and filled to /var/log. I'm using AMD FX-8320 with ASROCK 990FX Extreme4 mainboard. I did workaround of this : edit /etc/default/grub and set "iommu=soft" to GRUB_CMDLINE variable. Please fix this issue, do not print this message with these board environment. Regards, Ohta. -- Package-specific info: ** Version: Linux version 4.2.0-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2-1~exp1 (2015-08-31) ** Command line: BOOT_IMAGE=/vmlinuz-4.2.0-trunk-amd64 root=UUID=040b41b0-26fe-4064-af0a-3619f3112096 ro quiet systemd.debug-shell iommu=soft ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Model information sys_vendor: To Be Filled By O.E.M. product_name: To Be Filled By O.E.M. product_version: To Be Filled By O.E.M. 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: P2.70 board_vendor: ASRock board_name: 990FX Extreme4 board_version: ** Loaded modules: bnep nfnetlink_queue nfnetlink_log nfnetlink bluetooth rfkill pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc snd_hrtimer snd_seq cpufreq_conservative cpufreq_stats cpufreq_userspace cpufreq_powersave pl2303 usbserial joydev xfs libcrc32c hid_pl ff_memless hid_generic usbhid hid uas usb_storage jfs nls_utf8 nls_cp437 vfat fat kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel radeon ghash_clmulni_intel sha256_ssse3 sha256_generic tg3 hmac drbg ansi_cprng aesni_intel evdev aes_x86_64 mxm_wmi lrw gf128mul ptp glue_helper ttm pps_core ablk_helper snd_hda_codec_realtek drm_kms_helper mxl301rf efi_pstore drm qm1d1c0042 snd_hda_codec_hdmi snd_hda_codec_generic tc90522 ohci_pci earth_pt3 dvb_core psmouse cryptd serio_raw ata_generic sg pata_marvell libphy efivars i2c_algo_bit sp5100_tco fam15h_power k10temp xhci_pci snd_hda_intel ehci_pci snd_hda_codec edac_mce_amd snd_hda_core ohci_hcd xhci_hcd edac_core ehci_hcd i2c_piix4 shpchp acpi_cpufreq processor button floppy thermal_sys 8250_fintek wmi cuse fuse w83627ehf hwmon_vid snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device usbcore usb_common snd_dummy snd_pcm snd_timer snd soundcore loop parport_pc ppdev lp parport efivarfs autofs4 overlay ext4 crc16 mbcache jbd2 md_mod sr_mod cdrom sd_mod ahci libahci libata scsi_mod ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] (rev 02) Subsystem: ASRock Incorporation Device [1849:5a14] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD/ATI] RD990 I/O Memory Management Unit (IOMMU) [1002:5a23] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD990 I/O Memory Management Unit (IOMMU) [1002:5a23] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16] (prog-if 00 [Normal decode]) 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:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) [1002:5a18] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
Bug#797471: marked as done (XHCI_TRUST_TX_LENGTH quirk spams syslog)
Your message dated Fri, 30 Apr 2021 21:37:33 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #797471, regarding XHCI_TRUST_TX_LENGTH quirk spams syslog 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.) -- 797471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-3.16.0-4-amd64 Version: 3.16.7-ckt11-1+deb8 Severity: important I'm getting tons of the following messages in the syslog: [19395.539218] handle_tx_event: 715 callbacks suppressed [19395.539225] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.567179] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.595169] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.607128] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.62] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.615106] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.619112] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.623102] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.627091] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19395.631098] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.569069] handle_tx_event: 716 callbacks suppressed [19400.569085] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.573062] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.577054] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.581038] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.585042] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.589036] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.593031] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.597025] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.601020] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? [19400.605016] xhci_hcd :04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Has the following patch been applied: http://www.spinics.net/lists/linux-usb/msg111798.html ? --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#798494: marked as done (iw: Can't connect to wireless router when running 4.1 kernel)
Your message dated Fri, 30 Apr 2021 21:37:56 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #798494, regarding iw: Can't connect to wireless router when running 4.1 kernel 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.) -- 798494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iw Version: 3.17-1 Severity: important Dear Maintainer, My network manager (wicd) lost the ability to connect to my unsecured wireless router when I upgraded from the 3.16-0-4-686-pae kernel to the 4.1.0-1-686-pae kernel. It still works normally when I boot into the 3.16 kernel. This computer has a Qualcomm Atheros wireless adapter using the ath5k driver. See further details in the command line output below. On another computer of mine, wicd lost the ability to connect when upgrading from the 4.0.0-2-686-pae to the 4.1.0-1-686-pae kernel. (On this computer -- the one I'm preparing this bug report on -- I upgraded directly from the 3.16 kernel to the 4.1 kernel, so have not tested the wireless connection on this computer when running the 4.0 kernel.) On that other computer -- the one on which I lost wireless capability on the upgrade from the 4.0 to the 4.1 kernel -- I have an Intel Ultimate N Wifi Link 5300 adapter using the iwlwifi driver. Since I have the same problem with two different devices, I assume this problem is not specific to a particular adapter or driver. Sorry if I'm reporting this bug against the wrong package. From the command line I can't connect using either the iw or the iwconfig utilities, and I don't know how to narrow the problem down any further. Below are a series of commands that I ran under both the 3.16 and the 4.1 kernel with the corresponding terminal output, showing that both the iw and iwconfig commands successfully connect when running the 3.16 but fail when running the 4.1 kernel: ___ OUTPUT WHEN RUNNING THE 3.16 KERNEL: root@kitchencomp:/home# lspci -k 00:0d.0 Ethernet controller: Qualcomm Atheros AR5212/5213/2414 Wireless Network Adapter (rev 01) Subsystem: D-Link System Inc AirPlus DWL-G520 Wireless PCI Adapter (rev. B) Kernel driver in use: ath5k root@kitchencomp:/home# iw dev phy#0 Interface wlan0 ifindex 3 wdev 0x1 addr 00:11:95:92:61:bd ssid NETGEAR type managed channel 11 (2462 MHz), width: 20 MHz (no HT), center1: 2462 MHz root@kitchencomp:/home# ip link set wlan0 down root@kitchencomp:/home# iw dev phy#0 Interface wlan0 ifindex 3 wdev 0x1 addr 00:11:95:92:61:bd type managed root@kitchencomp:/home# ip link show wlan0 3: wlan0: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 00:11:95:92:61:bd brd ff:ff:ff:ff:ff:ff root@kitchencomp:/home# ip link set wlan0 up root@kitchencomp:/home# ip link show wlan0 3: wlan0: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 00:11:95:92:61:bd brd ff:ff:ff:ff:ff:ff root@kitchencomp:/home# iw dev wlan0 scan BSS 00:14:6c:20:29:3c(on wlan0) TSF: 185632755274 usec (2d, 03:33:52) freq: 2462 beacon interval: 100 TUs capability: ESS ShortPreamble ShortSlotTime (0x0421) signal: -80.00 dBm last seen: 72 ms ago Information elements from Probe Response frame: SSID: NETGEAR Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 12.0 24.0 36.0 DS Parameter set: channel 11 ERP: Extended supported rates: 9.0 18.0 48.0 54.0 root@kitchencomp:/home# iwconfig wlan0 essid NETGEAR root@kitchencomp:/home# iw dev wlan0 link Connected to 00:14:6c:20:29:3c (on wlan0) freq: 2462 RX: 24920 bytes (369 packets) TX: 6490 bytes (34 packets) signal: -84 dBm tx bitrate: 6.0 MBit/s bss flags: short-preamble short-slot-time dtim period:0 beacon int: 100 root@kitchencomp:/home# ip link set wlan0 down root@kitchencomp:/home# iw dev wlan0 link Not connected. root@kitchencomp:/home# ip link set wlan0 up root@kitchencomp:/home# iw dev wlan0 connect NETGEAR root@kitchencomp:/home# iw dev wlan0 link Connected to 00:14:6c:20:29:3c (on wlan0) SSID: NETGEAR freq: 2462 RX: 10726 bytes (130 packets) TX: 5439 bytes (29 packets) signal: -83
Bug#796485: marked as done (/lib/modules/4.1.0-1-amd64/kernel/drivers/net/wireless/rtlwifi/rtlwifi.ko: rtlwifi dereferencing NULL pointer when creating hotspot)
Your message dated Fri, 30 Apr 2021 21:37:07 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #796485, regarding /lib/modules/4.1.0-1-amd64/kernel/drivers/net/wireless/rtlwifi/rtlwifi.ko: rtlwifi dereferencing NULL pointer when creating hotspot 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.) -- 796485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.1.3-1 Severity: important File: /lib/modules/4.1.0-1-amd64/kernel/drivers/net/wireless/rtlwifi/rtlwifi.ko Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, When creating a hotspot with gnome-network-manager the rtlwifi seems to dereference a NULL pointer. This causes the kernel to go berserk and ultimately requires a hard reboot. I used to be able to create hotspots on the same hardware a while back. It only broke in the last 2 or 3 months. This bug seems to have been reported upstream: * https://bugzilla.kernel.org/show_bug.cgi?id=97441 * http://thread.gmane.org/gmane.linux.kernel.wireless.general/138645 I have attached the relevant part (as far as I can tell) of syslog in the `kernel log` section. Please let me know if you need anymore information, I'd be happy to help. Thanks a lot for your help. - -- Package-specific info: ** Version: Linux version 4.1.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-3) ) #1 SMP Debian 4.1.3-1 (2015-08-03) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.0-1-amd64 root=UUID=f58c2952-f542-4ad4-a9f6-63538d32a369 ro quiet init=/bin/systemd ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: dbus[916]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' nm-dispatcher: Dispatching action 'down' for wlan0 systemd[1]: Started Network Manager Script Dispatcher Service. NetworkManager[836]: Config: set interface ap_scan to 2 wpa_supplicant[973]: Using interface wlan0 with hwaddr e0:b9:a5:4a:49:f3 and ssid "shiki" NetworkManager[836]: wpa_supplicant stopped NetworkManager[836]: (wlan0): supplicant interface state: disconnected -> down kernel: [ 1128.378224] BUG: unable to handle kernel NULL pointer dereference at 0006 kernel: [ 1128.378240] IP: [] rtl_get_tcb_desc+0x59/0x760 [rtlwifi] kernel: [ 1128.378258] PGD 0 kernel: [ 1128.378263] Oops: 0002 [#1] SMP kernel: [ 1128.378270] Modules linked in: fuse ecb ctr ccm binfmt_misc pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp intel_rapl iosf_mbi nvidia(PO) coretemp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel joydev snd_hda_controller aesni_intel snd_hda_codec aes_x86_64 iTCO_wdt lrw snd_hda_core iTCO_vendor_support gf128mul snd_hwdep evdev glue_helper ablk_helper psmouse arc4 cryptd snd_pcm serio_raw rtl8192ce rtl_pci rtl8192c_common jmb38x_ms rtlwifi sg memstick mac80211 lpc_ich mei_me pcspkr mei i2c_i801 cfg80211 rfkill snd_timer snd mfd_core soundcore ac video battery button processor drm shpchp wmi ecryptfs parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod uas usb_storage hid_generic usbhid hid crc32c_intel ahci libahci libata firewire_ohci xhc i_pci ehci_pci scsi_mod sdhci_pci xhci_hcd ehci_hcd firewire_core sdhci crc_itu_t jme mmc_core mii usbcore usb_common thermal thermal_sys kernel: [ 1128.378385] CPU: 2 PID: 973 Comm: wpa_supplicant Tainted: P O4.1.0-1-amd64 #1 Debian 4.1.3-1 kernel: [ 1128.378387] Hardware name: CLEVO P150HMx/P150HMx, BIOS 4.6.4 04/22/2011 kernel: [ 1128.378388] task: 8800ca02e290 ti: 8800c930 task.ti: 8800c930 kernel: [ 1128.378389] RIP: 0010:[] [] rtl_get_tcb_desc+0x59/0x760 [rtlwifi] kernel: [ 1128.378393] RSP: 0018:8800c93037e8 EFLAGS: 00010086 kernel: [ 1128.378394] RAX: RBX: 880224e406a0 RCX: kernel: [ 1128.378395] RDX: RSI: 880224e41908 RDI: 880224e406a0 kernel: [ 1128.378396] RBP: 880206fd7c28 R08: R09: 08916d2d kernel: [ 1128.378397] R10: 0212 R11: 0004 R12: 8800be8b2da0 kernel: [ 1128.378399] R13: 0080 R14: 880224e413a0 R15: 8800be8b2da0 kernel: [ 1128.378400] FS:
Bug#797091: marked as done (iwl4965: Debian 8 Crash for wireless error)
Your message dated Fri, 30 Apr 2021 21:37:18 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #797091, regarding iwl4965: Debian 8 Crash for wireless error 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.) -- 797091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1+deb8u3 Severity: important File: iwl4965 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 3.16.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae root=UUID=04ece126-5320-48a6-b321-86a792a1ea5d ro quiet ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [ 86.171455] [] ? do_softirq_own_stack+0x22/0x30 [ 86.171459][] ? irq_exit+0x8d/0xa0 [ 86.171468] [] ? do_IRQ+0x45/0xd0 [ 86.171473] [] ? sched_clock+0x8/0x10 [ 86.171480] [] ? sched_clock_local+0x45/0x140 [ 86.171486] [] ? common_interrupt+0x33/0x38 [ 86.171493] [] ? kmsg_dump_get_buffer+0x27b/0x2f0 [ 86.171503] [] ? acpi_processor_preregister_performance+0x3de/0x42e [processor] [ 86.171510] [] ? cpuidle_enter_state+0x40/0xd0 [ 86.171517] [] ? cpu_startup_entry+0x2be/0x3b0 [ 86.171525] [] ? start_kernel+0x3d8/0x3dd [ 86.171531] [] ? set_init_arg+0x45/0x45 [ 86.171535] ---[ end trace 76b919d472df631c ]--- [ 86.171540] iwl data: : 00 00 55 55 72 72 6f 72 5f 64 65 66 61 75 6c 74 ..UUrror_default [ 86.171545] iwl data: 0010: 28 73 65 6c 66 2c 20 75 72 6c 2c 20 66 70 2c 0a (self, url, fp,. [ 86.367826] iwl4965 :0b:00.0: Microcode SW error detected. Restarting 0x200. [ 86.367844] iwl4965 :0b:00.0: Loaded firmware version: 228.61.2.24 [ 86.367870] iwl4965 :0b:00.0: Start IWL Error Log Dump: [ 86.367876] iwl4965 :0b:00.0: Status: 0x000213E4, count: 5 [ 86.368070] iwl4965 :0b:00.0: Desc Time data1 data2 line [ 86.368080] iwl4965 :0b:00.0: NMI_INTERRUPT_WDG(0x0004) 0980978064 0x0002 0x0263 208 [ 86.368085] iwl4965 :0b:00.0: pc blink1 blink2 ilink1 ilink2 hcmd [ 86.368092] iwl4965 :0b:00.0: 0x0046C 0x04B0C 0x004C2 0x006DE 0x04B22 0x43000A8 [ 86.368097] iwl4965 :0b:00.0: FH register values: [ 86.368118] iwl4965 :0b:00.0: FH49_RSCSR_CHNL0_STTS_WPTR_REG: 0X032f2000 [ 86.368141] iwl4965 :0b:00.0: FH49_RSCSR_CHNL0_RBDCB_BASE_REG: 0X0032f240 [ 86.368166] iwl4965 :0b:00.0:FH49_RSCSR_CHNL0_WPTR: 0X00f8 [ 86.368193] iwl4965 :0b:00.0: FH49_MEM_RCSR_CHNL0_CONFIG_REG: 0X80809000 [ 86.368213] iwl4965 :0b:00.0:FH49_MEM_RSSR_SHARED_CTRL_REG: 0X003c [ 86.368233] iwl4965 :0b:00.0: FH49_MEM_RSSR_RX_STATUS_REG: 0X0263 [ 86.368257] iwl4965 :0b:00.0: FH49_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [ 86.368280] iwl4965 :0b:00.0: FH49_TSSR_TX_STATUS_REG: 0X07ff0002 [ 86.368301] iwl4965 :0b:00.0: FH49_TSSR_TX_ERROR_REG: 0X [ 86.369824] iwl4965 :0b:00.0: Can't stop Rx DMA. [ 86.369889] ieee80211 phy0: Hardware restart was requested [ 87.064540] iwl4965 :0b:00.0: Read idx for DMA queue txq id (4), idx 48, is out of range [0-256] 34 34. [ 87.262411] iwl4965 :0b:00.0: Microcode SW error detected. Restarting 0x200. [ 87.262428] iwl4965 :0b:00.0: Loaded firmware version: 228.61.2.24 [ 87.262456] iwl4965 :0b:00.0: Start IWL Error Log Dump: [ 87.262462] iwl4965 :0b:00.0: Status: 0x000213E4, count: 5 [ 87.262648] iwl4965 :0b:00.0: Desc Time data1 data2 line [ 87.262653] iwl4965 :0b:00.0: NMI_INTERRUPT_WDG(0x0004) 0981872636 0x0002 0x0263 208 [ 87.262656] iwl4965 :0b:00.0: pc blink1 blink2 ilink1 ilink2 hcmd [ 87.262660] iwl4965 :0b:00.0: 0x0046C 0x04B0C 0x004C2 0x006DE 0x04B22 0x42100A8 [ 87.262663] iwl4965 :0b:00.0: FH
Bug#794810: marked as done (BUG: soft lockup - CPU#1 stuck for 22s! [alsa-sink-CMI87:4123])
Your message dated Fri, 30 Apr 2021 21:36:09 +0200
with message-id
and subject line Closing this bug
has caused the Debian Bug report #794810,
regarding BUG: soft lockup - CPU#1 stuck for 22s! [alsa-sink-CMI87:4123]
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.)
--
794810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt11-1
Severity: important
I encountered a lock-up several times in short succession:
1. lockup
2. reboot
3. lockup shortly after login
The system became unresponsive via the GUI, and I couldn't switch to
a terminal. I could log in remotely, though the system had very high
load, and was very slow to respond.
During the first lockup, I saw messages that referenced alsa, and a
particular audio driver (ALC66), so I disabled the onboard audio card,
and installed PCI card with a different chipset/driver, which I was
using when the 2nd lockup occured, FWIW.
Dmesg showed indication of soft lockups on various cores and a hard
lockup.
-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24)
** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/system-root ro quiet
** Tainted: O (4096)
* Out-of-tree module has been loaded.
** Kernel log:
[Thu Aug 6 14:10:13 2015] INFO: rcu_sched detected stalls on CPUs/tasks: { 0}
(detected by 4, t=5252 jiffies, g=246830, c=246829, q=7791)
[Thu Aug 6 14:10:13 2015] sending NMI to all CPUs:
[Thu Aug 6 14:10:13 2015] NMI backtrace for cpu 0
[Thu Aug 6 14:10:13 2015] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O
3.16.0-4-amd64 #1 Debian 3.16.7-ckt11-1
[Thu Aug 6 14:10:13 2015] Hardware name: BIOSTAR Group A780L3G/A780L3G, BIOS
080014 04/21/2010
[Thu Aug 6 14:10:13 2015] task: 8181a460 ti: 8180 task.ti:
8180
[Thu Aug 6 14:10:13 2015] RIP: 0010:[] []
finish_unlinks+0x53/0x3e0 [ohci_hcd]
[Thu Aug 6 14:10:13 2015] RSP: 0018:88022fc03e58 EFLAGS: 0046
[Thu Aug 6 14:10:13 2015] RAX: 8800ba3eda58 RBX: 8800bfb18030 RCX:
8800ba3eda78
[Thu Aug 6 14:10:13 2015] RDX: ba3b1120 RSI: 8800bfb18000 RDI:
8800ba3eda58
[Thu Aug 6 14:10:13 2015] RBP: 8800bfb18000 R08: R09:
[Thu Aug 6 14:10:13 2015] R10: 8800bfb18030 R11: 8800ba3b1000 R12:
8800bf5c0340
[Thu Aug 6 14:10:13 2015] R13: 8800ba3b1128 R14: 8801a066ca40 R15:
8800bfb18030
[Thu Aug 6 14:10:13 2015] FS: 7f65b682d9c0()
GS:88022fc0() knlGS:
[Thu Aug 6 14:10:13 2015] CS: 0010 DS: ES: CR0: 8005003b
[Thu Aug 6 14:10:13 2015] CR2: 7f562b143019 CR3: 0001f3ea7000 CR4:
07f0
[Thu Aug 6 14:10:13 2015] Stack:
[Thu Aug 6 14:10:13 2015] 8800ba3eda58 a00dbb48 8800bfb18020
8800bfb18008
[Thu Aug 6 14:10:13 2015] e9ca8802 8800ba3eda78 8800ba3ed800
c9c68000
[Thu Aug 6 14:10:13 2015] 0004 8800ba3eda58 0004
a01ff158
[Thu Aug 6 14:10:13 2015] Call Trace:
[Thu Aug 6 14:10:13 2015]
[Thu Aug 6 14:10:13 2015] [] ? ohci_irq+0x13d/0x3b0
[ohci_hcd]
[Thu Aug 6 14:10:13 2015] [] ? usb_hcd_irq+0x22/0x30
[usbcore]
[Thu Aug 6 14:10:13 2015] [] ?
handle_irq_event_percpu+0x35/0x190
[Thu Aug 6 14:10:13 2015] [] ? handle_irq_event+0x38/0x60
[Thu Aug 6 14:10:13 2015] [] ? handle_fasteoi_irq+0x83/0x150
[Thu Aug 6 14:10:13 2015] [] ? handle_irq+0x1d/0x30
[Thu Aug 6 14:10:13 2015] [] ? do_IRQ+0x49/0xe0
[Thu Aug 6 14:10:13 2015] [] ? common_interrupt+0x6d/0x6d
[Thu Aug 6 14:10:13 2015]
[Thu Aug 6 14:10:13 2015] [] ? cpuidle_enter_state+0x4f/0xc0
[Thu Aug 6 14:10:13 2015] [] ? cpuidle_enter_state+0x48/0xc0
[Thu Aug 6 14:10:13 2015] [] ? cpu_startup_entry+0x2f8/0x400
[Thu Aug 6 14:10:13 2015] [] ? start_kernel+0x492/0x49d
[Thu Aug 6 14:10:13 2015] [] ? set_init_arg+0x4e/0x4e
[Thu Aug 6 14:10:13 2015] [] ?
early_idt_handlers+0x120/0x120
[Thu Aug 6 14:10:13 2015] [] ?
x86_64_start_kernel+0x14d/0x15c
[Thu Aug 6 14:10:13 2015] Code: 48 8b 04 24 48 8b 68 20 48 85 ed 0f 84 d0 00
00 00 48 8b 44 24 28 48 89 44 24 10 eb 67 0f 1f 00 48 8b 04 24 83 b8 60 03 00
00 02 <0f> 85 e3 02 00 00 0f b7 44 24 26 66 3b 45 4a 78 32 48 8b 45 30
[Thu Aug 6 14:10:13 2015] NMI backtrace for cpu 5
[Thu Aug 6 14:10:13 2015] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G
Bug#795555: marked as done (linux-image-3.16.0-4-686-pae: cannot find /sbin/init (though probably can't find filesystem?))
Your message dated Fri, 30 Apr 2021 21:36:54 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #79, regarding linux-image-3.16.0-4-686-pae: cannot find /sbin/init (though probably can't find filesystem?) 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.) -- 79: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-3.16.0-4-686-pae Version: 3.16.7-ckt11-1+deb8u3 Severity: important Dear Maintainer, After upgrading from 3.10 to 3.16 my system fails to boot - it says it couldn't find /sbin/init and then dumps me into a "(initramfs)" prompt. I poked around and the md arrays are assembled, but the LVM volumes are not activated. I was able to activate them, so all the necessary tools appear to be there, so it's unclear what goes wrong. I tried both the 586 and 686-pae variants (this is on an old PII). Reverting back to 3.10 enables me to boot. -- System Information: Debian Release: 8.1 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.10-0.bpo.2-486 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages linux-image-3.16.0-4-686-pae depends on: ii debconf [debconf-2.0] 1.5.56 ii initramfs-tools [linux-initramfs-tool] 0.120 ii kmod18-3 ii linux-base 3.5 ii module-init-tools 18-3 Versions of packages linux-image-3.16.0-4-686-pae recommends: ii firmware-linux-free 3.3 ii irqbalance 1.0.6-3 ii libc6-i686 2.19-18 Versions of packages linux-image-3.16.0-4-686-pae suggests: pn debian-kernel-handbook ii grub-pc 2.02~beta2-22 pn linux-doc-3.16 --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#795060: marked as done (Latest Wheezy backport kernel prefers Infiniband mlx4_en over mlx4_ib, breaks existing installs)
Your message dated Fri, 30 Apr 2021 21:36:25 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #795060, regarding Latest Wheezy backport kernel prefers Infiniband mlx4_en over mlx4_ib, breaks existing installs 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.) -- 795060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-3.16.0-0.bpo.4-amd64 Version: 3.16.7-ckt11-1+deb8u2~bpo70+1 Severity: Critical Hello, We have a 2 node Supermicro chassis (2028TP-DC0FR) chassis with an onboard Mellanox ConnecX-3 HBA in production since last year. Both nodes are directly connected with a QFSP FDR cable. We use IPoIB (for DRBD) and thus load the mlx4_ib module and all the assorted other ones in /etc/modules at boot time. These are Wheezy machines, currently with the 3.16.7-ckt2-1~bpo70+1 kernel. Last week we got another (identical) one of these chassis and I installed Wheezy as well (we need pacemaker, which is sorely lacking in Jessie). This was with the 3.16.7-ckt11-1+deb8u2~bpo70+1 kernel and unlike in the past it proceeded to load the mlx4_en module automatically, created an eth2: interface and the ib0: interface was nowhere to be found. This was not only very unexpected, I was also under the impression that mlx4_en and mlx4_ib could be used in parallel, but even though mlx4_ib was loaded it did not work (the /sys/class/net/ib0 entry was not created). Booting into the stock Wheezy 3.2 kernel (which we also run on older machines with ConnectX-2 HBAs) resulted in the expected behavior, IB interface, no Ethernet. I'm also not seeing this on several other machines we use for Ceph with the current Jessie kernel, but to be fair they use slightly different (QDR, not FDR) ConnectX-3 HBAs. After doing a fake-install (blacklisting didn't work) like this: --- echo "install mlx4_en /bin/true" > /etc/modprobe.d/mlx4_en.conf depmod -a update-initramfs -u --- and rebooting I have IB running on 3.16.0-0.bpo.4-amd64 again as well. Given that the previous version works as expected and that Jessie is doing the "right" thing as well, I'd consider this a critical bug. Had I rebooted the older production cluster with 500,000 users on it into this kernel, the results would not have been pretty. Regards, Christian -- Christian BalzerNetwork/Systems Engineer ch...@gol.com Global OnLine Japan/Fusion Communications http://www.gol.com/ --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#795305: marked as done (missing support in jessie for broadcom 43341)
Your message dated Fri, 30 Apr 2021 21:36:40 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #795305, regarding missing support in jessie for broadcom 43341 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.) -- 795305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:linux Hi, please include firmware for Broadcom 43341. (I manually downloaded it as explained in https://wiki.debian.org/InstallingDebianOn/Asus/X205TA) Cheers, Christophe --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#793793: marked as done (linux-image-3.16.0-4-amd64: nouveau can make suspend fail: suspend failed with -16 [NV108 Quadro K610M])
Your message dated Fri, 30 Apr 2021 21:35:19 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #793793, regarding linux-image-3.16.0-4-amd64: nouveau can make suspend fail: suspend failed with -16 [NV108 Quadro K610M] 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.) -- 793793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1+deb8u2 Severity: important The last suspend of my ZBook 15 G2 failed. I didn't notice, and the laptop was switched off when I wanted to wake it up. The syslog file contains, starting from the initial Sleep event: Jul 27 10:12:12 zira systemd[1]: Reached target Sleep. Jul 27 10:12:12 zira systemd[1]: Starting Sleep. Jul 27 10:12:12 zira systemd[1]: Starting Suspend... Jul 27 10:12:12 zira systemd-sleep[15760]: Suspending system... Jul 27 10:12:12 zira kernel: [146468.895525] PM: Syncing filesystems ... done. Jul 27 10:12:12 zira kernel: [146468.937982] PM: Preparing system for mem sleep Jul 27 10:12:18 zira kernel: [146471.480812] (NULL device *): firmware: direct-loading firmware iwlwifi-7260-9.ucode Jul 27 10:12:18 zira kernel: [146471.480830] (NULL device *): firmware: direct-loading firmware intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq Jul 27 10:12:18 zira kernel: [146471.480835] Freezing user space processes ... (elapsed 0.001 seconds) done. Jul 27 10:12:18 zira kernel: [146471.482089] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. Jul 27 10:12:18 zira kernel: [146471.482830] PM: Entering mem sleep Jul 27 10:12:18 zira kernel: [146471.482897] Suspending console(s) (use no_console_suspend to debug) Jul 27 10:12:18 zira kernel: [146471.483179] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 27 10:12:18 zira kernel: [146471.485781] sd 0:0:0:0: [sda] Stopping disk Jul 27 10:12:18 zira kernel: [146471.687376] parport_pc 00:04: disabled Jul 27 10:12:18 zira kernel: [146471.687499] nouveau [ DRM] suspending console... Jul 27 10:12:18 zira kernel: [146471.687505] nouveau [ DRM] suspending display... Jul 27 10:12:18 zira kernel: [146471.687658] nouveau [ DRM] evicting buffers... Jul 27 10:12:18 zira kernel: [146471.692320] nouveau E[ PFIFO][:01:00.0] read fault at 0x00016c [PTE] from CE0/CE0 on channel 0x003fce4000 [DRM] Jul 27 10:12:18 zira kernel: [146471.692321] nouveau E[ PFIFO][:01:00.0] PCE0 engine fault on channel 0, recovering... Jul 27 10:12:18 zira kernel: [146471.932979] nouveau [ DRM] waiting for kernel channels to go idle... Jul 27 10:12:18 zira kernel: [146471.932982] nouveau [ DRM] suspending client object trees... Jul 27 10:12:18 zira kernel: [146471.934342] nouveau [ DRM] suspending kernel object tree... Jul 27 10:12:18 zira kernel: [146473.937170] nouveau E[ PDISP][:01:00.0][0xc000927c][880488f45840] fini: 0xc2071088 Jul 27 10:12:18 zira kernel: [146473.937171] nouveau E[ PDISP][:01:00.0][0xc000927c][880488f45840] failed suspend, -16 Jul 27 10:12:18 zira kernel: [146473.937172] nouveau E[ DRM] 0xd150:0xd15c7c00 suspend failed with -16 Jul 27 10:12:18 zira kernel: [146473.937184] nouveau E[ DRM] 0x:0xd150 suspend failed with -16 Jul 27 10:12:18 zira kernel: [146473.937292] nouveau E[ DRM] 0x:0x suspend failed with -16 Jul 27 10:12:18 zira kernel: [146473.937545] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x000260 [ TIMEOUT ] Jul 27 10:12:18 zira kernel: [146473.937703] nouveau E[PBUS][:01:00.0] MMIO write of 0xbad0011f FAULT at 0x000260 [ TIMEOUT ] Jul 27 10:12:18 zira kernel: [146473.937786] nouveau E[ DRM] 0x:0x suspend failed with -16 Jul 27 10:12:18 zira kernel: [146473.937855] nouveau [ DRM] resuming display... [...] I've attached the compressed syslog up to the point the machine was switched on again. This seems similar to bug 722001 (same error), but on a different laptop. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u2 (2015-07-17) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/zira--vg-root ro quiet ** Not tainted ** Kernel log: [ 16.299671] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 16.301030] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 16.316278] Bluetooth: hci0: Intel Bluetooth firmware patch
Bug#794680: marked as done (drbd kernel module incompatible with drbd-utils -> kernel panics)
Your message dated Fri, 30 Apr 2021 21:35:55 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #794680, regarding drbd kernel module incompatible with drbd-utils -> kernel panics 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.) -- 794680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux Version: 3.16.7-ckt11-1+deb8u2 Severity: critical Hi, TL;DR - please provide a kernel with a newer drbd module (e.g. 8.4.6), as the current version is incompatible with stable's drbd-utils and will result in kernel panics under load. I have the following kernel: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u2 (2015-07-17) This ships with version 8.4.3 of the drbd kernel module (which advertises '(api:1/proto:86-101)'). Using that version of the module with stable's drbd-utils (8.9.2rc1) results in kernel panics under heavy I/O load, fairly repeatedly. A kernel log of a typical crash is attached to this report. I intially reported this issue to Xen (since it happened in a dom0), and they referred me to this blog post: http://blog.chinewalking.com/drbd-kernel-oops-w-trim/ Notably, you will observe that drbd-module >=8.4.4 supports "trim", whereas 8.4.3 does not. Yet the userland tools arrange to use trim anyway: Aug 4 14:28:24 ophon kernel: [2856757.049680] drbd mws-02474: Agreed to support TRIM on protocol level Following that suggestion, I installed the kernel module 8.4.6 from upstream, and the kernel has stopped panicking. You might argue that drbd upstream's api/proto discrimination is inadequate (and perhaps a bug report should go there), but nonetheless kernel panics are a serious flaw in the kernel (or the offending module) IMAO. Regards, Matthew -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-backports'), (500, 'stable\ ') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Aug 3 16:03:13 opus kernel: [ 1250.026811] drbd mws-priv-1: Starting worker thread (from drbdsetup-84 [12987]) Aug 3 16:03:13 opus kernel: [ 1250.027313] block drbd4: disk( Diskless -> Attaching ) Aug 3 16:03:13 opus kernel: [ 1250.027409] drbd mws-priv-1: Method to ensure write ordering: flush Aug 3 16:03:13 opus kernel: [ 1250.027413] block drbd4: max BIO size = 4096 Aug 3 16:03:13 opus kernel: [ 1250.027418] block drbd4: drbd_bm_resize called with capacity == 41941688 Aug 3 16:03:13 opus kernel: [ 1250.027558] block drbd4: resync bitmap: bits=5242711 words=81918 pages=160 Aug 3 16:03:13 opus kernel: [ 1250.027561] block drbd4: size = 20 GB (20970844 KB) Aug 3 16:03:13 opus kernel: [ 1250.032268] block drbd4: Writing the whole bitmap, size changed Aug 3 16:03:13 opus kernel: [ 1250.047827] block drbd4: bitmap WRITE of 160 pages took 4 jiffies Aug 3 16:03:13 opus kernel: [ 1250.061634] block drbd4: 20 GB (5242711 bits) marked out-of-sync by on disk bit-map. Aug 3 16:03:13 opus kernel: [ 1250.180186] block drbd4: bitmap READ of 160 pages took 2 jiffies Aug 3 16:03:13 opus kernel: [ 1250.180291] block drbd4: recounting of set bits took additional 0 jiffies Aug 3 16:03:13 opus kernel: [ 1250.180293] block drbd4: 20 GB (5242711 bits) marked out-of-sync by on disk bit-map. Aug 3 16:03:13 opus kernel: [ 1250.180304] block drbd4: Suspended AL updates Aug 3 16:03:13 opus kernel: [ 1250.180307] block drbd4: disk( Attaching -> Inconsistent ) Aug 3 16:03:13 opus kernel: [ 1250.180310] block drbd4: attached to UUIDs 0004::: Aug 3 16:03:13 opus kernel: [ 1250.191161] drbd mws-priv-1: conn( StandAlone -> Unconnected ) Aug 3 16:03:13 opus kernel: [ 1250.191183] drbd mws-priv-1: Starting receiver thread (from drbd_w_mws-priv [12989]) Aug 3 16:03:13 opus kernel: [ 1250.191345] drbd mws-priv-1: receiver (re)started Aug 3 16:03:13 opus kernel: [ 1250.191360] drbd mws-priv-1: conn( Unconnected -> WFConnection ) Aug 3 16:03:13 opus kernel: [ 1250.689576] drbd mws-priv-1: Handshake successful: Agreed network protocol version 101 Aug 3 16:03:13 opus kernel: [ 1250.689580] drbd mws-priv-1: Agreed to support TRIM on protocol level Aug 3 16:03:13 opus kernel: [ 1250.689616] drbd mws-priv-1: conn(
Bug#794465: marked as done (Bug fixes to be2net driver)
Your message dated Fri, 30 Apr 2021 21:35:35 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #794465, regarding Bug fixes to be2net driver 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.) -- 794465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11 Severity: important Don’t allow Skyhawk P1 firmware to be downloaded to Skyhawk P2 cards. Here I am submitting the patch set to fix this issue. These patches have been accepted upstream. --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#793507: marked as done (linux-image-3.2.0-4-amd64: Repeated "BUG: soft lockup" followed by system freeze)
Your message dated Fri, 30 Apr 2021 21:35:06 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #793507, regarding linux-image-3.2.0-4-amd64: Repeated "BUG: soft lockup" followed by system freeze 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.) -- 793507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.68-1+deb7u2 Severity: important Dear Maintainer, The kernel reported a series of messages of the form "BUG: soft lockup": $ grep BUG /var/log/syslog.1 Jul 23 01:33:00 physionet2 kernel: [08.348031] BUG: soft lockup - CPU#3 stuck for 22s! [apache2:7555] Jul 23 01:33:28 physionet2 kernel: [36.348024] BUG: soft lockup - CPU#3 stuck for 22s! [apache2:7555] Jul 23 01:34:08 physionet2 kernel: [76.348025] BUG: soft lockup - CPU#3 stuck for 22s! [apache2:7555] Jul 23 01:34:36 physionet2 kernel: [555604.348024] BUG: soft lockup - CPU#3 stuck for 22s! [apache2:7555] Jul 23 01:35:04 physionet2 kernel: [555632.348024] BUG: soft lockup - CPU#3 stuck for 22s! [apache2:7555] Jul 23 01:35:32 physionet2 kernel: [555660.348025] BUG: soft lockup - CPU#3 stuck for 23s! [apache2:7555] ... Jul 23 03:10:12 physionet2 kernel: [561340.348023] BUG: soft lockup - CPU#3 stuck for 22s! [apache2:7555] Jul 23 03:10:12 physionet2 kernel: [561340.532039] BUG: soft lockup - CPU#5 stuck for 23s! [ATM:30084] Jul 23 03:10:13 physionet2 kernel: [561340.992064] BUG: soft lockup - CPU#10 stuck for 22s! [challenge-d:6735] Jul 23 03:10:13 physionet2 kernel: [561341.084076] BUG: soft lockup - CPU#11 stuck for 22s! [apcupsd:2873] Jul 23 03:10:13 physionet2 kernel: [561341.268087] BUG: soft lockup - CPU#13 stuck for 22s! [ATM:20277] Jul 23 03:10:40 physionet2 kernel: [561368.072017] BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:93] $ grep BUG /var/log/syslog.1 | wc -l 298 (Full contents of one of these messages shown below.) As you can see, this happened many times over a period of an hour and a half. During this time, the system was still working on some level (the apache log shows a steady stream of requests), but I have no idea if anything unusual was going on. At 03:01:06, the apache log stops. At 03:10:40, the system log abruptly cuts off in the middle of an error message. When I came to look at the machine the next day, it was *mostly* frozen - neither apache, nor ssh, nor any other network services were responding; however, it still responded to pings, and nmap still reported various ports as open. The console was blank and did not respond to CapsLock, NumLock, nor Ctrl+Alt+Delete. I have no idea how to debug this. Obviously a web search turns up huge numbers of results for "BUG: soft lockup" (including other Debian bugs), but I have no idea if any of them are relevant to my case, nor have I found any information about how to narrow down the problem. Please tell me if there is anything I can do to make it possible to figure out what is going on if this happens in the future. The first error message: - Jul 23 01:33:00 physionet2 kernel: [08.348031] BUG: soft lockup - CPU#3 stuck for 22s! [apache2:7555] Jul 23 01:33:00 physionet2 kernel: [08.348145] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc xfs loop cryptd aes_x86_64 aes_generic xts gf128mul dm_crypt dm_mod radeon snd_pcm ttm drm_kms_helper drm snd_page_alloc power_supply snd_timer amd64_edac_mod nv_tco snd k10temp i2c_nforce2 i2c_algo_bit edac_mce_amd shpchp soundcore edac_core evdev i2c_core mperf pcspkr psmouse serio_raw processor thermal_sys button ext4 crc16 jbd2 mbcache sr_mod cdrom sg usbhid mptsas hid scsi_transport_sas mptscsih sd_mod crc_t10dif ata_generic e1000e pata_amd mptbase e1000 3w_9xxx ohci_hcd sata_nv libata ehci_hcd usbcore scsi_mod usb_common [last unloaded: scsi_wait_scan] Jul 23 01:33:00 physionet2 kernel: [08.348226] CPU 3 Jul 23 01:33:00 physionet2 kernel: [08.348228] Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc xfs loop cryptd aes_x86_64 aes_generic xts gf128mul dm_crypt dm_mod radeon snd_pcm ttm drm_kms_helper drm snd_page_alloc power_supply
Bug#793169: marked as done (Null pointer dereference in dentry_lru_prune)
Your message dated Fri, 30 Apr 2021 21:34:12 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #793169, regarding Null pointer dereference in dentry_lru_prune 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.) -- 793169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.68-1+deb7u2 Severity: important Control: submitter -1 "Dr. Nagy Elemér Kár oly" On Tue, 2015-07-21 at 12:07 +0200, Dr. Nagy Elemér Kár oly wrote: > Dear Debian Kernel Team! > > A Sun X4200M2 locked up running linux-image-3.2.0-4-amd64 (3.2.68 > -1+deb7u2) running Debian 7.8. Blank screen, no SSH > access, no HDD activity. > > I attached the relevant part of syslog - maybe you can trace some > rare-to-occur bug with it. > > In not, sorry for wasting your time. I'm afraid the initial BUG message is too garbled... actually, after puzzling over it for a while I can see that every second character has been lost from the garbled part. (I've seen this happen before on Linux 3.0 but never worked out how it happens.) As some details are printed more than once, and I have a list of function names I can fill in a lot of the missing characters to get a somewhat useful log: [703010.276487] BUG: unable to handle kernel NULL pointer dereference at 0028 [703010.2?6?0?] RIP: [] dentry_lru_prune+0x1d/0x3d [703010.27?5?3] ?G? ? [703010.275?1?] ?o?s? ?0?0?[?1? ?M? [703010.275?3?] ? ?P? ? [703010.275?6?] Modules linked in: dm_snapshot nls_utf8 ncpfs fuse veth ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables cpufreq_powersave cpufreq_conservative cpufreq_stats cpufreq_userspace bridge stp ext3 jbd kvm_amd kvm snd_pcm snd_page_alloc psmouse snd_timer snd soundcore pcspkr serio_raw joydev evdev shpchp powernow_k8 mperf amd64_edac_mod edac_mce_amd i2c_nforce2 edac_core i2c_core k8temp button processor thermal_sys ext4 crc16 jbd2 mbcache dm_mod raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 md_mod sd_mod crc_t10dif usbhid hid sg sr_mod cdrom ata_generic ohci_hcd mptsas scsi_transport_sas mptscsih mptbase e1000 pata_amd libata scsi_mod ehci_hcd forcedeth usbcore usb_common [last unloaded: scsi_wait_scan] [703010.276?5?] [703010.276?5?] Pid: ?3, comm: kswapd0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.68-1+deb7u2 Sun Microsystems Sun Fire X4200 M2/Sun Fire X4200 M2 [703010.27?7?8] RIP: 0010:[] [] dentry_lru_prune+0x1d/0x3d [703010.2?6?1?] RSP: 0018:8?0?1?f?9?c? EFLAGS: 0?0?0?0? [703010.2?6?4?] RAX: ?0?0?0?0?0?0?0?0 RBX: ?f?f?8?2?0?0?2?0 RCX: ?0?0?0?0?8?0?8?f [703010.27?8?6] RDX: 0?0?0?0?0?0?0?0? RSI: 0?0?0?0?0?0?0?0? RDI: f?f?8?0?0?0?0?0? [703010.2?6?2?] RBP: ?f?f?8?1?6?3?3?0 R08: ?f?f?a?0?1?1?3?8 R09: ?f?f?a?0?1?1?3?8 [703010.27?9?0] R10: f?f?e?0?0?a?4?c? R11: 0?0?0?0?0?0?0?c? R12: f?f?8?0?0?0?4?5? [703010.2?7?1?] R13: ?0?0?0?0?0?0?0?0 R14: ?f?f?8?1?b?e?c?0 R15: ?f?f?8?1?b?e?c?0 [703010.27?0?6] FS: 7?f?2?f?9?0?(?0?0) GS:8?0?2?c?0?0?(?0?0) knlGS:?0?0?0?0?0?0 [703010.27?1?0] CS: 0?1? DS: ?0?0 ES:?0?0? CR0: 0?0?0?0?8?0?0?3? [703010.2?7?2?] CR2: 0028 CR3: ?0?0?0?1?d?2?0?0 CR4: ?0?0?0?0?0?0?6?0 [703010.27?1?9] DR0: 0?0?0?0?0?0?0?0? DR1: 0?0?0?0?0?0?0?0? DR2: 0?0?0?0?0?0?0?0? [703010.2?7?1?] DR3: ?0?0?0?0?0?0?0?0 DR6: ?0?0?0?0?f?f?f?0 DR7: ?0?0?0?0?0?0?4?0 [703010.27?2?4] Process kswapd0 (pid: ?3, threadinfo 8?0?1?f?8?0?, task ?8?1?b?9?1?0) [703010.2?7?9?] Stack: [703010.2?7?1?] ?f?f?8?2?0?0?2?0 f?f?f?f?8?1?b?0? ?f?f?8?2?0?0?2?0 f?f?8?0?0?0?0?0? [703010.2?7?6?] ?f?f?8?1?b?e?c?0 f?f?8?0?0?0?0?8? ?f?f?8?2?b?3?0?0 f?f?f?f?8?1?b?4? [703010.2?7?0?] ?f?f?a?0?3?d?4?8 f?f?8?0?3?0?6?4? ?0?0?0?0?0?0?0?0 f?f?8?0?0?0?0?8? [703010.2?7?5?] Call Trace: [703010.27?4?8] [] ? dentry_kill+0x73/0x137 [703010.27?5?6] [] ? shrink_dentry_list+0x7?/0xc9 [703010.27?5?4] [] ? prune_dcache_sb+0x12?/0x134 [703010.2?7?6?] [] ? prune_super+0xd4/0x149 [703010.2?7?9?] [] ? shrink_slab+0x1?f/0x2?d [703010.27?6?9] [] ? balance_pgdat+0x?8?/0x?b? [703010.2?7?4?] [] ? kswapd+0x?e?/0x?1? [703010.2?7?7?] [] ? add_wait_queue+0x?c/0x3? [703010.2?7?0?] [] ? balance_pgdat+0x4?7/0x4?7 [703010.27?7?0] [] ? kthread+0x?6/0x7? [703010.2?7?5?] [] ? kernel_thread_helper+0x?/0x?0 [703010.27?7?6] [] ? kthread_worker_fn+0x?3?/0x?3? [703010.2?7?1?] [] ? gs_change+0x1?/0x?3 [703010.27?8?0] Code: ?f 4? ?8 6? ?f 4? ?c 5? ?b 4? ?9 e? ?d c? ?3 4? ?d 8? ?0 0? ?0 0? ?8 3? ?7 8? ?0 0? ?0 4? ?9 f? ?4 2? ?6 0? ?0 7? ?7 4?
Bug#793377: marked as done (linux-image-4.0.0-2-amd64: USB keyboard losing keystrokes)
Your message dated Fri, 30 Apr 2021 21:34:52 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #793377, regarding linux-image-4.0.0-2-amd64: USB keyboard losing keystrokes 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.) -- 793377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-4.0.0-2-amd64 Version: 4.0.8-1 Severity: important Dear Maintainer, I recently upgraded from Jessie to Stretch, which bought along a kernel upgrade from 3.16 to 4.0. After the upgrade - and a reboot - my USB keyboard (TypeMatrix 2030) started losing keystrokes: typing at normal speed, about 25% of keys pressed were lost completely. This happened under GNOME. I tried on the console, and couldn't reproduce the problem (I didn't try typing fast, mind you). I couldn't reproduce the problem with the built-in keyboard of my laptop (Dell XPS 13, 2014 model), either. I have not tried switching to another DE, or WM. But I did try downgrading the kernel to 3.16, and my woes are now gone. I have no idea how to debug the regression, any pointers in that direction would be helpful. I can provide dmesg output and whatever logs you may need, if told to do so. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#922666: confirmed bug report
]] Salvatore Bonaccorso > Can you confirm if this issue is still present with a recent kernel? I haven't seen it for quite some time on my Buster machine, so from my point of view, it can be closed. Regards, -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Processed: tagging 944092
Processing commands for cont...@bugs.debian.org: > tags 944092 + moreinfo Bug #944092 [src:linux] linux-image-5.3.0-1-amd64: i915 gpu hang, system freezes for seconds every few minutes Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 944092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 983672
Processing commands for cont...@bugs.debian.org: > tags 983672 - patch Bug #983672 [src:linux] linux-image: fails to recognize certain microSD cards Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 983672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976093: marked as done (linux-image-5.9.0-3-arm64: Network failure Pine A64 LTS)
Your message dated Fri, 30 Apr 2021 21:21:08 +0200 with message-id and subject line Re: Bug#976093: linux-image-5.9.0-3-arm64: Network failure Pine A64 LTS has caused the Debian Bug report #976093, regarding linux-image-5.9.0-3-arm64: Network failure Pine A64 LTS 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.) -- 976093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux X-Debbugs-Cc: xypron.g...@gmx.de Version: 5.9.9-1 Severity: normal Tags: patch upstream Dear Maintainer, since Bullseye switched to Linux v5.9 my Pine A64 LTS board fails to boot via iSCSI. I have posted a patch upstream. Please, consider it for inclusion: [PATCH 1/1] arm64: dts: allwinner: A64 Sopine: phy-mode rgmii https://lore.kernel.org/linux-arm-kernel/20201129162627.1244808-1-xypron.g...@gmx.de/T/#u Best regards Heinrich -- Package-specific info: ** Version: Linux version 5.9.0-3-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.9-1 (2020-11-19) --- End Message --- --- Begin Message --- Source: linux Source-Version: 5.10.1-1~exp1 On Sun, Nov 29, 2020 at 05:38:28PM +0100, Heinrich Schuchardt wrote: > Package: src:linux > X-Debbugs-Cc: xypron.g...@gmx.de > Version: 5.9.9-1 > Severity: normal > Tags: patch upstream > > Dear Maintainer, > > since Bullseye switched to Linux v5.9 my Pine A64 LTS board fails to > boot via iSCSI. > > I have posted a patch upstream. Please, consider it for inclusion: > > [PATCH 1/1] arm64: dts: allwinner: A64 Sopine: phy-mode rgmii > https://lore.kernel.org/linux-arm-kernel/20201129162627.1244808-1-xypron.g...@gmx.de/T/#u Those were included in 5.10 first, so closing the bug accordingly. Regards, Salvatore--- End Message ---
Bug#944092: linux-image-5.3.0-1-amd64: i915 gpu hang, system freezes for seconds every few minutes
Control: tags -1 + moreinof On Mon, Nov 04, 2019 at 08:39:15AM +0100, Philipp Marek wrote: > Package: src:linux > Version: 5.3.7-1 > Severity: normal > Tags: patch upstream > > Whole machine hangs, but recovers after a few seconds; no visible > association to CPU or memory load. > > Please include the patch from > > https://patchwork.freedesktop.org/patch/300891/ > > it claims to fix a bug that is reported since about a year in many different > bug reports and -trackers. AFAICS, the patch was not applied, but could you confirm if the issue still persist with recent kernel? Regards, Salvatore
Processed (with 1 error): Re: Bug#944092: linux-image-5.3.0-1-amd64: i915 gpu hang, system freezes for seconds every few minutes
Processing control commands: > tags -1 + moreinof Unknown tag/s: moreinof. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore. Bug #944092 [src:linux] linux-image-5.3.0-1-amd64: i915 gpu hang, system freezes for seconds every few minutes Requested to add no tags; doing nothing. -- 944092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923393: marked as done (CONFIG_DRM_I915_GVT_KVMGT is not enabled)
Your message dated Fri, 30 Apr 2021 21:08:09 +0200 with message-id and subject line Re: Bug#923393: CONFIG_DRM_I915_GVT_KVMGT is not enabled has caused the Debian Bug report #923393, regarding CONFIG_DRM_I915_GVT_KVMGT is not enabled 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.) -- 923393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-4.19.0-2-amd64 Version: 4.19.16-1 I would like to try GVT like described in https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide to get native 3D accelaration in a KVM guest. Unfortunately, the kernel compile options CONFIG_DRM_I915_GVT and CONFIG_DRM_I915_GVT_KVMGT are not set. So I can't use it with the provided kernels. Can it be enabled in the official builds? Best regards, Michael Fritscher --- End Message --- --- Begin Message --- Source: linux Source-Version: 5.5.13-1 On Wed, Feb 27, 2019 at 03:01:39PM +0100, Michael Fritscher wrote: > Package: linux-image-4.19.0-2-amd64 > Version: 4.19.16-1 > > I would like to try GVT like described in > https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide to get native > 3D accelaration in a KVM guest. Unfortunately, the kernel compile > options CONFIG_DRM_I915_GVT and CONFIG_DRM_I915_GVT_KVMGT are not set. > So I can't use it with the provided kernels. > > Can it be enabled in the official builds? This was done in the 5.5.13-1 upload, cf. #954088. Regards, SAlvatore--- End Message ---
Processed: Re: Bug#922666: confirmed bug report
Processing control commands: > tags -1 + moreinfo Bug #922666 [src:linux] linux-image-4.19.0-2-amd64: Trackpad and trackpoint stop working after suspend Bug #928189 [src:linux] linux-image-4.19.0-4-amd64: After resume trackpad of Lenovo Helix (tablet with keyboard dock) doesn't work Added tag(s) moreinfo. Added tag(s) moreinfo. -- 922666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666 928189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922666: confirmed bug report
Control: tags -1 + moreinfo Hi Tollef, Antoine, On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote: > Control: forcemerge 922666 928189 > Control: severity 922666 important > Control: tags 922666 +patch +confirmed > > I also see a regression with touchpads and trackpoint on a Thinkpad E431 > after upgrading from Debian stretch to buster. My research indicates > this is a kernel regression, as yet to be fixed. > > This is the result of my research, as available online at: > > https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep > > On a Thinkpad E431, the entire mouse interface (touch, trackpoint) > freezes after sleep. Keyboard still works but not mouse until a > reboot. > > There's [bug 922666][] in Debian buster, without a fix. It also says > it eventually recovers, which is not our experience. Possible dupe is > [bug 928189][]. > > [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189 > [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666 > > There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and > which proposes the following workarounds: > > * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method > disabled` > > * A .service file: > > # /etc/systemd/system/touchpad-sleep.service > # restore touchpad on suspend > > [Unit] > Description=Restore Touchpad on suspend > Before=sleep.target > StopWhenUnneeded=yes > > [Service] > #Type=oneshot > Type=idle > RemainAfterExit=yes > ExecStart=/bin/bash -c 'echo ":00:1f.4" > > /sys/bus/pci/drivers/i801_smbus/unbind' > ExecStop=/bin/bash -c 'echo ":00:1f.4" > > /sys/bus/pci/drivers/i801_smbus/bind' > > [Install] > WantedBy=sleep.target > > * "Maybe try xserver-xorg-input-evdev instead of > xserver-xorg-input-libinput?" > > * reloading `psmouse`: > > sudo modprobe -r psmouse > sudo modprobe psmouse > > * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to > solve the issue." > > * whatever this is: > > # echo 1 > /sys/devices/rmi4-00/nosleep > > * "Anyone who still affected by touchpad issues after S3. Please >switch back to suspend-to-idle in BIOS if s2idle is >supported. ThinkPad Carbon 6th and Yoga 3rd do support >suspend-to-idle in BIOS->config->power menu." > > [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427 > > There's also [bug 1442699][] in Fedora, which suggests those > workarounds: > > * another module reload: > > sudo rmmod i2c_hid > sudo modprobe i2c_hid > > * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing >and this issue seems to have been resolved (for me)." > > * another `/proc` hack: > > echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl > > * "The `psmouse.synaptics_intertouch=0` workaround still works for me." > > [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699 > > Also related is this [libinput bug][] that's closed as "not our bug" > because they claim it's a bug in the kernel. > > [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149 > > There are [two][] [patches][] on the Linux kernel which apparently fix the > issue, still pending approval: > > [two]: https://lkml.org/lkml/2019/2/20/700 > [patches]: https://lkml.org/lkml/2019/2/20/701 > > Possibly related: https://lkml.org/lkml/2016/8/18/134 > > [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A > [pull request][] has been merged in mainline with two other fixes on > the module./ [5.0.11][] also has fixes on the module. It's clearly a > regression from Debian stretch (kernel 4.9) since it was working fine > before. > > Possibly related, [two-finger scrolling bug in Ubuntu][], which > identifies [this commit][] as the source of the regression. [Upstream > kernel bug][], still open. > > [5.1rc7]: https://lkml.org/lkml/2019/4/28/270 > [pull request]: https://lkml.org/lkml/2019/7/12/19 > [5.0.11]: https://lkml.org/lkml/2019/5/2/287 > [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719 > [this commit]: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738 > [two-finger scrolling bug in Ubuntu]: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478 > > I haven't tried any of those workarounds. I hope this helps! Can you confirm if this issue is still present with a recent kernel? Regards, Salvatore
Processed: Re: Bug#922666: confirmed bug report
Processing control commands: > tags -1 + moreinfo Bug #928189 [src:linux] linux-image-4.19.0-4-amd64: After resume trackpad of Lenovo Helix (tablet with keyboard dock) doesn't work Bug #922666 [src:linux] linux-image-4.19.0-2-amd64: Trackpad and trackpoint stop working after suspend Ignoring request to alter tags of bug #928189 to the same tags previously set Ignoring request to alter tags of bug #922666 to the same tags previously set -- 922666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666 928189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 918156
Processing commands for cont...@bugs.debian.org: > tags 918156 + moreinfo Bug #918156 [src:linux] linux-image-4.18.0-0.bpo.3-armmp: please enable support for Ti WL1838 Bluetooth Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 918156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910366: marked as done (linux: ath9k-htc on OHCI -> bogus usb xfer)
Your message dated Fri, 30 Apr 2021 11:57:28 -0700 (PDT) with message-id <608c5318.1c69fb81.57759.6...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #910366, regarding linux: ath9k-htc on OHCI -> bogus usb xfer 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.) -- 910366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux Version: 4.9.110-1 Tags: patch This is regression, on older (3.x) kernels, it used to work: On my USB 1.1 port I cannot use my USB WLAN adaptor anymore (TL-WN722N with hostapd). When I remove the following lines, everything is fine again: diff --git a/drivers/usb/core/urb.c b/drivers/usb/core/urb.c index 3d27477..a317e1e 100644 --- a/drivers/usb/core/urb.c +++ b/drivers/usb/core/urb.c @@ -443,11 +443,6 @@ int usb_submit_urb(struct urb *urb, gfp_t mem_flags) * cause problems in HCDs if they get it wrong. */ - /* Check that the pipe's type matches the endpoint's type */ - if (usb_pipetype(urb->pipe) != pipetypes[xfertype]) - dev_WARN(>dev, "BOGUS urb xfer, pipe %x != type %x\n", - usb_pipetype(urb->pipe), pipetypes[xfertype]); - /* Check against a simple/standard policy */ allowed = (URB_NO_TRANSFER_DMA_MAP | URB_NO_INTERRUPT | URB_DIR_MASK | URB_FREE_BUFFER); Thanks to Alexey Brodkin for finding the culprit. See here: https://lists.openwrt.org/pipermail/openwrt-devel/2016-July/001723.html and here: http://lists.infradead.org/pipermail/linux-snps-arc/2016-July/001310.html --- End Message --- --- Begin Message --- Hi This bug was filed for a very old kernel or the bug is old itself without resolution. If you can reproduce it with - the current version in unstable/testing - the latest kernel from backports please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore--- End Message ---
Bug#882105: marked as done (linux-image-4.9.0-4-amd64: HDMI - HD Audio passthrough dont work for HBA (High Bit Rate) Audio like e.g. DTS HD MA, TrueHD)
Your message dated Fri, 30 Apr 2021 20:53:38 +0200 with message-id and subject line Re: Bug#882105: linux-image-4.9.0-4-amd64: HDMI - HD Audio passthrough dont work for HBA (High Bit Rate) Audio like e.g. DTS HD MA, TrueHD has caused the Debian Bug report #882105, regarding linux-image-4.9.0-4-amd64: HDMI - HD Audio passthrough dont work for HBA (High Bit Rate) Audio like e.g. DTS HD MA, TrueHD 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.) -- 882105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.9.51-1 Severity: normal Tags: patch Dear Maintainer, I have a problem with the HBA audio. I am use ALSA to play movies with kodi. Platform is a INTEL NUCi3BNK with the latest BIOS and (V 0054) the latest HDMI 2.0 Firmware (V1.72). Only the DTS HD MA or True HD are affected (High Bit Rate Audio) I am found a bug report with a fix/patch on: https://bugs.freedesktop.org/show_bug.cgi?id=98797 Kind regards, Thomas -- Package-specific info: ** Version: Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 root=UUID=dfd27520-6009-4064-af45-a4c5f2498396 ro quiet ** Not tainted ** Kernel log: [3.073968] Bluetooth: HCI UART protocol AG6XX registered [3.073969] Bluetooth: HCI UART protocol Marvell registered [3.075292] ite_cir: Auto-detected model: ITE8708 CIR transceiver [3.075293] ite_cir: Using model: ITE8708 CIR transceiver [3.075294] ite_cir: TX-capable: 1 [3.075295] ite_cir: Sample period (ns): 8680 [3.075295] ite_cir: TX carrier frequency (Hz): 38000 [3.075296] ite_cir: TX duty cycle (%): 33 [3.075297] ite_cir: RX low carrier frequency (Hz): 0 [3.075297] ite_cir: RX high carrier frequency (Hz): 0 [3.106987] Registered IR keymap rc-rc6-mce [3.107103] input: ITE8708 CIR transceiver as /devices/virtual/rc/rc0/input4 [3.107134] rc rc0: ITE8708 CIR transceiver as /devices/virtual/rc/rc0 [3.127524] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [3.127932] wmi: Mapper loaded [3.128825] lirc_dev: IR Remote Control driver registered, major 243 [3.129366] mei_me :00:16.0: enabling device ( -> 0002) [3.130980] rc rc0: lirc_dev: driver ir-lirc-codec (ite-cir) registered at minor = 0 [3.130982] IR LIRC bridge handler initialized [3.133865] [drm] Initialized [3.133879] EFI Variables Facility v0.08 2004-May-17 [3.137371] iTCO_vendor_support: vendor-support=0 [3.139381] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [3.139512] iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400) [3.139756] input: PC Speaker as /devices/platform/pcspkr/input/input5 [3.144133] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [3.149668] IR RC6 protocol handler initialized [3.159410] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [3.173785] pstore: using zlib compression [3.173797] pstore: Registered efi as persistent store backend [3.175006] ite_cir: driver has been successfully loaded [3.191881] [drm] Memory usable by graphics device = 4096M [3.191884] checking generic (4000 7f) vs hw (4000 4000) [3.191885] fb: switching to inteldrmfb from EFI VGA [3.191938] Console: switching to colour dummy device 80x25 [3.192517] Adding 4079612k swap on /dev/nvme0n1p4. Priority:-1 extents:1 across:4079612k SSFS [3.192979] [drm] Replacing VGA console driver [3.201069] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.201071] [drm] Driver supports precise vblank timestamp query. [3.203506] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [3.204254] i915 :00:02.0: firmware: failed to load i915/kbl_dmc_ver1_01.bin (-2) [3.204263] i915 :00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed with error -2 [3.204267] i915 :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management. [3.227207] kvm: disabled by bios [3.231048] intel_rapl: Found RAPL domain package [3.231050] intel_rapl: Found RAPL domain core [3.231051] intel_rapl: Found RAPL domain uncore [3.231052] intel_rapl: Found RAPL domain dram [3.474440] [drm] failed to retrieve link info, disabling eDP [3.475374] [drm]
Processed: severity of 987798 is important
Processing commands for cont...@bugs.debian.org: > severity 987798 important Bug #987798 [src:linux] general: TG3 fails without repair when applying high load to NIC Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 987798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#864437: marked as done (linux-image-4.9.0-3-amd64: Soft lockup of igb/e1000e driver at stats update)
Your message dated Fri, 30 Apr 2021 11:46:28 -0700 (PDT) with message-id <608c5084.1c69fb81.3e1ea.6...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #864437, regarding linux-image-4.9.0-3-amd64: Soft lockup of igb/e1000e driver at stats update 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.) -- 864437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.9.30-1 Severity: critical Tags: patch upstream Justification: causes serious data loss Hello, the igb/e1000e driver causes a soft lockup when doing stats updates. For instance, when using the ledtrig-netdev kernel module to visualize network activity via LEDs. The lockup mostly happens within the first 3 days of uptime, probably depending on network activity: [168313.275259] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:1:46] [168323.276973] INFO: rcu_sched self-detected stall on CPU [168323.282239] 2-...: (1 GPs behind) idle=337/142/0 softirq=359087/359089 fqs=14081745 [168323.291202] (t=28187367 jiffies g=247240 c=247239 q=1072734) The attached patch fixes the problem and originates from: http://git.ipfire.org/?p=people/arne_f/ipfire-2.x.git;a=commit;h=fcffac1340f61923786af8a860c12056a9ef3706 -- Package-specific info: ** Version: Linux version 4.9.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-1 (2017-06-04) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=UUID=77a53576-9972-4229-b526-b41dac38844a ro console=ttyS0,115200 earlyprint=serial,ttyS0,115200 quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [3.620382] igb :02:00.0 enp2s0: renamed from eth1 [3.766809] ata2: SATA link down (SStatus 0 SControl 300) [3.767950] usb 1-1: new high-speed USB device number 2 using ehci-pci [3.916363] usb 1-1: New USB device found, idVendor=0438, idProduct=7900 [3.916369] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [3.917813] hub 1-1:1.0: USB hub found [3.917945] hub 1-1:1.0: 4 ports detected [3.927913] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [3.928179] ata1.00: ATA-11: SATA SSD, SBFM01.0, max UDMA/133 [3.928184] ata1.00: 31277232 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [3.928445] ata1.00: configured for UDMA/133 [3.929358] scsi 0:0:0:0: Direct-Access ATA SATA SSD 01.0 PQ: 0 ANSI: 5 [3.970427] sd 0:0:0:0: [sda] 31277232 512-byte logical blocks: (16.0 GB/14.9 GiB) [3.970824] sd 0:0:0:0: [sda] Write Protect is off [3.970831] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3.970907] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.972327] sda: sda1 [3.973719] sd 0:0:0:0: [sda] Attached SCSI disk [4.095895] raid6: sse2x1 gen() 479 MB/s [4.163885] raid6: sse2x1 xor() 709 MB/s [4.231873] raid6: sse2x2 gen() 1157 MB/s [4.299855] raid6: sse2x2 xor() 911 MB/s [4.367891] raid6: sse2x4 gen() 1466 MB/s [4.435908] raid6: sse2x4 xor() 997 MB/s [4.435912] raid6: using algorithm sse2x4 gen() 1466 MB/s [4.435914] raid6: xor() 997 MB/s, rmw enabled [4.435918] raid6: using ssse3x2 recovery algorithm [4.435993] clocksource: Switched to clocksource tsc [4.436784] xor: automatically using best checksumming function avx [4.456601] Btrfs loaded, crc32c=crc32c-intel [4.473946] BTRFS: device label root devid 1 transid 38792 /dev/sda1 [4.508781] BTRFS info (device sda1): disk space caching is enabled [4.508800] BTRFS info (device sda1): has skinny extents [4.519800] BTRFS info (device sda1): detected SSD devices, enabling SSD mode [4.711926] random: fast init done [4.760742] ip_tables: (C) 2000-2006 Netfilter Core Team [4.772255] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [4.772993] systemd[1]: Detected architecture x86-64. [4.774225] systemd[1]: Set hostname to . [4.928434] systemd[1]: Created slice System Slice. [4.929098] systemd[1]: Created slice system-getty.slice. [4.929339] systemd[1]: Listening on Journal Socket. [4.933803] systemd[1]: Starting Load Kernel Modules... [4.934229] systemd[1]:
Bug#877869: marked as done (kirkwood-t5325.dts fixes for poweroff and sound device detection issues on HP T5325)
Your message dated Fri, 30 Apr 2021 20:49:54 +0200
with message-id
and subject line Re: Bug#877869: kirkwood-t5325.dts fixes for poweroff and
sound device detection issues on HP T5325
has caused the Debian Bug report #877869,
regarding kirkwood-t5325.dts fixes for poweroff and sound device detection
issues on HP T5325
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.)
--
877869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.9.0-3-marvell
Version: 4.9.30-2+deb9u5
When the kirkwood-t5325.dtb included in the package is used on HP T5325,
the poweroff command fails to power off the device (indicated by the
front blue light not turning off). It does however brings the device to
near power off ( I have seen a kernel panic at the end that can be seen
if a hardware serial connection is used). Also, with the same dtb, sound
device does not get detected. dmesg output contains the following:
[ 10.861482] OF: /sound/simple-audio-card,cpu: arguments longer than
property
[ 10.861492] asoc-simple-card sound: parse error -22
[ 10.861508] asoc-simple-card: probe of sound failed with error -22
Fix:
Both problems could be corrected by fixing the dtb. "bodhi" at
https://forum.doozan.com possibly with the help of other forum members
had fixed and tested the corrections. Thanks go to him and those who
supported him!
If ever needed, package "bodhi" maintains can be found at
https://forum.doozan.com/read.php?2,12096 and the download contains a
patch file showing his modifications.
I myself tested the changes needed to fix the poweroff problem and the
sound device detection issue by getting the upstream kernel source,
changing two lines and compiling the kirkwood-t5325.dts. Please find the
attached working dtb and dts. The two fixes needed are as follows:
--- linux-master/arch/arm/boot/dts/kirkwood-t5325.dts 2017-10-05
01:16:05.0 +0100
+++ linux-master-fixed/arch/arm/boot/dts/kirkwood-t5325.dts
2017-10-06 13:59:19.834377641 +0100
@@ -174,7 +174,7 @@
compatible = "gpio-poweroff";
pinctrl-0 = <_power_off>;
pinctrl-names = "default";
- gpios = < 17 GPIO_ACTIVE_HIGH>;
+ gpios = < 16 GPIO_ACTIVE_HIGH>;
};
sound {
@@ -195,7 +195,7 @@
simple-audio-card,mclk-fs = <256>;
simple-audio-card,cpu {
- sound-dai = <>;
+ sound-dai = < 0>;
};
simple-audio-card,codec {
I haven't submitted the changes to upstream. Appreciate if you release
the package with a corrected kirkwood-t5325.dtb.
Kamal
kirkwood-t5325.dtb
Description: Binary data
/*
* Device Tree file for HP t5325 Thin Client"
*
* Copyright (C) 2014
*
* Thomas Petazzoni
* Andrew Lunn
*
* This file is licensed under the terms of the GNU General Public
* License version 2. This program is licensed "as is" without any
* warranty of any kind, whether express or implied.
*/
/dts-v1/;
#include "kirkwood.dtsi"
#include "kirkwood-6281.dtsi"
/ {
model = "HP t5325 Thin Client";
compatible = "hp,t5325", "marvell,kirkwood-88f6281", "marvell,kirkwood";
memory {
device_type = "memory";
reg = <0x 0x2000>;
};
chosen {
bootargs = "console=ttyS0,115200n8";
stdout-path =
};
ocp@f100 {
pinctrl: pin-controller@1 {
pinctrl-0 = <_i2s _sysrst>;
pinctrl-names = "default";
pmx_button_power: pmx-button_power {
marvell,pins = "mpp45";
marvell,function = "gpio";
};
pmx_power_off: pmx-power-off {
marvell,pins = "mpp48";
marvell,function = "gpio";
};
pmx_led: pmx-led {
marvell,pins = "mpp21";
marvell,function = "gpio";
};
pmx_usb_sata_power_enable: pmx-usb-sata-power-enable {
marvell,pins = "mpp44";
marvell,function = "gpio";
};
pmx_spi: pmx-spi {
marvell,pins = "mpp1", "mpp2", "mpp3", "mpp7";
marvell,function = "spi";
Bug#861301: marked as done (linux-image-4.9.0-2-amd64: Dell Optiplex 790 does not reboot without reboot=pci)
Your message dated Fri, 30 Apr 2021 10:37:01 -0700 (PDT) with message-id <608c403d.1c69fb81.80f22.5...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #861301, regarding linux-image-4.9.0-2-amd64: Dell Optiplex 790 does not reboot without reboot=pci 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.) -- 861301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.9.18-1 Severity: normal Tags: patch Dear Maintainer, with the lastest and older kernels a Dell Optiplex needs the additional kernel commandline reboot=pci to reboot correctly. With it the machine hangs at the end of the shutdown. I found this bug report which confirms it: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818933 There is a patch included which seems not included upstream (0004): http://people.canonical.com/~ogasawara/dell-reboot-quirks/ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/reboot.c Maybe it could be included in Debian and upstream and then it will be fixed in the long run. Thanks for your work. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi This bug was filed for a very old kernel or the bug is old itself without resolution. If you can reproduce it with - the current version in unstable/testing - the latest kernel from backports please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore--- End Message ---
Bug#860534: marked as done (firmware-amd-graphics: Random system freezes with AMD GPU)
Your message dated Fri, 30 Apr 2021 19:14:22 +0200 with message-id and subject line Re: Bug#860534: drm/radeon: Change the default to PCI on PowerPC has caused the Debian Bug report #860534, regarding firmware-amd-graphics: Random system freezes with AMD GPU 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.) -- 860534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-amd-graphics Version: 20161130-2 Severity: important Dear Maintainer, Since my update to stretch, my system is randomly freezing after some time of use. The freezes do not require any intensive graphics use, it happened opening a new tab on firefox, and another time firing up Vim on terminal. This is the pertinent kern.log Apr 16 00:24:15 venus kernel: [ 3823.269564] radeon :01:00.0: ring 0 stalled for more than 10172msec Apr 16 00:24:15 venus kernel: [ 3823.269572] radeon :01:00.0: GPU lockup (current fence id 0x0002b53c last fence id 0x0002b554 on ring 0) Apr 16 00:24:16 venus kernel: [ 3823.781490] radeon :01:00.0: ring 0 stalled for more than 10684msec Apr 16 00:24:16 venus kernel: [ 3823.781498] radeon :01:00.0: GPU lockup (current fence id 0x0002b53c last fence id 0x0002b554 on ring 0) Apr 16 00:24:16 venus kernel: [ 3824.293468] radeon :01:00.0: ring 0 stalled for more than 11196msec Apr 16 00:24:16 venus kernel: [ 3824.293476] radeon :01:00.0: GPU lockup (current fence id 0x0002b53c last fence id 0x0002b554 on ring 0) Apr 16 00:24:17 venus kernel: [ 3824.805484] radeon :01:00.0: ring 0 stalled for more than 11708msec Apr 16 00:24:17 venus kernel: [ 3824.805492] radeon :01:00.0: GPU lockup (current fence id 0x0002b53c last fence id 0x0002b555 on ring 0) Apr 16 00:24:18 venus kernel: [ 3825.317515] radeon :01:00.0: ring 0 stalled for more than 12220msec Apr 16 00:24:18 venus kernel: [ 3825.317523] radeon :01:00.0: GPU lockup (current fence id 0x0002b53c last fence id 0x0002b555 on ring 0) Apr 16 00:24:18 venus kernel: [ 3825.829429] radeon :01:00.0: ring 0 stalled for more than 12732msec Apr 16 00:24:18 venus kernel: [ 3825.829437] radeon :01:00.0: GPU lockup (current fence id 0x0002b53c last fence id 0x0002b555 on ring 0) Apr 16 00:24:19 venus kernel: [ 3826.341456] radeon :01:00.0: ring 0 stalled for more than 13244msec Apr 16 00:24:19 venus kernel: [ 3826.341460] radeon :01:00.0: GPU lockup (current fence id 0x0002b53c last fence id 0x0002b559 on ring 0) Apr 16 00:24:19 venus kernel: [ 3826.553557] radeon :01:00.0: Saved 1367 dwords of commands on ring 0. The lspci from this GPU: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at fbdc (64-bit, non-prefetchable) [size=128K] I/O ports at ce00 [size=256] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon Kernel modules: radeon After the freeze occours I need to reboot the machine, I cannot restart the X server nor open another virtual console, and in one case I got some files corrupted when the system crashed firing up vim. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-amd-graphics depends on no packages. firmware-amd-graphics recommends no packages. Versions of packages firmware-amd-graphics suggests: ii initramfs-tools 0.127 -- no debconf information --- End Message --- --- Begin Message --- Hi Mathieu, On Mon, Sep 10, 2018 at 02:12:14PM +0200, Mathieu Malaterre wrote: > rafael, > > On Sat, Sep 8, 2018 at 4:02 PM Salvatore Bonaccorso
Bug#852749: Bug still present, patches work on modules in kernel package 4.9.0-9
Control: tags -1 + moreinfo On Fri, May 10, 2019 at 10:10:05PM -0400, AJ Milne wrote: > Realizing this thread is now a few years old: I had the same error > (transfer buffer not dma capable, coming from usb_hcd_map_urb_for_dma) > using a Line6 Pod XT through the snd-usb-pod kernel module (uses > snd-usb-line6), the machine running stock kernel package 4.9.0-9. > > Inspecting the source, it appears the message buffers are still coming from > the stack as of this kernel package. Applying Ben Hutchings' patches as of > message: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749#10 > > ... these moving the message buffers off the stack and adding error checks > to the toneport set, doing so corrected the problem. Device is now > functional; thanks much. Can you check with more recent kernels if the issue still persist without the patches from Ben? (I.e. has the issue in meanwhile been fixed upstream directly)? Regards, Salvatore
Processed: Re: Bug#852749: Bug still present, patches work on modules in kernel package 4.9.0-9
Processing control commands: > tags -1 + moreinfo Bug #852749 [src:linux] linux-image-4.9.0-1-amd64: usb-audio-device not working since kernel 4.9.0.1 Added tag(s) moreinfo. -- 852749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795991: /boot/vmlinuz-3.16.0-0.bpo.4-amd64: duplicate request cache is too small for NFS 4.1 servers
Am 30.04.21 um 14:32 schrieb Salvatore Bonaccorso: > > is this problem still relevant? > I think so. My upstream request was never really considered. You still have the problem that a kernel-nfs server with only few memory runs out of sessions with a lot of clients. > Side note that we would anyway not apply a patch which would not have > been accepted upstream, likely unless there are very valid reasons. > Yes I also think so. We changed to nfs-ganesha as a user level NFS server, which does not have this restriction. Christoph
Processed: tagging 987281
Processing commands for cont...@bugs.debian.org: > tags 987281 - moreinfo Bug #987281 [src:linux] linux-image-amd64: Enable i915 HDCP 2.2 support Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 987281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#792930: marked as done (linux-image-4.0.0-2-586: [Geode LX] fails to load via GRUB 2)
Your message dated Fri, 30 Apr 2021 15:38:27 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #792930, regarding linux-image-4.0.0-2-586: [Geode LX] fails to load via GRUB 2 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.) -- 792930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.0.8-1 Severity: important Kernel 4 completely fails to launch on this Geode LX host. GRUB displays the usual messages about loading the kernel and the initrd image, then the cursor freezes. No further message is displayed. Kernel 3.2 (oldstable) and 3.16 (stable) boot normaly on the exact same host. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** Network interface configuration: auto lo iface lo inet loopback ** PCI devices: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] Host Bridge [1022:2080] (rev 31) Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- [disabled] 00:01.2 Entertainment encryption device [1010]: Advanced Micro Devices, Inc. [AMD] Geode LX AES Security Block [1022:2082] Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Kernel driver in use: 8139too 00:0f.0 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] ISA [1022:2090] (rev 03) Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:801b] Control: I/O+ Mem- BusMaster- SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ohci-pci 00:0f.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] EHC [1022:2095] (rev 02) (prog-if 20 [EHCI]) 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 ** USB devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (1001, 'testing'), (1001, 'stable'), (1001, 'oldstable') Architecture: i386 (i586) Kernel: Linux 3.16.0-4-586 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.0.0-2-586 depends on: ii debconf [debconf-2.0] 1.5.56 ii initramfs-tools [linux-initramfs-tool] 0.120 ii kmod20-1 ii linux-base 3.5 Versions of packages linux-image-4.0.0-2-586 recommends: ii firmware-linux-free 3.3 Versions of packages linux-image-4.0.0-2-586 suggests: pn debian-kernel-handbook ii grub-pc 2.02~beta2-26 pn linux-doc-4.0 Versions of packages linux-image-4.0.0-2-586 is related to: pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi0.44 pn firmware-libertas ii firmware-linux 0.44 ii firmware-linux-nonfree 0.44 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-ralink pn firmware-realtek pn xen-hypervisor -- debconf information: linux-image-4.0.0-2-586/postinst/depmod-error-initrd-4.0.0-2-586: false linux-image-4.0.0-2-586/prerm/removing-running-kernel-4.0.0-2-586: true linux-image-4.0.0-2-586/postinst/mips-initrd-4.0.0-2-586: --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with -
Bug#792323: marked as done (linux-image-4.0.0-2-amd64: display doesn't detach when running newest kernel on Lenovo T450s)
Your message dated Fri, 30 Apr 2021 15:37:55 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #792323, regarding linux-image-4.0.0-2-amd64: display doesn't detach when running newest kernel on Lenovo T450s 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.) -- 792323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.0.8-1 Severity: important Dear Maintainer, Running Gnome 3.16.2, plugging my (lid closed) Lenovo T450s into its dock which has a DisplayPort connection to a Dell monitor (2560x1440), the monitor is autodetected and set as primary monitor, with the built-in screen apparently disabled. Disconnecting the laptop and opening it up results in the system still thinking that the external monitor is attached, which causes it to switch to default extended displays. Since the laptop thinks that the screen is still attached, I have to either disable it or switch it to mirrored mode to use the laptop normally. Not sure that this is actually a problem with the kernel, but this issue is completely absent when I boot with the older kernel, linux-image-4.0.0-1-amd64 version 4.0.2-1. This issue was happening with both version 4.0.7-1 of linux- image-4.0.0-2-amd64 and the current 4.0.8-1 version. -- Package-specific info: ** Version: Linux version 4.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-1) ) #1 SMP Debian 4.0.8-1 (2015-07-11) ** Command line: BOOT_IMAGE=/vmlinuz-4.0.0-2-amd64 root=/dev/mapper/rafiki--vg-root ro quiet ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [ 3272.775355] processor parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 algif_skcipher af_alg dm_crypt dm_mod sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel rtsx_pci_sdmmc mmc_core ahci libahci aesni_intel libata aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd scsi_mod xhci_pci ehci_pci xhci_hcd ehci_hcd e1000e rtsx_pci mfd_core ptp usbcore pps_core thermal usb_common thermal_sys [ 3272.775388] CPU: 0 PID: 2118 Comm: Xorg Tainted: GW O 4.0.0-2-amd64 #1 Debian 4.0.8-1 [ 3272.775390] Hardware name: LENOVO 20BX001KUS/20BX001KUS, BIOS JBET47WW (1.12 ) 03/10/2015 [ 3272.775392] a03f9fd0 81562ce2 88032d1fb918 [ 3272.775412] 8106cf91 1000 0010 [ 3272.775418] 88032d425608 000c 8106d00a a03fae25 [ 3272.775456] Call Trace: [ 3272.775480] [] ? dump_stack+0x40/0x50 [ 3272.775498] [] ? warn_slowpath_common+0x81/0xb0 [ 3272.775519] [] ? warn_slowpath_fmt+0x4a/0x50 [ 3272.775546] [] ? process_single_tx_qlock+0x5e0/0x650 [drm_kms_helper] [ 3272.775568] [] ? process_single_down_tx_qlock+0x4a/0x150 [drm_kms_helper] [ 3272.775580] [] ? drm_dp_queue_down_tx+0x5c/0x70 [drm_kms_helper] [ 3272.775593] [] ? drm_dp_mst_i2c_xfer+0x15e/0x270 [drm_kms_helper] [ 3272.775613] [] ? drm_for_each_detailed_block+0x39/0x150 [drm] [ 3272.775621] [] ? __i2c_transfer+0x6c/0x200 [ 3272.775629] [] ? i2c_transfer+0x77/0xd0 [ 3272.775647] [] ? drm_do_probe_ddc_edid+0xcc/0x140 [drm] [ 3272.775667] [] ? drm_get_edid+0x2d/0x3f0 [drm] [ 3272.775695] [] ? gen6_read32+0xd4/0x190 [i915] [ 3272.775702] [] ? mutex_lock+0xe/0x30 [ 3272.775718] [] ? drm_dp_mst_get_edid+0x6c/0x80 [drm_kms_helper] [ 3272.775742] [] ? intel_dp_mst_get_modes+0x28/0x50 [i915] [ 3272.775767] [] ? drm_helper_probe_single_connector_modes_merge_bits+0xf2/0x4d0 [drm_kms_helper] [ 3272.775782] [] ? mutex_lock+0xe/0x30 [ 3272.775804] [] ? drm_mode_getconnector+0x310/0x370 [drm] [ 3272.775824] [] ? drm_ioctl+0x1c3/0x5a0 [drm] [ 3272.775832] [] ? __hrtimer_start_range_ns+0x2dd/0x420 [ 3272.775836] [] ? do_vfs_ioctl+0x2e8/0x4f0 [ 3272.775843] [] ? __sys_recvmsg+0x65/0x80 [ 3272.775846] [] ? SyS_ioctl+0x81/0xa0 [ 3272.775851] [] ? system_call_fast_compare_end+0xc/0x11 [ 3272.775854] ---[ end trace b32110bf3e587dfc ]--- [ 3272.778830] [ cut here ] [ 3272.778842] WARNING: CPU: 0 PID: 2118 at /build/linux-aqtDGz/linux-4.0.8/drivers/gpu/drm/drm_dp_mst_topology.c:1272 process_single_tx_qlock+0x5e0/0x650 [drm_kms_helper]() [ 3272.778844] fail [ 3272.778845] Modules linked in: hid_kensington hid_generic usbhid hid fuse ctr ccm bnep pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc joydev
Bug#792769: marked as done (linux-image-4.0.0-2-686-pae - hibernate not working correctly)
Your message dated Fri, 30 Apr 2021 15:38:10 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #792769, regarding linux-image-4.0.0-2-686-pae - hibernate not working correctly 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.) -- 792769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.0.8-1 Severity: important Dear maintainers, since the update from kernel 3.16 to 4.0.0, suspend to disk is not working correctly. The bug shows as follows: When hibernation is activated (either manually or by closing lid), all memory is written to swap, then the screen is switched off. But after this, the computer should be switched off, which does not. The computer is still switched on. I can reproduce this bug by reverting back to kernel 3.16 (where everything is ok), then booting kernel 4.0.0. and the bug appears again. It would be nice, if you could take a look at it. At the moment I have to stay at kernel 3.16 due it is not usable for me at the moment as this one and another major bug (#792627). Thank you for any help! Best regards Hans-J. Ullrich Thank you very much. --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#790050: marked as done (linux-image-4.0.0-2-amd64: Cannot use sdcard: DMA: Out of SW-IOMMU space for 65536 bytes at device 0000:02:00.0)
Your message dated Fri, 30 Apr 2021 15:37:27 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #790050, regarding linux-image-4.0.0-2-amd64: Cannot use sdcard: DMA: Out of SW-IOMMU space for 65536 bytes at device :02:00.0 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.) -- 790050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.0.5-1 Severity: important Dear Maintainer, I am getting errors from kernel while using sdcard. Cannot use it, getting i/o errors. -- Package-specific info: ** Version: Linux version 4.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-21) ) #1 SMP Debian 4.0.5-1 (2015-06-16) ** Command line: BOOT_IMAGE=/vmlinuz-4.0.0-2-amd64 root=UUID=cf003a88-7b95-426f-a0e8-7b1a5a589ef9 ro elevator=deadline quiet acpi_backlight=vendor acpi_osi=Linux thinkpad-acpi.brightness_enable=1 video.use_native_backlight=1 ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [ 4067.094735] [] ? cpu_startup_entry+0x36f/0x420 [ 4067.094739] [] ? tick_check_new_device+0xe0/0x110 [ 4067.094744] [] ? start_secondary+0x199/0x1c0 [ 4067.094747] ---[ end trace f961235527a8beac ]--- [ 4067.098191] DMA: Out of SW-IOMMU space for 65536 bytes at device :02:00.0 [ 4067.098197] [ cut here ] [ 4067.098222] WARNING: CPU: 2 PID: 0 at /build/linux-YbgLKW/linux-4.0.5/drivers/mmc/host/sdhci.c:857 sdhci_send_command+0xa76/0xc50 [sdhci]() [ 4067.098224] Modules linked in: fuse ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_multiport iptable_filter ip_tables x_tables rfcomm bnep pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 serpent_avx_x86_64 serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cbc cmac xcbc rmd160 sha512_ssse3 sha512_generic sha256_ssse3 sha256_generic hmac crypto_null af_key xfrm_algo nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc tun loop parport_pc [ 4067.098272] ppdev lp parport iTCO_wdt iTCO_vendor_support arc4 iwldvm snd_hda_codec_hdmi mac80211 x86_pkg_temp_thermal snd_hda_codec_realtek intel_powerclamp snd_hda_codec_generic intel_rapl btusb iosf_mbi bluetooth coretemp kvm_intel iwlwifi kvm cfg80211 qmi_wwan cdc_wdm usbnet mii qcserial usb_wwan usbserial efi_pstore pcspkr evdev psmouse serio_raw efivars snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm thinkpad_acpi snd_timer lpc_ich nvram sg i2c_i801 mfd_core snd shpchp i915 soundcore wmi rfkill battery ac drm_kms_helper tpm_tis tpm drm mei_me mei i2c_algo_bit video processor button ext4 crc16 mbcache jbd2 algif_skcipher af_alg dm_crypt dm_mod sd_mod uas usb_storage mmc_block crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel [ 4067.098325] aes_x86_64 lrw gf128mul glue_helper ablk_helper ahci cryptd libahci libata scsi_mod sdhci_pci sdhci xhci_pci ehci_pci mmc_core xhci_hcd e1000e ehci_hcd ptp pps_core usbcore thermal usb_common thermal_sys [ 4067.098346] CPU: 2 PID: 0 Comm: swapper/2 Tainted: GW O 4.0.0-2-amd64 #1 Debian 4.0.5-1 [ 4067.098349] Hardware name: LENOVO 2306CTO/2306CTO, BIOS G2ETA3WW (2.63 ) 02/05/2015 [ 4067.098351] a008a460 8156393b [ 4067.098355] 8106ce91 88040afac4c0 88039c5be8f0 88039c5be970 [ 4067.098359] 0001 a0087cd6 8800d29983f8 [ 4067.098363] Call Trace: [ 4067.098365][] ? dump_stack+0x40/0x50 [ 4067.098383] [] ? warn_slowpath_common+0x81/0xb0 [ 4067.098397] [] ? sdhci_send_command+0xa76/0xc50 [sdhci] [ 4067.098404] [] ? native_sched_clock+0x26/0x90 [ 4067.098417] [] ? sdhci_irq+0x308/0x91b [sdhci] [ 4067.098423] [] ? ttwu_do_wakeup+0x14/0xd0 [ 4067.098429] [] ? timerqueue_del+0x22/0x70 [ 4067.098435] [] ? handle_irq_event_percpu+0x75/0x190 [ 4067.098439] [] ? read_tsc+0x5/0x10 [ 4067.098443] [] ? read_tsc+0x5/0x10 [ 4067.098447] [] ? handle_irq_event+0x3e/0x60 [ 4067.098452] [] ? handle_fasteoi_irq+0x8d/0x170 [ 4067.098458] [] ? handle_irq+0x1d/0x30 [ 4067.098462] [] ?
Bug#790346: marked as done (linux-image-3.16.0-4-amd64: btrfs snapshot gives error in syslog)
Your message dated Fri, 30 Apr 2021 15:37:41 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #790346, regarding linux-image-3.16.0-4-amd64: btrfs snapshot gives error in syslog 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.) -- 790346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? btrfs snapshot of subvolume * What exactly did you do (or not do) that was effective (or ineffective)? I daily take a snapshot of my btrfs file system (and delete the old). This week I upgraded to Debian 8, since then I get the following in the syslog: A 'btrfs scrub start /' was done, no problems/errors detected. A 'btrfs bal start /' crashes the system. [63691.969080] [ cut here ] [63691.969116] WARNING: CPU: 0 PID: 149 at /build/linux-QZaPpC/linux-3.16.7-ckt11/fs/btrfs/qgroup.c:1353 btrfs_delayed_qgroup_accounting+0x79e/0xbd0 [btrfs]() [63691.969117] Modules linked in: xt_multiport iptable_filter ip_tables x_tables joydev iTCO_wdt iTCO_vendor_support coretemp arc4 kvm_intel ppdev kvm evdev psmouse pcspkr serio_raw i2c_i80$ [63691.969160] CPU: 0 PID: 149 Comm: btrfs-cleaner Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt11-1 [63691.969162] Hardware name: FUJITSU SIEMENS ESPRIMO Mobile D9500/Z11D, BIOS 1.06 - 046 - 1566 04/22/2008 [63691.969164] 0009 8150b405 81067797 [63691.969167] 88007708d918 880036ac3d88 880014a46f60 880036e5a0c8 [63691.969169] 880036f09000 a01f907e 000b 880035078000 [63691.969172] Call Trace: [63691.969179] [] ? dump_stack+0x41/0x51 [63691.969183] [] ? warn_slowpath_common+0x77/0x90 [63691.969194] [] ? btrfs_delayed_qgroup_accounting+0x79e/0xbd0 [btrfs] [63691.969204] [] ? btrfs_run_delayed_refs.part.64+0x207/0x280 [btrfs] [63691.969215] [] ? btrfs_should_end_transaction+0x3d/0x60 [btrfs] [63691.969225] [] ? btrfs_drop_snapshot+0x458/0x7d0 [btrfs] [63691.969229] [] ? __schedule+0x2b1/0x710 [63691.969240] [] ? btrfs_clean_one_deleted_snapshot+0xbe/0x110 [btrfs] [63691.969250] [] ? cleaner_kthread+0x120/0x180 [btrfs] [63691.969261] [] ? check_leaf+0x3a0/0x3a0 [btrfs] [63691.969265] [] ? kthread+0xbd/0xe0 [63691.969267] [] ? kthread_create_on_node+0x180/0x180 [63691.969270] [] ? ret_from_fork+0x58/0x90 [63691.969273] [] ? kthread_create_on_node+0x180/0x180 [63691.969274] ---[ end trace e2e98137cca25c80 ]--- With my previous kernel (3.14-bpo) everything worked fine. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=fe95e563-9296-47ac-83e7-bfc42f43574e ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 736.484733] BTRFS info (device sdb2): relocating block group 515458990080 flags 17 [ 736.905252] BTRFS info (device sdb2): relocating block group 514385248256 flags 17 [ 737.414820] BTRFS info (device sdb2): relocating block group 513311506432 flags 17 [ 737.835192] BTRFS info (device sdb2): relocating block group 512237764608 flags 17 [ 738.322134] BTRFS info (device sdb2): found 17 extents [ 741.748295] BTRFS info (device sdb2): found 17 extents [ 742.477514] BTRFS info (device sdb2): relocating block group 511164022784 flags 17 [ 742.960885] BTRFS info (device sdb2): relocating block group 510090280960 flags 17 [ 743.602710] BTRFS info (device sdb2): found 1 extents [ 747.051738] BTRFS info (device sdb2): found 1 extents [ 748.308003] BTRFS info (device sdb2): relocating block group 509016539136 flags 17 [ 749.441981] BTRFS info (device sdb2): relocating block group 507942797312 flags 17 [ 750.803314] BTRFS info (device sdb2): relocating block group 506869055488 flags 17 [ 752.496433] BTRFS info (device sdb2): relocating block group 505795313664 flags 17 [ 753.770136] BTRFS info (device sdb2): relocating block group 504721571840 flags 17 [ 754.821444] BTRFS info (device sdb2): found 1 extents [ 757.069205] BTRFS info (device
Bug#789770: marked as done (linux-image-3.16.0-4-amd64: Dell R310 server (Xen 4.4 Dom0) periodically crashing after upgrade to Jessie from Wheezy)
Your message dated Fri, 30 Apr 2021 15:36:32 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #789770, regarding linux-image-3.16.0-4-amd64: Dell R310 server (Xen 4.4 Dom0) periodically crashing after upgrade to Jessie from Wheezy 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.) -- 789770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the server from wheezy to jessie the server, which is a Xen 4.4 Dom0, it is crashing every 2-3 days and bringing down all its hosted VMs, with the following syslog dump: Jun 24 13:24:09 servername kernel: [438520.690952] WARNING: CPU: 0 PID: 0 at /build/linux-QZaPpC/linux-3.16.7-ckt11/net/sched/sch_generic.c:264 dev_watchdog+0x236/0x240() Jun 24 13:24:09 servername kernel: [438520.690959] NETDEV WATCHDOG: eth0 (bnx2): transmit queue 7 timed out Jun 24 13:24:09 servername kernel: [438520.690963] Modules linked in: dm_snapshot dm_bufio binfmt_misc xt_physdev xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi bridge stp llc xt_tcpudp xt_recent xt_conntrack iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables joydev acpi_power_meter coretemp ipmi_devintf evdev ttm drm_kms_helper drm i2c_algo_bit dcdbas iTCO_wdt iTCO_vendor_support i2c_core pcspkr button ipmi_si tpm_tis ipmi_msghandler tpm lpc_ich i7core_edac mfd_core edac_core processor shpchp thermal_sys loop autofs4 ext4 crc16 mbcache jbd2 dm_mod sd_mod crc_t10dif crct10dif_generic sg ses crct10dif_common enclosure sr_mod cdrom usb_storage hid_generic usbhid hid ata_generic crc32c_intel ehci_pci ata_piix ehci_hcd libata m egaraid_sas usbcore usb_common scsi_mod bnx2 Jun 24 13:24:09 servername kernel: [438520.691049] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt11-1 Jun 24 13:24:09 servername kernel: [438520.691052] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.6.4 03/03/2011 Jun 24 13:24:09 servername kernel: [438520.691055] 0009 8150b405 88007c803e28 81067797 Jun 24 13:24:09 servername kernel: [438520.691059] 0007 88007c803e78 0008 Jun 24 13:24:09 servername kernel: [438520.691062] 880002444000 810677fc 81777fb8 8830 Jun 24 13:24:09 servername kernel: [438520.691066] Call Trace: Jun 24 13:24:09 servername kernel: [438520.691069][] ? dump_stack+0x41/0x51 Jun 24 13:24:09 servername kernel: [438520.691081] [] ? warn_slowpath_common+0x77/0x90 Jun 24 13:24:09 servername kernel: [438520.691085] [] ? warn_slowpath_fmt+0x4c/0x50 Jun 24 13:24:09 servername kernel: [438520.691092] [] ? dev_watchdog+0x236/0x240 Jun 24 13:24:09 servername kernel: [438520.691096] [] ? dev_graft_qdisc+0x70/0x70 Jun 24 13:24:09 servername kernel: [438520.691102] [] ? call_timer_fn+0x31/0x100 Jun 24 13:24:09 servername kernel: [438520.691108] [] ? dev_graft_qdisc+0x70/0x70 Jun 24 13:24:09 servername kernel: [438520.691113] [] ? run_timer_softirq+0x209/0x2f0 Jun 24 13:24:09 servername kernel: [438520.691117] [] ? __do_softirq+0xf1/0x290 Jun 24 13:24:09 servername kernel: [438520.691122] [] ? irq_exit+0x95/0xa0 Jun 24 13:24:09 servername kernel: [438520.691128] [] ? xen_evtchn_do_upcall+0x35/0x50 Jun 24 13:24:09 servername kernel: [438520.691135] [] ? xen_do_hypervisor_callback+0x1e/0x30 Jun 24 13:24:09 servername kernel: [438520.691137][] ? xen_hypercall_sched_op+0xa/0x20 Jun 24 13:24:09 servername kernel: [438520.691145] [] ? xen_hypercall_sched_op+0xa/0x20 Jun 24 13:24:09 servername kernel: [438520.691150] [] ? xen_safe_halt+0xc/0x20 Jun 24 13:24:09 servername kernel: [438520.691154] [] ? default_idle+0x19/0xb0 Jun 24 13:24:09 servername kernel: [438520.691158] [] ? cpu_startup_entry+0x340/0x400 Jun 24 13:24:09 servername kernel: [438520.691161] [] ? start_kernel+0x492/0x49d Jun 24 13:24:09 servername kernel: [438520.691163] [] ? set_init_arg+0x4e/0x4e Jun 24 13:24:09 servername kernel: [438520.691166] [] ? xen_start_kernel+0x569/0x573 Jun 24 13:24:09 servername kernel: [438520.691169] ---[ end trace 05255fd39e925fd5 ]--- Jun 24
Bug#788656: marked as done (missing patch for apparmor with lxc)
Your message dated Fri, 30 Apr 2021 15:36:16 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #788656, regarding missing patch for apparmor with lxc 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.) -- 788656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxc Version: 1:1.0.6-6 Severity: important Dear Maintainer, lxc-start does not seem to switch lxc containers to the default profile. aa-status reports lxc-start keeping the 'lxc-start' profile after the container has launched. I installed packages lxc, apparmor, apparmor-utils, apparmor-profiles* on jessie, fully patched. AppArmor works fine for libvirt (qemu/kvm machine profiles) and all others. I created: lxc-create -n myvm -t debian -- -r jessie executed: lxc-start -n myvm However, when I run aa-status, the output is: apparmor module is loaded. 68 profiles are loaded. 31 profiles are in enforce mode. [...] /usr/bin/lxc-start [...] lxc-container-default lxc-container-default-with-mounting lxc-container-default-with-nesting 37 profiles are in complain mode. [...] 18 processes have profiles defined. 14 processes are in enforce mode. /usr/bin/lxc-start (2596) /usr/bin/lxc-start (2598) /usr/bin/lxc-start (2620) /usr/bin/lxc-start (2687) /usr/bin/lxc-start (2693) /usr/bin/lxc-start (2694) /usr/bin/lxc-start (2695) /usr/bin/lxc-start (2696) /usr/bin/lxc-start (2697) /usr/bin/lxc-start (3572) /usr/bin/lxc-start (3573) /usr/sbin/cups-browsed (1214) /usr/sbin/cupsd (1210) /usr/sbin/libvirtd (1166) 4 processes are in complain mode. [...] 0 processes are unconfined but have a profile defined. It shows lxc-container-default as not loaded. Setting lxc.aa_profile = unconfined|lxc-container-default|lxc-default in /var/lib/lxc/myvm/config all produce the same result. I compared this to a Ubuntu installation with roughly the same steps. Its output is: 21 processes are in enforce mode. /sbin/dhclient (897) /usr/bin/lxc-start (2348) /usr/sbin/cups-browsed (583) /usr/sbin/cupsd (546) lxc-container-default (2356) lxc-container-default (2547) lxc-container-default (2569) lxc-container-default (2665) lxc-container-default (2679) lxc-container-default (2680) lxc-container-default (2686) lxc-container-default (2728) lxc-container-default (2733) lxc-container-default (2752) lxc-container-default (2754) lxc-container-default (2755) lxc-container-default (2764) lxc-container-default (2784) lxc-container-default (2795) lxc-container-default (2796) lxc-container-default (2799) 2 processes are in complain mode. That is what I would expect. So going by aa-status it appears LXC isn't switching to the container profile in Jessie. Unless I'm missing a package this would be a security issue. Couldn't find a specific in the logs but it's not my forte. Thank you -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxc depends on: ii init-system-helpers 1.22 ii libapparmor1 2.9.0-3 ii libc62.19-18 ii libcap2 1:2.24-8 ii libseccomp2 2.1.1-1 ii libselinux1 2.3-2 ii multiarch-support2.19-18 ii python3 3.4.2-2 Versions of packages lxc recommends: ii debootstrap 1.0.67 ii openssl 1.0.1k-3+deb8u1 ii rsync3.1.1-3 Versions of packages lxc suggests: pn lua5.2 -- no debconf information --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#784262: marked as done (linux-image-3.16.0-4-686-pae: System hangs at poweroff command)
Your message dated Fri, 30 Apr 2021 15:33:36 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #784262, regarding linux-image-3.16.0-4-686-pae: System hangs at poweroff command 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.) -- 784262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt9-3~deb8u1 Severity: important Dear Maintainer, I have installed debian jessie last week on my laptop. Since then my system hangs when I order it to shutdown. Because of the new init-system I first checked whether systemd was to blame using this guide: http://freedesktop.org/wiki/Software/systemd/Debugging/ I started up in recovery mode and issued the "shutdown" command. All services were shutdown, all processes were killed etc. But the system hanged at the very end, when it needed to go off. I then disabled the system by keeping the power button pressed. I restarted again in recovery mode. This time I issued the "poweroff -f" command. The system failed to poweroff again and kept hanging. The cursor blinked, but I could not ctrl+c and issue new commands. According to the guide this is a kernel issue and not systemd's fault. I did not have this problem on debian wheezy using the default 3.2 linux-kernel. I have attached a sysinfo file in case it may be related to my hardware. Could you please look into this issue? Shutting down is a function I use multiple times per day using this laptop. When the laptop refuses to poweroff it drains the battery and I can't help but feel that forcing it to poweroff with the power button is not healthy for the system. I therefore flagged the bug as "important" and I hope the fix can help other users who are experiencing the same problem. If there is any more information you need I will be glad to help. Thank you very much for considering this problem! Kind regards, Ruben Vorderman -- Package-specific info: ** Version: Linux version 3.16.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae root=UUID=1d82564a-a25a- 4b84-b057-e832c9e50701 ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [9.597043] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: [9.597052] excluding 0xc-0xc7fff 0xcc000-0xc 0xdc000-0xf [9.597091] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: [9.597114] clean. [9.597136] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: [9.597144] excluding 0x6000-0x600f [9.597183] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: [9.597963] clean. [9.640864] fbcon: inteldrmfb (fb0) is primary device [ 10.055024] kvm: disabled by bios [ 10.069384] kvm: disabled by bios [ 10.137246] coretemp coretemp.0: Using relative temperature scale! [ 10.137268] coretemp coretemp.0: Using relative temperature scale! [ 10.203086] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [ 10.302716] ath5k :04:00.0: can't disable ASPM; OS doesn't have ASPM control [ 10.302896] ath5k :04:00.0: registered as 'phy0' [ 10.528154] Console: switching to colour frame buffer device 160x50 [ 10.534748] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 10.534810] i915 :00:02.0: registered panic notifier [ 10.548066] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 10.550504] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X [ 10.562243] Adding 3145724k swap on /dev/sda3. Priority:-1 extents:1 across:3145724k FS [ 10.725819] sound hdaudioC0D0: autoconfig: line_outs=1 (0xb/0x0/0x0/0x0/0x0) type:line [ 10.725911] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 10.725977] sound hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 10.726038] sound hdaudioC0D0:mono: mono_out=0x0 [ 10.726088] sound hdaudioC0D0:inputs: [ 10.726130] sound hdaudioC0D0: Internal Mic=0x10 [ 10.726181] sound hdaudioC0D0: Mic=0xd [ 10.789079] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/sound/card0/hdaudioC0D0/input14 [ 10.791303] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input15 [ 10.851271] ath: EEPROM regdomain: 0x30 [ 10.851342] ath: EEPROM indicates we should expect a direct regpair map [ 10.851443] ath: Country alpha2 being used: AM [ 10.853829]
Bug#785601: marked as done (linux-image-3.16.0-4-amd64: DualPoint TouchPad at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away)
Your message dated Fri, 30 Apr 2021 15:34:54 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #785601, regarding linux-image-3.16.0-4-amd64: DualPoint TouchPad at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away 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.) -- 785601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt9-2 Severity: normal Dear Maintainer, Since I migrated away from wheezy to jessie, I am having lots of trouble using the touchpad. I keep getting: [ 536.216745] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 536.729797] psmouse serio1: resync failed, issuing reconnect request [ 716.338204] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. [ 716.849390] psmouse serio1: resync failed, issuing reconnect request which result in unrelable behavior (pointer stops and jumps around). Using debugfs I can see the following pattern: [ 717.30] psmouse serio1: alps: E6 report: 00 00 64 [ 717.328605] psmouse serio1: alps: E7 report: 73 02 64 [ 717.352794] psmouse serio1: alps: EC report: 88 07 9d [ 717.374019] psmouse serio1: alps: EC report: 88 07 9d [ 717.423501] psmouse serio1: alps: EC report: 88 07 9d As far as I remember it used to work properly in older linux kernel version. This laptop (DELL Vostro 3750) is a dual boot system and I do not have any single issue when running Windows 7/64bits Pro on it. If that matter: i8kfan 1 1 does not have any effect anymore of the fan, and my fan are running very oddly since the upgrade (runs quickly and stop quickly). My USB mouse does not seems to be powered for the first few seconds (gnome session). And keyboard seems to produce duplicate key events. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=0b17f6ae-4025-41be-ab21-1f6e2472ad73 ro quiet acpi_backlight=vendor ** Not tainted ** Kernel log: [ 14.944538] ACPI: Video Device [PEGP] (multi-head: yes rom: yes post: no) [ 14.944668] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:26/LNXVIDEO:00/input/input11 [ 14.960484] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 14.960611] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12 [ 14.960714] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 14.961098] snd_hda_intel :00:1b.0: irq 54 for MSI/MSI-X [ 14.977235] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled [ 14.977238] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled [ 14.977240] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled [ 14.977241] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0 [ 14.977334] iwlwifi :02:00.0: L1 Enabled - LTR Disabled [ 15.160582] sound hdaudioC0D0: autoconfig: line_outs=2 (0x14/0x1a/0x0/0x0/0x0) type:speaker [ 15.160586] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.160588] sound hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.160589] sound hdaudioC0D0:mono: mono_out=0x0 [ 15.160591] sound hdaudioC0D0:inputs: [ 15.160593] sound hdaudioC0D0: Mic=0x18 [ 15.160594] sound hdaudioC0D0: Internal Mic=0x12 [ 15.165784] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/sound/card0/hdaudioC0D0/input13 [ 15.165957] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input14 [ 15.166010] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input15 [ 15.167005] intel_rapl: Found RAPL domain package [ 15.167009] intel_rapl: Found RAPL domain core [ 15.167012] intel_rapl: Found RAPL domain uncore [ 15.408162] media: Linux media interface: v0.10 [ 15.438314] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 15.526200] Linux video capture interface: v2.00 [ 15.566019] cfg80211: Calling CRDA to update world regulatory domain [ 15.844754] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [ 16.177267] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_FHD (1bcf:2b81) [ 16.199867] input: Laptop_Integrated_Webcam_FHD as
Bug#784579: marked as done ([REGRESSION] vmwgfx black screen until X started)
Your message dated Fri, 30 Apr 2021 15:34:17 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #784579, regarding [REGRESSION] vmwgfx black screen until X started 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.) -- 784579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt9-3~deb8u1 Severity: important The installation has been a Debian 7 system in a VMware Workstation 11 environment which runs under Windows 7x64 on a HP G61 laptop. There is no display manager installed. Linux just boots to a console login prompt. X11 is started manually after login using "startx". The vesa mode for Linux is set in /etc/default/grub using "GRUB_GFXPAYLOAD_LINUX=1366x768x8". The kernel package used in Debian 7 was linux-image-3.2.0-4-amd64. The system is now upgraded to Debian 8 (Jessie). Old kernel is still installed (optional boot via Grub). The new kernel (see subject) boots normal. VESA screen mode is set. But when DRM initializes the screen goes dark. The last message I cound see was: "[drm] Initialized drm 1.1.0 20060810". The system then completes the boot process normally but the screen stays dark. The system still resonds to the keyboard. I can login typing blindly and then start X11 typing blindly. X11 launches and the screen starts working. After logging out of X11 the console comes back to life, using the VESA mode it is supposed to use. This problem does not occur if I boot Jessie with the old 3.2.0-4 kernel which I still have installed (a leftover from the upgrade process). The problem therefore is not related to grub or the surrounding environment (VMware Workstation 11 virtual machine). It is also not dependent on if I select systemd or sysvinit at boot. The only thing it depends on is the kernel image. If you need any other information, please let me know. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=9f0f6795-79de-40b4-9b55-37967d4d395e ro clocksource=acpi_pm noresume ipv6.disable=1 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 12.609836] systemd[1]: Started udev Coldplug all Devices. [ 12.672981] loop: module loaded [ 12.711217] systemd[1]: Started Create list of required static device nodes for the current kernel. [ 12.712542] systemd[1]: Starting Create Static Device Nodes in /dev... [ 12.976492] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 [ 12.978206] vmw_vmci :00:07.7: Using capabilities 0xc [ 12.979396] vmw_vmci :00:07.7: irq 72 for MSI/MSI-X [ 12.979520] vmw_vmci :00:07.7: irq 73 for MSI/MSI-X [ 12.980329] Guest personality initialized and is active [ 12.981448] VMCI host device registered (name=vmci, major=10, minor=59) [ 12.982038] Initialized host personality [ 13.040301] systemd[1]: Started Load Kernel Modules. [ 13.042247] systemd[1]: Mounting FUSE Control File System... [ 13.044692] systemd[1]: Starting Apply Kernel Variables... [ 13.047278] systemd[1]: Mounted Configuration File System. [ 13.157679] systemd[1]: Started Increase datagram queue length. [ 13.160344] systemd[1]: Starting Syslog Socket. [ 13.162282] systemd[1]: Listening on Syslog Socket. [ 13.163297] systemd[1]: Starting Journal Service... [ 13.169404] systemd[1]: Started Journal Service. [ 13.479538] systemd-udevd[163]: starting version 215 [ 15.799082] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 15.800624] ACPI: Power Button [PWRF] [ 16.013242] piix4_smbus :00:07.3: SMBus Host Controller not enabled! [ 16.019237] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [ 16.098070] ACPI: AC Adapter [ACAD] (on-line) [ 16.111492] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 16.165681] [drm] Initialized drm 1.1.0 20060810 [ 16.392818] [drm] DMA map mode: Using physical TTM page addresses. [ 16.392931] [drm] Capabilities: [ 16.392932] [drm] Rect copy. [ 16.392932] [drm] Cursor. [ 16.392933] [drm] Cursor bypass. [ 16.392933] [drm] Cursor bypass 2. [ 16.392934] [drm] 8bit emulation. [ 16.392934] [drm] Alpha cursor. [ 16.392934] [drm] 3D. [ 16.392935] [drm] Extended Fifo. [ 16.392935] [drm] Multimon. [ 16.392935] [drm] Pitchlock. [ 16.392936] [drm] Irq mask. [
Bug#785277: marked as done ([4.0][regression] r8169: (unnamed net_device) (uninitialized): unknown MAC, using family default)
Your message dated Fri, 30 Apr 2021 15:34:33 +0200
with message-id
and subject line Closing this bug
has caused the Debian Bug report #785277,
regarding [4.0][regression] r8169: (unnamed net_device) (uninitialized):
unknown MAC, using family default
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.)
--
785277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.0.2-1
Severity: important
Tags: upstream
Control: notfound -1 linux/3.19-1~exp1
Dear Debian folks,
Booting with `linux-image-4.0.0-1-686-pae` 4.0.2-1 the following errors
are shown on the monitor.
r8169 :03:00.0 (unnamed net_device) (uninitialized):
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Here are all message from the module r8169.
$ dmesg | grep r8169
[1.309298] calling rtl8169_pci_driver_init+0x0/0x1000 [r8169] @ 72
[1.309412] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[1.309648] r8169 :03:00.0 (unnamed net_device) (uninitialized):
unknown MAC, using family default
[1.324615] r8169 :03:00.0 (unnamed net_device) (uninitialized):
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
[1.336859] r8169 :03:00.0 eth0: RTL8168b/8111b at 0xf8222000,
ff:ff:ff:ff:ff:ff, XID 9cf0f8ff IRQ 26
[1.336869] r8169 :03:00.0 eth0: jumbo features [frames: 4080
bytes, tx checksumming: ko]
[1.336949] initcall rtl8169_pci_driver_init+0x0/0x1000 [r8169]
returned 0 after 26918 usecs
The MAC address of the device is ff:ff:ff:ff:ff:ff.
$ ip addr show dev eth0
2: eth0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
This regression was reported to the Linux kernel linux-pci mailing list
[1] and is supposedly a regression of commit *x86/PCI/ACPI: Ignore
resources consumed by host bridge itself*.
I’ll paste Gerry’s reply in here for completeness.
> Hi Bernhard,
> Thanks for providing acpi data. I have figured out the cause of
> the regression. Your platform defines PCI host bridge MMIO resources as:
> Name (CRES, ResourceTemplate ()
> {
> IO (Decode16,
> 0x0CF8, // Range Minimum
> 0x0CF8, // Range Maximum
> 0x01, // Alignment
> 0x08, // Length
> )
> WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode,
> EntireRange,
> 0x, // Granularity
> 0x, // Range Minimum
> 0x0CF7, // Range Maximum
> 0x, // Translation Offset
> 0x0CF8, // Length
> ,, , TypeStatic)
> WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode,
> EntireRange,
> 0x, // Granularity
> 0x0D00, // Range Minimum
> 0x, // Range Maximum
> 0x, // Translation Offset
> 0xF300, // Length
> ,, , TypeStatic)
> Memory32Fixed (ReadOnly,
> 0x000A, // Address Base
> 0x0002, // Address Length
> )
> Memory32Fixed (ReadOnly,
> 0x, // Address Base
> 0x, // Address Length
> _Y00)
> })
>
> With commit (x86/PCI/ACPI: Ignore resources consumed by host bridge
> itself), all resources without PRODUCER flag will be ignored, so
> MMIO defined by Memory32Fixed operator gets ignored. The fix is only
> to ignore IO resources without PRODUCER flag and keeps all MMIO
> resources no matter PRODUCER is set or not.
> Could you please help to try following patch?
> Regards!
> Gerry
>
> diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
> index e4695985f9de..66d7dbe56926 100644
> --- a/arch/x86/pci/acpi.c
> +++ b/arch/x86/pci/acpi.c
> @@ -346,7 +346,7 @@ static void probe_pci_root_info(struct pci_root_info
> *info,
> "no IO and memory resources present in _CRS\n");
> else
> resource_list_for_each_entry_safe(entry, tmp, list) {
> -
Bug#788423: marked as done (linux-image-3.16.0-4-amd64: no inode allocation after xfs_growfs)
Your message dated Fri, 30 Apr 2021 15:35:47 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #788423, regarding linux-image-3.16.0-4-amd64: no inode allocation after xfs_growfs 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.) -- 788423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: linux-image-3.16.0-4-amd64: no inode allocation after xfs_growfs Package: src:linux Version: 3.16.7-ckt9-3~deb8u1 Justification: causes serious data loss Severity: critical Tags: upstream Dear Maintainer, When extending a lvm volume and then the xfs filesystem with wfs_growfs, we often encounter "no space left on device" error even with df reporting a lot of free space and inode. This seems to be related to this patch : http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9de67c3ba9ea961ba420573d56479d09d33a7587 which is implemented in kernel 3.17. Remounting the filesystem allow to write data again. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=0ab4af79-6e21-4c58-8514-2cf849d53ae1 ro quiet -- --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#784305: marked as done (linux-image-3.16.0-4-686-pae: frozen Screen kernel 3.16 with video[NVIDIA Corporation C61 [GeForce 7025 / nForce 630a]])
Your message dated Fri, 30 Apr 2021 15:33:50 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #784305, regarding linux-image-3.16.0-4-686-pae: frozen Screen kernel 3.16 with video[NVIDIA Corporation C61 [GeForce 7025 / nForce 630a]] 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.) -- 784305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt9-3 Severity: important Dear Maintainer, * What led up to the situation? used kernel 3.16or > 3.12 bersion whit video[NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] and Driver "nouveau" * What exactly did you do (or not do) that was effective (or ineffective)? 1) wait for a Xscreensaver ,(runing normal or activate), the muve the mouse to start to work , ( this means STOP Xscreensaver), = i think this make a graphic acceleration. 2) open ICEWEASEL i think this make a graphic acceleration = * What was the outcome of this action? FROZEN SCREEN !! * What outcome did you expect instead? NOT FAILED one more thik, this problem not happen whit kernel 3.2.0-4-686-pae or 3.2.0-3-686-pae. that mean the proble it the kernel ! -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** Network interface configuration: auto lo iface lo inet loopback ** PCI devices: 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP61 Host Bridge [10de:03e2] (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP61 LPC Bridge [10de:03e1] (rev a2) Subsystem: Gigabyte Technology Co., Ltd Device [1458:0c11] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: nForce2_smbus 00:01.2 RAM memory [0500]: NVIDIA Corporation MCP61 Memory Controller [10de:03f5] (rev a2) Subsystem: Gigabyte Technology Co., Ltd Device [1458:0c11] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: ohci_hcd 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP61 USB 2.0 Controller [10de:03f2] (rev a3) (prog-if 20 [EHCI]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004] 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: ehci_hcd 00:04.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI bridge [10de:03f3] (rev a1) (prog-if 01 [Subtractive decode]) 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: 00:05.0 Audio device [0403]: NVIDIA Corporation MCP61 High Definition Audio [10de:03f0] (rev a2) Subsystem: Gigabyte Technology Co., Ltd Device [1458:a002] 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 00:07.0 Bridge [0680]: NVIDIA Corporation MCP61 Ethernet [10de:03ef] (rev a2) Subsystem: Gigabyte Technology Co., Ltd Device [1458:e000] 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: forcedeth 00:08.0 IDE interface [0101]: NVIDIA Corporation MCP61 SATA Controller [10de:03f6] (rev a2) (prog-if 85 [Master SecO PriO]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:b002] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+
Bug#784337: marked as done (usb: [29493.628253] hub 1-0:1.0: unable to enumerate USB device on port 6)
Your message dated Fri, 30 Apr 2021 15:34:04 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #784337, regarding usb: [29493.628253] hub 1-0:1.0: unable to enumerate USB device on port 6 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.) -- 784337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: usbutils Version: 1:007-2 Severity: important File: usb Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Connecting Sandisk Ultra 32GB micro * What exactly did you do (or not do) that was effective (or ineffective)? Just connectiog via usb * What was the outcome of this action? [29493.440259] hub 1-0:1.0: unable to enumerate USB device on port 6 very often, nothing else can be seen * What outcome did you expect instead? mounting on /media/usb0 *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages usbutils depends on: ii libc6 2.19-18 ii libusb-1.0-0 2:1.0.19-1 ii zlib1g1:1.2.8.dfsg-2+b1 usbutils recommends no packages. Versions of packages usbutils suggests: ii lynx-cur 2.8.9dev5-2 ii wget 1.16.3-2 -- debconf-show failed --- End Message --- --- Begin Message --- This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control--- End Message ---
Bug#783881: marked as done (Jessie: hanging on shutdown after turning off display and disks)
Your message dated Fri, 30 Apr 2021 15:33:21 +0200
with message-id
and subject line Closing this bug
has caused the Debian Bug report #783881,
regarding Jessie: hanging on shutdown after turning off display and disks
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.)
--
783881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt9-3~deb8u1
Severity: important
If I do a shutdown from MATE, my system does the following:
* MATE closes as expected
* within a couple of seconds the display switches off (all OK so far)
* then very shortly after that I hear at least some of my disks spinning down
(as I'd expect)
* However my CPU and power fans continue to spin, and my power LED remains on.
I would expect the system to power off at this point.
To power off, I have to press and hold the power button for a few seconds.
I can't see any kernel messages at this point because by this stage the graphics
card has switched off.
I can reboot normally, and I can also press the RESET button and boot fine
once the shutdown process has hung in the described not-quite-off state.
This problem is intermittent, but seems much more likely to occur
if shutting down after a cold boot than it is if shutting down having
rebooted the machine.
Have previously had this enabled in /etc/hdparm.conf, around the time I started
to notice this issue:
/dev/disk/by-id/ata-WDC_WD30EZRX-00SPEB0_WD-WCC4EHHH3TH7 {
spindown_time = 240
}
/dev/disk/by-id/ata-WDC_WD30EZRX-00SPEB0_WD-WCC4ENVNFAV0 {
spindown_time = 240
}
/dev/disk/by-id/ata-WDC_WD20EARX-00ZUDB0_WD-WCC1H0246293 {
spindown_time = 240
}
I've now commented them out but it's still giving me problems, so
I doubt those spindown_times have caused the problem but thought I'd
mention it in case anyone disagrees (I'm unsure if they continue to take
effect across cold boots).
This is Debian Jessie, installed from scratch.
-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24)
** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/oak-debian ro
** Not tainted
** Kernel log:
[8.363510] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[8.363565] ACPI Warning: SystemIO range
0x0500-0x052f conflicts with OpRegion
0x0500-0x053f (\GPS0) (20140424/utaddress-258)
[8.363693] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[8.363748] lpc_ich: Resource conflict(s) found affecting gpio_ich
[8.418058] ACPI Warning: SystemIO range
0x0400-0x041f conflicts with OpRegion
0x0400-0x040f (\SMRG) (20140424/utaddress-258)
[8.418188] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[8.533746] input: PC Speaker as /devices/platform/pcspkr/input/input10
[8.673093] sound hdaudioC0D0: autoconfig: line_outs=4
(0x14/0x15/0x16/0x17/0x0) type:line
[8.673151] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[8.673196] sound hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[8.673240] sound hdaudioC0D0:mono: mono_out=0x0
[8.673283] sound hdaudioC0D0:dig-out=0x11/0x1e
[8.673326] sound hdaudioC0D0:inputs:
[8.673369] sound hdaudioC0D0: Front Mic=0x19
[8.673412] sound hdaudioC0D0: Rear Mic=0x18
[8.673454] sound hdaudioC0D0: Line=0x1a
[8.685084] input: HDA Digital PCBeep as
/devices/pci:00/:00:1b.0/sound/card0/hdaudioC0D0/input11
[8.685307] input: HDA Intel Front Mic as
/devices/pci:00/:00:1b.0/sound/card0/input12
[8.685392] input: HDA Intel Rear Mic as
/devices/pci:00/:00:1b.0/sound/card0/input13
[8.685476] input: HDA Intel Line as
/devices/pci:00/:00:1b.0/sound/card0/input14
[8.685560] input: HDA Intel Line Out Front as
/devices/pci:00/:00:1b.0/sound/card0/input15
[8.685645] input: HDA Intel Line Out Surround as
/devices/pci:00/:00:1b.0/sound/card0/input16
[8.685730] input: HDA Intel Line Out CLFE as
/devices/pci:00/:00:1b.0/sound/card0/input17
[8.685815] input: HDA Intel Line Out Side as
/devices/pci:00/:00:1b.0/sound/card0/input18
[8.685900] input: HDA Intel Front Headphone as
Bug#783365: marked as done (linux-image-3.16.0-4-amd64: wired interface goes down with 'fatal interrupt' spam in kernel log)
Your message dated Fri, 30 Apr 2021 15:32:22 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #783365, regarding linux-image-3.16.0-4-amd64: wired interface goes down with 'fatal interrupt' spam in kernel log 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.) -- 783365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt9-3 Severity: important Dear Maintainer, * What led up to the situation? This bug seems to appear randomly. At some point of running my laptop shuts down wired interface (in all ~8 occassions i've been actively using network). I am using alienware m17x laptop with mix of testing (which is stable Jessie since yesterday) and unstable, with following pin-priorities: $ cat /etc/apt/preferences Package: * Pin: release a=testing Pin-Priority: 500 Package: * Pin: release a=unstable Pin-Priority: 499 Package: * Pin: release a=experimental Pin-Priority: -10 >From unstable i'm using mostly wine-development and virtualbox packages (when they were removed from testing). I am using Gnome with network-manager. Virtualbox and nvidia kernel modules are probably two which taint kernel. Unfortunately i'm using both for my everyday tasks - so it's hard to reproduce bug on clean kernel, given it's seemingly random nature. I observed 1st manifestation of bug after i received my laptop from service and upgraded my system. According to service engineers, they did nothing but clean some dust and replace thermic interfaces, thus most likely following system update led to an issue: === [UPGRADE] apt:amd64 1.0.9.7 -> 1.0.9.8 [UPGRADE] apt-utils:amd64 1.0.9.7 -> 1.0.9.8 [UPGRADE] avahi-autoipd:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] avahi-daemon:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] console-setup:amd64 1.120 -> 1.123 [UPGRADE] console-setup-linux:amd64 1.120 -> 1.123 [UPGRADE] dmsetup:amd64 2:1.02.90-2.1 -> 2:1.02.90-2.2 [UPGRADE] dpkg:amd64 1.17.24 -> 1.17.25 [UPGRADE] dpkg-dev:amd64 1.17.24 -> 1.17.25 [UPGRADE] gir1.2-upowerglib-1.0:amd64 0.99.1-3.1 -> 0.99.1-3.2 [UPGRADE] gnome-font-viewer:amd64 3.14.0-1 -> 3.14.0-2 [UPGRADE] initramfs-tools:amd64 0.119 -> 0.120 [UPGRADE] initscripts:amd64 2.88dsf-58 -> 2.88dsf-59 [UPGRADE] keyboard-configuration:amd64 1.120 -> 1.123 [UPGRADE] libapt-inst1.5:amd64 1.0.9.7 -> 1.0.9.8 [UPGRADE] libapt-pkg4.12:amd64 1.0.9.7 -> 1.0.9.8 [UPGRADE] libavahi-client-dev:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-client3:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-client3:i386 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-common-data:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-common-data:i386 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-common-dev:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-common3:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-common3:i386 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-compat-libdnssd1:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-core7:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-glib1:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-gobject0:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libavahi-ui-gtk3-0:amd64 0.6.31-4+b2 -> 0.6.31-5 [UPGRADE] libbrlapi0.6:amd64 5.2~20141018-4 -> 5.2~20141018-5 [UPGRADE] libc-bin:amd64 2.19-17 -> 2.19-18 [UPGRADE] libc-dev-bin:amd64 2.19-17 -> 2.19-18 [UPGRADE] libc6:amd64 2.19-17 -> 2.19-18 [UPGRADE] libc6:i386 2.19-17 -> 2.19-18 [UPGRADE] libc6-dev:amd64 2.19-17 -> 2.19-18 [UPGRADE] libc6-dev:i386 2.19-17 -> 2.19-18 [UPGRADE] libc6-dev-i386:amd64 2.19-17 -> 2.19-18 [UPGRADE] libc6-dev-x32:amd64 2.19-17 -> 2.19-18 [UPGRADE] libc6-i386:amd64 2.19-17 -> 2.19-18 [UPGRADE] libc6-i686:i386 2.19-17 -> 2.19-18 [UPGRADE] libc6-x32:amd64 2.19-17 -> 2.19-18 [UPGRADE] libdevmapper1.02.1:amd64 2:1.02.90-2.1 -> 2:1.02.90-2.2 [UPGRADE] libdpkg-perl:amd64 1.17.24 -> 1.17.25 [UPGRADE] libgudev-1.0-0:amd64 215-14 -> 215-17 [UPGRADE] libldap-2.4-2:amd64 2.4.40-4 -> 2.4.40+dfsg-1 [UPGRADE] libldap-2.4-2:i386 2.4.40-4 -> 2.4.40+dfsg-1 [UPGRADE] libldap2-dev:amd64 2.4.40-4 -> 2.4.40+dfsg-1 [UPGRADE] libpam-systemd:amd64 215-14 -> 215-17 [UPGRADE] libsystemd0:amd64 215-14 -> 215-17 [UPGRADE] libsystemd0:i386 215-14 -> 215-17 [UPGRADE] libtasn1-6:amd64 4.2-2 -> 4.2-3 [UPGRADE] libtasn1-6:i386 4.2-2 -> 4.2-3 [UPGRADE] libudev1:amd64 215-14 -> 215-17 [UPGRADE] libudev1:i386 215-14 -> 215-17 [UPGRADE] libupower-glib3:amd64 0.99.1-3.1 -> 0.99.1-3.2 [UPGRADE] lintian:amd64 2.5.30+deb8u3 ->
Bug#781423: marked as done (linux-image-3.16.0-4-amd64: BUG: Bad page map in process x)
Your message dated Fri, 30 Apr 2021 15:31:08 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #781423, regarding linux-image-3.16.0-4-amd64: BUG: Bad page map in process x 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.) -- 781423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt7-1 Severity: important Hello all, This is more or less a followup to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708064 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708737 only for a more recent kernel version added with a new kind of message. All of them seem to point to problems in the VM system, though. FWIW, I also get BUG: Bad rss-counter state messages, but even upstream at http://comments.gmane.org/gmane.linux.kernel/1316358 seems to have no solution for that. They provide https://lkml.org/lkml/2012/6/9/47 which comes up empty for me … -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=0a492183-24f8-4fcf-a41b-434efd825fe8 ro quiet nouveau.config=NvBios=vbios.rom ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 10.894280] b43-phy0: Broadcom 4321 WLAN found (core revision 12) [ 10.924249] b43-phy0: Found PHY: Analog 5, Type 4 (N), Revision 2 [ 10.924281] b43-phy0 warning: 5 GHz band is unsupported on this PHY [ 10.936439] Broadcom 43xx driver loaded [ Features: PMNLS ] [ 11.001450] wmi: Mapper loaded [ 11.072321] iTCO_vendor_support: vendor-support=0 [ 11.095208] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 11.095251] iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x0460) [ 11.095358] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 11.191089] b43 ssb0:0: firmware: direct-loading firmware b43/ucode11.fw [ 11.345433] b43 ssb0:0: firmware: direct-loading firmware b43/n0initvals11.fw [ 11.436026] b43 ssb0:0: firmware: direct-loading firmware b43/n0bsinitvals11.fw [ 11.560402] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 11.703635] nouveau [ DEVICE][:01:00.0] BOOT0 : 0x084700a2 [ 11.703639] nouveau [ DEVICE][:01:00.0] Chipset: G84 (NV84) [ 11.703641] nouveau [ DEVICE][:01:00.0] Family : NV50 [ 11.754997] nouveau :01:00.0: firmware: direct-loading firmware vbios.rom [ 11.755025] nouveau [ VBIOS][:01:00.0] image: vbios.rom [ 11.755070] nouveau [ VBIOS][:01:00.0] ... appears to be valid [ 11.755162] nouveau [ VBIOS][:01:00.0] BIT signature found [ 11.755165] nouveau [ VBIOS][:01:00.0] version 60.84.49.03.00 [ 11.775217] nouveau :01:00.0: irq 47 for MSI/MSI-X [ 11.775229] nouveau [ PMC][:01:00.0] MSI interrupts enabled [ 11.775264] nouveau [ PFB][:01:00.0] RAM type: GDDR3 [ 11.775266] nouveau [ PFB][:01:00.0] RAM size: 512 MiB [ 11.775268] nouveau [ PFB][:01:00.0]ZCOMP: 1892 tags [ 11.777111] nouveau [VOLT][:01:00.0] GPU voltage: 113uv [ 11.806301] nouveau [ PTHERM][:01:00.0] FAN control: none / external [ 11.806310] nouveau [ PTHERM][:01:00.0] fan management: automatic [ 11.806314] nouveau [ PTHERM][:01:00.0] internal sensor: yes [ 11.806333] nouveau [ CLK][:01:00.0] 20: core 169 MHz shader 338 MHz memory 100 MHz [ 11.806336] nouveau [ CLK][:01:00.0] 21: core 283 MHz shader 566 MHz memory 297 MHz [ 11.806339] nouveau [ CLK][:01:00.0] 22: core 375 MHz shader 750 MHz memory 502 MHz [ 11.806344] nouveau [ CLK][:01:00.0] 23: core 470 MHz shader 940 MHz memory 635 MHz [ 11.806373] nouveau [ CLK][:01:00.0] --: core 275 MHz shader 550 MHz memory 302 MHz [ 11.806526] [TTM] Zone kernel: Available graphics memory: 1019504 kiB [ 11.806528] [TTM] Initializing pool allocator [ 11.806534] [TTM] Initializing DMA pool allocator [ 11.806545] nouveau [ DRM] VRAM: 512 MiB [ 11.806547] nouveau [ DRM] GART: 1048576 MiB [ 11.806550] nouveau [ DRM] TMDS table version 2.0 [ 11.806552] nouveau [ DRM] DCB version 4.0 [ 11.806554] nouveau [ DRM] DCB outp 00: 01000123 00010034 [ 11.806556] nouveau [ DRM] DCB outp 01: 02011210 0028 [ 11.806558] nouveau [ DRM] DCB outp 02: 02011212 0030 [ 11.806560] nouveau [
Bug#781337: marked as done (xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend)
Your message dated Fri, 30 Apr 2021 15:30:52 +0200 with message-id and subject line Closing this bug has caused the Debian Bug report #781359, regarding xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend 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.) -- 781359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: important Dear Maintainer, I get on a regular basis problems resuming from suspend. (sometimes very serious needing a hard reset). The problem is the following: Instead of resuming, the system partially hangs and the screen displays black and white rectangles. Switching to the console is not always possible. If I can switch to it, I get messages repetitively flooding it: kernel: [ 2723.298937] nouveau E[ PGRAPH][:02:00.0] PGRAPH_VSTATUS0: 0x00145b4d CCACHE kernel: [ 2723.298939] nouveau E[ PGRAPH][:02:00.0] PGRAPH_VSTATUS1: 0x002d kernel: [ 2723.298941] nouveau E[ PGRAPH][:02:00.0] PGRAPH_VSTATUS2: 0x0034db40 ENG2D ROP kernel: [ 2725.298350] nouveau E[ PGRAPH][:02:00.0] PGRAPH TLB flush idle timeout fail kernel: [ 2725.298355] nouveau E[ PGRAPH][:02:00.0] PGRAPH_STATUS : 0x011fde03 BUSY DISPATCH VFETCH CCACHE_PREGEOM STRMOUT_VATTR_POSTGEOM VCLIP TRAST CLIPID ZCULL ENG2D RMASK TPC_RAST TPC_PROP ROP If I can switch to the console, I can blindly type some commands to reboot. It worked like this since I upgrade to 3.14 kernel I think. I also noticed other people suffer the same problem solved by upgrading to experimental kernel 3.19. See https://bugs.freedesktop.org/show_bug.cgi?id=89186. Apparently, the reportbug does its job very well. If you need more info, feel free to get in touch. Jean-Marc. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 19 2013 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 01:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) Xorg X server log files on system: -- -rw-r--r-- 1 root root 8851 Jun 12 2014 /var/log/Xorg.3.log -rw-r--r-- 1 root root 8851 Jun 12 2014 /var/log/Xorg.4.log -rw-r--r-- 1 root root 8851 Jun 12 2014 /var/log/Xorg.5.log -rw-r--r-- 1 root root 36984 Mar 10 17:49 /var/log/Xorg.2.log -rw-r--r-- 1 root root 36787 Mar 25 11:36 /var/log/Xorg.1.log -rw-r--r-- 1 root root 45354 Mar 27 18:46 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [20.533] X.Org X Server 1.16.4 Release Date: 2014-12-20 [20.533] X Protocol Version 11, Revision 0 [20.533] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [20.533] Current Operating System: Linux Cunegonde 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 [20.533] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=f763cefc-7dc7-47b1-b9f4-4600778e0176 ro quiet [20.533] Build Date: 11 February 2015 12:32:02AM [20.533] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [20.533] Current version of pixman: 0.32.6 [20.533]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [20.533] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [20.533] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 27 18:06:06 2015 [20.664] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [20.895] (==) No Layout section. Using the first Screen section. [20.895] (==) No screen section available. Using defaults. [20.895] (**) |-->Screen "Default Screen Section" (0) [20.895] (**) | |-->Monitor "" [20.908] (==) No monitor
Processed: bug 781337 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=90092
Processing commands for cont...@bugs.debian.org: > forwarded 781337 https://bugs.freedesktop.org/show_bug.cgi?id=90092 Bug #781337 [src:linux] xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend Bug #781359 [src:linux] linux-image-3.16.0-4-amd64: nouveau: fails to properly resume after suspend Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=90092'. Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=90092'. > thanks Stopping processing here. Please contact me if you need assistance. -- 781337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781337 781359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#850425: marked as done (linux-image-3.16.0-4-amd64: mpt3sas "swiotlb buffer is full" problem only under Xen)
Your message dated Fri, 30 Apr 2021 14:58:38 +0200 with message-id and subject line Re: Bug#850425: mpt3sas "swiotlb buffer is full" problem only under Xen has caused the Debian Bug report #850425, regarding linux-image-3.16.0-4-amd64: mpt3sas "swiotlb buffer is full" problem only under Xen 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.) -- 850425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.36-1+deb8u2 Severity: normal Dear Maintainer, This machine has an LSI SAS controller using the mpt3sas drive. When running as a Xen dom0 and hitting the drives attached to the SAS controller with significant IO (e.g.e the mdadm periodic scrub), kernel errors happen within a few seconds, sometimes to the point of panic and reboot. If not reboot then IO crawls to an unusably slow speed. As this only happens when running as a Xen dom0, I reported this to the xen-devel list: https://lists.xen.org/archives/html/xen-devel/2016-12/msg00287.html In this response: https://lists.xen.org/archives/html/xen-devel/2016-12/msg00294.html Andrew Cooper suggested trying two patches: > Can you try these two patches from the XenServer Patch queue? > https://github.com/xenserver/linux-3.x.pg/blob/master/master/series#L613-L614 > > There are bugs with some device drivers in choosing the correct DMA > mask, which cause them incorrectly to believe that they need > bounce-buffering. Once you hit bounce buffering, everything grinds > to a halt. Using a kernel built with those patches the problem has gone away for me and has been stable for about a month of production load. I tried a backports kernel and it still has the problem. I don't think this is fixed in stretch or sid either from a quick look but I may be mistaken. I don't know the timescale at which the patches Andrew Cooper linked to will make it into upstream but I thought it best to report this bug as it seems likely that others will be affected. Some logs of the problem happening are appended below. Thanks, Andy Dec 4 07:06:00 elephant kernel: [22019.373653] mpt3sas :01:00.0: swiotlb buffer is full (sz: 57344 bytes) Dec 4 07:06:00 elephant kernel: [22019.374707] mpt3sas :01:00.0: swiotlb buffer is full Dec 4 07:06:00 elephant kernel: [22019.375754] BUG: unable to handle kernel NULL pointer dereference at 0010 Dec 4 07:06:00 elephant kernel: [22019.376430] IP: [] _base_build_sg_scmd_ieee+0x1f9/0x2d0 [mpt3sas] Dec 4 07:06:00 elephant kernel: [22019.377122] PGD 0 Dec 4 07:06:00 elephant kernel: [22019.377825] Oops: [#1] SMP Dec 4 07:06:00 elephant kernel: [22019.378494] Modules linked in: binfmt_misc xen_gntdev xen_evtchn xenfs xen_privcmd nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc ipt_REJECT xt_LOG xt_limit xt_NFLOG nfnetlink_log nfnetlink xt_multiport xt_tcpudp iptable_filter ip_tables x_tables bonding joydev hid_generic usbhid hid x86_pkg_temp_thermal coretemp crc32_pclmul crc32c_intel iTCO_wdt iTCO_vendor_support evdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd pcspkr i2c_i801 ast ttm drm_kms_helper xhci_hcd ehci_pci ehci_hcd drm lpc_ich mfd_core mei_me usbcore mei usb_common igb ptp pps_core dca sg i2c_algo_bit i2c_core shpchp tpm_tis tpm button wmi ipmi_si ipmi_msghandler processor thermal_sys acpi_power_meter fuse autofs4 ext4 crc16 mbcache jbd2 dm_mod raid10 raid1 md_mod sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common ahci libahci libata mpt3sas raid_class scsi_transport_sas scsi_mod Dec 4 07:06:00 elephant kernel: [22019.384778] CPU: 0 PID: 29516 Comm: md5_resync Not tainted 3.16.0-4-amd64 #1 Debian 3.16.36-1+deb8u2 Dec 4 07:06:00 elephant kernel: [22019.385574] Hardware name: Supermicro Super Server/X10SRH-CLN4F, BIOS 2.0a 09/20/2016 Dec 4 07:06:00 elephant kernel: [22019.386400] task: 8800704ae2d0 ti: 88005c41 task.ti: 88005c41 Dec 4 07:06:00 elephant kernel: [22019.387204] RIP: e030:[] [] _base_build_sg_scmd_ieee+0x1f9/0x2d0 [mpt3sas] Dec 4 07:06:00 elephant kernel: [22019.388054] RSP: e02b:88005c413a00 EFLAGS: 00010282 Dec 4 07:06:00 elephant kernel: [22019.388855] RAX: 0010 RBX: 88006fb84070 RCX: 88006fb41be0 Dec 4 07:06:00 elephant kernel: [22019.389684] RDX: RSI: ff30 RDI: 88005c507300 Dec 4 07:06:00 elephant kernel: [22019.390572] RBP: R08: 88006f90ae80 R09: Dec 4 07:06:00 elephant kernel:
Bug#844124: marked as done (linux-vyatta-kbuild-4.9: Lintian error: wrong-path-for-interpreter)
Your message dated Fri, 30 Apr 2021 14:53:41 +0200
with message-id
and subject line Re: Bug#844124: linux-vyatta-kbuild-4.9: Lintian error:
wrong-path-for-interpreter
has caused the Debian Bug report #844124,
regarding linux-vyatta-kbuild-4.9: Lintian error: wrong-path-for-interpreter
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.)
--
844124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-vyatta-kbuild-4.9
Severity: normal
Tags: patch
Dear Maintainers,
A new script in 4.9, shipped in linux-vyatta-kbuild-4.9, uses /bin/awk
as shebang but in Debian the path is /usr/bin/awk, which triggers a
Lintian error.
Small patch to fix attached.
Thank you!
Kind regards,
Luca Boccassi
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable'), (104, 'testing'), (103, 'unstable'), (102, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
From d98b01cff054bff2e60e08411eddf6887c77838a Mon Sep 17 00:00:00 2001
From: Luca Boccassi
Date: Sat, 12 Nov 2016 17:59:44 +
Subject: [PATCH] Fix shebang of ver_linux to fix L:E
E: linux-vyatta-kbuild-4.9: wrong-path-for-interpreter
usr/lib/linux-kbuild-4.9/scripts/ver_linux (#!/bin/awk != /usr/bin/awk)
---
debian/patches/bugfix/all/ver_linux_interpreter.patch | 8
debian/patches/series | 1 +
2 files changed, 9 insertions(+)
create mode 100644 debian/patches/bugfix/all/ver_linux_interpreter.patch
diff --git a/debian/patches/bugfix/all/ver_linux_interpreter.patch
b/debian/patches/bugfix/all/ver_linux_interpreter.patch
new file mode 100644
index 000..e84561b
--- /dev/null
+++ b/debian/patches/bugfix/all/ver_linux_interpreter.patch
@@ -0,0 +1,8 @@
+--- a/scripts/ver_linux
b/scripts/ver_linux
+@@ -1,4 +1,4 @@
+-#!/bin/awk -f
++#!/usr/bin/awk -f
+ # Before running this script please ensure that your PATH is
+ # typical as you use for compilation/installation. I use
+ # /bin /sbin /usr/bin /usr/sbin /usr/local/bin, but it may
diff --git a/debian/patches/series b/debian/patches/series
index c5d0919..0278e13 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -120,3 +120,4 @@ bugfix/all/liblockdep-enable-wall-by-default.patch
bugfix/all/liblockdep-fix-unused-value-warnings.patch
bugfix/all/liblockdep-fix-set-but-not-used-warnings.patch
bugfix/all/liblockdep-fix-defined-but-not-used-warning-for-init.patch
+bugfix/all/ver_linux_interpreter.patch
--
2.1.4
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.12.2-1~exp1
Hi,
On Sat, Nov 12, 2016 at 06:38:14PM +, Luca Boccassi wrote:
> Package: linux-vyatta-kbuild-4.9
> Severity: normal
> Tags: patch
>
> Dear Maintainers,
>
> A new script in 4.9, shipped in linux-vyatta-kbuild-4.9, uses /bin/awk
> as shebang but in Debian the path is /usr/bin/awk, which triggers a
> Lintian error.
> Small patch to fix attached.
This was fixed upstream in 8af11c1cdd8f ("ver_linux: Use /usr/bin/awk
instead of /bin/awk") and included in Debian starting in
4.12.2-1~exp1.
Regards,
Salvatore--- End Message ---
Bug#987281: linux-image-amd64: Enable i915 HDCP 2.2 support
Le 2021-04-30 13:41, Salvatore Bonaccorso a écrit : > Hi Vincent, > > On Fri, Apr 30, 2021 at 12:43:22PM +0200, Vincent Blut wrote: > > Le 2021-04-30 09:12, Bastian Germann a écrit : > > > Am 29.04.21 um 20:13 schrieb Vincent Blut: > > > > Running 'xrandr --verbose' from Xorg should give you the supported > > > > HDCP Content Type. If that reports "HDCP Type1" then support for HDCP > > > > 2.2 is > > > > enabled. > > > > > > Works as expected. Enabling the two configs is sufficient. > > > > Thanks for confirming. > > > > Salvatore, how do you feel about enabling those kernel options for Bullseye? > > Should I open a MR? > > As it was verified to work and it adds important additional hardware > support, then yes please. Done. https://salsa.debian.org/kernel-team/linux/-/merge_requests/354 > I just find at this stage the part very important, we should try to > enable additional HW support only if we have some verification that it > adds value for the users, this is why I mentioned it last time. Definitely agree! > Regards, > Salvatore Cheers, Vincent signature.asc Description: PGP signature
Bug#841044: Problem with gem network card
Control: tags -1 + moreinfo On Mon, Aug 27, 2018 at 12:14:58PM +0100, Mark Cave-Ayland wrote: > On 27/08/18 10:39, Mathieu Malaterre wrote: > > > Christian, > > > > On Mon, Oct 17, 2016 at 9:32 AM Mathieu Malaterre wrote: > >> > >> Hi, > >> > >> On Fri, Oct 14, 2016 at 4:45 PM, Thadeu Lima de Souza Cascardo > >> wrote: > >>> There is certainly a way to automate this, but my question on whether > >>> that sequence would fix the problem was intended to more easily fix a > >>> real bug in the driver. > >>> > >>> I can try to help fix the driver on my free time as a volunteer. > >>> Christian, would you be willing to test patches to the driver? That > >>> would require some back and forth between us and some patience of yours, > >>> as I would be doing it on my spare time, considering I have family and > >>> other projects I would like to attend to as well. > >>> > >>> I don't have a PPC Macbook of my own, but I used to fix Linux drivers on > >>> PPC64 for a living not too long ago. > >> > >> That's a good news ! Feel free to use the bug report #841044 to send > >> your patch (and/or updates). > > > > Any update on the patch ? > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841044#30 > > FWIW QEMU now has sungem emulation which may help when trying to track > down overflow errors such as this. Is this bug still relevant/present or can the bug be closed by now? Regards, Salvatore
Bug#834113: marked as done (linux-image-3.16.0-4-amd64: Logitech camera microphone does not work / makes "chipmunk" sound)
Your message dated Fri, 30 Apr 2021 05:47:51 -0700 (PDT) with message-id <608bfc77.1c69fb81.3d4e2.3...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #834113, regarding linux-image-3.16.0-4-amd64: Logitech camera microphone does not work / makes "chipmunk" sound 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.) -- 834113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt25-2+deb8u3 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? Attempted to use google hangouts for audio call on a desktop machine with Debian 8 (KDE) * What exactly did you do (or not do) that was effective (or ineffective)? Recorded audio from Bus 003 Device 005: ID 046d:0819 Logitech, Inc. Webcam C210 was high-pitched and rendered my voice unintelligible. Copied /etc/pulse/daemon.conf, /etc/pulse/default.pa to ~/.pulse Added 'set-default-source alsa_input.usb- 046d_0819_DC70B3D0-02-U0x46d0x819.analog-mono' to ~/.pulse/default.pa to make the webcam microphone the default. Added 'default-sample-rate = 16000' to ~/.pulse/daemon.conf to fix audio issue Restarted pulseaudio with pulseaudio --kill && pulseaudio --start Restarted Crome so that it would use the restarted pulseaudio server * What was the outcome of this action? Audio sounded normal in the hangout call * What outcome did you expect instead? Recorded audio from the webcam's microphone should sound normal without the custom ~/.pulse configurations. My hunch is this kernel is affected by the same bug as this in Ubuntu (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/843431) and this in Fedora (https://bugzilla.redhat.com/show_bug.cgi?id=742010). Changing the sample rate was a workaround I found in the comments to the bug on Launchpad. I didn't try the other solution of adding 'usbcore.autosuspend=-1' to the boot parameter. I'm not sure if this should be filed against the pulseaudio or kernel package so I'm filing it here. If it should be filed there please feel free to toss this ball to the pulseaudio maintainers. If there's anything else you need from my side on this please don't hesitate to ask. Thanks for looking at this. kev. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=06286bf2-3ae4-4e0b-ab9c-81268c8a752c ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [120526.311145] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [120582.633367] [UFW BLOCK] IN=wlan0 OUT= MAC=33:33:00:00:00:01:64:70:02:8f:1a:d0:86:dd SRC=fe80::::6670:02ff:fe8f:1ad0 DST=ff02:::::::0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=130 CODE=0 [120591.235242] [UFW BLOCK] IN=wlan0 OUT= MAC=33:33:00:00:00:fb:0c:84:dc:a6:68:23:86:dd SRC=fe80::::0e84:dcff:fea6:6823 DST=ff02:::::::00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=131 CODE=0 [120651.653497] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [120707.974732] [UFW BLOCK] IN=wlan0 OUT= MAC=33:33:00:00:00:01:64:70:02:8f:1a:d0:86:dd SRC=fe80::::6670:02ff:fe8f:1ad0 DST=ff02:::::::0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=130 CODE=0 [120714.526837] [UFW BLOCK] IN=wlan0 OUT= MAC=33:33:00:00:00:fb:0c:84:dc:a6:68:23:86:dd SRC=fe80::::0e84:dcff:fea6:6823 DST=ff02:::::::00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=131 CODE=0 [120777.196603] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:64:70:02:8f:1a:d0:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 [120833.518232] [UFW BLOCK] IN=wlan0 OUT= MAC=33:33:00:00:00:01:64:70:02:8f:1a:d0:86:dd SRC=fe80::::6670:02ff:fe8f:1ad0 DST=ff02:::::::0001 LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=ICMPv6 TYPE=130 CODE=0 [120840.072354] [UFW BLOCK] IN=wlan0 OUT= MAC=33:33:00:00:00:fb:0c:84:dc:a6:68:23:86:dd
Processed: Re: Bug#841044: Problem with gem network card
Processing control commands: > tags -1 + moreinfo Bug #841044 [src:linux] gem 0001:04:0f.0 eth0: RX MAC fifo overflow smac[03810400] Added tag(s) moreinfo. -- 841044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#820622: marked as done (linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped)
Your message dated Fri, 30 Apr 2021 14:45:52 +0200 with message-id and subject line Re: Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped has caused the Debian Bug report #820622, regarding linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped 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.) -- 820622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.5-1~exp1 Severity: normal Thanks for enabling support for raspberry pi 2! It works for the most part, but floods syslog with messages: [501966.870273] net_ratelimit: 35702 callbacks suppressed [501966.875438] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped It seems to function ok, though I'm not sure if there's degraded network performance... Not sure if the version of the boot firmware and/or u-boot would likely impact this, or running stretch/sid vs. jessie. I also experience this on a second rpi2, similarly configured. live well, vagrant -- Package-specific info: ** Version: Linux version 4.5.0-trunk-armmp-lpae (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160316 (Debian 5.3.1-12) ) #1 SMP Debian 4.5-1~exp1 (2016-03-20) ** Command line: root=/dev/mapper/rpi2b-root console=ttyAMA0,115200 ** Not tainted ** Kernel log: [496926.383178] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.390069] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.397026] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.405843] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.412441] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.419085] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.425923] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.433675] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.440371] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496926.447153] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496931.412674] net_ratelimit: 6206 callbacks suppressed [496931.417762] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.093933] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.108465] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.164059] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.208265] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.226975] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.246691] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.265630] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.287754] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [496932.294860] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.490001] net_ratelimit: 285 callbacks suppressed [497554.495003] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.501775] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.510097] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.516646] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.523284] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.531653] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.538317] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.545981] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.554849] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [497554.561473] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498179.500059] net_ratelimit: 5196 callbacks suppressed [498179.505139] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498190.972627] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498192.138691] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.264114] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.270634] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.278020] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.284598] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.291305] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.298322] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.305610] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498193.312196] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped [498667.628700]
Processed: closing 813616
Processing commands for cont...@bugs.debian.org: > close 813616 3.17~rc5-1~exp1 Bug #813616 [src:linux] linux-image-3.16: namespaces: the syscall setns() is too slow Marked as fixed in versions linux/3.17~rc5-1~exp1. Bug #813616 [src:linux] linux-image-3.16: namespaces: the syscall setns() is too slow Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 813616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#796882: hyperv-daemons: include debian specific versions of hv_get* scripts
Processing control commands: > tags -1 + moreinfo Bug #796882 [src:linux] hyperv-daemons: include debian specific versions of hv_get* scripts Added tag(s) moreinfo. -- 796882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796882: hyperv-daemons: include debian specific versions of hv_get* scripts
control: tags -1 + moreinfo On Tue, Aug 25, 2015 at 02:27:46PM +0200, Christoph Martin wrote: > Package: hyperv-daemons > Version: 4.1.4-2~bpo8+1 > Severity: normal > > hv_kvp_daemon gives the following errors: > > hv_kvp_daemon[941]: sh: 1: hv_get_dns_info: not found > hv_kvp_daemon[941]: sh: 1: hv_get_dhcp_info: not found > hv_kvp_daemon[941]: sh: 1: hv_get_dns_info: not found > hv_kvp_daemon[941]: sh: 1: hv_get_dhcp_info: not found > > These scripts are missing from the package. > Debian should include there own disto specific versions of this scripts. > > Examples are in the linux-tools source in the directory tools/hv/ This should have been resolved in 4.5.1-1, when we got own init and systemd service units, is this correct? Regards, Salvatore
Bug#792929: marked as done (linux-image-3.16.0-4-amd64: Sporadic "hv_storvsc" in dmesg and FS remounted read-only, when running as an Hyper-V guest)
Your message dated Fri, 30 Apr 2021 05:28:21 -0700 (PDT) with message-id <608bf7e5.1c69fb81.736c8.3...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #792929, regarding linux-image-3.16.0-4-amd64: Sporadic "hv_storvsc" in dmesg and FS remounted read-only, when running as an Hyper-V guest 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.) -- 792929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.7-ckt11-1 Severity: normal Tags: patch upstream Dear Maintainer, * What led up to the situation? Running as an Hyper-V guest, I see sporadic messages like the ones you can see at the end of this dmesg output. This doesn't appear to be related to what happens on the machine, it may be related to the underlying storage taking backup snapshots, but I am not sure since I don't have access to it. In one occasione dmesg said: [1710593.904046] sd 2:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. [1710593.904061] end_request: I/O error, dev sda, sector 531976632 [1710593.905535] Aborting journal on device sda5-8. [1710593.912586] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [1710593.913975] EXT4-fs (sda5): Remounting filesystem read-only [1797034.976074] EXT4-fs (sda5): error count since last fsck: 2 [1797034.976116] EXT4-fs (sda5): initial error at time 1436081211: ext4_journal_check_start:56 [1797034.976133] EXT4-fs (sda5): last error at time 1436081211: ext4_journal_check_start:56 The FS was read-only, we had to reboot and manually run fsck. This appears to be the bug in the Hyper-V virtualized storage driver described in: https://social.technet.microsoft.com/Forums/windowsserver/en-US/8807f61c-565e-45bc-abc4-af09abf59de2/ubuntu-14042-lts-generation-2-scsi-errors-on-vss-based-backups That bug lead to the patch: http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=dc45708ca9988656d706940df5fd102672c5de92 * What exactly did you do (or not do) that was effective (or ineffective)? Most of this messages are harmless, when it remounted RO we rebooted. * What was the outcome of this action? fsck had to be run manually * What outcome did you expect instead? I expect the FS not to be remounted read-only. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=c52e963f-ad44-49b5-b657-65ffae35a135 ro quiet ** Not tainted ** Kernel log: [1.307341] cdrom: Uniform CD-ROM driver Revision: 3.20 [1.307713] sr 1:0:0:0: Attached scsi CD-ROM sr0 [1.310584] sd 2:0:0:0: Attached scsi generic sg0 type 0 [1.310821] sr 1:0:0:0: Attached scsi generic sg1 type 5 [1.800087] tsc: Refined TSC clocksource calibration: 1999.998 MHz [2.013645] hv_netvsc vmbus_0_13: Send section size: 6144, Section count:170 [2.013955] hv_netvsc vmbus_0_13: Device MAC 00:15:5d:00:87:1f link state up [2.273864] PM: Starting manual resume from disk [2.273873] PM: Hibernation image partition 8:1 present [2.273875] PM: Looking for hibernation image. [2.274221] PM: Image not found (code -22) [2.274224] PM: Hibernation image not present or could not be loaded. [2.453629] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [3.533926] random: nonblocking pool is initialized [ 11.807712] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. [ 15.117107] systemd-udevd[197]: starting version 215 [ 19.098448] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 19.098457] ACPI: Power Button [PWRF] [ 19.444133] input: PC Speaker as /devices/platform/pcspkr/input/input4 [ 19.779940] hv_vmbus: registering driver hyperv_fb [ 19.780832] hyperv_fb: Screen resolution: 1152x864, Color depth: 32 [ 19.785620] Console: switching to colour frame buffer device 144x54 [ 19.968763] psmouse serio1: alps: Unknown ALPS touchpad: E7=12 00 64, EC=12 00 64 [ 20.013638] piix4_smbus :00:07.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr [ 20.172074] psmouse serio1:
Processed: Re: Bug#795991: /boot/vmlinuz-3.16.0-0.bpo.4-amd64: duplicate request cache is too small for NFS 4.1 servers
Processing control commands: > tags -1 + moreinfo Bug #795991 [src:linux] linux-image-3.16.0-4-amd64: duplicate request cache is too small for NFS 4.1 servers Added tag(s) moreinfo. -- 795991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795991: /boot/vmlinuz-3.16.0-0.bpo.4-amd64: duplicate request cache is too small for NFS 4.1 servers
Control: tags -1 + moreinfo On Tue, Aug 18, 2015 at 03:30:59PM +0200, Christoph Martin wrote: > Package: src:linux > Version: 3.16.7-ckt11-1+deb8u3~bpo70+1 > Severity: normal > File: /boot/vmlinuz-3.16.0-0.bpo.4-amd64 > > The drc (duplicate request cache) for NFS 4.1 in the vanilla kernel > has a fixed size only depending on the RAM of the machine. > > For example, when setting up a vm which should only serve as a > nfs referral server with 768 MB RAM it could only server about > 20 clients. So it is roughly 32 clients per GB. > > The problem is, that in nfssvc.c the size of drc is calculated with > a shift of NFSD_DRC_SIZE_SHIFT bits from the RAM size. > > I attach a patch for this which I also sent to linux-nfs. > (See http://www.spinics.net/lists/linux-nfs/msg51791.html) > > It implements a module variable to set the size on module load. > > It hope that such a patch can make it into Debian soon. is this problem still relevant? Side note that we would anyway not apply a patch which would not have been accepted upstream, likely unless there are very valid reasons. Regards, Salvatore
Bug#774896: Exynos4 CONFIG_HZ
Hi,
On Mon, Jan 19, 2015 at 11:23:04AM +0100, Krzysztof Kozłowski wrote:
> 2015-01-18 17:57 GMT+01:00 Sten Spans :
> >
> > With the improvements in upstream support for exynos4 devices
> > I've been looking into adding support odroid devices to Debian's
> > armmp kernel. The kernel config changes needed are quite minimal
> > as can be seen here:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774896
> >
> > Mostly enabling support and various modules.
> >
> > However as Ian Campbell notes, enabling ARCH_EXYNOS4 triggers
> > the following from arch/arm/Kconfig:
> > config HZ_FIXED
> > int
> > default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \
> > ARCH_S5PV210 || ARCH_EXYNOS4
> > default AT91_TIMER_HZ if ARCH_AT91
> > default SHMOBILE_TIMER_HZ if ARCH_SHMOBILE_LEGACY
> > default 0
> >
> > This forces CONFIG_HZ=200 for the entire armmp kernel, which is
> > undesirable. The reason for this setting isn't very clear to either
> > me or Ian. I personally have verified that HZ=250 (the default for debian
> > armmp kernels) boots fine.
> >
> > Is there a particular reason for this setting?
> > Would a patch removing this requirement for ARCH_EXYNOS4 be accepted?
>
> +Cc Kukjin Kim
>
> I cannot find a valid reason for fixed 200 Hz, especially that other
> values (<100, 1000>) are working. Maybe Kukjin will share some light
> on this?
I'm not sure if this bugreport is still relevant, but in any case
upstream changed this in da6b21e97e39 ("ARM: Drop fixed 200 Hz timer
requirement from Samsung platforms").
In case the bugreport is not anymore relevant, let's close it.
Regards,
Salvatore
Bug#711108: marked as done (linux-image-* should suggest linux-perf-*)
Your message dated Fri, 30 Apr 2021 14:18:09 +0200
with message-id
and subject line Re: Bug#711108: linux-image-* should suggest linux-tools-*
has caused the Debian Bug report #711108,
regarding linux-image-* should suggest linux-perf-*
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.)
--
711108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: wishlist
Please consider having the linux-image-${version}-* packages suggesting
the matching linux-tools-${version} package. This would help users to keep
them in sync.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Hi,
On Tue, Jun 04, 2013 at 08:46:50PM +0200, Piotr Engelking wrote:
> Source: linux
> Severity: wishlist
>
> Please consider having the linux-image-${version}-* packages suggesting
> the matching linux-tools-${version} package. This would help users to keep
> them in sync.
I'm closing this bug now as I think it's not anymore relevant in this
outlined form. But please let me know if you disagree.
Regards,
Salvatore--- End Message ---
Bug#987281: linux-image-amd64: Enable i915 HDCP 2.2 support
Hi Vincent, On Fri, Apr 30, 2021 at 12:43:22PM +0200, Vincent Blut wrote: > Le 2021-04-30 09:12, Bastian Germann a écrit : > > Am 29.04.21 um 20:13 schrieb Vincent Blut: > > > Running 'xrandr --verbose' from Xorg should give you the supported > > > HDCP Content Type. If that reports "HDCP Type1" then support for HDCP 2.2 > > > is > > > enabled. > > > > Works as expected. Enabling the two configs is sufficient. > > Thanks for confirming. > > Salvatore, how do you feel about enabling those kernel options for Bullseye? > Should I open a MR? As it was verified to work and it adds important additional hardware support, then yes please. I just find at this stage the part very important, we should try to enable additional HW support only if we have some verification that it adds value for the users, this is why I mentioned it last time. Regards, Salvatore
Bug#987281: linux-image-amd64: Enable i915 HDCP 2.2 support
Le 2021-04-30 09:12, Bastian Germann a écrit : > Am 29.04.21 um 20:13 schrieb Vincent Blut: > > Running 'xrandr --verbose' from Xorg should give you the supported > > HDCP Content Type. If that reports "HDCP Type1" then support for HDCP 2.2 is > > enabled. > > Works as expected. Enabling the two configs is sufficient. Thanks for confirming. Salvatore, how do you feel about enabling those kernel options for Bullseye? Should I open a MR? signature.asc Description: PGP signature
Bug#987815: MPTCP is not enabled
Source: linux Version: 5.10.28-1 Severity: wishlist The current configuration does not enable the multipath TCP functionality provided by the kernel through the MPTCP (and the the-default MPTCP_IPV6) binary options. These have been available since kernel version 5.6. When enabled, user space applications can opt in to MPTCP behavior by using the new IPPROTO_MPTCP; regular TCP connections are unaffected. Applications using this are starting slowly (outside of the Apple ecosystem where this has been in used for years to ensure smooth network handovers), but having this available widely would make it easier for application developers to verify MPTCP operation on systems where they can't easily (or don't have the experience to) rebuild their kernel with CONFIG_MPTCP=y. Please consider enabling this feature. -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.12.0-rc5 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom signature.asc Description: PGP signature
Bug#987281: linux-image-amd64: Enable i915 HDCP 2.2 support
Am 29.04.21 um 20:13 schrieb Vincent Blut: Running 'xrandr --verbose' from Xorg should give you the supported HDCP Content Type. If that reports "HDCP Type1" then support for HDCP 2.2 is enabled. Works as expected. Enabling the two configs is sufficient.
