[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
With amdgpu.dc=0 I get random mouse lag after moving my mouse quickly. The cursor will just stop moving. I turned amdgpu.dc=1 and it went away. -- 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/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
I am using one displayport 4k monitor, and one hdmi 1080p monitor. They keep waking each other up. When I used an adapter to make the 1080p monitor connect via a displayport > hdmi adapter, they both just output black when trying to sleep and cannot be woken up. They are still outputting black, they did not go to sleep. -- 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/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to:
[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
I am having the same issue on my rx570, I am on kernel 5.1.21 -- 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/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+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 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
whoops, I meant the linked kernel.org thread. :) -- 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/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+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 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
@James - Likely it had nothing to do with the firmware update. Have a look at the linked Ubuntu thread... many of us have been through exactly what you're going through now. Make a change, seems to help, 2 days later it's back. Please try some of the suggested solutions we've listed here: firm pressure on various parts of the lower case seems to resolve it for days at a time, for some people. As far as we can tell, there is no software or firmware fix possible for this issue. -- 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/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+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 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
Thank you for the pointer to debug mode in i2c_hid. Here's a log of it happening. I am not touching the touchpad at all. At the end I do a single, hard left click to end the episode. I don't know how to interpret the input (yet), but I will look it up. Hope this is helpful. Also FWIW I agree with @kai - this belongs in an upstream issue, really. It happens on my generic kernel. When we get an issue opened there, I'm happy to cross post as necessary. Nov 2 12:27:18 simba kernel: [196169.000701] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 92 01 00 Nov 2 12:27:18 simba kernel: [196169.007873] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 84 92 01 00 Nov 2 12:27:18 simba kernel: [196169.014979] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cb 92 01 00 Nov 2 12:27:18 simba kernel: [196169.022019] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 93 01 00 Nov 2 12:27:18 simba kernel: [196169.029205] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 59 93 01 00 Nov 2 12:27:18 simba kernel: [196169.036144] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 93 01 00 Nov 2 12:27:18 simba kernel: [196169.043416] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e7 93 01 00 Nov 2 12:27:18 simba kernel: [196169.050452] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2e 94 01 00 Nov 2 12:27:18 simba kernel: [196169.057508] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 76 94 01 00 Nov 2 12:27:18 simba kernel: [196169.064610] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bd 94 01 00 Nov 2 12:27:18 simba kernel: [196169.071651] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 95 01 00 Nov 2 12:27:18 simba kernel: [196169.078748] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4b 95 01 00 Nov 2 12:27:18 simba kernel: [196169.086108] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 93 95 01 00 Nov 2 12:27:18 simba kernel: [196169.093125] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 da 95 01 00 Nov 2 12:27:18 simba kernel: [196169.100075] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 21 96 01 00 Nov 2 12:27:18 simba kernel: [196169.107278] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 69 96 01 00 Nov 2 12:27:18 simba kernel: [196169.114471] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b1 96 01 00 Nov 2 12:27:18 simba kernel: [196169.121475] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f8 96 01 00 Nov 2 12:27:18 simba kernel: [196169.128628] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3f 97 01 00 Nov 2 12:27:18 simba kernel: [196169.135582] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 86 97 01 00 Nov 2 12:27:18 simba kernel: [196169.142774] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ce 97 01 00 Nov 2 12:27:18 simba kernel: [196169.149915] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 15 98 01 00 Nov 2 12:27:18 simba kernel: [196169.157067] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5c 98 01 00 Nov 2 12:27:18 simba kernel: [196169.164079] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a3 98 01 00 Nov 2 12:27:18 simba kernel: [196169.171073] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 eb 98 01 00 Nov 2 12:27:18 simba kernel: [196169.178389] i2c_hid i2c-DLL075B:01: input: 20 00 03 02 99 04 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 32
[Kernel-packages] [Bug 1326725] [NEW] PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
Public bug reported: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1/2-1.1.3.1:1.0/input/input22 Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:0268.000E: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:1d.0-1.1.3.1/input0 Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38 Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1 Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/1326725 Title: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic Status in “linux” package in Ubuntu: Incomplete Bug description: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony
[Kernel-packages] [Bug 1326725] Re: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
I am unable to run this command because I don't have access to the relevant machine now and I believe also there is enough information/logs in the bug report to reproduce and/or fix the bug. PS: It happens on several machines, with several different sixaxis controllers. I will try to change the status to Confirmed. ** 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/1326725 Title: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic Status in “linux” package in Ubuntu: Confirmed Bug description: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1/2-1.1.3.1:1.0/input/input22 Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:0268.000E: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:1d.0-1.1.3.1/input0 Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38 Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1 Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326725/+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 1326725] Re: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
I booted one of the machines on kernel 3.13.0-24-generic and the sixaxis device now works (no error message in dmesg and appears as /dev/input/js0). I have tried -26, -27 and -29 and the bug is in those but not in -24, as far as I can see. -- 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/1326725 Title: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic Status in “linux” package in Ubuntu: Confirmed Bug description: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1/2-1.1.3.1:1.0/input/input22 Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:0268.000E: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:1d.0-1.1.3.1/input0 Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38 Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1 Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326725/+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
