[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
I did found a workaround, but iam still convinced that we have a kind of bug. I think i should explain our typical systemsetup, for better understandig. Typical field of application are failoversystems. overall we use very few software and systems have minimal load. we have 2 servers in a cluster realised with pacemaker/corosync. they manage a reource haproxy and a floating ip. We do this with different ubuntu OS, from 18.04 over 20.04 to 22.04 Our systems are bound to Windows Active Director with SSSD (System Security Services Daemon) (https://schroeffu.ch/2019/09/linux-active- directory-ldap-ssh-login-mit-sssd-und-realmd/) so it is possible to Login with our AD Credentials. last component is altiris server management suite agent (former symantec now broadcom) wich is running with root privileges and helps to manage our computerlandscape. And this is where i located the problem. every evening the agent runs a bash script which was wrote by me 3 years ago. it is a small script with 90 lines, it collects some data, mounts a windows fileshare and finally uploads some small files before unmounting the share. nothing special, it takes around 5 seconds to complete, but here seems to be the problem. As i can see every affected server shows in syslog this lines about kernel bug i uploaded on 2023-09-11 (#4) . In some cases there happens something unexpected and triggers this bug. this happens since 5.15.0-83-generic the system gets unstable, high load without running processes, every command takes forever to complete. mostly we had to do a vmware hardstop, because even "reboot -f" failed. i uploaded already some logs. I deactivated this job and the problems disappeared. i was not able to trigger this problem by manual run of the script. as the job was active, every morning we had a bunch of servers in this state between life and death. So i can not confirm a change on our site, i still think about a newly introduced kind of bug. I would like to hear from you, please tell me your opinion to this case. strange that i report a bug with documented kernel error and no one gets back to me. Thanks, Hajo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
lspci -vvnn 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01) Subsystem: VMware Virtual Machine Chipset [15ad:1976] 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- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08) Subsystem: VMware Virtual Machine Chipset [15ad:1976] 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- TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx 00:10.0 SCSI storage controller [0100]: Broadcom / LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01) Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976] 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- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Subsystem: VMware PCI bridge [15ad:0790] 00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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: [40] Subsystem: VMware PCI Express Root Port [15ad:07a0] Capabilities: [48] 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: [50] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x32, ASPM L0s, Exit Latency L0s <64ns ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s (ok), Width x32 (ok) TrErr- Train- SlotClk- DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn+ PwrCtrl+ MRL- AttnInd- PwrInd- HotPlug+ Surprise- Slot #160, PowerLimit 240.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn+ PwrFlt- MRL- PresDet- CmdCplt- HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd- AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
uname Linux myhost 5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
/proc/version_signature Ubuntu 5.15.0-83.92-generic 5.15.116 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
dmesg [0.00] Linux version 5.15.0-83-generic (buildd@lcy02-amd64-027) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 (Ubuntu 5.15.0-83.92-generic 5.15.116) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic root=UUID=16488428-7c39-44f3-b82c-95b445a58fea ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] Disabled fast string operations [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009f3ff] usable [0.00] BIOS-e820: [mem 0x0009f400-0x0009] reserved [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xbfed] usable [0.00] BIOS-e820: [mem 0xbfee-0xbfefefff] ACPI data [0.00] BIOS-e820: [mem 0xbfeff000-0xbfef] ACPI NVS [0.00] BIOS-e820: [mem 0xbff0-0xbfff] usable [0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec0] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xfffe-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00043fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 [0.00] vmware: hypercall mode: 0x02 [0.00] Hypervisor detected: VMware [0.00] vmware: TSC freq read from hypervisor : 2099.999 MHz [0.00] vmware: Host bus clock speed read from hypervisor : 6600 Hz [0.00] vmware: using clock offset of 6397541515 ns [0.16] tsc: Detected 2099.999 MHz processor [0.002306] e820: update [mem 0x-0x0fff] usable ==> reserved [0.002313] e820: remove [mem 0x000a-0x000f] usable [0.002324] last_pfn = 0x44 max_arch_pfn = 0x4 [0.002374] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.002397] total RAM covered: 31744M [0.002629] Found optimal setting for mtrr clean up [0.002631] gran_size: 64K chunk_size: 64K num_reg: 5 lose cover RAM: 0G [0.002709] e820: update [mem 0xc000-0x] usable ==> reserved [0.002720] last_pfn = 0xc max_arch_pfn = 0x4 [0.008571] found SMP MP-table at [mem 0x000f6a70-0x000f6a7f] [0.008609] Using GB pages for direct mapping [0.008902] RAMDISK: [mem 0x2aee3000-0x31768fff] [0.008911] ACPI: Early table checksum verification disabled [0.008915] ACPI: RSDP 0x000F6A00 24 (v02 PTLTD ) [0.008921] ACPI: XSDT 0xBFEEE8FB 5C (v01 INTEL 440BX 0604 VMW 01324272) [0.008929] ACPI: FACP 0xBFEFEE73 F4 (v04 INTEL 440BX 0604 PTL 000F4240) [0.008935] ACPI: DSDT 0xBFEEEBBD 0102B6 (v01 PTLTD Custom 0604 MSFT 0301) [0.008939] ACPI: FACS 0xBFEFFFC0 40 [0.008943] ACPI: FACS 0xBFEFFFC0 40 [0.008946] ACPI: BOOT 0xBFEEEB95 28 (v01 PTLTD $SBFTBL$ 0604 LTP 0001) [0.008950] ACPI: APIC 0xBFEEEB1B 7A (v01 PTLTD ? APIC 0604 LTP ) [0.008954] ACPI: MCFG 0xBFEEEADF 3C (v01 PTLTD $PCITBL$ 0604 LTP 0001) [0.008958] ACPI: SRAT 0xBFEEE9F7 E8 (v02 VMWARE MEMPLUG 0604 VMW 0001) [0.008965] ACPI: HPET 0xBFEEE9BF 38 (v01 VMWARE VMW HPET 0604 VMW 0001) [0.008970] ACPI: WAET 0xBFEEE997 28 (v01 VMWARE VMW WAET 0604 VMW 0001) [0.008973] ACPI: Reserving FACP table memory at [mem 0xbfefee73-0xbfefef66] [0.008975] ACPI: Reserving DSDT table memory at [mem 0xbfeeebbd-0xbfefee72] [0.008977] ACPI: Reserving FACS table memory at [mem 0xbfefffc0-0xbfef] [0.008978] ACPI: Reserving FACS table memory at [mem 0xbfefffc0-0xbfef] [0.008979] ACPI: Reserving BOOT table memory at [mem 0xbfeeeb95-0xbfeeebbc] [0.008980] ACPI: Reserving APIC table memory at [mem 0xbfeeeb1b-0xbfeeeb94] [0.008982] ACPI: Reserving MCFG table memory at [mem 0xbfeeeadf-0xbfeeeb1a] [0.008983] ACPI: Reserving SRAT table memory at [mem 0xbfeee9f7-0xbfeeeade] [0.008984] ACPI: Reserving HPET table memory at [mem 0xbfeee9bf-0xbfeee9f6] [0.008986] ACPI: Reserving WAET table memory at [mem 0xbfeee997-0xbfeee9be] [0.009144] SRAT: PXM 0 -> APIC 0x00 -> Node 0 [0.009148] SRAT: PXM 0 -> APIC 0x02 -> Node 0 [0.009149] SRAT: PXM 0 -> APIC 0x04 ->
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
It seems that Ubuntu 22.04 is affected in a critical way. Currently we had freezes only on Ubuntu22, but in Ubuntu 20.04 there are similiar loglines. After some hours of running the ubuntu 22.04 crashes and kernel/systemd are damaged. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
I collected some more loglines, produced by unproductive member of a haproxy failoversystem with usually zero load. over the weekend there are affected several servers. I think this is serious. Sep 8 17:01:06 myhost kernel: [115882.039808] CIFS: Attempting to mount \\host123\folder Sep 8 17:01:06 myhost systemd[1]: mnt-win_share.mount: Deactivated successfully. Sep 8 17:01:06 myhost kernel: [115882.497413] BUG: kernel NULL pointer dereference, address: 0040 Sep 8 17:01:06 myhost kernel: [115882.497460] #PF: supervisor read access in kernel mode Sep 8 17:01:06 myhost kernel: [115882.497485] #PF: error_code(0x) - not-present page Sep 8 17:01:06 myhost kernel: [115882.497502] PGD 0 P4D 0 Sep 8 17:01:06 myhost kernel: [115882.497515] Oops: [#1] SMP PTI Sep 8 17:01:06 myhost kernel: [115882.497530] CPU: 1 PID: 1046703 Comm: kworker/1:2 Not tainted 5.15.0-83-generic #92-Ubuntu Sep 8 17:01:06 myhost kernel: [115882.497560] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 Sep 8 17:01:06 myhost kernel: [115882.497598] Workqueue: cifsoplockd cifs_oplock_break [cifs] Sep 8 17:01:06 myhost kernel: [115882.497691] RIP: 0010:cifs_oplock_break+0x202/0x5c0 [cifs] Sep 8 17:01:06 myhost kernel: [115882.497738] Code: 89 45 b8 c0 eb 02 83 e3 01 e8 aa f6 ff ff 84 db 75 34 49 8b 47 48 4c 89 e2 0f b7 4d b8 4d 89 f0 4c 89 ee 4c 89 ff 48 8b 40 48 <48> 8b 40 40 48 8b 80 28 02 00 00 ff d0 0f 1f 00 41 89 c4 f6 05 30 Sep 8 17:01:06 myhost kernel: [115882.497794] RSP: 0018:a74603d87e10 EFLAGS: 00010246 Sep 8 17:01:06 myhost kernel: [115882.497812] RAX: RBX: RCX: Sep 8 17:01:06 myhost kernel: [115882.497834] RDX: 000b RSI: 236fcc211deddb5a RDI: 94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.497856] RBP: a74603d87e70 R08: 9408a1cd6a40 R09: Sep 8 17:01:06 myhost kernel: [115882.497879] R10: 9408a2da3000 R11: ff00 R12: 000b Sep 8 17:01:06 myhost kernel: [115882.497902] R13: 236fcc211deddb5a R14: 9408a1cd6a40 R15: 94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.497925] FS: () GS:940bafc8() knlGS: Sep 8 17:01:06 myhost kernel: [115882.497951] CS: 0010 DS: ES: CR0: 80050033 Sep 8 17:01:06 myhost kernel: [115882.497971] CR2: 0040 CR3: 0001008dc005 CR4: 007706e0 Sep 8 17:01:06 myhost kernel: [115882.498018] PKRU: 5554 Sep 8 17:01:06 myhost kernel: [115882.498029] Call Trace: Sep 8 17:01:06 myhost kernel: [115882.498040] Sep 8 17:01:06 myhost kernel: [115882.498051] ? show_trace_log_lvl+0x1d6/0x2ea Sep 8 17:01:06 myhost kernel: [115882.498071] ? show_trace_log_lvl+0x1d6/0x2ea Sep 8 17:01:06 myhost kernel: [115882.498098] ? process_one_work+0x228/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.498662] ? show_regs.part.0+0x23/0x29 Sep 8 17:01:06 myhost kernel: [115882.499192] ? __die_body.cold+0x8/0xd Sep 8 17:01:06 myhost kernel: [115882.499703] ? __die+0x2b/0x37 Sep 8 17:01:06 myhost kernel: [115882.500219] ? page_fault_oops+0x13b/0x170 Sep 8 17:01:06 myhost kernel: [115882.500699] ? kfree+0x1f7/0x250 Sep 8 17:01:06 myhost kernel: [115882.501195] ? do_user_addr_fault+0x321/0x670 Sep 8 17:01:06 myhost kernel: [115882.501657] ? exc_page_fault+0x77/0x170 Sep 8 17:01:06 myhost kernel: [115882.502125] ? asm_exc_page_fault+0x27/0x30 Sep 8 17:01:06 myhost kernel: [115882.502964] ? cifs_oplock_break+0x202/0x5c0 [cifs] Sep 8 17:01:06 myhost kernel: [115882.503767] process_one_work+0x228/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.504498] worker_thread+0x53/0x420 Sep 8 17:01:06 myhost kernel: [115882.505222] ? process_one_work+0x3d0/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.505959] kthread+0x127/0x150 Sep 8 17:01:06 myhost kernel: [115882.506719] ? set_kthread_struct+0x50/0x50 Sep 8 17:01:06 myhost kernel: [115882.507426] ret_from_fork+0x1f/0x30 Sep 8 17:01:06 myhost kernel: [115882.508112] Sep 8 17:01:06 myhost kernel: [115882.508760] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs tls intel_rapl_msr vmw_balloon intel_rapl_common isst_if_mbox_msr isst_if_common nfit rapl joydev input_leds serio_raw vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock vmw_vmci mac_hid binfmt_misc sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pstore_blk ramoops pstore_zone reed_solomon efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear vmwgfx ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd cryptd syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core ahci mptspi drm i2c_piix4 libahci mptscsih psmouse
[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update
Our servers are not connected with public internet. i cant run apport- collect: ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out You can reset the credentials by removing the file "/root/.cache/apport/launchpad.credentials" Today Morning same notice like yesterday. Again 2 Servers down and i had to hardstop them. Login by ssh was possible with extreme delay, any other commands like reboot etc. failed, just nothing happens. Hajo ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
Thanks. Just for general information, when this patch will be published to live- repos? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in iotop package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in iotop source package in Xenial: Invalid Status in linux source package in Xenial: In Progress Bug description: [Impact] The CVE-2018-3639 for Xenial introduced a double newline sequence in the /proc/PID/status files. This breaks some userspace tools, such as iotop, that parse those files. [Test Case] Incorrect output in 4.4.0-127.153-generic: $ cat /proc/self/status ... Seccomp: 0 Speculation_Store_Bypass: thread vulnerable ... Expected output: $ cat /proc/self/status ... Seccomp: 0 Speculation_Store_Bypass: thread vulnerable ... [Regression Potential] None [Original Report] Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
yes, 4.4.0-129 also seems to be ok, but again no Speculation_Store_Bypass line in /proc/PID/status. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in iotop package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in iotop source package in Xenial: Confirmed Status in linux source package in Xenial: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
** Also affects: iotop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in iotop package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in iotop source package in Xenial: Confirmed Status in linux source package in Xenial: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
Hello, i installed v4.17-rc6 and this problem seems fixed, no emtpy line in /proc/PID/status, but i also miss the line Speculation_Store_Bypass which was existing in 4.4.0-127-generic #153-Ubuntu So may be this is fixed because meltdown/spectre patches are not applied? Iam not sure, so i hesitate to set tag kernel-fixed-upstream. What do you think? For information: I could not install linux- headers-4.17.0-041700rc6-generic, there is a dependency to libssl1.1 which is not available currently for xenial. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
yes, i can fix this in iotop, but i thin the main problem is kernel and there should not exist an empty line under /proc/PID/status Ubuntu Kernel Bot told me to send logs, but i cant run apport-collect for security/dataprotection reasons. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] [NEW] Kernel produces empty lines in /proc/PID/status
Public bug reported: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: xenial ** Package changed: dpkg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
When this new kernel will be released? This bug is killing our MySQL Servers. Booting old kernels is only a bad workaround. I think a lot of people with busy servers will have a problem. This is 2.nd time we were hit by a big bug within short time. In oct 2016 our nameservers got problems because of bug 1634892 Is LTS-Ubuntu still right system for servers? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error
I also upgraded to 3.13.0-106-generic from canonical-kernel-team ppa and can confirm it is working again: # sysctl -w net.ipv4.neigh.default.gc_thresh1=8192 net.ipv4.neigh.default.gc_thresh1 = 8192 # uname -a Linux myhostname 3.13.0-106-generic #153-Ubuntu SMP Tue Dec 6 15:44:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux How to add tags? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634892 Title: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic kernel and below worked fine using the following: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 128 As of 3.13.0-97-generic, though, it no longer works as expected: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1" There are two potentially related revisions in the -97 release - http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty=563cf19389d8e999e69d6c94995966aeaf7c3a08 and http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty=7b82096b0ebc9bf487b390fe970d66ffa5a5774e. The expected behavior is that changing neighbor table settings works using 'sysctl -w' with the same values as before the -97 kernel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1 ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-98-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory CurrentDmesg: [4.586115] NET: Registered protocol family 40 Date: Wed Oct 19 06:13:36 2016 HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139 InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) IwConfig: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg noprompt quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-98-generic N/A linux-backports-modules-3.13.0-98-generic N/A linux-firmware 1.79.16 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error
Today we updated 14.04 to 3.13.0-105-generic, bug still present. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634892 Title: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic kernel and below worked fine using the following: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 128 As of 3.13.0-97-generic, though, it no longer works as expected: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1" There are two potentially related revisions in the -97 release - http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty=563cf19389d8e999e69d6c94995966aeaf7c3a08 and http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty=7b82096b0ebc9bf487b390fe970d66ffa5a5774e. The expected behavior is that changing neighbor table settings works using 'sysctl -w' with the same values as before the -97 kernel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1 ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-98-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory CurrentDmesg: [4.586115] NET: Registered protocol family 40 Date: Wed Oct 19 06:13:36 2016 HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139 InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) IwConfig: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg noprompt quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-98-generic N/A linux-backports-modules-3.13.0-98-generic N/A linux-firmware 1.79.16 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error
When this fix will appear in official kernel-release? Yesterday i updated Trusty Tahr/14.04 to 3.13.0-103-generic and this problem is still present. This is a problem for all people who use 14.04 in high frequented environments, just like nameservers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634892 Title: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic kernel and below worked fine using the following: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 128 As of 3.13.0-97-generic, though, it no longer works as expected: $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128 error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1" There are two potentially related revisions in the -97 release - http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty=563cf19389d8e999e69d6c94995966aeaf7c3a08 and http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts- backport-trusty=7b82096b0ebc9bf487b390fe970d66ffa5a5774e. The expected behavior is that changing neighbor table settings works using 'sysctl -w' with the same values as before the -97 kernel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1 ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-98-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory CurrentDmesg: [4.586115] NET: Registered protocol family 40 Date: Wed Oct 19 06:13:36 2016 HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139 InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) IwConfig: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg noprompt quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-98-generic N/A linux-backports-modules-3.13.0-98-generic N/A linux-firmware 1.79.16 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
