[Kernel-packages] [Bug 1390223] Re: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel
We encountered the same problem and noticed it only happened on 64 bit containers, while 32 bit containers seemed to work. We also tested upstream kernels 4.1 and 4.2.3, same result. -- 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/1390223 Title: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Fix Committed Bug description: I recently noticed a bunch of containers failing in a rather odd way when running postfix. The most visible example is when running mailq on an empty queue. Without apparmor (unconfined container) I see that the queue is empty, with apparmor, I get Permission denied. That's all running as root so the permission denied looks a tiny bit odd. Also, running the 3.13 kernel, I don't get any of that weirdness. My guess is that it has to do with the work that went into the 3.16 kernel for socket mediation. In theory only systems that run the utopic apparmor (which I DO NOT) should be seeing that kind of behavior, but it looks like some code path isn't checking things properly :) == strace in unconfined container == chdir("/var/spool/postfix") = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x7f8963a62c30}, {SIG_IGN, [], 0}, 8) = 0 getuid()= 0 socket(PF_LOCAL, SOCK_STREAM, 0)= 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR) = 0 connect(4, {sa_family=AF_LOCAL, sun_path="public/showq"}, 110) = 0 poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, revents=POLLIN|POLLHUP}]) read(4, "Mail queue is empty\n", 4096) = 20 poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, revents=POLLIN|POLLHUP}]) read(4, "", 4096) = 0 write(1, "Mail queue is empty\n", 20Mail queue is empty ) = 20 close(4)= 0 exit_group(0) = ? +++ exited with 0 +++ == strace in confined container == chdir("/var/spool/postfix") = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x7ffe62de4c30}, {SIG_IGN, [], 0}, 8) = 0 getuid()= 0 socket(PF_LOCAL, SOCK_STREAM, 0)= 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR) = 0 connect(4, {sa_family=AF_LOCAL, sun_path="public/showq"}, 110) = 0 poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, revents=POLLIN|POLLHUP}]) read(4, 0x7ffe65b35c00, 4096) = -1 EACCES (Permission denied) close(4)= 0 write(2, "postqueue: warning: close: Permi"..., 45postqueue: warning: close: Permission denied ) = 45 sendto(3, "<20>Nov 6 20:40:42 postfix/post"..., 78, MSG_NOSIGNAL, NULL, 0) = 78 exit_group(0) = ? Kernel is a slightly outdated version of the kernel from the kernel team PPA: Linux shell01 3.16.0-23-generic #31-Ubuntu SMP Thu Oct 23 20:13:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux If you think the latest build will improve this, I can test it, but seeing how this is a production server, I can't just flip kernels every 5 minutes (I'm running 3.16 to avoid a nasty btrfs bug on 3.13). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390223/+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 1490440] Re: cursor jumps around randomly
It seems more like a hardware fault than a Ubuntu bug since I tried several distros and it always occurs. Even in Windows, cursor behaves not normal (gets stuck, no jumping but still faulty behaviour). I sent the machine for repair. -- 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/1490440 Title: cursor jumps around randomly Status in linux package in Ubuntu: Incomplete Bug description: after a while of usage the cursor might start to jump around randomly very quickly and also begin to click sometimes randomly. it cannot be stopped permanently. it will eventually get stuck in a place and will not respond to any input any longer until reboot. once this random movements started, reboot will only fix it for a short amount of time. switching from advanced touchpad to basic will not eliminate this bug. Acer Travelmate B115-M ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Mon Aug 31 10:43:27 2015 InstallationDate: Installed on 2015-08-30 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490440/+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 1390223] Re: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel
Ah those "upstream" kernels weren't pure... Just tested manually compiled kernel master branch and tag 4.2, no issues. Copied over a packaged one: problem reappears. It's not a container problem though. Running this on a host has the same effect: # aa-exec -p $pick_your_favorite_profile -- socat UNIX:/var/spool/postfix/public/showq - also gets an EPERM. Also not 32/64 bit dependent, however we do have some containers where it always works, and some where it always fails, and that was their only obvious distinction, which now seems unrelated. -- 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/1390223 Title: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Fix Committed Bug description: I recently noticed a bunch of containers failing in a rather odd way when running postfix. The most visible example is when running mailq on an empty queue. Without apparmor (unconfined container) I see that the queue is empty, with apparmor, I get Permission denied. That's all running as root so the permission denied looks a tiny bit odd. Also, running the 3.13 kernel, I don't get any of that weirdness. My guess is that it has to do with the work that went into the 3.16 kernel for socket mediation. In theory only systems that run the utopic apparmor (which I DO NOT) should be seeing that kind of behavior, but it looks like some code path isn't checking things properly :) == strace in unconfined container == chdir("/var/spool/postfix") = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x7f8963a62c30}, {SIG_IGN, [], 0}, 8) = 0 getuid()= 0 socket(PF_LOCAL, SOCK_STREAM, 0)= 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR) = 0 connect(4, {sa_family=AF_LOCAL, sun_path="public/showq"}, 110) = 0 poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, revents=POLLIN|POLLHUP}]) read(4, "Mail queue is empty\n", 4096) = 20 poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, revents=POLLIN|POLLHUP}]) read(4, "", 4096) = 0 write(1, "Mail queue is empty\n", 20Mail queue is empty ) = 20 close(4)= 0 exit_group(0) = ? +++ exited with 0 +++ == strace in confined container == chdir("/var/spool/postfix") = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 0x7ffe62de4c30}, {SIG_IGN, [], 0}, 8) = 0 getuid()= 0 socket(PF_LOCAL, SOCK_STREAM, 0)= 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR) = 0 connect(4, {sa_family=AF_LOCAL, sun_path="public/showq"}, 110) = 0 poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, revents=POLLIN|POLLHUP}]) read(4, 0x7ffe65b35c00, 4096) = -1 EACCES (Permission denied) close(4)= 0 write(2, "postqueue: warning: close: Permi"..., 45postqueue: warning: close: Permission denied ) = 45 sendto(3, "<20>Nov 6 20:40:42 postfix/post"..., 78, MSG_NOSIGNAL, NULL, 0) = 78 exit_group(0) = ? Kernel is a slightly outdated version of the kernel from the kernel team PPA: Linux shell01 3.16.0-23-generic #31-Ubuntu SMP Thu Oct 23 20:13:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux If you think the latest build will improve this, I can test it, but seeing how this is a production server, I can't just flip kernels every 5 minutes (I'm running 3.16 to avoid a nasty btrfs bug on 3.13). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390223/+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 1607530] [NEW] linux-firmware-nonfree deleted from xenial. Old .fw crashes kernel
Public bug reported: My 'DViCO FusionHDTV5 USB Gold' tuner used to work fine under 14.04 using dvb-usb-bluebird-01.fw which was part of linux-firmware-nonfree. That package no longer exists in 16.04 but dvb-usb is still looking for dvb-usb-bluebird-01.fw: [1099531.611529] dvb-usb: found a 'DViCO FusionHDTV5 USB Gold' in cold state, will try to load a firmware [1099531.611577] usb 1-2: Direct firmware load for dvb-usb-bluebird-01.fw failed with error -2 [1099531.611581] dvb-usb: did not find the firmware file. (dvb-usb-bluebird-01.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2) [1099531.611587] dvb_usb_cxusb: probe of 1-2:1.0 failed with error -22 [1099531.611670] usbcore: registered new interface driver dvb_usb_cxusb I tried adding dvb-usb-bluebird-01.fw to /lib/firmware but that crashes the kernel as soon as the usb device is detected. Have not debugged this further but the system stops listening to mouse, keyboard, ssh attempts and anything else short of the power button. No messages in the log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 28 13:29:34 2016 Dependencies: InstallationDate: Installed on 2016-07-10 (18 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1607530 Title: linux-firmware-nonfree deleted from xenial. Old .fw crashes kernel Status in linux-firmware package in Ubuntu: New Bug description: My 'DViCO FusionHDTV5 USB Gold' tuner used to work fine under 14.04 using dvb-usb-bluebird-01.fw which was part of linux-firmware-nonfree. That package no longer exists in 16.04 but dvb-usb is still looking for dvb-usb-bluebird-01.fw: [1099531.611529] dvb-usb: found a 'DViCO FusionHDTV5 USB Gold' in cold state, will try to load a firmware [1099531.611577] usb 1-2: Direct firmware load for dvb-usb-bluebird-01.fw failed with error -2 [1099531.611581] dvb-usb: did not find the firmware file. (dvb-usb-bluebird-01.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2) [1099531.611587] dvb_usb_cxusb: probe of 1-2:1.0 failed with error -22 [1099531.611670] usbcore: registered new interface driver dvb_usb_cxusb I tried adding dvb-usb-bluebird-01.fw to /lib/firmware but that crashes the kernel as soon as the usb device is detected. Have not debugged this further but the system stops listening to mouse, keyboard, ssh attempts and anything else short of the power button. No messages in the log. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 28 13:29:34 2016 Dependencies: InstallationDate: Installed on 2016-07-10 (18 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1607530/+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 1779678] [NEW] deadlocks in copy_net_ns
Public bug reported: Various users have reported hangs happening during network namespace creation. This mostly manifests in issues while starting lxc containers, and, when triggered, can be seen clearly by running `unshare -n` which will simply hang forever. This has been happening randomly for quite a few kernel versions now. This has been confirmed on 4.13 from Proxmox users (which uses an ubuntu based kernel with few patches), and various other older and newer kernels as found by reports in the links [1][2][3] below. [2] in particular contains the same symptoms across multiple distributions and kernel versions. The posted stack traces do include copy_net_ns() on top as well. There are races in the network code causing copy_net_ns() to hang (seemingly permanently). Some of these are caused by specific types of interfaces being in use and have been addressed (various refcount leak fixes), but that's not all of them. We've received yet another report with the current version 4.15.0-22.24 / 4.15.17 with the same symptoms. Processes in this state always have copy_net_ns() on top of their /proc/$pid/stack looking like: ~/ cat /proc/5228/stack [<0>] copy_net_ns+0xab/0x220 [<0>] create_new_namespaces+0x11b/0x1e0 [<0>] unshare_nsproxy_namespaces+0x5a/0xb0 [<0>] SyS_unshare+0x201/0x3a0 [<0>] do_syscall_64+0x73/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x or cat /proc/23900/stack [<0>] copy_net_ns+0xab/0x220 [<0>] create_new_namespaces+0x11b/0x1e0 [<0>] copy_namespaces+0x6d/0xa0 [<0>] copy_process.part.35+0x941/0x1ab0 [<0>] _do_fork+0xdf/0x3f0 [<0>] SyS_clone+0x19/0x20 [<0>] do_syscall_64+0x73/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x This randomly affects users of network namespaces (lxc, lxd, docker, PVE as well as service units using systemd's PrivateNetwork option and various others). Upstream there have been a lot of changes to the involved locking mechanism since 4.16 and we should try to backport these patches. This includes most of Kirill Tkhai's network patches and some others. I've been going through the following ones generated via various `git log` calls on net/, drivers/net/ (initially limiting to the ones with `--author='Kirill Tkhai'` as a starting point.) There's also a long list of patches we don't need to pick as they're implicitly reverted by 1 later change, provided we include all the necessary patches. They seem to be nice to review given that they're a progressive change first introducing a flag about async-safety, then going through all the affected areas with commit messages detailing why/if/how they're safe, followed finally when they're all the same by a commit to remove the flag again. Orderd newest to oldest U .. already in the ubuntu kernel, included due to its order when viewing related patches P .. should be cherry-picked Q .. (just 1) included for completion, will conflict in case backports of the patches adding NETDEV_{C,S}VLAN_FILTER_PUSH_INFO, which is probably good as a reminder for verification? - .. if all other patches are applied, they're made obsolete by 2f635ceeb22b ("net: Drop pernet_operations::async") Q 3f5ecd8a90dd net: Fix coccinelle warning P eb7f54b90bd8 kcm: Fix use-after-free caused by clonned sockets P 554873e51711 net: Do not take net_rwsem in __rtnl_link_unregister() P fc1dd36992bb net: Remove net_rwsem from {, un}register_netdevice_notifier() P 328fbe747ad4 net: Close race between {un, }register_netdevice_notifier() and setup_net()/cleanup_net() P 9e2f6c5d78db netfilter: Rework xt_TEE netdevice notifier P e9a441b6e729 xfrm: Register xfrm_dev_notifier in appropriate place P 152f253152cc net: Remove rtnl_lock() in nf_ct_iterate_destroy() P ec9c780925c5 ovs: Remove rtnl_lock() from ovs_exit_net() P 350311aab4c0 security: Remove rtnl_lock() in selinux_xfrm_notify_policyload() P 10256debb918 net: Don't take rtnl_lock() in wireless_nlevent_flush() P f0b07bb151b0 net: Introduce net_rwsem to protect net_namespace_list d 8518e9bb98b6 net: Add more comments P 4420bf21fb6c net: Rename net_sem to pernet_ops_rwsem P 2f635ceeb22b net: Drop pernet_operations::async P 094374e5e173 net: Reflect all pernet_operations are converted - 67441c2472dd net: Convert nfsd_net_ops - dbf7bb443726 net: Convert nfs4blocklayout_net_ops - 436de500948e net: Convert nfs4_dns_resolver_ops - 5e804a6077dc net: Convert sunrpc_net_ops - 855aeba34047 net: Convert rpcsec_gss_net_ops P 070f2d7e264a net: Drop NETDEV_UNREGISTER_FINAL P 3e0c2dbfea28 infiniband: Replace usnic_ib_netdev_event_to_string() with netdev_cmd_to_name() P ede2762d93ff net: Make NETDEV_XXX commands enum { } - b2864fbdc5ab net: Convert rxrpc_net_ops - fc18999ed2a2 net: Convert udp_sysctl_ops P d9ff3049739e net: Replace ip_ra_lock with per-net mutex P 5796ef75ec7b net: Make ip_ra_chain per struct net P 128aaa98ad14 net: Revert "ipv4: fix a deadlock in ip_ra_control" P 0526947f9dd0 net: Move IP_ROUTER_ALERT out of lock_sock(sk) P 76d3e153d0d1 net:
[Kernel-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
I suppose that would that be an ubuntu-specific patch for apparmor userspace? I'm assuming the ABI tells userspace which features are supported, unless this particular feature can be tested for some other way? Would the patched userspace know not to use these features under this ABI in a future 4.18+ kernel or a non-Ubuntu pre-4.17 kernel? I'm just a bit worried about the upgrade path here. -- 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/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780227/+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 1964827] Re: zfs-linux upstream at 2.1.3, jammy has 2.1.2
Yes, would be really important to still get the fixes in zfs-2.1.3 into jammy. I'd love to see that too! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.3, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+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 1973610] [NEW] Bluetooth will not stay on or connect to devices when on
Public bug reported: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in bluez package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.v
[Kernel-packages] [Bug 1778333] [NEW] package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: package linux-image-extra-4.4.0-124-generic is not ready for configuration ca
Public bug reported: ...some time ago I installed openbox and gnome in addition to unity. The reason was a kind of instability with the latter one. Could it be that this could possibly lead to the problemsof today ? Should I delete the mentioned gui packages ? Best regards Wolfgang ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Jun 23 12:55:33 2018 ErrorMessage: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half-installed') IwConfig: lono wireless extensions. enp0s10 no wireless extensions. enp0s18 no wireless extensions. MachineType: MEDIONPC MS-7255 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=3ac16d19-cdac-4494-a966-7b1336652ab5 ro drm.debug=0xe vesafb.invalid=1 plymouth:debug splash quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7255 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/24/2008:svnMEDIONPC:pnMS-7255:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7255:rvr:cvnMEDIONPC:ct3:cvr: dmi.product.name: MS-7255 dmi.sys.vendor: MEDIONPC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1778333/+attachment/5155794/+files/lspci-vnvn.log -- 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/1778333 Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: ...some time ago I installed openbox and gnome in addition to unity. The reason was a kind of instability with the latter one. Could it be that this could possibly lead to the problemsof today ? Should I delete the mentioned gui packages ? Best regards Wolfgang ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Jun 23 12:55:33 2018 ErrorMessage: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half-installed') IwConfig: lono wireless extensions. enp0s10 no wireless extensions. enp0s18 no wireless extensions. MachineType: MEDIONPC MS-7255 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=3ac16d19-cdac-4494-a966-7b1336652ab5 ro drm.debug=0xe vesafb.invalid=1 plymouth:debug splash quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7255 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr
[Kernel-packages] [Bug 1778333] Re: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: package linux-image-extra-4.4.0-124-generic is not ready for configuration cann
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778333/+attachment/5155813/+files/version.log -- 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/1778333 Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: ...some time ago I installed openbox and gnome in addition to unity. The reason was a kind of instability with the latter one. Could it be that this could possibly lead to the problemsof today ? Should I delete the mentioned gui packages ? Best regards Wolfgang ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Jun 23 12:55:33 2018 ErrorMessage: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half-installed') IwConfig: lono wireless extensions. enp0s10 no wireless extensions. enp0s18 no wireless extensions. MachineType: MEDIONPC MS-7255 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=3ac16d19-cdac-4494-a966-7b1336652ab5 ro drm.debug=0xe vesafb.invalid=1 plymouth:debug splash quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-124-generic 4.4.0-124.148 failed to install/upgrade: package linux-image-extra-4.4.0-124-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7255 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/24/2008:svnMEDIONPC:pnMS-7255:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7255:rvr:cvnMEDIONPC:ct3:cvr: dmi.product.name: MS-7255 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778333/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
Can confirm that the patch seems to work on 4.15. No "denied" "file_lock" log-spam when starting ArchLinux containers anymore, and they seem to be behaving as expected again. -- 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/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in apparmor source package in Xenial: Invalid Status in linux source package in Xenial: Triaged Status in apparmor source package in Bionic: Invalid Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 2009785] Re: [RTL8821CE] WLAN functionality cannot be controlled any more
The suggested incantation worked: WLAN operable again. - Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009785 Title: [RTL8821CE] WLAN functionality cannot be controlled any more Status in linux-hwe-5.19 package in Ubuntu: New Bug description: After the latest upgrade and a reboot, the WLAN connectivity features have disappeared from the menu on the upper right hand side menu, and the system does not connect to the local WLAN at my home; in short: WLAN DOES NOT WORK ANY MORE (Luckily, Ethernet connectivity is still available so I can send this using USB tethering.) New, however is Bluetooth connectivity control. Turning this off, turns on airplane mode; turning airplane mode off returns the Bluetooth control menu entry. $ lspci -nnk -d::0280 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] DeviceName: WLAN Subsystem: Hewlett-Packard Company RTL8821CE 802.11ac PCIe Wireless Network Adapter [103c:831a] Kernel modules: rtw88_8821ce THIS DOES NOT REPORT A KERNEL DRIVER IN USE. Thank you Wolfgang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 9 05:12:28 2023 DistUpgraded: 2022-11-14 12:08:39,894 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-67-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:86c1] InstallationDate: Installed on 2020-12-19 (809 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP 250 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=ac8de2b3-079a-406a-af37-4891044b3642 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-11-14 (114 days ago) dmi.bios.date: 07/31/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86C1 dmi.board.vendor: HP dmi.board.version: 89.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 89.35 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/31/2020:br15.33:efr89.35:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn86C1:rvr89.35:cvnHP:ct10:cvrChassisVersion:sku1B7K9ES#ABD: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 1B7K9ES#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009785/+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 1908992] Re: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1908992 Title: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Pointstick and its left right buttons don't work on EliteBook 859 G7. [Fix] Use the MT_CLS_WIN_8_FORCE_MULTI_INPUT so the usage collection for pointsitck and touchpad won't merge together. [Test] With the patch applied, pointstick and its left and right buttons start to work. [Where problems could occur] The quirk limits to one specific touchpad/pointstick combo, so regression would be highly unlikely. == Original Bug Report == $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Mouse id=11 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Touchpad id=12 [slave pointer (2)] The touchpad is working fine, but the pointing stick/trackpoint does not work at all. No input is registered with xinput and libinput device tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Dec 22 10:13:13 2020 DistUpgraded: 2020-12-22 07:48:08,643 DEBUG /openCache(), new cache size 70584 DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2020-12-11 (10 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteBook 850 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgxubuntu-root ro quiet splash psmouse.proto=bare SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to focal on 2020-12-22 (0 days ago) dmi.bios.date: 08/24/2020 dmi.bios.release: 1.7 dmi.bios.vendor: HP dmi.bios.version: S73 Ver. 01.01.07 dmi.board.name: 8724 dmi.board.vendor: HP dmi.board.version: KBC Version 06.34.00 dmi.chassis.asset.tag: 5CG0471SRC dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.52 dmi.modalias: dmi:bvnHP:bvrS73Ver.01.01.07:bd08/24/2020:br1.7:efr6.52:svnHP:pnHPEliteBook850G7NotebookPC:pvr:rvnHP:rn8724:rvrKBCVersion06.34.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G7 Notebook PC dmi.product.sku: 1J6F3EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908992/+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 1908992] Re: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all
Since linux-oem-5.10 - 5.10.0-1010.11 doesn't seem to have hit the mirrors yet, I've installed it from the kernel PPA. https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa Works for me, thank you! -- 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/1908992 Title: SYNA30B4:00 06CB:CE09 Mouse on HP EliteBook 850 G7 not working at all Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Pointstick and its left right buttons don't work on EliteBook 859 G7. [Fix] Use the MT_CLS_WIN_8_FORCE_MULTI_INPUT so the usage collection for pointsitck and touchpad won't merge together. [Test] With the patch applied, pointstick and its left and right buttons start to work. [Where problems could occur] The quirk limits to one specific touchpad/pointstick combo, so regression would be highly unlikely. == Original Bug Report == $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Mouse id=11 [slave pointer (2)] ⎜ ↳ SYNA30B4:00 06CB:CE09 Touchpad id=12 [slave pointer (2)] The touchpad is working fine, but the pointing stick/trackpoint does not work at all. No input is registered with xinput and libinput device tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Dec 22 10:13:13 2020 DistUpgraded: 2020-12-22 07:48:08,643 DEBUG /openCache(), new cache size 70584 DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2020-12-11 (10 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteBook 850 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/vgxubuntu-root ro quiet splash psmouse.proto=bare SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to focal on 2020-12-22 (0 days ago) dmi.bios.date: 08/24/2020 dmi.bios.release: 1.7 dmi.bios.vendor: HP dmi.bios.version: S73 Ver. 01.01.07 dmi.board.name: 8724 dmi.board.vendor: HP dmi.board.version: KBC Version 06.34.00 dmi.chassis.asset.tag: 5CG0471SRC dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.52 dmi.modalias: dmi:bvnHP:bvrS73Ver.01.01.07:bd08/24/2020:br1.7:efr6.52:svnHP:pnHPEliteBook850G7NotebookPC:pvr:rvnHP:rn8724:rvrKBCVersion06.34.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G7 Notebook PC dmi.product.sku: 1J6F3EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908992/+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 1562076] Re: Ubuntu freezes a few seconds after plugin a screen
To me it freezes even if I boot with the cable already plugged in. In this case, it will freeze when the login screen is displayed, sometimes I'm not even able to begin to type my password. -- 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/1562076 Title: Ubuntu freezes a few seconds after plugin a screen Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm running the latest beta of Ubuntu 16.04 Xenial on an ASUS UX303LA (Intel i5 6200U, Intel HD 520) and each time I plug a screen, using either HDMI or Mini DisplayPort, my laptop freezes after a few seconds. Alt + Function keys doesn't work, sound stops and I'm forced to shutdown the computer by long-pressing its Power button. I attached syslog, kern.log and Xorg.0.log for further information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 1632 F pulseaudio CurrentDesktop: GNOME Date: Fri Mar 25 17:34:54 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2acdb9a2-2923-4550-9019-32e79d136c4d InstallationDate: Installed on 2016-02-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303UA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=de727ab1-db17-453b-a371-4a143f37dcad ro noprompt persistent 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: Upgraded to xenial on 2016-02-25 (28 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303UA.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303UA.202:bd08/27/2015:svnASUSTeKCOMPUTERINC.:pnUX303UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562076/+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 1525878] Re: Wacom serial pen stops working in kernel 4.2.0-19
apport information ** Tags added: apport-collected ** Description changed: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: wolfgang 2040 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 15.10 + HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 + InstallationDate: Installed on 2015-10-22 (56 days ago) + InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + MachineType: FUJITSU SIEMENS LIFEBOOK T5010 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 + RelatedPackageVersions: + linux-restricted-modules-4.2.0-21-generic N/A + linux-backports-modules-4.2.0-21-generic N/A + linux-firmware1.149.3 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: wily + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 4.2.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 08/20/2009 + dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. + dmi.bios.version: Version 3.05 + dmi.board.name: FJNB1EA + dmi.board.vendor: FUJITSU + dmi.board.version: CP378200-01 + dmi.chassis.type: 10 + dmi.chassis.vendor: FUJITSU SIEMENS + dmi.chassis.version: T50__ + dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: + dmi.product.name: LIFEBOOK T5010 + dmi.sys.vendor: FUJITSU SIEMENS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536761/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi
[Kernel-packages] [Bug 1525878] Re: Wacom serial pen stops working in kernel 4.2.0-19
It's all working again. I guess some recent update fixed it already, even for the 4.2.0-19 kernel. I still appended the debugging information, just in case this or a similar error pops up again. -- 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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536772/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536776/+files/WifiSyslog.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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536773/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536767/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536775/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536770/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536764/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536766/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] PccardctlIdent.txt
apport information ** Attachment added: "PccardctlIdent.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536768/+files/PccardctlIdent.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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536763/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536774/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536771/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] PccardctlStatus.txt
apport information ** Attachment added: "PccardctlStatus.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536769/+files/PccardctlStatus.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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536765/+files/JournalErrors.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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1525878] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1525878/+attachment/4536762/+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/1525878 Title: Wacom serial pen stops working in kernel 4.2.0-19 Status in linux package in Ubuntu: Incomplete Bug description: The pen (on a Fujitsu T5010) completely stopped working when using Kernel 4.2.0-19. When booting 4.2.0-18, it works again, so I suspect it's somehow kernel related. When booting 4.2.0-19, xsetwacom --list devices is completely empty. When booting 4.2.0-18, see output below. xsetwacom --list devices Serial Wacom Tablet FUJ02e5 stylusid: 17 type: STYLUS Serial Wacom Tablet FUJ02e5 eraserid: 18 type: ERASER dmesg | grep -i wacom [9.109484] input: Wacom Serial Penabled 1FG Touchscreen as /devices/pnp0/00:06/tty/ttyS4/serio5/input/input17 Please let me know whether I can provide further information. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolfgang 2040 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=f511f0ce-d11b-4d49-adf4-dfd90bb5cca8 InstallationDate: Installed on 2015-10-22 (56 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: FUJITSU SIEMENS LIFEBOOK T5010 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=e1b708e6-a55f-4db1-bdec-020cae371625 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/20/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 3.05 dmi.board.name: FJNB1EA dmi.board.vendor: FUJITSU dmi.board.version: CP378200-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: T50__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion3.05:bd08/20/2009:svnFUJITSUSIEMENS:pnLIFEBOOKT5010:pvr:rvnFUJITSU:rnFJNB1EA:rvrCP378200-01:cvnFUJITSUSIEMENS:ct10:cvrT50__: dmi.product.name: LIFEBOOK T5010 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525878/+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 1298802] Re: 2357:0100 [Gigabyte 965P-DS3] USB Wifi TP-Link WN8200ND cannot associate to access points
I have the same issue with Bus 001 Device 002: ID 0b05:17ab ASUSTek Computer, Inc. USB-N13 802.11n Network Adapter (rev. B1) [Realtek RTL8192CU] -- 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/1298802 Title: 2357:0100 [Gigabyte 965P-DS3] USB Wifi TP-Link WN8200ND cannot associate to access points Status in “linux” package in Ubuntu: Triaged Bug description: The Usb Wifi dongle TP-Link WN8200ND (rtl8192cu driver) does not connect with a default 14.04 trusty updated one or two days ago from the internet. Partial WORKAROUND: If I add the dkms module that replaces the builtin driver (see instructions and source code in [1]) then I can connect to some access points (like my cellphone tethering access point) but not to other access points where my laptop connects without any problems. [1] https://github.com/pvaret/rtl8192cu-fixes Upstream URL: http://marc.info/?l=linux-wireless&m=139628227208870&w=2 --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ps 1652 F pulseaudio /dev/snd/controlC2: ps 1652 F pulseaudio /dev/snd/controlC0: ps 1652 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=503046a7-aabc-47e4-8821-4d73a4a06de1 InstallationDate: Installed on 2014-03-23 (5 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140321) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=7f56cb3c-a7fe-4445-85d6-321baab07d41 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/12/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: 965P-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd01/12/2007:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965P-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1298802/+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 1298802] Re: 2357:0100 [Gigabyte 965P-DS3] USB Wifi TP-Link WN8200ND cannot associate to access points
Not sure why opening a duplicate of this bug would make sense. I have the same chipset and exactly the same issues as the reporter. If you still want me to open a new bug, I can ofc do that. -- 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/1298802 Title: 2357:0100 [Gigabyte 965P-DS3] USB Wifi TP-Link WN8200ND cannot associate to access points Status in “linux” package in Ubuntu: Triaged Bug description: The Usb Wifi dongle TP-Link WN8200ND (rtl8192cu driver) does not connect with a default 14.04 trusty updated one or two days ago from the internet. Partial WORKAROUND: If I add the dkms module that replaces the builtin driver (see instructions and source code in [1]) then I can connect to some access points (like my cellphone tethering access point) but not to other access points where my laptop connects without any problems. [1] https://github.com/pvaret/rtl8192cu-fixes Upstream URL: http://marc.info/?l=linux-wireless&m=139628227208870&w=2 --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ps 1652 F pulseaudio /dev/snd/controlC2: ps 1652 F pulseaudio /dev/snd/controlC0: ps 1652 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=503046a7-aabc-47e4-8821-4d73a4a06de1 InstallationDate: Installed on 2014-03-23 (5 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140321) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=7f56cb3c-a7fe-4445-85d6-321baab07d41 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/12/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: 965P-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd01/12/2007:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965P-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1298802/+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 1308474] [NEW] CPU-intensive processes killed by OS
Public bug reported: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0 000 S 3 0.0 0.0 0:27 rcu_sched 14 root 20 0 000 S 3 0.0 0.0 0:06 rcuos/0 15 root 20 0 000 S 1 0.0 0.0 0:07 rcuos/1 Remark: The critical figure seems to be the swap space. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-19-generic 3.11.0-19.33 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 Ap
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
apport information ** Tags added: apport-collected ** Description changed: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0 000 S 3 0.0 0.0 0:27 rcu_sched 14 root 20 0 000 S 3 0.0 0.0 0:06 rcuos/0 15 root 20 0 000 S 1 0.0 0.0 0:07 rcuos/1 Remark: The
[Kernel-packages] [Bug 1308474] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085343/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085342/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 r
[Kernel-packages] [Bug 1308474] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085345/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085336/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085346/+files/UdevLog.txt ** 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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 00
[Kernel-packages] [Bug 1308474] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085344/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085340/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085339/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] HookError_source_linux.txt
apport information ** Attachment added: "HookError_source_linux.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085337/+files/HookError_source_linux.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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2
[Kernel-packages] [Bug 1308474] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085338/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1308474/+attachment/4085341/+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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
apport information ** Description changed: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0 000 S 3 0.0 0.0 0:27 rcu_sched 14 root 20 0 000 S 3 0.0 0.0 0:06 rcuos/0 15 root 20 0 000 S 1 0.0 0.0 0:07 rcuos/1 Remark: The critical figure seems to be the swap s
Re: [Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
On 04/16/2014 09:36 PM, Joseph Salisbury wrote: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v3.15 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > If you are unable to test the mainline kernel, for example it will not boot, > please add the tag: 'kernel-unable-to-test-upstream'. > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > > ** Tags added: kernel-da-key > Sorry, I did not find a specific field to add a tag, so I added a comment, right? WJ -- Dr. Wolfgang Jansen Lauenburger Straße 40 D-12169 Berlin Tel: (+49) 0172 40 86 916 e-mail: wo.jan...@kabelmail.de -- 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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01l
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0 000 S 3 0.0 0.0 0:2
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
** 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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Confirmed Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0
[Kernel-packages] [Bug 1308474] Re: CPU-intensive processes killed by OS
** Tags added: kernel-bug-reported-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/1308474 Title: CPU-intensive processes killed by OS Status in “linux” package in Ubuntu: Triaged Bug description: When testing some algorithm I ran the test program several times with different parameters. It was to be expected that each run takes about four hours, and to utilize the capacities of my computer (4 CPUs) I started the program 4 times running in parallel and with lowered priority (the latter to be able to do meanwhile something else on the computer). All four processes ran in parallel for a few minutes but then two of them were killed with the error message: Command terminated by signal 9 [1] Exit 137/usr/bin/time -f '%U+%S sec, avg %Kk max %Mk memory, major %F minor %R faults, %I+%O i/o' ./testu01long -d9689 -b3 > cat9689.tub Here, "/usr/bin/time ..." is the command I launched for the first process, the second error message was quite similar, now for the second process. The process started first ran about 6 minutes, the second about 14 minutes, so the TERM signals have been issued at different times (the processes had been started within one minute). The two other processes continued without problems. The point is that I did NOT issue a TERM signal to the processes, I conclude that the OS issued the TERM signals. The effect can be repeated to some extend: if another CPU-intensive process is started (e.g. a lengthy compilation) then an already running CPU-intensive process may be killed, if so then the one first started. When the killed program had been relaunched with the same parameters but without concurrency of other CPU-intensive processes (e.g. only editing, reading e-mails running in parallel) then all things were fine, so the kill is really not caused by the program. The program does not use external devices and even no I/O except for writing a summary to stdout at program end (i.e. not when the processes were killed). The question is, why have the processes been killed? Is the OS unable to manage as many running processes? I consider this a bug in the OS, part process management. The bug implies that the computer can be used for light weight tasks only. With regards Dr. Wolfgang Jansen PS: Additional platform info (commands "ulimit -a", "top" when two CPU-intensive processes were still running): core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30092 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30092 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- Tasks: 244 total, 3 running, 241 sleeping, 0 stopped, 0 zombie %Cpu(s): 15.5 us, 1.2 sy, 27.5 ni, 54.6 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3930376 total, 2263872 used, 1666504 free,36756 buffers KiB Swap: 9212 total, 9212 used,0 free, 705612 cached PID USER PR NI VIRT RES SHR S P %CPU %MEM TIME COMMAND 18804 wolfgang 30 10 14632 960 648 R 1 103.0 0.0 95:09 testu01long 18817 wolfgang 30 10 14632 960 648 R 0 103.0 0.0 94:03 testu01long 2491 root 20 0 444m 128m 103m S 2 6.4 3.3 7:04 Xorg 2945 wolfgang 20 0 1950m 205m 11m S 2 6.4 5.4 13:08 cinnamon 1 root 20 0 27336 15360 S 1 0.0 0.0 0:01 init 2 root 20 0 000 S 3 0.0 0.0 0:00 kthreadd 3 root 20 0 000 S 0 0.0 0.0 0:00 ksoftirqd/0 5 root 0 -20 000 S 0 0.0 0.0 0:00 kworker/0:0H 7 root rt 0 000 S 0 0.0 0.0 0:00 migration/0 8 root 20 0 000 S 0 0.0 0.0 0:00 rcu_bh 9 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/0 10 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/1 11 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/2 12 root 20 0 000 S 0 0.0 0.0 0:00 rcuob/3 13 root 20 0
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
this patch fixes kernel crashes with kernels >=3.18 for me on BCM43228. I'm currently using it on top of vivids bcmwl-kernel-source: 6.30.223.248+bdcom-0ubuntu2 and the vivid 3.19.0 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: Incomplete Bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1412470] [NEW] HL-DT-ST DVDRAM GSA-T20N-(P)
Public bug reported: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: New Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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.la
[Kernel-packages] [Bug 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P)
** Tags removed: apport-bug i386 trusty ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: Incomplete Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P)
Hello Joseph, I installed as described in the wiki. But there is no boot menu. kubuntu started streigt away. It is the only OS on this laptop. After installation I made a sceen shot from the output of the terminal. See the attachment. Best regards Wolfgang Am 20.01.2015 um 19:11 schrieb Joseph Salisbury: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v3.19 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > If you are unable to test the mainline kernel, for example it will not boot, > please add the tag: 'kernel-unable-to-test-upstream'. > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc5-vivid/ > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > -- Mit freundlichen Grüßen Wolfgang Hahnl E-Mail: wolfgang.ha...@gmx.de ** Attachment added: "Installationsprozess.png" https://bugs.launchpad.net/bugs/1412470/+attachment/4305244/+files/Installationsprozess.png -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: Incomplete Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P)
Hello Joseph, I installed as described in the wiki. After installation I made a sceen shot from the output of the terminal. See the attachment of my E-Mail. But there is no boot menu, like it says in the Wiki, to choose the upstrean kernel. kubuntu started streigt away. It is the only OS on this laptop. I inserted a DVD and noting happend. Best regards Wolfgang -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: Incomplete Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P)
Hello Christopher, I installed (3.19-rc6) and couldn't boot into the OS. There were no boot menu to select and test the new kernel version. Wolfgang Am 27.01.2015 um 12:49 schrieb Christopher M. Penalver: > Wolfgang Hahnl, could you please test the latest upstream kernel > available (3.19-rc6) from the very top line at the top of the page (the > release names are irrelevant for testing, and please do not test the > daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? > It will allow additional upstream developers to examine the issue. > > If the test did not allow you to test to the issue (ex. you couldn't boot > into the OS) please make a comment in your report about this, and continue to > test the next most recent kernel version until you can test to the issue. > Once you've tested the upstream kernel, please comment on which kernel > version specifically you tested. If this bug is fixed in the mainline kernel, > please add the following tags by clicking on the yellow circle with a black > pencil icon, next to the word Tags, located at the bottom of the report > description: > kernel-fixed-upstream > kernel-fixed-upstream-3.XY-rcZ > > Where XY and Z are numbers corresponding to the kernel version. > > If the mainline kernel does not fix this bug, please add the following tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-3.XY-rcZ > > Once testing of the upstream kernel is complete, please mark this bug's > Status as Confirmed. Please let us know your results. > > Thank you for your understanding. > > ** Tags removed: kernel-unable-to-test-upstream > ** Tags added: apport-bug i386 trusty > -- Mit freundlichen Grüßen Wolfgang Hahnl Neschwitzweg 15 04668 Grimma Tel.03437 94 30 45 Mobil: 0160 90 90 3711 E-Mail: wolfgang.ha...@gmx.de -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: Incomplete Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P)
Today I have tested upstream kernel v3.19.0 rc6. I pressed the shift key during boot process. So I could select the kernel. But the kernel-bug-exists-upstream-3.19-rc6 ** 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P)
tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.19-rc6 -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P)
I got this laptop as a gift. XP was obsolate and the fellow wouldn't use it any more. So I started with 12.04 This problem occurt with 12.04. Therefore I installed 14.04. Because I thougt: the newer the better. Am 31.01.2015 um 02:38 schrieb Christopher M. Penalver: > Wolfgang Hahnl, did this problem not occur in a release prior to 14.04? > > ** Tags added: latest-bios-1.04 > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > Wolfgang -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) Status in linux package in Ubuntu: Incomplete Bug description: I installed ubuntu 14.04 via DVD-iso. I inserted it in the DVD-device. During installation procedure the DVD-device worked properly. After installation I got no connection to the device. If I insert a video DVD the device stats an stops again. If I use a teminal and ask with sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. I looked in the BIOS there is the information: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 The ubuntu system is up to date. I hope you can send me a patch. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P) not recognized after installation
done sent e.mail to linux-scsi mailing list -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) not recognized after installation Status in linux package in Ubuntu: Triaged Bug description: I installed Ubuntu 14.04 via DVD-iso in the DVD drive. During installation procedure the DVD drive worked properly. After installation I got no connection to the device. If I insert a video DVD the drive starts and stops again. If I execute at a terminal: sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. As per the BIOS: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P) not recognized after installation
Link to the linux-scsi mailing list: http://marc.info/?l=linux-scsi&m=142282087601285&w=2 -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) not recognized after installation Status in linux package in Ubuntu: Triaged Bug description: I installed Ubuntu 14.04 via DVD-iso in the DVD drive. During installation procedure the DVD drive worked properly. After installation I got no connection to the device. If I insert a video DVD the drive starts and stops again. If I execute at a terminal: sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. As per the BIOS: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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 1412470] Re: HL-DT-ST DVDRAM GSA-T20N-(P) not recognized after installation
Today I installed kernel-version 3.19 from 09-Feb-2015 15:34 Nothing changed -- 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/1412470 Title: HL-DT-ST DVDRAM GSA-T20N-(P) not recognized after installation Status in linux package in Ubuntu: Triaged Bug description: I installed Ubuntu 14.04 via DVD-iso in the DVD drive. During installation procedure the DVD drive worked properly. After installation I got no connection to the device. If I insert a video DVD the drive starts and stops again. If I execute at a terminal: sudo lshw -C disk I get only information about the hard drive and no information about DVDRAM. As per the BIOS: IDE Slave HL-DT-ST DVDRAM GSA-T20N-(P) Transfer Mode: 8FPIO4/DMA2] Ultra DMA Mode: Mode 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilly 1907 F pulseaudio lilly 2062 F pulseaudio CurrentDesktop: KDE Date: Mon Jan 19 15:53:18 2015 HibernationDevice: RESUME=UUID=d1531850-f916-46b3-bc78-7f7369cb061d InstallationDate: Installed on 2015-01-14 (5 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1) MachineType: MAXDATA ECO4511IW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=0c43b0f2-91c5-4b9a-abcc-ffabd104c5d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/31/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04MAX dmi.board.name: ECO4511IW dmi.board.vendor: MAXDATA dmi.chassis.type: 10 dmi.chassis.vendor: MAXDATA dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04MAX:bd08/31/2007:svnMAXDATA:pnECO4511IW:pvr:rvnMAXDATA:rnECO4511IW:rvr:cvnMAXDATA:ct10:cvr: dmi.product.name: ECO4511IW dmi.sys.vendor: MAXDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412470/+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 1248500] [NEW] Atheros AR3012 cannot be turned up/is not recognized
Public bug reported: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: New Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Re: Atheros AR3012 cannot be turned up/is not recognized
kubuntu 13.10 -- 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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: New Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Re: Atheros AR3012 cannot be turned up/is not recognized
apport information ** Tags added: apport-collected saucy ** Description changed: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: wolfgang 2142 F pulseaudio + /dev/snd/controlC2: wolfgang 2142 F pulseaudio + /dev/snd/controlC0: wolfgang 2142 F pulseaudio + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d + InstallationDate: Installed on 2013-11-02 (4 days ago) + InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) + MachineType: Dell Inc. XPS 8700 + MarkForUpload: True + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 + RelatedPackageVersions: + linux-restricted-modules-3.11.0-12-generic N/A + linux-backports-modules-3.11.0-12-generic N/A + linux-firmware 1.116 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: yes + Hard blocked: no + Tags: saucy + Uname: Linux 3.11.0-12-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + dmi.bios.date: 08/02/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A03 + dmi.board.name: 0KWVT8 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 3 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: + dmi.product.name: XPS 8700 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901387/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1248500] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901391/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901393/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901388/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901392/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901389/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901390/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901397/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901398/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901400/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901396/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901401/+files/WifiSyslog.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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901399/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901394/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1248500/+attachment/3901395/+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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Re: Atheros AR3012 cannot be turned up/is not recognized
** 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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Confirmed Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Re: Atheros AR3012 cannot be turned up/is not recognized
** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Re: Atheros AR3012 cannot be turned up/is not recognized
Sorry Kernel v3.12 does'nt boot to graphic, only to terminal login -- 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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Re: Atheros AR3012 cannot be turned up/is not recognized
If WLAN is soft switched on, Bluetooth seems to work properly. -- 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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1248500] Re: Atheros AR3012 cannot be turned up/is not recognized
Bluetooth worked during several boots, now again not. Seems to be a sporadic effect -- 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/1248500 Title: Atheros AR3012 cannot be turned up/is not recognized Status in “linux” package in Ubuntu: Incomplete Bug description: lsusb -s 3:8 Bus 003 Device 008: ID 0cf3:e004 Atheros Communications, Inc. dmesg [ 22.302858] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 22.302865] Bluetooth: Loading patch file failed [ 22.302871] ath3k: probe of 3-13:1.0 failed with error -110 [ 22.302900] usbcore: registered new interface driver ath3k --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolfgang 2142 F pulseaudio /dev/snd/controlC2: wolfgang 2142 F pulseaudio /dev/snd/controlC0: wolfgang 2142 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f64f66e4-320f-417a-b25f-f7d9b8aed16d InstallationDate: Installed on 2013-11-02 (4 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 8700 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=5577f2c6-030c-4234-b371-5b3dbf22b355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/02/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248500/+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 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36
Hi! Same here with an Acer Swift SF314-56G. Sound does not work on -45 but works on -46 (from proposed). -- 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/1867803 Title: ALSA: No soundcards found after updating kernel to 5.3.0.42.36 Status in linux package in Ubuntu: Confirmed Bug description: There seems to be some changes in ALSA in 5.3.0.41 and it seems to have caused some regression on my HP Spectrre (details attached). ~$ alsactl init alsactl: init:1759: No soundcards found... I verified that 5.3.0.40 works. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 01:11:42 2020 InstallationDate: Installed on 2019-07-11 (249 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP Spectre x360 Convertible 13-ap0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.vendor: AMI dmi.bios.version: F.28 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8514 dmi.board.vendor: HP dmi.board.version: 09.48 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx dmi.product.sku: 5KX23PA#ABJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867803/+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 1868376] [NEW] after kernel update: no sound, freeze on standby
Public bug reported: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1868376 Title: after kernel update: no sound, freeze on standby Status in linux package in Ubuntu: New Bug description: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868376/+subscriptions -- Mailing list: https://launchpad.n
Re: [Kernel-packages] [Bug 1868376] Re: after kernel update: no sound, freeze on standby
*** This bug is a duplicate of bug 1867803 *** https://bugs.launchpad.net/bugs/1867803 I can verify that Kernel version 5.3.0-43 (from proposed) works, as did 5.3.0-40. So this is probably a duplicate of 1867803. Kind regards Wolfgang Ratzka ** This bug has been marked a duplicate of bug 1867803 ALSA: No soundcards found after updating kernel to 5.3.0.42.36 -- 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/1868376 Title: after kernel update: no sound, freeze on standby Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868376/+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 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
I can confirm for Ubuntu 22.04, but also affects Ubuntu 18.04 (all using a dummy bridge for Xen domUs in my case). -> last working: 22.04: - linux-image-5.15.0-57-generic 18.04: - linux-image-4.15.0-201-generic -> broken: 22.04: - linux-image-5.15.0-58-generic - linux-image-5.15.0-60-generic 18.04: - linux-image-4.15.0-202-generic - linux-image-4.15.0-204-generic -- 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/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+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 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
The latest updates seem to have fixed this. -> working again: 22.04: - linux-image-5.15.0-67-generic 18.04: - linux-image-4.15.0-206-generic -- 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/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+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