[Kernel-packages] [Bug 1730924]
Hello! Tsuchiya & Verdre: Do you have some fixes for instability issues when card is in 5GHz AP mode? This is issue which we are observing on 88W8997 SDIO wifi chips. I described some problems related to power save mode, nl80211/cfg80211 layer and mwifiex driver in email which I sent to linux-wireless mailing list: https://lore.kernel.org/linux- wireless/20200609111544.v7u5ort3yk4s7coy@pali/ But I have not got any response about it yet and I think that without fixing those issues at cfg80211 layer we cannot fix mwifiex driver for power save mode. Andy, are you still able to help us with (generic/cfg80211) wireless part? -- 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/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+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 815914] Re: dell_wmi: Unknown key eXXX pressed
In case somebody would debug this problem again, here is answer to my question from Jean-Louis back in 2015: AT Translated Set 2 keyboard reports these events: left button: EV_MSC MSC_SCAN 219 EV_KEY KEY_LEFTMETA (0x7d) pressed EV_SYN code=0 value=0 EV_MSC MSC_SCAN 45 EV_KEY KEY_X (0x2d) pressed EV_SYN code=0 value=0 EV_MSC MSC_SCAN 45 EV_KEY KEY_X (0x2d) released EV_SYN code=0 value=0 EV_MSC MSC_SCAN 219 EV_KEY KEY_LEFTMETA (0x7d) released EV_SYN code=0 value=0 middle button: EV_MSC MSC_SCAN 133 EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed EV_SYN code=0 value=0 EV_MSC MSC_SCAN 133 EV_KEY KEY_BRIGHTNESSDOWN (0xe0) released EV_SYN code=0 value=0 right button: EV_MSC MSC_SCAN 132 EV_KEY KEY_NEXTSONG (0xa3) pressed EV_SYN code=0 value=0 EV_MSC MSC_SCAN 132 EV_KEY KEY_NEXTSONG (0xa3) released EV_SYN code=0 value=0 So left button generates combination META+X, middle button is reported as brightness down and right button as next song. So keys are reported via PS/2 keyboard and also by WMI. Dell WMI events are ignored by kernel to prevent duplication. -- 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/815914 Title: dell_wmi: Unknown key eXXX pressed Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Bug description: I got a new Dell XPS 15 laptop (L502X). Now when i'm changing the volume with the hotkeys, dmesg throws me the following errors: [16971.294903] dell_wmi: Unknown key e0f8 pressed [16985.978025] dell_wmi: Unknown key e0f7 pressed [16986.731775] dell_wmi: Unknown key e0f9 pressed The keys actually work, but the WMI doesn't seem to be supported yet. Is there any chance to fix this? If you need additional information, feel free to ask! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/815914/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
Hi Kamal! When will be this bug fixed in precise kernel release? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux-lts-trusty source package in Precise: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
@Kamal: I tested your build 3.13.0-69-generic #112~precise1+lp1527902 and it fixed this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: Fix Committed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Fix Committed Status in linux-lts-trusty source package in Precise: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
So it is same error code for recvfrom() on UDP packet. It is possible that it is same problem... Anyway, currently I cannot test next kernel, so if you cannot reproduce that bug, you need to wait some time after I could test next kernel build... -- 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/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1528664] Re: Resume from hibernation does not working since 3.13.0-74
On Sunday 03 January 2016 23:34:52 Christopher M. Penalver wrote: > Pali, could you please cold boot (not resume from hibernate) and then > perform the request in > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528664/comments/1 > ? Which logs or debug information do you need? > ** Tags added: kernel-fixed-upstream-4.4-rc6 needs-reverse-bisect > > ** No longer affects: linux-lts-trusty (Ubuntu) Nope, this bug affects *only* linux-lts-trusty package found in Ubuntu Precise. Bug was introduced in linux-lts-trusty. So why removed it from package list? > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1528664 Title: Resume from hibernation does not working since 3.13.0-74 Status in linux package in Ubuntu: Incomplete Bug description: My laptop Dell Latitude E6440 is not able to resume from hibernation on linux kernel version 3.13.0-74. Version 3.13.0-71 is last working. When I try to resume on version 3.13.0-74 it just show bootlog, then reading resume image. And after resume image is loaded, screen goes black and laptop do nothing. Network is not working, so I cannot connect to laptop. Even enabled SYSRQ keys do not work. Hard shutdown with power button is needed. After next boot there is nothing about last failed resume in syslog, so I do not have any information for debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528664/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
I tested kernel 3.13.0-68-generic #111~Commit40c4e87e7 and this is good. -- 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/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
Now I tested also v3.13.11-ckt32-trusty kernel and this is bad. -- 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/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
Looks like that program dig is not affected, so not all stub resolvers are non working. Kopete uses libiris xmpp library which uses jdns resolver. It is 100% reproducable. I tested also new upstream 4.x kernels and they do not have this problem. Only ubuntu kernels >= 3.13.0-69. If you need to test jdns library, upstream project has also example dns lookup cmdline tool in git repo: https://github.com/psi-im/iris/tree/master/src/jdns/tools/jdns (Call it with arg "-6" against some IPv6 DNS server) I tested it and it reacts exactly same as Kopete, on 3.13.0-69 kernel (and above) just do not receive UDP IPv6 packets. As I wrote in description strace show that every recvfrom() calls just return -EAGAIN. But wireshark see that packets was received. -- 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/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
Now I tested version 3.13.0-69.112~precise1 from https://launchpad.net /~canonical-kernel-team/+archive/ubuntu/ppa/+packages?field.name_filter =linux-lts-trusty_filter=_filter=precise and it has same problem as 3.13.0-71. So this bug was introduced somewhere between -68 and -69. -- 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/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1528664] Re: Resume from hibernation does not working since 3.13.0-74
I tested v4.4-rc6-wily and hibernation is working fine. ** Tags added: kernel-fixed-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/1528664 Title: Resume from hibernation does not working since 3.13.0-74 Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Triaged Bug description: My laptop Dell Latitude E6440 is not able to resume from hibernation on linux kernel version 3.13.0-74. Version 3.13.0-71 is last working. When I try to resume on version 3.13.0-74 it just show bootlog, then reading resume image. And after resume image is loaded, screen goes black and laptop do nothing. Network is not working, so I cannot connect to laptop. Even enabled SYSRQ keys do not work. Hard shutdown with power button is needed. After next boot there is nothing about last failed resume in syslog, so I do not have any information for debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528664/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
Now I tested your last build and it does *not* fix this bug :-( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received
For reproducing just try to use Kopete IM client and try to connect to some jabber server. Kopete must use IPv6 recursive DNS server for translating jabber SRV or A records. DNS server address is read from standard file /etc/resolv.conf. So if you do not have IPv6 connectivity, you can you start some recursive (or forward) DNS server on IPv6 localhost and set nameserver ::1 in /etc/resolv.conf. This is quick hack, but should work. I see that NetworkManager on Ubuntu is already using dnsmasq (as forwarder), but does not have enabled IPv6 support on localhost. It automatically add "nameserver 127.0.0.1" line into /etc/resolv.conf. To tell dnsmasq to listen also on IPv6 localhost add configuration like: $ echo listen-address=::1 > /etc/NetworkManager/dnsmasq.d/ipv6 (and reboot) And set "nameserver ::1" in /etc/resolv.conf (note that NetworkManager is changing that file when reconnecting...) -- 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/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1528664] [NEW] Resume from hibernation does not working since 3.13.0-74
Public bug reported: My laptop Dell Latitude E6440 is not able to resume from hibernation on linux kernel version 3.13.0-74. Version 3.13.0-71 is last working. When I try to resume on version 3.13.0-74 it just show bootlog, then reading resume image. And after resume image is loaded, screen goes black and laptop do nothing. Network is not working, so I cannot connect to laptop. Even enabled SYSRQ keys do not work. Hard shutdown with power button is needed. After next boot there is nothing about last failed resume in syslog, so I do not have any information for debugging. ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1528664 Title: Resume from hibernation does not working since 3.13.0-74 Status in linux-lts-trusty package in Ubuntu: New Bug description: My laptop Dell Latitude E6440 is not able to resume from hibernation on linux kernel version 3.13.0-74. Version 3.13.0-71 is last working. When I try to resume on version 3.13.0-74 it just show bootlog, then reading resume image. And after resume image is loaded, screen goes black and laptop do nothing. Network is not working, so I cannot connect to laptop. Even enabled SYSRQ keys do not work. Hard shutdown with power button is needed. After next boot there is nothing about last failed resume in syslog, so I do not have any information for debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1528664/+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 1527902] [NEW] 3.13.0-71: IPv6 UDP DNS packets are not received
Public bug reported: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1527902 Title: 3.13.0-71: IPv6 UDP DNS packets are not received Status in linux-lts-trusty package in Ubuntu: New Bug description: After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server. I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect. Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers. Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied. So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1527902/+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 815914] Re: dell_wmi: Unknown key eXXX pressed
Old bug, I would like to ask: Does linux report key press to userspace (scan code via "AT Translated Set 2 keyboard") when "Shortcut key" or "Audio Panel key" is pressed on Dell XPS 15 laptop (L502X)? Because now dell-wmi receive events for those two keys, but ignore/drop it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/815914 Title: dell_wmi: Unknown key eXXX pressed Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Bug description: I got a new Dell XPS 15 laptop (L502X). Now when i'm changing the volume with the hotkeys, dmesg throws me the following errors: [16971.294903] dell_wmi: Unknown key e0f8 pressed [16985.978025] dell_wmi: Unknown key e0f7 pressed [16986.731775] dell_wmi: Unknown key e0f9 pressed The keys actually work, but the WMI doesn't seem to be supported yet. Is there any chance to fix this? If you need additional information, feel free to ask! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/815914/+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 1199217] Re: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all
Userspace daemon hdapsd starting from version 20141024 has also support for Dell SMO88xx accelerometers. Package hdapsd version 1:20141203-1 is already packaged in Ubuntu Vivid release. Older ubuntu versions have older version of hdapsd which do not have SMO88xx support. -- 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/1199217 Title: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all Status in linux package in Ubuntu: Confirmed Bug description: CID: 201201-10339 Dell Latitude E6530 [1] CID: 201307-13941 Dell Latitude E5440 [2] According to the information provided by Dell, these systems should have an accelerometer on the motherboard (Free-Fall sensor), but it cannot be detected at all (cannot be found in /proc/bus/input/devices) If using windows, it shows ACPI/SMO8810 in device manager If you run lspnp, you can see: 00:0c SMO8810 (unknown) [1] http://www.dell.com/downloads/global/products/latit/dell_latitude_e6530_spec_sheet.pdf [2] http://www.dell.com/us/business/p/latitude-e5440-laptop/pd This issue has also been verified with 12.04.4, see bug 1310879 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1635 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 49' Mixer name : 'IDT 92HD93BXX' Components : 'HDA:111d76df,10280535,00100203 HDA:14f12c06,14f1000f,0010' Controls : 20 Simple ctrls : 10 Date: Tue Jul 9 11:09:52 2013 HibernationDevice: RESUME=UUID=8ee31955-e727-4041-b013-ddde9c2533a6 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Latitude E6530 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=81b802b0-1e06-43e7-8c92-b241adf7768c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/19/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1199217/+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 1450813] Re: Regression in mei_me.ko for 3.13.0-51
I tested new kernel package linux-lts-trusty on ubuntu precise from backports and it fixes this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450813 Title: Regression in mei_me.ko for 3.13.0-51 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Bug description: After upgrading linux-image-3.13.0-49-generic to linux- image-3.13.0-51-generic I started getting this error message in dmesg: [ 6.352555] mei_me :00:16.0: irq 47 for MSI/MSI-X [ 6.355708] mei_me :00:16.0: version message write failed: ret = -5 [ 6.355712] mei_me :00:16.0: hbm_start failed ret = -5 [ 6.355714] mei_me :00:16.0: reset failed [ 6.355716] mei_me :00:16.0: link layer initialization failed. [ 6.355717] mei_me :00:16.0: init hw failure. [ 6.355880] mei_me :00:16.0: initialization failed. Downgrading back to linux-image-3.13.0-49-generic fixed this problem. So this is regression for version 3.13.0-51. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450813/+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 1450813] Re: Regression in mei_me.ko for 3.13.0-51
I tested 0001-mei-me-fix-hw-ready-reset-flow.patch and 0002-UBUNTU-Fix- mei-me-release-hw-from-reset-only-during-.patch on top of linux- image-3.13.0-51-generic and those two patches also fixed init mei problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450813 Title: Regression in mei_me.ko for 3.13.0-51 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Bug description: After upgrading linux-image-3.13.0-49-generic to linux- image-3.13.0-51-generic I started getting this error message in dmesg: [ 6.352555] mei_me :00:16.0: irq 47 for MSI/MSI-X [ 6.355708] mei_me :00:16.0: version message write failed: ret = -5 [ 6.355712] mei_me :00:16.0: hbm_start failed ret = -5 [ 6.355714] mei_me :00:16.0: reset failed [ 6.355716] mei_me :00:16.0: link layer initialization failed. [ 6.355717] mei_me :00:16.0: init hw failure. [ 6.355880] mei_me :00:16.0: initialization failed. Downgrading back to linux-image-3.13.0-49-generic fixed this problem. So this is regression for version 3.13.0-51. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450813/+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 1450813] Re: Regression in mei_me.ko for 3.13.0-51
I tested mei.ko and mei-me.ko drivers from linux-image-3.13.0-51-generic source with these two additional patches: http://kernel.ubuntu.com/git/kamal/ubuntu- trusty.git/commit/?h=pali-1450813id=cce32088947917cb93520b9dffc0fd4bb0b21ade http://kernel.ubuntu.com/git/kamal/ubuntu- trusty.git/commit/?h=pali-1450813id=845a0dc3427014d8ff74a34f90120be88e98760c And after that mei.ko and mei-me.ko initialized without any error. -- 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/1450813 Title: Regression in mei_me.ko for 3.13.0-51 Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: After upgrading linux-image-3.13.0-49-generic to linux- image-3.13.0-51-generic I started getting this error message in dmesg: [ 6.352555] mei_me :00:16.0: irq 47 for MSI/MSI-X [ 6.355708] mei_me :00:16.0: version message write failed: ret = -5 [ 6.355712] mei_me :00:16.0: hbm_start failed ret = -5 [ 6.355714] mei_me :00:16.0: reset failed [ 6.355716] mei_me :00:16.0: link layer initialization failed. [ 6.355717] mei_me :00:16.0: init hw failure. [ 6.355880] mei_me :00:16.0: initialization failed. Downgrading back to linux-image-3.13.0-49-generic fixed this problem. So this is regression for version 3.13.0-51. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450813/+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 1450813] [NEW] Regression in mei_me.ko for 3.13.0-51
Public bug reported: After upgrading linux-image-3.13.0-49-generic to linux- image-3.13.0-51-generic I started getting this error message in dmesg: [ 6.352555] mei_me :00:16.0: irq 47 for MSI/MSI-X [ 6.355708] mei_me :00:16.0: version message write failed: ret = -5 [ 6.355712] mei_me :00:16.0: hbm_start failed ret = -5 [ 6.355714] mei_me :00:16.0: reset failed [ 6.355716] mei_me :00:16.0: link layer initialization failed. [ 6.355717] mei_me :00:16.0: init hw failure. [ 6.355880] mei_me :00:16.0: initialization failed. Downgrading back to linux-image-3.13.0-49-generic fixed this problem. So this is regression for version 3.13.0-51. ** Affects: linux (Ubuntu) Importance: Medium Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450813 Title: Regression in mei_me.ko for 3.13.0-51 Status in linux package in Ubuntu: New Bug description: After upgrading linux-image-3.13.0-49-generic to linux- image-3.13.0-51-generic I started getting this error message in dmesg: [ 6.352555] mei_me :00:16.0: irq 47 for MSI/MSI-X [ 6.355708] mei_me :00:16.0: version message write failed: ret = -5 [ 6.355712] mei_me :00:16.0: hbm_start failed ret = -5 [ 6.355714] mei_me :00:16.0: reset failed [ 6.355716] mei_me :00:16.0: link layer initialization failed. [ 6.355717] mei_me :00:16.0: init hw failure. [ 6.355880] mei_me :00:16.0: initialization failed. Downgrading back to linux-image-3.13.0-49-generic fixed this problem. So this is regression for version 3.13.0-51. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450813/+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 1450813] Re: Regression in mei_me.ko for 3.13.0-51
here are my test results: 3.13.0-51 without fa90035 and without e301eaa = init ok 3.13.0-51 without fa90035 = init ok 3.13.0-51 without e301eaa = init error 3.13.0-51 = init error So problem is really caused by commit fa90035. -- 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/1450813 Title: Regression in mei_me.ko for 3.13.0-51 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: After upgrading linux-image-3.13.0-49-generic to linux- image-3.13.0-51-generic I started getting this error message in dmesg: [ 6.352555] mei_me :00:16.0: irq 47 for MSI/MSI-X [ 6.355708] mei_me :00:16.0: version message write failed: ret = -5 [ 6.355712] mei_me :00:16.0: hbm_start failed ret = -5 [ 6.355714] mei_me :00:16.0: reset failed [ 6.355716] mei_me :00:16.0: link layer initialization failed. [ 6.355717] mei_me :00:16.0: init hw failure. [ 6.355880] mei_me :00:16.0: initialization failed. Downgrading back to linux-image-3.13.0-49-generic fixed this problem. So this is regression for version 3.13.0-51. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450813/+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 1444698] Re: linux-lts-trusty: 3.13.0-51.84~precise1 -proposed tracker
After upgrading linux-image-3.13.0-49-generic to linux- image-3.13.0-51-generic I started getting this error message in dmesg: [6.352555] mei_me :00:16.0: irq 47 for MSI/MSI-X [6.355708] mei_me :00:16.0: version message write failed: ret = -5 [6.355712] mei_me :00:16.0: hbm_start failed ret = -5 [6.355714] mei_me :00:16.0: reset failed [6.355716] mei_me :00:16.0: link layer initialization failed. [6.355717] mei_me :00:16.0: init hw failure. [6.355880] mei_me :00:16.0: initialization failed. Downgrading back to linux-image-3.13.0-49-generic fixed this problem. So this is regression for version 3.13.0-51. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1444698 Title: linux-lts-trusty: 3.13.0-51.84~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-51.84~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 15. April 2015 21:03 UTC kernel-stable-master-bug:1444141 kernel-stable-Prepare-package-end:Thursday, 16. April 2015 04:01 UTC kernel-stable-Promote-to-proposed-start:Thursday, 16. April 2015 04:01 UTC kernel-stable-Promote-to-proposed-end:Thursday, 16. April 2015 20:48 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 16. April 2015 22:04 UTC kernel-stable-Verification-testing-start:Thursday, 16. April 2015 22:04 UTC kernel-stable-Certification-testing-start:Thursday, 16. April 2015 22:04 UTC kernel-stable-Security-signoff-start:Thursday, 16. April 2015 22:04 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 16. April 2015 22:04 UTC kernel-stable-Security-signoff-end:Tuesday, 21. April 2015 20:01 UTC kernel-stable-Regression-testing-end:Tuesday, 21. April 2015 21:01 UTC kernel-stable-Certification-testing-end:Wednesday, 22. April 2015 14:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1444698/+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 1398544] Re: Please enable CONFIG_PCIEASPM_DEBUG
I tested 3.13.0.51.44 version of linux-image-generic-lts-trusty package on Ubuntu Precise 12.04.5 (which contains trusty kernel backports). And looks like it working fine. See log: $ lspci -nn | grep 00:1c.7 00:1c.7 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 [8086:8c1e] (rev d4) $ sudo lspci -s 00:1c.7 -v -v | grep -i aspm LnkCap: Port #8, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 1us, L1 16us LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- $ cat /sys/bus/pci/devices/:00:1c.7/power/link_state 0 $ echo 1 | sudo tee /sys/bus/pci/devices/:00:1c.7/power/link_state 1 $ sudo lspci -s 00:1c.7 -v -v | grep -i aspm LnkCap: Port #8, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 1us, L1 16us LnkCtl: ASPM L0s Enabled; RCB 64 bytes Disabled- Retrain- CommClk- $ echo 2 | sudo tee /sys/bus/pci/devices/:00:1c.7/power/link_state 2 $ sudo lspci -s 00:1c.7 -v -v | grep -i aspm LnkCap: Port #8, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 1us, L1 16us LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk- $ echo 3 | sudo tee /sys/bus/pci/devices/:00:1c.7/power/link_state 3 $ sudo lspci -s 00:1c.7 -v -v | grep -i aspm LnkCap: Port #8, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 1us, L1 16us LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk- $ echo 0 | sudo tee /sys/bus/pci/devices/:00:1c.7/power/link_state 0 $ sudo lspci -s 00:1c.7 -v -v | grep -i aspm LnkCap: Port #8, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 1us, L1 16us LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- tag verification-done-trusty tag -verification-needed-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/1398544 Title: Please enable CONFIG_PCIEASPM_DEBUG Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: [Impact] CONFIG_PCIEASPM_DEBUG (which is currently disabled for Ubuntu kernels) can be used to enable/disable ASPM settings per PCIE device. CONFIG_PCIEASPM (which is enabled for Ubuntu kernels) allows only to set global ASPM policy. BIOSes on more machines are buggy and lot of times do not configure ASPM for PCIE device property. CONFIG_PCIEASPM_DEBUG option allows users or testers to hotfix potential bugs in BIOS... That config option only add new sysfs files so it should not break anything else in kernel. [Test Case] Try to use PCIe ASPM sysfs debug interface. [Fix] Enable CONFIG_PCIEASPM_DEBUG vivid discussion: https://lists.ubuntu.com/archives/kernel-team/2014-December/051914.html -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398544/+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 1398544] Re: Please enable CONFIG_PCIEASPM_DEBUG
@Kamal Mostafa (kamalmostafa): Any chance to enable it also for 3.13 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/1398544 Title: Please enable CONFIG_PCIEASPM_DEBUG Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: CONFIG_PCIEASPM_DEBUG (which is currently disabled for Ubuntu kernels) can be used to enable/disable ASPM settings per PCIE device. CONFIG_PCIEASPM (which is enabled for Ubuntu kernels) allows only to set global ASPM policy. BIOSes on more machines are buggy and lot of times do not configure ASPM for PCIE device property. CONFIG_PCIEASPM_DEBUG option allows users or testers to hotfix potential bugs in BIOS... That config option only add new sysfs files so it should not break anything else in kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398544/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
On Friday 02 January 2015 11:56:09 Christopher M. Penalver wrote: Rob: So what I'm doing is more purposeful than nagging people about opening a new bug report with info that you already have. Spamming everyone with comments about a forum post is not helping here. As well, nobody has the information previously requested from you, as you didn't file a new report. Christopher, spamming everyone without your useless posts about duplicating same bug is even less useless. *IF* it is a BIOS/firmware/EC bug there is no point in opening yet another bug report for an issue that can't be resolved in Linux! Then you don't understand how linux kernel development works. And you Christopher do not know how linux kernel development works too! *NOBODY* in linux kernel development want from users to open duplicate bug reports. On select occasions, linux kernel engineers (not Dell employees) have implemented patches that WORKAROUND buggy, and outdated BIOS and hardware firmware. Citation needed (TM). Who and how implemented WORKAROUND for outdated BIOS? And what is outdated BIOS?? Btw, *I* am that developer who implemented WORKAROUND for current situation and sent patch to upstream kernel (which is now part of 3.18 release). But it has nothing with BIOS and there are no outdated BIOS versions. If you still do not understand this problem reported in this (and more other!) bugs happens on all Latitude Exx40 machines with any BIOS version. I'm fed up with you. You just spam bug reports, bitching on users who reported serious and critical problems, you did not helped with *anything* and also you did not implemented any fix for this problem. Sorry but *all* your comments in this (and others too) are totally useless. It did not helped me or other people who wanted to fix this problem. What you have done is just fed up users and forced them to not report bugs anymore because it is useless... However, by not filing a report, you are robbing developers to track the true impact this has, all the hardware permutations that may be affected, and the opportunity to review your hardware specifically (marking yourself affected, or making Me too! comments is useless here as it's not verifiable by anyone). As well, you are just adding comment noise that isn't contributing towards having the issue addressed. By not doing as previously requested, you are only delaying your own problem from being addressed. Addressed to whom? In last year nobody else provided any fix for this bug. So what are you trying to do? We already know that this problem is *same* for all Exx40 laptops and affect all people. And posts me too just say that this problem happens really on all those laptops and with all BIOS versions. -- Pali Rohár pali.ro...@gmail.com -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash
[Kernel-packages] [Bug 1402853] Re: Trusty update to v3.13.11-ckt12 stable release
All those specified alps commits: Input: alps - ignore bad data on Dell Latitudes E6440 and E7440 Input: alps - allow up to 2 invalid packets without resetting device Input: alps - ignore potential bare packets when device is out of sync Should fix alps bugs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1272624 https://bugzilla.redhat.com/show_bug.cgi?id=1145954 And all other duplicated alps bugs created by suggestion of Christopher M. Penalver (penalvch). ** Bug watch added: Red Hat Bugzilla #1145954 https://bugzilla.redhat.com/show_bug.cgi?id=1145954 -- 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/1402853 Title: Trusty update to v3.13.11-ckt12 stable release Status in linux package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from Linus' tree or in a minimally backported form of that patch. The v3.13.11-ckt12 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches are in the v3.13.11-ckt12 stable release: Linux 3.13.11-ckt12 drm/radeon: fix endian swapping in vbios fetch for tdp table IB/isert: Adjust CQ size to HW limits ACPI / PM: Ignore wakeup setting if the ACPI companion can't wake up MIPS: oprofile: Fix backtrace on 64-bit kernel clockevent: sun4i: Fix race condition in the probe code of/base: Fix PowerPC address parsing hack of/irq: Drop obsolete 'interrupts' vs 'interrupts-extended' text x86, mm: Set NX across entire PMD at boot can: esd_usb2: fix memory leak on disconnect can: dev: avoid calling kfree_skb() from interrupt context ASoC: wm_adsp: Avoid attempt to free buffers that might still be in use drm/i915: drop WaSetupGtModeTdRowDispatch:snb x86: Require exact match for 'noxsave' command line option bitops: Fix shift overflow in GENMASK macros ALSA: usb-audio: Add ctrl message delay quirk for Marantz/Denon devices ASoC: sgtl5000: Fix SMALL_POP bit definition ath9k: Fix RTC_DERIVED_CLK usage ath9k: Add version/revision macros for QCA9531 rt2x00: do not align payload on modern H/W mac80211: Fix regression that triggers a kernel BUG with CCMP ASoC: dpcm: Fix race between FE/BE updates and trigger iser-target: Handle DEVICE_REMOVAL event on network portal listener correctly ib_isert: Add max_send_sge=2 minimum for control PDU responses ASoC: rsnd: remove unsupported PAUSE flag ASoC: fsi: remove unsupported PAUSE flag srp-target: Retry when QP creation fails with ENOMEM vhost-scsi: Take configfs group dependency during VHOST_SCSI_SET_ENDPOINT target: Don't call TFO-write_pending if data_length == 0 nfs: Don't busy-wait on SIGKILL in __nfs_iocounter_wait md: Always set RECOVERY_NEEDED when clearing RECOVERY_FROZEN firewire: cdev: prevent kernel stack leaking into ioctl arguments Input: alps - ignore bad data on Dell Latitudes E6440 and E7440 zram: avoid kunmap_atomic() of a NULL pointer ARM: 8198/1: make kuser helpers depend on MMU ARM: 8191/1: decompressor: ensure I-side picks up relocated code libceph: do not crash on large auth tickets NFS: Don't try to reclaim delegation open state if recovery failed NFSv4: Ensure that we call FREE_STATEID when NFSv4.x stateids are revoked NFSv4: Fix races between nfs_remove_bad_delegation() and delegation return NFSv4.1: nfs41_clear_delegation_stateid shouldn't trust NFS_DELEGATED_STATE NFSv4: Ensure that we remove NFSv4.0 delegations when state has expired nfs: Fix use of uninitialized variable in nfs_getattr() nfs: fix pnfs direct write memory leak audit: keep inode pinned ALSA: usb-audio: Fix memory leak in FTU quirk parisc: Use compat layer for msgctl, shmat, shmctl and semtimedop syscalls dm btree: fix a recursion depth bug in btree walking code scsi: only re-lock door after EH on devices that were reset Input: alps - allow up to 2 invalid packets without resetting device Input: alps - ignore potential bare packets when device is out of sync ALSA: hda_intel: Add DeviceIDs for Sunrise Point-LP ALSA: hda_intel: Add Device IDs for Intel Sunrise Point PCH drm/radeon: add missing crtc unlock when setting up the MC drm/radeon: use gart for DMA IB tests drm/radeon: make sure mode init is complete in bandwidth_update drm/radeon: set correct CE ram size for CIK hwrng: pseries - port to new read API and fix stack corruption
[Kernel-packages] [Bug 1398544] Re: Please enable CONFIG_PCIEASPM_DEBUG
Hello, how did you decide? Will you enable CONFIG_PCIEASPM_DEBUG? -- 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/1398544 Title: Please enable CONFIG_PCIEASPM_DEBUG Status in linux package in Ubuntu: In Progress Bug description: CONFIG_PCIEASPM_DEBUG (which is currently disabled for Ubuntu kernels) can be used to enable/disable ASPM settings per PCIE device. CONFIG_PCIEASPM (which is enabled for Ubuntu kernels) allows only to set global ASPM policy. BIOSes on more machines are buggy and lot of times do not configure ASPM for PCIE device property. CONFIG_PCIEASPM_DEBUG option allows users or testers to hotfix potential bugs in BIOS... That config option only add new sysfs files so it should not break anything else in kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398544/+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 1377596] Re: pcie_aspm.policy=powersave pcie_aspm=force does not enable L0sL1 (L0s L1) on each ASPM PCIe device
See bug #1398544 it could help to debug this problem... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377596 Title: pcie_aspm.policy=powersave pcie_aspm=force does not enable L0sL1 (L0s L1) on each ASPM PCIe device Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: 4) What happened instead === # dmesg | grep -e _OSC -e ASPM [0.00] PCIe ASPM is forcibly enabled [0.085767] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.116506] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.116664] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME] [0.116764] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability] [0.125997] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported) # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.17.0-999-generic root=/dev/sda1 ro biosdevname=0 intel_pstate=enable ipv6.disabled=1 debug ignore_loglevel panic=10 pcie_aspm.policy=powersave pcie_aspm=force r8168.aspm=1 r8168.eee_enable=1 oops=panic # lspci - | grep ASPM LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s 1us, L1 8us LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 1us, L1 4us LnkCtl: ASPM L0s Enabled; RCB 64 bytes Disabled- CommClk- LnkCap: Port #6, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 512ns, L1 16us LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 64us LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ 3) What you expected to happen === # lspci - | grep ASPM LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s 1us, L1 8us LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 1us, L1 4us LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- LnkCap: Port #6, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 512ns, L1 16us LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 64us LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ Corresponding PCIe devices: # lspci -s 00:01.00 -nn 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) # lspci -s 00:1c.00 -nn 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5) # lspci -s 00:1c.05 -nn 00:1c.5 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 [8086:8c1a] (rev d5) # lspci -s 03:00.00 -nn 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 11) Current workaround: ASPM L0s L1 Enabled on each PCIe device can be created using manually using the correct setpci commands. This reliably enables ASPM L0s and L1 saving 25% in power consumption when measured at wall over at least 8 hours: # setpci -s 00:01.00 0xB0.B=0x3 # Intel Xeon E3-1200 PCIe controller [8086:0c01] # setpci -s 00:1c.05 0x50.B=0x43 # Intel 8 series PCIe root port #6 [8086:8c1a] # setpci -s 00:1c.00 0x50.B=0x43 # Intel 8 series PCIe root port #1 [8086:8c10] # setpci -s 03:00.00 0x80.B=0x43 # Realtek Gigabit Ethernet [10ec:8168] 2) The version of the package you are using === # uname -a Linux ubuntu14 3.17.0-999-generic #201409282205 SMP Mon Sep 29 02:06:39 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux 1) The release of Ubuntu === Description: Ubuntu 14.04.1 LTS Release: 14.04 Version signature is missing due to: # cat /proc/version_signature cat: /proc/version_signature: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1377596/+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 1398544] [NEW] Please enable CONFIG_PCIEASPM_DEBUG
Public bug reported: CONFIG_PCIEASPM_DEBUG (which is currently disabled for Ubuntu kernels) can be used to enable/disable ASPM settings per PCIE device. CONFIG_PCIEASPM (which is enabled for Ubuntu kernels) allows only to set global ASPM policy. BIOSes on more machines are buggy and lot of times do not configure ASPM for PCIE device property. CONFIG_PCIEASPM_DEBUG option allows users or testers to hotfix potential bugs in BIOS... That config option only add new sysfs files so it should not break anything else in kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1398544 Title: Please enable CONFIG_PCIEASPM_DEBUG Status in linux package in Ubuntu: New Bug description: CONFIG_PCIEASPM_DEBUG (which is currently disabled for Ubuntu kernels) can be used to enable/disable ASPM settings per PCIE device. CONFIG_PCIEASPM (which is enabled for Ubuntu kernels) allows only to set global ASPM policy. BIOSes on more machines are buggy and lot of times do not configure ASPM for PCIE device property. CONFIG_PCIEASPM_DEBUG option allows users or testers to hotfix potential bugs in BIOS... That config option only add new sysfs files so it should not break anything else in kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398544/+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 1398544] Re: Please enable CONFIG_PCIEASPM_DEBUG
@Brad Figg (brad-figg): Can I ask, which logs you need? And *why*? -- 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/1398544 Title: Please enable CONFIG_PCIEASPM_DEBUG Status in linux package in Ubuntu: Incomplete Bug description: CONFIG_PCIEASPM_DEBUG (which is currently disabled for Ubuntu kernels) can be used to enable/disable ASPM settings per PCIE device. CONFIG_PCIEASPM (which is enabled for Ubuntu kernels) allows only to set global ASPM policy. BIOSes on more machines are buggy and lot of times do not configure ASPM for PCIE device property. CONFIG_PCIEASPM_DEBUG option allows users or testers to hotfix potential bugs in BIOS... That config option only add new sysfs files so it should not break anything else in kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398544/+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 1199217] Re: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all
See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330832 -- 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/1199217 Title: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201201-10339 Dell Latitude E6530 [1] CID: 201307-13941 Dell Latitude E5440 [2] According to the information provided by Dell, these systems should have an accelerometer on the motherboard (Free-Fall sensor), but it cannot be detected at all (cannot be found in /proc/bus/input/devices) If using windows, it shows ACPI/SMO8810 in device manager If you run lspnp, you can see: 00:0c SMO8810 (unknown) [1] http://www.dell.com/downloads/global/products/latit/dell_latitude_e6530_spec_sheet.pdf [2] http://www.dell.com/us/business/p/latitude-e5440-laptop/pd This issue has also been verified with 12.04.4, see bug 1310879 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1635 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 49' Mixer name : 'IDT 92HD93BXX' Components : 'HDA:111d76df,10280535,00100203 HDA:14f12c06,14f1000f,0010' Controls : 20 Simple ctrls : 10 Date: Tue Jul 9 11:09:52 2013 HibernationDevice: RESUME=UUID=8ee31955-e727-4041-b013-ddde9c2533a6 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Latitude E6530 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=81b802b0-1e06-43e7-8c92-b241adf7768c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/19/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1199217/+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 1330832] Re: Backport dell-smo8800 driver from 3.16 kernel to Trusty
@Jesse Sung (wenchien): Userspace tool is in linux kernel tree (since 3.16 commit 3a57cc5f1935d824c36264e0fa888d7d6a9038c0) in file: Documentation/laptops/freefall.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1330832 Title: Backport dell-smo8800 driver from 3.16 kernel to Trusty Status in “linux” package in Ubuntu: In Progress Bug description: http://www.phoronix.com/scan.php?page=news_itempx=MTcxNzg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330832/+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 1330832] Re: Backport dell-smo8800 driver from 3.16 kernel to Trusty
Possible duplicate bug report? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1199217 -- 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/1330832 Title: Backport dell-smo8800 driver from 3.16 kernel to Trusty Status in “linux” package in Ubuntu: In Progress Bug description: http://www.phoronix.com/scan.php?page=news_itempx=MTcxNzg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330832/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Rob, see my comments #70. But Christopher already told us to not use this bug tracker, so I will not provide here more info anymore. Watch LKML for new patches. -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Fedora: Unknown Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
On Friday 17 October 2014 19:58:54 Christopher M. Penalver wrote: Unfortunately, this bug report is not scoped to you, or your problem. What?? Sorry I do not want to spam this bug tracker, but there are plenty people who have this and *same* problems on their Latitude Exx40 laptops. Or I missed something? So your hardware and problem may be tracked, could you please file a new report Did I understand correctly that you want that I should open new duplicate bug about existing problem which is already tracked in bug tracker? Why should I do that? And my last question, how do you want to fix this problem? do you have any idea what cause generating invalid packets? -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Anyway, to prevent random cursor movement and random mouse clicks you can force psmouse driver to reset ALPS device immediately after first invalid packet. It can be done with: $ echo 1 /sys/module/psmouse/drivers/serio:psmouse/serio1/resetafter -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Why is this bug still in state incomplete?? What is there missing? -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+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 1320022] Re: [Dell Latitude E6540] ALPS touchpad keeps having state reset
** Changed in: linux (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1320022 Title: [Dell Latitude E6540] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Confirmed Bug description: While using the 'eraser' pointer on my Dell Latitude E6540, the cursor will sometimes instantly jump around randomly and open a few windows. After this happens, it will become completely unresponsive for 10-20 seconds. Sometimes the keyboard will stop responding also. It seems like it is most likely to happen when I bump the trackpad with my palm when using the eraser pointer in the middle of the keyboard. Also - I have always had the trackpad disabled when this happens via the Dell hotkey (Fn-F5). Of course, it has never happened when the laptop is docked and I am using an external keyboard/mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jgibson4335 F pulseaudio /dev/snd/controlC1: jgibson4335 F pulseaudio CurrentDesktop: Unity Date: Thu May 15 17:45:24 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b89369d3-0c28-4203-b73e-5085341e1fe7 InstallationDate: Installed on 2014-03-12 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) MachineType: Dell Inc. Latitude E6540 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
@Allan Crooks (amcone): Do you mean acpi ec driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+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 1199217] Re: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all
@Joseph Salisbury (jsalisbury): Driver which I sent to LKML was only now pulled by Linus to his tree. So it will be in 3.16 kernel. If you do not backport it back to trusty kernel, than it will never hit older ( 3.16) 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/1199217 Title: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201201-10339 Dell Latitude E6530 [1] CID: 201307-13941 Dell Latitude E5440 [2] According to the information provided by Dell, these systems should have an accelerometer on the motherboard (Free-Fall sensor), but it cannot be detected at all (cannot be found in /proc/bus/input/devices) If using windows, it shows ACPI/SMO8810 in device manager If you run lspnp, you can see: 00:0c SMO8810 (unknown) [1] http://www.dell.com/downloads/global/products/latit/dell_latitude_e6530_spec_sheet.pdf [2] http://www.dell.com/us/business/p/latitude-e5440-laptop/pd This issue has also been verified with 12.04.4, see bug 1310879 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1635 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 49' Mixer name : 'IDT 92HD93BXX' Components : 'HDA:111d76df,10280535,00100203 HDA:14f12c06,14f1000f,0010' Controls : 20 Simple ctrls : 10 Date: Tue Jul 9 11:09:52 2013 HibernationDevice: RESUME=UUID=8ee31955-e727-4041-b013-ddde9c2533a6 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Latitude E6530 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=81b802b0-1e06-43e7-8c92-b241adf7768c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/19/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1199217/+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 1320022] Re: [Dell Latitude E6540] ALPS touchpad keeps having state reset
@Christopher M. Penalver (penalvch): Sorry, but I cannot. I already wrote it: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/comments/50 If can specify which information or logs you need I can provide you it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1320022 Title: [Dell Latitude E6540] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: While using the 'eraser' pointer on my Dell Latitude E6540, the cursor will sometimes instantly jump around randomly and open a few windows. After this happens, it will become completely unresponsive for 10-20 seconds. Sometimes the keyboard will stop responding also. It seems like it is most likely to happen when I bump the trackpad with my palm when using the eraser pointer in the middle of the keyboard. Also - I have always had the trackpad disabled when this happens via the Dell hotkey (Fn-F5). Of course, it has never happened when the laptop is docked and I am using an external keyboard/mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jgibson4335 F pulseaudio /dev/snd/controlC1: jgibson4335 F pulseaudio CurrentDesktop: Unity Date: Thu May 15 17:45:24 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b89369d3-0c28-4203-b73e-5085341e1fe7 InstallationDate: Installed on 2014-03-12 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) MachineType: Dell Inc. Latitude E6540 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022/+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 1320022] Re: ALPS touchpad keeps having state reset
Same problem on my Dell Latitude E6440. But it happends also when touchpad is enabled (via Fn+F5). Here is relevant part from dmesg log: [ 104.187214] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 104.188223] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 104.189283] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 104.190479] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 104.191525] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 [ 104.191528] psmouse serio1: issuing reconnect request -- 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/1320022 Title: ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Confirmed Bug description: While using the 'eraser' pointer on my Dell Latitude E6540, the cursor will sometimes instantly jump around randomly and open a few windows. After this happens, it will become completely unresponsive for 10-20 seconds. Sometimes the keyboard will stop responding also. It seems like it is most likely to happen when I bump the trackpad with my palm when using the eraser pointer in the middle of the keyboard. Also - I have always had the trackpad disabled when this happens via the Dell hotkey (Fn-F5). Of course, it has never happened when the laptop is docked and I am using an external keyboard/mouse. This issue seems identical to Bug #1258837. On that page @penalvch says to file new bug reports to capture the hardware, and to mention him :). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jgibson4335 F pulseaudio /dev/snd/controlC1: jgibson4335 F pulseaudio CurrentDesktop: Unity Date: Thu May 15 17:45:24 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b89369d3-0c28-4203-b73e-5085341e1fe7 InstallationDate: Installed on 2014-03-12 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) MachineType: Dell Inc. Latitude E6540 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022/+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 1320022] Re: ALPS touchpad keeps having state reset
When this error happends I see also this error in dmesg: [42282.319939] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 [42282.321094] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 [42282.322120] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 [42282.323162] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 [42282.324158] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 [42282.324162] psmouse serio1: issuing reconnect request In both cases it happen when I'm using trackpoint. -- 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/1320022 Title: ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Confirmed Bug description: While using the 'eraser' pointer on my Dell Latitude E6540, the cursor will sometimes instantly jump around randomly and open a few windows. After this happens, it will become completely unresponsive for 10-20 seconds. Sometimes the keyboard will stop responding also. It seems like it is most likely to happen when I bump the trackpad with my palm when using the eraser pointer in the middle of the keyboard. Also - I have always had the trackpad disabled when this happens via the Dell hotkey (Fn-F5). Of course, it has never happened when the laptop is docked and I am using an external keyboard/mouse. This issue seems identical to Bug #1258837. On that page @penalvch says to file new bug reports to capture the hardware, and to mention him :). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jgibson4335 F pulseaudio /dev/snd/controlC1: jgibson4335 F pulseaudio CurrentDesktop: Unity Date: Thu May 15 17:45:24 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b89369d3-0c28-4203-b73e-5085341e1fe7 InstallationDate: Installed on 2014-03-12 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) MachineType: Dell Inc. Latitude E6540 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022/+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 1320022] Re: [Dell Latitude E6540] ALPS touchpad keeps having state reset
Above my dmesg logs are from 3.15-rc5 kernel. So it is not fixed. ** 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/1320022 Title: [Dell Latitude E6540] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Confirmed Bug description: While using the 'eraser' pointer on my Dell Latitude E6540, the cursor will sometimes instantly jump around randomly and open a few windows. After this happens, it will become completely unresponsive for 10-20 seconds. Sometimes the keyboard will stop responding also. It seems like it is most likely to happen when I bump the trackpad with my palm when using the eraser pointer in the middle of the keyboard. Also - I have always had the trackpad disabled when this happens via the Dell hotkey (Fn-F5). Of course, it has never happened when the laptop is docked and I am using an external keyboard/mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jgibson4335 F pulseaudio /dev/snd/controlC1: jgibson4335 F pulseaudio CurrentDesktop: Unity Date: Thu May 15 17:45:24 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b89369d3-0c28-4203-b73e-5085341e1fe7 InstallationDate: Installed on 2014-03-12 (64 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) MachineType: Dell Inc. Latitude E6540 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022/+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 1199217] Re: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all
Hello, today I sent dell-smo8800 kernel driver (ACPI SMO8800 and SMO8810) to LKML: https://lkml.org/lkml/2014/5/3/33 -- 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/1199217 Title: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201201-10339 Dell Latitude E6530 [1] CID: 201307-13941 Dell Latitude E5440 [2] According to the information provided by Dell, these systems should have an accelerometer on the motherboard (Free-Fall sensor), but it cannot be detected at all (cannot be found in /proc/bus/input/devices) If using windows, it shows ACPI/SMO8810 in device manager If you run lspnp, you can see: 00:0c SMO8810 (unknown) [1] http://www.dell.com/downloads/global/products/latit/dell_latitude_e6530_spec_sheet.pdf [2] http://www.dell.com/us/business/p/latitude-e5440-laptop/pd This issue has also been verified with 12.04.4, see bug 1310879 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1635 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 49' Mixer name : 'IDT 92HD93BXX' Components : 'HDA:111d76df,10280535,00100203 HDA:14f12c06,14f1000f,0010' Controls : 20 Simple ctrls : 10 Date: Tue Jul 9 11:09:52 2013 HibernationDevice: RESUME=UUID=8ee31955-e727-4041-b013-ddde9c2533a6 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Latitude E6530 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=81b802b0-1e06-43e7-8c92-b241adf7768c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/19/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1199217/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
I have very same problem on my Dell Latitude E6440. Are there any news about this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: This is very similar to bug 1048258 - the mouse cursor keeps on jumping around, and these messages appear in the log when it hapepns: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+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 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Sorry, but I cannot use ubuntu-bug command, because of problem (see under). Please tell me what info do you need from me and I can provide it. But I really do not want to debug or hack that ubuntu-bug command... $ ubuntu-bug linux The program 'ubuntu-bug' is currently not installed. You can install it by typing: sudo apt-get install apport $ sudo apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: sbsigntool efibootmgr secureboot-db shim Use 'apt-get autoremove' to remove them. Suggested packages: apport-gtk apport-kde The following packages will be REMOVED: grub-common grub-efi-amd64-bin grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common shim-signed The following NEW packages will be installed: apport 0 upgraded, 1 newly installed, 7 to remove and 0 not upgraded. Need to get 148 kB of archives. After this operation, 14.4 MB disk space will be freed. Do you want to continue [Y/n]? n Abort. $ sudo aptitude install apport The following NEW packages will be installed: apport 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 148 kB of archives. After unpacking 999 kB will be used. The following packages have unmet dependencies: grub-common : Breaks: apport ( 2.1.1-0ubuntu1) but 2.0.1-0ubuntu17.6 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) grub-common 2) grub-efi-amd64-bin 3) grub-gfxpayload-lists 4) grub-pc 5) grub-pc-bin 6) grub2-common 7) shim-signed $ sudo aptitude install apport The following NEW packages will be installed: apport 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 148 kB of archives. After unpacking 999 kB will be used. The following packages have unmet dependencies: grub-common : Breaks: apport ( 2.1.1-0ubuntu1) but 2.0.1-0ubuntu17.6 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) grub-common 2) grub-efi-amd64-bin 3) grub-gfxpayload-lists 4) grub-pc 5) grub-pc-bin 6) grub2-common 7) shim-signedsudo aptitude install apport The following NEW packages will be installed: apport 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 148 kB of archives. After unpacking 999 kB will be used. The following packages have unmet dependencies: grub-common : Breaks: apport ( 2.1.1-0ubuntu1) but 2.0.1-0ubuntu17.6 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) grub-common 2) grub-efi-amd64-bin 3) grub-gfxpayload-lists 4) grub-pc 5) grub-pc-bin 6) grub2-common 7) shim-signed Accept this solution? [Y/n/q/?] q Abandoning all efforts to resolve these dependencies. Abort. -- 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: This is very similar to bug 1048258 - the mouse cursor keeps on jumping around, and these messages appear in the log when it hapepns: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a AlpsPS/2 ALPS DualPoint TouchPad. This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7
[Kernel-packages] [Bug 1290745] Re: [Radeon HD 8670A][1002:6660] Unable to load into live desktop after clicked Try Ubuntu on 12.04.4 bootable usb drive
After upgrading kernel to 3.14 (plus adding radeon.runpm=0 to kernel
cmdline) and upgrading xserver ati/radeon intel drivers from git
(version in trusty is not enough!), then *both* graphics cards (via dri
prime) on Dell Latitude E6440 in Ubuntu Precise 12.04.4 started working.
$ glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.0 Mesa 10.2.0-devel
OpenGL shading language version string: 1.30
OpenGL extensions:
$ xrandr --setprovideroutputsource 1 0
$ DRI_PRIME=1 glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD HAINAN
OpenGL version string: 2.1 Mesa 10.2.0-devel
OpenGL shading language version string: 1.30
OpenGL extensions:
You can find kernel 3.14 (works with precise) on:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/
And xserver drivers in my PPA (for precise):
https://launchpad.net/~pali/+archive/graphics-drivers
--
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/1290745
Title:
[Radeon HD 8670A][1002:6660] Unable to load into live desktop after
clicked Try Ubuntu on 12.04.4 bootable usb drive
Status in “linux” package in Ubuntu:
Confirmed
Status in “xorg-lts-saucy” package in Ubuntu:
Confirmed
Bug description:
Failed to load into live desktop after clicked the Try Ubuntu button on
welcome screen.
Expected:
Log into live desktop
Actual result:
Following prompted window, trying to run low-graphic mode still not able to
load the desktop, will fallback to console.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-15-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3516 F pulseaudio
/dev/snd/controlC1: ubuntu 3516 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xf7d34000 irq 48'
Mixer name : 'Intel Haswell HDMI'
Components : 'HDA:80862807,80860101,0010'
Controls : 21
Simple ctrls : 3
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7d3 irq 49'
Mixer name : 'Realtek ALC292'
Components : 'HDA:10ec0292,102805bd,0011'
Controls : 28
Simple ctrls : 13
CasperVersion: 1.315.1
DistroRelease: Ubuntu 12.04
LiveMediaBuild: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64
(20140204)
MachineType: Dell Inc. Latitude E6440
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 inteldrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/username.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
RelatedPackageVersions:
linux-restricted-modules-3.11.0-15-generic N/A
linux-backports-modules-3.11.0-15-generic N/A
linux-firmware 1.79.9
Tags: precise
Uname: Linux 3.11.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/03/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X23
dmi.board.name: 02P3T1
dmi.board.vendor: Dell Inc.
dmi.board.version: X03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrX23:bd07/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn02P3T1:rvrX03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
---
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CasperVersion: 1.315.1
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
DistUpgraded: Fresh install
DistroCodename: precise
DistroRelease: Ubuntu 12.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, even including gdb or git bisection work if
needed
GraphicsCard:
Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:05bd]
Subsystem: Dell Device [1028:05bd]
LiveMediaBuild: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64
(20140204)
MachineType: Dell Inc. Latitude E6440
MarkForUpload: True
Package: xorg 1:7.6+12ubuntu2
PackageArchitecture: amd64
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom
[Kernel-packages] [Bug 1023174] Re: ip -6 addr flush flushes much more than just the addresses
Tested on 3.12.0-5-generic kernel and problem is still there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1023174 Title: ip -6 addr flush flushes much more than just the addresses Status in “linux” package in Ubuntu: Triaged Bug description: root@testv6-tester:~# ls /proc/sys/net/ipv*/conf/ /proc/sys/net/ipv4/conf/: all default eth0 lo sit0 /proc/sys/net/ipv6/conf/: all default eth0 lo sit0 root@testv6-tester:~# ip addr flush dev eth0 root@testv6-tester:~# ls /proc/sys/net/ipv*/conf/ /proc/sys/net/ipv4/conf/: all default eth0 lo sit0 /proc/sys/net/ipv6/conf/: all default lo sit0 This results in no IPv6 connectivity on the interface and no obvious way to get it back to working condition other than destroying and recreating the interface (usually by rebooting). I reproduced this on the stable 12.04 kernel (3.2.0-26-generic) as well as 12.10 (3.5.0-3-generic). This is currently breaking ipv6 connectivity for some dual-stack setups in debian-installer though only for Ubuntu 12.10 (because the flush call was ipv4-specific in 12.04). I'll workaround the issue in d-i, but this bug should really be looked into. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1023174/+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
