[Kernel-packages] [Bug 1744791] Comment bridged from LTC Bugzilla
--- Comment From abdha...@in.ibm.com 2018-02-19 02:22 EDT--- I am looking for debug symbols package linux-image-4.15.0-generic-dbgsym Any link where I can get the packages for bionic kernel ? -- 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/1744791 Title: [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in repo which is required for crash analysis of vmcore Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Bug description: ---Problem Description--- No debug kernel deb packages available for 4.13.0-25-generic kernel [Ubuntu 18.04 ] Unable to analyze vmcore generated via crash. ---uname output--- Linux spoon2 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8335-GTC ---Steps to Reproduce--- Install 18.04 ppc64el upgrade kernel to 4.13.0-25-generic or 4.13.0-17-generic try configuring debug repo https://wiki.ubuntu.com/Kernel/CrashdumpRecipe http://ddebs.ubuntu.com/pool/main/l/linux/ sudo tee /etc/apt/sources.list.d/ddebs.list << EOF deb http://ddebs.ubuntu.com/ $(lsb_release -cs) main restricted universe multiverse deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates main restricted universe multiverse deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted universe multiverse EOF sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ECDCAD72428D7C01 sudo apt-get update sudo apt-get install linux-image-$(uname -r)-dbgsym Warning /!\ Be aware that those packages are huge! (~600 MB) When installed, the debug kernel can be found under /usr/lib/debug/boot/ and crash is started by: crash Crash command to analyze vmcore will not work as kernel debuginfo deb package is not found in repo . root@spoon2:~# sudo apt-get install linux-image-$(uname -r)-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-image-4.13.0-25-generic-dbgsym E: Couldn't find any package by glob 'linux-image-4.13.0-25-generic-dbgsym' E: Couldn't find any package by regex 'linux-image-4.13.0-25-generic-dbgsym' root@spoon2:~# I was also not able to find this debug symbol for 18.04 kernel. I understand that the current 18.04 kernel is old and was removed from the archive. Is it correct? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744791/+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 1746340] Re: Samsung SSD corruption (fsck needed)
Build a Debian/Ubuntu kernel: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel#Building_the_kernel Kernel source: http://kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/ http://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/ -- 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
[Kernel-packages] [Bug 1750308] Re: FAIL: test_one_adapter (__main__.TestBlueZ5)
Oh. Maybe this is a bluez regression. It looks like the shell code has been rewritten and that's what is not working. Sometimes the test commands from python-dbusmock don't get through. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1750308 Title: FAIL: test_one_adapter (__main__.TestBlueZ5) Status in bluez package in Ubuntu: In Progress Status in python-dbusmock package in Ubuntu: In Progress Bug description: When bluez 5.48 is installed, we see this failure: == FAIL: test_one_adapter (__main__.TestBlueZ5) -- Traceback (most recent call last): File "test_bluez5.py", line 128, in test_one_adapter self.assertIn('Controller ' + address, out) AssertionError: 'Controller 00:01:02:03:04:05' not found in ['Waiting to connect to bluetoothd...', '[\x1b[0;92mNEW\x1b[0m] Controller 00:01:02:03:04:05 my-computer [default]', '[SIGNAL] org.freedesktop.DBus.Mock.MethodCalled', 'Agent registered', 'Controller 00:01:02:03:04:05 my-computer [default]', 'Agent unregistered', '[\x1b[0;91mDEL\x1b[0m] Controller 00:01:02:03:04:05 my-computer [default]'] -- However the failure only occurs in the Ubuntu package of python- dbusmock. It does not occur with the upstream git repo (run as 'tests /run-ubuntu-chroot'). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python-dbusmock 0.17-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Feb 19 11:42:48 2018 InstallationDate: Installed on 2017-12-12 (68 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) PackageArchitecture: all SourcePackage: python-dbusmock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1750308/+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 1750317] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1750317 Title: PGD 0 Status in linux package in Ubuntu: Confirmed Bug description: nuc7i7bnh there is an interaction between wifi and bluetooth. changing wifi locks up bluetooth ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1933 F pulseaudio steve 2319 F pulseaudio Date: Sun Feb 18 22:39:03 2018 Failure: oops InstallationDate: Installed on 2018-02-18 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) MachineType: Intel Corporation NUC7i7BNH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=f0fb1895-b2be-48ca-8c8d-fbba5791ebcb ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: PGD 0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0052.2017.0918.1346 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0052.2017.0918.1346:bd09/18/2017:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750317/+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 1750317] [NEW] PGD 0
Public bug reported: nuc7i7bnh there is an interaction between wifi and bluetooth. changing wifi locks up bluetooth ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1933 F pulseaudio steve 2319 F pulseaudio Date: Sun Feb 18 22:39:03 2018 Failure: oops InstallationDate: Installed on 2018-02-18 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) MachineType: Intel Corporation NUC7i7BNH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=f0fb1895-b2be-48ca-8c8d-fbba5791ebcb ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: PGD 0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0052.2017.0918.1346 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0052.2017.0918.1346:bd09/18/2017:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops bionic kernel-oops -- 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/1750317 Title: PGD 0 Status in linux package in Ubuntu: New Bug description: nuc7i7bnh there is an interaction between wifi and bluetooth. changing wifi locks up bluetooth ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1933 F pulseaudio steve 2319 F pulseaudio Date: Sun Feb 18 22:39:03 2018 Failure: oops InstallationDate: Installed on 2018-02-18 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) MachineType: Intel Corporation NUC7i7BNH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=f0fb1895-b2be-48ca-8c8d-fbba5791ebcb ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: PGD 0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0052.2017.0918.1346 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0052.2017.0918.1346:bd09/18/2017:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750317/+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 1739214] Re: System Freeze
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1739214 Title: System Freeze Status in linux package in Ubuntu: Expired Bug description: Happens several times a day ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toyo 2006 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 19 15:36:24 2017 InstallationDate: Installed on 2017-12-15 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Inspiron 7460 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1243e99e-928a-47b1-b203-799869a12e72 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 09WC1G dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd02/14/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7460 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739214/+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 1739386] Re: [xhci_hcd] HC died · USB controller died, reboot necessary
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1739386 Title: [xhci_hcd] HC died · USB controller died, reboot necessary Status in linux package in Ubuntu: Expired Bug description: * Ubuntu release: 17.04 * uname -r: 4.10.0-42-generic * Expected behaviour: the USB ports run well * What happens: the USB ports are randomly killed from time to time * Explanation: The xhci_hcd driver reports that the xHCI host is not responding to a stop endpoint command. The USB host controller is then shut down and all USB ports are left dead until a reboot is performed. This is not immediate nor predictable --- sometimes, it can be days before it happens; sometimes it is just hours. If I understood correctly, there is no way to reload the kernel module of the USB driver, because it is baked into the kernel at compile time. Something like that? :) When rebooting, the shutdown process completes (it reports a "shutdown target achieved" or similar), but is unable to unmount the /home/user partition. Therefore, the system does not shutdown unless I press the power button (hard shutdown). I do not know if there is a way to get a TTY at that point to manually unmount the partition. The home folder is encrypted... I do not know if this has something to do with it, but this error only occurs when the USB HC is killed. I suspect the USB problem has to do with an external USB hub by TP- LINK. It seems to only fail when this device is connected. The hub model is UH400, by TP-LINK. Anything I can add, just ask for it! Thanks a lot! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739386/+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 1739080] Re: package linux-headers-4.13.0-21 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-21/arch/blackfin/mach-bf548/include/mach/de
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1739080 Title: package linux-headers-4.13.0-21 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.13.0-21/arch/blackfin/mach-bf548/include/mach/defBF549.h .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: deja vu linux headers again. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-21 (not installed) ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doc2570 F pulseaudio /dev/snd/controlC1: doc2570 F pulseaudio Date: Tue Dec 19 10:14:14 2017 DpkgTerminalLog: Preparing to unpack .../0-linux-headers-4.13.0-21_4.13.0-21.24_all.deb ... Unpacking linux-headers-4.13.0-21 (4.13.0-21.24) ... dpkg: error processing archive /tmp/apt-dpkg-install-ozQSzM/0-linux-headers-4.13.0-21_4.13.0-21.24_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.13.0-21/arch/blackfin/mach-bf548/include/mach/defBF549.h.dpkg-new': Operation not permitted DuplicateSignature: package:linux-headers-4.13.0-21:(not installed) Unpacking linux-headers-4.13.0-21 (4.13.0-21.24) ... dpkg: error processing archive /tmp/apt-dpkg-install-ozQSzM/0-linux-headers-4.13.0-21_4.13.0-21.24_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.13.0-21/arch/blackfin/mach-bf548/include/mach/defBF549.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.13.0-21/arch/blackfin/mach-bf548/include/mach/defBF549.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072 InstallationDate: Installed on 2016-01-18 (700 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: EVGA 122-CK-NF68 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-headers-4.13.0-21 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-21/arch/blackfin/mach-bf548/include/mach/defBF549.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 122-CK-NF68 dmi.board.vendor: EVGA dmi.board.version: 2 dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 122-CK-NF68 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68: dmi.product.name: 122-CK-NF68 dmi.product.version: 2 dmi.sys.vendor: EVGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739080/+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 1737133] Re: package linux-image-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1737133 Title: package linux-image-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in linux package in Ubuntu: Expired Bug description: Installation of automatic update keeps to fail/hang. Manually executing the postinst script hangs here: $ sudo /usr/bin/perl /var/lib/dpkg/info/linux-image-4.13.0-19-generic.postinst configure Running depmod. update-initramfs: Generating /boot/initrd.img-4.13.0-19-generic initrd.img(/boot/initrd.img-4.13.0-19-generic ) points to /boot/initrd.img-4.13.0-19-generic (/boot/initrd.img-4.13.0-19-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-19-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.13.0-19-generic ) points to /boot/vmlinuz-4.13.0-19-generic (/boot/vmlinuz-4.13.0-19-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-19-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-19-generic /boot/vmlinuz-4.13.0-19-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-19-generic /boot/vmlinuz-4.13.0-19-generic Possibly a DKMS issue with nvidia drivers. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1825 F pulseaudio dave 4654 F pulseaudio Date: Fri Dec 8 10:50:41 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-11-10 (27 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO F0C20011MZ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=67079586-555b-453d-915b-90fed825fefd ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: O29KT21AUS dmi.board.name: 3647 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259605522151 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO29KT21AUS:bd06/30/2017:svnLENOVO:pnF0C20011MZ:pvrideacentreAIO910-27ISH:rvnLENOVO:rn3647:rvrSDK0J40709WIN3259605522151:cvnLENOVO:ct13:cvrNone: dmi.product.family: ideacentre AIO 910-27ISH dmi.product.name: F0C20011MZ dmi.product.version: ideacentre AIO 910-27ISH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737133/+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 1746340] Re: Samsung SSD corruption (fsck needed)
I compiled a kernel myself apllying the patcch and using make deb-pkg and got these files: linux-headers-4.15.4_4.15.4-4_amd64.deb linux-image-4.15.4_4.15.4-4_amd64.deb linux-image-4.15.4-dbg_4.15.4-4_amd64.deb linux-libc-dev_4.15.4-4_amd64.deb but you don't have image...dbg neither libc, and you have image-extra and headers...generic. What's the difference? Will mine work? If not, how do I get your 4 files exactly? -- 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
[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
Thanks for those files. They seem to confirm that the kernel change in comment #16 is the cause of the regression. So the kernel is basically doing the right thing in trying to support all screen types. Only your screen contains inadequate firmware to be able to tell the kernel what it really is. So the solution is probably to detect your particular screen model and apply a workaround just for that model (equivalent to ASUS providing a custom display driver in Windows). It is unfortunate (for you) that hardly anyone else will experience this bug. Even on other 6-bit panels, many people won't have a problem (and I have tried on a few systems). So you're just a bit unlucky with this particular LCD panel. But it sounds like a fix is now coming :) -- 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/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: Incomplete Bug description: - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1502238] Re: bridge does not forward neighbor solicitation packets
I also suffer from this issue for a long time. All my computers work fine, however my Ubuntu homeserver running virtual machines have problems when I try to connect to them over IPv6 locally. They work at first and then suddenly it stops working due to the neighbour advertisement not reaching my router. I can see the advertisement is being send on the actual host or vm's, but that packet is not visible on the router or the clients. So this is a bug in the bridge I guess? I really need a fix for this, can someone explain the workaround for me? Also, why is this bug not updated anymore? Was it fixed, or not reproducable? -- 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/1502238 Title: bridge does not forward neighbor solicitation packets Status in linux package in Ubuntu: Expired Bug description: 3 hosts involved here: kailan is connected to a cisco switch, which is also connected to kurrat (eth3), which is running a bridge with tigernut connected to eth1. kurrat's controllers are 06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection, using the e1000e driver (3.13.0-65-generic kernel) (while kailan is doing a ping6 2601:282:8100:3500:82ee:73ff:fe99:368d): +kurrat 324 : sudo tcpdump -eni eth3 ip6 and not tcp and not udp tcpdump: WARNING: eth3: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth3, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:16.080888 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:16.431484 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:17.077446 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:18.077457 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:19.095034 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:20.093436 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.093425 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.43 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:22.111042 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 ^C 10 packets captured 11 packets received by filter 0 packets dropped by kernel +kurrat 325 : sudo tcpdump -eni eth1 ip6 and not tcp and not udp tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:28.201110 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:31.552677 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:38.103919 08:10:78:fc:b3:d2 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 90: fe80::a10:78ff:fefc:b3d2 > ff02::1: HBH ICMP6, multicast listener query v2 [gaddr ::], length 28 10:39:39.663357 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 ^C 4 packets captured 4 packets received by filter 0 packets dropped by kernel 1 packet dropped by interface +kurrat 326 : uname -a Linux kurrat 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Adding a host route for the 2001:: IP via the link IP on kailan works as a workaround, but the neighbor solicitiation packets are clearly not
[Kernel-packages] [Bug 1746970] Re: lpfc.ko module doesn't work
I can also confirm that the Kernel posted in #20 resolves the issue with my Emulex Zephyr-X FC adapter. -- 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/1746970 Title: lpfc.ko module doesn't work Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == The bug reporter stated that the HBA Emulex LPe12000 Fibre channel adapter does not see the disk on direct attach. Broadcom support confirmed that bug and suggested to update module. It was found that commit 2877cbf is the fix for this bug. Commit 2877cbf is in mainline as of v4.14-rc1. == Fix == commit 2877cbffb79ed121a6bcc5edbe629d3aba36cd29 Author: Dick KennedyDate: Wed Aug 23 16:55:31 2017 -0700 scsi: lpfc: Fix loop mode target discovery == Regression Potential == Low. Clean cherry pick and only adds a new check for loop mode. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == Hi. I have problem with HBA Emulex LPe12000 Fibre channel adapter. It doesn't see disk on direct attach. [4.015493] lpfc :04:00.0: 0:1303 Link Up Event x1 received Data: x1 x1 x10 x2 x0 x0 0 [4.015570] lpfc :04:00.0: 0:1309 Link Up Event npiv not supported in loop topology [4.016671] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 TMO:x0 Data x1000 x0 [4.017627] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 TMO:x0 Data x1000 x0 [4.018561] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 TMO:x0 Data x1000 x0 [4.018636] lpfc :04:00.0: 0:(0):0100 FLOGI failure Status:x3/x18 TMO:x0 [4.019713] lpfc :04:00.0: 0:(0):0266 Issue NameServer Req x117 err 1 Data: x8 x0 I have made a little investigation. Ubuntu 16.04.3 LTS, kernel 4.10.0-28, lpfc 11.2.0.2 - no problem. Ubuntu 17.10.1, kernel 4.13.0-21, lpfc 11.4.0.1 - problem. Debian 9.3, kernel 4.9.0-4, lpfc 11.2.0.0 - no problem. Fedora 27, kernel 4.13.9-300, lpfc 11.4.0.1 - problem. Proxmox 5.0, kernel 4.10.15-1, lpfc 11.2.0.2 - no problem. Proxmox 5.1, kernel 4.13.13-5, lpfc 11.4.0.1 - problem. Another user with this problem said that if fiber switch is added between the server and the storage it's working as expected. I think problem is in lpfc.ko 11.4.0.1. Any kernel (4.13 now) that has this module version is affected. Broadcom support confirmed that bug and suggested to update module. But Broadcom supports only RHEL and SLES. I tried to compile, but no luck. Please, could you update lpfc.ko module in linux-image-generic package? There are version 11.4.142.21 for SLES 12 and 11.4.204.11 for RHEL 6 and 7 on Broadcom site. Thanks. --- 04:00.0 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] (rev 03) Subsystem: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: lpfc --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.387 DistroRelease: Ubuntu 17.10 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP ProLiant DL160 G6 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=ru keyboard-configuration/layoutcode?=ru ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 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-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: Tags: artful Uname: Linux 4.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/19/2010 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd05/19/2010:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
[Kernel-packages] [Bug 1748678] Re: Intel graphics timeout, possibly caused wifi network to fail
Further, I've managed to cause two system lock-ups, which I do not have logs for because the lock-ups were so severe that the logging system didn't record the kernel logs before death. I therefore cannot attribute those two lockups to this issue for now. I've set-up netconsole now to try to gather logs from these lock-ups so that I can definitively attribute or rule them out. -- 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/1748678 Title: Intel graphics timeout, possibly caused wifi network to fail Status in linux package in Ubuntu: Confirmed Bug description: My wifi network device stopped responding, unable to list any local wifi networks, which required turning off the adapter in settings and back-on again. while investigating I found the following in the dmesg output from the time the network device stopped responding. This is the only relevant message in recent history so I'm working on the assumption that somehow the intel gfx timeout knocked-onto the wifi device or the pci bus. === lcpsi of wifi card === 03:00.0 Network controller: Broadcom Limited BCM4331 802.11a/b/g/n (rev 02) Subsystem: Apple Inc. AirPort Extreme Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: wl Kernel modules: bcma, wl === lspci of gfx === 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 === relevant dmesg output === [ 7450.338278] pipe A vblank wait timed out [ 7450.338321] [ cut here ] [ 7450.338380] WARNING: CPU: 2 PID: 29153 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 7450.338380] Modules linked in: rfcomm scsi_transport_iscsi binfmt_misc veth ebtable_filter ebtables ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_CHECKSUM xt_comment xt_tcpudp iptable_mangle unix_diag ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack libcrc32c l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox mmc_block cmac bnep joydev applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi snd_seq_midi_event snd_rawmidi bcm5974 kvm_intel [ 7450.338405] btusb btrtl uvcvideo btbcm btintel kvm bluetooth irqbypass videobuf2_vmalloc videobuf2_memops snd_seq ecdh_generic videobuf2_v4l2 videobuf2_core videodev intel_cstate intel_rapl_perf media wl(POE) input_leds snd_seq_device snd_timer mei_me lpc_ich cfg80211 mei snd soundcore thunderbolt sbs shpchp sbshc apple_gmux acpi_als kfifo_buf industrialio apple_bl mac_hid iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq algif_skcipher af_alg hid_generic hid_apple usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 sdhci_pci ahci aesni_intel libahci sdhci i2c_algo_bit aes_x86_64 drm_kms_helper crypto_simd glue_helper syscopyarea cryptd sysfillrect sysimgblt fb_sys_fops [ 7450.338442] drm video [ 7450.338445] CPU: 2 PID: 29153 Comm: kworker/u8:6 Tainted: P OE 4.13.0-32-generic #35-Ubuntu [ 7450.338446] Hardware name: Apple Inc. MacBookPro10,2/Mac-AFD8A9D944EA4843, BIOS MBP102.88Z.010B.B00.1708080805 08/08/2017 [ 7450.338478] Workqueue: events_unbound intel_atomic_commit_work [i915] [ 7450.338479] task: 9873194445c0 task.stack: b24909028000 [ 7450.338506] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 7450.338507] RSP: 0018:b2490902bd90 EFLAGS: 00010286 [ 7450.338508] RAX: 001c RBX: RCX: [ 7450.338509] RDX: RSI: 98732f316578 RDI: 98732f316578 [ 7450.338509] RBP: b2490902be48 R08: 0001 R09: 04b1 [ 7450.338510] R10: b2490902bd90 R11: R12: 00066ddd [ 7450.338511] R13: 98731ab2 R14: 98731a7ea000 R15: 0001 [ 7450.338512] FS: () GS:98732f30() knlGS: [
[Kernel-packages] [Bug 1713638] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: ‘struct net_device’ has no member named ‘last_rx’]
*** This bug is a duplicate of bug 1724863 *** https://bugs.launchpad.net/bugs/1724863 hello, this is my first bug report. i am also experiencing wifi issues. are patches overwritten manually or simply installed? thank you for providing solutions to this problem. -- 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/1713638 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: ‘struct net_device’ has no member named ‘last_rx’] Status in bcmwl package in Ubuntu: Confirmed Bug description: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 DKMSKernelVersion: 4.11.0-14-generic Date: Sun Aug 27 20:05:06 2017 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10: error: ‘struct net_device’ has no member named ‘last_rx’ InstallationDate: Installed on 2016-09-21 (342 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1713638/+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 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13
do you need other type of logs? -- 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/1745342 Title: touchscreen that worked in artful with 4.12 no longer works with 4.13 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: I have a Dell Venue 11 Pro 7139, and when I installed artful on it (before release) it worked fine. Recently (over the xmas break I think but I'm not sure; this is not a machine I intended to pay too much attention to) the kernel moved from 4.12 to 4.13, and the touchscreen has stopped working. I _think_ the last kernel to work was 4.12.0-13. I haven't done any sort of bisection though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1041 F pulseaudio /dev/snd/pcmC1D0p: john 1041 F...m pulseaudio /dev/snd/controlC1: john 1041 F pulseaudio Date: Thu Jan 25 10:18:51 2018 InstallationDate: Installed on 2017-07-10 (198 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709) MachineType: Dell Inc. Venue 11 Pro 7139 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0Y4RMT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7139 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+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 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic
I've been having this same issue on ubuntu mate 17.10 on a thinkpad T450s since kernel 4.13.0-25, and was booting with previous 4.13.0-21. Just tried #14 suggestion (adding noibpb) and it fixed it here. -- 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/1746418 Title: System freezes when starting Xorg after installing linux- image-4.13.0-32-generic Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only after installing the latest ubuntu kernel for 17.10, linux- image-4.13.0-32-generic. Am running Xorg instead of MIR due to MIR crashing when I initially upgraded from 17.04 to 17.10, but that's a different problem for a different day. It's been running with Xorg stably for at least 2-3 months. If I boot with the previous kernel version on my /boot (linux- image-4.13.0-25-generic), everything works fine. If I boot with the latest mainline kernel from the Ubuntu mainline repo (4.15.0), everything works. Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I am able to use the CLI and access the encrypted root filesystem, which is how I generated the apport repo that's attached. It's only when telling it to continue Normal booting that it freezes, which is why I suspect the problem of being Xorg. When the system freezes, the fan starts to spin up. I cannot switch virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed repeatedly doesn't do anything. To reboot, I have to hold the power button until the system powers off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746418/+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 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
@Kai-Heng Feng: Thanks for your fast reply! Does this mean, that UAS just will be disabled (slow disk) or is it like a fix? I will give it a try as soon as possible. Is there a kernel version for 16.04.3 LTS besides the mainline kernel? -- 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/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+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 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
This commit might help: commit 7fee72d5e8f1e7b8d8212e28291b1a0243ecf2f1 Author: Hans de GoedeDate: Tue Nov 14 19:27:22 2017 +0100 uas: Always apply US_FL_NO_ATA_1X quirk to Seagate devices Please try kernel version >= v4.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+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 1750245] [NEW] i915 kbl_guc_ver9_14.bin does not load
Public bug reported: The provided i915/kbl_guc_ver9_14.bin does not load when configured to do so . If the file is replaced by manually installing with the included script from 01.org, it loads properly: https://01.org/linuxgraphics/downloads/kabylake-guc-9.14 Before: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 After: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: SUCCESS load: SUCCESS version wanted: 9.14 version found: 9.14 header: offset is 0; size = 128 uCode: offset is 128; size = 142272 RSA: offset is 142400; size = 256 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1750245 Title: i915 kbl_guc_ver9_14.bin does not load Status in linux-firmware package in Ubuntu: New Bug description: The provided i915/kbl_guc_ver9_14.bin does not load when configured to do so . If the file is replaced by manually installing with the included script from 01.org, it loads properly: https://01.org/linuxgraphics/downloads/kabylake-guc-9.14 Before: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 After: GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: SUCCESS load: SUCCESS version wanted: 9.14 version found: 9.14 header: offset is 0; size = 128 uCode: offset is 128; size = 142272 RSA: offset is 142400; size = 256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1750245/+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 1746848] Re: Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15 retina 2013 late
I don't know if this helps but... "dmidecode" command doesn't show a "Lid" entry. ** Attachment added: "dmidecode command" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746848/+attachment/5057718/+files/dmidecode.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/1746848 Title: Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15 retina 2013 late Status in linux package in Ubuntu: Confirmed Bug description: When I click on the suspend button (alternative of power off button) in the menu or I click the power button, the Ubuntu seems like will be suspended (with a black screen) and, after 5-10 seconds, come back to the login screen. Closing the lid also doesn't take effect. It doesn't even turn off the display. I found that clicking on the suspend button and very quickly closing the lid seems to make it stays suspended. I'm having this trouble in a Macbook Pro 15 retina 2013 late running a Ubuntu 17.10 in the most recent version. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: otto 1600 F pulseaudio /dev/snd/controlC0: otto 1600 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 1 22:58:16 2018 InstallationDate: Installed on 2018-01-26 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookPro10,1 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00F2.B00.1708080809 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00F2.B00.1708080809:bd08/08/2017:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.family: Mac dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746848/+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 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
I'm also seeing this issue with a Maxtor Seagate 1 TB external USB 3 hard drive on HP Pavilion Desktop PC 570-p0xx System is Kubuntu 16.04.3 LTS with Kernel 4.13.0-32-generic The workaround/quirk from the original post makes the errors go away, but the device is really slow. lsusb output Bus 005 Device 003: ID 0bc2:61b6 Seagate RSS LLC Drive is brand new and has no SMART errors. Output of lshw is attached. If you need any other informations please let me know. But I could take some _weeks_ untill I will have access to this machine again. ** Attachment added: "lshw output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+attachment/5057651/+files/lshw.out -- 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/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+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 1750226] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1750226 Title: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 Status in linux package in Ubuntu: Confirmed Bug description: Automatic bug kernel oops on 18.04 devel branch @ 18/2/2018 ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm 731 F pulseaudio lotuspsychje 1437 F pulseaudio Date: Sun Feb 18 12:16:11 2018 Failure: oops InstallationDate: Installed on 2017-12-16 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) OopsText: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 BUG: Bad rss-counter state mm:8b256d6f4200 idx:3 val:2 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=c2cc7350-42f8-4953-840d-8330750d7f5c ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: KV8-MAX3 (VIA K8T800-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750226/+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 1750226] [NEW] BUG: Bad rss-counter state mm:ffff8b256d6f4200 idx:0 val:-2
Public bug reported: Automatic bug kernel oops on 18.04 devel branch @ 18/2/2018 ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm 731 F pulseaudio lotuspsychje 1437 F pulseaudio Date: Sun Feb 18 12:16:11 2018 Failure: oops InstallationDate: Installed on 2017-12-16 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) OopsText: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 BUG: Bad rss-counter state mm:8b256d6f4200 idx:3 val:2 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=c2cc7350-42f8-4953-840d-8330750d7f5c ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: KV8-MAX3 (VIA K8T800-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-oops -- 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/1750226 Title: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 Status in linux package in Ubuntu: Confirmed Bug description: Automatic bug kernel oops on 18.04 devel branch @ 18/2/2018 ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm 731 F pulseaudio lotuspsychje 1437 F pulseaudio Date: Sun Feb 18 12:16:11 2018 Failure: oops InstallationDate: Installed on 2017-12-16 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) OopsText: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 BUG: Bad rss-counter state mm:8b256d6f4200 idx:3 val:2 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=c2cc7350-42f8-4953-840d-8330750d7f5c ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: KV8-MAX3 (VIA K8T800-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750226/+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 1675540] Re: i2c i2c-1: sendbytes: NAK bailout.
I'm getting this on a 14.04 production server without nouveau and X. Can't test newer kernel since it's a production server. It started happening after upgrade from 3.13.something to 4.4.0-112. -- 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/1675540 Title: i2c i2c-1: sendbytes: NAK bailout. Status in linux package in Ubuntu: Expired Bug description: This bug still exists and looks like it was identified as part of the Nouveau video driver, experienced now with Ubuntu 16.10. Timed out (original?) bug thread: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1015165 Trackback on forums with no clear resolution: https://ubuntuforums.org/showthread.php?t=2074280 Details: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety $ lsmod | grep 'i2c' i2c_piix4 24576 0 i2c_algo_bit 16384 1 nouveau support@apollo:~$ lsmod | grep 'nouveau' nouveau 1572864 1 mxm_wmi16384 1 nouveau video 40960 1 nouveau i2c_algo_bit 16384 1 nouveau ttm 102400 1 nouveau drm_kms_helper167936 1 nouveau drm 368640 4 nouveau,ttm,drm_kms_helper wmi16384 2 mxm_wmi,nouveau $ uname -a Linux apollo 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lspci | grep -i 'nvidia' 01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) dmesg spam : [74243.701317] Raw EDID: [74243.702234] 78 ee c1 25 a3 56 4b 99 27 11 50 54 bf ef 80 95 [74243.703153] 00 71 4f 81 80 95 0f 01 01 01 01 01 01 01 01 9a [74243.704050] 29 a0 d0 51 84 22 30 50 98 36 00 98 ff 10 00 00 [74243.704925] 1c 00 00 00 fd 00 38 4b 1e 53 0e 00 0a 20 20 20 [74243.705816] 20 20 20 00 00 00 ff 00 37 33 37 33 31 38 33 49 [74243.706732] 32 38 57 53 01 00 00 00 fc 00 44 45 4c 4c 20 45 [74243.707617] 31 39 38 57 46 50 0a 00 3a ff ff ff ff ff ff ff [74243.708508] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [74243.65] i2c i2c-1: sendbytes: NAK bailout. [74246.557345] i2c i2c-1: sendbytes: NAK bailout. [74246.843767] i2c i2c-1: sendbytes: NAK bailout. [74247.128195] i2c i2c-1: sendbytes: NAK bailout. [74249.366638] i2c i2c-1: sendbytes: NAK bailout. [74250.883810] i2c i2c-1: sendbytes: NAK bailout. [74251.295261] i2c i2c-1: sendbytes: NAK bailout. [74252.939101] i2c i2c-1: sendbytes: NAK bailout. [74254.200165] i2c i2c-1: sendbytes: NAK bailout. [74254.885717] i2c i2c-1: readbytes: ack/nak timeout [74255.169703] i2c i2c-1: readbytes: ack/nak timeout [74255.737676] i2c i2c-1: readbytes: ack/nak timeout [74257.450821] i2c i2c-1: sendbytes: NAK bailout. No packages : $ dpkg --list | grep -i 'nvidia' $ dpkg --list | grep -i 'nouveau' --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-41-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/midiC1D0', '/dev/snd/pcmC1D3c', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=/dev/mapper/mike--ubuntu--vg-swap_1 InstallationDate: Installed on 2017-03-01 (24 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IwConfig: Error: [Errno 2] No such file or directory MachineType: ECS A780GM-A Ultra Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/mike--ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.161.1 RfKill: Error: [Errno 2] No such file or directory
[Kernel-packages] [Bug 1745608] Re: [x86_64] Kernel panic when building on NFS in VM
Any updates on this? -- 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/1745608 Title: [x86_64] Kernel panic when building on NFS in VM Status in linux package in Ubuntu: Confirmed Bug description: Since around begin of December (definitely before any KPTI was merged), I'm having problems building AOSP on an NFS share that is mounted in a VM with Ubuntu 16.04.3. After some minutes the system freezes completely, the SSH session becomes unresponsive and I can't open a new one. Logging in via virt-manager's UI isn't possible either. When connecting to serial port, I got the following kernel panic stack trace: [ 2531.058622] PANIC: double fault, error_code: 0x0 [ 2531.073231] Kernel panic - not syncing: Machine halted. [ 2531.074309] CPU: 2 PID: 16421 Comm: kworker/2:0H Not tainted 4.4.0-112-generic #135-Ubuntu [ 2531.076122] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-20171110_100015-anatol 04/01/2014 [ 2531.080374] Workqueue: rpciod rpc_async_schedule [sunrpc] [ 2531.081818] 0086 3c797ca978191564 88013fd07e80 813fc233 [ 2531.083022] 81cba603 88013fd07f18 88013fd07f08 8118f1c7 [ 2531.084382] 0008 88013fd07f18 88013fd07eb0 3c797ca978191564 [ 2531.086127] Call Trace: [ 2531.086928] <#DF> [] dump_stack+0x63/0x90 [ 2531.088606] [] panic+0xd3/0x215 [ 2531.091309] [] df_debug+0x2d/0x30 [ 2531.092424] [] do_double_fault+0x7c/0xf0 [ 2531.093294] [] double_fault+0x28/0x30 [ 2531.094170] [] ? __build_skb+0x9d/0xe0 [ 2531.095017] <>[] __netdev_alloc_skb+0xc0/0x100 [ 2531.096281] [] page_to_skb+0x65/0x340 [ 2531.097120] [] virtnet_receive+0x2a5/0x8f0 [ 2531.098055] [] ? virtnet_receive+0x5d3/0x8f0 [ 2531.099023] [] virtnet_poll+0x1d/0x80 [ 2531.100100] [] net_rx_action+0x21e/0x360 [ 2531.100894] [] ? skb_recv_done+0x43/0x50 [ 2531.101765] [] __do_softirq+0x101/0x290 [ 2531.102619] [] irq_exit+0xa3/0xb0 [ 2531.103511] [] do_IRQ+0x54/0xd0 [ 2531.104453] [] common_interrupt+0x1a6/0x1a6 [ 2531.105459][] ? new_slab+0x29f/0x490 [ 2531.106516] [] ? new_slab+0x385/0x490 [ 2531.107428] [] ___slab_alloc+0x22b/0x470 [ 2531.108372] [] ? rpc_malloc+0x34/0xa0 [sunrpc] [ 2531.109389] [] ? xs_sendpages+0x61/0x1d0 [sunrpc] [ 2531.110693] [] ? rpcauth_lookup_credcache+0xbe/0x2a0 [sunrpc] [ 2531.112050] [] ? rpc_malloc+0x34/0xa0 [sunrpc] [ 2531.113174] [] __slab_alloc+0x20/0x40 [ 2531.113906] [] __kmalloc+0x1d5/0x250 [ 2531.114649] [] rpc_malloc+0x34/0xa0 [sunrpc] [ 2531.115483] [] call_allocate+0xc2/0x1b0 [sunrpc] [ 2531.116353] [] ? call_reserveresult+0x120/0x120 [sunrpc] [ 2531.117298] [] ? call_reserveresult+0x120/0x120 [sunrpc] [ 2531.118236] [] __rpc_execute+0x91/0x470 [sunrpc] [ 2531.119085] [] rpc_async_schedule+0x15/0x20 [sunrpc] [ 2531.120327] [] process_one_work+0x165/0x480 [ 2531.121364] [] worker_thread+0x4b/0x4d0 [ 2531.122340] [] ? process_one_work+0x480/0x480 [ 2531.123696] [] kthread+0xe5/0x100 [ 2531.124717] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 2531.126057] [] ret_from_fork+0x3f/0x70 [ 2531.127192] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 2531.129000] Kernel Offset: disabled [ 2531.160053] ---[ end Kernel panic - not syncing: Machine halted. I decided to try the HWE kernel - with the same result, but a different stack trace: [ 3643.637138] PANIC: double fault, error_code: 0x0 [ 3643.650655] Kernel panic - not syncing: Machine halted. [ 3643.651474] CPU: 0 PID: 47 Comm: kswapd0 Not tainted 4.13.0-32-generic #35~16.04.1-Ubuntu [ 3643.653108] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-20171110_100015-anatol 04/01/2014 [ 3643.654974] Call Trace: [ 3643.655384] <#DF> [ 3643.655740] dump_stack+0x63/0x8b [ 3643.656337] panic+0xe4/0x23d [ 3643.656870] df_debug+0x2d/0x30 [ 3643.657421] do_double_fault+0x9a/0x130 [ 3643.658119] double_fault+0x22/0x30 [ 3643.658722] RIP: 0010:_raw_spin_trylock+0x9/0x30 [ 3643.659518] RSP: :a3ec408a3bf8 EFLAGS: 00010292 [ 3643.660404] RAX: 0040008c RBX: 8c31683d1f00 RCX: a3ec408a3c50 [ 3643.661664] RDX: 0001 RSI: 8c31683d19b0 RDI: 8c3166d1e720 [ 3643.662927] RBP: a3ec408a3bf8 R08: a3ec408a3c50 R09: a3ec408a3d50 [ 3643.664166] R10: 0004dde0 R11: 0040 R12: 8c3166cb7f58 [ 3643.665359] R13: a3ec408a3c50 R14: 8c3166cb7f00 R15: 8c3166cb7f80 [ 3643.666573] [ 3643.666948] shrink_dentry_list+0x101/0x2e0 [ 3643.667679] prune_dcache_sb+0x5a/0x80 [ 3643.668330] super_cache_scan+0x119/0x1a0 [ 3643.669025] shrink_slab.part.48+0x1fa/0x420 [ 3643.669760] shrink_slab+0x29/0x30 [ 3643.670357] shrink_node+0x108/0x310 [ 3643.670995] kswapd+0x32a/0x770
[Kernel-packages] [Bug 1691214] Re: Consider enabling --color by default
The attachment "iproute2_4.14.1-0ubuntu3.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1691214 Title: Consider enabling --color by default Status in iproute2 package in Ubuntu: Confirmed Bug description: The output of ip --color a looks a lot nicer to me than ip a If you look in /etc/skel/.bashrc you can see that we already enable color for other commands: alias ls='ls --color=auto' alias grep='grep --color=auto' alias fgrep='fgrep --color=auto' alias egrep='egrep --color=auto' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1691214/+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 1746340] Re: Samsung SSD corruption (fsck needed)
The patch doesn't get merged yet. -- 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-88b1-1f784fb40346 ro