[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
As I commented in http://askubuntu.com/a/775524/16395, some people reported success with the python script at https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae --- be warned, there is a bit of NSFW language there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
I was not really able to reproduce the crash neither on my 32 nor the 64 bit system... so I am quite unable to help. Has anyone explored the possibility of a corrupted/wrong wacom.ko in the distribution media? Romano -- 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/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] [NEW] Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
Public bug reported: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of the kernel panic log." https://bugs.launchpad.net/bugs/1310800/+attachment/4091720/+files/kernel-panic-on-tablet-plugin.jpg ** Summary changed: - Trusty Thar: automatic load of wacom.ko driver cause a "hard"kernel panic + Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux-meta” package in Ubuntu: New Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
I reported it here too: https://sourceforge.net/p/linuxwacom/bugs/238/ -- 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/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
I tried --- but the page that opens my browser, after I (correctly) log in, says "the information on this page is private" "Not allowed here" How can I upload the data manually? -- 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/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
Marked as confirmed because I am unable to user apport-collect, as commented above. I tried in all the way I can, but launchpad refuses to allow the data upload. I used apport_cli --save apport_report.txt linux and attached the resulting file. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment added: "result of apport_cli --save apport_report.txt linux" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+attachment/4091819/+files/apport_report.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
Tested with linux-image-3.15.0-031500rc2-generic_3.15.0-031500rc2.201404201435_i386.deb, still here. Will attach oops image. There are hints that the problem is known here: https://sourceforge.net/p/linuxwacom/bugs/238/#f170 In that case, I strongly advise adding "modprobe wacom" at boot in all the systems, to avoid crashes and potential data loss. BTW, I installed the aforementioned kernel with dpkg -i ... how do I go back to the stock one? Thanks! ** Attachment added: "crash with kernel 3.15.0-031500rc2-generic_3.15.0-031500rc2.20140420143" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+attachment/4094382/+files/IMG_20140423_094253.jpg ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
I can confirm that with linux- image-3.15.0-031500rc2-generic_3.15.0-031500rc2 the tablet works correctly if I manually load the driver *before* connecting it. Still, seems a dangerous bug to me. -- 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/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
Ok, compiling 0.21.0 against the upstream kernel (will test with the stock one) will too avoid the crash. I think that my expertise stops here... I do not know how to check for differences between the input-wacom official tree and the ubuntu tree. -- 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/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
Ok, (relatively) good news 1) still with kernel linux- image-3.15.0-031500rc2-generic_3.15.0-031500rc2 2) I recompiled the input-wacom-0.20.0 that worked for me in 13.10, from here: http://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom /input-wacom/input-wacom-0.20.0.tar.bz2/download 3) I substituted the module to the stock one, then rebooted; 4) the Oops is gone. So the problem must be in the changes from 0.20.0 and the current driver in the kernel, or in some modification of the ubuntu kernel team. In the first case the bug should be easy to catch, see the list of changes: https://sourceforge.net/p/linuxwacom/input- wacom/ci/2d38b3ce57d003cbef854674a4850e38f32f8c13/log/?path= Will test now with 0.21.0 to check if the bug is 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/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
I reinstalled the linux-image-extra-3.13.0-24-generic and the crash went away. I am really puzzled; I *did* try the newer kernel and had the crash. This morning has disappeared. Marking invalid for now, still looking at it. ** 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/1310800 Title: Trusty Thar, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Incomplete Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1268780] [NEW] Please backport the "libata.force disable" patch to 13.10 kernel
Public bug reported: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Please add the "libata.force disable" patch + Please backport the "libata.force disable" patch to 13.10 kernel -- 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/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: New Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948047/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] Re: Please backport the "libata.force disable" patch to 13.10 kernel
apport information ** Tags added: apport-collected ** Description changed: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. Thanks! + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: romano 2109 F pulseaudio + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=c4b932f3-b46b-4a90-ad7c-6e9f82aee6ac + InstallationDate: Installed on 2013-09-30 (105 days ago) + InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) + MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B + MarkForUpload: True + Package: linux (not installed) + ProcFB: + 0 inteldrmfb + 1 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=d3ddeeff-b3aa-4f29-acf4-4d63f87a38ac ro splash radeon.dpm=1 libata.force=2.00:disable vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-15.23-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.116 + Tags: saucy + Uname: Linux 3.11.0-15-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-10-18 (87 days ago) + UserGroups: adm lpadmin sambashare sudo + dmi.bios.date: 11/06/2012 + dmi.bios.vendor: Phoenix Technologies Ltd. + dmi.bios.version: 15FD + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 700Z3A/700Z4A/700Z5A/700Z5B + dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.board.version: FAB1 + dmi.chassis.asset.tag: Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.chassis.version: 0.1 + dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15FD:bd11/06/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3A/700Z4A/700Z5A/700Z5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn700Z3A/700Z4A/700Z5A/700Z5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: + dmi.product.name: 700Z3A/700Z4A/700Z5A/700Z5B + dmi.product.version: 0.1 + dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948045/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948048/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948046/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948050/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948058/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948057/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948059/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948051/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948056/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948049/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] Re: Please backport the "libata.force disable" patch to 13.10 kernel
Marking confirmed as suggested in the apport message. ** 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/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948060/+files/WifiSyslog.txt ** Description changed: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . - Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. + Could be backported to 3.11 kernel for 13.10? It applies and works + perfectly --- I tested it. + + More info available at: http://askubuntu.com/questions/352836/how-can-i + -tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not-even-co + Thanks! - --- - ApportVersion: 2.12.5-0ubuntu2.2 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: romano 2109 F pulseaudio - DistroRelease: Ubuntu 13.10 - HibernationDevice: RESUME=UUID=c4b932f3-b46b-4a90-ad7c-6e9f82aee6ac - InstallationDate: Installed on 2013-09-30 (105 days ago) - InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) - MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B - MarkForUpload: True - Package: linux (not installed) - ProcFB: - 0 inteldrmfb - 1 radeondrmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=d3ddeeff-b3aa-4f29-acf4-4d63f87a38ac ro splash radeon.dpm=1 libata.force=2.00:disable vt.handoff=7 - ProcVersionSignature: Ubuntu 3.11.0-15.23-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.116 - Tags: saucy - Uname: Linux 3.11.0-15-generic x86_64 - UpgradeStatus: Upgraded to saucy on 2013-10-18 (87 days ago) - UserGroups: adm lpadmin sambashare sudo - dmi.bios.date: 11/06/2012 - dmi.bios.vendor: Phoenix Technologies Ltd. - dmi.bios.version: 15FD - dmi.board.asset.tag: Base Board Asset Tag - dmi.board.name: 700Z3A/700Z4A/700Z5A/700Z5B - dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. - dmi.board.version: FAB1 - dmi.chassis.asset.tag: Asset Tag - dmi.chassis.type: 9 - dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. - dmi.chassis.version: 0.1 - dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15FD:bd11/06/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3A/700Z4A/700Z5A/700Z5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn700Z3A/700Z4A/700Z5A/700Z5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: - dmi.product.name: 700Z3A/700Z4A/700Z5A/700Z5B - dmi.product.version: 0.1 - dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -- 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/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948054/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948055/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948052/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1268780/+attachment/3948053/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] Re: Please backport the "libata.force disable" patch to 13.10 kernel
@henrix: thanks. Is there a repository where one can see the patches/commits for the next Ubuntu kernels? I tried to find it but I got lost. -- 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/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Triaged Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1268780] Re: Please backport the "libata.force disable" patch to 13.10 kernel
@henrix ok, found --- sorry for the noise. https://wiki.ubuntu.com/Kernel/Dev/ExtendedStable (to help future google-impaired searchers...) -- 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/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in “linux” package in Ubuntu: Triaged Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+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 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
@riban: As I commented, I can't reproduce it any more. Or maybe it's random (I had a crash with the tablet in once, when reconnected with the wireless option). There is a bug upstream: http://sourceforge.net/p/linuxwacom/bugs/238/ --- maybe you can chime in there and see if the developers can help. -- 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/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in “linux” package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1310800] Re: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic
I have a new incarnation of the bug, but I am not being able to capture a track, although is quite easy to trigger. Steps: 1 - load wacom.ko 2- connect the tablet **wirelessly** 3- wait until the tablet go to deep sleep (around 10 minutes) 4- switch the tablet on -> hard crash, the PC is completely dead. If you unplug and replug the USB radio dongle before switching the tablet on all is ok. -- 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/1310800 Title: 056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 from 13.10. I have a wacom cth-480 touch+pen tablet, which was not recognized on 13.10 (kernel 3.11). With the stock kernel from 14.04, I have an immediate kernel panic as soon as I plug in the tablet to the laptop. The system is a asus 1005PE (32 bit install), Xubuntu, up-to date: Linux asus-romano 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux The really strange thing is that if I manually load the driver with `sudo modprobe wacom` *before* pluggin the tablet in, then the tablet is recognized and works ok: SYS: Apr 21 15:15:47 asus-romano kernel: [ 265.664161] usbcore: registered new interface driver wacom SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.088161] usb 2-1: new full-speed USB device number 2 using uhci_hcd SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253626] usb 2-1: New USB device found, idVendor=056a, idProduct=0302 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253641] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253651] usb 2-1: Product: Intuos PTS SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.253659] usb 2-1: Manufacturer: Wacom Co.,Ltd. SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.257027] input: Wacom Intuos PT S Pen as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input14 SYS: Apr 21 15:15:52 asus-romano kernel: [ 270.260630] input: Wacom Intuos PT S Finger as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input15 SYS: Apr 21 15:15:52 asus-romano mtp-probe: checking bus 2, device 2: "/sys/devices/pci:00/:00:1d.0/usb2/2-1" SYS: Apr 21 15:15:52 asus-romano mtp-probe: bus: 2, device: 2 was not an MTP device A screenshot of the kernel panic is added. I can reproduce it at will. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800/+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 1268780] Re: Please backport the "libata.force disable" patch to 13.10 kernel
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- 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/1268780 Title: Please backport the "libata.force disable" patch to 13.10 kernel Status in linux package in Ubuntu: Fix Committed Bug description: Hi, I have a system with an on-board, soldered SSD which is failing, creating havoc in boot and suspend/resume process. It cannot be disabled in BIOS. Robin H. Johnson found a very nice and elegant solution, proposing the following patch: https://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?h=linux-3.12.y&id=83ceef0795fb85bb40bb90b300e3ebd8e8628454 which is now in stable 3.12 . Could be backported to 3.11 kernel for 13.10? It applies and works perfectly --- I tested it. More info available at: http://askubuntu.com/questions/352836/how- can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not- even-co Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
I had this problem with a Dell desktop; It was especially bad with the second monitor, which blanked out every time it lost focus. I can confirm that - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic after having created the directory /etc/preferences.d manually, and so upgrading to the yakkety kernel, fixed the issue. Can anyone please post the instruction to revert this and go back to normal Xenial kernel release when the bug is fixed there? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic *** Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
Updated to 16.04, have the same problem. The fix in comment#5 fixes it! Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Confirmed Status in pulseaudio source package in Vivid: Confirmed Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+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 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
Same thing with a Samsung 700Z3A/700Z4A/700Z5A/700Z5B. Fixed by upgrading to 4.4.8 kernel; followed instructions in comment #22 fixed the problem completely. -- 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/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Confirmed Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
@Vasya: seems a different problem. The flickering which this bug is referring to is application-independent, and visible in the full screen(s). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic ``` There was a typo in instructions (/etc/preferences.d should have been /etc/apt/preferences.d). As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix). I suggest you move /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety to /etc/apt/preferences.d/ and downgrade related packages: $ apt update $ apt install linux-headers-generic/xenial-updates linux-tools-generic/xenial-updates linux-image-generic/xenial-updates ``` *** Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
A new error mode is that now the BT device is not connected at all, even after doing the #5 thing, with the error: bluetoothd[984]: Unable to get Headset Voice gateway SDP record: Host is down I need to reboot the system, unpair and pair again the device, and then doing the dance of connecting with low quality, change to the internal audio, disconnecting the BT device, reconnecting again, switch to A2DP --- which now works. After 20 minutes. I think something happened in the last kernel update. Will start looking in Google for rain dances for the next time... ;-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1093217] Re: Ubuntu 12.04/12.10/13.04 10-20min boot delay (From 3.2.0.29->3.8.0.19) [Lenovo IdeaPad Z580]
Any new on this bug? I am thinking to buy this laptop --- just to know if the glitch is fixed or if there is some working workaround. Thanks. -- 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/1093217 Title: Ubuntu 12.04/12.10/13.04 10-20min boot delay (From 3.2.0.29->3.8.0.19) [Lenovo IdeaPad Z580] Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: On updating the kernel from 3.2.0.29 to any later version (3.2.0.30) and above, Ubuntu will not boot. I see a blank screen with a cursor but nothing happens after that. Trying to boot into recovery mode is not useful either. Booting into an older version of the kernel (3.2.0.29) is successful. I have seen this issue with all kernels after 3.2.0.29 till date : 3.2.0.31, 3.2.0.32, 3.2.0.33, 3.2.0.34, 3.2.0.35 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15.1 Architecture: i386, AMD64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abhishek 2104 F pulseaudio /dev/snd/pcmC0D0p: abhishek 2104 F...m pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf061 irq 46' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa4022,00100202 HDA:80862806,80860101,0010' Controls : 26 Simple ctrls : 12 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=4b3dd96d-8b88-4dbf-97d4-e2d78e5ad0fc InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: LENOVO IdeaPad Z580 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae root=UUID=a24e74a5-a245-4b37-b63c-96869939bf5c ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 RelatedPackageVersions: linux-restricted-modules-3.2.0-29-generic-pae N/A linux-backports-modules-3.2.0-29-generic-pae N/A linux-firmware1.79.1 StagingDrivers: rts5139 mei Tags: precise running-unity staging Uname: Linux 3.2.0-29-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo dmi.bios.date: 06/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5FCN34WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: Lenovo Z580 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr5FCN34WW:bd06/11/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvrLenovoZ580:cvnIntelCorporation:ct9:cvr0.1: dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 dmi.sys.vendor: LENOVO These logs were collected from 3.2.0.29 version which boots successfully To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1093217/+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 1093217] Re: Ubuntu 12.04/12.10/13.04 10-20min boot delay (From 3.2.0.29->3.8.0.19) [Lenovo IdeaPad Z580]
Thanks. Have you tested too with the acpi command line options in the boot parameters? I have a little Asus which need the acpi_os_name=Linux to work reliably... Nevertheless, thank for advising. Each new laptop is a PITA when you want to run Linux... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1093217 Title: Ubuntu 12.04/12.10/13.04 10-20min boot delay (From 3.2.0.29->3.8.0.19) [Lenovo IdeaPad Z580] Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: On updating the kernel from 3.2.0.29 to any later version (3.2.0.30) and above, Ubuntu will not boot. I see a blank screen with a cursor but nothing happens after that. Trying to boot into recovery mode is not useful either. Booting into an older version of the kernel (3.2.0.29) is successful. I have seen this issue with all kernels after 3.2.0.29 till date : 3.2.0.31, 3.2.0.32, 3.2.0.33, 3.2.0.34, 3.2.0.35 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15.1 Architecture: i386, AMD64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abhishek 2104 F pulseaudio /dev/snd/pcmC0D0p: abhishek 2104 F...m pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf061 irq 46' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa4022,00100202 HDA:80862806,80860101,0010' Controls : 26 Simple ctrls : 12 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=4b3dd96d-8b88-4dbf-97d4-e2d78e5ad0fc InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: LENOVO IdeaPad Z580 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae root=UUID=a24e74a5-a245-4b37-b63c-96869939bf5c ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 RelatedPackageVersions: linux-restricted-modules-3.2.0-29-generic-pae N/A linux-backports-modules-3.2.0-29-generic-pae N/A linux-firmware1.79.1 StagingDrivers: rts5139 mei Tags: precise running-unity staging Uname: Linux 3.2.0-29-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo dmi.bios.date: 06/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5FCN34WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: Lenovo Z580 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr5FCN34WW:bd06/11/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvrLenovoZ580:cvnIntelCorporation:ct9:cvr0.1: dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 dmi.sys.vendor: LENOVO These logs were collected from 3.2.0.29 version which boots successfully To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1093217/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
I have to confirm that it started to happen to me too, ii linux-firmware 20220329.git681281e4-0ubuntu3.23 all Firmware for Linux kernel drivers and [romano:~] % inxi -G Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel Device-2: AMD Seymour [Radeon HD 6400M/7400M Series] driver: radeon v: kernel Device-3: Silicon Motion WebCam SC-13HDL11431N type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: intel gpu: i915 resolution: 1600x900~60Hz OpenGL: renderer: Mesa Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 23.0.4-0ubuntu1~22.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: in
