[Kernel-packages] [Bug 1821879] [NEW] Error
Public bug reported: ERROR: apport (pid 957) Mon Mar 25 08:21:44 2019: called for pid 438, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 957) Mon Mar 25 08:21:44 2019: executable: /sbin/plymouthd (command line "@sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session") ERROR: apport (pid 957) Mon Mar 25 08:21:44 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 957) Mon Mar 25 08:21:45 2019: wrote report /var/crash/_sbin_plymouthd.0.crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crea 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 27 10:21:36 2019 InstallationDate: Installed on 2019-03-15 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=1d5c5803-f2c3-4f8a-ad48-3787040f4fe1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.06 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic package-from-proposed -- 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/1821879 Title: Error Status in linux package in Ubuntu: Confirmed Bug description: ERROR: apport (pid 957) Mon Mar 25 08:21:44 2019: called for pid 438, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 957) Mon Mar 25 08:21:44 2019: executable: /sbin/plymouthd (command line "@sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session") ERROR: apport (pid 957) Mon Mar 25 08:21:44 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 957) Mon Mar 25 08:21:45 2019: wrote report /var/crash/_sbin_plymouthd.0.crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crea 2184 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 27 10:21:36 2019 InstallationDate: Installed on 2019-03-15 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=1d5c5803-f2c3-4f8a-ad48-3787040f4fe1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.06 dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821879/+s
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
I tested the kernel 4.15.0-46 from bionic/proposed. I confirm that it fix the problem for Ubuntu 18.04 -- 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/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1813873] Re: Userspace break as a result of missing patch backport
Am I wrong or the fix hasn't yet been released? I understood the release date was the 4th March. -- 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/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1813873] Re: Userspace break as a result of missing patch backport
still available only in Proposed though -- 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/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1813873] Re: Userspace break as a result of missing patch backport
fix confirmed, 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/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1743158] [NEW] Trackpad doesn't work proprerly
Public bug reported: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: ASUSTeK Computer Inc. Skylake Gaussian Mixture Model [1043:1bb0] 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-
[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly
apport information ** Tags added: apport-collected wayland-session ** Description changed: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: ASUSTeK Computer Inc. Skylake Gaussian Mixture Model [1043:1bb0] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- Fas
[Kernel-packages] [Bug 1743158] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1743158/+attachment/5036845/+files/ProcCpuinfoMinimal.txt ** 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/1743158 Title: Trackpad doesn't work proprerly Status in linux package in Ubuntu: Confirmed Bug description: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #1
[Kernel-packages] [Bug 1743158] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1743158/+attachment/5036843/+files/ProcCpuinfoMinimal.txt ** Description changed: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: ASUSTeK Computer Inc. Skylake Gaussian Mixture Model [1043:1bb0] Control: I/O- Mem- BusMaster- SpecCycle- MemWIN
[Kernel-packages] [Bug 1743158] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1743158/+attachment/5036844/+files/JournalErrors.txt -- 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/1743158 Title: Trackpad doesn't work proprerly Status in linux package in Ubuntu: Confirmed Bug description: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:08
[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly
** Tags added: kernel-bug-exists-upstream -- 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/1743158 Title: Trackpad doesn't work proprerly Status in linux package in Ubuntu: Incomplete Bug description: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsyste
[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly
** 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/1743158 Title: Trackpad doesn't work proprerly Status in linux package in Ubuntu: Confirmed Bug description: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8
[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly
Hello Kai, here you are the result of the command ** Attachment added: "udevadm info -e.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743158/+attachment/5039003/+files/udevadm%20info%20-e.txt -- 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/1743158 Title: Trackpad doesn't work proprerly Status in linux package in Ubuntu: Confirmed Bug description: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel dri
[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly
Ok, tomorrow I'll read that post and try to fix my issue. In case of failure what do you suggest me to do? -- 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/1743158 Title: Trackpad doesn't work proprerly Status in linux package in Ubuntu: Confirmed Bug description: Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the Elantech trackpad here the two files of the commands: 1) the file was empty because the file doesn't exist 2) 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5910] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:1bb0] 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 Skylake PCIe Controller (x16) [8086:1901] (rev 05) (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: ASUSTeK Computer Inc. Skylake PCIe Controller (x16) [1043:1bb0] 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: fee00238 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us 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 Unknown, PwrInd Unknown, 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- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/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- 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=ff 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 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:08.0 System peripheral [0880]: Intel Corporat
[Kernel-packages] [Bug 1626299] Re: ACPI Errors in dmesg, battery monitor shows empty
This problem is not solved yet, i tried many ways (changing kernel and so on), even after upgrading the bios to the latest (1.09). I tried Ubuntu 14, Ubuntu 16, Ubuntu 17, many kernel versions in Manjaro KDE. -- 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/1626299 Title: ACPI Errors in dmesg, battery monitor shows empty Status in linux package in Ubuntu: Expired Bug description: I am using Xubuntu, and the power manager show an empty battery at all times, regardless of battery level. I essentially have no indicators of how much power my laptop has left. Once I run out of power, the laptop obviously shuts down causing data corruption. my dmesg shows: [ 10.587295] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.587303] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.587309] ACPI Error: Method parse/execution failed [\_SB.TAMB._TMP] (Node 88015a0f7208), AE_NOT_EXIST (20150930/psparse-542) [ 10.587325] thermal thermal_zone0: failed to read out thermal zone (-5) [ 10.598876] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.598882] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.598886] ACPI Error: Method parse/execution failed [\_SB.TEFN._TMP] (Node 88015a0f76e0), AE_NOT_EXIST (20150930/psparse-542) [ 10.598898] thermal thermal_zone1: failed to read out thermal zone (-5) [ 10.600460] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.600465] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.600469] ACPI Error: Method parse/execution failed [\_SB.TSKN._TMP] (Node 88015a0f94b0), AE_NOT_EXIST (20150930/psparse-542) [ 10.600479] thermal thermal_zone2: failed to read out thermal zone (-5) later it shows: [ 11.235601] acer_wmi: Enabling Launch Manager failed: 0xe4 - 0x0 It's unfortunate to never know how much power is left, as one might imagine. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: coder 1607 F pulseaudio /dev/snd/controlC1: coder 1607 F pulseaudio CurrentDesktop: XFCE Date: Thu Sep 22 00:34:51 2016 HibernationDevice: RESUME=UUID=c0846449-28bd-4d6a-9ccb-732cf1582f3a InstallationDate: Installed on 2016-09-08 (13 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire SW5-173 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Crepe dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd04/11/2016:svnAcer:pnAspireSW5-173:pvrV1.08:rvnAcer:rnCrepe:rvrV1.08:cvnAcer:ct9:cvrV1.08: dmi.product.name: Aspire SW5-173 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626299/+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 1626299] Re: ACPI Errors in dmesg, battery monitor shows empty
I have the same machine, by the way i opened a new bug here https://bugzilla.kernel.org/show_bug.cgi?id=198177 ** Bug watch added: Linux Kernel Bug Tracker #198177 https://bugzilla.kernel.org/show_bug.cgi?id=198177 -- 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/1626299 Title: ACPI Errors in dmesg, battery monitor shows empty Status in linux package in Ubuntu: Expired Bug description: I am using Xubuntu, and the power manager show an empty battery at all times, regardless of battery level. I essentially have no indicators of how much power my laptop has left. Once I run out of power, the laptop obviously shuts down causing data corruption. my dmesg shows: [ 10.587295] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.587303] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.587309] ACPI Error: Method parse/execution failed [\_SB.TAMB._TMP] (Node 88015a0f7208), AE_NOT_EXIST (20150930/psparse-542) [ 10.587325] thermal thermal_zone0: failed to read out thermal zone (-5) [ 10.598876] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.598882] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.598886] ACPI Error: Method parse/execution failed [\_SB.TEFN._TMP] (Node 88015a0f76e0), AE_NOT_EXIST (20150930/psparse-542) [ 10.598898] thermal thermal_zone1: failed to read out thermal zone (-5) [ 10.600460] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.600465] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.600469] ACPI Error: Method parse/execution failed [\_SB.TSKN._TMP] (Node 88015a0f94b0), AE_NOT_EXIST (20150930/psparse-542) [ 10.600479] thermal thermal_zone2: failed to read out thermal zone (-5) later it shows: [ 11.235601] acer_wmi: Enabling Launch Manager failed: 0xe4 - 0x0 It's unfortunate to never know how much power is left, as one might imagine. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: coder 1607 F pulseaudio /dev/snd/controlC1: coder 1607 F pulseaudio CurrentDesktop: XFCE Date: Thu Sep 22 00:34:51 2016 HibernationDevice: RESUME=UUID=c0846449-28bd-4d6a-9ccb-732cf1582f3a InstallationDate: Installed on 2016-09-08 (13 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire SW5-173 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Crepe dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd04/11/2016:svnAcer:pnAspireSW5-173:pvrV1.08:rvnAcer:rnCrepe:rvrV1.08:cvnAcer:ct9:cvrV1.08: dmi.product.name: Aspire SW5-173 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626299/+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 1572435] [NEW] package linux-image-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo sta
Public bug reported: this crash happend during software installation like busybox ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-55-generic 3.16.0-55.74~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16 Uname: Linux 3.16.0-50-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Apr 20 09:46:12 2016 DpkgHistoryLog: Start-Date: 2016-04-20 09:46:09 Commandline: apt install busybox Install: busybox:i386 (1.21.0-1ubuntu1) Remove: busybox-static:i386 (1.21.0-1ubuntu1), ubuntu-standard:i386 (1.325) DuplicateSignature: package:linux-image-3.16.0-55-generic:3.16.0-55.74~14.04.1:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 InstallationDate: Installed on 2015-04-07 (378 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: linux-lts-utopic Title: package linux-image-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1572435 Title: package linux-image-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: il sottoprocesso installato script di post- installation ha restituito lo stato di errore 2 Status in linux-lts-utopic package in Ubuntu: New Bug description: this crash happend during software installation like busybox ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-55-generic 3.16.0-55.74~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16 Uname: Linux 3.16.0-50-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Apr 20 09:46:12 2016 DpkgHistoryLog: Start-Date: 2016-04-20 09:46:09 Commandline: apt install busybox Install: busybox:i386 (1.21.0-1ubuntu1) Remove: busybox-static:i386 (1.21.0-1ubuntu1), ubuntu-standard:i386 (1.325) DuplicateSignature: package:linux-image-3.16.0-55-generic:3.16.0-55.74~14.04.1:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 InstallationDate: Installed on 2015-04-07 (378 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: linux-lts-utopic Title: package linux-image-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1572435/+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 1376581] Re: DisplayPort monitor not properly detected via HP ultraslim docking station 2013
Hi all, as suggested, I tried to install the latest v3.17 kernel[0] in Ubuntu 14.10. Hardware: elitebook 840 hp ultraslim docking station 2013 Software Ubuntu 14.10 - with both the default kernel and the 3.17 - without using AMD drivers - installing the drivers available in the Additional Drivers tool (fglrx) - installing the drivers downloaded from the AMD website In the best situation, the external monitors are not rightly recognized (just 1 monitor with a lower resolution) but the screen is always off. -- 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/1376581 Title: DisplayPort monitor not properly detected via HP ultraslim docking station 2013 Status in “linux” package in Ubuntu: Confirmed Bug description: DisplayPort monitor not properly detected via HP ultraslim docking station 2013 My configuration: - Ubuntu 14.04, with all updates (3.13.0-36.63-generic 3.13.11.6) - EliteBook 850 G1 connected to a HP ultraslim docking station 2013. - 1 Dell 2209WA connected to the VGA port of the docking - 1 Dell P2414H connected to the DP of the docking Currently I have the lateste fglrx (14.301.1001), but if was the same with the version from Ubuntu repo. This is the output from xrandr: Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 eDP1 connected (normal left inverted right x axis y axis) 1920x1080 60.4 + 59.9 40.3 1680x1050 60.0 59.9 1600x1024 60.2 1400x1050 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1360x768 59.8 60.0 1152x864 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP2 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 HDMI2 disconnected (normal left inverted right x axis y axis) There is some scrambled image displayed on the DP monitor like in the attached image. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: amaguran 2383 F pulseaudio /dev/snd/controlC2: amaguran 2383 F pulseaudio /dev/snd/controlC0: amaguran 2383 F pulseaudio /dev/snd/controlC1: amaguran 2383 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-08 (135 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 850 G1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=UUID=26de6228-15cb-4089-8788-f4a0fd918347 ro splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Oct 22 09:44:23 amaguran-laptop kernel: [ 1602.950963] [UFW BLOCK] IN=eth0 OUT= MAC=28:80:23:04:15:1e:f0:1f:af:66:73:e1:08:00 SRC=10.240.11.1 DST=10.240.11.52 LEN=139 TOS=0x00 PREC=0x00 TTL=128 ID=32371 PROTO=UDP SPT=34761 DPT=29889 LEN=119 Oct 22 09:44:29 amaguran-laptop kernel: [ 1608.999016] [UFW BLOCK] IN=eth0 OUT= MAC=28:80:23:04:15:1e:f0:1f:af:66:73:e1:08:00 SRC=10.240.11.1 DST=10.240.11.52 LEN=139 TOS=0x00 PREC=0x00 TTL=128 ID=32385 PROTO=UDP SPT=34761 DPT=29889 LEN=119 _MarkForUpload: True dmi.bios.date: 07/28/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.20 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.55 dmi.chassis.asset.tag: CNU4199369 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.20:bd07/28/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.55:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 850 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: amaguran 2383 F pulseaudio /dev/snd/controlC2: amaguran 2383 F
[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute
@Andrew have you updated the grub after edit? May sound obvious but to me, as a noob, i just realized after a while that i MUST (as seen on the grub itslef, first line: "# If you change this file, run 'update-grub' afterwards to update") give in terminal sudo update-grub So here (chromebook 14 singleboot with Ubuntu 14.04 kernel 3.17) editing grub worked perfectly. Thanks Alois!! -- 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/1308264 Title: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+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 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute
AH almost forgot, if anyone care here is my output (before editing): [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.17.0-031700rc1-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 [0.00] DMI: Hewlett-Packard Falco, BIOS 08/13/2014 [2.879706] Switched to clocksource tsc [ 53.995182] evm: HMAC attrs: 0x1 I get also this strange error, but i don't know if it has anything to do with this (cuz i get the same even after editing) [2.385250] usb 2-4: string descriptor 0 malformed (err = -61), defaulting to 0x0409 -- 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/1308264 Title: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+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 1623022] [NEW] Very slow wireless with rt2800pci
Public bug reported: I have a Linksys WMP600N (rt2800pci driver). My wireless connection is extremely slow and unstable. I am using Kubuntu 16.04, with Kernel 4.4.0-36 or 4.7.0-0. The speed test results are: DL: 2.02Mbps UL:0.05Mbps Ping:183ms , the speed test with another PC with the same wireless network : DL:12Mbps UL:1.20Mbps Ping:48ms. I have follow this guide: http://askubuntu.com/questions/405644/slow-wireless-with-rt2800pci But nothing is changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 3231 F pulseaudio CurrentDesktop: KDE Date: Tue Sep 13 14:28:22 2016 HibernationDevice: RESUME=UUID=7237eef7-9261-4799-8955-b4466b0e5cb5 InstallationDate: Installed on 2016-09-02 (11 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=83949c88-4099-41fa-a6fd-f143912ae477 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7n dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7n:bd09/07/2010:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "SpeedTest" https://bugs.launchpad.net/bugs/1623022/+attachment/4740002/+files/Screenshot_20160913_142800.png -- 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/1623022 Title: Very slow wireless with rt2800pci Status in linux package in Ubuntu: New Bug description: I have a Linksys WMP600N (rt2800pci driver). My wireless connection is extremely slow and unstable. I am using Kubuntu 16.04, with Kernel 4.4.0-36 or 4.7.0-0. The speed test results are: DL: 2.02Mbps UL:0.05Mbps Ping:183ms , the speed test with another PC with the same wireless network : DL:12Mbps UL:1.20Mbps Ping:48ms. I have follow this guide: http://askubuntu.com/questions/405644/slow-wireless-with-rt2800pci But nothing is changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 3231 F pulseaudio CurrentDesktop: KDE Date: Tue Sep 13 14:28:22 2016 HibernationDevice: RESUME=UUID=7237eef7-9261-4799-8955-b4466b0e5cb5 InstallationDate: Installed on 2016-09-02 (11 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=83949c88-4099-41fa-a6fd-f143912ae477 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7n dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7n:bd09/07/2010:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lin
[Kernel-packages] [Bug 1623022] Re: Very slow wireless with rt2800pci
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: I have a Linksys WMP600N (rt2800pci driver). My wireless connection is extremely slow and unstable. I am using Kubuntu 16.04, with Kernel 4.4.0-36 or 4.7.0-0. The speed test results are: DL: 2.02Mbps UL:0.05Mbps Ping:183ms , the speed test with another PC with the same wireless network : DL:12Mbps UL:1.20Mbps Ping:48ms. I have follow this guide: http://askubuntu.com/questions/405644/slow-wireless-with-rt2800pci But nothing is changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: andrea 3231 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: andrea 3231 F pulseaudio CurrentDesktop: KDE Date: Tue Sep 13 14:28:22 2016 HibernationDevice: RESUME=UUID=7237eef7-9261-4799-8955-b4466b0e5cb5 InstallationDate: Installed on 2016-09-02 (11 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=83949c88-4099-41fa-a6fd-f143912ae477 ro quiet splash RelatedPackageVersions: - linux-restricted-modules-4.4.0-36-generic N/A - linux-backports-modules-4.4.0-36-generic N/A - linux-firmware1.157.3 + linux-restricted-modules-4.4.0-36-generic N/A + linux-backports-modules-4.4.0-36-generic N/A + linux-firmware1.157.3 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7n dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7n:bd09/07/2010:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Tags added: kernel-bug-exists-upstream -- 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/1623022 Title: Very slow wireless with rt2800pci Status in linux package in Ubuntu: Confirmed Bug description: I have a Linksys WMP600N (rt2800pci driver). My wireless connection is extremely slow and unstable. I am using Kubuntu 16.04, with Kernel 4.4.0-36 or 4.7.0-0. The speed test results are: DL: 2.02Mbps UL:0.05Mbps Ping:183ms , the speed test with another PC with the same wireless network : DL:12Mbps UL:1.20Mbps Ping:48ms. I have follow this guide: http://askubuntu.com/questions/405644/slow-wireless-with-rt2800pci But nothing is changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 3231 F pulseaudio CurrentDesktop: KDE Date: Tue Sep 13 14:28:22 2016 HibernationDevice: RESUME=UUID=7237eef7-9261-4799-8955-b4466b0e5cb5 InstallationDate: Installed on 2016-09-02 (11 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=83949c88-4099-41fa-a6fd-f143912ae477 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7n dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7n:bd09/07/2010:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTe
[Kernel-packages] [Bug 1623022] Re: Very slow wireless with rt2800pci
Workaround Connect to the 5Ghz wireless network. -- 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/1623022 Title: Very slow wireless with rt2800pci Status in linux package in Ubuntu: Confirmed Bug description: I have a Linksys WMP600N (rt2800pci driver). My wireless connection is extremely slow and unstable. I am using Kubuntu 16.04, with Kernel 4.4.0-36 or 4.7.0-0. The speed test results are: DL: 2.02Mbps UL:0.05Mbps Ping:183ms , the speed test with another PC with the same wireless network : DL:12Mbps UL:1.20Mbps Ping:48ms. I have follow this guide: http://askubuntu.com/questions/405644/slow-wireless-with-rt2800pci But nothing is changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 3231 F pulseaudio CurrentDesktop: KDE Date: Tue Sep 13 14:28:22 2016 HibernationDevice: RESUME=UUID=7237eef7-9261-4799-8955-b4466b0e5cb5 InstallationDate: Installed on 2016-09-02 (11 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. M720-US3 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=83949c88-4099-41fa-a6fd-f143912ae477 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7n dmi.board.name: M720-US3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7n:bd09/07/2010:svnGigabyteTechnologyCo.,Ltd.:pnM720-US3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM720-US3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M720-US3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623022/+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 1949289] Re: Screen flickering and then turn off.
Can you please advise how to reattach the log? I thought this was automatically done since I saw the screen annoying for papers Three issues to capture the details -- 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/1949289 Title: Screen flickering and then turn off. Status in linux package in Ubuntu: Incomplete Bug description: When I'm working without the power cable connected (mostly), I noticed that after some while - still can't identify a pattern - the screen starts to flicker and then goes black/turn off. Closing the lid and reopening after few secs restores the screen (sure at that point I have to log in again). As far as I've seen, if a second screen is connected, this is not happening. But at that point I have the power cable in. So this might explain why. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 08:57:52 2021 InstallationDate: Installed on 2021-10-19 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949289/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
Sorry, I would like to inform that I also get this issue. Is there a solution - fix to test? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Noble: In Progress Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+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 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Same here. If anybody knows how to stress the system please say. Yesterday -50 run 12 H no problems. Today -50 failed after 1 H, and now installed -51. -- 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/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1930783] Re: integrity: Problem loading X.509 certificate
Also affects: Computer: Acer Nitro 515 Ubuntu version: Ubuntu 22.04.2 LTS Kernel: linux-image-5.19.0-35-generic -- 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/1930783 Title: integrity: Problem loading X.509 certificate Status in linux package in Ubuntu: Confirmed Bug description: Following error shows on Acer machines while booting when UEFI boot is enabled. integrity: Problem loading X.509 certificate -65 The issue is discussed at https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is available at https://lkml.org/lkml/2019/7/16/23. Seems like this patch is not included in Ubuntu as I'm still getting this error. I'm using Linux Mint 20, which is based on Ubuntu 20.04. This error comes while live booting Ubuntu 20.04 and Ubuntu 18.04 also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+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 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
** This bug is no longer a duplicate of bug 1796292 Tight timeout for bcache removal causes spurious failures ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 ArecordDevices:
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Hi Ryan, I've uploaded a new test kernel:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-54.58+lp1796292/
This one is based on 4.15.0-54.58 and it addresses specifically the
bch_bucket_alloc() problem (with this patch applied:
https://lore.kernel.org/lkml/20190710093117.GA2792@xps-13/T/#u).
With this kernel I wasn't able to reproduce the hung task timeout issue
in bch_bucket_alloc() anymore.
It would be great if you could repeat your test also with this kernel.
Thanks in advance!
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures
... and, just in case, I've uploaded also a test kernel based on the latest
bionic's master-next + a bunch of extra bcache fixes:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-55.60+lp1796292+1/
If the previous kernel is still buggy it'd be nice to try also this one.
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
I've found other upstream fixes that might be interesting to test: https://git.launchpad.net/~arighi/+git/bionic-linux/log/?h=lp-1835279 I've uploaded a new test kernel here (still based of 4.15.0-54 + the backported fixes): https://kernel.ubuntu.com/~arighi/LP-1835279/ It'd be great if you could repeat your test and see if the NULL pointer dereference is still happening. 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/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+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 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.15.0-48.51 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips) -- swm properties -- phase: Packaging phase-changed: Tuesday, 02. April 2019 16:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+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 1822883] Re: linux: 3.13.0-169.219 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.13.0-169.219 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- 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/1822883 Title: linux: 3.13.0-169.219 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822882 (precise/linux-lts-trusty) -- swm properties -- phase: Ready for Packaging phase-changed: Tuesday, 02. April 2019 21:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822883/+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 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker
** Summary changed: - linux-oracle: -proposed tracker + linux-oracle: 4.15.0-1011.13 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822812 Title: linux-oracle: 4.15.0-1011.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822811 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1822820 phase: Ready for Packaging phase-changed: Wednesday, 03. April 2019 09:02 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822812/+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 1822579] Re: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1822579 Title: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: If one issues a rmmod (or modprobe -r) command after a failed fallocate attempt, it will cause error with call trace: = BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on kmem_cache_close() - Disabling lock debugging due to kernel taint INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080 CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70 c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 Call Trace: [] dump_stack+0x58/0x79 [] slab_err+0x82/0xa0 [] ? __kmalloc+0x22d/0x240 [] ? __free_slab+0xa0/0x130 [] ? free_partial+0xa9/0x1b0 [] ? free_partial+0xa9/0x1b0 [] free_partial+0xce/0x1b0 [] ? __flush_cpu_slab+0x40/0x40 [] __kmem_cache_shutdown+0x42/0x80 [] kmem_cache_destroy+0x162/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 INFO: Object 0xf43fe078 @offset=120 kmem_cache_destroy btrfs_extent_map: Slab cache still has objects CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ed4 c13c034f ef34f600 ef34f674 f4ed9f0c c119e630 c1a14d18 f55f3220 f4ed9f04 000d96ab f4ed9eec f4ed9eec f4ed9ef4 f4ed9ef4 35a7d73c 022ffd44 f8e46880 f4ed8000 f4ed9f14 f8dc0ac6 f4ed9f1c Call Trace: [] dump_stack+0x58/0x79 [] kmem_cache_destroy+0x1b0/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 Steps to reproduce this: TMP=/tmp MNT=/tmp/mnt mkdir $MNT TMPIMG0=$TMP/test0.img DEV0=`losetup -f` truncate --size 512M $TMPIMG0 losetup $DEV0 $TMPIMG0 mkfs.btrfs -f $DEV0 >& /dev/null mount $DEV0 $MNT btrfs quota enable $MNT btrfs sub create $MNT/subv btrfs qgroup limit 10M $MNT/subv fallocate --length 20M $MNT/subv/data rmmod btrfs ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169 ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 1 11:43 seq crw-rw 1 root audio 116, 33 Apr 1 11:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 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: Mon Apr 1 11:55:56 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDe
[Kernel-packages] [Bug 1822579] Re: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386
Adding a test case script to reproduce the bug. ** Attachment added: "btrfs-fallocate-test.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822579/+attachment/5252459/+files/btrfs-fallocate-test.sh -- 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/1822579 Title: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: If one issues a rmmod (or modprobe -r) command after a failed fallocate attempt, it will cause error with call trace: = BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on kmem_cache_close() - Disabling lock debugging due to kernel taint INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080 CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70 c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 Call Trace: [] dump_stack+0x58/0x79 [] slab_err+0x82/0xa0 [] ? __kmalloc+0x22d/0x240 [] ? __free_slab+0xa0/0x130 [] ? free_partial+0xa9/0x1b0 [] ? free_partial+0xa9/0x1b0 [] free_partial+0xce/0x1b0 [] ? __flush_cpu_slab+0x40/0x40 [] __kmem_cache_shutdown+0x42/0x80 [] kmem_cache_destroy+0x162/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 INFO: Object 0xf43fe078 @offset=120 kmem_cache_destroy btrfs_extent_map: Slab cache still has objects CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ed4 c13c034f ef34f600 ef34f674 f4ed9f0c c119e630 c1a14d18 f55f3220 f4ed9f04 000d96ab f4ed9eec f4ed9eec f4ed9ef4 f4ed9ef4 35a7d73c 022ffd44 f8e46880 f4ed8000 f4ed9f14 f8dc0ac6 f4ed9f1c Call Trace: [] dump_stack+0x58/0x79 [] kmem_cache_destroy+0x1b0/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 Steps to reproduce this: TMP=/tmp MNT=/tmp/mnt mkdir $MNT TMPIMG0=$TMP/test0.img DEV0=`losetup -f` truncate --size 512M $TMPIMG0 losetup $DEV0 $TMPIMG0 mkfs.btrfs -f $DEV0 >& /dev/null mount $DEV0 $MNT btrfs quota enable $MNT btrfs sub create $MNT/subv btrfs qgroup limit 10M $MNT/subv fallocate --length 20M $MNT/subv/data rmmod btrfs ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169 ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 1 11:43 seq crw-rw 1 root audio 116, 33 Apr 1 11:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 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: Mon Apr 1 11:55:56 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:
[Kernel-packages] [Bug 1822579] Re: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386
This problem is fixed by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be2d253cc98244765323a7c94cc1ac5cd5a17072. Only Xenial seems to be affected. I'll post an SRU soon. -- 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/1822579 Title: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: If one issues a rmmod (or modprobe -r) command after a failed fallocate attempt, it will cause error with call trace: = BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on kmem_cache_close() - Disabling lock debugging due to kernel taint INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080 CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70 c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 Call Trace: [] dump_stack+0x58/0x79 [] slab_err+0x82/0xa0 [] ? __kmalloc+0x22d/0x240 [] ? __free_slab+0xa0/0x130 [] ? free_partial+0xa9/0x1b0 [] ? free_partial+0xa9/0x1b0 [] free_partial+0xce/0x1b0 [] ? __flush_cpu_slab+0x40/0x40 [] __kmem_cache_shutdown+0x42/0x80 [] kmem_cache_destroy+0x162/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 INFO: Object 0xf43fe078 @offset=120 kmem_cache_destroy btrfs_extent_map: Slab cache still has objects CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 c1b0d967 35a7d73c 0286 f4ed9ed4 c13c034f ef34f600 ef34f674 f4ed9f0c c119e630 c1a14d18 f55f3220 f4ed9f04 000d96ab f4ed9eec f4ed9eec f4ed9ef4 f4ed9ef4 35a7d73c 022ffd44 f8e46880 f4ed8000 f4ed9f14 f8dc0ac6 f4ed9f1c Call Trace: [] dump_stack+0x58/0x79 [] kmem_cache_destroy+0x1b0/0x1e0 [] extent_map_exit+0x16/0x20 [btrfs] [] exit_btrfs_fs+0x26/0x206 [btrfs] [] SyS_delete_module+0x1af/0x200 [] ? fput+0xd/0x10 [] ? task_work_run+0x8f/0xa0 [] ? exit_to_usermode_loop+0xb6/0xe0 [] do_fast_syscall_32+0x9f/0x160 [] sysenter_past_esp+0x3d/0x61 Steps to reproduce this: TMP=/tmp MNT=/tmp/mnt mkdir $MNT TMPIMG0=$TMP/test0.img DEV0=`losetup -f` truncate --size 512M $TMPIMG0 losetup $DEV0 $TMPIMG0 mkfs.btrfs -f $DEV0 >& /dev/null mount $DEV0 $MNT btrfs quota enable $MNT btrfs sub create $MNT/subv btrfs qgroup limit 10M $MNT/subv fallocate --length 20M $MNT/subv/data rmmod btrfs ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169 ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 1 11:43 seq crw-rw 1 root audio 116, 33 Apr 1 11:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 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: Mon Apr 1 11:55:56 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:r
[Kernel-packages] [Bug 1822579] Re: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386
** Description changed: - If one issues a rmmod (or modprobe -r) command after a failed fallocate - attempt, it will cause error with call trace: + SRU Justification: - = - BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on kmem_cache_close() - - + [Impact] + + * If fallocate() is failing on a btrfs subvolume when its qgroup quota + limit exceeded, a previously allocated extent map isn't correctly + released, causing a memory leak from the pool btrfs_extent_map. + + * Fix by correctly deallocating the object in case of failure + + [Test Case] - Disabling lock debugging due to kernel taint - INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080 - CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu - Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 - c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70 - c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f - 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 - Call Trace: - [] dump_stack+0x58/0x79 - [] slab_err+0x82/0xa0 - [] ? __kmalloc+0x22d/0x240 - [] ? __free_slab+0xa0/0x130 - [] ? free_partial+0xa9/0x1b0 - [] ? free_partial+0xa9/0x1b0 - [] free_partial+0xce/0x1b0 - [] ? __flush_cpu_slab+0x40/0x40 - [] __kmem_cache_shutdown+0x42/0x80 - [] kmem_cache_destroy+0x162/0x1e0 - [] extent_map_exit+0x16/0x20 [btrfs] - [] exit_btrfs_fs+0x26/0x206 [btrfs] - [] SyS_delete_module+0x1af/0x200 - [] ? fput+0xd/0x10 - [] ? task_work_run+0x8f/0xa0 - [] ? exit_to_usermode_loop+0xb6/0xe0 - [] do_fast_syscall_32+0x9f/0x160 - [] sysenter_past_esp+0x3d/0x61 - INFO: Object 0xf43fe078 @offset=120 - kmem_cache_destroy btrfs_extent_map: Slab cache still has objects - CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu - Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 - c1b0d967 35a7d73c 0286 f4ed9ed4 c13c034f ef34f600 ef34f674 f4ed9f0c - c119e630 c1a14d18 f55f3220 f4ed9f04 000d96ab f4ed9eec f4ed9eec f4ed9ef4 - f4ed9ef4 35a7d73c 022ffd44 f8e46880 f4ed8000 f4ed9f14 f8dc0ac6 f4ed9f1c - Call Trace: - [] dump_stack+0x58/0x79 - [] kmem_cache_destroy+0x1b0/0x1e0 - [] extent_map_exit+0x16/0x20 [btrfs] - [] exit_btrfs_fs+0x26/0x206 [btrfs] - [] SyS_delete_module+0x1af/0x200 - [] ? fput+0xd/0x10 - [] ? task_work_run+0x8f/0xa0 - [] ? exit_to_usermode_loop+0xb6/0xe0 - [] do_fast_syscall_32+0x9f/0x160 - [] sysenter_past_esp+0x3d/0x61 + * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822579/+attachment/5252459/+files/btrfs-fallocate-test.sh + [Fix] + + * + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be2d253cc98244765323a7c94cc1ac5cd5a17072 + + Fix the memory leak by adding the proper free_extent_map() call to the + failure path. + + [Regression Potential] + + * This is an upstream fix, tested on the affected platform. The patch + is really small, backport changes are minimal. All the other Ubuntu + releases are including this fix already. + + [Original bug report] + If one issues a rmmod (or modprobe -r) command after a failed fallocate attempt, it will cause error with call trace: + + = + BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on kmem_cache_close() + - + + Disabling lock debugging due to kernel taint + INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080 + CPU: 1 PID: 1608 Comm: rmmod Tainted: GB 4.4.0-143-generic #169-Ubuntu + Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 + c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70 + c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f + 20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74 + Call Trace: + [] dump_stack+0x58/0x79 + [] slab_err+0x82/0xa0 + [] ? __kmalloc+0x22d/0x240 + [] ? __free_slab+0xa0/0x130 + [] ? free_partial+0xa9/0x1b0 + [] ? free_partial+0xa9/0x1b0 + [] free_partial+0xce/0x1b0 + [] ? __flush_cpu_slab+0x40/0x40 + [] __kmem_cache_shutdown+0x42/0x80 + [] kmem_cache_destroy+0x162/0x1e0 + [] extent_map_exit+0x16/0x20 [btrfs] + [] exit_btrfs_fs+0x26/0x206 [btrfs] + [] SyS_delete_module+0x1af/0x200 + [] ? fput+0xd/0x10 + [] ? task_work_run+0x8f/0xa0 + [] ? exit_to_usermode_loop+0xb6/0xe0 + [] do_fast_syscall_32+0x9f/0x160 + [] sysenter_past_esp+0x3d/0x61 + INFO: Object 0xf43fe078 @offset=120 + kmem_cache_destroy btrfs_extent_map: Slab cache still has objects +
[Kernel-packages] [Bug 1822826] Re: linux-kvm: 4.4.0-1044.50 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.4.0-1044.50 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1822826 Title: linux-kvm: 4.4.0-1044.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822834 phase: Ready for Packaging phase-changed: Wednesday, 03. April 2019 09:33 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822826/+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 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822812 Title: linux-oracle: 4.15.0-1011.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822811 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1822820 phase: Packaging phase-changed: Wednesday, 03. April 2019 10:35 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822812/+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 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.15.0-1042.46 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822817 Title: linux-azure: 4.15.0-1042.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1822820 phase: Ready for Packaging phase-changed: Wednesday, 03. April 2019 08:36 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+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 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1080.90 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822824 Title: linux-aws: 4.4.0-1080.90 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822834 phase: Packaging phase-changed: Thursday, 04. April 2019 12:36 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822824/+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 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.15.0-1036.38 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822805 Title: linux-aws: 4.15.0-1036.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- kernel-stable-master-bug: 1822820 phase: Ready for Packaging phase-changed: Wednesday, 03. April 2019 09:03 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+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 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
I've done a test with the fix from bug #1813244 and the problem doesn't
seem to happen. Probably a duplicate bug.
--
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/1736390
Title:
openvswitch: kernel oops destroying interfaces on i386
Status in linux package in Ubuntu:
In Progress
Status in openvswitch package in Ubuntu:
Invalid
Status in linux source package in Artful:
Won't Fix
Status in openvswitch source package in Artful:
Invalid
Status in linux source package in Bionic:
In Progress
Status in openvswitch source package in Bionic:
Invalid
Status in linux source package in Cosmic:
In Progress
Status in openvswitch source package in Cosmic:
Invalid
Status in linux source package in Disco:
In Progress
Status in openvswitch source package in Disco:
Invalid
Bug description:
== SRU Justification ==
Commit 120645513f55 ("openvswitch: Add eventmask support to CT
action.") introduced a regression on i386. Simply running the
following commands in a loop will trigger a crash rather quickly:
ovs-vsctl add-br test
ovs-vsctl del-br test
== Fix ==
Disable the logic introduced by the above commit on i386.
== Regression Potential ==
Low, the above commit introduced a new feature. Per upstream, the
result of not having this feature results in higher CPU usage and
potential buffering issues in user space.
== Test Case ==
See SRU justification above.
Original bug description:
Reproducable on bionic using the autopkgtest's from openvswitch on
i386:
[ 41.420568] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 41.421000] IP: igmp_group_dropped+0x21/0x220
[ 41.421246] *pdpt = 1d62c001 *pde =
[ 41.421659] Oops: [#1] SMP
[ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse
virtio_blk virtio_net pata_acpi floppy
[ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW
4.13.0-18-generic #21-Ubuntu
[ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.10.2-1ubuntu1 04/01/2014
[ 41.424849] Workqueue: netns cleanup_net
[ 41.425071] task: db8fba80 task.stack: dba1
[ 41.425346] EIP: igmp_group_dropped+0x21/0x220
[ 41.425656] EFLAGS: 00010202 CPU: 0
[ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002
[ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
[ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0
[ 41.427340] Call Trace:
[ 41.427485] ? __wake_up+0x36/0x40
[ 41.427680] ip_mc_down+0x27/0x90
[ 41.427869] inetdev_event+0x398/0x4e0
[ 41.428082] ? skb_dequeue+0x5b/0x70
[ 41.428286] ? wireless_nlevent_flush+0x4c/0x90
[ 41.428541] notifier_call_chain+0x4e/0x70
[ 41.428772] raw_notifier_call_chain+0x11/0x20
[ 41.429023] call_netdevice_notifiers_info+0x2a/0x60
[ 41.429301] dev_close_many+0x9d/0xe0
[ 41.429509] rollback_registered_many+0xd7/0x380
[ 41.429768] unregister_netdevice_many.part.102+0x10/0x80
[ 41.430075] default_device_exit_batch+0x134/0x160
[ 41.430344] ? do_wait_intr_irq+0x80/0x80
[ 41.430650] ops_exit_list.isra.8+0x4d/0x60
[ 41.430886] cleanup_net+0x18e/0x260
[ 41.431090] process_one_work+0x1a0/0x390
[ 41.431317] worker_thread+0x37/0x450
[ 41.431525] kthread+0xf3/0x110
[ 41.431714] ? process_one_work+0x390/0x390
[ 41.431941] ? kthread_create_on_node+0x20/0x20
[ 41.432187] ret_from_fork+0x19/0x24
[ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
[ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
[ 41.433750] CR2:
[ 41.433961] ---[ end trace 595db54cab84070c ]---
system then becomes unresponsive; no further interfaces can be
created.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
Fix has been merged upstream. -- 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_
[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822816 Title: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822817 phase: Ready for Packaging phase-changed: Thursday, 04. April 2019 17:09 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822816/+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 1823320] [NEW] Asus Zenbook 14 UX433F - NumPad
Public bug reported: I just bought this amazing laptop, installed Linux Ubuntu 18.04 LTS, upgraded the kernel to v5.0.6 to get sound working. Everything is working except the new feature of the numpad keys within the touchpad. Discussion already opened in the past but never solved: https://unix.stackexchange.com/questions/494400/asus-zenbook-ux433-ux333 -configure-touchpad-embedded-numpad-on-linux https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183 Thanks for any hints ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1823320 Title: Asus Zenbook 14 UX433F - NumPad Status in linux package in Ubuntu: Incomplete Bug description: I just bought this amazing laptop, installed Linux Ubuntu 18.04 LTS, upgraded the kernel to v5.0.6 to get sound working. Everything is working except the new feature of the numpad keys within the touchpad. Discussion already opened in the past but never solved: https://unix.stackexchange.com/questions/494400/asus-zenbook- ux433-ux333-configure-touchpad-embedded-numpad-on-linux https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183 Thanks for any hints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823320/+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 1820275] Re: btrfs-kernel oops from btrfs subvolume delete command
Moreover, any chance to add slub_debug=FZPU to the kernel boot parameters and see if we can trigger the problem again? This would add useful information to the kernel oops reported in syslog. 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/1820275 Title: btrfs-kernel oops from btrfs subvolume delete command Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: This report show a kernel oops in the btrfs lugin , happened every few days when running a test suite on a test system. It looks like their systemd/Journal failed to kick off a dump immediately following the panic. The exploiter is using the kernel 4.15.0-42 We're not sure it's the btrfs subvolume delete that's causing it yet Following infos are attached: - syslog - sosreport - kdump output here : https://ibm.ent.box.com/folder/70219521934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1820275/+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 1823499] Re: RPM wakelock ref not held during HW access
This seems to be fixed upstream by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a8ab5ea0cde753b03bfefe4c98a8c4c61f46550 -- 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/1823499 Title: RPM wakelock ref not held during HW access Status in linux package in Ubuntu: Confirmed Bug description: [ 2249.763713] [ cut here ] [ 2249.763716] RPM wakelock ref not held during HW access [ 2249.763839] WARNING: CPU: 3 PID: 472 at drivers/gpu/drm/i915/intel_drv.h:2138 gen5_read32+0x11d/0x130 [i915] [ 2249.763840] Modules linked in: nfnetlink xt_tcpudp snd_hda_codec_hdmi xt_conntrack snd_hda_codec_realtek nf_conntrack snd_hda_codec_generic ledtrig_audio nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter snd_hda_intel bpfilter snd_hda_codec snd_hda_core snd_hwdep arc4 snd_pcm snd_seq_midi snd_seq_midi_event uvcvideo ath9k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 ath9k_common videobuf2_common ath9k_hw snd_rawmidi intel_powerclamp coretemp ath videodev media mac80211 intel_cstate snd_seq joydev input_leds cfg80211 serio_raw intel_ips snd_seq_device snd_timer snd sony_laptop mac_hid mei_me mei soundcore sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs btrfs xor zstd_compress raid6_pq libcrc32c dm_mirror dm_region_hash dm_log i915 kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops sdhci_pci psmouse drm ahci libahci cqhci sky2 lpc_ich sdhci video [ 2249.763900] CPU: 3 PID: 472 Comm: ips-monitor Not tainted 5.0.0-8-generic #9-Ubuntu [ 2249.763902] Hardware name: Sony Corporation VPCEB15FM/VAIO, BIOS R0300Y8 07/20/2010 [ 2249.763952] RIP: 0010:gen5_read32+0x11d/0x130 [i915] [ 2249.763955] Code: 55 dc e9 2d ff ff ff 80 3d 47 19 11 00 00 0f 85 2e ff ff ff 48 c7 c7 f0 f8 45 c0 89 55 dc c6 05 30 19 11 00 01 e8 15 1a 72 d6 <0f> 0b 8b 55 dc e9 0e ff ff ff 66 0f 1f 84 00 00 00 00 00 66 66 66 [ 2249.763957] RSP: 0018:b92cc0a33e20 EFLAGS: 00010082 [ 2249.763959] RAX: RBX: 99a18474 RCX: [ 2249.763961] RDX: 0002 RSI: 9855a8ea RDI: 0046 [ 2249.763962] RBP: b92cc0a33e48 R08: 0002 R09: 9855a8c0 [ 2249.763964] R10: 045fb6a38aa0 R11: R12: 000112e4 [ 2249.763966] R13: 00cc R14: 99a18cb57ec0 R15: 99a18cb57f40 [ 2249.763968] FS: () GS:99a193ec() knlGS: [ 2249.763970] CS: 0010 DS: ES: CR0: 80050033 [ 2249.763972] CR2: 7f369be34000 CR3: 4460e000 CR4: 06e0 [ 2249.763974] Call Trace: [ 2249.764018] __i915_chipset_val+0x51/0x160 [i915] [ 2249.764059] i915_read_mch_val+0x2e/0x60 [i915] [ 2249.764064] ips_monitor+0x46c/0x560 [intel_ips] [ 2249.764070] kthread+0x120/0x140 [ 2249.764073] ? ips_probe+0x650/0x650 [intel_ips] [ 2249.764077] ? __kthread_parkme+0x70/0x70 [ 2249.764081] ret_from_fork+0x35/0x40 [ 2249.764085] ---[ end trace d7875370c8c0873e ]--- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.8.9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js12367 F pulseaudio CurrentDesktop: LXQt Date: Sat Apr 6 22:23:10 2019 InstallationDate: Installed on 2019-03-10 (27 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:6409 Microdia Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Sony Corporation VPCEB15FM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=21099aa8-c55d-4180-9011-29a6f9fe4561 ro ipv6.disable=1 elevator=deadline quiet splash resume=UUID=a926bd0d-7579-483f-a6a8-edafea197e79 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0300Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corp
[Kernel-packages] [Bug 1823320] Re: Asus Zenbook 14 UX433F - NumPad
*** This bug is a duplicate of bug 1810183 *** https://bugs.launchpad.net/bugs/1810183 I see a message running apport-collect 1823320 saying that I'm not the owner of the bug report or it is a duplicate. I subscribed the duplicated bug report, if you need additional info from logs please let me know. Thanks, Andrea -- 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/1823320 Title: Asus Zenbook 14 UX433F - NumPad Status in linux package in Ubuntu: Incomplete Bug description: I just bought this amazing laptop, installed Linux Ubuntu 18.04 LTS, upgraded the kernel to v5.0.6 to get sound working. Everything is working except the new feature of the numpad keys within the touchpad. Discussion already opened in the past but never solved: https://unix.stackexchange.com/questions/494400/asus-zenbook- ux433-ux333-configure-touchpad-embedded-numpad-on-linux https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183 Thanks for any hints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823320/+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 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns - kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the superblock's namespace or a descendant b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems outside of init_user_ns - which suggests that other FUSE fixes should be cherry-picked too. - Please consider cherry-picking those additional patches too. They are all in upstream kernel + Please consider cherry-picking those additional patches too. They are all in upstream kernel stable series, e.g. stable/linux-4.14.y has them: kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-4.14.y -- fs/fuse/ 266a69895b89 fuse: handle zero sized retrieve correctly b928e93d864c fuse: decrement NR_WRITEBACK_TEMP on the right page 65f222bb370e fuse: call pipe_buf_release() under pipe lock c1149b873482 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS 6ceec07cc84a fuse: fix leaked notify reply a42d933dc281 fuse: fix use-after-free in fuse_direct_IO() 78da72ee42d8 fuse: set FR_SENT while locked f6f21a2b70c6 fuse: fix blocked_waitq wakeup ab962e91008a fuse: Fix use-after-free in fuse_dev_do_write() d94b3a2375cb fuse: Fix use-after-free in fuse_dev_do_read() e8a3f3a03655 fuse: Add missed unlock_page() to fuse_readpages_fill() ff4a71855d0a fuse: Fix oops at process_init_reply() 973206923812 fuse: umount should wait for all requests fc17d7519e8e fuse: fix unlocked access to processing queue cfb6eca6e4bb fuse: fix double request_end() 7d392674443c fuse: fix initial parallel dirops eaebcf902ae0 fuse: Don't access pipe->buffers without pipe_lock() 69829f749a43 fuse: fix control dir setup and teardown 3a37d85a90da fuse: don't keep dead fuse_conn at fuse_fill_super(). 2f7bf369b5f8 fuse: atomic_o_trunc should truncate pagecache 02832578eb9d fuse: fix congested state leak on aborted connections - - and it is just that stable/linux-4.15.y stopped being maintained by Greg KH. + and it is just that stable/linux-4.15.y stopped being maintained by Greg + KH. Thanks beforehand, Kirill - --- + --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=dec25862-42c7-4494-8f75-e6cc76aa65ea InstallationDate: Installed on 2019-02-28 (39 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) IwConfig: - lono wireless extensions. - - ens3 no wireless extensions. + lono wireless extensions. + + ens3 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 virtiodrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=fe1f50d9-7142-4ee3-8904-bae7d80bc6b1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 RelatedPackageVersions: - linux-restricted-modules-4.15.0-45-generic N/A - linux-backports-modules-4.15.0-45-generic N/A - linux-firmware 1.157.21 + linux-restricted-modules-4.15.0-45-generic N/A + linux-backports-modules-4.15.0-45-generic N/A + linux-firmware 1.157.21 RfKill: - + Tags: xenial Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Description changed: SRU Justification: [Impact] - * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a + * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a race condition that leave fuse inode's mutex held, triggering a dea
[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
I'll take a look at the other patches, I think they can be easily applied to 4.15 if they don't require too much backporting work. -- 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/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: [Impact] * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a race condition that leave fuse inode's mutex held, triggering a deadlock * The problem is that the lock and unlock paths are relying on get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to be acquired/released, but its value might be set in the lock path and unset in the unlock path (leaving the mutex held) [Test Case] * A test case that triggers the bug almost immediately can be found here https://github.com/hanwen/go-fuse/pull/288 [Fix] * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the locking path and pass a variable to fuse_unlock_inode() to determine if the mutex was acquired or not [Regression Potential] * Fix has been tested on the affected platform. It is an upstream fix that seems to affect only 4.7+ kernels, more exactly in our case only Bionic kernels (and derived) are affected. Cosmic and above already include this fix. So regression potential is minimal. [Original bug report] Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: All
[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
@navytux yes, a few of them require minimal changes, but most of them can be applied cleanly to 4.15. -- 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/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: [Impact] * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a race condition that leave fuse inode's mutex held, triggering a deadlock * The problem is that the lock and unlock paths are relying on get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to be acquired/released, but its value might be set in the lock path and unset in the unlock path (leaving the mutex held) [Test Case] * A test case that triggers the bug almost immediately can be found here https://github.com/hanwen/go-fuse/pull/288 [Fix] * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the locking path and pass a variable to fuse_unlock_inode() to determine if the mutex was acquired or not [Regression Potential] * Fix has been tested on the affected platform. It is an upstream fix that seems to affect only 4.7+ kernels, more exactly in our case only Bionic kernels (and derived) are affected. Cosmic and above already include this fix. So regression potential is minimal. [Original bug report] Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on aborted connections 45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts 12
[Kernel-packages] [Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
All fixes applied here: git://git.launchpad.net/~arighi/+git/bionic-linux fuse-fixes And also sent an SRU pull request. Let's see if they get merged. -- 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/1823972 Title: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: SRU Justification: [Impact] * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a race condition that leave fuse inode's mutex held, triggering a deadlock * The problem is that the lock and unlock paths are relying on get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to be acquired/released, but its value might be set in the lock path and unset in the unlock path (leaving the mutex held) [Test Case] * A test case that triggers the bug almost immediately can be found here https://github.com/hanwen/go-fuse/pull/288 [Fix] * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the locking path and pass a variable to fuse_unlock_inode() to determine if the mutex was acquired or not [Regression Potential] * Fix has been tested on the affected platform. It is an upstream fix that seems to affect only 4.7+ kernels, more exactly in our case only Bionic kernels (and derived) are affected. Cosmic and above already include this fix. So regression potential is minimal. [Original bug report] Hello up there, We were reported about a deadlock in the kernel while using a FUSE-based filesystem on Ubuntu. The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the following patch, in despite the patch being marked as needed for v4.7+ stable kernels: https://git.kernel.org/linus/63576c13bd Please see the following go-fuse issue for full details: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562 The bug is potentially applicable to libfuse users too since libfuse by default enables parallel dirops whenever kernel claims support for it, which libfuse maintained confirmed: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202 https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381 We tested that cherry-picking 63576c13bd into 4.15.x series makes the problem go away: https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969 So please include https://git.kernel.org/linus/63576c13bd into Ubuntu 4.15.x kernel series which are bionic/master and xenial/hwe, and which currently don't have this patch. Here is a full list of FUSE patches marked to be needed in stable kernels starting from v4.15: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 --grep="stable@" -- fs/fuse/ a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page 9509941e9c53 fuse: call pipe_buf_release() under pipe lock 8a3177db59cd cuse: fix ioctl 97e1532ef81a fuse: handle zero sized retrieve correctly 2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS ebacb8127359 fuse: fix use-after-free in fuse_direct_IO() 2d84a2d19b61 fuse: fix possibly missed wake-up after abort 7fabaf303458 fuse: fix leaked notify reply 908a572b80f6 fuse: fix blocked_waitq wakeup 4c316f2f3ff3 fuse: set FR_SENT while locked d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write() bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read() a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock() 63576c13bd17 fuse: fix initial parallel dirops e8f3bd773d22 fuse: Fix oops at process_init_reply() b8f95e5d13f5 fuse: umount should wait for all requests 45ff350bbd9d fuse: fix unlocked access to processing queue 87114373ea50 fuse: fix double request_end() 543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at fuse_fill_super(). 6becdb601bae fuse: fix control dir setup and teardown 8a301eb16d99 fuse: fix congested state leak on aborted connections df0e91d48827 fuse: atomic_o_trunc should truncate pagecache Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to 4.15.x becuase they cure a problem introduced in a later kernel (please see got log without --oneline for stable@ details) However both bionic and xenial/hwe has much less fuse patches applied: kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master -- fs/fuse/ e992e3521885 fuse: fix control dir setup and teardown f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super(). 840c77082f93 fuse: atomic_o_trunc should truncate pagecache c0e31b214498 fuse: fix congested state leak on a
[Kernel-packages] [Bug 1824553] [NEW] Bionic update: update stable patchset for fuse 2019-04-12
Public bug reported: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Andrea Righi (arighi) Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1824553 Title: Bionic update: update stable patchset for fuse 2019-04-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+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 1824553] Re: Bionic update: update stable patchset for fuse 2019-04-12
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Assignee: Andrea Righi (arighi) => (unassigned) -- 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/1824553 Title: Bionic update: update stable patchset for fuse 2019-04-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+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 1824553] Re: Bionic update: upstream stable patchset for fuse 2019-04-12
** Summary changed: - Bionic update: update stable patchset for fuse 2019-04-12 + Bionic update: upstream stable patchset for fuse 2019-04-12 -- 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/1824553 Title: Bionic update: upstream stable patchset for fuse 2019-04-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: SRU Justification: [Impact] This stable patchset update affects only the FUSE filesystem, since we have received bug reports about FUSE causing problems with the Bionic kernel, see also bug #1823972. The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-04-12 (ported from v4.15 .. v5.0) from git://git.kernel.org/ fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock fuse: handle zero sized retrieve correctly fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS fuse: fix use-after-free in fuse_direct_IO() fuse: fix possibly missed wake-up after abort fuse: fix leaked notify reply fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked fuse: Fix use-after-free in fuse_dev_do_write() fuse: Fix use-after-free in fuse_dev_do_read() fuse: Don't access pipe->buffers without pipe_lock() fuse: Fix oops at process_init_reply() fuse: umount should wait for all requests fuse: fix unlocked access to processing queue fuse: fix double request_end() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824553/+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 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
@jason-hobbs, I don't see any kernel error in the log attached to comment #53, so it seems to be a different issue, maybe a performance regression that is causing curtin to timeout. I would keep this bug closed / fixed and open a new one. If you can easily reproduce it, could you open a new bug and collect some info on the box after the problem happens? (in particular uname -a, dmesg, ps axuw). 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/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-c
[Kernel-packages] [Bug 1828134] Re: Wifi not working after suspend/resume cycle
Interesting that the d3cold_allowed change made some differences (I'm assuming it was failing 100% of the times before that change). Few more questions. After a bad resume: 1) are there unkillable processes (D state) in the system (`ps axuw | grep D`)? 2) does `sudo iwlist wlp4s0 scan` return any error or does it hang indefinitely? 3) do you have bluetooth enabled (what's the output of `sudo rfkill list`)? As a temporary workaround you can automate the modprobe trick (#3) doing something like the following: $ cat /lib/systemd/system-sleep/iwlmvm.sh #!/bin/sh case $1 in pre) modprobe -r iwlmvm ;; post) modprobe iwlmvm ;; esac But it'd be nice to find a proper solution to this. 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/1828134 Title: Wifi not working after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828134/+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 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Hi Hyeonho, good catch. It looks like b49151d684f44 renamed tx_waited to
tx_dirty_delayed, but only in the tracepoint definition in trace_dmu.h
and not in the rest of the code. I think we should simply restore the
original name.
Can you check if this patch solves the problem? Thanks.
** Patch added: "zfs-fix-build-error-with-tracepoints-enabled.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828763/+attachment/5263595/+files/zfs-fix-build-error-with-tracepoints-enabled.patch
--
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/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
__entry->tx_start = tx->tx_start;
__entry->tx_wait_dirty = tx->tx_wait_dirty;
__entry->tx_err = tx->tx_err;
__entry->dirty = dir
[Kernel-packages] [Bug 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
** Tags added: patch
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
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/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
__entry->tx_start = tx->tx_start;
__entry->tx_wait_dirty = tx->tx_wait_dirty;
__entry->tx_err = tx->tx_err;
__entry->dirty = dirty;
__entry->min_tx_time= min_tx_time;
),
TP_printk("tx { txg %llu lastsnap_txg %llu tx_lasttried_txg %llu "
"anyobj %d dirty_delayed %d start %llu wait_dirty %d err %i "
"} dirty %llu min_tx_time %llu",
__entry->tx_txg, __en
[Kernel-packages] [Bug 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Hyeonho, you're absolutely right, there's a typo in my previous patch.
Can you double check if this one is correct? Thanks again!
** Patch added: "zfs-fix-build-error-with-tracepoints-enabled-v2.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828763/+attachment/5263626/+files/zfs-fix-build-error-with-tracepoints-enabled-v2.patch
--
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/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
__entry->tx_lasttried_txg = tx->tx_lasttried_txg;
__entry->tx_anyobj = tx->tx_anyobj;
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
__entry->tx_start = tx->tx_start;
__entry->tx_wait_dirty = tx->tx_wait_dirty;
__entry->tx_err = tx->tx_err;
__entry->dirty = dirty;
__entry->min_tx_time= min_tx_time;
),
TP_printk("tx { txg %llu lastsnap_txg %llu tx_lasttrie
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Bug description: I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+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 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
** Tags added: bionic cosmic -- 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/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Bug description: I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+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 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
** Description changed:
+ [Impact]
+
+ * In b49151d684f44 tx_waited has been renamed to tx_dirty_delayed, but
+ only in the tracepoint definition (in trace_dmu.h) and not in the rest
+ of the code, causing build errors if zfs tracepoints are enabled.
+
+ * Fix by reverting tx_dirty_delayed back to the original name tx_waited
+
+ NOTE: this bug doesn't show up in regular kernel builds, because zfs
+ tracepoints are not enabled by default, it is possible to see this
+ problem only by enabling them and recompiling zfs outside our regular
+ build process, but it's a good cleanup anyway (in case we need to enable
+ zfs tracepoints in the future).
+
+ [Test Case]
+
+ * enable zfs tracepoints in config and build zfs
+
+ [Fix]
+
+ * Restore the old struct name to fix the build bug
+
+ [Regression Potential]
+
+ * It is a very small fix (just a rename of a struct member), so
+ regression potential is minimal
+
+ [Original bug report]
+
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
- UBUNTU: Ubuntu-4.15.0-48.51
-
- Signed-off-by: Andrea Righi
+ UBUNTU: Ubuntu-4.15.0-48.51
+
+ Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point, 'zfs/module/zfs/trace.c'
(as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
- from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
- from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
+ from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
+ from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
- __entry->tx_dirty_delayed = tx->tx_dirty_delayed;
- ^
+ __entry->tx_dirty_delayed = tx->tx_dirty_delayed;
+ ^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
- { assign; } \
- ^~
+ { assign; } \
+ ^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
- TP_fast_assign(
- ^~
+ TP_fast_assign(
+ ^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
- from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
- from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
+ from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
+ from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
- __entry->tx_dirty_delayed = tx->tx_dirty_delayed;
- ^
+ __entry->tx_dirty_delayed = tx->tx_dirty_delayed;
+ ^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
- { assign; } \
- ^~
+ { assign; } \
+ ^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
- TP_fast_assign(
- ^~
+ TP_fast_assign(
+ ^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
- TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
- TP_ARGS(tx, dirty, min_tx_time),
- TP_STRUCT__entry(
- __field(uint64_t, tx_txg)
- __field(uint64_t, tx_lastsnap_txg)
- __field(uint64_t, tx_lasttried_txg)
- __field(boolean_t, tx_anyobj)
- __field(boolean_t, tx_dirty_delayed)
- __field(hrtime_t, tx_start)
- __field(boolean_t, tx_wait_dirty)
-
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
** Description changed: + [Impact] + + It is possible to trigger a NULL pointer dereference in tcindex_delete() + with a simple reproducer script, this is because in tcindex_set_parms() + when old_r doesn't exist we set the new exts to cr.exts that can be + uninitialized, triggering the NULL pointer dereference. + + In addition to that we may also hit a race condition in + tcindex_destroy() (as pointed out in the original bug report and also + here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10), that + is also fixed upstream, but it requires 4b79817f7add "net_sched: switch + to rcu_work". + + However adding these changes introduces three memory leak problems in + cls_tcindex (that can be easily verified using the same test case). + These leaks are also fixed upstream by 711ff09f3330 "net_sched: fix a + memory leak in cls_tcindex" and 000d2aeda70c "net_sched: fix two more + memory leaks in cls_tcindex", so we need to backport also these two + additional fixes. + + After all these fixes are applied the test case doesn't seem to trigger + any bug. + + [Test Case] + + #!/bin/sh -ex + + modprobe ifb + + while true; do + tc qdisc add dev ifb0 root handle 2:0 prio bands 5 + tc qdisc add dev ifb0 parent 2:5 sfq + tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex mask 0 classid 2:5 pass_on + tc qdisc del dev ifb0 root || true + done + + [Fix] + + * Fixes required to solve this problem: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2df8bee5654bb2b7312662ca6810d4dc16b0b67f + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8015d93ebd27484418d4952284fd02172fa4b0b2 + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=033b228e7f26b29ae37f8bfa1bc6b209a5365e9f + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1db817e75f5b9387b8db11e37d5f0624eb9223e0 + + [Regression Potential] + + * All upstream fixes, tested on the affected platform, backport changes + are minimal. + + [Original bug report] + I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. -- 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/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Bug description: [Impact] It is possible to trigger a NULL pointer dereference in tcindex_delete() with a simple reproducer script, this is because in tcindex_set_parms() when old_r doesn't exist we set the new exts to cr.exts that can be uninitialized, triggering the NULL pointer dereference. In addition to that we may also hit a race condition in tcindex_destroy() (as pointed out in the original bug report and also here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10), that is also fixed upstream, but it requires 4b79817f7add "net_sched: switch to rcu_work". However adding these changes introduces three memory leak problems in cls_tcindex (that can be easily verified using the same test case). These leaks are also fixed upstream by 711ff09f3330 "net_sched: fix a memory leak in cls_tcindex" and 000d2aeda70c "net_sched: fix two more memory leaks in cls_tcindex", so we need to backport also these two additional fixes. After all these fixes are applied the test case doesn't seem to trigger any bug. [Test Case] #!/bin/sh -ex modprobe ifb while true; do tc qdisc add dev ifb0 root handle 2:0 prio bands 5 tc qdisc add dev ifb0 parent 2:5 sfq tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex mask 0 classid 2:5 pass_on tc qdisc del dev ifb0 root || true done [Fix] * Fixes required to solve this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2df8bee5654bb2b7312662ca6810d4dc16b0b67f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8015d93ebd27484418d4952284fd02172fa4b0b2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=033b228e7f26b29ae37f8bfa1bc6b209a5365e9f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1db817e75f5b9387b8db11e37d5f0624eb9223e0 [Reg
[Kernel-packages] [Bug 1829169] Re: linux-kvm: 5.0.0-1007.7 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 5.0.0-1007.7 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1829169 Title: linux-kvm: 5.0.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829173 phase: Ready for Packaging phase-changed: Wednesday, 15. May 2019 11:31 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829169/+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 1829184] Re: linux-kvm: 4.18.0-1013.13 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.18.0-1013.13 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1829184 Title: linux-kvm: 4.18.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829186 phase: Ready for Packaging phase-changed: Wednesday, 15. May 2019 13:33 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829184/+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 1829204] Re: linux-kvm: 4.15.0-1035.35 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.15.0-1035.35 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1829204 Title: linux-kvm: 4.15.0-1035.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829219 phase: Ready for Packaging phase-changed: Wednesday, 15. May 2019 15:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829204/+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 1829195] Re: linux-kvm: 4.4.0-1047.53 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.4.0-1047.53 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1829195 Title: linux-kvm: 4.4.0-1047.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 phase: Ready for Packaging phase-changed: Wednesday, 15. May 2019 14:03 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829195/+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 1829166] Re: linux-azure: 5.0.0-1007.7 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 5.0.0-1007.7 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829166 Title: linux-azure: 5.0.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829173 phase: Ready for Packaging phase-changed: Wednesday, 15. May 2019 11:31 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829166/+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 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
Hi Chris, just to make sure I understand (from a kernel perspective), can you confirm that `echo mem > /sys/power/state` is also fast at reaching the suspend state? In that case it would be interesting to check if there's a delay at detecting the state of the lid switch. For this, could you run the following command in a bash session: $ while :; do echo `date` - `cat /proc/acpi/button/lid/LID0/state`; sleep 1; done Close the lid, re-open it and you should notice something like this: Thu May 16 17:50:42 CEST 2019 - state: open Thu May 16 17:50:43 CEST 2019 - state: open Thu May 16 17:50:44 CEST 2019 - state: open Thu May 16 17:50:45 CEST 2019 - state: closed Thu May 16 17:50:46 CEST 2019 - state: closed Thu May 16 17:50:47 CEST 2019 - state: closed Thu May 16 17:50:48 CEST 2019 - state: open Thu May 16 17:50:49 CEST 2019 - state: open Thu May 16 17:50:50 CEST 2019 - state: open ^C Note that I have set the "lid close action" to do nothing, in this way we can better isolate the problem. 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Incomplete Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
@manjo can you confirm that the "integrity: Unable to open file" errors are not reported anymore with the fix applied? 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/1766201 Title: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The integrity subsystem is still reporting error messages like this at boot: integrity: Unable to open file: /etc/keys/x509_evm.der (-2) In a previous commit we have downgraded this error to warning: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master- next&id=58441dc86d7b066a2c02079829a96035587a7066 (this fix is applied everywhere, not only in bionic) But there's another place (security/integrity/digsig.c) that reports the same error message that should be also downgraded to warning for consistency. [Test Case] No special test case is required, errors are reported at boot if an integrity policy is enabled. [Fix] Downgrade also this error message to a warning. [Regression Potential] It is a one-liner that changes a printk() error message, regression potential is minimal. [Original bug report] == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.g
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
Fix against bionic submitted to the kernel ML: https://lists.ubuntu.com/archives/kernel-team/2019-May/100741.html -- 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/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Bug description: [Impact] It is possible to trigger a NULL pointer dereference in tcindex_delete() with a simple reproducer script, this is because in tcindex_set_parms() when old_r doesn't exist we set the new exts to cr.exts that can be uninitialized, triggering the NULL pointer dereference. In addition to that we may also hit a race condition in tcindex_destroy() (as pointed out in the original bug report and also here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10), that is also fixed upstream, but it requires 4b79817f7add "net_sched: switch to rcu_work". However adding these changes introduces three memory leak problems in cls_tcindex (that can be easily verified using the same test case). These leaks are also fixed upstream by 711ff09f3330 "net_sched: fix a memory leak in cls_tcindex" and 000d2aeda70c "net_sched: fix two more memory leaks in cls_tcindex", so we need to backport also these two additional fixes. After all these fixes are applied the test case doesn't seem to trigger any bug. [Test Case] #!/bin/sh -ex modprobe ifb while true; do tc qdisc add dev ifb0 root handle 2:0 prio bands 5 tc qdisc add dev ifb0 parent 2:5 sfq tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex mask 0 classid 2:5 pass_on tc qdisc del dev ifb0 root || true done [Fix] * Fixes required to solve this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2df8bee5654bb2b7312662ca6810d4dc16b0b67f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8015d93ebd27484418d4952284fd02172fa4b0b2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=033b228e7f26b29ae37f8bfa1bc6b209a5365e9f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1db817e75f5b9387b8db11e37d5f0624eb9223e0 [Regression Potential] * All upstream fixes, tested on the affected platform, backport changes are minimal. [Original bug report] I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+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 1819485] Re: AMD Rome : Additional patches
Hi Kim, I've applied the following patches to the bionic kernel (4.15): [from LP #1816669] 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode [from LP #1819485] 210ba1201ff9 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef2 x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baff x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc28 x86/MCE/AMD: Fix the thresholding machinery initialization order I haven't applied the following crypo patches yet (because they require additional backporting in bionic): dcbc0c6e4aa1 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512 crypto: ccp - Support register differences between PSP devices And here is a test kernel: https://kernel.ubuntu.com/~arighi/LP-1819485/ Could you test it and see if it's working as intented? 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/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+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 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
Alright, the fact that `echo mem > /sys/power/state` is fast means that the delay issue is not in the "suspend" path and we also know that it's not even in the detection path (/proc/acpi/button/lid/LID0/state). So the delay must be somewhere between the detection of the event and the delivery of the proper suspend action, that should be driven by systemd, more exactly systemd-logind. At this point I think it would interesting to take a look at journalctl, more exactly the timestamps and messages around a line like "systemd- logind[...]: Lid closed.". This should give us an idea how fast systemd detected the event and how fast it processed it. -- 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Incomplete Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1816669] Re: AMD Rome : Minimal support patches
*** This bug is a duplicate of bug 1819485 *** https://bugs.launchpad.net/bugs/1819485 ** This bug has been marked a duplicate of bug 1819485 AMD Rome : Additional patches -- 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/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Released Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+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 1819485] Re: x86: add support to AMD Rome CPU
** Summary changed: - AMD Rome : Additional patches + x86: add support to AMD Rome CPU -- 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/1819485 Title: x86: add support to AMD Rome CPU Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+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 1819485] Re: x86: add support to AMD Rome CPU
** Description changed: + [Impact] + + * Some upstream patches are missing to properly support the AMD Rome + architecture, without them the affected systems cannot work correctly. + + [Test Case] + + * No test case provided (tests have been made by the bug reporter using + the affected platform) + + [Fix] + + * The following commits are required to properly support this + architecture: + + 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum + e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register + 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode + 210ba1201ff9 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs + be3518a16ef2 x86/amd_nb: Add PCI device IDs for family 17h, model 30h + 556e4c62baff x86/amd_nb: Add support for newer PCI topologies + dedf7dce4cec hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs + 60c8144afc28 x86/MCE/AMD: Fix the thresholding machinery initialization order + + [Regression Potential] + + * All the patches have been applied upstream and they have been tested + on the newly supported platform with positive feedback. + + [Original bug report] + The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: - enp33s0f0 no wireless extensions. - - lono wireless extensions. - - enp33s0f1 no wireless extensions. + enp33s0f0 no wireless extensions. + + lono wireless extensions. + + enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: - linux-restricted-modules-4.18.0-15-generic N/A - linux-backports-modules-4.18.0-15-generic N/A - linux-firmware 1.173.3 + linux-restricted-modules-4.18.0-15-generic N/A + linux-backports-modules-4.18.0-15-generic N/A + linux-firmware 1.173.3 RfKill: - + Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1819485 Title: x86: add support to AMD Rome CPU Status in linux package in Ubuntu: Conf
[Kernel-packages] [Bug 1819485] Re: x86: add support for AMD Rome
** Summary changed: - x86: add support to AMD Rome CPU + x86: add support for AMD Rome -- 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/1819485 Title: x86: add support for AMD Rome Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * Some upstream patches are missing to properly support the AMD Rome architecture, without them the affected systems cannot work correctly. [Test Case] * No test case provided (tests have been made by the bug reporter using the affected platform) [Fix] * The following commits are required to properly support this architecture: 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode 210ba1201ff9 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef2 x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baff x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc28 x86/MCE/AMD: Fix the thresholding machinery initialization order [Regression Potential] * All the patches have been applied upstream and they have been tested on the newly supported platform with positive feedback. [Original bug report] The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+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 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
This patch seems to fix the problem for me. See also: https://lkml.org/lkml/2019/3/13/181 ** Patch added: "btrfs-raid56-properly-unmap-parity-page-in-finish_pa.patch" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812845/+attachment/5245817/+files/btrfs-raid56-properly-unmap-parity-page-in-finish_pa.patch -- 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/1812845 Title: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup. Please find the attachment for the complete log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 11:54 seq crw-rw 1 root audio 116, 33 Jan 22 11:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 11:54:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iw
[Kernel-packages] [Bug 1819699] Re: linux-kvm: 4.15.0-1031.31 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.15.0-1031.31 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1819699 Title: linux-kvm: 4.15.0-1031.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819716 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 11:05 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819699/+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 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.15.0-1041.45 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819713 Title: linux-azure: 4.15.0-1041.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Packaging phase-changed: Thursday, 14. March 2019 14:03 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+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 1819618] Re: linux-azure: 4.18.0-1014.14 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.18.0-1014.14 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819618 Title: linux-azure: 4.18.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819617 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1819624 phase: Ready for Packaging phase-changed: Wednesday, 13. March 2019 15:36 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819618/+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 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker
** Summary changed: - linux-oracle: -proposed tracker + linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1819703 Title: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1819704 phase: Ready for Packaging phase-changed: Monday, 18. March 2019 16:33 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819703/+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 1396654] Re: C++ demangling support missing from perf
Tested the following on bionic:
$ cat main.cpp
#include
#include
static __attribute__ ((noinline)) int my_really_big_function()
{
for(size_t i = 0; i < 1000; ++i)
{
benchmark::DoNotOptimize(i % 5);
}
return 0;
}
static __attribute__ ((noinline)) void caller1()
{
for(size_t i = 0; i < 1000; ++i)
{
benchmark::DoNotOptimize(my_really_big_function());
benchmark::DoNotOptimize(i % 5);
}
}
static __attribute__ ((noinline)) void myfun(benchmark::State& state)
{
while(state.KeepRunning())
{
caller1();
}
}
BENCHMARK(myfun);
BENCHMARK_MAIN();
$ clang++ main.cpp -o main -fno-omit-frame-pointer -O0 -lpthread
-lbenchmark
$ perf record -g ./main
$ perf report -g 'graph,0.5,caller'
Result:
- with linux-tools-common 4.15.0-46.49:
Samples: 3K of event 'cpu-clock', Event count (approx.): 75725
Children Self Command Shared Object Symbol
+ 99.67% 0.00% main libbenchmark.so.1.3.0 [.] 0x00015b58
+ 99.67% 0.00% main main [.]
_ZL5myfunRN9benchmark5StateE
+ 99.64% 0.17% main main [.] _ZL7caller1v
+ 99.50%99.47% main main [.]
_ZL22my_really_big_functionv
...
- with linux-tools-common 4.15.0-47.50 (from -proposed):
Samples: 3K of event 'cpu-clock', Event count (approx.): 75500
Children Self Command Shared Object Symbol
+ 99.77% 0.00% main libbenchmark.so.1.3.0 [.] 0x00015b58
+ 99.77% 0.00% main main [.] myfun
+ 99.70% 0.13% main main [.] caller1
+ 99.64%99.64% main main [.] my_really_big_function
...
This problem seems fixed now.
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
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/1396654
Title:
C++ demangling support missing from perf
Status in linux package in Ubuntu:
Triaged
Status in linux-hwe package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Status in linux-hwe source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Won't Fix
Status in linux source package in Zesty:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux-hwe source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux-hwe source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Triaged
Status in linux-hwe source package in Disco:
Confirmed
Bug description:
Hi,
It appears that C++ demangling support is missing from linux-tools-3.16.0-24,
on Utopic on arm64.
Could the following please be added to the build dependencies for that
package:
libiberty-dev
binutils-dev
Installing the above and rebuilding the package fixed the problem for
me.
Cheers,
--
Steve
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.7-0ubuntu8
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission
denied
DistroRelease: Ubuntu 14.10
IwConfig: Error: [Errno 2] No such file or directory
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: console=ttyS0,115200n8 ro
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
RfKill: Error: [Errno 2] No such file or directory
Tags: utopic utopic
Uname: Linux 3.16.0-24-generic aarch64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago)
UserGroups: sudo
WifiSyslog:
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+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 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
I have also been able to reproduce this bug with 4.18.0-10, 4.18.0-13, 4.18.0-14 and 4.18.0-16. So it doesn't seem to be a regression. -- 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: New Bug description: This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/0x2c0 Jan 25 00:00:37 onza kernel: [45283.058991] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 00:00:37 onza kernel: [45283.063849] ? ext4_readdir+0x9d4/0xb10 Jan 25 00:00:37 onza kernel: [45283.067854] ext4_readdir+0x6aa/0xb10 Jan 25 00:00:37 onza kernel: [45283.071687] ? _copy_to_user+0x21/0x30 Jan 25 00:00:37 onza kernel: [45283.075597] ? do_statfs64+0x34/0x60 Jan 25 00:00:37 onza kernel: [45283.079334] ? security_file_permission+0x7c/0xb0 Jan 25 00:00:37 onza kernel: [45283.084306] iterate_dir+0x15c/0x1a0 Jan 25 00:00:37 onza kernel: [45283.087883] ksys_getdents64+0x6f/0x110 Jan 25 00:00:37 onza kernel: [45283.091853] ? iterate_dir+0x1a0/0x1a0 Jan 25 00:00:37 onza kernel: [45283.095771] sys_getdents64+0x16/0x20 Jan 25 00:00:37 onza kernel: [45283.099595] do_fast_syscall_32+0x7f/0x1e0 Jan 25 00:00:37 onza kernel: [45283.103858] entry_SYSENTER_32+0x4e/0x7c Jan 25 00:00:37 onza kernel: [45283.107938] EIP: 0xb7ef4d41 Jan 25 00:00:37 onza k
[Kernel-packages] [Bug 1820275] Re: btrfs-kernel oops from btrfs subvolume delete command
According to the trace reported in syslog the problem happened in btrfs_get_or_create_delayed_node(), specifically the faulty function was prefetch_freepointer() defined in mm/slub.c. Considering that btrfs_get_or_create_delayed_node() is allocating a "node" object using kmem_cache_zalloc() from a local kmem_cache pool called "delayed_node_cache", I would say that most likely that pool was corrupted due to a bug in btrfs (because only btrfs is using that pool). If I understand correctly this problem can be reproduced fairly easily (it's happening every few days running a specific test suite). It would be interesting to understand if it is a regression or not. Do you know if the problem started to happen recently from a specific kernel version? Have you tried to run the same test suite on an older kernel? Ideally if we can find a "good" kernel and a "bad" kernel we could try to bisect the problem. -- 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/1820275 Title: btrfs-kernel oops from btrfs subvolume delete command Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: This report show a kernel oops in the btrfs lugin , happened every few days when running a test suite on a test system. It looks like their systemd/Journal failed to kick off a dump immediately following the panic. The exploiter is using the kernel 4.15.0-42 We're not sure it's the btrfs subvolume delete that's causing it yet Following infos are attached: - syslog - sosreport - kdump output here : https://ibm.ent.box.com/folder/70219521934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1820275/+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 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
I did more tests with this, it looks like the problem is hidden somewhere in openvswitch. The specific test case that seems to trigger the bug 100% of the time is the one attached, but it requires to change the time immediately before running it (for example using date --set "23:57:00", as suggested before). An interesting thing that I've tried is to always return an error from ovs_vport_alloc(), this obviously prevents openvswitch from working, but with this change applied I wasn't able to trigger the bug. This requires more investigation, but it looks like somewhere in the openvswitch is corrupting some allocated memory, triggering the kernel bug from other random places. ** Attachment added: "openvswitch test case to trigger this bug" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+attachment/5249516/+files/lp1262692 -- 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/0x2c0 Jan 25 00:00:37 onza kernel: [45283.058991] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 00:00:37 onza kernel: [45283.063849] ? ext4_readdir+0x9d4/0xb10 Jan 25 00:00:37 onza kernel: [45283.067854] ext4_readdir+0x6aa/0xb10 Jan 25 00:00:37 onza kernel: [45
[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
About the first two errors ("Unable to open file ... x509_ima.der") they should
be downgraded to warnings and this was previously addressed here:
https://lists.ubuntu.com/archives/kernel-team/2017-February/082526.html
Apparently this patch didn't get merged. I think we can easily apply
this one.
About the other errors (synthetic uevent) it looks like a userspace
daemon/program is sending incorrect data via sysfs (this could be caused
by an old deprecated udev setting, or something else). Are they
happening once at boot, for example when a particular device is detected
/ registered in the system, or they are reported periodically also when
the system is running?
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/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg
error Checking for all LINUX clients for devops4p10
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Application Cdeadmin -
2018-04-20 05:56:03 ==
== Comment: #1 - Application Cdeadmin - 2018-04-20
05:56:05 ==
State: Open by: stccdenv on 18 April 2018 06:27:28
This defect was opened automatically using defect_template with only
logs. Please refer to 2nd seq for the problem description.
==Automatic entries==
Full Log:
http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138
Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy
Adams(tnad...@us.ibm.com)
Backup: Atit Patel (a...@us.ibm.com)
System Name: devops4fp1
FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com)
System Firmware Level:
Current Side Driver:.fips861/b0413a_1816.861
Non-Current Side Driver:.fips861/b0410a_1816.861
Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab
password. (The Lab Test Passwords are now accessible only through the auto or
manual install web apps. For example, from the manual install web app, enter
your email address, check the Lab Passwords checkbox and then click on Submit.)
(To access the Lpars in 10.33.x.x network, login to any LCB or HMC then
ssh/telnet to 10.33.x.x lpars)
---
HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com)
HMC Version:
"version= Version: 9
Release: 1
Service Pack: 910
HMC Build level 1803052221
","base_version=V9R1
"
---
=Logs
SNAP :
devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149
/tmp/IBM.DRM.180418060149.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02
/tmp/htx.180418060149.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02
devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149
/tmp/IBM.DRM.180418060149.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03
/tmp/htx.180418060149.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03
devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148
/tmp/IBM.DRM.180418060148.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04
/tmp/htx.180418060148.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04
devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148
/tmp/IBM.DRM.180418060148.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05
/tmp/htx.180418060148.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05
devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz
/tmp/var_log.180418060149.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz
/var/log/nts_linux-hjmh_180418_0703.tbz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/nts_linux-hjmh_180418_0703.tbz
/tmp/IBM.DRM.180418060149.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p06
/tmp/htx.180418060149.tar.gz and also @
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p06
devops4p07: /tmp/ctsupt/ctsnap.devops4p07
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
With this patch applied I can't reproduce the problem anymore. See also: https://lkml.org/lkml/2019/3/27/1762 ** Patch added: "openvswitch: fix flow actions reallocation" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+attachment/5249928/+files/0001-openvswitch-fix-flow-actions-reallocation.patch -- 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/0x2c0 Jan 25 00:00:37 onza kernel: [45283.058991] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 00:00:37 onza kernel: [45283.063849] ? ext4_readdir+0x9d4/0xb10 Jan 25 00:00:37 onza kernel: [45283.067854] ext4_readdir+0x6aa/0xb10 Jan 25 00:00:37 onza kernel: [45283.071687] ? _copy_to_user+0x21/0x30 Jan 25 00:00:37 onza kernel: [45283.075597] ? do_statfs64+0x34/0x60 Jan 25 00:00:37 onza kernel: [45283.079334] ? security_file_permission+0x7c/0xb0 Jan 25 00:00:37 onza kernel: [45283.084306] iterate_dir+0x15c/0x1a0 Jan 25 00:00:37 onza kernel: [45283.087883] ksys_getdents64+0x6f/0x110 Jan 25 00:00:37 onza kernel: [45283.091853] ? iterate_dir+0x1a0/0x1a0 Jan 25 00:00:37 onza kernel: [45283.095771] sys_getdents64+0x16/0x20 Jan 25 00:00:37 onza kernel: [45283.099595] do_
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
New patch after the review from the LKML. ** Patch added: "openvswitch: fix flow actions reallocation - v2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+attachment/5250007/+files/0001-openvswitch-fix-flow-actions-reallocation.patch -- 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/0x2c0 Jan 25 00:00:37 onza kernel: [45283.058991] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 00:00:37 onza kernel: [45283.063849] ? ext4_readdir+0x9d4/0xb10 Jan 25 00:00:37 onza kernel: [45283.067854] ext4_readdir+0x6aa/0xb10 Jan 25 00:00:37 onza kernel: [45283.071687] ? _copy_to_user+0x21/0x30 Jan 25 00:00:37 onza kernel: [45283.075597] ? do_statfs64+0x34/0x60 Jan 25 00:00:37 onza kernel: [45283.079334] ? security_file_permission+0x7c/0xb0 Jan 25 00:00:37 onza kernel: [45283.084306] iterate_dir+0x15c/0x1a0 Jan 25 00:00:37 onza kernel: [45283.087883] ksys_getdents64+0x6f/0x110 Jan 25 00:00:37 onza kernel: [45283.091853] ? iterate_dir+0x1a0/0x1a0 Jan 25 00:00:37 onza kernel: [45283.095771] sys_getdents64+0x16/0x20 Jan 25 00:00:37 onza kernel: [45283.099595] do_fast_syscall_32+0x7f/0x1e0 Jan 25 00:00:37 onza kernel: [4528
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
** Description changed: + SRU Justification: + + [Impact] + + * Parity page in btrfs raid56 is incorrectly unmapped, allowing to + easily trigger a reference counter bug on i386 causing a kernel panic + + * The fix unmaps the right rbio pages and adds the proper kunmap() call + for the parity page + + [Test Case] + + * create a raid5 btrfs filesystem: +# mkfs.btrfs -m raid5 -d raid5 /dev/sdb /dev/sdc /dev/sdd /dev/sde + + * mount it: +# mount /dev/sdb /mnt + + * run btrfs scrub in a loop: +# while :; do btrfs scrub start -BR /mnt; done + + [Regression Potential] + + * This is an upstream fix, regression potential is minimal. + + [Original bug report] + This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: - btrfs scrub start -BR $MNT + btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: - [ 494.357824] [ cut here ] - [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! - [ 494.365079] invalid opcode: [#1] SMP - [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi - [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu - [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 - [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] - [ 494.453657] EIP: kunmap_high+0xaa/0xb0 - [ 494.457571] EFLAGS: 00010246 CPU: 2 - [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: - [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 - [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 - [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 - [ 494.486353] Call Trace: - [ 494.488967] kunmap+0x3e/0x50 - [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] - [ 494.497226] ? update_load_avg+0x64f/0x830 - [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] - [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] - [ 494.513058] bio_endio+0xb9/0x110 - [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] - [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] - [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] - [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] - [ 494.536621] process_one_work+0x1b9/0x3d0 - [ 494.540799] worker_thread+0x37/0x420 - [ 494.544628] kthread+0xf0/0x110 - [ 494.547931] ? process_one_work+0x3d0/0x3d0 - [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 - [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 - [ 494.562701] ret_from_fork+0x2e/0x38 - [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef - [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 - [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- + [ 494.357824] [ cut here ] + [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! + [ 494.365079] invalid opcode: [#1] SMP + [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi + [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu + [ 494.438618] Hardware n
[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386
** Description changed: SRU Justification: [Impact] - * Parity page in btrfs raid56 is incorrectly unmapped, allowing to + * Parity page in btrfs raid56 is incorrectly unmapped, allowing to easily trigger a reference counter bug on i386 causing a kernel panic - * The fix unmaps the right rbio pages and adds the proper kunmap() call + * The fix unmaps the right rbio pages and adds the proper kunmap() call for the parity page [Test Case] - * create a raid5 btrfs filesystem: -# mkfs.btrfs -m raid5 -d raid5 /dev/sdb /dev/sdc /dev/sdd /dev/sde + * create a raid5 btrfs filesystem: + # mkfs.btrfs -m raid5 -d raid5 /dev/sdb /dev/sdc /dev/sdd /dev/sde - * mount it: -# mount /dev/sdb /mnt + * mount it: + # mount /dev/sdb /mnt - * run btrfs scrub in a loop: -# while :; do btrfs scrub start -BR /mnt; done + * run btrfs scrub in a loop: + # while :; do btrfs scrub start -BR /mnt; done + + [Fix] + + * + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3897b6f0a859288c22fb793fad11ec2327e60fcd + + kunmap(p_page) was completely left out, so we never + did an unmap for the p_page and the loop unmapping the rbio page was + iterating over the wrong number of stripes: unmapping should be done + with nr_data instead of rbio->real_stripes. [Regression Potential] - * This is an upstream fix, regression potential is minimal. + * This is an upstream fix, tested on the affected platform. The bug is + affecting only btrfs raid5/6 users on architectures where kunamp() is + not a no-op (like i386). It is also a very small patch, so backport + changes are minimal. [Original bug report] This issue was not spotted on AMD64 Reproduce rate: 100% The following command is the key to trigger this: btrfs scrub start -BR $MNT Steps: # (Install necessary packages) # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests # TMP=/tmp/tmp MNT=/tmp/mnt # mkdir -p $TMP; mkdir -p $MNT # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh Trace: [ 494.357824] [ cut here ] [ 494.357828] kernel BUG at /build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350! [ 494.365079] invalid opcode: [#1] SMP [ 494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas pata_acpi wmi [ 494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 4.15.0-43-generic #46-Ubuntu [ 494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 [ 494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] [ 494.453657] EIP: kunmap_high+0xaa/0xb0 [ 494.457571] EFLAGS: 00010246 CPU: 2 [ 494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: [ 494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40 [ 494.474264] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0 [ 494.486353] Call Trace: [ 494.488967] kunmap+0x3e/0x50 [ 494.492140] finish_parity_scrub+0x24d/0x570 [btrfs] [ 494.497226] ? update_load_avg+0x64f/0x830 [ 494.501528] validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs] [ 494.507527] raid56_parity_scrub_end_io+0x53/0x70 [btrfs] [ 494.513058] bio_endio+0xb9/0x110 [ 494.516574] ? end_workqueue_fn+0x2c/0x40 [btrfs] [ 494.521435] end_workqueue_fn+0x33/0x40 [btrfs] [ 494.526139] normal_work_helper+0x7d/0x2f0 [btrfs] [ 494.531087] btrfs_endio_raid56_helper+0x10/0x20 [btrfs] [ 494.536621] process_one_work+0x1b9/0x3d0 [ 494.540799] worker_thread+0x37/0x420 [ 494.544628] kthread+0xf0/0x110 [ 494.547931] ? process_one_work+0x3d0/0x3d0 [ 494.552282] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.557488] ? kthread_create_worker_on_cpu+0x20/0x20 [ 494.562701] ret_from_fork+0x2e/0x38 [ 494.566441] Code: 2d ee ff 58 8b 5d fc c9 c3 90 8d b4 26 00 00 00 00 a1 80 d1 c4 cf 31 c9 3d 80 d1 c4 cf 0f 95 c1 eb bc 8d b4 26 00 00 00 00 0f 0b <0f> 0b 8d 74 26 00 66 66 66 66 90 55 89 e5 56 53 31 db e8 1f ef [ 494.585751] EIP: kunmap_high+0xaa/0xb0 SS:ESP: 0068:f4883e40 [ 494.591688] ---[ end trace 5e6d708abb85eeba ]--- Follow up with CPU soft lockup
[Kernel-packages] [Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
*** This bug is a duplicate of bug 1766201 *** https://bugs.launchpad.net/bugs/1766201 The following patch should be applied to downgrade the "integrity: Unable to open file:" errors: https://lists.ubuntu.com/archives/kernel-team/2017-February/082526.html, as addressed in the duplicate bug #1766201. ** This bug has been marked a duplicate of bug 1766201 CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 -- 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/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771555/+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 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
** Description changed: + SRU Justification: + + [Impact] + + * Flow action buffer can be incorrectly resized to contain the newly + added action entries: the buffer is always resized multiplying the + previous size by 2, but this might be not enough if the requested size + is bigger than previous_size*2, causing a buffer overflow + + * The fix correctly resizes the buffer to prevent the buffer overflow + + * Despite the subject this bug can be triggered potentially on any + architecture, but it is very likely to happen on i386 running the + following test case + + [Test Case] + + * run this openvswitch test case: + https://launchpadlibrarian.net/416589265/lp1262692 + + [Fix] + + * Instead of resizing the buffer by a factor of 2, use max(current_size + * 2, current_size + requested_size) + + [Regression Potential] + + * Fix has been tested on the affected platform and verified using + slub_debug. The patch has been queued up for -stable by David Miller, it + will be included upstream for the next merge window. It is also a very + small patch (a one-liner basically), so backport changes are minimal. + + [Original bug report] + This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 - Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = + Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 - Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 + Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/
[Kernel-packages] [Bug 1831103] [NEW] bionic: netlink: potential shift overflow in netlink_bind()
Public bug reported: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. ** Affects: linux (Ubuntu) Importance: High Assignee: Andrea Righi (arighi) Status: New ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Andrea Righi (arighi) Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1831103 Title: bionic: netlink: potential shift overflow in netlink_bind() Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831103/+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 1831103] Re: bionic: netlink: potential shift overflow in netlink_bind()
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) 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/1831103 Title: bionic: netlink: potential shift overflow in netlink_bind() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831103/+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 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)
Considering that only one of the two fixes mentioned in comment #11 are applied to the bionic kernel, I've uploaded a new test kernel here https://kernel.ubuntu.com/~arighi/LP-1752002/ with both fixes applied. It would be great if someone could test this kernel to confirm that the problem is actually solved. 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/1752002 Title: [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Shriya R. Kulkarni - 2018-02-02 01:21:36 == Problem Description : = Warn on message is seen while running perf fuzzer tests. Machine details : == Hardware : Witherspoon (wsp12) + DD2.1 OS : Ubuntu 1804 uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 ) Steps to reproduce : Build Kernel : To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 #! /bin/bash set -x git clone https://github.com/deater/perf_event_tests.git cd perf_event_tests/include mkdir asm cd asm wget http://9.114.13.132/repo/shriya/perf_regs.h cd ../../lib make sleep 10 cd ../fuzzer make sleep 10 echo 0 > /proc/sys/kernel/nmi_watchdog echo 2 > /proc/sys/kernel/perf_event_paranoid echo 10 > /proc/sys/kernel/perf_event_max_sample_rate ./perf_fuzzer -r 1492143527 Call trace : === [ 329.228031] [ cut here ] [ 329.228039] WARNING: CPU: 43 PID: 9088 at /home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 perf_pmu_sched_task+0x170/0x180 [ 329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc [ 329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 4.13.0-32-generic #35~lp1746225 [ 329.228070] task: c03f776ac900 task.stack: c03f77728000 [ 329.228071] NIP: c0299b70 LR: c02a4534 CTR: c029bb80 [ 329.228073] REGS: c03f7772b760 TRAP: 0700 Not tainted (4.13.0-32-generic) [ 329.228073] MSR: 9282b033 [ 329.228079] CR: 24008822 XER: [ 329.228080] CFAR: c0299a70 SOFTE: 0 GPR00: c02a4534 c03f7772b9e0 c1606200 c03fef858908 GPR04: c03f776ac900 0001 003fee73 GPR08: c11220d8 0002 GPR12: c029bb80 c7a3d900 GPR16: GPR20: c03f776ad090 c0c71354 GPR24: c03fef716780 003fee73 c03fe69d4200 c03f776ad330 GPR28: c11220d8 0001 c14c6108 c03fef858900 [ 329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180 [ 329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230 [ 329.228101] Call Trace: [ 329.228102] [c03f7772b9e0] [c02a0678] perf_iterate_sb+0x158/0x2a0 (unreliable) [ 329.228105] [c03f7772ba30] [c02a4534] __perf_event_task_sched_in+0xc4/0x230 [ 329.228107] [c03f7772bab0] [c01396dc] finish_task_switch+0x21c/0x310 [ 329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80 [ 329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0 [ 329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0 [ 329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0 [ 329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0 [ 329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c [ 329.228121] Instruction dump: [ 329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 38210050 [ 329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 6000 6042 [ 329.228131] ---[ end trace 8c46856d314c1811 ]--- [ 375.755943] hrtimer: interrupt took 31601 ns == Comment: #4 - SEET
[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
Thanks Chris, looking at journalct it seems that from the "Lid closed" event and "Reached target Sleep" there's just 1s. So, the time between these two events is also definitely fast, therefore the bottleneck is not in the part of systemd that processes the "lid closed" event. At this point I'm wondering if the bottleneck is in the part of systemd that detects the "lid closed" event. For that we should run the same loop in a bash session (while :; do echo `date` - `cat /proc/acpi/button/lid/LID0/state`; sleep 1; done), close the lid and compare the timestamps of the transition between "open" and "closed" (in the bash session) with the timestamp of the "Lid closed" event in journalctl. If they don't match the bottleneck is in systemd not being able to detect the lid closed event fast enough. Moreover, in the last comment (#10) you mentioned that things have been improved. Do you have some numbers (i.e., how many second it needs to actually go to sleep) or is it just a feeling? 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/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Incomplete Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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
