[Kernel-packages] [Bug 2003226] Re: libvirt live migrate to a lower generation processor freeze the migrated vm
@Daniel testing rc versions might be ok, although typically at this point you'd want to consider switching to bisecting a git checkout of the kernel since there'll be a limited number of -rc's. -- 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/2003226 Title: libvirt live migrate to a lower generation processor freeze the migrated vm Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, i have several libvirt hosts servers with differents CPU generation, in particular : - older generation : Intel Xeon E5-2640 v4 2.40GHz - newer generation : Intel Xeon Gold 5215 2.50GHz i recently re-install all this servers into ubuntu server 22.04.1 and since, when i live migrate a VM from a new generation processor to older generation processor the migrated guest freeze without generating any error logs. if i migrate the opposite way ( older cpu to newer cpu ) it works perfectly. previous version of hosts ( same hardware on ubuntu 16.04 ) did not present the problem the live migration is done with the following command ( issued from a third server playing the role of 'virtual-center' ) : virsh -c qemu+ssh://root@new_server/system migrate --verbose --live --undefinesource --persistent --unsafe guest_name qemu+ssh://root@old_server/system this one freeze the guest while the opposite migration : virsh -c qemu+ssh://root@old_server/system migrate --verbose --live --undefinesource --persistent --unsafe guest_name qemu+ssh://root@new_server/system works without problem migrate between 2 servers with same generation CPU also works perfectly the cpu configuration of guest is generic : qemu64 i have tried several ( almost all ) other virtual cpu configuration , always with the same problem. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 févr. 16 12:39 seq crw-rw 1 root audio 116, 33 févr. 16 12:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-15 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: FUJITSU PRIMERGY RX2530 M2 Package: linux (not installed) PciMultimedia: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=13e84e97-ad18-49ed-8050-c8f7293e5e7d ro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=13e84e97-ad18-49ed-8050-c8f7293e5e7d ro ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 5.15.0-60-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.release: 1.10 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.11 R1.10.0 for D3279-B1x dmi.board.name: D3279-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3279-B12 WGS03 GS02 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2530M2R1 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.11R1.10.0forD3279-B1x:bd09/29/2016:br1.10:svnFUJITSU:pnPRIMERGYRX2530M2:pvrGS01:rvnFUJITSU:rnD3279-B1:rvrS26361-D3279-B12WGS03GS02:cvnFUJITSU:ct23:cvrRX2530M2R1:skuABNK1565-V101-236: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2530 M2 dmi.product.sku: ABN:K1565-V101-236 dmi.product.version: GS01 dmi.sys.vendor: FUJITSU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 févr. 16 12:39 seq crw-rw 1 root audio 116, 33 févr. 16 12:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A
[Kernel-packages] [Bug 1938474] Re: delve golang debugger can't read vvar on arm64
** Merge proposal linked: https://code.launchpad.net/~bryce/britney/+git/britney/+merge/406611 -- 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/1938474 Title: delve golang debugger can't read vvar on arm64 Status in Delve: Unknown Status in delve package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Also documented upstream: https://github.com/go-delve/delve/issues/2630 In version 1.6.1 of the delve golang debugger, a 'dump' feature was added. https://github.com/go-delve/delve/pull/2173 Since that time, arm64 autopkgtest of delve has been failing like so: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/delve/20210707_003312_d3699@/log.gz === RUN TestDump proc_test.go:5117: testing normal dump proc_test.go:5029: bad DumpState {Mutex:sync.Mutex{state:0, sema:0x0}, Dumping:false, AllDone:true, Canceled:false, DoneChan:(chan struct {})(nil), ThreadsDone:5, ThreadsTotal:5, MemDone:0x657b000, MemTotal:0x657d000, Err:error(nil)} --- FAIL: TestDump (0.98s) The test fails becaue MemDone != MemTotal. The decision on what to dump or not is based on smaps. The failing item is vvar. err when attempting to read is error(syscall.Errno) golang.org/x/sys/unix.EIO (5) Notably however, this test passes in debian CI. (kernel 4.19) Also, running on older series such as bionic/focal does pass. vvar section from vm with kernel 5.4 (test pass): 924a4000-924a5000 r--p 00:00 0 [vvar] Size: 4 kB KernelPageSize:4 kB MMUPageSize: 4 kB Rss: 0 kB Pss: 0 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 0 kB Private_Dirty: 0 kB Referenced:0 kB Anonymous: 0 kB LazyFree: 0 kB AnonHugePages: 0 kB ShmemPmdMapped:0 kB FilePmdMapped:0 kB Shared_Hugetlb:0 kB Private_Hugetlb: 0 kB Swap: 0 kB SwapPss: 0 kB Locked:0 kB THPeligible:0 VmFlags: rd mr de vvar from failing case ac144000-ac146000 r--p 00:00 0 [vvar] Size: 8 kB KernelPageSize:4 kB MMUPageSize: 4 kB Rss: 0 kB Pss: 0 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 0 kB Private_Dirty: 0 kB Referenced:0 kB Anonymous: 0 kB LazyFree: 0 kB AnonHugePages: 0 kB ShmemPmdMapped:0 kB FilePmdMapped: 0 kB Shared_Hugetlb:0 kB Private_Hugetlb: 0 kB Swap: 0 kB SwapPss: 0 kB Locked:0 kB THPeligible:0 VmFlags: rd mr pf de Two noticible differences 1) 4kB vs 8kB size 2) Failing case adds the "pf" flag ("pure PFN range") Open questions: 1) Would we expect that a debugger could read vvar on arm64? 2) Any thoughts on why this seems to work on older kernels? 3) Do we believe this to be a kernel bug, or should the delve debugger not expect to read vvar? 4) Is it sensible for a debugger to attempt to read things with the "pf" flag? Note that the "dd" ("do not include area into core dump") flag is not set. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 21:21 seq crw-rw 1 root audio 116, 33 Jul 29 21:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu67 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu Jul 29 21:34:34 2021 InstallationDate: Installed on 2021-07-29 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210729) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M MachineType: QEMU QEMU Virtual Machine PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB:
[Kernel-packages] [Bug 1938474] Re: delve golang debugger can't read vvar on arm64
** Bug watch added: github.com/go-delve/delve/issues #2630 https://github.com/go-delve/delve/issues/2630 ** Also affects: linux via https://github.com/go-delve/delve/issues/2630 Importance: Unknown Status: Unknown ** Project changed: linux => delve -- 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/1938474 Title: delve golang debugger can't read vvar on arm64 Status in Delve: Unknown Status in delve package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Also documented upstream: https://github.com/go-delve/delve/issues/2630 In version 1.6.1 of the delve golang debugger, a 'dump' feature was added. https://github.com/go-delve/delve/pull/2173 Since that time, arm64 autopkgtest of delve has been failing like so: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/delve/20210707_003312_d3699@/log.gz === RUN TestDump proc_test.go:5117: testing normal dump proc_test.go:5029: bad DumpState {Mutex:sync.Mutex{state:0, sema:0x0}, Dumping:false, AllDone:true, Canceled:false, DoneChan:(chan struct {})(nil), ThreadsDone:5, ThreadsTotal:5, MemDone:0x657b000, MemTotal:0x657d000, Err:error(nil)} --- FAIL: TestDump (0.98s) The test fails becaue MemDone != MemTotal. The decision on what to dump or not is based on smaps. The failing item is vvar. err when attempting to read is error(syscall.Errno) golang.org/x/sys/unix.EIO (5) Notably however, this test passes in debian CI. (kernel 4.19) Also, running on older series such as bionic/focal does pass. vvar section from vm with kernel 5.4 (test pass): 924a4000-924a5000 r--p 00:00 0 [vvar] Size: 4 kB KernelPageSize:4 kB MMUPageSize: 4 kB Rss: 0 kB Pss: 0 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 0 kB Private_Dirty: 0 kB Referenced:0 kB Anonymous: 0 kB LazyFree: 0 kB AnonHugePages: 0 kB ShmemPmdMapped:0 kB FilePmdMapped:0 kB Shared_Hugetlb:0 kB Private_Hugetlb: 0 kB Swap: 0 kB SwapPss: 0 kB Locked:0 kB THPeligible:0 VmFlags: rd mr de vvar from failing case ac144000-ac146000 r--p 00:00 0 [vvar] Size: 8 kB KernelPageSize:4 kB MMUPageSize: 4 kB Rss: 0 kB Pss: 0 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 0 kB Private_Dirty: 0 kB Referenced:0 kB Anonymous: 0 kB LazyFree: 0 kB AnonHugePages: 0 kB ShmemPmdMapped:0 kB FilePmdMapped: 0 kB Shared_Hugetlb:0 kB Private_Hugetlb: 0 kB Swap: 0 kB SwapPss: 0 kB Locked:0 kB THPeligible:0 VmFlags: rd mr pf de Two noticible differences 1) 4kB vs 8kB size 2) Failing case adds the "pf" flag ("pure PFN range") Open questions: 1) Would we expect that a debugger could read vvar on arm64? 2) Any thoughts on why this seems to work on older kernels? 3) Do we believe this to be a kernel bug, or should the delve debugger not expect to read vvar? 4) Is it sensible for a debugger to attempt to read things with the "pf" flag? Note that the "dd" ("do not include area into core dump") flag is not set. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 21:21 seq crw-rw 1 root audio 116, 33 Jul 29 21:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu67 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu Jul 29 21:34:34 2021 InstallationDate: Installed on 2021-07-29 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210729) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M MachineType: QEMU QEMU Virtual
[Kernel-packages] [Bug 1891336] Re: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel
It appears to fail only for ppc64el. The proper solution sounds to be complicated; would it be suitable as a temporary workaround to drop that arch from the cpufreqd package (and leave this bug open until the underlying issue is resolved)? -- 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/1891336 Title: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel Status in cpufreqd package in Ubuntu: New Status in gkrellm2-cpufreq package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I don't know how important that is as gkrellm2-cpufreq itself is scheduled for removal. But I wanted to make sure that it is known that the Debian kernel produces "libcpupower-dev" which isn't available in Ubuntu and thereby blocking various things in proposed. root@d10-sid:~# apt-cache show libcpupower-dev Package: libcpupower-dev Source: linux Version: 5.7.10-1 Installed-Size: 169 Maintainer: Debian Kernel Team Architecture: amd64 Replaces: libcpufreq-dev Provides: libcpufreq-dev Depends: libcpupower1 (= 5.7.10-1) Conflicts: libcpufreq-dev Description-en: CPU frequency and voltage scaling tools for Linux (development files) libcpupower is a library for inspecting and controlling cpufreq and cpuidle tunables. . This package is needed to compile programs against libcpupower. gkrellm2-cpufreq will most likely be removed from goovy as it makes no sense without that build-dep. Never the less the kernel Team could evaluate if providing "libcpupower-dev" makes sense for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1891336/+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 1848013] Re: liburing package missing for >= 5.1 kernels
Thanks for this bug report, it does look like liburing would be worthy of packaging and inclusion in debian and ubuntu, although I don't think it's correct to have this filed against libaio. Instead I'm tagging it as 'needs packaging', per the New Package Policy, which covers this situation: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages It sounds like a 0.2 release of liburing is pending, and since FF for eoan has already closed, maybe worth waiting until 0.2 is out: https://www.mail-archive.com/linux-block@vger.kernel.org/msg39689.html Fwiw, there is a RPM package of 0.1 (https://pkgs.org/download/liburing), and from its .spec file the packaging looks super straightforward. Hopefully someone will grab it from the needs-packaging queue soon. Or, if you'd be interested in taking a first crack at the deb packaging, that would certainly be a great way to get this moved forward. ** Tags added: needs-packaging ** Package changed: libaio (Ubuntu) => ubuntu ** Summary changed: - liburing package missing for >= 5.1 kernels + [needs-packaging] liburing package needed for >= 5.1 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/1848013 Title: [needs-packaging] liburing package needed for >= 5.1 kernels Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: eoan will ship with a 5.3 kernel and has support for the io_uring interface. In order to allow applications to use that the userspace library liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in addition to the 5.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1848013/+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 1848013] Re: liburing package missing for >= 5.1 kernels
** Changed in: libaio (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/1848013 Title: liburing package missing for >= 5.1 kernels Status in libaio package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: eoan will ship with a 5.3 kernel and has support for the io_uring interface. In order to allow applications to use that the userspace library liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in addition to the 5.3 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaio/+bug/1848013/+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 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
The firmware update seems to have done the trick. -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+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 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
Thanks, I've installed that firmware update and will give it a try. As I expected, disabling bluetooth in BIOS didn't resolve the issue. Apparently in the Dell XPS 13 9730 the wifi card is soldered to the motherboard, so replacing it is sadly not an option. I'm also keeping an eye on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988 which seems relevant at least to my case. -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+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 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
That's too bad it didn't work, but thanks for testing it. I've read suggestions that it relates to bluetooth, so am currently testing with that disabled in bios, but I don't have high hopes. If it doesn't, I'll probably just go with the replacement option myself. -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+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 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
I'm able to reproduce this with QCA6174 802.11ac Wireless Network Adapter on a Dell XPS 13 9370 (07E6). From a bit of googling this seems to be a widespread problem, but only mentioned solution is to replace the wifi card, as also mentioned in this bug report. Jay, did you have any success from testing the newer kernel + firmware? -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+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 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+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 713864] Re: Black screen with nouveau on a GeForce 8600M GT, either LiveCD or fresh install
Expired, here and upstream. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Incomplete = 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/713864 Title: Black screen with nouveau on a GeForce 8600M GT, either LiveCD or fresh install Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-video-nouveau” package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-nouveau Using Ubuntu Natty up-to-date on a Dell Vostro 1500 with a GeForce 8600M GT GPU. When I boot on the LiveCD or on a fresh install, nouveau seems to load correctly but all I get is a black screen. On the attached Xorg.log, the lines at 27.960 is when I press Ctrl+Alt+F1 to see if I can get a tty (I still get a black screen), and 31.965 is when I Ctrl+Alt+Del to reboot the computer. Please let me know if you need additional informations. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic x86_64 Architecture: amd64 Date: Sun Feb 6 00:58:13 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.0.2: added GraphicsCard: Subsystem: Dell Device [1028:0228] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110131) MachineType: Dell Inc. Vostro 1500 ProcEnviron: LANGUAGE=fr_FR.UTF-8:fr:en_GB:en LANG=fr_FR.UTF-8 LC_MESSAGES=fr_FR.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=55a88c4e-93f6-4ba7-aeae-9104bddc2682 ro nomodeset SourcePackage: xserver-xorg-video-nouveau dmi.bios.date: 04/21/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.2.1+glibmainloop4-0ubuntu9 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu1 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2+git20110124.fadee040-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/713864/+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 1047710] Re: [nouveau] OOPS - Page fault running piglit in nv50_vm_flush+0x1f/0xb0
Someone else can run piglit to reproduce if you care about the bug. ** Tags removed: needs-kernel-logs needs-upstream-testing ** Tags added: kernel-unable-to-test-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/1047710 Title: [nouveau] OOPS - Page fault running piglit in nv50_vm_flush+0x1f/0xb0 Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Precise: Confirmed Bug description: While running the piglit testsuite for mesa on a system with the nouveau driver, the system crashed with a kernel OOPS. The attached photo is a bit hard to read. I could not locate the crash data in any log files after rebooting the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1047710/+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 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.
nico, from your snippet sounds like you're on hw version 3; the patch here is relevant to v7. v3 has been supported by the driver for some time, so it may be you have some more specific bug. Might be best to open a new bug report with full logs, so that issue can be focused on separately. -- 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/1166442 Title: Elantech clickpad/touchpad lacks multitouch features. Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Precise: In Progress Status in “linux” source package in Quantal: In Progress Status in “linux” source package in Raring: In Progress Status in “linux” source package in Saucy: In Progress Status in “linux” package in Arch Linux: New Bug description: Newer versions of the Elantech multitouch trackpad are not fully supported in Linux. These appear in many of the newer Samsung laptops, for example. elantech.c in the kernel needs to be updated to support these models (up to v7 perhaps?) This bug is confirmed to affect a range of samsung laptops running Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current (3.9) upstream kernel. A dkms package was produced in 2011 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64) which may fix certain older laptops affected by this issue, but doesn't fix newer models. == Original Report == Hello, So far I've been having a problem with my Elantech multitouch trackpad in Linux. Basically all i get is right click, left click, and tap to click, along with basic movement. The problem seems to be rooted in improper detection of the trackpad, likely b/c its a new revision or whatnot. Of note is that working elantech trackpads of the past in forums i scouted through show up as ETPS/2 Elantech Touchpad. Mine just shows up in xinput as PS/2 Elantech Touchpad. I think this might be a simple fix in the end, just improper detection, I hope. For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on Ubuntu 13.04 thus far, with all combinations of psmouse. -- What's expected: touchpad multitouch support What happened: basic touchpad support Laptop mode: Samsung Series 7 NP780 series Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04 Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and psmouse-alps-dst. No improvements so removed. synclient -l reports Couldn't find synaptics properties. No synaptics driver loaded? -- See attached for more info. Ask anything you need! --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gscoppino 2272 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d InstallationDate: Installed on 2013-04-06 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7 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.104 StagingDrivers: rts5139 Tags: raring staging Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03ABU.139.130226.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP780Z5E-S01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 770Z5E/780Z5E/870Z5E/880Z5E dmi.product.version:
[Kernel-packages] [Bug 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.
From linus' tree, posted there last week. ** Patch added: elantech_v7.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442/+attachment/3742049/+files/elantech_v7.patch ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Low Status: 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/1166442 Title: Elantech clickpad/touchpad lacks multitouch features. Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Precise: New Status in “linux” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux” source package in Saucy: Confirmed Status in “linux” package in Arch Linux: New Bug description: Newer versions of the Elantech multitouch trackpad are not fully supported in Linux. These appear in many of the newer Samsung laptops, for example. elantech.c in the kernel needs to be updated to support these models (up to v7 perhaps?) This bug is confirmed to affect a range of samsung laptops running Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current (3.9) upstream kernel. A dkms package was produced in 2011 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64) which may fix certain older laptops affected by this issue, but doesn't fix newer models. == Original Report == Hello, So far I've been having a problem with my Elantech multitouch trackpad in Linux. Basically all i get is right click, left click, and tap to click, along with basic movement. The problem seems to be rooted in improper detection of the trackpad, likely b/c its a new revision or whatnot. Of note is that working elantech trackpads of the past in forums i scouted through show up as ETPS/2 Elantech Touchpad. Mine just shows up in xinput as PS/2 Elantech Touchpad. I think this might be a simple fix in the end, just improper detection, I hope. For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on Ubuntu 13.04 thus far, with all combinations of psmouse. -- What's expected: touchpad multitouch support What happened: basic touchpad support Laptop mode: Samsung Series 7 NP780 series Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04 Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and psmouse-alps-dst. No improvements so removed. synclient -l reports Couldn't find synaptics properties. No synaptics driver loaded? -- See attached for more info. Ask anything you need! --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gscoppino 2272 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d InstallationDate: Installed on 2013-04-06 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7 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.104 StagingDrivers: rts5139 Tags: raring staging Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03ABU.139.130226.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP780Z5E-S01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.
Verified the patch applied to the LTS quantal backport kernel. Patch should apply cleanly to all kernels between 3.5 and 3.10, and since it affects a broad range of Samsung laptops it may well be worth considering for SRUs to precise and newer. -- 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/1166442 Title: Elantech clickpad/touchpad lacks multitouch features. Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Precise: New Status in “linux” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux” source package in Saucy: Confirmed Status in “linux” package in Arch Linux: New Bug description: Newer versions of the Elantech multitouch trackpad are not fully supported in Linux. These appear in many of the newer Samsung laptops, for example. elantech.c in the kernel needs to be updated to support these models (up to v7 perhaps?) This bug is confirmed to affect a range of samsung laptops running Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current (3.9) upstream kernel. A dkms package was produced in 2011 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64) which may fix certain older laptops affected by this issue, but doesn't fix newer models. == Original Report == Hello, So far I've been having a problem with my Elantech multitouch trackpad in Linux. Basically all i get is right click, left click, and tap to click, along with basic movement. The problem seems to be rooted in improper detection of the trackpad, likely b/c its a new revision or whatnot. Of note is that working elantech trackpads of the past in forums i scouted through show up as ETPS/2 Elantech Touchpad. Mine just shows up in xinput as PS/2 Elantech Touchpad. I think this might be a simple fix in the end, just improper detection, I hope. For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on Ubuntu 13.04 thus far, with all combinations of psmouse. -- What's expected: touchpad multitouch support What happened: basic touchpad support Laptop mode: Samsung Series 7 NP780 series Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04 Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and psmouse-alps-dst. No improvements so removed. synclient -l reports Couldn't find synaptics properties. No synaptics driver loaded? -- See attached for more info. Ask anything you need! --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gscoppino 2272 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d InstallationDate: Installed on 2013-04-06 (3 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7 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.104 StagingDrivers: rts5139 Tags: raring staging Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03ABU.139.130226.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP780Z5E-S01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 770Z5E/780Z5E/870Z5E/880Z5E dmi.product.version: P03ABU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: