[Kernel-packages] [Bug 1691481] [NEW] package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes
Public bug reported: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 12 14:10:01 2017 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2016-06-20 (331 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: Upgraded to xenial on 2016-09-13 (245 days ago) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1691481 Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in bcmwl package in Ubuntu: New Bug description: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 12 14:10:01 2017 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2016-06-20 (331 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: Upgraded to xenial on 2016-09-13 (245 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1691481/+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 1290110] Re: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others]
Hi, installed Ubuntu 14.10 on my HP Probook 4525s and when resume from suspend fan work slowly. Normally laptop work at 53/55 C. But after resume from suspend temperature go to 60/70 C. -- 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/1290110 Title: Fan stops after resume from suspend leading to overheating; requires reboot to fix [HP Probook 4710s and many others] Status in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Bug description: After resume from suspend, the fan (there is only one) first speeds up to about a normal speed and then slows down in a couple of seconds to a complete stop. It doesn't spin up again even if the temperatures shoot way up (monitoring using indicator-sensors or lm-sensors, both use acpitz info). There are 2 ways to get the fan spinning again: - reboot the system - echo 1 > /sys/class/thermal/cooling_device[4|12...don't remember which]/curr_state This is happening on a clean install of Trusty from daily build that also has the updates-proposed source enabled. Previously the laptop ran 13.10 and suspend and resume worked fine. Only thing is, I also updated the BIOS during formatting for Trusty, which could cause this issue but I'm leaning more towards an ACPI issue (the latest BIOS is from 2010 and someone would have probably noticed a problem with the fan?) Attached is the output from cd /sys/class/thermal && grep . */* 2&>/dev/null after first boot and after resume suspend; as can be seen, after resume all fan states are 0 whereas on boot some are also 1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 [modified: boot/vmlinuz-3.13.0-16-generic] ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jernej 2582 F pulseaudio /dev/snd/controlC0: jernej 2582 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 78.199783] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 104.824460] audit_printk_skb: 147 callbacks suppressed [ 104.824464] type=1400 audit(1394393526.590:61): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1986 comm="apparmor_parser" [ 104.824472] type=1400 audit(1394393526.590:62): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1986 comm="apparmor_parser" [ 104.824884] type=1400 audit(1394393526.590:63): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1986 comm="apparmor_parser" Date: Sun Mar 9 20:46:48 2014 HibernationDevice: RESUME=UUID=79b35f90-100a-4582-9b65-a84fbedf5bf7 InstallationDate: Installed on 2014-03-08 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308) MachineType: Hewlett-Packard HP ProBook 4710s ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic root=UUID=9561bd56-ffa3-4f61-91cf-019c359ed8e8 ro quiet splash radeon.dpm=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3074 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU9465LRD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4710s:pvrF.18:rvnHewlett-Packard:rn3074:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4710s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1290110/+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 2098724] Re: Missing package linux-signatures-nvidia-6.11.0-18-generic
Same here :( Operating System: Kubuntu 24.10 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 Kernel Version: 6.11.0-18-generic (64-bit) Graphics Platform: X11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2098724 Title: Missing package linux-signatures-nvidia-6.11.0-18-generic Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: The latest update to linux-modules-nvidia-560-generic fails to install due to the dependency on linux-signatures-nvidia-6.11.0-18-generic (via linux-modules-nvidia-560-6.11.0-18-generic), which does not exist in the repositories. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-modules-nvidia-560-6.11.0-18-generic (not installed) ProcVersionSignature: Ubuntu 6.11.0-14.15-generic 6.11.0 Uname: Linux 6.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Feb 17 23:18:34 2025 InstallationDate: Installed on 2025-01-23 (25 days ago) InstallationMedia: Kubuntu 24.10 "Oracular Oriole" - Release amd64 (20241007.6) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-restricted-modules UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2098724/+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 2098724] Re: Missing package linux-signatures-nvidia-6.11.0-18-generic
Missing package released (linux-signatures-nvidia-6.11.0-18), so I upgraded and solved it for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2098724 Title: Missing package linux-signatures-nvidia-6.11.0-18-generic Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: The latest update to linux-modules-nvidia-560-generic fails to install due to the dependency on linux-signatures-nvidia-6.11.0-18-generic (via linux-modules-nvidia-560-6.11.0-18-generic), which does not exist in the repositories. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-modules-nvidia-560-6.11.0-18-generic (not installed) ProcVersionSignature: Ubuntu 6.11.0-14.15-generic 6.11.0 Uname: Linux 6.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Feb 17 23:18:34 2025 InstallationDate: Installed on 2025-01-23 (25 days ago) InstallationMedia: Kubuntu 24.10 "Oracular Oriole" - Release amd64 (20241007.6) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-restricted-modules UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2098724/+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 1155845] Re: Targus Bluetooth 4.0 USB adapter using Broadcom BCM20702A0 not supported, sort of, needs firmware. Kernel regression maybe?
*** This bug is a duplicate of bug 1242079 *** https://bugs.launchpad.net/bugs/1242079 ** This bug has been marked a duplicate of bug 1242079 13.10 Bluetooth: can't load firmware, may not work correctly -- 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/1155845 Title: Targus Bluetooth 4.0 USB adapter using Broadcom BCM20702A0 not supported, sort of, needs firmware. Kernel regression maybe? Status in “linux” package in Ubuntu: Expired Bug description: As you can see the Broadcom BCM20702A0 chipset is reconized but the firmware is missing. I have seen other bug reports that say the firmware issues is fixed in the 3.2 kernel and I have the 3.5 kernel. Retail product name is Targus Bluetooth 4.0 Dual -Mode Micro USB Adapter. See these bug reports which say the problem is fixed, but not for me. Is this a regression in the kernel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863051 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400 usb 5-2: new full-speed USB device number 2 using uhci_hcd usb 5-2: New USB device found, idVendor=0a5c, idProduct=21e8 usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 5-2: Product: BCM20702A0 usb 5-2: Manufacturer: Broadcom Corp usb 5-2: SerialNumber: 00190E117807 usbcore: registered new interface driver btusb Bluetooth: can't load firmware, may not work correctly ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1 ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 2567 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf6ff8000 irq 43' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,103c2a69,00100101' Controls : 49 Simple ctrls : 21 Date: Fri Mar 15 18:13:17 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8b753f77-dad9-4ad3-a1c3-c497f2ae9c6b InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP-Pavilion KT608AV-ABA d5000t MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-25-generic root=/dev/mapper/pluto-charon ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-25-generic N/A linux-backports-modules-3.5.0-25-generic N/A linux-firmware1.79.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.21 dmi.board.name: Burbank dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.21:bd12/17/2008:svnHP-Pavilion:pnKT608AV-ABAd5000t:pvr:rvnPEGATRONCORPORATION:rnBurbank:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KT608AV-ABA d5000t dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1155845/+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 1242079] Re: 13.10 Bluetooth: can't load firmware, may not work correctly
I'm affected too. This is my "dmesg" log: [ 6511.928736] usb 3-2: new full-speed USB device number 13 using xhci_hcd [ 6511.948071] usb 3-2: New USB device found, idVendor=0a5c, idProduct=21e8 [ 6511.948083] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 6511.948089] usb 3-2: Product: BCM20702A0 [ 6511.948094] usb 3-2: Manufacturer: Broadcom Corp [ 6511.948098] usb 3-2: SerialNumber: 00190E124F47 [ 6511.952833] Bluetooth: can't load firmware, may not work correctly "sudo rfkill unblock bluetooth" did nothing for me. I also reinstalled "gnome-bluetooth" and nothing happened. Bug is still marked as "Incomplete" but no more info is requested and still remains "Unassigned". I own a Targus USB dongle and I found this bug marked as "Expired": https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1155845 I marked it as a Duplicate of this current bug (not branded). As you can see in the other bug comments, bluetooth worked in previous kernel versions (3.9.0-030900rc3-generic). Something went wrong with ubuntu 13.11. Thank you in advance and, please, request more info in order to help to solve the problem. ** 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/1242079 Title: 13.10 Bluetooth: can't load firmware, may not work correctly Status in “linux” package in Ubuntu: Confirmed Bug description: Bluetooth does not work on Thinkpad E135 (Broadcom) dmesg|grep -i bluetooth gives ... Bluetooth: can't load firmware, may not work correctly This was also a problem on 13.04 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=98833f0e-41cc-46c9-81a3-9b7cc9e45c3a InstallationDate: Installed on 2013-06-12 (129 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 335963G MarkForUpload: True NonfreeKernelModules: wl fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=2f4442d5-4677-47b6-9a14-b62928d2c161 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-19 (1 days ago) UserGroups: dmi.bios.date: 12/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: HMET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 335963G 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHMET90WW(2.50):bd12/26/2012:svnLENOVO:pn335963G:pvrThinkPadEdgeE135:rvnLENOVO:rn335963G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 335963G dmi.product.version: ThinkPad Edge E135 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242079/+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 1242079] Re: 13.10 Bluetooth: can't load firmware, may not work correctly
Sorry, there is more info: juanca@mobility:~$ uname -r 3.11.0-18-generic juanca@mobility:~$ lsusb | grep -i bluetooth Bus 003 Device 013: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 -- 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/1242079 Title: 13.10 Bluetooth: can't load firmware, may not work correctly Status in “linux” package in Ubuntu: Confirmed Bug description: Bluetooth does not work on Thinkpad E135 (Broadcom) dmesg|grep -i bluetooth gives ... Bluetooth: can't load firmware, may not work correctly This was also a problem on 13.04 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=98833f0e-41cc-46c9-81a3-9b7cc9e45c3a InstallationDate: Installed on 2013-06-12 (129 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 335963G MarkForUpload: True NonfreeKernelModules: wl fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=2f4442d5-4677-47b6-9a14-b62928d2c161 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-19 (1 days ago) UserGroups: dmi.bios.date: 12/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: HMET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 335963G 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHMET90WW(2.50):bd12/26/2012:svnLENOVO:pn335963G:pvrThinkPadEdgeE135:rvnLENOVO:rn335963G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 335963G dmi.product.version: ThinkPad Edge E135 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242079/+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 1595969] [NEW] Suspend doesn't work in ACER laptop
Public bug reported: I bought this laptop three years ago. Used Kubuntu 14.04 and 15.04 without **any** problem. A couple of weeks ago I installed Kubuntu 16.04 as always (formatting /root partition and doing a fresh install, not an upgrade). Since then both suspend and hibernation hang the laptop: the screen goes black, the laptop seems to stop but it won't. After a couple of minutes the fan can be heard and there is no way to restart linux. I have to power off the laptop (the hard way) and then turn it on. I have followed some threads and it seems that this is a common bug (it happens in several different hardware configurations). The original 4.4.0-22-generic kernel has been updated to versions 23 and 24 (current) but no way. The bug is still present. Thanks a lot in advance! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jcamen 1409 F pulseaudio /dev/snd/controlC0: jcamen 1409 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 24 16:07:20 2016 HibernationDevice: RESUME=UUID=17e78447-07a8-4fbb-9f86-955840d83074 InstallationDate: Installed on 2016-06-06 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire V5-552G ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=92ac6050-61ef-4135-b375-623a96d7f33d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd08/28/2013:svnAcer:pnAspireV5-552G:pvrV2.04:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-552G dmi.product.version: V2.04 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1595969 Title: Suspend doesn't work in ACER laptop Status in linux package in Ubuntu: New Bug description: I bought this laptop three years ago. Used Kubuntu 14.04 and 15.04 without **any** problem. A couple of weeks ago I installed Kubuntu 16.04 as always (formatting /root partition and doing a fresh install, not an upgrade). Since then both suspend and hibernation hang the laptop: the screen goes black, the laptop seems to stop but it won't. After a couple of minutes the fan can be heard and there is no way to restart linux. I have to power off the laptop (the hard way) and then turn it on. I have followed some threads and it seems that this is a common bug (it happens in several different hardware configurations). The original 4.4.0-22-generic kernel has been updated to versions 23 and 24 (current) but no way. The bug is still present. Thanks a lot in advance! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jcamen 1409 F pulseaudio /dev/snd/controlC0: jcamen 1409 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 24 16:07:20 2016 HibernationDevice: RESUME=UUID=17e78447-07a8-4fbb-9f86-955840d83074 InstallationDate: Installed on 2016-06-06 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire V5-552G ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=92ac6050-61ef-4135-b375-623a96d7f33d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.ven
[Kernel-packages] [Bug 1595969] Re: Suspend doesn't work in ACER laptop
I think this bug is closely related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302 and, more recent: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589139 -- 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/1595969 Title: Suspend doesn't work in ACER laptop Status in linux package in Ubuntu: New Bug description: I bought this laptop three years ago. Used Kubuntu 14.04 and 15.04 without **any** problem. A couple of weeks ago I installed Kubuntu 16.04 as always (formatting /root partition and doing a fresh install, not an upgrade). Since then both suspend and hibernation hang the laptop: the screen goes black, the laptop seems to stop but it won't. After a couple of minutes the fan can be heard and there is no way to restart linux. I have to power off the laptop (the hard way) and then turn it on. I have followed some threads and it seems that this is a common bug (it happens in several different hardware configurations). The original 4.4.0-22-generic kernel has been updated to versions 23 and 24 (current) but no way. The bug is still present. Thanks a lot in advance! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jcamen 1409 F pulseaudio /dev/snd/controlC0: jcamen 1409 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 24 16:07:20 2016 HibernationDevice: RESUME=UUID=17e78447-07a8-4fbb-9f86-955840d83074 InstallationDate: Installed on 2016-06-06 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire V5-552G ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=92ac6050-61ef-4135-b375-623a96d7f33d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd08/28/2013:svnAcer:pnAspireV5-552G:pvrV2.04:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-552G dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595969/+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 1595969] Re: Suspend doesn't work in ACER laptop
I have installed kernel v4.7-rc4-yakkety as requested (packages linux- image-generic, linux-headers-generic, both amd64, and linux-headers, all). I have rebooted with this kernel and I have suspended two times the laptop (one from the KDE menu and the other one just closing the lid). Both times suspend worked OK. Everything was fine. Finally, I have hibernated the laptop and... everything was right again! The laptop halted and resumed OK. I will use this kernel version until the bug has been solved in mainstream kernel. I proceed to mark this bug as requested. Thanks a lot! -- 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/1595969 Title: Suspend doesn't work in ACER laptop Status in linux package in Ubuntu: Incomplete Bug description: I bought this laptop three years ago. Used Kubuntu 14.04 and 15.04 without **any** problem. A couple of weeks ago I installed Kubuntu 16.04 as always (formatting /root partition and doing a fresh install, not an upgrade). Since then both suspend and hibernation hang the laptop: the screen goes black, the laptop seems to stop but it won't. After a couple of minutes the fan can be heard and there is no way to restart linux. I have to power off the laptop (the hard way) and then turn it on. I have followed some threads and it seems that this is a common bug (it happens in several different hardware configurations). The original 4.4.0-22-generic kernel has been updated to versions 23 and 24 (current) but no way. The bug is still present. Thanks a lot in advance! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jcamen 1409 F pulseaudio /dev/snd/controlC0: jcamen 1409 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 24 16:07:20 2016 HibernationDevice: RESUME=UUID=17e78447-07a8-4fbb-9f86-955840d83074 InstallationDate: Installed on 2016-06-06 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire V5-552G ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=92ac6050-61ef-4135-b375-623a96d7f33d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd08/28/2013:svnAcer:pnAspireV5-552G:pvrV2.04:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-552G dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595969/+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 1595969] Re: Suspend doesn't work in ACER laptop
** Tags added: confirmed kernel-fixed-upstream ** Description changed: I bought this laptop three years ago. Used Kubuntu 14.04 and 15.04 without **any** problem. A couple of weeks ago I installed Kubuntu 16.04 as always (formatting /root partition and doing a fresh install, not an upgrade). Since then both suspend and hibernation hang the laptop: the screen goes black, the laptop seems to stop but it won't. After a couple of minutes the fan can be heard and there is no way to restart linux. I have to power off the laptop (the hard way) and then turn it on. I have followed some threads and it seems that this is a common bug (it happens in several different hardware configurations). The original 4.4.0-22-generic kernel has been updated to versions 23 and 24 (current) but no way. The bug is still present. Thanks a lot in advance! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jcamen 1409 F pulseaudio - /dev/snd/controlC0: jcamen 1409 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: jcamen 1409 F pulseaudio + /dev/snd/controlC0: jcamen 1409 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 24 16:07:20 2016 HibernationDevice: RESUME=UUID=17e78447-07a8-4fbb-9f86-955840d83074 InstallationDate: Installed on 2016-06-06 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire V5-552G ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=92ac6050-61ef-4135-b375-623a96d7f33d ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-24-generic N/A - linux-backports-modules-4.4.0-24-generic N/A - linux-firmware1.157.1 + linux-restricted-modules-4.4.0-24-generic N/A + linux-backports-modules-4.4.0-24-generic N/A + linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd08/28/2013:svnAcer:pnAspireV5-552G:pvrV2.04:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-552G dmi.product.version: V2.04 dmi.sys.vendor: Acer -- 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/1595969 Title: Suspend doesn't work in ACER laptop Status in linux package in Ubuntu: Incomplete Bug description: I bought this laptop three years ago. Used Kubuntu 14.04 and 15.04 without **any** problem. A couple of weeks ago I installed Kubuntu 16.04 as always (formatting /root partition and doing a fresh install, not an upgrade). Since then both suspend and hibernation hang the laptop: the screen goes black, the laptop seems to stop but it won't. After a couple of minutes the fan can be heard and there is no way to restart linux. I have to power off the laptop (the hard way) and then turn it on. I have followed some threads and it seems that this is a common bug (it happens in several different hardware configurations). The original 4.4.0-22-generic kernel has been updated to versions 23 and 24 (current) but no way. The bug is still present. Thanks a lot in advance! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jcamen 1409 F pulseaudio /dev/snd/controlC0: jcamen 1409 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 24 16:07:20 2016 HibernationDevice: RESUME=UUID=17e78447-07a8-4fbb-9f86-955840d83074 InstallationDate: Installed on 2016-06-06 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire V5-552G ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=92ac6050-61ef-4135-b375-623a96d7f33d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backp
[Kernel-packages] [Bug 1595969] Re: Suspend doesn't work in ACER laptop
Dear Christopher, I've been out on holiday since the beginning of the month (without the laptop). I came back yesterday, so now I've been able to test the kernel. Good news: when I turned on the laptop, a huge update was waiting for me, including a new kernel version, 4.4.0-31. I have booted with this version of the kernel, so as to test both suspend and hibernate and... everything was OK! I have successfully suspended seven times the laptop. Hibernation also works OK (tested two times). Therefore, I think that this bug can be closed because kernel version 4.4.0-31 seems to solve it. I apologize for the inconveniences. Thanks a lot for your time and efforts. Let me know if I have to do something else. -- 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/1595969 Title: Suspend doesn't work in ACER laptop Status in linux package in Ubuntu: Incomplete Bug description: I bought this laptop three years ago. Used Kubuntu 14.04 and 15.04 without **any** problem. A couple of weeks ago I installed Kubuntu 16.04 as always (formatting /root partition and doing a fresh install, not an upgrade). Since then both suspend and hibernation hang the laptop: the screen goes black, the laptop seems to stop but it won't. After a couple of minutes the fan can be heard and there is no way to restart linux. I have to power off the laptop (the hard way) and then turn it on. I have followed some threads and it seems that this is a common bug (it happens in several different hardware configurations). The original 4.4.0-22-generic kernel has been updated to versions 23 and 24 (current) but no way. The bug is still present. Thanks a lot in advance! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jcamen 1409 F pulseaudio /dev/snd/controlC0: jcamen 1409 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 24 16:07:20 2016 HibernationDevice: RESUME=UUID=17e78447-07a8-4fbb-9f86-955840d83074 InstallationDate: Installed on 2016-06-06 (18 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire V5-552G ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=92ac6050-61ef-4135-b375-623a96d7f33d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware1.157.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Dazzle_RL dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd08/28/2013:svnAcer:pnAspireV5-552G:pvrV2.04:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-552G dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595969/+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 1852479] Re: laptop crashed all of a sudden
*** This bug is a duplicate of bug 1746340 *** https://bugs.launchpad.net/bugs/1746340 here a bit of my cat /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash modprobe.blacklist=nouveau nvme_core.default_ps_max_latency_us=5500 pcie_aspm=off" GRUB_CMDLINE_LINUX="nouveau.modeset=0" For me pcie_aspm=off was the parameter that helped solve the issue. for more info +see here: https://wiki.archlinux.org/index.php/Solid_state_drive/NVMe +and here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340#yui_3_10_3_1_1590400769591_1615 -- 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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
an update on this: it was actually pcie_aspm=off what helped to solve the problem. I think the problem is related to the power management of PCIe ports. Without pcie_aspm=off I started seeing errors like the following ones: - [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=7841 end=7842) time 291 us, min 1063, max 1079, scanline start 1044, end 1092 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 I think the bug is not with the nvme controller but somewhere in ASPM. But I am not a kernel developer. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
No I have a laptop from a XMG, it is a German brand. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=0ca062da-7e8f-425a-88b
[Kernel-packages] [Bug 1852479] [NEW] laptop crashed all of a sudden
Public bug reported: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Error of this Agent is reported first nvme :03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) nvme :03:00.0: AER: device [144d:a808] error status/mask=0001/e000 nvme
[Kernel-packages] [Bug 1852479] Re: laptop crashed all of a sudden
apport information ** Tags added: apport-collected eoan ** Description changed: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Error of this Agent is reported first
[Kernel-packages] [Bug 1852479] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305213/+files/AudioDevicesInUse.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error rece
[Kernel-packages] [Bug 1852479] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305214/+files/CRDA.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pciep
[Kernel-packages] [Bug 1852479] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305218/+files/Lsusb.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pci
[Kernel-packages] [Bug 1852479] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305216/+files/IwConfig.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0
[Kernel-packages] [Bug 1852479] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305217/+files/Lspci.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pci
[Kernel-packages] [Bug 1852479] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305219/+files/ProcCpuinfo.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :0
[Kernel-packages] [Bug 1852479] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305215/+files/CurrentDmesg.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received:
[Kernel-packages] [Bug 1852479] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305224/+files/PulseList.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d
[Kernel-packages] [Bug 1852479] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305225/+files/RfKill.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 p
[Kernel-packages] [Bug 1852479] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305220/+files/ProcCpuinfoMinimal.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error re
[Kernel-packages] [Bug 1852479] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305223/+files/ProcModules.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :0
[Kernel-packages] [Bug 1852479] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305221/+files/ProcEnviron.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :0
[Kernel-packages] [Bug 1852479] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305227/+files/WifiSyslog.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr p
[Kernel-packages] [Bug 1852479] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305226/+files/UdevDb.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 p
[Kernel-packages] [Bug 1852479] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1852479/+attachment/5305222/+files/ProcInterrupts.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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received:
[Kernel-packages] [Bug 1852479] Re: laptop crashed all of a sudden
*** This bug is a duplicate of bug 1746340 *** https://bugs.launchpad.net/bugs/1746340 after digging a bit I am pretty sure that the problem is similar to this one: https://bugzilla.kernel.org/show_bug.cgi?id=195039 I have also a Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983. It just dies very randomly. Any updates from the kernel? ** Bug watch added: Linux Kernel Bug Tracker #195039 https://bugzilla.kernel.org/show_bug.cgi?id=195039 -- 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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 p
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I have exactly the same drive: /dev/nvme0n1 S444NY0K600040 SAMSUNG MZVLB256HAHQ-0 1 81.09 GB / 256.06 GB512 B + 0 B EXD7101Q and exactly the same problem. I filled a bug before deactivating AER (pci=noaer) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852479 -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu
[Kernel-packages] [Bug 1852479] Re: laptop crashed all of a sudden
*** This bug is a duplicate of bug 1746340 *** https://bugs.launchpad.net/bugs/1746340 ** This bug has been marked a duplicate of bug 1746340 Samsung SSD corruption (fsck needed) -- 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/1852479 Title: laptop crashed all of a sudden Status in linux package in Ubuntu: Confirmed Bug description: My laptop just crashed spectacularly two times. I was using chrome both times but I am not sure if that is related. There was no possibility of rescuing the system whatsoever. I just dug into the logs. probably related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 kernel log: rfkill: input handler disabled pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Multiple Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: can't find device of ID00e8 pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) pcieport :00:1d.0: AER: device [8086:a330] error status/mask=0001/2000 pcieport :00:1d.0: AER:[ 0] RxErr pcieport :00:1d.0: AER:
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
For anyone struggling with this hideous bug, try the following: add "nvme_core.default_ps_max_latency_us=250" in /etc/default/grub, for example: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off nvme_core.default_ps_max_latency_us=250" then run "update-grub" My laptop has been running smoothly for a week now. (/dev/nvme0n1 S444NY0K600040 SAMSUNG MZVLB256HAHQ-0 1 81.09 GB / 256.06 GB 512 B + 0 B EXD7101Q) see more infos here: https://wiki.archlinux.org/index.php/Solid_state_drive/NVMe @kernel developers, would it not be great to detect such disks and lower automatically the nvme_core.default_ps_max_latency_us? Thi bug is really hard to detect and solve because there are NO logs whatsoever. Disk goes read-only ya know? -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi try: cat /sys/module/nvme_core/parameters/default_ps_max_latency_us sudo nvme get-feature -f 0x0c -H /dev/nvme0 please read carefully the link provided. the info is there. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) Pro
[Kernel-packages] [Bug 1844928] [NEW] i2c_hid blocks waking up
Public bug reported: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "hardware info" https://bugs.launchpad.net/bugs/1844928/+attachment/5290399/+files/hardinfo_report.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: New Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] Re: i2c_hid blocks waking up
apport information ** Tags added: apport-collected disco ** Description changed: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 - after adding i2c_hid to the /etc/suspend-modules.conf the problems was - solved. + after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: jccb 1835 F pulseaudio + /dev/snd/controlC0: jccb 1835 F pulseaudio + CurrentDesktop: pop:GNOME + DistroRelease: Pop!_OS 19.04 + MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-27-generic N/A + linux-backports-modules-5.0.0-27-generic N/A + linux-firmware1.178.3 + Tags: disco + Uname: Linux 5.0.0-27-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) + UserGroups: adm sudo + _MarkForUpload: True + dmi.bios.date: 11/29/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: N.1.09 + dmi.board.asset.tag: Standard + dmi.board.name: GK5CN6Z + dmi.board.vendor: SchenkerTechnologiesGmbH + dmi.board.version: Standard + dmi.chassis.asset.tag: Standard + dmi.chassis.type: 10 + dmi.chassis.vendor: SchenkerTechnologiesGmbH + dmi.chassis.version: Standard + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: + dmi.product.family: CFL + dmi.product.name: XMG NEO 15 - XNE15M18 + dmi.product.sku: XNE15M18 + dmi.product.version: Standard + dmi.sys.vendor: SchenkerTechnologiesGmbH ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290452/+files/AlsaInfo.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.pr
[Kernel-packages] [Bug 1844928] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290461/+files/ProcInterrupts.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290463/+files/PulseList.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290460/+files/ProcEnviron.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290456/+files/Lspci.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290465/+files/UdevDb.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290457/+files/Lsusb.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290462/+files/ProcModules.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290455/+files/IwConfig.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290464/+files/RfKill.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290454/+files/CurrentDmesg.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290459/+files/ProcCpuinfoMinimal.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290453/+files/CRDA.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290458/+files/ProcCpuinfo.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1844928/+attachment/5290466/+files/WifiSyslog.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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 1844928] Re: i2c_hid blocks waking up
can you ellaborate more? where should I apply it? -and how? I'm glad to try 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/1844928 Title: i2c_hid blocks waking up Status in linux package in Ubuntu: Confirmed Bug description: i2c_hid blocks the system from waking up after sleep mode. I experienced random wake up problems. System will hang and show some errors. For example: "bios contains wgds but no wrds" solution was provided by: https://gist.github.com/mauron85/f764c88d2dc47af157487a7a318dd35b https://bbs.archlinux.org/viewtopic.php?id=243878 after adding i2c_hid to the /etc/suspend-modules.conf the problems was solved. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jccb 1835 F pulseaudio /dev/snd/controlC0: jccb 1835 F pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 19.04 MachineType: SchenkerTechnologiesGmbH XMG NEO 15 - XNE15M18 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=ce33b159-ce12-4227-92f3-3ea93527e6d4 ro nouveau.modeset=0 quiet splash modprobe.blacklist=nouveau vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-19 (33 days ago) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 11/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.09 dmi.board.asset.tag: Standard dmi.board.name: GK5CN6Z dmi.board.vendor: SchenkerTechnologiesGmbH dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.09:bd11/29/2018:svnSchenkerTechnologiesGmbH:pnXMGNEO15-XNE15M18:pvrStandard:rvnSchenkerTechnologiesGmbH:rnGK5CN6Z:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard: dmi.product.family: CFL dmi.product.name: XMG NEO 15 - XNE15M18 dmi.product.sku: XNE15M18 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844928/+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 659434] Re: Font/image corruption after resume from hibernate
this is still happening... I experience screen tearing and corruption only after resume -- 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/659434 Title: Font/image corruption after resume from hibernate Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xorg Since updating to Maverick I've noticed that the display becomes somewhat corrupted after resuming from hibernate on my laptop. It looks like the X server's cached images have become corrupt (guess!). It starts out small, but after a few cycles text becomes totally unreadable. * It's mostly text which is corrupt, and each instance of the same character looks similarly garbled * All applications are affected - eg terminal, Firefox, chromium, apport-gtk, the GNOME menus * Changing the font (eg by changing to "Monochrome" from "Best shapes" in the Appearance Settings->Font makes many things look better, but revert to being unreadable after switching back * Changing the font size in the application (terminal, Firefox) also temporarily fixes the issue * Some images in Firefox also become garbled, but recover after a forced reload. I can confirm that the issue still happens with the mainline kernel (linux-image-3.4.0-999-generic_3.4.0-999.201204170501_amd64.deb). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 edid-base64: AP///wBMozM2AAAPAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZDwAAACOHAmQC/gBTQU1TVU5HCiAgICAg/gBMVE4xNTRYMy1MMDYKAHA= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Tue Oct 12 19:52:02 2010 MachineType: LENOVO 0769BMG ProcCmdLine: root=UUID=1fdf1f18-3ca9-447c-a9b5-9b40d4c276bd ro resume=/dev/sda4 resume2=/dev/sda4 quiet splash ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 04/16/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET35WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET35WW:bd04/16/2008:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 0769BMG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-22-generic [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:383e] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659434/+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
