linux_4.19.37-6_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 00:23:17 +0200 Source: linux Architecture: source Version: 4.19.37-6 Distribution: unstable Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 930554 930904 Changes: linux (4.19.37-6) unstable; urgency=high . [ John Paul Adrian Glaubitz ] * [sh4]: Check for kprobe trap number before trying to handle a kprobe trap . [ Salvatore Bonaccorso ] * tcp: refine memory limit test in tcp_fragment() (Closes: #930904) * ptrace: Fix ->ptracer_cred handling for PTRACE_TRACEME (CVE-2019-13272) . [ Steve McIntyre ] * [arm64] Improve support for the Huawei TaiShan server platform (Closes: #930554): - Enable the HNS/ROCE Infiniband driver - Backport fixes from 4.20 and 4.21 for HNS3 networking, hisi_sas SAS and HNS/ROCE Infiniband - Add module:drivers/scsi/hisi_sas/* to the ABI ignore list . [ Cyril Brulebois ] * [arm] Backport DTB support for Rasperry Pi Compute Module 3. * [arm64] Backport DTB support for Rasperry Pi Compute Module 3. Checksums-Sha1: de42ca6566e1b5f9ee746553e3a5bdd102caa77a 189279 linux_4.19.37-6.dsc 4dbb491c8724f30a0e5f5d70ea0732987f3c91ba 4279752 linux_4.19.37-6.debian.tar.xz d580b78aaed3b4ef58ad01d53d4f2516fb8e02da 47670 linux_4.19.37-6_source.buildinfo Checksums-Sha256: a3123c85cf397618c3f52dd410f3215566c957abd88a2d13d3df6748bb6dfda5 189279 linux_4.19.37-6.dsc bc699c4ccd4c6fbd69f55bca4335fa011003ffd1deda9cdd1ec6c3f3a5df116e 4279752 linux_4.19.37-6.debian.tar.xz 9f369e04f8987b675e1e3c441ce303c1c08ef6deab2f891b06cc794f423b9252 47670 linux_4.19.37-6_source.buildinfo Files: a0073ef04455b211ec8d72b67c485914 189279 kernel optional linux_4.19.37-6.dsc 87f55467335fddf729b594a56e1ad9fc 4279752 kernel optional linux_4.19.37-6.debian.tar.xz c4cc4c3968d2227c56323bdd2522c1a8 47670 kernel optional linux_4.19.37-6_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl0xRzVfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EWYIQAJ7eKSJOmXFABFldzvKh1hivYHV5sYkp eixEg5+c6VNSS24FlI//MDRC6Z+DCZqZ2K2lFKtTZA1IDj+LviPj6gDTcdGcXrfB G1NykU3ImuC7OTKwEppYAPkkrZEbN1qLuA/DRP97lAKMw8kjTtv3OpGy6Ovn7GPj S11JaSgocneGo9Dgb5ap4EjGn17WBZGVQ8rpBZwD1E3os3D2494Jr9zM6qDmNiTV kXIaGnjFzHLGP7ZYiDMbG/jhqqZiIT0gI5M997eQyefGOYcrw9d9lQhghbWvGpwN Fb89wwdZ5ntt/t9lYEQ/yxyX3K8vXiWp61p2QbdYivcG6os/jM4lRD2VyNCOPAxD ZYQGpt+RM3zPy3q0XRjteZleeZnQEGqSZfnyu/ZoIgD7/GZWgitQ5hV9h+vhTF0n vwYXwWeA3Tod+CNRsBFFeh686ldA2n61xYEwn0Tljjhl/E+O2stJVEbeCvoYMU0o iP2dgJHUH9s6+frvBIvAu+sG2VXeD/d078xp4Z5ToJplvWxR5KwAZkvQWA6UDrPH 9Dv2u0EciG8YqQT5YxJIvqpDHEhQ6hixZR7zBgH4N5HGVbFxrUfYxJez9xawAE2j 74buR0EVZ0tH+4KB1WlXvRCkKjkfb1Nm/Iq+p4U9B85tuTR56v13xH8uAu35mDPi cJxIq7Q7rjCU =b/nj -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#930554: marked as done (Please add support for Huawei's TaiShan server platform)
Your message dated Fri, 19 Jul 2019 04:55:49 + with message-id and subject line Bug#930554: fixed in linux 4.19.37-6 has caused the Debian Bug report #930554, regarding Please add support for Huawei's TaiShan server platform 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.) -- 930554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.19.28-2 Severity: important Hi folks, The TaiShan is an arm64 server made by Huawei, using the HiSilicon 1620 CPU. It's a nice big beast of a machine, with lots of cores, memory etc. We've been loaned one to use (maybe as a buildd?), but at the moment the Buster kernel doesn't support it out of the box. I'm partway through a set of patches to enable it, turning on some device drivers and backporting a few fixes. Patch coming very soon. It would be very helpful to have this in our Buster release. Cheers, Steve -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.37-6 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 00:23:17 +0200 Source: linux Architecture: source Version: 4.19.37-6 Distribution: unstable Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 930554 930904 Changes: linux (4.19.37-6) unstable; urgency=high . [ John Paul Adrian Glaubitz ] * [sh4]: Check for kprobe trap number before trying to handle a kprobe trap . [ Salvatore Bonaccorso ] * tcp: refine memory limit test in tcp_fragment() (Closes: #930904) * ptrace: Fix ->ptracer_cred handling for PTRACE_TRACEME (CVE-2019-13272) . [ Steve McIntyre ] * [arm64] Improve support for the Huawei TaiShan server platform (Closes: #930554): - Enable the HNS/ROCE Infiniband driver - Backport fixes from 4.20 and 4.21 for HNS3 networking, hisi_sas SAS and HNS/ROCE Infiniband - Add module:drivers/scsi/hisi_sas/* to the ABI ignore list . [ Cyril Brulebois ] * [arm] Backport DTB support for Rasperry Pi Compute Module 3. * [arm64] Backport DTB support for Rasperry Pi Compute Module 3. Checksums-Sha1: de42ca6566e1b5f9ee746553e3a5bdd102caa77a 189279 linux_4.19.37-6.dsc 4dbb491c8724f30a0e5f5d70ea0732987f3c91ba 4279752 linux_4.19.37-6.debian.tar.xz d580b78aaed3b4ef58ad01d53d4f2516fb8e02da 47670 linux_4.19.37-6_source.buildinfo Checksums-Sha256: a3123c85cf397618c3f52dd410f3215566c957abd88a2d13d3df6748bb6dfda5 189279 linux_4.19.37-6.dsc bc699c4ccd4c6fbd69f55bca4335fa011003ffd1deda9cdd1ec6c3f3a5df116e 4279752 linux_4.19.37-6.debian.tar.xz 9f369e04f8987b675e1e3c441ce303c1c08ef6deab2f891b06cc794f423b9252 47670 linux_4.19.37-6_source.buildinfo Files: a0073ef04455b211ec8d72b67c485914 189279 kernel optional linux_4.19.37-6.dsc 87f55467335fddf729b594a56e1ad9fc 4279752 kernel optional linux_4.19.37-6.debian.tar.xz c4cc4c3968d2227c56323bdd2522c1a8 47670 kernel optional linux_4.19.37-6_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl0xRzVfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EWYIQAJ7eKSJOmXFABFldzvKh1hivYHV5sYkp eixEg5+c6VNSS24FlI//MDRC6Z+DCZqZ2K2lFKtTZA1IDj+LviPj6gDTcdGcXrfB G1NykU3ImuC7OTKwEppYAPkkrZEbN1qLuA/DRP97lAKMw8kjTtv3OpGy6Ovn7GPj S11JaSgocneGo9Dgb5ap4EjGn17WBZGVQ8rpBZwD1E3os3D2494Jr9zM6qDmNiTV
Bug#930904: marked as done (linux-image-4.19.0-5-amd64: Latest kernel upgrades on unstable break Steam (link to fix included))
Your message dated Fri, 19 Jul 2019 04:55:49 + with message-id and subject line Bug#930904: fixed in linux 4.19.37-6 has caused the Debian Bug report #930904, regarding linux-image-4.19.0-5-amd64: Latest kernel upgrades on unstable break Steam (link to fix included) 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.) -- 930904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.37-5 Severity: important Dear Maintainer, Latest security fixes in the kernel (from 4.19.37-4 onwards) break some apps like at least Steam. The fix already exists as mentioned there : https://www.phoronix.com/scan.php?page=news_item=Steam-Linux-Network-One-Line A workaround exists for Steam but it may not be the case for other apps. Could you please backport the fix and re-release the kernel ? Thanks and regards -- Package-specific info: ** Version: Linux version 4.19.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-5 (2019-06-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=b762a3a5-b58c-46e5-9fbd-15927e33bdf9 ro apparmor=1 security=apparmor quiet ** Tainted: POE (12289) * Proprietary module has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [24717.439314] cache: parent cpu1 should not be sleeping [24717.439513] CPU1 is up [24717.439534] smpboot: Booting Node 0 Processor 2 APIC 0x4 [24717.441249] cache: parent cpu2 should not be sleeping [24717.441460] CPU2 is up [24717.441479] smpboot: Booting Node 0 Processor 3 APIC 0x6 [24717.443255] cache: parent cpu3 should not be sleeping [24717.443486] CPU3 is up [24717.443505] smpboot: Booting Node 0 Processor 4 APIC 0x1 [24717.443993] cache: parent cpu4 should not be sleeping [24717.444307] CPU4 is up [24717.444326] smpboot: Booting Node 0 Processor 5 APIC 0x3 [24717.444743] cache: parent cpu5 should not be sleeping [24717.444944] CPU5 is up [24717.444960] smpboot: Booting Node 0 Processor 6 APIC 0x5 [24717.445376] cache: parent cpu6 should not be sleeping [24717.445594] CPU6 is up [24717.445609] smpboot: Booting Node 0 Processor 7 APIC 0x7 [24717.446037] cache: parent cpu7 should not be sleeping [24717.446817] CPU7 is up [24717.471699] ACPI: Waking up from system sleep state S3 [24717.472540] ACPI: EC: interrupt unblocked [24717.510729] ACPI: EC: event unblocked [24717.511197] sd 0:0:0:0: [sda] Starting disk [24717.511202] sd 1:0:0:0: [sdb] Starting disk [24717.511204] sd 2:0:0:0: [sdc] Starting disk [24717.511208] sd 4:0:0:0: [sdd] Starting disk [24717.512015] serial 00:06: activated [24717.638422] nvme nvme0: Shutdown timeout set to 8 seconds [24717.801991] usb 2-14: reset high-speed USB device number 11 using xhci_hcd [24717.888248] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [24717.888263] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [24717.888306] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [24717.889184] ata1.00: supports DRM functions and may not be fully accessible [24717.889484] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) [24717.889487] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) [24717.889942] ata1.00: supports DRM functions and may not be fully accessible [24717.890490] ata1.00: configured for UDMA/133 [24717.905182] ata4.00: configured for UDMA/100 [24717.929649] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) [24717.929652] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) [24717.929657] ata6.00: configured for UDMA/100 [24718.434026] usb 2-14.1: reset low-speed USB device number 12 using xhci_hcd [24718.990103] usb 2-14.2: reset low-speed USB device number 13 using xhci_hcd [24719.546162] usb 2-14.3: reset low-speed USB device number 14 using xhci_hcd [24719.847479] OOM killer enabled. [24719.847481] Restarting tasks ... [24719.847718] pci_bus :04: Allocating resources [24719.847749] pci :03:00.0: PCI bridge to [bus 04] [24719.847757] pci :03:00.0: bridge window [io 0x2000-0x2fff] [24719.847770] pci :03:00.0: bridge window [mem 0xd200-0xd21f] [24719.847779] pci :03:00.0: bridge window [mem 0xd220-0xd23f 64bit pref] [24719.870016] done. [24719.875143] PM: suspend exit [24720.535943] e1000e: eth0 NIC Link is Up 1000
Processing of linux_4.19.37-6_source.changes
linux_4.19.37-6_source.changes uploaded successfully to localhost along with the files: linux_4.19.37-6.dsc linux_4.19.37-6.debian.tar.xz linux_4.19.37-6_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing
On Thu, 2019-07-18 at 21:36 +0100, Terry wrote: > Package: src:linux > Version: 4.19.37-5 > Severity: important > > Dear Maintainer, > > I performed an upgrade from stretch to buster today and the kernel > paniced with a not syncing error. > > I've attempted to switch of acpi but adding the options acpi=off > pci=noacpi to the boot line but this didn't have any effect. [...] Disabling use of ACPI on any PC made in the last 15 years is likely to make things worse, anyway. Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson signature.asc Description: This is a digitally signed message part
Processed: reassign 932368 to src:nvidia-graphics-drivers
Processing commands for cont...@bugs.debian.org: > reassign 932368 src:nvidia-graphics-drivers Bug #932368 [src:linux] linux-image-4.19.0-5-amd64: Blank a screen with setterm (setterm -blank force) is not possible anymore. Bug reassigned from package 'src:linux' to 'src:nvidia-graphics-drivers'. No longer marked as found in versions linux/4.19.37-5. Ignoring request to alter fixed versions of bug #932368 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 932368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 932408
Processing commands for cont...@bugs.debian.org: > tags 932408 + moreinfo Bug #932408 [src:linux] linux-image-4.19.0-5-amd64: kernel panic not syncing Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 932408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing
Package: src:linux Version: 4.19.37-5 Severity: important Dear Maintainer, I performed an upgrade from stretch to buster today and the kernel paniced with a not syncing error. I've attempted to switch of acpi but adding the options acpi=off pci=noacpi to the boot line but this didn't have any effect. The details below are from the same machine booted with the 4.9 kernel. I'll send images of the panic shortly. Kind regards, Terry. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP Compaq dc5800 Microtower product_version: chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: Hewlett-Packard bios_version: 786F2 v01.04 board_vendor: Hewlett-Packard board_name: 2820h board_version: ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82Q33 Express DRAM Controller [8086:29d0] (rev 02) Subsystem: Hewlett-Packard Company 82Q33 Express DRAM Controller [103c:281e] 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 PCI bridge [0604]: Intel Corporation 82Q33 Express PCI Express Root Port [8086:29d1] (rev 02) (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: [88] Subsystem: Hewlett-Packard Company 82Q33 Express PCI Express Root Port [103c:281e] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 41d1 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Kernel driver in use: pcieport Kernel modules: shpchp 00:03.0 Communication controller [0780]: Intel Corporation 82Q33 Express MEI Controller [8086:29d4] (rev 02) Subsystem: Hewlett-Packard Company 82Q33 Express MEI Controller [103c:281e] 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- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr-
[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #931330 (http://bugs.debian.org/931330) # Bug title: BUG: unable to handle kernel NULL pointer dereference at 0337 # * http://bugzilla.kernel.org/show_bug.cgi?id=203681 # * remote status changed: (?) -> NEW usertags 931330 + status-NEW thanks
Bug#686658: marked as done (nfs-kernel-server: NFS Thread usage (th))
Your message dated Thu, 18 Jul 2019 21:15:27 +0200 with message-id <23856.50511.278325.41...@informatik.uni-koeln.de> and subject line closing has caused the Debian Bug report #686658, regarding nfs-kernel-server: NFS Thread usage (th) 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.) -- 686658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.2-4squeeze2 Severity: normal Hi, NFS returns no information about process usage : "th" line in /proc/net/rpc/nfsd #cat /proc/net/rpc/nfsd rc 28 9722890 107643167 fh 144 0 0 0 0 io 3209523210 1191239098 th 32 0 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ra 64 4405519 0 0 0 0 0 0 0 0 0 4916247 net 117394796 2782 117394713 798 rpc 117380153 0 0 0 0 proc2 18 1390 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 proc3 22 1462 30358468 3601124 29210737 36446167 116121 9321183 5025391 322758 9871 39 0 340883 12647 410159 0 1219 923573 862000 84 35 381470 proc4 2 0 0 proc4ops 59 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Thanks, -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 Versions of packages nfs-kernel-server depends on: ii libblkid1 2.17.2-9 block device id library ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libgssapi-krb5-21.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4mechanism-switch gssapi library ii libk5crypto31.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libnfsidmap20.23-2 An nfs idmapping library ii librpcsecgss3 0.19-2 allows secure rpc communication us ii libwrap07.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii nfs-common 1:1.2.2-4squeeze2NFS support files common to client ii ucf 3.0025+nmu1 Update Configuration File: preserv nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- There's a replacement for the usage of the nfs daemons. -- regards Thomas--- End Message ---
Re: Bug#932199: insserv: warning: could not find all dependencies for $portmap
On Thu, 18 Jul 2019, Dmitry Bogatov wrote: > On my system, $x-display-manager is defined in /etc/insserv.conf.d/xdm; > on headless box there is no display manager, hence warning. Situation > with $portmap seems similar. Indeed, I also ran into the $x-display-manager one after having reported the $portmap one. > This warning was introduced in upstream [ddd9d38] with following > changelog: > > - When an initscript contains a "$service" dependency which cannot be > resolved (ie $service does not expand or does not exist) insserv > will display a warning. The initscript is still added. > > Seems problem is that warning emitted not only for hard, but only for > soft dependencies. Patch at bottom. > > Please check whether is solves all problems. I’d assume so but since it was only a warning I can now reboot without fear ☻ > > /etc/init.d/mountnfs.sh is from initscripts (= 2.93-8). Perhaps it > > ought to be moved to nfs-common or so? That being said, nfs-common > > does not Depends on portmap either… That being said, it Depends on rpcbind which Provides portmap nowadays, so I’d guess that will be it. > Sounds reasonable. Created bug. OK, thanks! bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg ** Mit der tarent Academy bieten wir auch Trainings und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an. Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt. **
Processed: severity of 874364 is normal
Processing commands for cont...@bugs.debian.org: > severity 874364 normal Bug #874364 [gnome-control-center,systemd,initramfs-tools] Keyboard layout set in GNOME or with localectl does not apply to initramfs LUKS prompt immediately Severity set to 'normal' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 874364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932250: [Fwd: Re: Bug#932250: linux-image-amd64: random segfaults without taking something down]
Forwarded Message From: a a To: Ben Hutchings Subject: Re: Bug#932250: linux-image-amd64: random segfaults without taking something down Date: Thu, 18 Jul 2019 13:09:53 +0200 Message-Id: It shouldnt be overheating, because i have custom setting on cpu heatsink fan and the ram module has a own heatsink. Plus i have fan on case which puls out the excees heat. The segfaults happend at low load, maybe it wasnt above P2 power state. Also i have made sure that the cpu doenst exceed 90°C. Out of tree modules are from virtual box. After disabling overcommit and apparmor i didnt experience a segfault for now. The segfaults started to dissapeer it seams. I fear that this might be a bug tied to certain order of instructions. For example if i enable debug it may change order of instruction and the bug doesnt occur. Reason that i reported this bug with package linux-image-amd64 is that i didnt know about the existence of linux-mage-4.19.0-5-amd64 and i tried to prevent creating bug file for nonexisting package. Should i file another bug and put a link to this report ? št 18. 7. 2019 o 4:04 Ben Hutchings napísal(a): > Control: tag -1 moreinfo > > On Wed, 2019-07-17 at 01:27 +0200, m.alfa...@gmail.com wrote: > > Package: linux-image-amd64 > > Version: 4.19+105 > > Severity: important > > > > Hi. > > > > Im currently running debian buster kernel and i experienced some > segfaults. > > Segfaults are random, which prevents me from pinpointing the trigger. > > First i tried disabling overcommit on memory, the behavior stoped. > > Today it started during installing updates for libreoffice. Two first > > segfaults were caused by xfdesktop, the two more with gmain. > > Another odd thing is that the error is in libglib and the code is > completly > > identical. The RAM was tested with memtest86+, memtester. Previous > release > > with backport kernel was working perfectly even with overcommit. I > > guess there is a small chance of defective hw. > > Could it be overheating? > > > My next suspect is apparmor. Im going to use the system with disabled > > apparmor to see if this problem persist. > > What about the out-of-tree module you are using? Can you run without > that? > > > Thank you > > > > I hope this helps make debian more stable and reliable. > [...] > > Well, it isn't as helpful as it could be, because you chose to ignore > the request to report a bug against linux-image-4.19.0-5-amd64. > > Ben. > > -- > Ben Hutchings > Any sufficiently advanced bug is indistinguishable from a feature. > > > -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature.
Bug#932250: Fwd: Bug#932250: linux-image-amd64: random segfaults without taking something down
It shouldnt be overheating, because i have custom setting on cpu heatsink fan and the ram module has a own heatsink. Plus i have fan on case which puls out the excees heat. The segfaults happend at low load, maybe it wasnt above P2 power state. Also i have made sure that the cpu doenst exceed 90°C. Out of tree modules are from virtual box. After disabling overcommit and apparmor i didnt experience a segfault for now. The segfaults started to dissapeer it seams. I fear that this might be a bug tied to certain order of instructions. For example if i enable debug it may change order of instruction and the bug doesnt occur. Reason that i reported this bug with package linux-image-amd64 is that i didnt know about the existence of linux-mage-4.19.0-5-amd64 and i tried to prevent creating bug file for nonexisting package. Should i file another bug and put a link to this report ? št 18. 7. 2019 o 4:04 Ben Hutchings napísal(a): > Control: tag -1 moreinfo > > On Wed, 2019-07-17 at 01:27 +0200, m.alfa...@gmail.com wrote: > > Package: linux-image-amd64 > > Version: 4.19+105 > > Severity: important > > > > Hi. > > > > Im currently running debian buster kernel and i experienced some > segfaults. > > Segfaults are random, which prevents me from pinpointing the trigger. > > First i tried disabling overcommit on memory, the behavior stoped. > > Today it started during installing updates for libreoffice. Two first > > segfaults were caused by xfdesktop, the two more with gmain. > > Another odd thing is that the error is in libglib and the code is > completly > > identical. The RAM was tested with memtest86+, memtester. Previous > release > > with backport kernel was working perfectly even with overcommit. I > > guess there is a small chance of defective hw. > > Could it be overheating? > > > My next suspect is apparmor. Im going to use the system with disabled > > apparmor to see if this problem persist. > > What about the out-of-tree module you are using? Can you run without > that? > > > Thank you > > > > I hope this helps make debian more stable and reliable. > [...] > > Well, it isn't as helpful as it could be, because you chose to ignore > the request to report a bug against linux-image-4.19.0-5-amd64. > > Ben. > > -- > Ben Hutchings > Any sufficiently advanced bug is indistinguishable from a feature. > > >
Bug#931574: nftables: kernel BUG at lib/list_debug.c:53
Am 17.07.19 um 19:32 schrieb Vincent Tondellier:
>> It looks like (one of) the two `flow table` lines are at fault,
>> but I am not able to confirm this for sure, because the assertion
>> is not 100% reliably triggered.
>
> I can reproduce your crash quite reliably, maybe because I have kernel
> hardening enabled (page_poison=1 slab_nomerge).
>
> Can you try removing the anonymous sets from your configuration ?
> Replacing "tcp dport { 22 }" with "tcp dport 22" in your example seems
> to resolve the crash.
> Unfortunatly, doing the same in my config is almost a full rewrite ...
The configuration in my bug report was already heavily shortened to the
point where I still could reliably reproduce the issue. Nonetheless it
was simple enough to make the change to remove all the anonymous
one-element sets from the configuration.
I can *confirm* that replacing the anonymous one-element sets by their
single element fixes the issue.
Replacing the multi-element sets was not necessary for me. I'll still
wait for an / the kernel update, because I still don't really trust it
to reliably work 100% of the time.
Best regards
Tim Düsterhus
Bug#932304: do_IRQ: 0.37 No irq handler for vector
On Wed, Jul 17, 2019 at 10:51 PM Miguel A. Vallejo wrote: > But for me this problem is triggered by the Arduino IDE. Interesting. The system bell only starts when I open my xfce session. I'll continue digging in the audio direction. Thanks
