[Kernel-packages] [Bug 2041558] Re: failed to load firmware renesas_usb_fw.mem
I'm not sure that this error message causes problems. My card had firmware in its non-volatile memory, and worked without this. After I updated its firmware to 2.0.2.6 with the chip vendor's Windows tool, I didn't have problems with the card itself after suspend. https://dreamlayers.blogspot.com/2016/03/a-firmware-upgrade-fixed-linux- usb-3.html Sometimes however particular USB devices, like an Arduino Uno clone, didn't work after suspend, and I wondered if providing that firmware could help. So, I put that same 2.0.2.6 firmware extracted from k2026fwup1.exe as /lib/firmware/renesas_usb_fw.mem in /boot/initrd.img. This did remove the error message, but then after a suspend the card stopped working. Even fully cutting power isn't enough to make it work. Only using upd72020x-check-and-init from https://github.com/markusj/upd72020x-load makes it work. So, apparently supplying this firmware is dangerous, because it can corrupt the flash or otherwise mess up a USB 3 card. -- 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/2041558 Title: failed to load firmware renesas_usb_fw.mem Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: Invalid Bug description: the log show below: xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback to ROM From this below, it seems just need to add renesas_usb_fw.mem into the initrd. https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549 When the firmware is required and is not present, kernel message: Direct firmware load for renesas_usb_fw.mem failed with error When the firmware is required and is an empty file, kernel message: FW has invalid version, followed by the above message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2041558/+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 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
I re-added the tags "verification-done-lunar-linux verification-done-mantic-linux" manually as they were deleted by the bridge (bugproxy) when syncing the target milestone. This problem of disappearing tags has been seen lately also in other bugs / LP items. IBM is currently investigating what's causing 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/2042853 Title: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] * Today no s390x-specific vfio-pci devices (zPCI) can be passed from a KVM host to a KVM guest (incl. secure execution guests in the context of confidential computing). * s390x PCI passthrough needs various changes in the s390x kernel zPCI code (incl. the new s390x-specific Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0 and got backported to 22.04/jammy as part of LP: #1853306. * Lunar an newer Ubuntu releases have the code already included from upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the config option is not set, hence zPCI pass-through is still not possible. [Fix] * To be able to make use of VFIO zPCI pass-through on s390x running newer Ubuntu releases (especially needed in the context of secure execution) the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs to be enabled and set to 'y'. [Test Case] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only available on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) [Regression Potential] * The regression potential is moderate, since the code is upstream for quite a while and already enabled in jammy. * The general way on using passthrough has not changed, with this change (config option) it's now just possible to passthrough zPCI on top. * CCW devices are not affected. * And this is s390x-specific anyway, so no other architectures are affected. [Other] * The enabling of the kernel config option is exactly the same for L, M and U/N, but I submitted separate patches due to slightly different context and offsets. __ === Description by mjros...@us.ibm.com === LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to enable enhanced interpretation of PCI passthrough on s390. It also
[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
** Tags added: verification-done-lunar-linux verification-done-mantic- linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042853 Title: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] * Today no s390x-specific vfio-pci devices (zPCI) can be passed from a KVM host to a KVM guest (incl. secure execution guests in the context of confidential computing). * s390x PCI passthrough needs various changes in the s390x kernel zPCI code (incl. the new s390x-specific Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0 and got backported to 22.04/jammy as part of LP: #1853306. * Lunar an newer Ubuntu releases have the code already included from upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the config option is not set, hence zPCI pass-through is still not possible. [Fix] * To be able to make use of VFIO zPCI pass-through on s390x running newer Ubuntu releases (especially needed in the context of secure execution) the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs to be enabled and set to 'y'. [Test Case] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only available on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) [Regression Potential] * The regression potential is moderate, since the code is upstream for quite a while and already enabled in jammy. * The general way on using passthrough has not changed, with this change (config option) it's now just possible to passthrough zPCI on top. * CCW devices are not affected. * And this is s390x-specific anyway, so no other architectures are affected. [Other] * The enabling of the kernel config option is exactly the same for L, M and U/N, but I submitted separate patches due to slightly different context and offsets. __ === Description by mjros...@us.ibm.com === LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to enable enhanced interpretation of PCI passthrough on s390. It also included a kernel config update for CONFIG_VFIO_PCI_ZDEV_KVM=y which is necessary to activate this kernel feature. For lunar and mantic, the kernel code did not require backporting due to the base kernel version already containing it,
[Kernel-packages] [Bug 1979298] Re: Installing nvidia-driver-510-server removes nvidia-cuda-dev
This seems to have been resolved using nvidia-driver-525-server. Thanks! ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510-server in Ubuntu. https://bugs.launchpad.net/bugs/1979298 Title: Installing nvidia-driver-510-server removes nvidia-cuda-dev Status in nvidia-graphics-drivers-510-server package in Ubuntu: Fix Released Bug description: On Ubuntu 22.04, installing first `nvidia-cuda-dev` and then `nvidia- driver-510-server` leads to `nvidia-cuda-dev` being removed (or at least most packages it installed). The other way the same happens too - installing `nvidia-driver-510-server` first and then `nvidia-cuda- dev` removes stuff from the driver. I guess this is related to https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda- toolkit/+bug/1963976 but I'm not sure if it's the same. Is there any workaround for this? I need both packages - `nvidia-cuda- dev` for `ffmpeg` to run (which is compiled with nvidia support) and `nvidia-driver-510-server` so that the card is actually used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510-server/+bug/1979298/+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 2030978] Re: kernel 6.5 changes cause UBSAN errors (patch included)
I applied the patch to files in /usr/src/broadcom-sta-6.30.223.271/ and then
reinstalled linux-image-6.5.0-7-generic to make DKMS rebuild the module. It
made this error go away:
UBSAN: array-index-out-of-bounds in
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:2394:26
But this error remains:
UBSAN: array-index-out-of-bounds in
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:1935:4
I did verify that in /usr/src/broadcom-sta-6.30.223.271/src/include/wlioctl.h,
the relevant struct has been changed:
struct maclist {
uint count;
struct ether_addr ea[];
};
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2030978
Title:
kernel 6.5 changes cause UBSAN errors (patch included)
Status in broadcom-sta package in Ubuntu:
New
Bug description:
"On Linux 6.5, due to commit 2d47c6956ab3 ("ubsan: Tighten UBSAN_BOUNDS
on GCC"), flexible trailing arrays declared like `whatever_t foo[1];`
will generate warnings when CONFIG_UBSAN & co. is enabled."
Due to changes in kernel 6.5, we get this error in dmesg:
[ 28.818756]
[ 28.822952] UBSAN: array-index-out-of-bounds in
/var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
[ 28.82] index 2 is out of range for type 'ether_addr [1]'
[ 28.832900] CPU: 1 PID: 1232 Comm: avahi-daemon Tainted: P OE
6.5.0-rc4 #1
[ 28.836452] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663,
BIOS 432.60.3.0.0 10/27/2021
[ 28.839806] Call Trace:
[ 28.843091]
[ 28.846387] dump_stack_lvl+0x48/0x60
[ 28.849692] dump_stack+0x10/0x20
[ 28.852965] __ubsan_handle_out_of_bounds+0xc6/0x100
[ 28.856251] _wl_set_multicast_list+0x1fd/0x220 [wl]
[ 28.859191] wl_set_multicast_list+0x3a/0x80 [wl]
[ 28.861879] __dev_set_rx_mode+0x6a/0xc0
[ 28.864237] __dev_mc_add+0x82/0x90
[ 28.866587] dev_mc_add+0x10/0x20
[ 28.868920] igmp_group_added+0x198/0x1d0
[ 28.871102] ip_mc_inc_group+0x185/0x2b0
[ 28.873231] __ip_mc_join_group+0x108/0x170
[ 28.875170] ip_mc_join_group+0x10/0x20
[ 28.877111] do_ip_setsockopt+0x104d/0x1160
[ 28.878894] ? __sys_setsockopt+0xeb/0x1c0
[ 28.880657] ip_setsockopt+0x30/0xb0
[ 28.882326] udp_setsockopt+0x22/0x40
[ 28.883949] sock_common_setsockopt+0x14/0x20
[ 28.885554] __sys_setsockopt+0xde/0x1c0
[ 28.887063] __x64_sys_setsockopt+0x1f/0x30
[ 28.888564] do_syscall_64+0x55/0x80
[ 28.889952] ? syscall_exit_to_user_mode+0x26/0x40
[ 28.891226] ? __x64_sys_recvmsg+0x1d/0x20
[ 28.892450] ? do_syscall_64+0x61/0x80
[ 28.893651] ? do_syscall_64+0x61/0x80
[ 28.894796] entry_SYSCALL_64_after_hwframe+0x46/0xb0
[ 28.895942] RIP: 0033:0x7f0a97a7ddae
[ 28.897100] Code: 0f 1f 40 00 48 8b 15 69 60 0d 00 f7 d8 64 89 02 48 c7 c0
ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 31
[ 28.898270] RSP: 002b:7fffb7b1b3f8 EFLAGS: 0246 ORIG_RAX:
0036
[ 28.899449] RAX: ffda RBX: 000c RCX:
7f0a97a7ddae
[ 28.900623] RDX: 0023 RSI: RDI:
000c
[ 28.901784] RBP: 0001 R08: 000c R09:
0004
[ 28.902895] R10: 7fffb7b1b404 R11: 0246 R12:
7fffb7b1b404
[ 28.904011] R13: 0014 R14: 55cc506ee078 R15:
55cc506eaf60
[ 28.905149]
[ 28.906228]
A patch is however available for this issue:
https://gist.github.com/joanbm/9cd5fda1dcfab9a67b42cc6195b7b269
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: bcmwl-kernel-source (not installed)
Uname: Linux 6.5.0-rc4 x86_64
NonfreeKernelModules: wl zfs
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Aug 10 10:40:27 2023
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: broadcom-sta
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2030978/+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 2035182] [NEW] Touchpad events recognized, but mousepointer does not move
Public bug reported: I did the debuggin like on the website: https://wiki.ubuntu.com/DebuggingTouchpadDetection I attached the file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 09:22:46 2023 InstallationDate: Installed on 2020-12-21 (994 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-06-01 (468 days ago) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "evteest" https://bugs.launchpad.net/bugs/2035182/+attachment/5700191/+files/evtest -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2035182 Title: Touchpad events recognized, but mousepointer does not move Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I did the debuggin like on the website: https://wiki.ubuntu.com/DebuggingTouchpadDetection I attached the file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 09:22:46 2023 InstallationDate: Installed on 2020-12-21 (994 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-06-01 (468 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2035182/+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 2033574] [NEW] Hangs due to Option "TripleBuffer" "1"
Public bug reported: I kept getting occasional hangs. Usually, the mouse would still move, but I couldn't do anything other than use Magic SysRq. These seemed to happen more after resume from suspend, but I also saw them happen if the computer hadn't been suspended since booting. They probably happened more often when Firefox was open and when using KDE Plasma instead of Xfce. This persisted through several Ubuntu releases, and continued happening in 23.04. In /etc/X11/xorg.conf, in the "Device" section, I had the line: Option "TripleBuffer" "1" After I commented that out, the hangs stopped. I did that on 2023-07-14 and now it's 2023-08-30. It has been way more than long enough to see that the hangs stopped. Fixing this problem, to allow me to use this option without the hangs, isn't important to me. I am reporting this to document how removing the option stopped hangs. This is with a GeForce GT 710. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-470 470.199.02-0ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Aug 30 23:15:08 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to lunar on 2023-04-21 (131 days ago) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2033574 Title: Hangs due to Option "TripleBuffer" "1" Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: I kept getting occasional hangs. Usually, the mouse would still move, but I couldn't do anything other than use Magic SysRq. These seemed to happen more after resume from suspend, but I also saw them happen if the computer hadn't been suspended since booting. They probably happened more often when Firefox was open and when using KDE Plasma instead of Xfce. This persisted through several Ubuntu releases, and continued happening in 23.04. In /etc/X11/xorg.conf, in the "Device" section, I had the line: Option "TripleBuffer" "1" After I commented that out, the hangs stopped. I did that on 2023-07-14 and now it's 2023-08-30. It has been way more than long enough to see that the hangs stopped. Fixing this problem, to allow me to use this option without the hangs, isn't important to me. I am reporting this to document how removing the option stopped hangs. This is with a GeForce GT 710. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-470 470.199.02-0ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Aug 30 23:15:08 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to lunar on 2023-04-21 (131 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2033574/+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 1950792] Re: No boot possible - Cannot open root device
Figured out what made that one node different from the rest: its UEFI network boot stack had both PXE and HTTP enabled, while the others were PXE only. After i added the kernel boot parameters, MAAS started to truncate the HTTP URI by a few characters (and now keeps doing that even if the kernel commandline options are cleared) which doesnt imapct the PXE clients but does break the HTTP ones (this node worked fine before the params were added). For anyone stuck in this situation, the workaround seems to be to disable HTTP-based image acquisition in the system's BIOS configuration menu - PXE only on the IP stack desired will avoid the oddly truncated HTTP URI which occurs after setting kernel boot parameters. -- 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/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Triaged Status in linux package in Ubuntu: Incomplete Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 1950792] Re: No boot possible - Cannot open root device
Still a problem on _random_ supermicro hardware: i have 15 identical nodes, set kernel parameters for `console=ttyS0 console=tty0` and now _one_ node will not commission or therefore provision with this error. Maas (snap) is at 3.2.7-12037-g.c688dd446 The maas UI doesn't update the parameters passed when saved, user has to refresh the page or it keeps showing up as the last set of parameters at page-load. After setting the parameters back to blank, this one node still cannot boot from MAAS - whatever broke, broke persistently. -- 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/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Triaged Status in linux package in Ubuntu: Incomplete Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 1997160] Re: Kernels 128, 131 and 132 won't boot on Pentium 3, attempted to kill the idle task
After adding mitigations=off to the kernel command line, 5.4.0-132-generic boots successfully every time. This workaround satisfies me. I don't need those mitigations on that old PC, and turning them off probably speeds it up a bit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1997160 Title: Kernels 128, 131 and 132 won't boot on Pentium 3, attempted to kill the idle task Status in linux-hwe-5.4 package in Ubuntu: New Bug description: I am running Ubuntu 18.04.6 LTS on an old PC with a Pentium 3 and Soltek SL-65KVB motherboard. The 5.4.0 generic kernels work fine up to and including release 126. Attempts to boot 128, 131 and 132 quickly lead to a panic every time. The error seems to be "Attempted to kill the idle task". I tried idle=halt and idle=poll kernel command line options without any change. The installation procedure for the kernels seems fine, because I installed kernel 125 after installing the problem kernels, and it worked. I am attaching a photo of what the screen shows when the crash happens. I could try to capture more of that via a serial port if that would be helpful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-126-generic 5.4.0-126.142~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203 Uname: Linux 5.4.0-126-generic i686 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CurrentDesktop: XFCE Date: Sat Nov 19 18:01:57 2022 InstallationDate: Installed on 2012-10-07 (3695 days ago) InstallationMedia: Mythbuntu 12.04.1 "Precise Pangolin" - Release i386 (20120818.1) SourcePackage: linux-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2018-04-08 (1686 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1997160/+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 1997160] [NEW] Kernels 128, 131 and 132 won't boot on Pentium 3, attempted to kill the idle task
Public bug reported: I am running Ubuntu 18.04.6 LTS on an old PC with a Pentium 3 and Soltek SL-65KVB motherboard. The 5.4.0 generic kernels work fine up to and including release 126. Attempts to boot 128, 131 and 132 quickly lead to a panic every time. The error seems to be "Attempted to kill the idle task". I tried idle=halt and idle=poll kernel command line options without any change. The installation procedure for the kernels seems fine, because I installed kernel 125 after installing the problem kernels, and it worked. I am attaching a photo of what the screen shows when the crash happens. I could try to capture more of that via a serial port if that would be helpful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-126-generic 5.4.0-126.142~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203 Uname: Linux 5.4.0-126-generic i686 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CurrentDesktop: XFCE Date: Sat Nov 19 18:01:57 2022 InstallationDate: Installed on 2012-10-07 (3695 days ago) InstallationMedia: Mythbuntu 12.04.1 "Precise Pangolin" - Release i386 (20120818.1) SourcePackage: linux-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2018-04-08 (1686 days ago) ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 third-party-packages ** Attachment added: "Screen shown when kernel crashed" https://bugs.launchpad.net/bugs/1997160/+attachment/5631659/+files/Kernel_132_crash.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1997160 Title: Kernels 128, 131 and 132 won't boot on Pentium 3, attempted to kill the idle task Status in linux-hwe-5.4 package in Ubuntu: New Bug description: I am running Ubuntu 18.04.6 LTS on an old PC with a Pentium 3 and Soltek SL-65KVB motherboard. The 5.4.0 generic kernels work fine up to and including release 126. Attempts to boot 128, 131 and 132 quickly lead to a panic every time. The error seems to be "Attempted to kill the idle task". I tried idle=halt and idle=poll kernel command line options without any change. The installation procedure for the kernels seems fine, because I installed kernel 125 after installing the problem kernels, and it worked. I am attaching a photo of what the screen shows when the crash happens. I could try to capture more of that via a serial port if that would be helpful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-126-generic 5.4.0-126.142~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203 Uname: Linux 5.4.0-126-generic i686 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CurrentDesktop: XFCE Date: Sat Nov 19 18:01:57 2022 InstallationDate: Installed on 2012-10-07 (3695 days ago) InstallationMedia: Mythbuntu 12.04.1 "Precise Pangolin" - Release i386 (20120818.1) SourcePackage: linux-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2018-04-08 (1686 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1997160/+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 1993668] Re: mSBC codec not available only CVSD one
This bug affects me, albeit with another chip that used to work with kernel 5.15 from Ubuntu 22.04 dmesg output: ``` [5.641569] Bluetooth: hci0: BCM: chip id 110 [5.642558] Bluetooth: hci0: BCM: features 0x2f [5.658564] Bluetooth: hci0: BCM4350C5 [5.658570] Bluetooth: hci0: BCM4350C5 (003.006.007) build [5.661596] Bluetooth: hci0: BCM4350C5 'brcm/BCM-0a5c-6412.hcd' Patch [5.682015] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4350-pcie for chip BCM4350/8 [5.682301] brcmfmac :3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.Dell Inc.-XPS 13 9350.bin failed with error -2 [5.684268] brcmfmac :3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.Dell Inc.-XPS 13 9350.txt failed with error -2 [5.684313] brcmfmac :3a:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.txt failed with error -2 [5.879989] psmouse serio1: synaptics: Unable to query device: -5 [5.974249] input: Dell WMI hotkeys as /devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input17 [6.021264] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4350-pcie for chip BCM4350/8 [6.021313] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [6.021581] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4350/8 wl0: Oct 22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176 [6.032590] _ART package 0 is invalid, ignored [6.032614] _ART package 0 is invalid, ignored [6.076145] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [6.076154] snd_hda_intel :00:1f.3: NHLT table not found [6.076170] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [6.076481] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [6.310307] intel_tcc_cooling: Programmable TCC Offset detected [6.316550] Bluetooth: hci0: Dell DW1820A [6.316558] Bluetooth: hci0: BCM4350C5 (003.006.007) build 1703 ``` -- 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/1993668 Title: mSBC codec not available only CVSD one Status in Linux: Confirmed Status in PipeWire: New Status in linux package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Bug description: I am using Ubuntu 22.10 and my headset Pixel Buds Pro works correctly but only the low-quality CVSD codec is available and not the mSBC one for the Handsfree profile. I know the Pixel Buds Pro headset are compatible with mSBC because on another machine also running Ubuntu 22.10, this headset correctly works with the mSBC codec (and the audio quality is much better for both input and output audio). My motherboard is an Aorus x670 with AMD Zen 4 CPU. The bluetooth controller seems to be: ``` Bus 005 Device 003: ID 0e8d:0616 MediaTek Inc. Wireless_Device ``` Let me know if you need more informations. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-27 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) NonfreeKernelModules: nvidia_modeset nvidia Package: pipewire 0.3.58-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1993668/+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 1991027] Re: rcu_preempt detected expedited stalls on CPUs/tasks
I see lots of these errors on my Dell Inspiron 6400 when booting. They
started after upgrading to Ubuntu 20.10. Everything still seems to work.
** Attachment added: "Errors from dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991027/+attachment/5622420/+files/rcu%20errors%20inspiron%206400.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/1991027
Title:
rcu_preempt detected expedited stalls on CPUs/tasks
Status in linux package in Ubuntu:
Confirmed
Bug description:
[3.740699] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 2-... } 6 jiffies s: 65 root: 0x1/.
[3.740714] rcu: blocking rcu_node structures (internal RCU debug):
l=1:0-9:0x4/.
[3.740739] Task dump for CPU 2:
[3.740740] task:systemd-udevd state:R running task stack:0
pid: 534 ppid: 516 flags:0x400a
[3.740743] Call Trace:
[3.740758]
[3.740760] ? kallsyms_lookup+0x14/0x20
[3.740763] ? test_for_valid_rec+0x38/0x80
[3.740765] ? change_page_attr_set_clr+0x158/0x1d0
[3.740768] ? ftrace_module_enable+0xa6/0x210
[3.740770] ? load_module+0x636/0xcb0
[3.740772] ? __do_sys_finit_module+0xbd/0x130
[3.740773] ? __do_sys_finit_module+0xbd/0x130
[3.740775] ? __x64_sys_finit_module+0x18/0x20
[3.740776] ? do_syscall_64+0x58/0x80
[3.740778] ? ksys_mmap_pgoff+0x10c/0x250
[3.740780] ? exit_to_user_mode_prepare+0x30/0xa0
[3.740782] ? syscall_exit_to_user_mode+0x26/0x50
[3.740784] ? __x64_sys_mmap+0x33/0x50
[3.740785] ? do_syscall_64+0x67/0x80
[3.740786] ? __x64_sys_lseek+0x18/0x20
[3.740788] ? do_syscall_64+0x67/0x80
[3.740789] ? exit_to_user_mode_prepare+0x85/0xa0
[3.740791] ? syscall_exit_to_user_mode+0x26/0x50
[3.740792] ? do_syscall_64+0x67/0x80
[3.740793] ? do_syscall_64+0x67/0x80
[3.740794] ? sysvec_call_function+0x4b/0xa0
[3.740796] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[3.740797]
[3.816703] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 2-... } 25 jiffies s: 65 root: 0x1/.
[3.816719] rcu: blocking rcu_node structures (internal RCU debug):
l=1:0-9:0x4/.
[3.816745] Task dump for CPU 2:
[3.816745] task:systemd-udevd state:R running task stack:0
pid: 534 ppid: 516 flags:0x400a
[3.816747] Call Trace:
[3.816748]
[3.816749] ? kallsyms_lookup+0x14/0x20
[3.816751] ? test_for_valid_rec+0x38/0x80
[3.816753] ? change_page_attr_set_clr+0x158/0x1d0
[3.816755] ? ftrace_module_enable+0xa6/0x210
[3.816757] ? load_module+0x636/0xcb0
[3.816759] ? __do_sys_finit_module+0xbd/0x130
[3.816760] ? __do_sys_finit_module+0xbd/0x130
[3.816762] ? __x64_sys_finit_module+0x18/0x20
[3.816763] ? do_syscall_64+0x58/0x80
[3.816765] ? ksys_mmap_pgoff+0x10c/0x250
[3.816766] ? exit_to_user_mode_prepare+0x30/0xa0
[3.816768] ? syscall_exit_to_user_mode+0x26/0x50
[3.816770] ? __x64_sys_mmap+0x33/0x50
[3.816771] ? do_syscall_64+0x67/0x80
[3.816772] ? __x64_sys_lseek+0x18/0x20
[3.816773] ? do_syscall_64+0x67/0x80
[3.816774] ? exit_to_user_mode_prepare+0x85/0xa0
[3.816776] ? syscall_exit_to_user_mode+0x26/0x50
[3.816777] ? do_syscall_64+0x67/0x80
[3.816778] ? do_syscall_64+0x67/0x80
[3.816779] ? sysvec_call_function+0x4b/0xa0
[3.816781] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[3.816782]
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-15-generic 5.19.0-15.15
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:crow 1930 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue Sep 27 18:51:41 2022
InstallationDate: Installed on 2022-09-10 (17 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
IwConfig:
lono wireless extensions.
enp2s0no wireless extensions.
MachineType: Dell Inc. XPS 8940
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic
root=UUID=a8ff0852-c8bb-4cba-a02f-7acb738f7666 ro audit=0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.19.0-15-generic N/A
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
After putting nvidia.NVreg_PreserveVideoMemoryAllocations=0 in the kernel command line I don't remember any black screens after wake from suspend. They certainly haven't happened in Ubuntu 22.04. The computer is always usable immediately after waking. However, I have gotten lockups some time later after waking. These seem to never happen if I only use my main monitor, connected to the DVI port of the GeForce GT 710. That is the way X is configured to start. However, if I switch to the second monitor at some point after booting (also DVI but connected to the HDMI port), then lockups can happen, even after I switch back to the primary monitor. I use xrandr to switch. This is with the 470 driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight
This is still a problem at least up until kernel 5.10 if not later. -- 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/1851833 Title: [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust brightness of backlight Status in linux package in Ubuntu: Expired Bug description: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 14:03:33 2019 DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1] NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1] InstallationDate: Installed on 2019-10-09 (30 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook PB50_70RF,RD,RC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago) dmi.bios.date: 02/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: PB50_70RF,RD,RC dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: PB50_70RF,RD,RC dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851833/+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 1950793] Re: util-linux/lsblk reports WWN as SERIAL in focal
Maybe this is the issue: https://github.com/util-linux/util- linux/commit/b95752ad206222dfaa854a01c6106c89d2c607a2 https://github.com/util-linux/util-linux/issues/1143 Maybe you can backport it? ** Bug watch added: github.com/util-linux/util-linux/issues #1143 https://github.com/util-linux/util-linux/issues/1143 -- 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/1950793 Title: util-linux/lsblk reports WWN as SERIAL in focal Status in linux package in Ubuntu: Confirmed Bug description: I've come across the problem that lsblk treats the WWN as SN. ~# lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~# apt-cache policy util-linux util-linux: Installed: 2.34-0.1ubuntu9.1 Candidate: 2.34-0.1ubuntu9.1 Version table: *** 2.34-0.1ubuntu9.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages What I expected to happen: Show the disks serial when using the SERIAL output What happened instead: The WWN is printed instead. This does not happen with every disk. how to reproduce: ~# lsblk -dn -o WWN /dev/sdb 0x539ad8d2cd39 ~# lsblk -dn -o SERIAL /dev/sdb 539ad8d2cd39 smartctl show the correct serial ~# smartctl -a /dev/sdb smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba MG06ACA... Enterprise Capacity HDD Device Model: TOSHIBA MG06ACA800E Serial Number:41P0A0SHFKRE LU WWN Device Id: 5 39 ad8d2cd39 <... snip ...> A disks where it works: ~# lsblk -dn -o SERIAL /dev/sdn SMC0515D93017CH75029 ~# lsblk -dn -o WWN /dev/sdn 0x515d93017c29 ~# smartctl -a /dev/sdn smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Silicon Motion based OEM SSDs Device Model: SuperMicro SSD Serial Number:SMC0515D93017CH75029 LU WWN Device Id: 5 15d930 17c29 <... snip ...> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950793/+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 1950793] Re: util-linux/lsblk reports WWN as SERIAL in focal
As I don't know what kind of data will be sent and this is a production system with customer data on it, I won't do this. There is also no need to actuall collect data from the system, as it is a simple out of the box installation. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950793 Title: util-linux/lsblk reports WWN as SERIAL in focal Status in linux package in Ubuntu: Confirmed Bug description: I've come across the problem that lsblk treats the WWN as SN. ~# lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~# apt-cache policy util-linux util-linux: Installed: 2.34-0.1ubuntu9.1 Candidate: 2.34-0.1ubuntu9.1 Version table: *** 2.34-0.1ubuntu9.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages What I expected to happen: Show the disks serial when using the SERIAL output What happened instead: The WWN is printed instead. This does not happen with every disk. how to reproduce: ~# lsblk -dn -o WWN /dev/sdb 0x539ad8d2cd39 ~# lsblk -dn -o SERIAL /dev/sdb 539ad8d2cd39 smartctl show the correct serial ~# smartctl -a /dev/sdb smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba MG06ACA... Enterprise Capacity HDD Device Model: TOSHIBA MG06ACA800E Serial Number:41P0A0SHFKRE LU WWN Device Id: 5 39 ad8d2cd39 <... snip ...> A disks where it works: ~# lsblk -dn -o SERIAL /dev/sdn SMC0515D93017CH75029 ~# lsblk -dn -o WWN /dev/sdn 0x515d93017c29 ~# smartctl -a /dev/sdn smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Silicon Motion based OEM SSDs Device Model: SuperMicro SSD Serial Number:SMC0515D93017CH75029 LU WWN Device Id: 5 15d930 17c29 <... snip ...> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950793/+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 1950793] [NEW] util-linux/lsblk reports WWN as SERIAL in focal
Public bug reported: I've come across the problem that lsblk treats the WWN as SN. ~# lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ~# apt-cache policy util-linux util-linux: Installed: 2.34-0.1ubuntu9.1 Candidate: 2.34-0.1ubuntu9.1 Version table: *** 2.34-0.1ubuntu9.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages What I expected to happen: Show the disks serial when using the SERIAL output What happened instead: The WWN is printed instead. This does not happen with every disk. how to reproduce: ~# lsblk -dn -o WWN /dev/sdb 0x539ad8d2cd39 ~# lsblk -dn -o SERIAL /dev/sdb 539ad8d2cd39 smartctl show the correct serial ~# smartctl -a /dev/sdb smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba MG06ACA... Enterprise Capacity HDD Device Model: TOSHIBA MG06ACA800E Serial Number:41P0A0SHFKRE LU WWN Device Id: 5 39 ad8d2cd39 <... snip ...> A disks where it works: ~# lsblk -dn -o SERIAL /dev/sdn SMC0515D93017CH75029 ~# lsblk -dn -o WWN /dev/sdn 0x515d93017c29 ~# smartctl -a /dev/sdn smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Silicon Motion based OEM SSDs Device Model: SuperMicro SSD Serial Number:SMC0515D93017CH75029 LU WWN Device Id: 5 15d930 17c29 <... snip ...> ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950793 Title: util-linux/lsblk reports WWN as SERIAL in focal Status in linux package in Ubuntu: New Bug description: I've come across the problem that lsblk treats the WWN as SN. ~# lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~# apt-cache policy util-linux util-linux: Installed: 2.34-0.1ubuntu9.1 Candidate: 2.34-0.1ubuntu9.1 Version table: *** 2.34-0.1ubuntu9.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages What I expected to happen: Show the disks serial when using the SERIAL output What happened instead: The WWN is printed instead. This does not happen with every disk. how to reproduce: ~# lsblk -dn -o WWN /dev/sdb 0x539ad8d2cd39 ~# lsblk -dn -o SERIAL /dev/sdb 539ad8d2cd39 smartctl show the correct serial ~# smartctl -a /dev/sdb smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba MG06ACA... Enterprise Capacity HDD Device Model: TOSHIBA MG06ACA800E Serial Number:41P0A0SHFKRE LU WWN Device Id: 5 39 ad8d2cd39 <... snip ...> A disks where it works: ~# lsblk -dn -o SERIAL /dev/sdn SMC0515D93017CH75029 ~# lsblk -dn -o WWN /dev/sdn 0x515d93017c29 ~# smartctl -a /dev/sdn smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-89-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Silicon Motion based OEM SSDs Device Model: SuperMicro SSD Serial Number:SMC0515D93017CH75029 LU WWN Device Id: 5 15d930 17c29 <... snip ...> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950793/+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 1821564] Re: b44 Ethernet driver null pointer during initialization
No, "pcie_aspm=off" does not help. I also tried uninstalling broadcom-sta-dkms. It blacklists the b44 module via /etc/modprobe.d/broadcom-sta-dkms.conf and also https://wiki.debian.org/wl says that b44 is incompatible with wl. This did not help either. My laptop seems fine with just having the b44 module loaded. Lockups only happen when I plug in the Ethernet cable and start using it. The lockup seems total, with even Magic SysRq from the laptop's own keyboard doing absolutely nothing. -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Incomplete Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
I got upgraded back to 470 because new 460 transitional dummy packages were released, which caused the upgrade. I could have prevented that via apt-mark hold. When I was getting these problems with 470 I had nvidia.NVreg_PreserveVideoMemoryAllocations=1 in my kernel command line, via /etc/default/grub. After being upgraded to 470 again, I changed that to nvidia.NVreg_PreserveVideoMemoryAllocations=0. So far, waking from sleep has been reliable. (Also, neither Firefox nor KDE Plasma have problems after sleep with this. I had set that option to 1 in the past because it seemed to help with earlier versions of Firefox and Plasma.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1946303] [NEW] No video after wake from S3 due to Nvidia driver crash
Public bug reported: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "crashes seen via journalctl" https://bugs.launchpad.net/bugs/1946303/+attachment/5531172/+files/nvidia_resume_crash.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 1821564] Re: b44 Ethernet driver null pointer during initialization
In Ubuntu 21.10 with 5.13.0-16-generic kernel, I don't get any dmesg errors after I "modprobe b44" and Ethernet works initially at reasonable speed, but the whole system freezes totally after a few minutes. I suppose this means the b44 driver still doesn't work properly, because I don't get such freezes when using WiFi. Though I don't know for sure, because I don't have any error messages. -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Incomplete Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX:
[Kernel-packages] [Bug 1922439] Re: X hangs after wake on Mobility Radeon x1400
Wake worked with kernel 5.11.0-16-generic. So, I guess this is fixed. -- 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/1922439 Title: X hangs after wake on Mobility Radeon x1400 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell Inspiron 6400 with Mobility Radeon x1400. In Ubuntu 20.10 and earlier, wake from sleep worked properly. In Ubuntu 21.04, X does not work after wake from sleep. It fails in Plasma, Xfce, Openbox and Twm. With both Plasma and Xfce the screen is totally black. In all cases it is possible to use Control+Alt+F2 to go to a text console and use that. Generally it is possible to kill and restart X to get a usable GUI again. I'm reporting this as a kernel bug because if I boot Ubuntu 21.04 with linux-image-5.8.0-48-generic from Ubuntu 20.10, then X works after wake from sleep. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-13-generic 5.11.0-13.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:20:38 2021 HibernationDevice: RESUME=UUID=2d7284cc-d0df-45d7-b0a1-e5a0a8128eb8 InstallationDate: Installed on 2012-01-19 (3362 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda5 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.196 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-02 (1 days ago) dmi.bios.date: 06/13/2007 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922439/+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 1922439] Re: X hangs after wake on Mobility Radeon x1400
Wake from sleep works in Xfce and Plasma in Ubuntu 21.04 when using kernel 5.12.0-051200rc5-generic from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.12-rc5/ -- 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/1922439 Title: X hangs after wake on Mobility Radeon x1400 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell Inspiron 6400 with Mobility Radeon x1400. In Ubuntu 20.10 and earlier, wake from sleep worked properly. In Ubuntu 21.04, X does not work after wake from sleep. It fails in Plasma, Xfce, Openbox and Twm. With both Plasma and Xfce the screen is totally black. In all cases it is possible to use Control+Alt+F2 to go to a text console and use that. Generally it is possible to kill and restart X to get a usable GUI again. I'm reporting this as a kernel bug because if I boot Ubuntu 21.04 with linux-image-5.8.0-48-generic from Ubuntu 20.10, then X works after wake from sleep. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-13-generic 5.11.0-13.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:20:38 2021 HibernationDevice: RESUME=UUID=2d7284cc-d0df-45d7-b0a1-e5a0a8128eb8 InstallationDate: Installed on 2012-01-19 (3362 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda5 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.196 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-02 (1 days ago) dmi.bios.date: 06/13/2007 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922439/+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 1922439] [NEW] X hangs after wake on Mobility Radeon x1400
Public bug reported: I have a Dell Inspiron 6400 with Mobility Radeon x1400. In Ubuntu 20.10 and earlier, wake from sleep worked properly. In Ubuntu 21.04, X does not work after wake from sleep. It fails in Plasma, Xfce, Openbox and Twm. With both Plasma and Xfce the screen is totally black. In all cases it is possible to use Control+Alt+F2 to go to a text console and use that. Generally it is possible to kill and restart X to get a usable GUI again. I'm reporting this as a kernel bug because if I boot Ubuntu 21.04 with linux-image-5.8.0-48-generic from Ubuntu 20.10, then X works after wake from sleep. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-13-generic 5.11.0-13.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:20:38 2021 HibernationDevice: RESUME=UUID=2d7284cc-d0df-45d7-b0a1-e5a0a8128eb8 InstallationDate: Installed on 2012-01-19 (3362 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda5 RelatedPackageVersions: linux-restricted-modules-5.11.0-13-generic N/A linux-backports-modules-5.11.0-13-generic N/A linux-firmware 1.196 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-02 (1 days ago) dmi.bios.date: 06/13/2007 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:br1.7:efr1.7:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy hirsute -- 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/1922439 Title: X hangs after wake on Mobility Radeon x1400 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell Inspiron 6400 with Mobility Radeon x1400. In Ubuntu 20.10 and earlier, wake from sleep worked properly. In Ubuntu 21.04, X does not work after wake from sleep. It fails in Plasma, Xfce, Openbox and Twm. With both Plasma and Xfce the screen is totally black. In all cases it is possible to use Control+Alt+F2 to go to a text console and use that. Generally it is possible to kill and restart X to get a usable GUI again. I'm reporting this as a kernel bug because if I boot Ubuntu 21.04 with linux-image-5.8.0-48-generic from Ubuntu 20.10, then X works after wake from sleep. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-13-generic 5.11.0-13.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:20:38 2021 HibernationDevice: RESUME=UUID=2d7284cc-d0df-45d7-b0a1-e5a0a8128eb8 InstallationDate: Installed on 2012-01-19 (3362 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /:
[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I found a way to trigger the problem fast (within one minute). On Raspberry Pi 3 B+: * Enable IPv4 forwarding: sysctl net.ipv4.ip_forward=1 * Enable masquerading: iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE * Start a netcat listening process: sudo nc -l -p 1234 > /dev/null On another machine: * Configure IPv4 address manually setting Raspberry Pi as gateway * Open browser and load some web pages to test routing * Send data to Raspberry Pi: nc RASPI_IP 1234 < /dev/zero * Parallel browsing now leads to network crash on Raspberry Pi. A few seconds later the kernel warining appears: NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Both machines are connected via ethernet to a 100MBit router. I tested the following hardware: * Raspberry Pi 2 Model B v1.1: no crash * Raspberry Pi 3 Model B+: crash * Raspberry Pi 4 Model B (4 GB): no crash $ uname -a Linux ubuntu 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:19:55 UTC 2020 armv7l armv7l armv7l GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) Status in linux-raspi package in Ubuntu: Incomplete Status in linux-raspi2 package in Ubuntu: Incomplete Status in linux-raspi2 source package in Eoan: Won't Fix Status in linux-raspi source package in Focal: Confirmed Bug description: Desciption changed: Raspberry Pi 3 network partially dies (transmission doesn't work, reception still does) shortly after a burst of network load over IPv6, when IPv6 connectivity is provided by a tunnel from tunnelbroker.net. The triggering load is typically an HTTP(S) download, and replication can be done without actually saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 GB, usually withinthe first 1 GB of traffic) Replication is 100% as long as _all_ of the following conditions are met - 6in4 tunnel to HE.net set up with netplan - ipv6 rules applied (netfilter-persistent) - ipv6 forwarding enabled (edit /etc/sysctl.conf) kern.log message that appears after a while: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 :
[Kernel-packages] [Bug 1733607] Re: ubuntu
** Bug watch added: Email to milanovic.boris90@gmail # mailto:milanovic.bori...@gmail.com ** Also affects: linux via mailto:milanovic.bori...@gmail.com Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733607 Title: ubuntu Status in Linux: New Status in linux package in Ubuntu: Expired Bug description: allan@allan-ThinkPad-T440p:~$ su Mot de passe : root@allan-ThinkPad-T440p:/home/allan# ubuntu-bug linux (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (apport-gtk:5335): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed root@allan-ThinkPad-T440p:/home/allan# (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (firefox:5976): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: La connexion est fermée (firefox:5976): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (firefox:5976): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (firefox:5976): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (firefox:5976): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed ^C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-101-generic 4.4.0-101.124 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture:
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
I don't see a null pointer message but the b44 driver is still broken in 5.4.0-33-generic on my Dell Inspiron 6400: [ 3148.539194] ssb: Found chip with id 0x4401, rev 0x02 and package 0x00 [ 3148.599317] b44 :03:00.0: Sonics Silicon Backplane found on PCI device :03:00.0 [ 3148.599414] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0 [ 3148.627839] b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:15:c5:b3:8a:ba [ 3148.684246] swiotlb_tbl_map_single: 14 callbacks suppressed [ 3148.684251] b44 :03:00.0: swiotlb buffer is full (sz: 1566 bytes), total 0 (slots), used 0 (slots) [ 3148.684261] [ cut here ] [ 3148.684267] WARNING: CPU: 0 PID: 36638 at kernel/dma/direct.c:35 report_addr+0x37/0x60 [ 3148.684268] Modules linked in: b44 mii iptable_filter bpfilter ccm b43 dell_laptop dell_smm_hwmon snd_hda_codec_hdmi cordic kvm snd_hda_codec_idt snd_hda_codec_generic bcma ledtrig_audio radeon dell_wmi snd_hda_intel snd_intel_dspcfg dell_smbios dcdbas input_leds joydev mac80211 snd_hda_codec r852 sparse_keymap wmi_bmof serio_raw dell_wmi_descriptor ttm sm_common snd_hda_core nand snd_hwdep drm_kms_helper nand_ecc snd_pcm cfg80211 bch i2c_algo_bit snd_timer fb_sys_fops r592 nandcore mtd memstick syscopyarea sysfillrect snd libarc4 sysimgblt soundcore mac_hid sch_fq_codel coretemp parport_pc ppdev lp parport drm ip_tables x_tables autofs4 ssb_hcd gpio_ich pata_acpi i2c_i801 psmouse lpc_ich firewire_ohci sdhci_pci cqhci firewire_core sdhci crc_itu_t ssb wmi video [ 3148.684314] CPU: 0 PID: 36638 Comm: NetworkManager Not tainted 5.4.0-33-generic #37-Ubuntu [ 3148.684315] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 [ 3148.684318] RIP: 0010:report_addr+0x37/0x60 [ 3148.684320] Code: 48 8b 87 28 02 00 00 48 89 75 f8 48 85 c0 74 2a 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 11 80 3d db c3 71 01 00 0f 84 7d 07 00 00 <0f> 0b c9 c3 48 83 bf 38 02 00 00 00 74 f2 eb e3 80 3d bf c3 71 01 [ 3148.684321] RSP: 0018:9ae68055b450 EFLAGS: 00010246 [ 3148.684323] RAX: fffe RBX: RCX: [ 3148.684324] RDX: 061e RSI: 6b440a80 RDI: 8cb34b4db0b0 [ 3148.684325] RBP: 9ae68055b458 R08: 3fff R09: 0004 [ 3148.684327] R10: R11: 0001 R12: 8cb2f8b0c000 [ 3148.684328] R13: 061e R14: 8cb2f45cef00 R15: 8cb2f96ac8c0 [ 3148.684330] FS: 7f02e05ca240() GS:8cb34c60() knlGS: [ 3148.684331] CS: 0010 DS: ES: CR0: 80050033 [ 3148.684333] CR2: 7f5935e43f28 CR3: c6128000 CR4: 06f0 [ 3148.684334] Call Trace: [ 3148.684340] dma_direct_map_page+0xdc/0xf0 [ 3148.684347] b44_alloc_rx_skb+0x1bb/0x4a0 [b44] [ 3148.684348] ? dma_direct_alloc_pages+0x93/0x130 [ 3148.684351] b44_init_rings+0xb8/0x190 [b44] [ 3148.684354] b44_open+0xfc/0x470 [b44] [ 3148.684357] __dev_open+0xd4/0x170 [ 3148.684359] __dev_change_flags+0x191/0x1f0 [ 3148.684361] dev_change_flags+0x26/0x60 [ 3148.684364] do_setlink+0x82e/0x980 [ 3148.684368] ? cpumask_next+0x1b/0x20 [ 3148.684371] ? __snmp6_fill_stats64.isra.0+0xe7/0x110 [ 3148.684375] ? __nla_validate_parse+0x42/0x140 [ 3148.684377] __rtnl_newlink+0x580/0x970 [ 3148.684380] ? __nla_put+0x20/0x30 [ 3148.684383] ? __kmalloc_node_track_caller+0x205/0x320 [ 3148.684385] ? pskb_expand_head+0x75/0x2d0 [ 3148.684387] ? __kmalloc_reserve.isra.0+0x31/0x90 [ 3148.684391] ? security_sock_rcv_skb+0x2f/0x50 [ 3148.684393] ? sk_filter_trim_cap+0x48/0x220 [ 3148.684395] ? skb_queue_tail+0x43/0x50 [ 3148.684397] ? __netlink_sendskb+0x42/0x50 [ 3148.684401] ? security_capable+0x3d/0x60 [ 3148.684404] ? _cond_resched+0x19/0x30 [ 3148.684406] ? kmem_cache_alloc_trace+0x16c/0x240 [ 3148.684408] rtnl_newlink+0x49/0x70 [ 3148.684410] rtnetlink_rcv_msg+0x2c0/0x380 [ 3148.684413] ? vsnprintf+0x35d/0x4e0 [ 3148.684414] ? rtnl_calcit.isra.0+0x100/0x100 [ 3148.684416] netlink_rcv_skb+0x50/0x120 [ 3148.684418] rtnetlink_rcv+0x15/0x20 [ 3148.684420] netlink_unicast+0x187/0x220 [ 3148.684422] netlink_sendmsg+0x222/0x3e0 [ 3148.684425] sock_sendmsg+0x65/0x70 [ 3148.684426] sys_sendmsg+0x212/0x280 [ 3148.684429] ___sys_sendmsg+0x88/0xd0 [ 3148.684431] ? rtnl_unlock+0xe/0x10 [ 3148.684433] ? addrconf_sysctl_forward+0x111/0x280 [ 3148.684436] ? get_max_files+0x20/0x20 [ 3148.684439] ? __fget_light+0x57/0x70 [ 3148.684441] __sys_sendmsg+0x5c/0xa0 [ 3148.68] __x64_sys_sendmsg+0x1f/0x30 [ 3148.684447] do_syscall_64+0x57/0x190 [ 3148.684450] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3148.684452] RIP: 0033:0x7f02e1a3b12d [ 3148.684454] Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 ca ee ff ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 48 89 44 24 08 e8 fe ee ff ff 48 [ 3148.684455] RSP: 002b:7fffaac61a40 EFLAGS:
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
iommu=soft does not help, and I don't understand why it would help theoretically when the Core 2 Duo T7400 CPU doesn't have a hardware IOMMU. The problem seems to be that the 64 MB buffer is allocated beyond 1 GB. One theoretical good workaround would be to boot up with only 1 GB and then enable the rest of memory. But I'm not sure how to do that. -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI:
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
This problem still exists in Ubuntu Focal Fossa (development branch) 20.04 with linux-image-5.4.0-21-generic. It also exists in linux-image- unsigned-5.6.2-050602-generic_5.6.2-050602.202004020822_amd64.deb With linux-image-5.4.0-21-generic I didn't get any error messages after "insmod b44" in recovery mode. Also I normally booted linux- image-5.4.0-21-generic with mem=1G (limiting available memory to 1 GB) twice and also didn't get error messages after "sudo insmod b44". These symptoms are consistent with the hypothesis that swiotlb bounce buffers normally get allocated above 1 GB, causing a problem for b44 because the device can't do DMA above 1 GB and the driver can't handle this situation. That's the same problem discussed in this thread from 2011 https://groups.google.com/forum/#!topic/linux.kernel/GEx80ZCue1o Obviously limiting memory to 1 GB has an unacceptable performance penalty, but it's nice to have at least one way to get working Ethernet. -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60
[Kernel-packages] [Bug 1860954] [NEW] b43 WiFi monitor mode doesn't work with BCM4321 card
Public bug reported: My Inspiron 6400 laptop has a Dell Wireless 1500 Draft 802.11n WLAN Mini-Card with BCM4321 chip. I was using airmon-ng from aircrack-ng to enter monitor mode. It claims the chipset is "non-mac80211 device? (report this!)" but I think that's incorrect information and only cosmetic. It does create the monitor device. Then I was using Wireshark to capture packets from that device. I was only getting beacon, probe request and probe response packets, despite knowing that there was data on the network. As a workaround, it is possible to properly monitor by using a different driver, from the broadcom-sta-dkms package. After installing that package and rebooting, I couldn't connect to my wireless network anymore, but I could "echo 1 | sudo tee /proc/brcm_monitor0" to create a prism0 device. Changing channels was a problem, maybe requiring a change on the associated non-monitor device before enabling the monitor. But capture on prism0 worked great. I was getting all kinds of packets and was able to decrypt data in Wireshark after enabling "Assume packets have FCS". Even though I couldn't connect to my network, I could capture and decrypt its traffic. Rebooting seems required for switching from b43 to wl drivers, because otherwise the wl driver doesn't start properly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-26-generic. ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1492 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 22 Simple ctrls : 9 CurrentDesktop: XFCE Date: Mon Jan 27 00:09:29 2020 HibernationDevice: RESUME=UUID=62d89c78-536c-42ab-968d-463122f8c3a2 InstallationDate: Installed on 2012-01-19 (2930 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda6 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (94 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- 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/1860954 Title: b43 WiFi monitor mode doesn't work with BCM4321 card Status in linux package in Ubuntu: Confirmed Bug description: My Inspiron 6400 laptop has a Dell Wireless 1500 Draft 802.11n WLAN Mini-Card with BCM4321 chip. I was using airmon-ng from aircrack-ng to enter monitor mode. It claims the chipset is "non-mac80211 device? (report this!)" but I think that's incorrect information and only cosmetic. It does create the monitor device. Then I was using Wireshark to capture packets from that device. I was only getting beacon, probe request and probe response packets, despite knowing that there was data on the network. As a workaround, it is possible to properly monitor by using a different driver, from the broadcom-sta-dkms package. After installing that package and rebooting, I couldn't connect to my wireless network anymore, but I could "echo 1 | sudo tee /proc/brcm_monitor0" to create a prism0 device. Changing channels was a problem, maybe requiring a change on the associated non-monitor device before enabling the monitor. But capture on prism0 worked great. I was getting
[Kernel-packages] [Bug 1860938] [NEW] Sound interruptions during high radeon OpenGL load
Public bug reported: On my Dell Inspiron 6400 laptop with Mobility Radeon X1400 and built in Intel HDA audio with STAC9200 codec, audio is normally perfect. Even with 100% load on both CPU cores audio is perfect. However, while playing high resolution video, audio has many tiny regular interruptions which can be like crackles or micro stuttering. This happens when playing 1080p YouTube video in Chrome or 1080p video via VLC using the OpenGL output. Other high GPU load, like scrolling Google Maps around a lot in Chrome, can also cause these interruptions. They don't only affect the application causing graphical load, but also affect other applications playing audio, like mpg123. I've changed bdl_pos_adj, position_fix and enable_msi parameters of the snd_hda_intel module. Maybe bdl_pos_adj=64 and position_fix=1 makes it a bit better, but I'm not certain and it's certainly still not okay. I tried interrupt priorities as described in https://wiki.ubuntu.com/UbuntuStudio/rtirq and that didn't help. Changing latency via setpci seems not applicable because this laptop uses PCI Express. Not running PulseAudio and using ALSA instead doesn't help. Running a bare-bones X configuration with twm doesn't help. Configuring VLC to use XVideo video output makes audio perfect with the same video which was causing these interruptions when using OpenGL video output. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-26-generic. ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 1646 F pulseaudio /dev/snd/pcmC0D0p: bgjenero 1646 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 22 Simple ctrls : 9 CurrentDesktop: XFCE Date: Sun Jan 26 16:45:23 2020 HibernationDevice: RESUME=UUID=62d89c78-536c-42ab-968d-463122f8c3a2 InstallationDate: Installed on 2012-01-19 (2929 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=d590f141-7b8d-421d-84b3-baa43181a241 ro resume=/dev/sda6 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-25 (93 days ago) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1860938 Title: Sound interruptions during high radeon OpenGL load Status in linux package in Ubuntu: New Bug description: On my Dell Inspiron 6400 laptop with Mobility Radeon X1400 and built in Intel HDA audio with STAC9200 codec, audio is normally perfect. Even with 100% load on both CPU cores audio is perfect. However, while playing high resolution video, audio has many tiny regular interruptions which can be like crackles or micro stuttering. This happens when playing 1080p YouTube video in Chrome or 1080p video via VLC using the OpenGL output. Other high GPU load, like scrolling Google Maps around a lot in Chrome, can also cause these interruptions. They don't only affect the application causing graphical load, but also affect other applications playing audio, like mpg123. I've changed bdl_pos_adj, position_fix and enable_msi parameters of the snd_hda_intel module. Maybe bdl_pos_adj=64 and position_fix=1 makes it a bit better, but I'm not certain and it's certainly
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
I don't normally use Ethernet on my laptop, and for some reason the b44 module for Ethernet doesn't get loaded normally. So I didn't notice this. But I'm getting the same problem reported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/comments/8 in Ubuntu 19.10 with linux-image-5.3.0-24-generic on my Inspiron 6400. This Debian bug report has some ideas about a cause: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939697 ** Bug watch added: Debian Bug tracker #939697 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939697 -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
linux-image- unsigned-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb is good but linux-image- unsigned-5.0.0-05rc1-generic_5.0.0-05rc1.201901062130_amd64.deb is bad. I'm not sure I'll have time for a git bisect. -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09:
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
Sorry, I mean bug is not present in 4.18.0-16-generic and present in 5.0.0-7-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14: 7ffe93a35e7c R15:
[Kernel-packages] [Bug 1821564] [NEW] b44 Ethernet driver null pointer during initialization
Public bug reported: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14: 7ffe93a35e7c R15: 6.485518] Modules linked in: arc4 b43 cordic snd_hda_codec_hdmi ttm bcma dell_laptop snd_hda_codec_idt snd_hda_codec_generic dell_smm_hwmon drm_kms_helper dell_wmi ledtrig_audio snd_hda_intel kvm mac80211 dell_smbios dcdbas drm joydev snd_hda_codec r852 irqbypass input_leds sm_common sparse_keymap wmi_bmof dell_wmi_descriptor snd_hda_core i2c_algo_bit snd_hwdep cfg80211 serio_raw snd_pcm nand fb_sys_fops snd_timer r592 syscopyarea nand_ecc snd nand_bch sysfillrect soundcore sysimgblt bch memstick mtd
[Kernel-packages] [Bug 1813769] [NEW] System crash with dual monitor setup
Public bug reported: Laptop crashes after successfully login with 2nd monitor attached. If I attach the monitor after login system crashes when changing display settings , e.g. monitor positions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: b 1883 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 15:32:04 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-30 (90 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20JWS09Q00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=9354306a-00ba-43a3-85ce-209a58d47604 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET45W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JWS09Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET45W(1.35):bd07/12/2018:svnLENOVO:pn20JWS09Q00:pvrThinkPadT570W10DG:rvnLENOVO:rn20JWS09Q00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T570 W10DG dmi.product.name: 20JWS09Q00 dmi.product.version: ThinkPad T570 W10DG dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813769 Title: System crash with dual monitor setup Status in linux package in Ubuntu: New Bug description: Laptop crashes after successfully login with 2nd monitor attached. If I attach the monitor after login system crashes when changing display settings , e.g. monitor positions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: b 1883 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 15:32:04 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-30 (90 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20JWS09Q00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=9354306a-00ba-43a3-85ce-209a58d47604 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET45W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JWS09Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET45W(1.35):bd07/12/2018:svnLENOVO:pn20JWS09Q00:pvrThinkPadT570W10DG:rvnLENOVO:rn20JWS09Q00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T570 W10DG dmi.product.name: 20JWS09Q00 dmi.product.version: ThinkPad T570 W10DG dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813769/+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 1795653] Re: 87cdf3148b11 was never backported to 4.15
I didn't had time to test again the kernel but a fast fix would be
kernel upgrade to 4.17 or newer version.
--
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/1795653
Title:
87cdf3148b11 was never backported to 4.15
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
Commit 87cdf3148b11 fixes a regression introduced by commit
5efec5c655dd. However, it has not never landed in Bionic. Requesting
this commit in Bionic, so we don't have to wait for it to come down from
upstream stable.
== Fix ==
87cdf3148b11 ("xfrm: Verify MAC header exists before overwriting
eth_hdr(skb)->h_proto")
== Regression Potential ==
Low. This commit fixes and existing regression by making sure teh MAC
header exists.
== 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.
Hello,
After a few days of troubleshooting a problem with L2TP and IPSec a
fellow from ServerFault pointed out that my problem is a known bug
fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel.
Ubuntu 4.15.0-36.39-generic 4.15.18
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795653/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Kai-Heng @kaihengfeng, Kernel from #187 doesn't work after Suspend on Ubuntu 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@elpraga, @kaihengfeng I can confirm that touchpad works perfectly with kernel from #162 on Chuwi Lapbook Air, Ubuntu 18.04. Please find attached dmesg for it. Is there anyhow I can help further to resolve this issue? ** Attachment added: "Dmesg for Kernel from #162. Touchpad is working." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5201683/+files/417.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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hi, Kai-Heng @kaihengfeng Please find attached dmesg file. This is with kernel from comment #187. Should I file a new bug from it? @elpraga, thank you. I wil try kernel from comment #162 and write back my testing results here. ** Attachment added: "Dmesg from Kernel from #187. Touchpad not working" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5201619/+files/dmesgUrmanChuwiTouchpadnotworking.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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hi, Hans/Kai-Heng Feng I tried kernel from comment #187 on Chuwi Lapbook Air 14.1 with touchpad HID\ALPS0001. It doesn't work for me completely - neither trackpad nor buttons. Is there anyhow I can help troubleshoot this issue? BTW. Hans, thank you for your support and answers in my previous question. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1795653] Re: 87cdf3148b11 was never backported to 4.15
Hello Joseph, I have checked with lp1795653 build and my problem is solved. IPSec packets are not translated anymore when passing thru a L2 tunnel. Thanks, Boris -- 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/1795653 Title: 87cdf3148b11 was never backported to 4.15 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Hello, After a few days of troubleshooting a problem with L2TP and IPSec a fellow from ServerFault pointed out that my problem is a known bug fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel. Ubuntu 4.15.0-36.39-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795653/+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 1795653] Re: 87cdf3148b11 was never backported to 4.15
Hi Joseph, Thank you for your fast response. I will be able to test it only next week as I am out of office until Monday. Bests, Boris -- 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/1795653 Title: 87cdf3148b11 was never backported to 4.15 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Hello, After a few days of troubleshooting a problem with L2TP and IPSec a fellow from ServerFault pointed out that my problem is a known bug fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel. Ubuntu 4.15.0-36.39-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795653/+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 1795653] [NEW] 87cdf3148b11 was never backported to 4.15
Public bug reported: Hello, After a few days of troubleshooting a problem with L2TP and IPSec a fellow from ServerFault pointed out that my problem is a known bug fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel. Ubuntu 4.15.0-36.39-generic 4.15.18 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795653 Title: 87cdf3148b11 was never backported to 4.15 Status in linux package in Ubuntu: Incomplete Bug description: Hello, After a few days of troubleshooting a problem with L2TP and IPSec a fellow from ServerFault pointed out that my problem is a known bug fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel. Ubuntu 4.15.0-36.39-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795653/+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 1777238] Re: video lag
This is getting really bad. I can't even type without the screen freezing momentarily! What information would be most useful to diagnose the problem? How do I collect it? How do I add it to the ticket? -- 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/1777238 Title: video lag Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1777238/+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 1777238] Re: video lag
Running the system monitor as suggested by Jon had no effect. Doing a cold boot reduced the problem tempoarily. -- 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/1777238 Title: video lag Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1777238/+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 1777238] Re: video lag
After a couple of weeks without issues, thanks to changing the v-sync in compris, it is back and getting progressively worse. Will try running system monitor and see if this helps. -- 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/1777238 Title: video lag Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1777238/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@bbaker6212 Hi, Brad Thank you for quick answer. Touchpad model is HID\ALPS0001. Laptop is Chuwi Lapbook Air 14.1. I tried linux kernel 4.18rc8 with Ubuntu 18.04 today and touchpad didn't work at all there. Could you please guide me on how to make it work? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1777238] Re: video lag
Hi Zoltan. This computer (HP Envy 17 Leap Motion SE) is a fresh install of 18.04. I upgraded my Dell Inspiron from 16.04 and don't have the issue. Very weird. -- 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/1777238 Title: video lag Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1777238/+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 1777238] Re: video lag
After posting the above, I found https://www.youtube.com/watch?v=cIQZv6MXzno. The first solution (uncheking v-sync, log out, log in) seems to be working. -- 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/1777238 Title: video lag Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1777238/+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 1777238] Re: video lag
The lag is everywhere for me, not just in video. Screen scrolling also has this stutter. -- 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/1777238 Title: video lag Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1777238/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hi, does anyone know when this bug will be fixed? I really would love to use Ubuntu on my Chuwi Lapbook Air but I can't because touchpad doesn't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
Since 16.04.4 LTS with Kernel 4.4.0-128-generic/x86_64 the problems seems to be fixed. Our VM with more than one VHD are running without problems for two weeks now. Neither backups nor cluster failovers are crashing the VM. -- 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/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless
[Kernel-packages] [Bug 1763967] Re: rmmod b43 hangs
rmmod b43 works in 4.15.0-21-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763967
Title:
rmmod b43 hangs
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43"
always hangs. So far I have only tried it while connected to a
wireless network. I immediately disconnect from the wireless network,
so it seems module removal does begin. But the rmmod process never
finishes and is unkillable. The hang seems indefinite, and a normal
reboot is not possible, the rapid ctrl-alt-del systemd emergency
reboot is impossible, and only a Magic SysRq reboot works.
This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04.
(I was unloading the module before suspend due to occasional problems
after resume. I tracked this down when wondering why suspend was
hanging. Even running the "rmmod b43" on its own without suspend
happening causes the hang. Right now I disabled that automatic
unloading.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-13-generic.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1560 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CurrentDesktop: XFCE
Date: Sat Apr 14 11:54:36 2018
HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
InstallationDate: Installed on 2012-01-19 (2277 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MM061
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware 1.173
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-11 (34 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763967/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hi, I tried Ubuntu 160404 and Ubuntu 1804 beta 2 on Chuwi Lapboo air with live usb. On both of them touchpad didn't work. I am not very experienced with linux environment yet. Is there way for me to contribute in solving this problem& -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hi, is there any progress on this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1763967] Re: rmmod b43 hangs
Bug does not exist in 4.16.2-041602-generic. I did rmmod b43 4 times and
it always succeeded immediately. It never worked properly in
4.15.0-13-generic so I am confident this isn't just random success, and
it means the bug is fixed in upstream.
What older version should I try? Currently I don't have any old versions
available.
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763967
Title:
rmmod b43 hangs
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43"
always hangs. So far I have only tried it while connected to a
wireless network. I immediately disconnect from the wireless network,
so it seems module removal does begin. But the rmmod process never
finishes and is unkillable. The hang seems indefinite, and a normal
reboot is not possible, the rapid ctrl-alt-del systemd emergency
reboot is impossible, and only a Magic SysRq reboot works.
This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04.
(I was unloading the module before suspend due to occasional problems
after resume. I tracked this down when wondering why suspend was
hanging. Even running the "rmmod b43" on its own without suspend
happening causes the hang. Right now I disabled that automatic
unloading.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-13-generic.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1560 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CurrentDesktop: XFCE
Date: Sat Apr 14 11:54:36 2018
HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
InstallationDate: Installed on 2012-01-19 (2277 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MM061
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware 1.173
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-11 (34 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763967/+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 1763967] [NEW] rmmod b43 hangs
Public bug reported:
I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43" always
hangs. So far I have only tried it while connected to a wireless
network. I immediately disconnect from the wireless network, so it seems
module removal does begin. But the rmmod process never finishes and is
unkillable. The hang seems indefinite, and a normal reboot is not
possible, the rapid ctrl-alt-del systemd emergency reboot is impossible,
and only a Magic SysRq reboot works.
This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04.
(I was unloading the module before suspend due to occasional problems
after resume. I tracked this down when wondering why suspend was
hanging. Even running the "rmmod b43" on its own without suspend
happening causes the hang. Right now I disabled that automatic
unloading.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-13-generic.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1560 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CurrentDesktop: XFCE
Date: Sat Apr 14 11:54:36 2018
HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
InstallationDate: Installed on 2012-01-19 (2277 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MM061
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware 1.173
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-11 (34 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763967
Title:
rmmod b43 hangs
Status in linux package in Ubuntu:
New
Bug description:
I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43"
always hangs. So far I have only tried it while connected to a
wireless network. I immediately disconnect from the wireless network,
so it seems module removal does begin. But the rmmod process never
finishes and is unkillable. The hang seems indefinite, and a normal
reboot is not possible, the rapid ctrl-alt-del systemd emergency
reboot is impossible, and only a Magic SysRq reboot works.
This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04.
(I was unloading the module before suspend due to occasional problems
after resume. I tracked this down when wondering why suspend was
hanging. Even running the "rmmod b43" on its own without suspend
happening causes the hang. Right now I disabled that automatic
unloading.)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-13-generic.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
[Kernel-packages] [Bug 1754911] Re: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
In 4.15.0-13-generic, BCM4321 WiFi works via b43 and BCM4401-B0 b44
Ethernet eth0 exists. So, it seems this has been fixed. Thank you.
--
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/1754911
Title:
b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
When I boot linux-image-4.13.0-36-generic then I get an eth0 interface
and dmesg output includes:
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42
43)
b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00
When I boot linux-image-4.15.0-10-generic those lines don't appear and
I don't get an eth0 interface. Doing modprobe b44 doesn't help.
This is on a Dell Inspiron 6400. I wonder if I'm running into this
bug: https://patchwork.kernel.org/patch/10185397/
I'm reporting it while running linux-image-4.13.0-36-generic because I
also can't get wireless to work in 4.15, so I can't report from there.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-36-generic.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1449 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CurrentDesktop: XFCE
Date: Sat Mar 10 20:55:15 2018
HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
InstallationDate: Installed on 2012-01-19 (2243 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
JournalErrors:
-- Logs begin at Sat 2018-03-10 18:57:57 EST, end at Sat 2018-03-10 20:55:01
EST. --
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus:
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus: Failed to construct
signal
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MM061
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.172
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754911/+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 1754911] Re: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.9/ I installed:
linux-headers-4.15.9-041509_4.15.9-041509.201803111231_all.deb
linux-headers-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb
linux-image-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb
And booted into 4.15.9-041509-generic on my Inspiron 6400.
BCM4321 WiFi works via b43 and BCM4401-B0 b44 Ethernet eth0 exists. In
other words, this bug does not exist in 4.15.9-041509-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1754911
Title:
b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
When I boot linux-image-4.13.0-36-generic then I get an eth0 interface
and dmesg output includes:
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42
43)
b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00
When I boot linux-image-4.15.0-10-generic those lines don't appear and
I don't get an eth0 interface. Doing modprobe b44 doesn't help.
This is on a Dell Inspiron 6400. I wonder if I'm running into this
bug: https://patchwork.kernel.org/patch/10185397/
I'm reporting it while running linux-image-4.13.0-36-generic because I
also can't get wireless to work in 4.15, so I can't report from there.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-36-generic.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1449 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CurrentDesktop: XFCE
Date: Sat Mar 10 20:55:15 2018
HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
InstallationDate: Installed on 2012-01-19 (2243 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
JournalErrors:
-- Logs begin at Sat 2018-03-10 18:57:57 EST, end at Sat 2018-03-10 20:55:01
EST. --
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus:
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus: Failed to construct
signal
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MM061
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.172
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754911/+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 1754911] Re: b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
After installing
linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb ,
linux-headers-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
and
linux-image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4/ and booting
4.16.0-041600rc4-generic I have eth0. So, apparently this is fixed in later
kernel versions.
I am still encountering
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752081 "platform
regulatory.0: Direct firmware load for regulatory.db failed with error
-2" but wireless now works nevertheless. I originally reported this bug
for the wired Ethernet interface because I wasn't sure if that other bug
was causing wireless to not work. Now I'm thinking this same bug was
probably making wireless not work either.
--
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/1754911
Title:
b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
Status in linux package in Ubuntu:
Confirmed
Bug description:
When I boot linux-image-4.13.0-36-generic then I get an eth0 interface
and dmesg output includes:
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42
43)
b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00
When I boot linux-image-4.15.0-10-generic those lines don't appear and
I don't get an eth0 interface. Doing modprobe b44 doesn't help.
This is on a Dell Inspiron 6400. I wonder if I'm running into this
bug: https://patchwork.kernel.org/patch/10185397/
I'm reporting it while running linux-image-4.13.0-36-generic because I
also can't get wireless to work in 4.15, so I can't report from there.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-36-generic.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1449 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CurrentDesktop: XFCE
Date: Sat Mar 10 20:55:15 2018
HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
InstallationDate: Installed on 2012-01-19 (2243 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
JournalErrors:
-- Logs begin at Sat 2018-03-10 18:57:57 EST, end at Sat 2018-03-10 20:55:01
EST. --
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus:
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus: Failed to construct
signal
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MM061
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.172
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754911/+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 1754911] [NEW] b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
Public bug reported:
When I boot linux-image-4.13.0-36-generic then I get an eth0 interface
and dmesg output includes:
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42
43)
b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00
When I boot linux-image-4.15.0-10-generic those lines don't appear and I
don't get an eth0 interface. Doing modprobe b44 doesn't help.
This is on a Dell Inspiron 6400. I wonder if I'm running into this bug:
https://patchwork.kernel.org/patch/10185397/
I'm reporting it while running linux-image-4.13.0-36-generic because I
also can't get wireless to work in 4.15, so I can't report from there.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-36-generic.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1449 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CurrentDesktop: XFCE
Date: Sat Mar 10 20:55:15 2018
HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
InstallationDate: Installed on 2012-01-19 (2243 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
JournalErrors:
-- Logs begin at Sat 2018-03-10 18:57:57 EST, end at Sat 2018-03-10 20:55:01
EST. --
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus:
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Mar 10 20:40:53 hostname wpa_supplicant[669]: dbus: Failed to construct signal
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. MM061
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.172
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1754911
Title:
b44 Ethernet driver not working in Linux 4.15 on Inspiron 6400
Status in linux package in Ubuntu:
New
Bug description:
When I boot linux-image-4.13.0-36-generic then I get an eth0 interface
and dmesg output includes:
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42
43)
b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00
When I boot linux-image-4.15.0-10-generic those lines don't appear and
I don't get an eth0 interface. Doing modprobe b44 doesn't help.
This is on a Dell Inspiron 6400. I wonder if I'm running into this
bug: https://patchwork.kernel.org/patch/10185397/
I'm reporting it while running linux-image-4.13.0-36-generic because I
also can't get wireless to work in 4.15, so I can't report from there.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-36-generic.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
I can confirm: VMs with more than one disk still crash with out of memory. We're using Hyper-V on Windows Server 2012 R2 with GEN2 VMs (Ubuntu 16.04.3 LTS/Xenial, Kernel 4.4.0-104-generic). VMs with just one disk are running perfectly. -- 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/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono
[Kernel-packages] [Bug 1737522] [NEW] cfq scheduler can write parts of sequential write in reverse order
Public bug reported: I'm opening a raw disk device (like /dev/sdb) with O_DIRECT and then doing write() calls. The device is actually USB mass storage. Looking at the USB packets with Wireshark, I see that the write() calls are being split into multiple SCSI writes. That part is okay I guess. The problem is that these writes can happen in reverse order. Suppose the write() call is writing to sectors 100 to 200. The first SCSI write may write 150 to 200 and the second SCSI write may write 100 to 149. Correctness does appear to be maintained. I only had a problem with correctness because I'm abusing the protocol for writing to a hacked digital photo frame via https://github.com/dreamlayers/st220x/blob/master/libst2205/st2205.c . The photo frame doesn't fully process the protocol and only looks at the data as a series of USB packets. However, this is bad for performance with hard disks. Surely if you have a sequential write, the optimal way to do that write is sequentially from start to finish. Since changing the scheduler for that block device from cfq to noop fixes this problem, I assume it has to do with the elevator algorithm use to optimize hard disk access. But surely such optimization only makes sense between contiguous sequential writes, and not for splitting up one such write. 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 NonfreeKernelModules: nvidia_uvm nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-19-generic. ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2116 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfa20 irq 30' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 63 Simple ctrls : 26 CurrentDesktop: XFCE Date: Mon Dec 11 05:23:12 2017 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=52543c1b-1764-4766-a504-f4b94422fa6e ro 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-09-30 (71 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1737522 Title: cfq scheduler can write parts of sequential write in reverse order Status in linux package in Ubuntu: New Bug description: I'm opening a raw disk device (like /dev/sdb) with O_DIRECT and then doing write() calls. The device is actually USB mass storage. Looking at the USB packets with Wireshark, I see that the write() calls are being split into multiple SCSI writes. That part is okay I guess. The problem is that these writes can happen in reverse order. Suppose the write() call is writing to sectors 100 to 200. The first SCSI write may write 150 to 200 and the second SCSI write may write 100 to 149. Correctness does appear to be maintained. I only had a problem with correctness because I'm abusing the protocol for writing to a hacked digital photo frame via https://github.com/dreamlayers/st220x/blob/master/libst2205/st2205.c . The photo frame doesn't fully process the protocol and only looks at the data as a series of USB packets. However, this is bad for performance with hard disks. Surely if you have a sequential write, the optimal way to do that write is sequentially from start to finish. Since changing the scheduler for that block device from cfq to noop fixes this problem, I assume it has to do with the elevator algorithm use to optimize hard disk access. But surely such optimization only makes sense between contiguous sequential writes, and not for splitting up one such write. ProblemType: Bug DistroRelease: Ubuntu 17.10
[Kernel-packages] [Bug 1453404] Re: r8169 occasionally doesn't work after suspend
After upgrading to Ubuntu 16.10 I removed the r8168-dkms package so I could see if this bug still exists in 4.8.0 kernels. I upgraded on October 13th, and everything worked fine until today, October 24th. After waking from sleep eth0 appeared up according to ifconfig, but I had no connectivity and couldn't even ping other devices on the LAN. This fixed itself after ifconfig down followed by ifconfig up. I never had to do such a thing while using r8168-dkms. So, it seems the bug still exists, and I will reinstall r8168-dkms now. -- 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/1453404 Title: r8169 occasionally doesn't work after suspend Status in linux package in Ubuntu: Expired Bug description: Occasionally the onboard gigabit Ethernet on this Gigabyte GA-P35-DS3R rev 1.0 motherboard doesn't work after suspend. This happens less than one out of ten times. This was the first time this bug happened in Ubuntu 15.04. WORKAROUND: sudo ifconfig eth0 down && sudo ifconfig eth0 up WORKAROUND: Unload and reload the r8169 module. WORKAROUND: I'm installing the r8168-dkms package, which includes the proprietary Realtek driver. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2673 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sat May 9 10:57:05 2015 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 InstallationDate: Installed on 2012-01-19 (1206 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (15 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453404/+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 1479136] Re: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards
I wonder if this is the same bug which I am seeing on my Dell Inspiron 6400 laptop with Radeon X1400 video. Occasionally I get white lines which are very similar to the https://www.youtube.com/watch?v=nx2-Fvihzxg video posted at the beginning. The only difference is that more lines are present at screen edges and high contrast borders. Line length and the way they flicker is very similar. This problem has been present over multiple Ubuntu versions, and is still present in 64-bit Ubuntu 16.10 with kernel 4.8.0-26-generic. In the past I posted about the problem at: https://ubuntuforums.org/showthread.php?t=2322535 Sometimes I've gotten worse corruption like how Ivan Zakharyaschev (imz) wrote "sometimes the flickering did appear as some regions (with text) displayed at another place on the screen appearing extremely quickly and transparently also at a wrong places at the top." This is more rare than the white lines, and has not happened in Ubuntu 16.10 yet. Changing video modes can start or stop corruption. So, if I have corruption, run a script which uses xrandr to change to a lower resolution and back to the native resolution. This usually works in one try but sometimes takes a few tries. The problem happens rarely enough that it's not a big deal, but a fix would be nice. -- 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/1479136 Title: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards Status in linux package in Ubuntu: Fix Committed Bug description: Ubuntu-Mate 14.04.2 This is what I get if I run a kernel newer than 3.13: https://www.youtube.com/watch?v=nx2-Fvihzxg sorry for the link, I just don't know how to describe these artefacts verbally. (a storm of small horizontal moving blips from right to left ??) Those artefacts appear as soon as new kernel is selected in GRUB, and remain during the whole session. The lastest kernel (from the main repository that is) working without artifacts is v3.13.0.59. All later kernels have artifacts. All later kernels also are either "-utopic" or "-vivid" instead of "-trusty", but I do not know if it is related. GPU: Mobility Radeon HD 3200 (RS780M) System: Ubuntu Mate 14.04.2 32-bit Kernels tested: 3.13.0.59 (and earlier) , 3.16.0.45 , 3.19.0.25 Only 3.13.0.59 (and earlier) are without problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479136/+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 1610622] Re: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f address=0x00000000bec09880 flags=0x0010]
** Changed in: linux (Ubuntu) Status: Expired => 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/1610622 Title: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f address=0xbec09880 flags=0x0010] Status in linux package in Ubuntu: Confirmed Bug description: [ 19.880847] xhci_hcd :02:00.0: can't setup: -110 [ 19.880915] clocksource: Switched to clocksource tsc [ 19.880919] xhci_hcd :02:00.0: USB bus 8 deregistered [ 19.880979] xhci_hcd :02:00.0: init :02:00.0 fail, -110 [ 19.881033] xhci_hcd: probe of :02:00.0 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hitkliv1854 F pulseaudio /dev/snd/controlC2: hitkliv1854 F pulseaudio /dev/snd/controlC0: hitkliv1854 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sun Aug 7 09:38:17 2016 HibernationDevice: RESUME=UUID=4c30b323-8466-484e-bca4-99052a00ff77 InstallationDate: Installed on 2016-08-06 (0 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=UUID=96a76e70-0ed0-478e-8558-7f0cffe4782d ro rootflags=subvol=@ quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1610622/+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 1631126] [NEW] package linux-image-extra-4.4.0-38-generic (not installed) failed to install/upgrade: no hay instalado ningún paquete llamado `linux-image-extra-4.4.0-38-generic'
Public bug reported:
Al actualizar mi ubuntu al linux-image-extra-4.4.0-38 no reconoce a mis
tarjetas de red, video o sonido pero al hacer un lspci se listan los
dispositivos.
actualmente estoy trabajando con el linux-image-extra-4.4.0-36 que si
puedo trabajar con ello pero con eso no puedo actualizar el sistema.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-38-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1915 F pulseaudio
boris 2340 F pulseaudio
Date: Thu Oct 6 15:01:24 2016
DpkgHistoryLog:
Start-Date: 2016-10-06 15:01:09
Commandline: apt-get -f install
Requested-By: boris (1000)
Install: linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57, automatic)
DpkgTerminalLog:
Preparando para desempaquetar
.../linux-image-extra-4.4.0-38-generic_4.4.0-38.57_amd64.deb ...
Desempaquetando linux-headers-4.4.0-38 (4.4.0-38.57) sobre (4.4.0-38.57) ...
dpkg: error al procesar el paquete linux-image-extra-4.4.0-38-generic
(--configure):
no hay instalado ningún paquete llamado `linux-image-extra-4.4.0-38-generic',
no se puede configurar
ErrorMessage: no hay instalado ningún paquete llamado
`linux-image-extra-4.4.0-38-generic', no se puede configurar
HibernationDevice: RESUME=UUID=ff500f4f-be28-4f2f-9bff-8944ef590901
InstallationDate: Installed on 2016-06-21 (107 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64
(20160421)
MachineType: Hewlett-Packard HP ENVY Sleekbook 4 PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed
root=UUID=244e0f86-6a47-47f5-8a60-563bcb8f3258 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.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-extra-4.4.0-38-generic (not installed) failed to
install/upgrade: no hay instalado ningún paquete llamado
`linux-image-extra-4.4.0-38-generic', no se puede configurar
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1895
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 72.43
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.16:bd10/17/2012:svnHewlett-Packard:pnHPENVYSleekbook4PC:pvr088511305A0310130:rvnHewlett-Packard:rn1895:rvr72.43:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Sleekbook 4 PC
dmi.product.version: 088511305A0310130
dmi.sys.vendor: Hewlett-Packard
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1631126
Title:
package linux-image-extra-4.4.0-38-generic (not installed) failed to
install/upgrade: no hay instalado ningún paquete llamado `linux-image-
extra-4.4.0-38-generic', no se puede configurar
Status in linux package in Ubuntu:
New
Bug description:
Al actualizar mi ubuntu al linux-image-extra-4.4.0-38 no reconoce a
mis tarjetas de red, video o sonido pero al hacer un lspci se listan
los dispositivos.
actualmente estoy trabajando con el linux-image-extra-4.4.0-36 que si
puedo trabajar con ello pero con eso no puedo actualizar el sistema.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-38-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1915 F pulseaudio
boris 2340 F pulseaudio
Date: Thu Oct 6 15:01:24 2016
DpkgHistoryLog:
Start-Date: 2016-10-06 15:01:09
Commandline: apt-get -f install
Requested-By: boris (1000)
Install: linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57, automatic)
DpkgTerminalLog:
Preparando para desempaquetar
.../linux-image-extra-4.4.0-38-generic_4.4.0-38.57_amd64.deb ...
Desempaquetando linux-headers-4.4.0-38 (4.4.0-38.57) sobre (4.4.0-38.57) ...
dpkg: error al procesar el paquete linux-image-extra-4.4.0-38-generic
(--configure):
no hay instalado ningún paquete llamado
`linux-image-extra-4.4.0-38-generic', no se puede configurar
ErrorMessage: no hay instalado ningún paquete llamado
`linux-image-extra-4.4.0-38-gener
[Kernel-packages] [Bug 1610622] [NEW] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f address=0x00000000bec09880 flags=0x0010]
Public bug reported: [ 19.880847] xhci_hcd :02:00.0: can't setup: -110 [ 19.880915] clocksource: Switched to clocksource tsc [ 19.880919] xhci_hcd :02:00.0: USB bus 8 deregistered [ 19.880979] xhci_hcd :02:00.0: init :02:00.0 fail, -110 [ 19.881033] xhci_hcd: probe of :02:00.0 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hitkliv1854 F pulseaudio /dev/snd/controlC2: hitkliv1854 F pulseaudio /dev/snd/controlC0: hitkliv1854 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sun Aug 7 09:38:17 2016 HibernationDevice: RESUME=UUID=4c30b323-8466-484e-bca4-99052a00ff77 InstallationDate: Installed on 2016-08-06 (0 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=UUID=96a76e70-0ed0-478e-8558-7f0cffe4782d ro rootflags=subvol=@ quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug sarah ** Attachment added: "AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f address=0xbec09880 flags=0x0010]" https://bugs.launchpad.net/bugs/1610622/+attachment/4715761/+files/apport.linux-image-4.4.0-31-generic.hfo7p1vh.apport -- 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/1610622 Title: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f address=0xbec09880 flags=0x0010] Status in linux package in Ubuntu: New Bug description: [ 19.880847] xhci_hcd :02:00.0: can't setup: -110 [ 19.880915] clocksource: Switched to clocksource tsc [ 19.880919] xhci_hcd :02:00.0: USB bus 8 deregistered [ 19.880979] xhci_hcd :02:00.0: init :02:00.0 fail, -110 [ 19.881033] xhci_hcd: probe of :02:00.0 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hitkliv1854 F pulseaudio /dev/snd/controlC2: hitkliv1854 F pulseaudio /dev/snd/controlC0: hitkliv1854 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sun Aug 7 09:38:17 2016 HibernationDevice: RESUME=UUID=4c30b323-8466-484e-bca4-99052a00ff77 InstallationDate: Installed on 2016-08-06 (0 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=UUID=96a76e70-0ed0-478e-8558-7f0cffe4782d ro rootflags=subvol=@ quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.1 RfKill:
[Kernel-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
I have got this bug. If you need some debug information, I can provide it. -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+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 1565234] Re: Intermittent Screen Flicker on Dell XPS 13 9350
*** This bug is a duplicate of bug 1554613 *** https://bugs.launchpad.net/bugs/1554613 Update: Now this bug is fixed for me by http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.4.9-xenial/ as well. -- 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/1565234 Title: Intermittent Screen Flicker on Dell XPS 13 9350 Status in linux package in Ubuntu: Incomplete Bug description: I am using the Dell XPS 13 9350 with Ubuntu 16.04, and I am experiencing random screen flickering where the screen will flicker to black for a split second. This happens repeatedly every few seconds for half a minute or so. Then the issue will disappear for a few minutes, but randomly come back. I have experienced using Ubuntu 16.04 with Unity, Gnome, and XFCE. See LP#1554613. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caleb 1533 F pulseaudio CurrentDesktop: XFCE Date: Sat Apr 2 05:06:21 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ac6dd208-0bc0-443d-bc73-3411a80e0328 InstallationDate: Installed on 2016-03-19 (13 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160319) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-16-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565234/+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 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
This bug is fixed for me in http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.4.9-xenial/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: *** Temporary workaround *** Install Kernel from one of the following locations: - http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc5-wily/ Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+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 1397880] Re: [v4.6-rc1 Regression] x86/topology: Create logical package id
On 05/06/2016 04:51 PM, Joseph Salisbury wrote: > Thomas' patch does resolve the bug. The cpuid info can be seen here: > https://launchpadlibrarian.net/258234267/cpuid_full.txt Any chance you could post it raw (cpuid -1 -r)? Thanks. -boris -- 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/1397880 Title: [Feature] Memory Bandwidth Monitoring Status in intel: New Status in linux package in Ubuntu: Fix Released Status in xen package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in xen source package in Xenial: Fix Released Bug description: Memory Bandwidth Monitoring (MBM) is a CPU feature included in the family of Platform QoS features. It is used to track memory bandwidth usage for a specific task, or group of tasks. Memory Bandwidth Monitoring is an extension of the existing Cache QoS Monitoring (CQM) feature found in Haswell server. The mechanism used is the same, where tasks are associated with an Resource Monitoring ID (RMID), which the CPU uses to track the bandwidth usage. Upstream status: Kernel - 4.6 Xen - target 4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1397880/+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 1397880] Re: [v4.6-rc1 Regression] x86/topology: Create logical package id
On 05/06/2016 03:38 PM, Joseph Salisbury wrote: > On 05/06/2016 03:13 PM, Boris Ostrovsky wrote: >> On 05/06/2016 02:48 PM, Thomas Gleixner wrote: >>> >>> Yuck. That dies with a divide error. And that looks like XEN is supplying >>> crap >>> data in the CPUID. >> Joe, do you have >> >> ed6069b xen/apic: Provide Xen-specific version of cpu_present_to_apicid >> APIC op >> >> -boris > Yes the commit is in the 4.4 based Ubuntu kernel. This bug also happens > with the vanilla 4.6-rc5 kernel, which also has that commit. Can you post guest's cpuid -1 -r ? (I guess after you verify Thomas' patch) Thanks. -boris -- 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/1397880 Title: [Feature] Memory Bandwidth Monitoring Status in intel: New Status in linux package in Ubuntu: Fix Released Status in xen package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in xen source package in Xenial: Fix Released Bug description: Memory Bandwidth Monitoring (MBM) is a CPU feature included in the family of Platform QoS features. It is used to track memory bandwidth usage for a specific task, or group of tasks. Memory Bandwidth Monitoring is an extension of the existing Cache QoS Monitoring (CQM) feature found in Haswell server. The mechanism used is the same, where tasks are associated with an Resource Monitoring ID (RMID), which the CPU uses to track the bandwidth usage. Upstream status: Kernel - 4.6 Xen - target 4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1397880/+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 1573231] Re: [v4.6-rc1 Regression] x86/topology: Create logical package id
On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
> On Fri, 6 May 2016, Joseph Salisbury wrote:
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>> commit 1f12e32f4cd5243ae46d8b933181be0d022c6793
>> Author: Thomas Gleixner <t...@linutronix.de>
>> Date: Mon Feb 22 22:19:15 2016 +
>>
>> x86/topology: Create logical package id
>>
>> To build successfully with this commit reverted, I also had to revert
>> commits: e7ee3e8,2d4de83,87f01cc and 33c3cc7.
>>
>> The regression was introduced as of v4.6-rc1.
>>
>> I was hoping to get your feedback, since you are the patch author. Do
>> you think gathering any additional data will help diagnose this issue,
>> or would it be best to submit a revert request?
> Yuck. That dies with a divide error. And that looks like XEN is supplying crap
> data in the CPUID.
Joe, do you have
ed6069b xen/apic: Provide Xen-specific version of cpu_present_to_apicid
APIC op
-boris
>
> Does the patch below cure the issue?
>
> Thanks,
>
> tglx
>
> 8<---
>
> --- a/arch/x86/kernel/smpboot.c
> +++ b/arch/x86/kernel/smpboot.c
> @@ -332,6 +332,11 @@ static void __init smp_init_package_map(
>* primary cores.
>*/
> ncpus = boot_cpu_data.x86_max_cores;
> + if (!ncpus) {
> + pr_warn("x86_max_cores == zero !?!?");
> + ncpus = 1;
> + }
> +
> __max_logical_packages = DIV_ROUND_UP(total_cpus, ncpus);
>
> /*
--
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/1573231
Title:
Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
release-upgrade -d
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Bug description:
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37
UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic
root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0
[0.00] KERNEL supported cpus:
[0.00] Intel GenuineIntel
[0.00] AMD AuthenticAMD
[0.00] Centaur CentaurHauls
[0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832
bytes, using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xefff] usable
[0.00] BIOS-e820: [mem 0xfc00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.4 present.
[0.00] Hypervisor detected: Xen
[0.00] Xen version 4.2.
[0.00] Netfront and the Xen platform PCI driver have been compiled
for this kernel: unplug emulated NICs.
[0.00] Blkfront and the Xen platform PCI driver have been compiled
for this kernel: unplug emulated disks.
[0.00] You might have to change the root device
[0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
[0.00] in your root= kernel command line option
[0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4
[0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT
[0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at
[880fbba0]
[0.00] Scanning 1 areas for low memory corruption
[0.00] RAMDISK: [mem 0x3407e000-0x36036fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen )
[Kernel-packages] [Bug 1565234] Re: Intermittent Screen Flicker on Dell XPS 13 9350
*** This bug is a duplicate of bug 1554613 *** https://bugs.launchpad.net/bugs/1554613 I am affected by this bug on dell xps 13 9350 both on FHD and QHD. Running kernel 4.6rc5 from http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.6-rc5-wily/ helps as a work-around. -- 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/1565234 Title: Intermittent Screen Flicker on Dell XPS 13 9350 Status in linux package in Ubuntu: Incomplete Bug description: I am using the Dell XPS 13 9350 with Ubuntu 16.04, and I am experiencing random screen flickering where the screen will flicker to black for a split second. This happens repeatedly every few seconds for half a minute or so. Then the issue will disappear for a few minutes, but randomly come back. I have experienced using Ubuntu 16.04 with Unity, Gnome, and XFCE. See LP#1554613. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caleb 1533 F pulseaudio CurrentDesktop: XFCE Date: Sat Apr 2 05:06:21 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ac6dd208-0bc0-443d-bc73-3411a80e0328 InstallationDate: Installed on 2016-03-19 (13 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160319) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-16-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565234/+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] R: [Bug 1492807] Re: the wi fi network do not work and no networs werefound
No, it was not and update/upgrade or other kernel version because i have sintalled for first time xubuntu on my pc. I have tryed to follow the instactions form the link you gave me, but i am not familiar with linux. If you want me to do something could you please give also instructions? Many thanks Regards Boris - Messaggio originale - Da: "Joseph Salisbury" <joseph.salisb...@canonical.com> Inviato: 08/09/2015 18:15 A: "vbori...@gmail.com" <vbori...@gmail.com> Oggetto: [Bug 1492807] Re: the wi fi network do not work and no networs werefound Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.2 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/ ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1492807 Title: the wi fi network do not work and no networs were found Status in linux package in Ubuntu: Incomplete Bug description: I have a Intel pro wireless 3945 for wifi connection, but it do not found any network and I can not fix. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-firmware 1.143 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CasperVersion: 1.360 CurrentDesktop: XFCE Date: Sun Sep 6 17:32:06 2015 Dependencies: LiveMediaBuild: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492807/+subscriptions -- 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/1492807 Title: the wi fi network do not work and no networs were found Status in linux package in Ubuntu: Incomplete Bug description: I have a Intel pro wireless 3945 for wifi connection, but it do not found any network and I can not fix. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-firmware 1.143 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CasperVersion: 1.360 CurrentDesktop: XFCE Date: Sun Sep 6 17:32:06 2015 Dependencies: LiveMediaBuild: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492807/+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 1492807] [NEW] the wi fi network do not work and no networs were found
Public bug reported: I have a Intel pro wireless 3945 for wifi connection, but it do not found any network and I can not fix. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-firmware 1.143 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CasperVersion: 1.360 CurrentDesktop: XFCE Date: Sun Sep 6 17:32:06 2015 Dependencies: LiveMediaBuild: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- 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/1492807 Title: the wi fi network do not work and no networs were found Status in linux-firmware package in Ubuntu: New Bug description: I have a Intel pro wireless 3945 for wifi connection, but it do not found any network and I can not fix. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-firmware 1.143 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CasperVersion: 1.360 CurrentDesktop: XFCE Date: Sun Sep 6 17:32:06 2015 Dependencies: LiveMediaBuild: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1492807/+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 1453404] Re: r8169 occasionally doesn't work after suspend
I refuse to test this with the latest upstream kernel. That is because the bug happens rarely and the upstream kernel breaks other stuff. I would have to use Ubuntu for a prolonged period with the upstream kernel, putting up with that brokenness, or I would have to go into suspend and wake many times quickly, which I believe is not good for my hardware. Feel free to delete this bug because of this refusal. -- 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/1453404 Title: r8169 occasionally doesn't work after suspend Status in linux package in Ubuntu: Incomplete Bug description: Occasionally the onboard gigabit Ethernet on this Gigabyte GA-P35-DS3R rev 1.0 motherboard doesn't work after suspend. This happens less than one out of ten times. This was the first time this bug happened in Ubuntu 15.04. WORKAROUND: sudo ifconfig eth0 down sudo ifconfig eth0 up WORKAROUND: Unload and reload the r8169 module. WORKAROUND: I'm installing the r8168-dkms package, which includes the proprietary Realtek driver. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2673 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sat May 9 10:57:05 2015 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 InstallationDate: Installed on 2012-01-19 (1206 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (15 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453404/+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 771857] Re: Realtek 8168B (r8169) interface not working following suspend
This keeps happening to me occasionally, less than one out of ten times. Over the last several Ubuntu releases, sudo ifconfig eth0 down followed by sudo ifconfig eth0 up has always been enough to re- establish connectivity. A long time ago, I sometimes had to unload and reload the r8169 module. This was the first time this bug happened in Ubuntu 15.04. I just filed a new report using ubuntu-bug linux: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453404 As a workaround, I'm installing the r8168-dkms package, which includes the proprietary Realtek driver. -- 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/771857 Title: Realtek 8168B (r8169) interface not working following suspend Status in The Linux Kernel: Incomplete Status in linux package in Ubuntu: Invalid Status in linux package in Fedora: Unknown Bug description: After suspending and resuming, the network adapter appears to be active (Link UP) however it is not able to properly communicate data and appears in network-manager as disconnected due to the inability to negotiate DHCP successfully. The workaround, in my case, is to execute this fixnet script following the resume to unload an reload the r8169 module. In 11.04 the network manager automatically reconnects at this point. imac@repo:/usr/local/bin$ cat fixnet #!/bin/sh rmmod r8169 modprobe r8169 imac@repo:/usr/local/bin$ lspci -v | grep -i realtek 0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Here is a typical dmesg, showing the link up after resume (@5958) followed by my script execution (starting @ 6105). [ 5956.140651] r8169 :0a:00.0: eth0: link down [ 5958.247724] r8169 :0a:00.0: eth0: link up [ 6105.570173] r8169 :0a:00.0: PCI INT A disabled [ 6105.604106] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 6105.604141] r8169 :0a:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 6105.604191] r8169 :0a:00.0: setting latency timer to 64 [ 6105.604248] r8169 :0a:00.0: irq 45 for MSI/MSI-X [ 6105.610321] r8169 :0a:00.0: eth0: RTL8168c/8111c at 0xc90002098000, 00:1e:ec:f2:0f:f3, XID 1c4000c0 IRQ 45 [ 6105.624882] r8169 :0a:00.0: eth0: link down [ 6105.624896] r8169 :0a:00.0: eth0: link down [ 6105.636108] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 6108.331777] r8169 :0a:00.0: eth0: link up [ 6108.332388] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 6118.770054] eth0: no IPv6 routers present Upstream we see this here: https://bugzilla.kernel.org/show_bug.cgi?id=12296 This problem also affects Maverick ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imac 2744 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xd240 irq 16' Mixer name : 'IDT 92HD71B7X' Components : 'HDA:111d76b2,103c30fd,00100302 HDA:11c11040,103c137e,00100200' Controls : 22 Simple ctrls : 14 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd231 irq 46' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Wed Apr 27 10:16:01 2011 HibernationDevice: RESUME=UUID=5828f841-5250-4229-bfc5-af24c6f41811 MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: LANGUAGE=en_US:en LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=52543d1c-6080-4cdf-80e0-30b9af3748f7 ro crashkernel=384M-2G:64M,2G-:128M splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: Upgraded to natty on 2011-04-06 (21 days ago) WpaSupplicantLog: dmi.bios.date: 08/17/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30FD dmi.board.vendor: Compal dmi.board.version: 01.99 dmi.chassis.type: 10
[Kernel-packages] [Bug 1453404] [NEW] r8169 occasionally doesn't work after suspend
Public bug reported: Occasionally the onboard gigabit Ethernet on this Gigabyte GA-P35-DS3R rev 1.0 motherboard doesn't work after suspend. This happens less than one out of ten times. Over the last several Ubuntu releases, sudo ifconfig eth0 down followed by sudo ifconfig eth0 up has always been enough to re-establish connectivity. A long time ago, I sometimes had to unload and reload the r8169 module. This was the first time this bug happened in Ubuntu 15.04. A similar bug already exists at https://bugs.launchpad.net/linux/+bug/771857 . I am reporting this here because the last comment there asks for a report via ubuntu-bug linux. Right now, as a workaround, I'm installing the r8168-dkms package, which includes the proprietary Realtek driver. Here is lspci -v output for this ethernet controller: 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Motherboard Flags: bus master, fast devsel, latency 0, IRQ 29 I/O ports at d000 [size=256] Memory at f900 (64-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at f800 [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c ? Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting ? Kernel driver in use: r8169 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2673 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sat May 9 10:57:05 2015 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 InstallationDate: Installed on 2012-01-19 (1206 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (15 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1453404 Title: r8169 occasionally doesn't work after suspend Status in linux package in Ubuntu: New Bug description: Occasionally the onboard gigabit Ethernet on this Gigabyte GA-P35-DS3R rev 1.0 motherboard doesn't work after suspend. This happens less than one out of ten times. Over the last several Ubuntu releases, sudo ifconfig eth0 down followed by sudo ifconfig eth0 up has always been enough to re-establish connectivity. A long time ago, I sometimes had to unload and reload the r8169 module. This was the first time this bug happened in Ubuntu 15.04. A similar bug already exists at https://bugs.launchpad.net/linux/+bug/771857 . I am reporting this here because the last comment there asks for a report via ubuntu-bug linux. Right now, as a workaround, I'm installing the r8168-dkms package, which includes the proprietary Realtek driver. Here is lspci -v output for this ethernet controller: 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Motherboard Flags: bus master, fast devsel, latency 0, IRQ 29 I/O ports at d000 [size=256]
[Kernel-packages] [Bug 1450088] Re: Wakes from S3 in a few seconds unless WIndows has been run
I solved the problem. This was wake on LAN. When I ran sudo ethtool eth0 the output included: Supports Wake-on: pumbg Wake-on: ug From the ethtool man page: u Wake on unicast messages g Wake on MagicPacket™ This was wake on unicast messages. Wake-on: ug is the default both with the r8169 driver that's included in the kernel and with the r8168-dkms package which presumably contains the driver from Realtek. I guess the BIOS sets it up this way. I see no BIOS options relating to wake on LAN. I disabled wake on LAN via the Advanced settings in Device Manager in Windows, and that was persisting until all power including standby power was cut. I am now disabling WOL with the following line in /etc/rc.local: ethtool -s eth0 wol d I also tried ethtool -s eth0 wol g which only wakes on magic packet and I didn't get an unexpected wakeup. Enabling wake on unicast messages by default is ridiculous. I guess this may be the fault of my BIOS. I'm not sure if there's anything Linux could do about that automatically. I just wish Linux would tell me what's the wake reason! If I saw something telling me this was wake on LAN I would have spent much less time figuring this out! Here's sudo lspci -v info about the ethernet controller, 10ec:8168: 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Motherboard Flags: bus master, fast devsel, latency 0, IRQ 29 I/O ports at d000 [size=256] Memory at f900 (64-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at f800 [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c ? Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting ? Kernel driver in use: r8169 My suspend tests were using this command to initiate suspend, running as a normal user: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true The attached /proc/acpi/wakeup file is in the state used during my most recent testing. I am disabling everything there via /etc/rc.local, but that didn't solve the problem. I never got any matches in my resume trace, just magic numbers. Anyways, that data should only be relevant if there is a lockup while going to sleep or resuming. ** Attachment added: /proc/acpi/wakeup https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450088/+attachment/4388745/+files/wakeup -- 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/1450088 Title: Wakes from S3 in a few seconds unless WIndows has been run Status in linux package in Ubuntu: Incomplete Bug description: I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0 motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power was fully cut, including standby power, and Windows has not been run since then, Ubuntu will quickly wake from S3 sleep without any apparent reason. Procedure to reproduce: 1. Shut down computer normally from the operating system. 2. When computer appears off, cut power either via the switch on the back or by unplugging it. 3. Wait some time. 10 seconds is probably enough and a minute should be 100% certain. 4. Boot directly into Ubuntu. It's okay to boot into Ubuntu via the Windows 7 boot menu. Do not actually boot into Windows itself though; if you do that you must restart at step 1. 5. Initiate S3 sleep. I have tried both of these with the same results: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true sudo sh -c echo mem /sys/power/state 6. Wait. The system should wake up within a few seconds, and certainly in less than a minute. The delay varies. The only problem is that the system won't stay sleeping. Everything works fine after the system wakes. Repeated attempts to sleep give the same result. I have disabled everything in /proc/acpi/wakeup using the following in /etc/rc.local: sed -n '/enabled/s,\([^\t]\+\)\s.*$,echo \1 /proc/acpi/wakeup,p' /proc/acpi/wakeup | sh I confirm that it appears disabled before and after sleep. I have also disabled all wakeup files in sys (found via sudo find /sys -iname wakeup -type f), and it didn't help. The logs don't seem to show a wakeup reason. If I boot into Windows 7 and then boot
[Kernel-packages] [Bug 1450088] Re: Wakes from S3 in a few seconds unless WIndows has been run
I can reproduce this with v4.1-rc1-vivid. I had to uninstall nvidia-340-updates because the DKMS module failed to build and boot hung while it was installed. So, I was using nouveau for my GeForce 8600GT PCI express graphics card. I can't reproduce it if not running X, or running X, twm and xterm or GNOME terminal. However, if I run Google Chrome in addition to that, I can reproduce it. Also, I can always reproduce it when using Openbox or Cinnamon. Successful sleep in Linux (without an unexpected wakeup) does not prevent future wakeups when conditions change. -- 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/1450088 Title: Wakes from S3 in a few seconds unless WIndows has been run Status in linux package in Ubuntu: Incomplete Bug description: I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0 motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power was fully cut, including standby power, and Windows has not been run since then, Ubuntu will quickly wake from S3 sleep without any apparent reason. Procedure to reproduce: 1. Shut down computer normally from the operating system. 2. When computer appears off, cut power either via the switch on the back or by unplugging it. 3. Wait some time. 10 seconds is probably enough and a minute should be 100% certain. 4. Boot directly into Ubuntu. It's okay to boot into Ubuntu via the Windows 7 boot menu. Do not actually boot into Windows itself though; if you do that you must restart at step 1. 5. Initiate S3 sleep. I have tried both of these with the same results: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true sudo sh -c echo mem /sys/power/state 6. Wait. The system should wake up within a few seconds, and certainly in less than a minute. The delay varies. The only problem is that the system won't stay sleeping. Everything works fine after the system wakes. Repeated attempts to sleep give the same result. I have disabled everything in /proc/acpi/wakeup using the following in /etc/rc.local: sed -n '/enabled/s,\([^\t]\+\)\s.*$,echo \1 /proc/acpi/wakeup,p' /proc/acpi/wakeup | sh I confirm that it appears disabled before and after sleep. I have also disabled all wakeup files in sys (found via sudo find /sys -iname wakeup -type f), and it didn't help. The logs don't seem to show a wakeup reason. If I boot into Windows 7 and then boot into Linux, this problem stops happening. Shutting down from either operating system or pressing the reset button does not cause the problem to reoccur. It only reoccurs if standby power has been cut. I am assuming that Linux fails to perform some initialization which Windows performs, and that initialization persists as long as standby power is available. I am assuming this is a kernel bug because it occurs even if I use echo mem /sys/power/state to enter sleep. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2280 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Apr 29 10:39:49 2015 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 InstallationDate: Installed on 2012-01-19 (1196 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (5 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1450088] [NEW] Wakes from S3 in a few seconds unless WIndows has been run
Public bug reported: I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0 motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power was fully cut, including standby power, and Windows has not been run since then, Ubuntu will quickly wake from S3 sleep without any apparent reason. Procedure to reproduce: 1. Shut down computer normally from the operating system. 2. When computer appears off, cut power either via the switch on the back or by unplugging it. 3. Wait some time. 10 seconds is probably enough and a minute should be 100% certain. 4. Boot directly into Ubuntu. It's okay to boot into Ubuntu via the Windows 7 boot menu. Do not actually boot into Windows itself though; if you do that you must restart at step 1. 5. Initiate S3 sleep. I have tried both of these with the same results: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true sudo sh -c echo mem /sys/power/state 6. Wait. The system should wake up within a few seconds, and certainly in less than a minute. The delay varies. The only problem is that the system won't stay sleeping. Everything works fine after the system wakes. Repeated attempts to sleep give the same result. I have disabled everything in /proc/acpi/wakeup using the following in /etc/rc.local: sed -n '/enabled/s,\([^\t]\+\)\s.*$,echo \1 /proc/acpi/wakeup,p' /proc/acpi/wakeup | sh I confirm that it appears disabled before and after sleep. I have also disabled all wakeup files in sys (found via sudo find /sys -iname wakeup -type f), and it didn't help. The logs don't seem to show a wakeup reason. If I boot into Windows 7 and then boot into Linux, this problem stops happening. Shutting down from either operating system or pressing the reset button does not cause the problem to reoccur. It only reoccurs if standby power has been cut. I am assuming that Linux fails to perform some initialization which Windows performs, and that initialization persists as long as standby power is available. I am assuming this is a kernel bug because it occurs even if I use echo mem /sys/power/state to enter sleep. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bgjenero 2280 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Apr 29 10:39:49 2015 HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11 InstallationDate: Installed on 2012-01-19 (1196 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (5 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1450088 Title: Wakes from S3 in a few seconds unless WIndows has been run Status in linux package in Ubuntu: New Bug description: I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0 motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power was fully cut, including standby power, and Windows has not been run since then, Ubuntu will quickly wake from S3 sleep without any apparent reason. Procedure to reproduce: 1. Shut down computer normally from the operating system. 2. When computer appears off, cut power either via the switch on the back or by unplugging it. 3. Wait some time. 10 seconds is probably enough and a minute should be 100% certain. 4. Boot directly into Ubuntu. It's okay to boot into Ubuntu via the Windows 7 boot menu. Do not actually boot into
[Kernel-packages] [Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
@Adam sadly, yes. But it now should be clear with the existing workarounds that's not necessary for future releases. -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in The Linux Kernel: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
Thx for the feedback Lars, I think we can call it on the bug Walter, so far nobody else has come forward with anything that suggests otherwise. Where would we propose to implement those params to be set as default for the specific systems in future builds/ releases, would a post to the ppc list be in order and would you do that Walter? -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
I believe this is due to incomplete or not at all set up Xorg conf which for some reason is not done for a long time on certain Radeon systems, so those are without DRI and all the bells and whistles. Did you try what I mentioned above? sudo service lightdm stop sudo Xorg -configure sudo mv xorg.conf.new /etc/X11/xorg.conf sudo nano /etc/X11/xorg.conf [Here some driver options could be set, eg. uncomment pageflip and set it to True, save any edits and after that reboot] sudo shutdown -r now After a reboot you can check your acceleration with the commands glxinfo and glxgears -info if it works you will notice the gears running well even if quickly moving it's window but likely lubuntu gui will otherwise remain kinda slow but should be better. -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
known ppc radeon 9000-range AGP-freeze issue, needs radeon.agpmode=-1 yaboot param workaround, additionally combination with video=ofonly is recommended ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Invalid Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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
Re: [Kernel-packages] [Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
Thanks Lars, still learning the ropes with this, from Walters response I gathered we could call it, but I'm glad we can work the installer defaults in, makes more sense that way and I expressed as much on the bug, was just not sure if this should be left open all the way. Am 11.11.2014 05:45 schrieb Lars Noodén lars.noo...@gmail.com: Boris, it's still a bug until the installer adds those boot options and the installed system ends up with them in yaboot.conf ** Changed in: linux (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+subscriptions -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
Thanks Lars, still learning the ropes with this, from Walters response I gathered we could call it, but I'm glad we can work the installer defaults in, makes more sense that way and I expressed as much in my comments above, was just not sure if this should be left open all the way, but yeah makes more sense. -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
Hi Walter, yep not default for every kind of ppc system, only for those specific G4 ibook's with the radeon 9200 variant, tho eMacs with those would also seems like a save bet-!? Sry I haven't yet gotten around to the FAQ/ Known Issues addition but I plan on spending some time on it tomorrow :) For everyone else reading up on this I figured I should post our conclusion so far here as well: 1. yaboot params don't seem to stick/ carry over from live-boot initiated installations (intentionally?? for many mac users this would probably be unexpected and result in what I'd like to describe as wtf I already had the correct params set why doesn't it work as expected and be cause for confusion as the needed workarounds to make it work would not be actually used anymore while still assumed to be in use, so likely cause for seemingly not working out of the box Question: what can be done about that or is pointing to more detailed Information on that and the actual params needed the only available course of action or can those params be set default out of the box on affected system configurations? 2. Radeon 9200/ RV 280 (M9+) chips on the PowerBook6,5 (ibook G4, 12' inch, 1.2 GHz) and also likely similar ibook and eMac Radeon 9000 range of chips for some reason won't work reliable on Radeon-KMS with AGP transfer enabled, so those need radeon.agpmode=-1 no idea if it's a flaw in the way Apple implemented AGP on these ibooks or in combination with an expectation of the driver on how AGP is supposed to be implemented, or simply some bug, but it won't work at the moment and causes the freeze issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878 3. using the older framebuffer params in any way on top of things causes conflicts with KMS which even with radeon.agpmode=-1 set would cause UI/ GUI issues like incomplete loading or nonfuctional UI/ GUI, so we additionally would need video=ofonly here and should not try to additionally use any combination of eg. radeonfb (which quite a few older workaround instructions might confusingly suggest and result in the user having any variation of params but not only the above 2 he or she would need to make it work) 4. with video=ofonly radeon.agpmode=-1 those ibooks would boot and be useable prefectly fine BUT there will be sluggish feeling 2D/ gui/ windows moving and no accel at all which would be the result of not having Xorg properly configured/ detecting the chip and using the appropriate driver out of the box which also would have to be initiated manually at this point: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1058641 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1366556 to fix from a booted Installation: sudo service lightdm stop sudo Xorg -configure sudo mv xorg.conf.new /etc/X11/xorg.conf sudo nano /etc/X11/xorg.conf [Here some driver options could be set, eg. uncomment pageflip and set it to True, save any edits and after that reboot] sudo shutdown -r now --- Grüße boris -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
System was installed using Boris/Adam's agpmode=-1that worked to clean up the 14.10 GUI . . . and I've tried various flavors of radeonfb boot parameters . . . - don't! My understanding was using radeonfb conflicts with KMS which we want to use nowadays, so try to leave it out and instead use only video=ofonly radeon.agpmode=-1 Yesterday I ran sudo Xorg -configure . . . and generated an xorg.conf file . . . it does show radeon as the driver, along with a bunch of other stuff . . . rebooted . . . no difference. - Did you move it to it's right place via sudo mv xorg.conf.new /etc/X11/xorg.conf -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1304001] Re: xen:balloon errors in 14.04 beta
It is now in mainline, commit fd8b79511349. -- 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/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Status in “linux” source package in Utopic: Triaged Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+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 1304001] Re: xen:balloon errors in 14.04 beta
I was waiting for this patch to be pulled into the mainline before posting a pointer/commitID here. It's not there yet. But yes, you need that commit (on top of 3dcf63677d4e) to make kernel shut up. -- 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/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Status in “linux” source package in Utopic: Triaged Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
Hello all, @Walter I did encounter this in 14.04.1 as well it works if I force PCI mode via yaboot radeon.agpmode=-1 (which I thought was the expected workaround for an unknown issue with AGP and the user would be expected to use it) While on my system with a 9200 based chip under OSX it's listed as AGP 4x I vaguely remember Apple once only listing a similar chip as AGP supported without them actually having it implemented that way (if that would make sense? but I think it was with the even older Rage 128 series if I recall correctly) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1377878] Re: PPC - GUI freezes except for mouse pointer
so I quess the question might be what changed, did AGP work before, was there no hardware acceleration, was PCI transfer maybe temporarily forced? -- 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/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+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 1304001] Re: xen:balloon errors in 14.04 beta
Hmm, yes, the patch may not work if something (AWS, I guess) keeps requesting to balloon memory. Can someone try the attached patch (on top of David's)? I only compile- tested it. ** Patch added: cancel_balloon.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4223567/+files/cancel_balloon.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+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 1304001] Re: xen:balloon errors in 14.04 beta
Actually, this (v2) is a slightly better one to try. ** Patch added: cancel_balloon_v2.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4223585/+files/cancel_balloon_v2.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+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 1168819] Re: 168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k
Sorry I noticed this was still open - problem did disappear after a few months with newer kernel version -- 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/1168819 Title: 168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: With the latest raring kernel image (linux-signed-image-3.8.0-18-generic) my wireless connection becomes very slow after a few minutes (ping to my AP increases from 1ms to ~ 900ms). Kernel 3.8.0.17.27 is still fine, other wireless devices continue to work fine if the problem occurs. HW is AR9485 (ath9k) 1x1 802.11n in Asus G75VX laptop, AP is Asus RT-AC66U. ~ --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: #RESUME=UUID=8c98d3e1-50af-4c74-820b-e3f29cefc50c #RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2013-03-27 (17 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=93525b3d-45ae-49d5-be79-e00da8ca123b ro bootchart=disable ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.105 Tags: raring Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (8 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video dmi.bios.date: 02/27/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX 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.:bvrG75VX.206:bd02/27/2013:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1168819/+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
