[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
So switching the "Sleep State" in the BIOS to "Linux" solved the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+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 2008774] Re: Ubuntu 22.04 not waking up after second suspend
The ctrl+alt+F2 trick didn't work with me. My keyboard seems to be not working after suspend. But I stumbled over this Reddit post: https://www.reddit.com/r/thinkpad/comments/lnyrt6/til_i_learn_newer_thinkpads_have_a_setting_for. There is a "Sleep State" switch in the BIOS of some Thinkpads (Config ➜ Power ➜ Sleep State ➜ “Linux” / “Windows 10”). I just turned it from "Windows" to "Linux" and it seems to work now. But I'm not sure yet. I will test more. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+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 2008774] [NEW] Ubuntu 22.04 not waking up after second suspend
Public bug reported: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+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 1942450] [NEW] Receiving duplicate packets on prp link
Public bug reported: Ubuntu release: Ubuntu 20.04 (Ubuntu 20.04.3 LTS) Package version: 5.10.0 After setting the same mac address on enp4s0 as enp3s0, I set up the prp link with the command ip link add name prp0 type hsr slave1 enp3s0 slave2 enp4s0 version 1 proto 1 I made a simple udp client that sends packets every 10 ms containing an int that increments for each packet. The udp client was running on computer 1. I made a simple udp server that receives the packets and prints the containing int. The udp server was running on computer 2. The computers were connected directly to each other with two network cables. The expected result was that the udp server would not receive any duplicates. What happened was that the first 1821 packets were ok. After that 55% of the packets were duplicates.' After a reboot, the first packets were ok, but again, duplicates started appearing after some time. I got more or less the same results with version 0 of prp. ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1942450 Title: Receiving duplicate packets on prp link Status in iproute2 package in Ubuntu: New Bug description: Ubuntu release: Ubuntu 20.04 (Ubuntu 20.04.3 LTS) Package version: 5.10.0 After setting the same mac address on enp4s0 as enp3s0, I set up the prp link with the command ip link add name prp0 type hsr slave1 enp3s0 slave2 enp4s0 version 1 proto 1 I made a simple udp client that sends packets every 10 ms containing an int that increments for each packet. The udp client was running on computer 1. I made a simple udp server that receives the packets and prints the containing int. The udp server was running on computer 2. The computers were connected directly to each other with two network cables. The expected result was that the udp server would not receive any duplicates. What happened was that the first 1821 packets were ok. After that 55% of the packets were duplicates.' After a reboot, the first packets were ok, but again, duplicates started appearing after some time. I got more or less the same results with version 0 of prp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1942450/+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 1828304] [NEW] QCA6174 slow transfer speeds
Public bug reported: Ubuntu 19.04 Package version 1.178 After the upgrade the transfer speeds dropped dramatically. Download/incoming is affected to a greater degree than upload/outgoing. A temporary solution as downloading linux-firmware 1.175.3 from cosmic- updates, and overwriting binaries in ath10k/QCA6174/hw3.0/ with the binaries from this package. Detailed hardware information lshw -C network *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:6e:00.0 logical name: wlp110s0 version: 32 serial: 6c:0b:84:26:e5:e1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.10.133 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:142 memory:dc40-dc5f *-network description: Wireless interface product: Wil6200 802.11ad Wireless Network Adapter vendor: Wilocity Ltd. physical id: 0 bus info: pci@:6f:00.0 logical name: wlp111s0 version: 02 serial: 04:ce:14:07:92:26 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wil6210 driverversion=5.0.0-13-generic firmware=5.2.0.18 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:138 memory:dc20-dc3f ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828304 Title: QCA6174 slow transfer speeds Status in linux-firmware package in Ubuntu: New Bug description: Ubuntu 19.04 Package version 1.178 After the upgrade the transfer speeds dropped dramatically. Download/incoming is affected to a greater degree than upload/outgoing. A temporary solution as downloading linux-firmware 1.175.3 from cosmic-updates, and overwriting binaries in ath10k/QCA6174/hw3.0/ with the binaries from this package. Detailed hardware information lshw -C network *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:6e:00.0 logical name: wlp110s0 version: 32 serial: 6c:0b:84:26:e5:e1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=WLAN.RM.4.4.1-00079-QCARMSWPZ-1 ip=192.168.10.133 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:142 memory:dc40-dc5f *-network description: Wireless interface product: Wil6200 802.11ad Wireless Network Adapter vendor: Wilocity Ltd. physical id: 0 bus info: pci@:6f:00.0 logical name: wlp111s0 version: 02 serial: 04:ce:14:07:92:26 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wil6210 driverversion=5.0.0-13-generic firmware=5.2.0.18 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:138 memory:dc20-dc3f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1828304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf
Ok, on 18.04 (Bionic), if I do this ``` sudo apt-get build-dep linux-tools-4.15.0-39-generic sudo apt-get install libiberty-dev binutils-dev mkdir tmp cd tmp apt-get source linux-tools-4.15.0-39-generic cd linux-4.15.0/tools/perf make ``` I do get a perf command that demangles (so I now have a workaround) Still, if I use `debuild` instead, as shown in my previous post, the command is apparently built differently and is not able to demangle. So, I can confirm the findings similar to post #24. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396654 Title: C++ demangling support missing from perf Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-hwe source package in Xenial: Confirmed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Bug description: Hi, It appears that C++ demangling support is missing from linux-tools-3.16.0-24, on Utopic on arm64. Could the following please be added to the build dependencies for that package: libiberty-dev binutils-dev Installing the above and rebuilding the package fixed the problem for me. Cheers, -- Steve --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-24-generic aarch64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf
I am affected by this on Ubuntu 18.04 (Bionic). The only workaround I have seen, is to build/rebuild the `perf` tool from the source package. This does not fix the problem for me on 18.04. ``` sudo apt-get install libiberty-dev binutils-dev mkdir tmp cd tmp apt-get source linux-tools-4.15.0-39-generic cd linux-4.15.0/ sudo apt-get build-dep linux-tools-4.15.0-39-generic debuild --no-sign ``` Then, the newly built `debian/linux-tools-4.15.0-39/usr/lib/linux- tools-4.15.0-39/perf` still does not do any demangling of C++ symbols. Am I doing something wrong, or is it a new kind of problem with a different solution on 18.04? Any help will be greatly appreciated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396654 Title: C++ demangling support missing from perf Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-hwe source package in Xenial: Confirmed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Bug description: Hi, It appears that C++ demangling support is missing from linux-tools-3.16.0-24, on Utopic on arm64. Could the following please be added to the build dependencies for that package: libiberty-dev binutils-dev Installing the above and rebuilding the package fixed the problem for me. Cheers, -- Steve --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-24-generic aarch64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790390] Re: Intel i915 GPU driver has wrong max resolution output for certain models
Update. This is a functional regression as a result of switching to modesetting. Source: https://bugs.freedesktop.org/show_bug.cgi?id=107840#c1 ** Package changed: linux-signed-oem (Ubuntu) => xorg (Ubuntu) ** Tags removed: kernel-bug ** Summary changed: - Intel i915 GPU driver has wrong max resolution output for certain models + Xorg cannot exceed pipeline dimensions reported by kernel ** Bug watch added: freedesktop.org Bugzilla #107840 https://bugs.freedesktop.org/show_bug.cgi?id=107840 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1790390 Title: Xorg cannot exceed pipeline dimensions reported by kernel Status in xorg package in Ubuntu: New Bug description: The i915 driver in the Linux kernel misrepresents the max output of certain, newer, GPUs. The output should be 16384x16384 for newer models (on at least 7th and 8th gen Intel CPUs) but it is stuck in 8192x8192. The problem lies in: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c The conditional branch which is wrong is: /* maximum framebuffer dimensions */ if (IS_GEN2(dev_priv)) { dev->mode_config.max_width = 2048; dev->mode_config.max_height = 2048; } else if (IS_GEN3(dev_priv)) { dev->mode_config.max_width = 4096; dev->mode_config.max_height = 4096; } else { dev->mode_config.max_width = 8192; dev->mode_config.max_height = 8192; } While I'm not certain which generations specifically allows the higher output it is most certainly true of all iGPUs on the 7th and 8th generation CPUs. This is corroborated by Intel's own hardware pages, and can be proven by running Wayland which ignores the limitation in the driver. Bug is present both on all Ubuntu releases, including 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790390/+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 1790390] [NEW] Intel i915 GPU driver has wrong max resolution output for certain models
Public bug reported: The i915 driver in the Linux kernel misrepresents the max output of certain, newer, GPUs. The output should be 16384x16384 for newer models (on at least 7th and 8th gen Intel CPUs) but it is stuck in 8192x8192. The problem lies in: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c The conditional branch which is wrong is: /* maximum framebuffer dimensions */ if (IS_GEN2(dev_priv)) { dev->mode_config.max_width = 2048; dev->mode_config.max_height = 2048; } else if (IS_GEN3(dev_priv)) { dev->mode_config.max_width = 4096; dev->mode_config.max_height = 4096; } else { dev->mode_config.max_width = 8192; dev->mode_config.max_height = 8192; } While I'm not certain which generations specifically allows the higher output it is most certainly true of all iGPUs on the 7th and 8th generation CPUs. This is corroborated by Intel's own hardware pages, and can be proven by running Wayland which ignores the limitation in the driver. Bug is present both on all Ubuntu releases, including 18.04. ** Affects: linux-signed-oem (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1790390 Title: Intel i915 GPU driver has wrong max resolution output for certain models Status in linux-signed-oem package in Ubuntu: New Bug description: The i915 driver in the Linux kernel misrepresents the max output of certain, newer, GPUs. The output should be 16384x16384 for newer models (on at least 7th and 8th gen Intel CPUs) but it is stuck in 8192x8192. The problem lies in: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c The conditional branch which is wrong is: /* maximum framebuffer dimensions */ if (IS_GEN2(dev_priv)) { dev->mode_config.max_width = 2048; dev->mode_config.max_height = 2048; } else if (IS_GEN3(dev_priv)) { dev->mode_config.max_width = 4096; dev->mode_config.max_height = 4096; } else { dev->mode_config.max_width = 8192; dev->mode_config.max_height = 8192; } While I'm not certain which generations specifically allows the higher output it is most certainly true of all iGPUs on the 7th and 8th generation CPUs. This is corroborated by Intel's own hardware pages, and can be proven by running Wayland which ignores the limitation in the driver. Bug is present both on all Ubuntu releases, including 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1790390/+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 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working
Since it appears to work with the above workaround, as far as I'm concerned this bug can be closed. -- 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller [Alpine Ridge] /0/100/1c/0/2/0/0usb3 busxHCI Host Controller /0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to Thunderbolt 2 Adapter /0/100/1c/0/2/0/0/2 input USB Optical Mouse /0/100/1c/0/2/0/1usb4 busxHCI Host Controller /0/100/1c/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c.2 bridge Sunrise Point-H PCI Express Root Port #3 /0/100/1c.3 bridge Sunrise Point-H PCI Express Root Port #4 /0/100/1c.4 bridge Sunrise Point-H PCI Express Root Port #5 /0/100/1c.4/0enp13s0networkKiller E2400 Gigabit Ethernet Controller /0/100/1c.5 bridge Sunrise Point-H PCI Express Root Port #6 /0/100/1c.5/0wlp14s0networkWireless 8260 /0/100/1c.6
[Kernel-packages] [Bug 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working
I found a way to make this work! Apparently when you connect the device it isn't authorized. I read here (http://www.omgubuntu.co.uk/2017/12/project-bolt-improves-thunderbolt- security-linux) that Redhat is working on making a GUI which will offer you a dialog to authorize, but for now it needs to be done manually. What one needs to do is to locate the device in the tree of devices in sysfs and authorize it. Here is a small snippet that will identify the device and write the authorized flag into the correct file: --- sudo bash -c 'echo 1 > $(dirname $(grep -l "Thunderbolt to FireWire Adapter" /sys/bus/thunderbolt/devices/[0-9]-[0-9]/device_name))/authorized' --- (In case the command is broken up, that's supposed to be all on one line) This assumes that your FireWire device indeed uses the label "Thunderbolt to FireWire Adapter" as its name, which is the case at least for the Apple FireWire dongle. I'm not sure if there are any others, but if so you may need to look inside the "devices" folder manually and look for a "device_name" file with similar content. Then "echo 1 > authorized" into the "authorized" file in the same folder. This was tested with the v4.15-rc1 kernel. I haven't tested earlier kernels. -- 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2 bridge DSL6540
[Kernel-packages] [Bug 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working
I can confirm that this is not fixed in kernel v4.15-rc1. I can see the device: --- $ cat /sys/bus/thunderbolt/devices/0-1/device_name Thunderbolt to FireWire Adapter --- .. but it doesn't show up in lspci, and it doesn't look like drivers can bind to it (I'm trying with libffado). Cold- or hotplugging makes no difference, the result is the same. ** Tags added: kernel-bug-exists-upstream ** 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller [Alpine Ridge] /0/100/1c/0/2/0/0usb3 busxHCI Host Controller /0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to Thunderbolt 2 Adapter /0/100/1c/0/2/0/0/2 input USB Optical Mouse /0/100/1c/0/2/0/1usb4 busxHCI Host Controller /0/100/1c/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c.2 bridge Sunrise Point-H PCI Express Root Port #3 /0/100/1c.3 bridge Sunrise Point-H PCI Express Root Port #4 /0/10
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
I also have to say that the system where I experienced this error is not with me anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Fix Committed Status in bcmwl source package in Vivid: Won't Fix Status in bcmwl source package in Wily: Fix Released Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+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 1279059] [NEW] [TOSHIBA SATELLITE C50D-A-11G] suspend/resume failure [non-free: fglrx]
Public bug reported: just after login. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.27 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: fglrx Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kostro 1928 F pulseaudio /dev/snd/controlC0: kostro 1928 F pulseaudio Date: Tue Feb 11 17:46:35 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=76b3328b-1587-4b75-89a3-f9573a655733 InstallationDate: Installed on 2014-01-20 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140115) InterpreterPath: /usr/bin/python3.3 MachineType: TOSHIBA SATELLITE C50D-A-11G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic.efi.signed root=UUID=7fcf011c-2166-4e83-a4da-112eda4bec22 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: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.123 SourcePackage: linux Title: [TOSHIBA SATELLITE C50D-A-11G] suspend/resume failure [non-free: fglrx] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.00 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PT10ABX dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.00:bd04/25/2013:svnTOSHIBA:pnSATELLITEC50D-A-11G:pvrPSCHNE-00N00MN5:rvnAMD:rnPT10ABX:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C50D-A-11G dmi.product.version: PSCHNE-00N00MN5 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend trusty -- 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/1279059 Title: [TOSHIBA SATELLITE C50D-A-11G] suspend/resume failure [non-free: fglrx] Status in “linux” package in Ubuntu: New Bug description: just after login. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.27 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: fglrx Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kostro 1928 F pulseaudio /dev/snd/controlC0: kostro 1928 F pulseaudio Date: Tue Feb 11 17:46:35 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=76b3328b-1587-4b75-89a3-f9573a655733 InstallationDate: Installed on 2014-01-20 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140115) InterpreterPath: /usr/bin/python3.3 MachineType: TOSHIBA SATELLITE C50D-A-11G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic.efi.signed root=UUID=7fcf011c-2166-4e83-a4da-112eda4bec22 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: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.123 SourcePackage: linux Title: [TOSHIBA SATELLITE C50D-A-11G] suspend/resume failure [non-free: fglrx] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.00 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PT10ABX dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.00:bd04/25/2013:svn
Re: [Kernel-packages] [Bug 1187214] Re: "ext4-fs error" -- Ubuntu upgrade from 12.10 to 13.04 corrupted filesystems (ext4 corruption bug)
Unable to test sorry. -- Kristian Erik Hermansen https://www.linkedin.com/in/kristianhermansen https://profiles.google.com/kristian.hermansen On Jan 2, 2014 6:10 PM, "Christopher M. Penalver" < christopher.m.penal...@gmail.com> wrote: > Kristian Erik Hermansen, this bug was reported a while ago and there > hasn't been any activity in it recently. We were wondering if this is > still an issue? If so, could you please test for this with the latest > development release of Ubuntu? ISO images are available from > http://cdimage.ubuntu.com/daily-live/current/ . > > If it remains an issue, could you please run the following command in > the development release (installed or live) from a Terminal > (Applications->Accessories->Terminal), as it will automatically gather > and attach updated debug information to this report: > > apport-collect -p linux > > If reproducible, could you also please test the latest upstream kernel > available (not the daily folder) following > https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional > upstream developers to examine the issue. Once you've tested the upstream > kernel, please comment on which kernel version specifically you tested. If > this bug is fixed in the mainline kernel, please add the following tags: > kernel-fixed-upstream > kernel-fixed-upstream-VERSION-NUMBER > > where VERSION-NUMBER is the version number of the kernel you tested. For > example: > kernel-fixed-upstream-v3.13-rc6 > > This can be done by clicking on the yellow circle with a black pencil icon > next to the word Tags located at the bottom of the bug description. As > well, please remove the tag: > needs-upstream-testing > > If the mainline kernel does not fix this bug, please add the following > tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-VERSION-NUMBER > > As well, please remove the tag: > needs-upstream-testing > > Once testing of the upstream kernel is complete, please mark this bug's > Status as Confirmed. Please let us know your results. Thank you for your > understanding. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > ** Tags added: needs-kernel-logs needs-upstream-testing regression- > potential > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1187214 > > Title: > "ext4-fs error" -- Ubuntu upgrade from 12.10 to 13.04 corrupted > filesystems (ext4 corruption bug) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1187214/+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/1187214 Title: "ext4-fs error" -- Ubuntu upgrade from 12.10 to 13.04 corrupted filesystems (ext4 corruption bug) Status in “linux” package in Ubuntu: Incomplete Bug description: I thought it would be a good idea to upgrade from 12.10 to 13.04. Apparently, Ubuntu likes to corrupt my data. My configuration has 4xHDD in RAID0 using ecryptfs of user data only. 70% into the upgrade process using the recommended GUI upgrade option, the process failed, the ext4 file-system became corrupted and all data was lost. Eventually, my kernel crashed shortly afterwards and rebooted. I was able to snap a quick photo, but it is only the last page of the errors ... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1187214/+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 823106] Re: Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout on macbook running oneiric
I no longer have the macbook to test sorry. -- Kristian Erik Hermansen https://www.linkedin.com/in/kristianhermansen https://profiles.google.com/kristian.hermansen On Dec 14, 2013 9:25 PM, "Christopher M. Penalver" < christopher.m.penal...@gmail.com> wrote: > Kristian Erik Hermansen, this bug was reported a while ago and there > hasn't been any activity in it recently. We were wondering if this is > still an issue? If so, could you please test for this with the latest > development release of Ubuntu? ISO images are available from > http://cdimage.ubuntu.com/daily-live/current/ . > > If it remains an issue, could you please just make a comment to this. > > ** Tags removed: 11.10 callin callout cpu cpu1 kernel > kernel-request-3.0.0-12.20 linux macbook panic smp > ** Tags added: bot-stop-nagging needs-kernel-logs needs-upstream-testing > > ** Tags added: regression-potential > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/823106 > > Title: > Kernel panic - not syncing: smp_callin: CPU1 started up but did not > get a callout on macbook running oneiric > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/823106/+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/823106 Title: Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout on macbook running oneiric Status in “linux” package in Ubuntu: Incomplete Bug description: Occurs on every boot. I expect no kernel panics on boot. """ lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 $ uname -a Linux ubuntu-macbook 3.0.0-7-generic #9-Ubuntu SMP Fri Jul 29 21:27:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/823106/+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 1257409] [NEW] [LENOVO 232032U] suspend/resume failure
Public bug reported: Error dialog always shows up after resume/boot. System seems to be working fine. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klette 2477 F pulseaudio /dev/snd/seq:timidity 2135 F timidity CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Dec 3 18:47:37 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=f0a8753f-b64c-433c-bab9-50fc3688d330 InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 232032U MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=060e990d-40a2-4633-8194-9a02bcaf83ee ro splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [LENOVO 232032U] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-10-12 (52 days ago) UserGroups: dmi.bios.date: 05/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET32WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 232032U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET32WW(1.12):bd05/30/2012:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 232032U dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume saucy suspend -- 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/1257409 Title: [LENOVO 232032U] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: Error dialog always shows up after resume/boot. System seems to be working fine. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klette 2477 F pulseaudio /dev/snd/seq:timidity 2135 F timidity CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Dec 3 18:47:37 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=f0a8753f-b64c-433c-bab9-50fc3688d330 InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 232032U MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=060e990d-40a2-4633-8194-9a02bcaf83ee ro splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [LENOVO 232032U] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-10-12 (52 days ago) UserGroups: dmi.bios.date: 05/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET32WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 232032U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET32WW(1.12):bd05/30/2012:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 232032U dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257409/+subscriptions -- Mailing list: http
[Kernel-packages] [Bug 557890] Re: transfer lockup connecting to a NetApp/CIFS share
I am unsure what to do with this one. Haven't tested and can't reproduce this as we don't run this device anymore. Right now, using a "plain" NetApp FAS-2020, OnTap 7.4 and a 3.8.0 kernel off Ubuntu 13.04, this is no longer a problem. As far as I am concerned, this one could be closed. -- 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/557890 Title: transfer lockup connecting to a NetApp/CIFS share Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Incomplete Bug description: Binary package hint: samba Mounting a CIFS share off an IBM N3300 filer (== NetApp FAS 2020), I experienced some file managers, applications, ... to more or less regularly lock up / don't do anything while trying to browse folders. Looking more into this, it seems the problem is more basic. The thing is mounted using cifs: //192.168.1.252/data on /opt/filer type cifs (rw,mand) Looking at dmesg, these errors do appear more or less frequently when trying to read off the filer: [ 3757.049058] CIFS VFS: No response for cmd 50 mid 11642 [ 3763.068762] CIFS VFS: Bad protocol string signature header 4 [ 3763.068788] CIFS VFS: bad smb detected. The Mid=11646 [ 3763.068794] Bad SMB: : dump of 48 bytes of data at 0xf46e8000 [ 3763.068825] 0040 0004 0032 80018800 @ . . . . . . . 2 . . . . . . . [ 3763.068855] 1e680040 . . . . . . . . . . . . @ . h . [ 3763.068885] 2d7e0800 0400020a 0200 3800 . . ~ - . . . . . . . . . 8 . . [ 3778.069085] CIFS VFS: No response for cmd 50 mid 11646 [ 3784.087139] CIFS VFS: Bad protocol string signature header 4 [ 3784.087161] CIFS VFS: bad smb detected. The Mid=11650 [ 3784.087165] Bad SMB: : dump of 48 bytes of data at 0xf46e9500 [ 3784.087171] 0040 0004 0032 80018800 @ . . . . . . . 2 . . . . . . . [ 3784.087195] 1e680040 . . . . . . . . . . . . @ . h . [ 3784.087202] 2d820800 0400020a 0200 3800 . . . - . . . . . . . . . 8 . . [ 3799.084053] CIFS VFS: No response for cmd 50 mid 11650 [ 3805.102848] CIFS VFS: Bad protocol string signature header 4 [ 3805.102852] CIFS VFS: bad smb detected. The Mid=11654 [ 3805.102873] Bad SMB: : dump of 48 bytes of data at 0xf46e8540 [ 3805.102879] 0040 0004 0032 80018800 @ . . . . . . . 2 . . . . . . . [ 3805.102903] 1e680040 . . . . . . . . . . . . @ . h . [ 3805.102909] 2d860800 0400020a 0200 3800 . . . - . . . . . . . . . 8 . . [ 3820.100062] CIFS VFS: No response for cmd 50 mid 11654 [ 3826.119095] CIFS VFS: Bad protocol string signature header 4 [ 3826.119100] CIFS VFS: bad smb detected. The Mid=11658 [ 3826.119120] Bad SMB: : dump of 48 bytes of data at 0xf46e8fc0 [ 3826.119127] 0040 0004 0032 80018800 @ . . . . . . . 2 . . . . . . . [ 3826.119151] 1e680040 . . . . . . . . . . . . @ . h . [ 3826.119157] 2d8a0800 0400020a 0200 3800 . . . - . . . . . . . . . 8 . . It happens once in a while copying things off the filer using the shell, and it happens almost reliably when browsing to the share using any visual file manager. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: smbfs 2:3.4.7~dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic-pae 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic-pae i686 Architecture: i386 CIFSMounts: Error: command ['mount', '|', 'grep', 'cifs'] failed with exit code 1: mount: only root can do that Date: Thu Apr 8 09:09:58 2010 InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) ProcEnviron: PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/bash SambaClientRegression: No SourcePackage: samba To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/557890/+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