[Kernel-packages] [Bug 1481481] Re: Unable to connect Lumia 730
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1481481 Title: Unable to connect Lumia 730 Status in linux package in Ubuntu: Expired Bug description: My mobile, Lumia 730 is not being recognised when I connect it with my laptop that runs Ubuntu OS. It shows the error "Error initializing camera could not claim the usb device ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: omrishy1349 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 5 02:37:16 2015 HibernationDevice: RESUME=UUID=113735e5-7e08-475a-b756-948dedb2eb29 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2015-07-30 (5 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: Hewlett-Packard HP G42 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=ea7239ae-7a96-4e84-b5c4-5420861c2702 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.2 SourcePackage: linux Symptom: storage UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 02:37:28.033: The udisks-daemon is running (name-owner :1.56). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.37 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1425 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.57 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.37:bd04/07/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr059C1300271001000:rvnHewlett-Packard:rn1425:rvr54.57:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 059C1300271001000 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481481/+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 1481621] Re: [LENOVO 27326FG] late resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1481621 Title: [LENOVO 27326FG] late resume failure Status in linux package in Ubuntu: Expired Bug description: no ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-57-generic 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.14.4-0ubuntu1~ubuntu14.04.1~c42.ppa1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: axel 2111 F pulseaudio /dev/snd/controlC0: axel 2111 F pulseaudio CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' Date: Wed Aug 5 09:28:40 2015 DuplicateSignature: late resume:LENOVO 27326FG:7YET71WW (3.01 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=c67a594d-f738-48ef-bf05-a3ed1a999c63 InstallationDate: Installed on 2014-08-07 (362 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 27326FG ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-57-generic root=UUID=a497e91b-9c74-4bf5-bdcf-728154b0d3c1 ro quiet splash vt.handoff=7 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-57-generic N/A linux-backports-modules-3.13.0-57-generic N/A linux-firmware 1.127.13 SourcePackage: linux Title: [LENOVO 27326FG] late resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/14/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7YET71WW (3.01 ) dmi.board.name: 27326FG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7YET71WW(3.01):bd05/14/2009:svnLENOVO:pn27326FG:pvrThinkPadR500:rvnLENOVO:rn27326FG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 27326FG dmi.product.version: ThinkPad R500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481621/+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 544548] Re: Kernel doesn't detect media in CD/DVD drives
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Satwik Bhandiwad (satwik-bhandiwad) -- 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/544548 Title: Kernel doesn't detect media in CD/DVD drives Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Karmic to Lucid Beta 1, my CD/DVD drive stops working (it doesn't detects inserted media). When I insert a CD or DVD, the light flashes but nothing more happens. I have the following messages on dmesg: ... [0.400909] pata_via :00:0f.1: version 0.3.4 [0.401137] scsi0 : pata_via [0.401214] scsi1 : pata_via [0.402618] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xe400 irq 14 [0.402621] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xe408 irq 15 [0.402721] alloc irq_desc for 21 on node -1 [0.402723] alloc kstat_irqs on node -1 [0.402729] pata_acpi :00:0f.0: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [0.402762] pata_acpi :00:0f.0: PCI INT B disabled ... [0.624914] ata1.00: ATAPI: PHILIPS SPD6000L1, L5P3, max UDMA/66 [0.653717] ata1.00: configured for UDMA/66 [0.711567] isapnp: No Plug & Play device found [0.712423] scsi 0:0:0:0: CD-ROMPHILIPS SPD6000L1L5P3 PQ: 0 ANSI: 5 [0.716534] sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray [0.716537] Uniform CD-ROM driver Revision: 3.20 [0.716645] sr 0:0:0:0: Attached scsi CD-ROM sr0 [0.716704] sr 0:0:0:0: Attached scsi generic sg0 type 5 ... [1.026637] sata_via :00:0f.0: version 2.4 [1.026648] sata_via :00:0f.0: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [1.026682] sata_via :00:0f.0: routed to hard irq line 11 ... [ 5446.31] ata1: lost interrupt (Status 0x50) [ 5477.35] ata1: lost interrupt (Status 0x51) [ 5482.36] ata1.00: qc timeout (cmd 0xa0) [ 5482.48] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 5482.54] sr 0:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00 [ 5482.70] ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [ 5482.71] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout) [ 5482.75] ata1.00: status: { DRDY ERR } [ 5482.000100] ata1: soft resetting link [ 5482.216303] ata1.00: configured for UDMA/66 [ 5487.216031] ata1.00: qc timeout (cmd 0xa0) [ 5487.216040] ata1.00: TEST_UNIT_READY failed (err_mask=0x5) [ 5487.216066] ata1: soft resetting link [ 5487.432316] ata1.00: configured for UDMA/66 [ 5492.432047] ata1.00: qc timeout (cmd 0xa0) [ 5492.432056] ata1.00: TEST_UNIT_READY failed (err_mask=0x5) [ 5492.432063] ata1.00: limiting speed to UDMA/66:PIO3 [ 5492.432089] ata1: soft resetting link [ 5492.644320] ata1.00: configured for UDMA/66 [ 5497.644030] ata1.00: qc timeout (cmd 0xa0) [ 5497.644039] ata1.00: TEST_UNIT_READY failed (err_mask=0x5) [ 5497.644042] ata1.00: disabled [ 5497.644082] ata1: soft resetting link [ 5497.800096] ata1: EH complete ... It's the first time I have a non-working CD/DVD drive under Ubuntu (and I'm an Ubuntu user since Warty). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/544548/+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 1494076] Re: [Feature] Please backport mei support for Sunrise Point
This bug was fixed in the package linux - 4.2.0-14.16 --- linux (4.2.0-14.16) wily; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim GardnerTue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Fix Released -- 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/1494076 Title: [Feature] Please backport mei support for Sunrise Point Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: Support for the Sunrise Point PCH has been added to the mei driver for linux 4.3, but it would be nice if this could be backported to Wily as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494076/+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 1501235] Re: linux-signed-: dependencies to linux-image-extra are on the wrong package
This bug was fixed in the package linux-signed - 4.2.0-14.16 --- linux-signed (4.2.0-14.16) wily; urgency=low [ Andy Whitcroft ] * split separate shell commands so make can see them, aids debugging in case of failure. [ Tim Gardner ] * Version 4.2.0-14.16 -- Tim GardnerThu, 01 Oct 2015 10:53:10 -0700 ** Changed in: linux-signed (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-meta (Ubuntu) Status: Fix Committed => Fix Released -- 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/1501235 Title: linux-signed-: dependencies to linux-image-extra are on the wrong package Status in linux-meta package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Released Bug description: The norm is for the linux-image-- packages to decide which component kernel bits they need, for split kernels this means -generic has linux-image--generic and linux-image--generic. For linux-signed-- this is being handled out of the linux-signed source package, which is both confusing and wrong in the sense it would prevent us from having a linux-signed-virtual. We should move the linux-image-extra dependency over to linux-meta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1501235/+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 1500910] Re: linux-signed should also produce linux-signed-image-*-lowlatency
This bug was fixed in the package linux-signed - 4.2.0-14.16 --- linux-signed (4.2.0-14.16) wily; urgency=low [ Andy Whitcroft ] * split separate shell commands so make can see them, aids debugging in case of failure. [ Tim Gardner ] * Version 4.2.0-14.16 -- Tim GardnerThu, 01 Oct 2015 10:53:10 -0700 ** Changed in: linux-signed (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-meta (Ubuntu) Status: Fix Committed => Fix Released -- 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/1500910 Title: linux-signed should also produce linux-signed-image-*-lowlatency Status in linux-meta package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Released Bug description: We are already uploading all flavours for signing by LP, it makes sense to produce actual binary packages from them. These are tiny anyhow as they only contain the signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1500910/+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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails
This bug was fixed in the package linux - 4.2.0-14.16 --- linux (4.2.0-14.16) wily; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim GardnerTue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Fix Released -- 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/1499869 Title: maas wily deployment to HP Proliant m400 arm64 server cartridge fails Status in cloud-init: Confirmed Status in curtin: New Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Status in cloud-init source package in Wily: Fix Released Status in linux source package in Wily: Fix Released Bug description: This is the error seen on the console: [ 64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin [ 124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))] [ 124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds [ 124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404] This times out eventually and the node is left at the login prompt. I can install wily via netboot without issue and some
[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid
This bug was fixed in the package linux - 4.2.0-14.16 --- linux (4.2.0-14.16) wily; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim GardnerTue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Fix Released -- 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/1440103 Title: [Hyper-V] Kernel panic not functional on Vivid Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: In Progress Status in linux source package in Wily: Fix Released Bug description: Issue description: Triggering a kernel panic will not produce a crash dump file. Steps to Reproduce: 1. install kdump related packages. 2. verify crashmem value - defaults to 384M-:129M 3. verify that the system is ready for crash: # cat /sys/kernel/kexec_crash_loaded 1 4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger 5. The system will freeze and no kernel dump will be generated, system is not rebooted automatically as configured in kdump-tools config. Versions details: Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter build 9600 Distribution name and release: Ubuntu Vivid Vervet Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 SMP Repro output with VM settings as follows: 2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M [ 149.328829] SysRq : Trigger a crash [ 149.342418] BUG: unable to handle kernel NULL pointer dereference at (null) [ 149.346369] IP: [] sysrq_handle_crash+0x16/0x20 [ 149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0 [ 149.346369] Oops: 0002 [#1] SMP [ 149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 8250_fintek hyperv_keyboard hv_balloon hyp erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc
[Kernel-packages] [Bug 1500672] Re: cpufreq: powernv : Decrease the severity of console messages
This bug was fixed in the package linux - 4.2.0-14.16 --- linux (4.2.0-14.16) wily; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim GardnerTue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Fix Released -- 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/1500672 Title: cpufreq: powernv : Decrease the severity of console messages Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: "CPU Frequency could be throttled" dmesg is logged with critical log level when the max frequency is clipped. This message should be logged to 'info' if the frequency is throttled between nominal and turbo and not as critical. Fix for this involves the below two patches: 1)053819e0bf8407746cc5febf7a4947bee50377b4 cpufreq: powernv: Handle throttling due to Pmax capping at chip level 2) https://patchwork.ozlabs.org/patch/517268/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500672/+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 1500894] Re: linux: 4.2.0-13.15 -proposed tracker
This bug was fixed in the package linux - 4.2.0-14.16 --- linux (4.2.0-14.16) wily; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim GardnerTue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu Wily) Status: Invalid => Fix Released -- 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/1500894 Title: linux: 4.2.0-13.15 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: This bug is for tracking the 4.2.0-13.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 29. September 2015 14:01 UTC kernel-phase-changed:Tuesday, 29. September 2015 14:01 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 15:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1500894/+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 1501235] Re: linux-signed-: dependencies to linux-image-extra are on the wrong package
This bug was fixed in the package linux-meta - 4.2.0.14.15 --- linux-meta (4.2.0.14.15) wily; urgency=medium * linux ABI 4.2.0-14 * Makefile: ignore dependencies when building the package -- Tim GardnerThu, 01 Oct 2015 12:07:00 -0600 -- 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/1501235 Title: linux-signed-: dependencies to linux-image-extra are on the wrong package Status in linux-meta package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Released Bug description: The norm is for the linux-image-- packages to decide which component kernel bits they need, for split kernels this means -generic has linux-image--generic and linux-image--generic. For linux-signed-- this is being handled out of the linux-signed source package, which is both confusing and wrong in the sense it would prevent us from having a linux-signed-virtual. We should move the linux-image-extra dependency over to linux-meta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1501235/+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 1492132] Re: Fix the white noise on Dell laptop
This bug was fixed in the package linux - 4.2.0-14.16 --- linux (4.2.0-14.16) wily; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim GardnerTue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/1492132 Title: Fix the white noise on Dell laptop Status in linux package in Ubuntu: Fix Released Bug description: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492132/+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 1500910] Re: linux-signed should also produce linux-signed-image-*-lowlatency
This bug was fixed in the package linux-meta - 4.2.0.14.15 --- linux-meta (4.2.0.14.15) wily; urgency=medium * linux ABI 4.2.0-14 * Makefile: ignore dependencies when building the package -- Tim GardnerThu, 01 Oct 2015 12:07:00 -0600 -- 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/1500910 Title: linux-signed should also produce linux-signed-image-*-lowlatency Status in linux-meta package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Released Bug description: We are already uploading all flavours for signing by LP, it makes sense to produce actual binary packages from them. These are tiny anyhow as they only contain the signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1500910/+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 1502552] Re: touchpad not working
** Changed in: linux-lts-raring (Ubuntu) Assignee: (unassigned) => Chintana Prabhu (chintanarp98) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1502552 Title: touchpad not working Status in linux-lts-raring package in Ubuntu: New Bug description: Touchpad is not responding. External mouse is working. The touchpad is not listed in xinput. External mouse is listed twice in xinput as well as in 'cat /proc/bus/input/devices' but touchpad driver isn't. What I expected to see in /proc/bus/input/devices file: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 U: Uniq= H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 7 0 0 0 0 0 0 0 0 B: ABS=1103 What I saw instead: I: Bus=0003 Vendor=046d Product=c07e Version=0111 N: Name="Logitech Gaming Mouse G402" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.0/input/input15 U: Uniq=6D9036795757 H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=143 B: MSC=10 I: Bus=0003 Vendor=046d Product=c07e Version=0111 N: Name="Logitech Gaming Mouse G402" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.1/input/input16 U: Uniq=6D9036795757 H: Handlers=sysrq kbd event6 B: PROP=0 B: EV=10001f B: KEY=4837fff072ff32d bf56 1 30f908b17c007 ffe77bfad941dfff febeffdfffef fffe B: REL=40 B: ABS=1 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-44-generic 3.8.0-44.66~precise1 ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25 Uname: Linux 3.8.0-44-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-44-generic. ApportVersion: 2.0.1-0ubuntu17.11 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sumit 2114 F pulseaudio /dev/snd/controlC0: sumit 2114 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf7a14000 irq 60' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xf7a1 irq 61' Mixer name : 'Realtek ALC255' Components : 'HDA:10ec0255,10280662,0012' Controls : 18 Simple ctrls : 8 Date: Sun Oct 4 10:01:29 2015 HibernationDevice: RESUME=UUID=45998e30-d2b6-4037-96ff-63f405f9832d InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Dell Inc. Vostro 3446 MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-44-generic root=UUID=8def0356-8cf9-4e71-829f-03a59b5d259f ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-44-generic N/A linux-backports-modules-3.8.0-44-generic N/A linux-firmware1.79.18 SourcePackage: linux-lts-raring StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1502552/+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 1210373] Re: kernel crash at veth interface shutdown (net_carrier_off)
Jérôme Petazzoni, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1210373 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210373 Title: kernel crash at veth interface shutdown (net_carrier_off) Status in linux package in Ubuntu: Incomplete Bug description: When destroying a veth interface when both members of the veth pair are up, a kernel bug is triggered. How to reproduce: ip link add type veth ip link set veth0 up ip link set veth1 up ip link del veth0 I've uploaded the kernel log to https://gist.github.com/jpetazzo/6190928. In some cases, it completely locks up the machine. For instance, when a LXC ocntainer is stopped, the bug happens, but the machine is then frozen (no console, no reply to ping). I've uploaded the corresponding kernel log to https://gist.github.com/jpetazzo/6190908. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-28-generic 3.8.0-28.41~precise1 ProcVersionSignature: Ubuntu 3.8.0-28.41~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-28-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Fri Aug 9 03:31:01 2013 MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=linux LANG=en_US.UTF-8 SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210373/+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 1502598] Re: Boot hangs on encryption password prompt on 3.19.0-30
Possibly related to #1502055 -- 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/1502598 Title: Boot hangs on encryption password prompt on 3.19.0-30 Status in linux package in Ubuntu: Incomplete Bug description: Starting with kernel 3.19.0-30-generic, the password prompt for my disk encryption password hangs at boot. I can workaround the issue by booting with kernel 3.19.0-28-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1788 F pulseaudio /dev/snd/controlC0: mark 1788 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 4 07:22:53 2015 HibernationDevice: RESUME=UUID=4392843b-ec3d-442b-8159-f2e4bed58105 InstallationDate: Installed on 2015-09-20 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502598/+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 1502055] Re: Crypt password screen not responding
@penalvch: As requested, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502598 -- 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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1502598] [NEW] Boot hangs on encryption password prompt on 3.19.0-30
Public bug reported: Starting with kernel 3.19.0-30-generic, the password prompt for my disk encryption password hangs at boot. I can workaround the issue by booting with kernel 3.19.0-28-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1788 F pulseaudio /dev/snd/controlC0: mark 1788 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 4 07:22:53 2015 HibernationDevice: RESUME=UUID=4392843b-ec3d-442b-8159-f2e4bed58105 InstallationDate: Installed on 2015-09-20 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-bug latest-bios-a05 vivid -- 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/1502598 Title: Boot hangs on encryption password prompt on 3.19.0-30 Status in linux package in Ubuntu: Incomplete Bug description: Starting with kernel 3.19.0-30-generic, the password prompt for my disk encryption password hangs at boot. I can workaround the issue by booting with kernel 3.19.0-28-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1788 F pulseaudio /dev/snd/controlC0: mark 1788 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 4 07:22:53 2015 HibernationDevice: RESUME=UUID=4392843b-ec3d-442b-8159-f2e4bed58105 InstallationDate: Installed on 2015-09-20 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502598/+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 1502598] Re: Boot hangs on encryption password prompt on 3.19.0-30
Mark Adams, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel 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 issue 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-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-a05 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502598 Title: Boot hangs on encryption password prompt on 3.19.0-30 Status in linux package in Ubuntu: Incomplete Bug description: Starting with kernel 3.19.0-30-generic, the password prompt for my disk encryption password hangs at boot. I can workaround the issue by booting with kernel 3.19.0-28-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1788 F pulseaudio /dev/snd/controlC0: mark 1788 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 4 07:22:53 2015 HibernationDevice: RESUME=UUID=4392843b-ec3d-442b-8159-f2e4bed58105 InstallationDate: Installed on 2015-09-20 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502598/+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 1502598] Re: Boot hangs on encryption password prompt on 3.19.0-30
It should be noted that these logs appear to show my workaround boot on the 3.19.0-28-generic. Not the hanging boot on the 3.19.0-30-generic kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502598 Title: Boot hangs on encryption password prompt on 3.19.0-30 Status in linux package in Ubuntu: Incomplete Bug description: Starting with kernel 3.19.0-30-generic, the password prompt for my disk encryption password hangs at boot. I can workaround the issue by booting with kernel 3.19.0-28-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1788 F pulseaudio /dev/snd/controlC0: mark 1788 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 4 07:22:53 2015 HibernationDevice: RESUME=UUID=4392843b-ec3d-442b-8159-f2e4bed58105 InstallationDate: Installed on 2015-09-20 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502598/+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 1268252] Re: Brightness settings stopped working after upgrade
** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Satwik Bhandiwad (satwik-bhandiwad) -- 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/1268252 Title: Brightness settings stopped working after upgrade Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, both the physical key and the brightness settings in the gnome-control centre have stopped working. Whatever level of brightness i decrease it to, it always stays on maximum. I'm able to reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 12 09:17:00 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2013-11-16 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago) --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krishnan 3070 F pulseaudio /dev/snd/controlC0: krishnan 3070 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c545b9da-fef4-4530-9051-29276dfd842c InstallationDate: Installed on 2013-11-16 (58 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO INVALID NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=0b897d24-0c02-4f57-9596-5fcd681c5ed0 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-2-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-06 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN12WW(V1.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.name: INVALID dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268252/+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 1501818] Re: linux: 4.2.0-14.16 -proposed tracker
This bug was fixed in the package linux - 4.2.0-14.16 --- linux (4.2.0-14.16) wily; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim GardnerTue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu Wily) Status: Invalid => Fix Released -- 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/1501818 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1501818/+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 1502055] Re: Crypt password screen not responding
I'm experiencing the same issue running after upgrading to 3.19.0-30-generic. If I downgrade to 3.19.0-28-generic, the password prompt for my encrypted disk behaves normally and I'm able to boot. -- 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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1502055] Re: Crypt password screen not responding
This problem also started happening since updating to 3.19.0-30. I'm running Ubuntu 15.04 on a Lenovo X1 Carbon 3rd generation. Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, integrated graphics. -- 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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1249302] Re: AMD Radeon HD 8210[1002:9834] Brightness cannnot be adjusted without fglrx driver
Po-Hsu Lin, as per http://www.dell.com/support/home/us/en/19/product- support/product/inspiron-3135/drivers an update to your computer's buggy and outdated BIOS is available (A02). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-a02 ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1249302 Title: AMD Radeon HD 8210[1002:9834] Brightness cannnot be adjusted without fglrx driver Status in linux package in Ubuntu: Incomplete Bug description: CID: 201308-14057 Dell Inspiron 3135 Brightness cannot be adjusted if the proprietary fglrx video driver is not installed. Module "radeon" cannot be found in lsmod, it seems that this graphic chip is not supported Steps: 1. Install 12.04.3, and boot to desktop. 2. Try to adjust screen brightness with hotkey 3. Try to adjust screen brightness in "Brightness and Lock" Expected results: 1. Brightness could be adjusted by the hokey 2. Brightness could be adjusted in "Brightness and Lock" Actual Results: 1. Hotkey event was correctly captured, brightness indicator level will change accordingly, but the brightness won't be altered. 2. Brightness cannot be adjusted in "Brightness and Lock" as well Update to 3.8.0-33 still not helping with this. However, acpi_backlight=vendor in grub can make it work. So as the proprietary fglrx driver. Debugging information: $ /usr/lib/nux/unity_support_test -c -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.2, 128 bits) OpenGL version string: 2.1 Mesa 9.1.7 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: no $ /usr/share/checkbox/scripts/graphics_driver - VIDEO DRIVER INFORMATION - ERROR: No video driver loaded! Possibly in failsafe mode! - HYBRID GRAPHICS CHECK Graphics Chipset: AMD (1002:9834) Loaded DDX Drivers: ati, radeon, vesa, modesetting, fbdev Hybrid Graphics: no $ cat /proc/version Linux version 3.8.0-33-generic (buildd@toyol) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #48~precise1-Ubuntu SMP Thu Oct 24 16:28:06 UTC 2013 $ dmesg | grep 'ACPI: Video' [9.979714] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) $ ls /sys/class/backlight dell_backlight === After the "acpi_backlight=vendor" was added into grub=== $ ls /sys/class/backlight dell_backlight ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: Generic_1 [HD-Audio Generic], device 0: ALC283 Analog [ALC283 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1735 F pulseaudio /dev/snd/controlC0: ubuntu 1735 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0x9024 irq 81' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100500' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0x90244000 irq 82' Mixer name : 'Realtek ALC283' Components : 'HDA:10ec0283,10280614,0013' Controls
[Kernel-packages] [Bug 1250144] Re: linux-image-3.8.0-* packages contails a lot of duplicated firmware files in /lib/firmware/3.8.0-*/
** No longer affects: linux-lts-raring (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1250144 Title: linux-image-3.8.0-* packages contails a lot of duplicated firmware files in /lib/firmware/3.8.0-*/ Status in linux-lts-saucy package in Ubuntu: Confirmed Bug description: I've found, that my system contains lots of duplicated files in /lib/firmware/ and /lib/firmware/3.8.0-*/ subfolders: /usr/lib/firmware/3.8.0-33-generic/asihpi/dsp5000.bin /usr/lib/firmware/3.8.0-33-generic/asihpi/dsp6200.bin /usr/lib/firmware/3.8.0-33-generic/asihpi/dsp6205.bin /usr/lib/firmware/3.8.0-33-generic/asihpi/dsp6400.bin /usr/lib/firmware/3.8.0-33-generic/asihpi/dsp6600.bin /usr/lib/firmware/3.8.0-33-generic/asihpi/dsp8700.bin /usr/lib/firmware/3.8.0-33-generic/asihpi/dsp8900.bin /usr/lib/firmware/3.8.0-33-generic/3com/typhoon.bin /usr/lib/firmware/3.8.0-33-generic/acenic/tg1.bin /usr/lib/firmware/3.8.0-33-generic/acenic/tg2.bin /usr/lib/firmware/3.8.0-33-generic/adaptec/starfire_rx.bin /usr/lib/firmware/3.8.0-33-generic/adaptec/starfire_tx.bin /usr/lib/firmware/3.8.0-33-generic/advansys/3550.bin /usr/lib/firmware/3.8.0-33-generic/advansys/38C0800.bin /usr/lib/firmware/3.8.0-33-generic/advansys/38C1600.bin /usr/lib/firmware/3.8.0-33-generic/advansys/mcode.bin /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.0/athwlan.bin.z77 /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.0/bdata.SD31.bin /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.0/data.patch.bin /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.0/otp.bin.z77 /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.1.1/athwlan.bin /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.1.1/bdata.SD31.bin /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.1.1/data.patch.bin /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.1.1/fw-2.bin /usr/lib/firmware/3.8.0-33-generic/ath6k/AR6003/hw2.1.1/otp.bin /usr/lib/firmware/3.8.0-33-generic/bnx2/bnx2-mips-06-6.2.3.fw /usr/lib/firmware/3.8.0-33-generic/bnx2/bnx2-mips-09-6.2.1b.fw /usr/lib/firmware/3.8.0-33-generic/bnx2/bnx2-rv2p-09-6.0.17.fw /usr/lib/firmware/3.8.0-33-generic/bnx2/bnx2-rv2p-09ax-6.0.17.fw: /usr/lib/firmware/3.8.0-33-generic/e100/d101m_ucode.bin /usr/lib/firmware/3.8.0-33-generic/e100/d101s_ucode.bin /usr/lib/firmware/3.8.0-33-generic/e100/d102e_ucode.bin /usr/lib/firmware/3.8.0-33-generic/qlogic/1040.bin /usr/lib/firmware/3.8.0-33-generic/qlogic/12160.bin /usr/lib/firmware/3.8.0-33-generic/qlogic/1280.bin /usr/lib/firmware/3.8.0-33-generic/rtlwifi/rtl8192cfwU.bin /usr/lib/firmware/3.8.0-33-generic/rtlwifi/rtl8192cfwU_B.bin /usr/lib/firmware/3.8.0-33-generic/rtlwifi/rtl8192defw.bin /usr/lib/firmware/3.8.0-33-generic/rtlwifi/rtl8192sefw.bin /usr/lib/firmware/3.8.0-33-generic/tigon/tg3.bin /usr/lib/firmware/3.8.0-33-generic/tigon/tg3_tso.bin /usr/lib/firmware/3.8.0-33-generic/tigon/tg3_tso5.bin Bug is in linux-image-3.8.0-* packages - they contains a lot of duplicated firmware files in /lib/firmware/3.8.0-*/ , because the same files also exists in linux-firmware package. You can easily find identical files with fdupes tool. Several megabytes in user systems and lots of megabytes in package mirrors are wasted because identical firmware files are included into linux-image-3.8.0-* packages and linux-firmware package. Btw, I've noticed several big firmware files with identical names, but different content, like /lib/firmware/3.8.0-33-generic/phanfw.bin and /lib/firmware/phanfw.bin - maybe these firmware files could be updated in linux-firmware package and then removed from linux-image-3.8.0-* packages? Should I report separate bug about updating these firmware files against linux-firmware package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1250144/+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 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting
I'm attaching the script here that I'm using as a workaround under Vivid and Wily for proper suspend (put into /lib/systemd/system-sleep). Kind regards, Jan ** Attachment added: "set-wol-on-suspend.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4483622/+files/set-wol-on-suspend.sh -- 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/1450396 Title: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on- lan setting Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: Hello, using Suspend-to-RAM on my system has stopped working reliably on Vivid when booting with Systemd. When I try to suspend my PC the following happens: - PC turns off - PC unwantedly wakes up (turns on) by itself again. This time span until it turns on again can reach from a second (almost immediately) until two or three minutes. - In a few cases (<25%), the PC stays suspended properly. A way to workaround this problem is to boot my PC with Upstart instead of Systemd, then this problem never happens (and has never happened in any of the previous Ubuntu versions since 2008). Thus it seems to be a bug somehow related to Systemd. Other steps I have tried to solve the problem (without any success): - Checking BIOS settings, all options are set that way that the PC should never wake up by any event other than pressing the power button. - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device could cause wake up events. This lists my USB controller, but deactivating it (with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the problem. Also suspend while running Upstart works fine despite the USB controller listed as "enabled". In the system logs I could see no hint what causes the undesired wake- ups. Allthough there is one factor which seems to have a certain influence: If I close programs like Pidgin, Skype or Firefox that cause continuous network traffic, the chance is higher that my PC will stay suspened (while runinng Systemd). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 11:24:46 2015 InstallationDate: Installed on 2015-04-16 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+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 1492466] Re: linux-lts-trusty: not split but trusty linux is leading to upgrade issues
** Changed in: linux-lts-trusty (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1492466 Title: linux-lts-trusty: not split but trusty linux is leading to upgrade issues Status in linux-lts-trusty package in Ubuntu: Triaged Status in linux-lts-trusty source package in Precise: Triaged Bug description: This leads to upgrade failures: Unpacking linux-image-extra-3.13.0-63-generic (3.13.0-63.103) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-3.13.0-63-generic_3.13.0-63.103_amd64.deb (--unpack): trying to overwrite '/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in package linux-image-3.13.0-63-generic 3.13.0-63.104~precise1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1492466/+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 1493839] Re: overlayfs: disabling V1 support leads to compile failure
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1493839 Title: overlayfs: disabling V1 support leads to compile failure Status in linux package in Ubuntu: Triaged Bug description: "CONFIG_OVERLAY_FS_V1 is not set": fs/overlayfs/super.c: In function 'ovl_init': fs/overlayfs/super.c:1213:30: error: 'ovl_v1_fs_type' undeclared (first use in this function) fs/overlayfs/super.c:1213:30: note: each undeclared identifier is reported only once for each function it appears in fs/overlayfs/super.c: In function 'ovl_exit': fs/overlayfs/super.c:1226:26: error: 'ovl_v1_fs_type' undeclared (first use in this function) scripts/Makefile.build:258: recipe for target 'fs/overlayfs/super.o' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493839/+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 1494943] Re: module signing can fail if the module identifier starts with a zero byte
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1494943 Title: module signing can fail if the module identifier starts with a zero byte Status in linux package in Ubuntu: In Progress Bug description: module signing can fail if the module identifier starts with a 0. This occurs randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494943/+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 1262516] Re: [Dell Latitude E5440] System will wake itself up on the first suspend after boot
Po-Hsu Lin, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1262516 Otherwise, please mark this as Invalid. ** Tags added: bios-outdated-a13 ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Changed in: linux (Ubuntu) Assignee: Jesse Sung (wenchien) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1262516 Title: [Dell Latitude E5440] System will wake itself up on the first suspend after boot Status in linux package in Ubuntu: Incomplete Bug description: CID: 201307-14032 Dell Latitude E5540 This system will wake itself up on the first suspend after boot. Steps: 1. Install 12.04.3 + update (3.8.0-43), boot to desktop 2. Suspend it by the "Suspend" option in system menu 3. Wake it up by pressing the power button Expected result: * System can be suspended / resumed successfully. Actual result: * System will wake itself up immediately after it's suspended. But if you try it again, there is no such problem. Please find "autoresume.dmesg" for dmesg output when this happens "suspendok.dmesg" is the dmesg output that the system didn't wake itself Compare these two file, an unique message could be found in autoresume.dmesg [ 69.057421] Broke affinity for irq 21 Maybe this has something to do with this issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-34-generic 3.8.0-34.49~precise1 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-34-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1976 F pulseaudio /dev/snd/controlC0: u 1976 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf7434000 irq 62' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 21 Simple ctrls : 3 Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xf743 irq 63' Mixer name : 'Realtek ALC292' Components : 'HDA:10ec0292,102805e0,0011' Controls : 23 Simple ctrls : 10 Date: Thu Dec 19 13:57:48 2013 HibernationDevice: RESUME=UUID=a97e3b8e-341d-4526-a2a7-99ab56c4b0fb InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Dell Inc. Latitude E5540 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=f68f708d-35d2-44d2-afd8-f6ff8bad692c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-34-generic N/A linux-backports-modules-3.8.0-34-generic N/A linux-firmware1.79.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 01389M dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd09/19/2013:svnDellInc.:pnLatitudeE5540:pvr01:rvnDellInc.:rn01389M:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1262516/+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 1255014] Re: [Lenovo V480] Unable to control the brightness from Max - Min
** Tags added: latest-bios-1.16 ** Package changed: linux-lts-raring (Ubuntu) => linux-lts-trusty (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1255014 Title: [Lenovo V480] Unable to control the brightness from Max - Min Status in linux-lts-trusty package in Ubuntu: Triaged Bug description: CID: 201204-10924 Lenovo V480 With the Brightness applet, the brightness level on this system cannot be adjusted from Max (let's say, level 11) to Min (level 1). The brightness level will goes down and up, which behaves like 11-10-9-8-7-6-5-4-3-4-5 Steps: 1. Install 12.04.3 + update (3.8.0-33), boot to desktop 2. Adjust the screen brightness by the Brightness and Lock applet, clicking the leftmost part of the scroll bar to change the brightness stepwise 3. Click and drag the slider to adjust the brightness Expected result: - Brightness could be adjusted smoothly. Actual result: 1. Brightness cannot go down to the lowest level, it behaves like 11-10-9-8-7-6-5-4-3-4-5 2. When you drag and move the slider, the backlight will flash between Max and the indicated level. Debugging information: $ ls /sys/class/backlight acpi_video0@ intel_backlight@ $ dmesg | grep 'ACPI: Video' [7.104361] ACPI: Video Device [PEGP] (multi-head: no rom: yes post: no) [7.107524] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) $ cat /proc/version Linux version 3.8.0-33-generic (buildd@toyol) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #48~precise1-Ubuntu SMP Thu Oct 24 16:28:06 UTC 2013 Note: the hotkey is probably affected by bug 1248442, but it will cause the same result when it's working. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1776 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf361 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa5002,00100202 HDA:80862806,80860101,0010' Controls : 29 Simple ctrls : 11 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Nov 26 01:10:44 2013 HibernationDevice: RESUME=UUID=0a4cd402-c938-4cc7-a55d-6230c539e25d InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 814TD01 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=6a396d09-0ad3-41a0-9d7d-18446b177e9d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.79.7 SourcePackage: linux-lts-raring StagingDrivers: keucr UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET73WW(1.16) dmi.board.asset.tag: Not Available dmi.board.name: 814TD01 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET73WW(1.16):bd04/10/2013:svnLENOVO:pn814TD01:pvrLenovoV480:rvnLENOVO:rn814TD01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814TD01 dmi.product.version: Lenovo V480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1255014/+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 1257381] Re: kernel panic -not syncing:VFS:unable to mount root fs on unkown-block(0, 0)
shiv, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1257381 Otherwise, please mark this as Invalid. ** Changed in: linux-lts-raring (Ubuntu) Importance: Undecided => Low ** Changed in: linux-lts-raring (Ubuntu) Status: Confirmed => Incomplete ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1257381 Title: kernel panic -not syncing:VFS:unable to mount root fs on unkown- block(0,0) Status in linux package in Ubuntu: Incomplete Bug description: [0.742262] kernel panic-not syncing VFS :UNABLE TO MOUNT root FSo unknown-block(0,0) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-31-generic 3.8.0-31.46~precise1 ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-31-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shiv 2130 F pulseaudio /dev/snd/controlC0: shiv 2130 F pulseaudio /dev/snd/pcmC0D0p: shiv 2130 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 46' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,104d6800,00100202' Controls : 23 Simple ctrls : 11 Card1.Amixer.info: Card hw:1 'Generic'/'HD-Audio Generic at 0xf7e4 irq 48' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,104d6800,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Dec 3 22:40:47 2013 HibernationDevice: RESUME=UUID=3c1eb018-4529-4a7f-a073-afe8a6aa28ad MachineType: Sony Corporation SVE14125CNB MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=7893b2db-eacd-4692-ba5b-5aeec0483d36 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.79.7 SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0140D7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0140D7:bd08/30/2012:svnSonyCorporation:pnSVE14125CNB:pvrC60B2W7X:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVE14125CNB dmi.product.version: C60B2W7X dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257381/+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 1255482] Re: [Lenovo V480] Unable to suspend by closing the lid with NVIDIA proprietary driver
** No longer affects: linux-lts-raring (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1255482 Title: [Lenovo V480] Unable to suspend by closing the lid with NVIDIA proprietary driver Status in linux-lts-raring source package in Saucy: Fix Released Bug description: CID: 201204-10924 Lenovo V480 Steps: 1. Install 12.04.3 + update (3.8.0-33), boot to desktop 2. Install the proprietary video driver (nvidia-319-updates) 3. Suspend it by closing the lid Expected result: - System could be suspended. Actual result: - The system was not suspended, the display will be turned off, but when you open the lid again, it behaves like nothing happened before. Error message could be found in dmesg: [ 542.875134] thinkpad_acpi: unhandled HKEY event 0x60a0 It looks like it's the same thing that Hui Wang found in comment #19 of bug 1089105 And this laptop could be suspended / resumed normally by using the "Suspend" option in the system menu. Along with bug 1255468, this bug will make both of these two suspend related bugs (w/, w/o proprietary driver) become blockers. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf361 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa5002,00100202 HDA:80862806,80860101,0010' Controls : 29 Simple ctrls : 11 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Wed Nov 27 05:22:57 2013 HibernationDevice: RESUME=UUID=0a4cd402-c938-4cc7-a55d-6230c539e25d InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 814TD01 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=6a396d09-0ad3-41a0-9d7d-18446b177e9d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.79.7 SourcePackage: linux-lts-raring StagingDrivers: keucr UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET73WW(1.16) dmi.board.asset.tag: Not Available dmi.board.name: 814TD01 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET73WW(1.16):bd04/10/2013:svnLENOVO:pn814TD01:pvrLenovoV480:rvnLENOVO:rn814TD01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814TD01 dmi.product.version: Lenovo V480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/saucy/+source/linux-lts-raring/+bug/1255482/+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 1263863] Re: [HP Pavilion 14] Multiple HIGH/CRITICAL failures found in fwts report
Po-Hsu Lin, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1210373 Also, could you please provide the full computer model and serial as noted on the sticker of the computer itself (not from the Bug Description)? Otherwise, please mark this as Invalid. ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Assignee: Ivan Hu (ivan.hu) => (unassigned) -- 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/1263863 Title: [HP Pavilion 14] Multiple HIGH/CRITICAL failures found in fwts report Status in linux package in Ubuntu: Incomplete Bug description: CID: 201303-13115 HP Pavilion 14 Critical failures: 2 klog: CRITICAL Kernel message: [5.345517] ACPI Exception: AE_NOT_FOUND, Evaluating _PRT [AE_NOT_FOUND] (20121018/pci_irq-269) klog: CRITICAL Kernel message: [5.722860] [Firmware Bug]: Invalid critical threshold (0) High failures: 5 klog: HIGH Kernel message: [5.311964] \_SB_.PCI0:_OSC invalid UUID klog: HIGH Kernel message: [5.345505] ACPI Error: [AR02] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) klog: HIGH Kernel message: [5.345510] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0._PRT] (Node 8801591fed70), AE_NOT_FOUND (20121018/psparse-537) klog: HIGH Kernel message: [ 13.551401] ACPI Error: [\_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359) klog: HIGH Kernel message: [ 13.551407] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG0.PEGP.DD02._BCL] (Node 880159209cd0), AE_NOT_FOUND (20121018/psparse-537) Error message: klog: HIGH Kernel message: [5.311964] \_SB_.PCI0:_OSC invalid UUID has been answered in bug 1219669 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-34-generic 3.8.0-34.49~precise1 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-34-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC282 Analog [ALC282 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1771 F pulseaudio /dev/snd/controlC0: ubuntu 1771 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xc361 irq 49' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xc3614000 irq 50' Mixer name : 'Realtek ALC282' Components : 'HDA:10ec0282,103c1974,0013' Controls : 20 Simple ctrls : 9 Date: Tue Dec 24 01:47:47 2013 HibernationDevice: RESUME=UUID=2b1037ae-50de-4c0c-8924-b3d0ec4aa1d3 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=9f17ab75-d20e-45c7-a266-3dd0cdd4e0d0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-34-generic N/A linux-backports-modules-3.8.0-34-generic N/A linux-firmware1.79.9 RfKill: SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1974 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.19 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1265110] Re: [HP Pavilion 15] Wireless key is not working
Po-Hsu Lin, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1265110 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265110 Title: [HP Pavilion 15] Wireless key is not working Status in linux package in Ubuntu: Incomplete Bug description: CID: 201307-13902 HP Pavilion 15 The wireless key is not working on this system Steps: 1. Install 12.04.3 + update (3.8.0-34) 2. Press the wireless key to see if it can turn on/off the wireless connection Expected result: * Wireless key shold work properly Actual result: * Wireless key not responding, however, the wireless still can be disabled by using the NetworkManager Debugging information: "showkey" command - key press events were not detected "xev" command - key press events were not detected "acpi_listen" - key press events were not detected ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-34-generic 3.8.0-34.49~precise1 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-34-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: Generic_1 [HD-Audio Generic], device 0: ALC282 Analog [ALC282 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1764 F pulseaudio /dev/snd/controlC0: ubuntu 1764 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xf034 irq 80' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100500' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0344000 irq 81' Mixer name : 'Realtek ALC282' Components : 'HDA:10ec0282,103c216f,0013' Controls : 20 Simple ctrls : 9 Date: Tue Dec 31 10:37:28 2013 HibernationDevice: RESUME=UUID=0653ac45-af83-4721-a85f-456bb73e61eb InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=16cb3b7b-0655-4a92-99e7-6c865bbe60fa ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-34-generic N/A linux-backports-modules-3.8.0-34-generic N/A linux-firmware1.79.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.0C dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 216F dmi.board.vendor: Hewlett-Packard dmi.board.version: 31.0E dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.0C:bd07/12/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr088D1200591620100:rvnHewlett-Packard:rn216F:rvr31.0E:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 088D1200591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265110/+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 1493814] Re: [Acer Travelmate B115-M] Synaptic touchpad
System is unstable with 3.13.0-rc8. It doesn't boot or if it boots blank screen after some seconds. Some weeks ago I migrated from 3.13 branch to 3.19 branch (lts-vivid) just because I had problems with 3.13 branch. https://wiki.ubuntu.com/Kernel/LTSEnablementStack -- 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/1493814 Title: [Acer Travelmate B115-M] Synaptic touchpad Status in linux package in Ubuntu: Incomplete Bug description: Touchpad has issues working. WORKAROUND: Set in BIOS Touchpad option from Advanced to Basic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.28~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Sep 9 13:13:40 2015 InstallationDate: Installed on 2014-09-16 (357 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuari 1911 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=6a63f422-0d53-4459-873d-c925133fdbec InstallationDate: Installed on 2014-09-16 (357 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer TravelMate B115-M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=681882b9-fe81-482e-a240-d2ee75144228 ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.19.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd04/11/2014:svnAcer:pnTravelMateB115-M:pvrV1.04:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: TravelMate B115-M dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493814/+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 1501345] Re: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication
Problem occured also when using Qt's QSerialPort. QSerialPort::waitforReadyRead() returns true, bute QSerialPort::readAll() returns no data. Downgrading kernel version to 3.13.0-63 'fixed' the problem. Gr. Henk - Qt 5.5.0 Linux henklaak-desktop 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1501345 Title: linux-image-3.13.0-65-generic 3.13.0-65 breaks Python based Serial communication Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Today after updating to the linux-image-3.13.0-65-generic 3.13.0-65 Kernel on Lubuntu 14.04.3 LTS two different programs that rely on PySerial quit working. miniterm.py and my ROS (Robot Operating System) based Python node quit working. When rebooted and selected 3.13.0-63-generic via GRUB everything worked again. Here are the steps to create the issue with miniterm.py, note that you need something connected via a USB to Serial adapter for this to work. I am working with a Parallax Activity Board, but an Arduino should also exhibit the same behavior. sudo apt install linux-image-3.13.0-65-generic sudo apt install linux-image-extra-3.13.0-65-generic reboot $ miniterm.py /dev/ttyUSB0 115200 --- Miniterm on /dev/ttyUSB0: 115200,8,N,1 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- --- exit --- Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/usr/bin/miniterm.py", line 220, in reader data = character(self.serial.read(1)) File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in read raise SerialException('device reports readiness to read but returned no data (device disconnected?)') SerialException: device reports readiness to read but returned no data (device disconnected?) Reverting to the 3.13.0-63 kernel allows miniterm.py and other Python Serial based programs to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+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 1490267] Re: Regression in overlayfs
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1490267 Title: Regression in overlayfs Status in linux package in Ubuntu: Confirmed Bug description: When installing the linux-lts-vivid kernel in Ubuntu 14.04, there is a regression with overlayfs and unprivileged containers: 'failed to whiteout' Below the system information: - Kernel error: http://pastebin.com/iajXHbHZ - Kernel version: 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux - Executed LXC command: lxc-clone -s -B overlayfs orig test (both unprivileged containers) - LXC version: 1.0.7 We discussed this on the LXC user mailing list, and this is likely a bug in one of the patches that add support for unprivileged use of overlayfs. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 13:56 seq crw-rw 1 root audio 116, 33 Aug 30 13:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-fceee9e1 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-central-1b Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb 1 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=dde0e30e-be54-43dc-9a44-5769353c2e27 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory StagingDrivers: visorutil Tags: trusty ec2-images staging Uname: Linux 3.19.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267/+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 1423796] Re: Unable to mount lvmcache root device at boot time
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+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 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1423343 Title: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Bug description: Following patches are missing from ubuntu vivid 15.04 compared to latest upstream (linux-next) , please include them in ubuntu vivid , all the patches listed here are already upstream . /arch/x86/include/uapi/asm/hyperv.h 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1 /drivers/hv/hyperv_vmbus.h 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2 drivers/hv/vmbus_drv.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac 5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945 6. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c /drivers/hv/hv_snapshot.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6 /drivers/hv/hv_kvp.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4 /drivers/hv/hv_fcopy.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed /drivers/hv/channel.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314 /drivers/hv/channel_mgmt.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64 5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7 /drivers/hv/hv_balloon.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8 /tools/hv/hv_vss_daemon.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd /tools/hv/hv_fcopy_daemon.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c1136da62170465920eea1ae9ba9ce2234091f77 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aba474b8185d60ca8cdbf3049fe6d655aa761e23 /drivers/net/hyperv/netvsc.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=da19fcd0d85f36420f578fe6dfe7a2a581b4fa6e 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d953ca4ddf71aa91a4596b2ff7ff1598f6ad4708 3.
[Kernel-packages] [Bug 1438651] Re: devel: consider shortening package name (only) to remove the .0
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1438651 Title: devel: consider shortening package name (only) to remove the .0 Status in linux package in Ubuntu: Triaged Bug description: We get a lot of confused people about why we have .0 in the package names and package versions. Consider ripping it out of the package version and replacing that .0 with the real version in the package. Less confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438651/+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 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+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 1478609] Re: overlayfs: port v1 support to v4.2
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1478609 Title: overlayfs: port v1 support to v4.2 Status in linux package in Ubuntu: Fix Committed Bug description: Need to port overlayfs v1 support to v4.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478609/+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 1479394] Re: aufs: update for mainline v4.2
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1479394 Title: aufs: update for mainline v4.2 Status in linux package in Ubuntu: Fix Committed Bug description: Need to look at porting aufs4 for v4.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479394/+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 1489516] Re: trusty: update linux-*-hwe-* packages to point to vivid at the 14.04.3 point release
** Changed in: linux-meta (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.10 -- 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/1489516 Title: trusty: update linux-*-hwe-* packages to point to vivid at the 14.04.3 point release Status in linux-meta package in Ubuntu: Triaged Bug description: When the 14.04.3 point release goes out we want to move to the *-hwe-* variants to vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1489516/+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 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+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 1483325] Re: mount -t overlayfs misinforms when nonexisting directories are provided
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1483325 Title: mount -t overlayfs misinforms when nonexisting directories are provided Status in linux package in Ubuntu: Confirmed Bug description: Consider the directory structure like this: root@MIKE /tmp/ofs> ls -al total 20 drwxr-xr-x 5 root root 4096 Aug 10 18:09 . drwxrwxrwt 9 root root 4096 Aug 10 18:09 .. drwxr-xr-x 2 root root 4096 Aug 10 18:09 lower drwxr-xr-x 2 root root 4096 Aug 10 18:09 mounting drwxr-xr-x 2 root root 4096 Aug 10 18:09 upper Mounting upper over lower on mounting mount point works just fine: root@MIKE /tmp/ofs> mount -t overlayfs myoverlay -o lowerdir=lower,upperdir=upper mounting/ root@MIKE /tmp/ofs> df -Th mounting/ Filesystem Type Size Used Avail Use% Mounted on myoverlay overlayfs 219G 94G 114G 46% /tmp/ofs/mounting root@MIKE /tmp/ofs> However if the directory name is misspelled (that is, we're providing wrong directory), the error message is misleading: 32 root@MIKE /tmp/ofs> mount -t overlayfs myoverlay -o lowerdir=IAMWRONG,upperdir=upper mounting/ mount: special device myoverlay does not exist I'm running this on Ubuntu 14.04.3 LTS, using 3.13.0-61-generic kernel. I'm not sure if this fits under 'linux' package, but I can't seem to be able to find 'mount' package in Launchpad. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mario 2458 F pulseaudio /dev/snd/controlC0: mario 2458 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=fa8de8e9-450d-4a2e-8ca6-fa542a0352e3 InstallationDate: Installed on 2014-12-16 (236 days ago) InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014) MachineType: LENOVO 42405XG NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=a3231802-c7ff-406a-9aca-83a4bb0c7d70 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.14 Tags: trusty Uname: Linux 3.13.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse libvirtd lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 42405XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn42405XG:pvrThinkPadT520:rvnLENOVO:rn42405XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42405XG dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483325/+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 1250109] Re: Please use dpkg-triggers
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1250109 Title: Please use dpkg-triggers Status in grub2 package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: Currently the kernel package runs update-grub every time one is installed or removed. This results in it being run a dozen times during a dist-upgrade, and this is rather time consuming and annoying. Please use a dpkg trigger to cause update-grub to be run only once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+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 1419446] Re: devel: overlayfs -- investigate multilayer r/o support
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1419446 Title: devel: overlayfs -- investigate multilayer r/o support Status in linux package in Ubuntu: Confirmed Bug description: Need to evaluate the multilayer read only support for overlayfs, we may need this in vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1419446/+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 1328583] Re: linux-tools upgrade fails
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1328583 Title: linux-tools upgrade fails Status in linux package in Ubuntu: Triaged Bug description: Errors while upgrading a server from Precise to Trusty: Unpacking linux-tools-3.13.0-27 (3.13.0-27.50) ... dpkg: error processing archive /var/cache/apt/archives/linux-tools-3.13.0-27_3.13.0-27.50_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.3.13.0-27', which is also in package linux-lts-trusty-tools-3.13.0-27 3.13.0-27.50~precise1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../linux-tools-3.13.0-27-generic_3.13.0-27.50_amd64.deb ... Unpacking linux-tools-3.13.0-27-generic (3.13.0-27.50) over (3.13.0-27.50~precise1) ... Processing triggers for man-db (2.6.1-2ubuntu1) ... Errors were encountered while processing: /var/cache/apt/archives/linux-tools-3.13.0-27_3.13.0-27.50_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328583/+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 1413664] Re: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.09 => ubuntu-15.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/1413664 Title: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files Status in linux package in Ubuntu: Confirmed Bug description: There is a new more efficient debug format enabled via CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need packaging in the .ddeb before we can enable this. Evaluate whether the other tooling we have will handle it before doing so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413664/+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 1475914] Re: login freezes or black screen with kernel higher than 3.19.0-15
Krzysztof Burliński, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475914 Title: login freezes or black screen with kernel higher than 3.19.0-15 Status in linux package in Ubuntu: Incomplete Bug description: Env : Linux 3.19.0-22-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] using xorg default driver (not the proprietary) Facts : - On the login page, just after the boot, the system is freezed (or looping) - I can't open a terminal with Ctrl+Alt+F1 - When I choose a previous kernel version from Grub, the problem occurs with all versions I had installed since 3.19.0-16 3.19.0-15 OK 3.19.0-16 KO 3.19.0-18 KO 3.19.0-20 KO 3.19.0-21 KO 3.19.0-22 KO - When I choose the recovery mode of the version that have the problem, the recovery menu freezes also (see attachment) - I've done a clean install on a new disk and after the update of the kernel (3.19.0-15 -> 3.19.0-22) I have a black screen after the boot (no login screen). And I have the same problem trying the recovery mode with version 3.19.0-22. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pierre 3474 F pulseaudio /dev/snd/controlC1: pierre 3474 F pulseaudio CRDA: country AM: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 18), (N/A) (5250 - 5330 @ 80), (N/A, 18), (0 ms), DFS CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=230b9245-44d0-4fc5-8440-be65b66292a9 InstallationDate: Installed on 2015-07-07 (81 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: MSI MS-7640 NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=fc6a9894-1b64-48bd-91ad-f545051a1773 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V19.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-GD65 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV19.9:bd10/08/2012:svnMSI:pnMS-7640:pvr3.0:rvnMSI:rn990FXA-GD65(MS-7640):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7640 dmi.product.version: 3.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475914/+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 1502055] Re: Crypt password screen not responding
Mark Adams, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1234594] Re: Unable to do network boot with Atheros AR8162 [1969:1090] AR8161[1969:1091] Ethernet controller
Po-Hsu Lin, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux-lts- raring/+bug/1234594/comments/2 regarding this being fixed with an update, and linux-lts-raring is EOL. ** Changed in: linux-lts-raring (Ubuntu) Status: Triaged => Invalid ** Changed in: linux-lts-raring (Ubuntu) Assignee: Jesse Sung (wenchien) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1234594 Title: Unable to do network boot with Atheros AR8162 [1969:1090] AR8161[1969:1091] Ethernet controller Status in linux-lts-raring package in Ubuntu: Invalid Bug description: CID: 201202-10508 Dell Inspiron 5420 This issue was found in 12.04.2, cause by the lack of alx driver. (bug 927782) For 12.04.3 stock image, the Ethernet works fine when installed by USB. It works fine with LiveUSB as well. However, it's unable to boot from Internet, kernel panic will occur. Here is the last thing that I can read from the screen: Begin: Loading essential drivers ... [5.506492] Btrfs loaded [5.510499] xor: automatically using best checksumming function: [5.546543]avx : 18213.000 MB/sec [5.546992] device-mapper: dm-raid45: initialized v0.2594b done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... [5.802369] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [6.302349] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0200 [6.302349] [6.302391] drm_kms_helper: panic occurred, switching back to text console I think AR8161 is affected too. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified: boot/vmlinuz-3.8.0-29-generic] ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-generic. ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1687 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x9061 irq 44' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:14f1506e,1028055d,0012 HDA:80862806,80860101,0010' Controls : 29 Simple ctrls : 11 CurrentDmesg: [ 45.399772] type=1400 audit(1380789162.280:31): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/usr/share/gvfs/remote-volume-monitors/" pid=1870 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 176.951824] alx :02:00.0 eth0: NIC Link Down [ 178.544219] alx :02:00.0 eth0: NIC Link Up: 100 Mbps Full Date: Thu Oct 3 16:39:19 2013 HibernationDevice: RESUME=UUID=a666e576-505e-4243-b829-4c7eaf019d98 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Dell Inc. Inspiron 5420 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=f54f0c0f-85ae-4050-9827-84fa151334d7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.79.6 SourcePackage: linux-lts-raring StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X52 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrX52:bd06/20/2012:svnDellInc.:pnInspiron5420:pvr:rvnDellInc.:rn:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 5420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1234594/+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 1248865] Re: [HP Paviliion dm1] [\_SB_.ACAD._PSR] [AE_ALREADY_EXISTS] ACPI Error message in kernel log after suspend resume
Taihsiang Ho, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1248865 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Assignee: Ivan Hu (ivan.hu) => (unassigned) -- 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/1248865 Title: [HP Paviliion dm1] [\_SB_.ACAD._PSR] [AE_ALREADY_EXISTS] ACPI Error message in kernel log after suspend resume Status in linux package in Ubuntu: Incomplete Bug description: Hardware: HP Paviliion dm1 (CID 201209-11793) System: ubuntu 12.04.3 Nov 7 02:33:57 201209-11793 kernel: [ 2788.356670] ACPI Error: [SSZE] Namespace lookup failure, AE_ALREADY_EXISTS (20121018/dsfield-211) Nov 7 02:33:57 201209-11793 kernel: [ 2788.356683] ACPI Error: Method parse/execution failed [\_SB_.ACAD._PSR] (Node 8800635dd758), AE_ALREADY_EXISTS (20121018/psparse-537) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-32-generic 3.8.0-32.47~precise1 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: Generic_1 [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1684 F pulseaudio /dev/snd/controlC0: ubuntu 1684 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0x90344000 irq 45' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0x9034 irq 46' Mixer name : 'IDT 92HD87B2/4' Components : 'HDA:111d76d9,103c18d4,00100107' Controls : 20 Simple ctrls : 10 Date: Thu Nov 7 03:20:39 2013 HibernationDevice: RESUME=UUID=c1796212-cc7e-43dc-af80-daed5a888443 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=UUID=f7ecd215-187c-4d9b-b3c5-8a5e159627d8 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-32-generic N/A linux-backports-modules-3.8.0-32-generic N/A linux-firmware1.79.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 18D4 dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr08901300462520100:rvnHewlett-Packard:rn18D4:rvr76.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm1 Notebook PC dmi.product.version: 08901300462520100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248865/+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 1243580] Re: [Lenovo Thinkpad Edge E525] Accelerometer was not detected
Po-Hsu Lin, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1243580 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243580 Title: [Lenovo Thinkpad Edge E525] Accelerometer was not detected Status in linux package in Ubuntu: Incomplete Bug description: CID: 201107-8258 Lenovo Thinkpad Edge E525 According to the maintenance manual from Lenovo[0], there is an accelerometer on the system board. But it seems that it was not detected at all (cannot be found in lspci). No HDAPS directory in /sys/devices/platform I do verified with the PC-DOCTOR v.2.0.1857 for E525 from Lenovo, but there is no such "ThinkPad Devices" category in "Diagnostics" as stated in the maintenance manual. So on the other hand, there is no clue that if this system DOES comes with an accelerometer or not. [0] http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/0a60536_02.pdf ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified: boot/vmlinuz-3.8.0-29-generic] ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-generic. ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1627 F pulseaudio /dev/snd/controlC0: ubuntu 1627 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xf0b44000 irq 47' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0b4 irq 16' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa21ea,0010' Controls : 22 Simple ctrls : 10 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Oct 22 23:35:33 2013 HibernationDevice: RESUME=UUID=f746ff69-0a94-4753-8729-e754d0d71a4c InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 120024U MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=5da29fe5-c880-4e79-9e8d-4420e3b1afe4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.79.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8IET33WW(1.06) dmi.board.asset.tag: Not Available dmi.board.name: 120024U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8IET33WW(1.06):bd07/14/2011:svnLENOVO:pn120024U:pvrThinkPadE525:rvnLENOVO:rn120024U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 120024U dmi.product.version: ThinkPad E525 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1235109] Re: [HP ENVY 4 Sleekbook] FWTS reports several high failures on this system
Taihsiang Ho, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1235109 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235109 Title: [HP ENVY 4 Sleekbook] FWTS reports several high failures on this system Status in linux package in Ubuntu: Incomplete Bug description: CID 201209-11790 HP ENVY 4 Sleekbook (12.04.3 / 3.8.0-29-generic) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified: boot/vmlinuz-3.8.0-29-generic] ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-generic. ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1736 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x5071 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:111d76e0,103c1894,00100102 HDA:80862806,80860101,0010' Controls : 27 Simple ctrls : 11 Date: Fri Oct 4 03:16:19 2013 HibernationDevice: RESUME=UUID=8ef0d03c-328d-429a-93b6-1233c368a702 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4503488a-ba73-4244-bdc5-1642bfe46206 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.79.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde dmi.bios.version: B.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1894 dmi.board.vendor: Hewlett-Packard dmi.board.version: 72.66 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.38:bd10/31/2012:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr088810250E102:rvnHewlett-Packard:rn1894:rvr72.66:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm4 Notebook PC dmi.product.version: 088810250E102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235109/+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 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box
Hello! I still have problems with both kuba-moo and neurobin drivers. I have an Asus x555la laptop running ubuntu-gnome 15.04. The installation was fine and and connection worked, but: -the divers don't load at startup. -the system crashes when I disconnect from a network, so to disconnect without problems I have to switch of the router... Any idea to fix this? Thank you in advance! -- 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/1220146 Title: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box Status in HWE Next: Confirmed Status in HWE Next trusty series: Confirmed Status in Linux: Unknown Status in vivid: New Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! The driver that upstream is working on can be found at https://github.com/lwfinger/mt7630. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+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 1475914] Re: login freezes or black screen with kernel higher than 3.19.0-15
I experience the same problem, but with integrated graphics card - Intel HD 4600, ubuntu 15.04 64 bit For me, it helps when in boot selection I pick the option of booting with Upstart. Otherwise, it is black screen 100% time, no matter if I change kernel or not. Windows starts without problem from the same GRUB. -- 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/1475914 Title: login freezes or black screen with kernel higher than 3.19.0-15 Status in linux package in Ubuntu: Incomplete Bug description: Env : Linux 3.19.0-22-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] using xorg default driver (not the proprietary) Facts : - On the login page, just after the boot, the system is freezed (or looping) - I can't open a terminal with Ctrl+Alt+F1 - When I choose a previous kernel version from Grub, the problem occurs with all versions I had installed since 3.19.0-16 3.19.0-15 OK 3.19.0-16 KO 3.19.0-18 KO 3.19.0-20 KO 3.19.0-21 KO 3.19.0-22 KO - When I choose the recovery mode of the version that have the problem, the recovery menu freezes also (see attachment) - I've done a clean install on a new disk and after the update of the kernel (3.19.0-15 -> 3.19.0-22) I have a black screen after the boot (no login screen). And I have the same problem trying the recovery mode with version 3.19.0-22. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pierre 3474 F pulseaudio /dev/snd/controlC1: pierre 3474 F pulseaudio CRDA: country AM: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 18), (N/A) (5250 - 5330 @ 80), (N/A, 18), (0 ms), DFS CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=230b9245-44d0-4fc5-8440-be65b66292a9 InstallationDate: Installed on 2015-07-07 (81 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: MSI MS-7640 NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=fc6a9894-1b64-48bd-91ad-f545051a1773 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V19.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-GD65 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV19.9:bd10/08/2012:svnMSI:pnMS-7640:pvr3.0:rvnMSI:rn990FXA-GD65(MS-7640):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7640 dmi.product.version: 3.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475914/+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 1399064] Re: bridges cannot have a mtu > 1500 by themselves
I am wondering if there has been any progress on this, and if a bug report has been opened to the kernel devs. This is impacting kvm deployments, and while there are workarounds, they are all rather ugly (read: scripts that adjust tun MTUs after VMs boot). -- 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/1399064 Title: bridges cannot have a mtu > 1500 by themselves Status in linux package in Ubuntu: Triaged Bug description: A linux bridge always adopts the smallest MTU of the enslaved devices. When no device are enslaved, it defaults to a MTU of 1500 and refuses to use a larger one. This is problematic when using bridges enslaving only virtual NICs (vnetX) like it's common with KVM guests. Steps to reproduce the problem 1) sudo ip link add br-test0 type bridge # create an empty bridge 2) sudo ip link set br-test0 mtu 9000# attempt to set MTU > 1500 3) ip link show dev br-test0 # confirm MTU Here, 2) returns "RTNETLINK answers: Invalid argument". One (cumbersome) way around this is: 4) sudo modprobe dummy 5) sudo ip link set dummy0 mtu 9000 master br-test0 Then the bridge's MTU can be changed from anywhere to 9000. This bug is especially annoying for the virtualization case because the KVM's tap driver will by default adopt the bridge's MTU on startup making it impossible (without the workaround) to use a large MTU on the guest VMs. Additional information: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy linux-image-3.13.0-41-generic iproute2 linux-image-3.13.0-41-generic: Installed: 3.13.0-41.70 Candidate: 3.13.0-41.70 Version table: *** 3.13.0-41.70 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status iproute2: Installed: 3.12.0-2 Candidate: 3.12.0-2 Version table: *** 3.12.0-2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-41-generic 3.13.0-41.70 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 4594 F pulseaudio CurrentDesktop: Unity CurrentDmesg: dmesg: klogctl failed: Operation not permitted Date: Wed Dec 3 23:02:25 2014 HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f InstallationDate: Installed on 2014-01-26 (311 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) MachineType: LENOVO 2516CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic root=/dev/mapper/crypt-root ro quiet splash cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 nmi_watchdog=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-41-generic N/A linux-backports-modules-3.13.0-41-generic N/A linux-firmware 1.127.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399064/+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 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting
Jan Rathmann, as per http://www.gigabyte.com/products/product- page.aspx?pid=2544#bios an update to your computer's buggy and outdated BIOS is available (F14). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450396 Title: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on- lan setting Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Bug description: Hello, using Suspend-to-RAM on my system has stopped working reliably on Vivid when booting with Systemd. When I try to suspend my PC the following happens: - PC turns off - PC unwantedly wakes up (turns on) by itself again. This time span until it turns on again can reach from a second (almost immediately) until two or three minutes. - In a few cases (<25%), the PC stays suspended properly. A way to workaround this problem is to boot my PC with Upstart instead of Systemd, then this problem never happens (and has never happened in any of the previous Ubuntu versions since 2008). Thus it seems to be a bug somehow related to Systemd. Other steps I have tried to solve the problem (without any success): - Checking BIOS settings, all options are set that way that the PC should never wake up by any event other than pressing the power button. - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device could cause wake up events. This lists my USB controller, but deactivating it (with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the problem. Also suspend while running Upstart works fine despite the USB controller listed as "enabled". In the system logs I could see no hint what causes the undesired wake- ups. Allthough there is one factor which seems to have a certain influence: If I close programs like Pidgin, Skype or Firefox that cause continuous network traffic, the chance is higher that my PC will stay suspened (while runinng Systemd). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 11:24:46 2015 InstallationDate: Installed on 2015-04-16 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450396/+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 1502055] Re: Crypt password screen not responding
Pascal Schwarz, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1223421] Re: [Lenovo S431, 531, S5]: Brightness keys to not function properly.
Jeff Marcom, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1223421 Otherwise, please mark this as Invalid. ** Tags added: bios-outdated-1.12 ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Assignee: Canonical Hardware Enablement Team (canonical-hwe-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1223421 Title: [Lenovo S431, 531, S5]: Brightness keys to not function properly. Status in linux package in Ubuntu: Incomplete Bug description: [Problem]: Pushing the brightness "down" key causes the brightess to immediately go to a value of 0 yet the actual brightness has not change on the screen. Pushing brightness "up" causes the brightness value to go up to around 5% and immediately sets the actual corresponding brightness level on the display. At this point pressing the brightness "up" or "down" keys causes the brightness slider to jump between 0 and 5% but will not go any higher value setting. You have to open gnome-control-center "brightness and lock" to reset the brightness to desired value. This particular bug is present on a few recent lenovos models. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified: boot/vmlinuz-3.8.0-29-generic] ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Tue Sep 10 11:45:00 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-generic. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1563 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xe281 irq 48' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa0001,00100203 HDA:80862806,80860101,0010' Controls : 36 Simple ctrls : 12 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=fbd820f1-0c28-488a-b1a5-90e425ff897e InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 20AX25C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=5cea22e2-4925-4f99-8469-1af7456106b3 ro quiet splash initcall_debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.79.6 Tags: precise running-unity Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 03/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: HFET25WW (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AX25C dmi.board.vendor: LENOVO dmi.board.version: Win8 STD PRC DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHFET25WW(1.02):bd03/26/2013:svnLENOVO:pn20AX25C:pvrThinkPadS3-S431:rvnLENOVO:rn20AX25C:rvrWin8STDPRCDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
[Kernel-packages] [Bug 1253942] Re: [Dell Inspiron 3737] Multiple CRITICAL failures found in fwts method test
Po-Hsu Lin, thank you for reporting this bug to Ubuntu. linux-lts-raring reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1253942 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Assignee: Ivan Hu (ivan.hu) => (unassigned) -- 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/1253942 Title: [Dell Inspiron 3737] Multiple CRITICAL failures found in fwts method test Status in linux package in Ubuntu: Incomplete Bug description: CID: 201305-13639 Dell Inspiron 3737 Steps: 1. Install 12.04.3 + update (3.8.0-33) 2. Boot to desktop, run fwts method test There are many CRITICAL failures reported by fwts when running the method test. Critical failures: 81 method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS01._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS02._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS03._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS04._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS05._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS06._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS07._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS08._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS09._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS11._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS12._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS13._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS14._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS15._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP1._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP2._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP3._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP4._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP5._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP6._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.PDRC._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKA._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKB._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKC._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKD._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKE._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKF._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKG._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKH._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKA._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKB._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKC._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKD._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKE._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKF._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKG._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKH._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.LPCB.LDR2._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS11._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS12._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS13._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS14._STA'. method: Detected error
[Kernel-packages] [Bug 1254957] Re: [HP Pavilion 15] Mute LED is not working
Po-Hsu Lin, could you please provide the full computer model and serial as noted on the sticker of the computer itself (not from the Bug Description)? ** Package changed: linux-lts-raring (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1254957 Title: [HP Pavilion 15] Mute LED is not working Status in linux package in Ubuntu: Incomplete Bug description: CID: 201306-13836 HP Pavilion 15 The mute button itself works fine. There is a small LED on the mute button, but the LED seems not working Steps: 1. Install 12.04.3 + update (3.8.0-33) and boot to desktop 2. Press the mute key (f6) Expected result: - When the system is muted, the LED should be lit. Actual result: System muted, but the LED still off. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC282 Analog [ALC282 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1683 F pulseaudio /dev/snd/pcmC1D0p: ubuntu 1683 F...m pulseaudio /dev/snd/controlC0: ubuntu 1683 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xb561 irq 61' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xb5614000 irq 62' Mixer name : 'Realtek ALC282' Components : 'HDA:10ec0282,103c2166,0013' Controls : 20 Simple ctrls : 9 Date: Mon Nov 25 22:11:52 2013 HibernationDevice: RESUME=UUID=afe330a3-e874-48bd-97f5-b267da69768f InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=6ab6df65-e406-4d7c-a1c4-71919e31a882 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.79.7 RfKill: SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.12:bd07/19/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr089E100620100:rvnHewlett-Packard:rn2166:rvr29.0B:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 089E100620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254957/+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 1502608] [NEW] package linux-image-extra-3.16.0-50-generic 3.16.0-50.66~14.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une err
Public bug reported: A broken not because of disk space ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.16.0-50-generic 3.16.0-50.66~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16 Uname: Linux 3.16.0-50-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Sun Oct 4 13:39:34 2015 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2015-05-09 (147 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: linux-lts-utopic Title: package linux-image-extra-3.16.0-50-generic 3.16.0-50.66~14.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1502608 Title: package linux-image-extra-3.16.0-50-generic 3.16.0-50.66~14.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in linux-lts-utopic package in Ubuntu: New Bug description: A broken not because of disk space ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.16.0-50-generic 3.16.0-50.66~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16 Uname: Linux 3.16.0-50-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Sun Oct 4 13:39:34 2015 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2015-05-09 (147 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: linux-lts-utopic Title: package linux-image-extra-3.16.0-50-generic 3.16.0-50.66~14.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1502608/+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 1502552] Re: touchpad not working
You need this driver: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=5V4HN -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1502552 Title: touchpad not working Status in linux-lts-raring package in Ubuntu: New Bug description: Touchpad is not responding. External mouse is working. The touchpad is not listed in xinput. External mouse is listed twice in xinput as well as in 'cat /proc/bus/input/devices' but touchpad driver isn't. What I expected to see in /proc/bus/input/devices file: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input8 U: Uniq= H: Handlers=mouse2 event8 B: EV=b B: KEY=420 0 7 0 0 0 0 0 0 0 0 B: ABS=1103 What I saw instead: I: Bus=0003 Vendor=046d Product=c07e Version=0111 N: Name="Logitech Gaming Mouse G402" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.0/input/input15 U: Uniq=6D9036795757 H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=143 B: MSC=10 I: Bus=0003 Vendor=046d Product=c07e Version=0111 N: Name="Logitech Gaming Mouse G402" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.1/input/input16 U: Uniq=6D9036795757 H: Handlers=sysrq kbd event6 B: PROP=0 B: EV=10001f B: KEY=4837fff072ff32d bf56 1 30f908b17c007 ffe77bfad941dfff febeffdfffef fffe B: REL=40 B: ABS=1 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-44-generic 3.8.0-44.66~precise1 ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25 Uname: Linux 3.8.0-44-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-44-generic. ApportVersion: 2.0.1-0ubuntu17.11 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sumit 2114 F pulseaudio /dev/snd/controlC0: sumit 2114 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf7a14000 irq 60' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xf7a1 irq 61' Mixer name : 'Realtek ALC255' Components : 'HDA:10ec0255,10280662,0012' Controls : 18 Simple ctrls : 8 Date: Sun Oct 4 10:01:29 2015 HibernationDevice: RESUME=UUID=45998e30-d2b6-4037-96ff-63f405f9832d InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Dell Inc. Vostro 3446 MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-44-generic root=UUID=8def0356-8cf9-4e71-829f-03a59b5d259f ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-44-generic N/A linux-backports-modules-3.8.0-44-generic N/A linux-firmware1.79.18 SourcePackage: linux-lts-raring StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1502552/+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 1268252] Re: Brightness settings stopped working after upgrade
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Rahul (rahulshantagiri) -- 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/1268252 Title: Brightness settings stopped working after upgrade Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, both the physical key and the brightness settings in the gnome-control centre have stopped working. Whatever level of brightness i decrease it to, it always stays on maximum. I'm able to reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 12 09:17:00 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2013-11-16 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago) --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krishnan 3070 F pulseaudio /dev/snd/controlC0: krishnan 3070 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c545b9da-fef4-4530-9051-29276dfd842c InstallationDate: Installed on 2013-11-16 (58 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO INVALID NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=0b897d24-0c02-4f57-9596-5fcd681c5ed0 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-2-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-06 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN12WW(V1.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.name: INVALID dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268252/+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 1268252] Re: Brightness settings stopped working after upgrade
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Rahul (rahulshantagiri) -- 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/1268252 Title: Brightness settings stopped working after upgrade Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, both the physical key and the brightness settings in the gnome-control centre have stopped working. Whatever level of brightness i decrease it to, it always stays on maximum. I'm able to reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 12 09:17:00 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2013-11-16 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago) --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krishnan 3070 F pulseaudio /dev/snd/controlC0: krishnan 3070 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c545b9da-fef4-4530-9051-29276dfd842c InstallationDate: Installed on 2013-11-16 (58 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO INVALID NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=0b897d24-0c02-4f57-9596-5fcd681c5ed0 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-2-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-06 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN12WW(V1.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.name: INVALID dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268252/+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 1421490] Re: Hyperthreading not always detected
Ken Sharp, thank you for reporting this bug to Ubuntu. linux-lts-saucy reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack However, while your statement on how your graphics card is not supported by the proprietary nvidia drivers in linux-lts-trusty was noticed, I'm not seeing evidence to this. As per nvidia's website, the latest version of the driver available for your card is 173.14.39. Also, this is available in both Precise with linux-lts-trusty and in Trusty itself as per https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173 . Hence, it would appear it is in fact supported, but wasn't working when you last tested it. I would recommend filing a bug report on the graphics card issue via: ubuntu-bug xorg Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Pivoting back to the scope of this report, would you be able to either downgrade your kernel to 3.2.x to maintain supportability and security updates, or upgrade to linux-lts-trusty+ so troubleshooting may continue on a supported release? As well, you may have already done this, but it wouldn't hurt to rule out a hardware issue by stress testing the CPU via https://help.ubuntu.com/community/Checkbox . ** Package changed: linux-lts-saucy (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: latest-bios-a07 ** Changed in: linux (Ubuntu) Importance: Low => Medium -- 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/1421490 Title: Hyperthreading not always detected Status in linux package in Ubuntu: Incomplete Bug description: From a cold boot (power off --> power on), this system doesn't always detect the presence of Hyperthreading on the processor. Note: warm reboot has very different problems so cannot be tested. It *usually* does, but on occasion for no obvious reason the system reports a single CPU (HT systems report two CPUs to increase performance). Despite all the articles claiming the opposite; this noticeably reduces performance of the system, especially in multi-threaded applications such as Google Chrome (in the case of Chrome the difference in response is considerable!) linux-lts-trusty is NOT an option as it is incompatible with my graphics drivers (no longer supported). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1 ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-26-generic. ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ken3021 F pulseaudio /dev/snd/pcmC0D0p: ken3021 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'ICH5'/'Intel ICH5 with AD1980 at irq 17' Mixer name : 'Analog Devices AD1980' Components : 'AC97a:41445370' Controls : 40 Simple ctrls : 29 Date: Fri Feb 13 02:00:00 2015 HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a IwConfig: lono wireless extensions. eth1 no wireless extensions. MachineType: Dell Computer Corporation Dimension 8300 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic root=UUID=9c013c53-e232-4e09-8235-315a373bac88 ro zswap.enabled=1 RelatedPackageVersions: linux-restricted-modules-3.11.0-26-generic N/A linux-backports-modules-3.11.0-26-generic N/A linux-firmware 1.79.18 RfKill: SourcePackage: linux-lts-saucy UpgradeStatus: Upgraded to precise on 2014-12-07 (67 days ago) dmi.bios.date: 09/27/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0W2562 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd09/27/2004:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0W2562:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 8300 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1421490/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1501993] Re: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]()
Martin Smith, let the scope of this report be only the kernel call trace mentioned in the Description. Regarding errors noticed in logs, this is not typically considered a bug, especially considering there is no noticed usability impact. Pivoting back to the call trace, the next step is to fully reverse commit bisect from kernel 4.2 to 4.3-rc3 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- 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/1501993 Title: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() Status in linux package in Ubuntu: Incomplete Bug description: I'm seeing a kernel hang when I 'dock' my laptop into my docking station; this happens with 4.2, specifically with: linux-image-extra-4.2.0-11-generic linux-image-extra-4.2.0-12-generic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4483862/+files/kern.log At this point I lose video, and can't do much else without a hard reboot back to linux-image-extra-3.19.0-30-generic. --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mart6985 1824 F pulseaudio /dev/snd/controlC0: mart6985 1824 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=ef25a70d-08ea-4cfb-a7a0-ab30671365cc InstallationDate: Installed on 2014-07-02 (456 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 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.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.148 Tags: wily Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-09-29 (3 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+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 1502630] [NEW] Screen brightness cannot be changed
Public bug reported: The screen brightness cannot be changed via the shortcut keys provided nor through the system setting menu. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Faraaz Ahmed (faraazahmed1994) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Faraaz Ahmed (faraazahmed1994) -- 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/1502630 Title: Screen brightness cannot be changed Status in linux package in Ubuntu: New Bug description: The screen brightness cannot be changed via the shortcut keys provided nor through the system setting menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502630/+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 1502630] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1502630 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502630 Title: Screen brightness cannot be changed Status in linux package in Ubuntu: Incomplete Bug description: The screen brightness cannot be changed via the shortcut keys provided nor through the system setting menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502630/+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 1095220] Re: ext4 file system corruptions due to a kernel bug
Huan Zhang, thank you for reporting this bug to Ubuntu. linux-lts-quantal reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1095220 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-quantal (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1095220 Title: ext4 file system corruptions due to a kernel bug Status in linux package in Ubuntu: Incomplete Bug description: A problematic kernel patch has been backported to Ubuntu since linux-image-3.5.0-18-generic: * jbd2: don't write superblock when if its empty (LP: #1066176) There are a few discussions on this issue: http://www.phoronix.com/scan.php?page=news_item=MTIxNDQ https://bbs.archlinux.org/viewtopic.php?id=151341=1 https://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8c673cbc7682b3f2862fe42f8069cac20c09e160 "This could potentially lead to minor file system corruptions (pass 5 complaints with the inode allocation bitmap) after an unclean shutdown under the wrong/unlucky workloads, but it turned into major failure if the journal_checksum and/or jouaral_async_commit was enabled." Another bug Bug #1019347 causing unclean shutdown makes the scenario worse in Ubuntu 12.10. I experienced serious filesystem corruptions twice on a newly installed Ubuntu 12.10 system after upgrading to the latest 3.5.0-21 kernel, especially when I frequently reboot my computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1095220/+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 1312559] Re: [Lenovo T540p] DevConfigDiffAfterS3 and DevConfigDiffAfterS4
Yung Shen, thank you for reporting this bug to Ubuntu. linux-lts-saucy reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1312559 Otherwise, please mark this as Invalid. ** Tags added: bios-outdated-2.21 ** Package changed: linux-lts-saucy (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Assignee: Ivan Hu (ivan.hu) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-saucy in Ubuntu. https://bugs.launchpad.net/bugs/1312559 Title: [Lenovo T540p] DevConfigDiffAfterS3 and DevConfigDiffAfterS4 Status in fwts package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Recivied device configuration differ messages when performing following tests: fwts -q --stdout-summary -r /home/ubuntu/.checkbox/suspend_30_cycles --s3-device-check --s3-device-check-delay 45 --s3-sleep-delay 30 s3 fwts -q --stdout-summary -r /home/ubuntu/.checkbox/hibernate_30_cycles --s4-device-check --s4-device-check-delay 45 --s4-sleep-delay 30 s4 DevConfigDiffAfterS3: Video configurations differ, before: PCI: :00:02.0, VID: 86:16, Class: 03:00 (VGA/8512 compatible controller) Config: : 86 80 16 04 07 04 90 00 06 00 00 03 00 00 00 00 0010: 04 00 00 f1 00 00 00 00 0c 00 00 e0 00 00 00 00 0020: 01 50 00 00 00 00 00 00 00 00 00 00 aa 17 11 22 .P." 0030: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00 PCI: :01:00.0, VID: de:90, Class: 03:00 (VGA/8512 compatible controller) Config: : de 10 90 12 03 00 10 00 a1 00 00 03 10 00 00 00 0010: 00 00 00 f0 0c 00 00 c0 00 00 00 00 0c 00 00 d0 0020: 00 00 00 00 01 40 00 00 00 00 00 00 aa 17 11 22 .@." 0030: 00 00 f8 ff 60 00 00 00 00 00 00 00 0b 01 00 00 `... versus after: PCI: :00:02.0, VID: 86:16, Class: 03:00 (VGA/8512 compatible controller) Config: : 86 80 16 04 07 04 90 00 06 00 00 03 00 00 00 00 0010: 04 00 00 f1 00 00 00 00 0c 00 00 e0 00 00 00 00 0020: 01 50 00 00 00 00 00 00 00 00 00 00 aa 17 11 22 .P." 0030: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00 PCI: :01:00.0, VID: de:90, Class: 03:00 (VGA/8512 compatible controller) Config: : de 10 90 12 03 00 10 00 a1 00 00 03 10 00 00 00 0010: 00 00 00 f0 0c 00 00 c0 00 00 00 00 0c 00 00 d0 0020: 00 00 00 00 01 40 00 00 00 00 00 00 00 00 00 00 .@.. 0030: 00 00 f8 ff 60 00 00 00 00 00 00 00 0b 01 00 00 `... DevConfigDiffAfterS4: Video configurations differ, before: PCI: :00:02.0, VID: 86:16, Class: 03:00 (VGA/8512 compatible controller) Config: : 86 80 16 04 07 04 90 00 06 00 00 03 00 00 00 00 0010: 04 00 00 f1 00 00 00 00 0c 00 00 e0 00 00 00 00 0020: 01 50 00 00 00 00 00 00 00 00 00 00 aa 17 11 22 .P." 0030: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00 PCI: :01:00.0, VID: de:90, Class: 03:00 (VGA/8512 compatible controller) Config: : de 10 90 12 03 00 10 00 a1 00 00 03 10 00 00 00 0010: 00 00 00 f0 0c 00 00 c0 00 00 00 00 0c 00 00 d0 0020: 00 00 00 00 01 40 00 00 00 00 00 00 00 00 00 00 .@.. 0030: 00 00 f8 ff 60 00 00 00 00 00 00 00 0b 01 00 00 `... versus after: PCI: :00:02.0, VID: 86:16, Class: 03:00 (VGA/8512 compatible controller) Config: : 86 80 16 04 07 04 90 00 06 00 00 03 00 00 00 00 0010: 04 00 00 f1 00 00 00 00 0c 00 00 e0 00 00 00 00 0020: 01 50 00 00 00 00 00 00 00 00 00 00 aa 17 11 22 .P." 0030: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00 PCI: :01:00.0, VID: de:90, Class: 03:00 (VGA/8512 compatible controller) Config: : de 10 90 12 03 00 10 00 a1 00 00 03 10 00 00 00 0010: 00 00 00 f0 0c 00 00 c0 00 00 00 00 0c 00 00 d0 0020: 00 00 00 00 01 40 00 00 00 00 00 00 aa 17 11 22 .@." 0030: 00 00 f8 ff 60 00 00 00 00 00 00 00 0b 01 00 00 `... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
[Kernel-packages] [Bug 1414363] Re: Computer cannot reboot
Ken Sharp, thank you for reporting this bug to Ubuntu. linux-lts-saucy reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please execute the following in a terminal: apport-collect 1414363 Otherwise, please mark this as Invalid. ** Tags added: latest-bios-a07 ** Description changed: The computer boots fine. It shuts down fine. The problem is that when rebooting it hangs shortly after the Grub screen. To add insult to injury none of the kernel output is ever printed, normal boot or broken reboot. "quiet splash" has been removed from the boot options. Tried "reboot=bios" but it made no difference. + WORKAROUND: Adding "reboot=warm" to the Linux boot options allows the + reboot to work correctly. + ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1 ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: nvidia AlsaDevices: - total 0 - crw-rw---T 1 root audio 116, 1 Jan 24 20:40 seq - crw-rw---T 1 root audio 116, 33 Jan 24 20:40 timer + total 0 + crw-rw---T 1 root audio 116, 1 Jan 24 20:40 seq + crw-rw---T 1 root audio 116, 33 Jan 24 20:40 timer AplayDevices: aplay: device_list:204: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 ArecordDevices: arecord: device_list:204: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat Jan 24 20:44:34 2015 HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a IwConfig: - lono wireless extensions. - - eth1 no wireless extensions. + lono wireless extensions. + + eth1 no wireless extensions. MachineType: Dell Computer Corporation Dimension 8300 MarkForUpload: True ProcEnviron: - LANGUAGE=en_GB:en - TERM=xterm - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=xterm + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic root=UUID=9c013c53-e232-4e09-8235-315a373bac88 ro zswap.enabled=1 reboot=rst vga_mode=800x600 RelatedPackageVersions: - linux-restricted-modules-3.11.0-26-generic N/A - linux-backports-modules-3.11.0-26-generic N/A - linux-firmware 1.79.18 + linux-restricted-modules-3.11.0-26-generic N/A + linux-backports-modules-3.11.0-26-generic N/A + linux-firmware 1.79.18 RfKill: - + SourcePackage: linux-lts-saucy UpgradeStatus: Upgraded to precise on 2014-12-07 (48 days ago) dmi.bios.date: 09/27/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0W2562 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd09/27/2004:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0W2562:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 8300 dmi.sys.vendor: Dell Computer Corporation ** Package changed: linux-lts-saucy (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-saucy in Ubuntu. https://bugs.launchpad.net/bugs/1414363 Title: Computer cannot reboot Status in linux package in Ubuntu: Incomplete Bug description: The computer boots fine. It shuts down fine. The problem is that when rebooting it hangs shortly after the Grub screen. To add insult to injury none of the kernel output is ever printed, normal boot or broken reboot. "quiet splash" has been removed from the boot options. Tried "reboot=bios" but it made no difference. WORKAROUND: Adding "reboot=warm" to the Linux boot options allows the reboot to work correctly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1 ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: nvidia AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Jan 24 20:40 seq crw-rw---T 1 root audio 116, 33 Jan 24 20:40 timer AplayDevices: aplay: device_list:204: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 ArecordDevices: arecord: device_list:204: no soundcards found... AudioDevicesInUse: Error:
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
I plugged my graphics card into an old computer I have (Asus M2NPV-VM). The other computer was running Ubuntu 14.04.3 with Linux version 3.13.0-63-generic (dmesg log attached). The same display connected on the same displayport did work fine. However, it was slow because the GPU was not yet well supported in Linux version 3.13. I believe My displayport problem might be BIOS related. I think I will have to wait for a BIOS update to use my displayport again. Until then I will use DVI ports. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+attachment/4483796/+files/dmesg.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/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+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 1501993] Re: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]()
Tag added. Let me know if the ACPI error means I should keep testing further older mainline kernels or not. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1501993 Title: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() Status in linux package in Ubuntu: Incomplete Bug description: Hi there -- I'm seeing a kernel hang when I 'dock' my laptop into my docking station; this happens with 4.2, specifically with: linux-image-extra-4.2.0-11-generic linux-image-extra-4.2.0-12-generic Oct 1 21:38:33 mart6985-laptop kernel: [ 876.317186] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:34 mart6985-laptop kernel: [ 877.156378] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995466] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995698] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to train DP, aborting Oct 1 21:38:36 mart6985-laptop kernel: [ 878.825806] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:37 mart6985-laptop kernel: [ 879.664854] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:38 mart6985-laptop kernel: [ 880.503908] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821042] ACPI Error: Index value 0x0083 overflows field width 0x7 (20150619/exfldio-341) Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821046] ACPI Error: Method parse/execution failed [\NEVT] (Node 88040e0c7258), AE_AML_REGISTER_LIMIT (20150619/pspa rse-536) Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821050] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV._Q66] (Node 88040e0c4b90), AE_AML_REGISTER_ LIMIT (20150619/psparse-536) Oct 1 21:38:38 mart6985-laptop kernel: [ 881.343010] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998373] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998374] [ cut here ] Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998386] WARNING: CPU: 1 PID: 1038 at /build/linux-X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_c rtc_state+0x2c5/0x440 [i915]() Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998387] pipe state doesn't match! Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998387] Modules linked in: hid_generic usbhid iptable_filter ip_tables x_tables ctr ccm rfcomm btusb btrtl btbcm btinte l pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep bluetooth binfmt_misc pn544_mei mei_phy pn544 arc4 hci nfc dell_wmi iwlmvm sparse_keymap mac8021 1 dell_laptop dcdbas dell_smm_hwmon intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp iwlwifi uvcvideo input_leds videobuf2_vmalloc kvm_intel videobu f2_memops kvm cfg80211 joydev serio_raw videobuf2_core v4l2_common snd_hda_codec_hdmi videodev media lpc_ich snd_hda_codec_realtek snd_soc_rt5640 snd_soc_rl6231 snd_h da_codec_generic snd_soc_core shpchp snd_compress ac97_bus snd_hda_intel snd_pcm_dmaengine snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_hwdep snd_ra wmidi mei_me snd_pcm mei snd_seq snd_seq_device snd_timer 8250_fintek snd dell_smo8800 soundcore dw_dmac snd_soc_sst_acpi dw_dmac_core 8250_dw i2c_designware_platform i2c_designware_core spi_pxa2xx_platform dell_rbtn mac_hid nfsd auth_rpcgss nfs_acl lockd parport_pc grace sunrpc ppdev lp parport autofs4 drbg ansi_cprng algif_skcip her af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper i915 ablk_helper cryptd psmouse ahci libahci i2c _algo_bit sdhci_pci drm_kms_helper e1000e drm ptp pps_core wmi sdhci_acpi video sdhci i2c_hid hid Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998438] CPU: 1 PID: 1038 Comm: Xorg Tainted: GW OE 4.2.0-12-generic #14-Ubuntu Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998439] Hardware name: Dell Inc. Latitude E7440/03HFCG, BIOS A14 02/02/2015 Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998440] c02b2ab0 8800da29f7e8 817b0cd5 Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998442] 8800da29f838 8800da29f828 81076536 8800da29f858 Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998443] 8800da29f8c0 8800d9e08800 0001 8800d9e08b50 Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998445] Call Trace:
[Kernel-packages] [Bug 1501993] Re: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]()
Hello again! I started by testing 4.3.0-040300rc3-generic. This seems to have fixed the hang, but I still see log lines that seem problematic: Oct 4 09:18:41 mart6985-laptop kernel: [ 56.385682] acpi PNP0401:00: Already enumerated Oct 4 09:18:41 mart6985-laptop kernel: [ 56.389467] acpi device:40: Cannot transition to power state D3hot for parent in (unknown) Oct 4 09:18:50 mart6985-laptop kernel: [ 65.823223] ACPI Error: Index value 0x0083 overflows field width 0x7 (20150818/exfldio-341) Oct 4 09:18:50 mart6985-laptop kernel: [ 65.823228] ACPI Error: Method parse/execution failed [\NEVT] (Node 88040e0cb258), AE_AML_REGISTER_LIMIT (20150818/psparse-542) Oct 4 09:18:50 mart6985-laptop kernel: [ 65.823233] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node 88040e0c9b90), AE_AML_REGISTER_LIMIT (20150818/psparse-542) Should I consider this fixed or keep going until I don't see the ACPI error? I also noted that closing the laptop lid while docked caused the very same following ACPI error about power state transitions -- should I be reporting this as a separate issue? It doesn't seem to hurt anything on my system. Oct 4 09:20:00 mart6985-laptop systemd[1]: Stopping User Manager for UID 112... Oct 4 09:20:00 mart6985-laptop systemd[1079]: Stopped target Default. Oct 4 09:20:00 mart6985-laptop systemd[1079]: Stopped target Basic System. Oct 4 09:20:00 mart6985-laptop systemd[1079]: Stopped target Timers. Oct 4 09:20:00 mart6985-laptop systemd[1079]: Stopped target Sockets. Oct 4 09:20:00 mart6985-laptop systemd[1079]: Stopped target Paths. Oct 4 09:20:00 mart6985-laptop systemd[1079]: Reached target Shutdown. Oct 4 09:20:00 mart6985-laptop systemd[1079]: Starting Exit the Session... Oct 4 09:20:00 mart6985-laptop systemd[1079]: Received SIGRTMIN+24 from PID 3029 (kill). Oct 4 09:20:00 mart6985-laptop systemd[1]: Stopped User Manager for UID 112. Oct 4 09:20:00 mart6985-laptop systemd[1]: Removed slice user-112.slice. Oct 4 09:20:06 mart6985-laptop avahi-daemon[864]: Invalid response packet from host 192.168.1.16. Oct 4 09:20:14 mart6985-laptop kernel: [ 149.531979] pci_bus :01: Allocating resources Oct 4 09:20:14 mart6985-laptop kernel: [ 149.532016] pci_bus :02: Allocating resources Oct 4 09:20:14 mart6985-laptop kernel: [ 149.532148] pci_bus :03: Allocating resources Oct 4 09:20:14 mart6985-laptop kernel: [ 149.534029] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Oct 4 09:20:14 mart6985-laptop kernel: [ 149.540179] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Oct 4 09:20:14 mart6985-laptop kernel: [ 149.540254] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Oct 4 09:20:14 mart6985-laptop kernel: [ 149.540369] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Oct 4 09:20:14 mart6985-laptop kernel: [ 149.540937] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Oct 4 09:20:14 mart6985-laptop kernel: [ 149.540975] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Oct 4 09:20:14 mart6985-laptop kernel: [ 149.541151] acpi device:40: Cannot transition to power state D3hot for parent in (unknown) Oct 4 09:20:14 mart6985-laptop kernel: [ 149.541342] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Oct 4 09:20:14 mart6985-laptop kernel: [ 149.541645] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.3-rc3 -- 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/1501993 Title: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() Status in linux package in Ubuntu: Incomplete Bug description: Hi there -- I'm seeing a kernel hang when I 'dock' my laptop into my docking station; this happens with 4.2, specifically with: linux-image-extra-4.2.0-11-generic linux-image-extra-4.2.0-12-generic Oct 1 21:38:33 mart6985-laptop kernel: [ 876.317186] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:34 mart6985-laptop kernel: [ 877.156378] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995466] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995698] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to train DP, aborting Oct 1 21:38:36 mart6985-laptop kernel: [ 878.825806] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up Oct 1 21:38:37 mart6985-laptop kernel: [ 879.664854] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up
[Kernel-packages] [Bug 1247773] Re: Fanotify blocks any write operation to CIFS mounted volumes for about 10-15 secs
pria, thank you for reporting this bug to Ubuntu. linux-lts-saucy reached EOL on August 2014. See the following documents for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases https://wiki.ubuntu.com/Kernel/LTSEnablementStack If this is still reproducible in a supported release, please upgrade and then execute the following in a terminal: apport-collect 1247773 Otherwise, please mark this as Invalid. ** Package changed: linux-lts-saucy (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247773 Title: Fanotify blocks any write operation to CIFS mounted volumes for about 10-15 secs Status in linux package in Ubuntu: Incomplete Bug description: Whenever we use Fanotify to monitor "CIFS" mounted volumes and try to write to a new file by doing: echo "ABC" > /mnt/cifs/test.c It takes around 10-15 secs to complete the write operation. This happens only when we try to monitor "FAN_OPEN_PERM". Looks like "FAN_OPEN_PERM" blocks and notifies only after 10-15 secs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247773/+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 1268252] Re: Brightness settings stopped working after upgrade
** Description changed: I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, both the physical key and the brightness settings in the gnome-control centre have stopped working. Whatever level of brightness i decrease it to, it always stays on maximum. I'm able to reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 12 09:17:00 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2013-11-16 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago) - --- + --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: krishnan 3070 F pulseaudio - /dev/snd/controlC0: krishnan 3070 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: krishnan 3070 F pulseaudio + /dev/snd/controlC0: krishnan 3070 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c545b9da-fef4-4530-9051-29276dfd842c InstallationDate: Installed on 2013-11-16 (58 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO INVALID NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=0b897d24-0c02-4f57-9596-5fcd681c5ed0 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-2-generic N/A - linux-backports-modules-3.13.0-2-generic N/A - linux-firmware1.121 + linux-restricted-modules-3.13.0-2-generic N/A + linux-backports-modules-3.13.0-2-generic N/A + linux-firmware1.121 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-2-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-06 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN12WW(V1.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.name: INVALID dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO ** Changed in: linux (Ubuntu) Assignee: Rahul (rahulshantagiri) => Faraaz Ahmed (faraazahmed1994) ** Changed in: linux (Ubuntu) Assignee: Faraaz Ahmed (faraazahmed1994) => (unassigned) -- 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/1268252 Title: Brightness settings stopped working after upgrade Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, both the physical key and the brightness settings in the gnome-control centre have stopped working. Whatever level of brightness i decrease it to, it always stays on maximum. I'm able to reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 12 09:17:00 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2013-11-16 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago) --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krishnan 3070 F pulseaudio /dev/snd/controlC0: krishnan 3070 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice:
[Kernel-packages] [Bug 1499491] Re: 1002:67b1 Display connected on DisplayPort turns black during boot and never returns
Olivier Caro, given you have the latest BIOS, we can continue to pursue it as a driver bug, and let an upstream developer make the call if there is nothing that can be done on the driver side. Despite this, a couple of follow up questions: 1) If you remove the Radeon HD 6670 so you only have the R9 290 installed, does this change anything? 2) With just the R9 290 installed, does using fglrx provide a WORKAROUND following https://help.ubuntu.com/community/BinaryDriverHowto/AMD ? ** Description changed: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. - Description: Ubuntu 15.04 - Release: 15.04 - --- + I plugged the R9 290 into a Asus M2NPV-VM based PC running Ubuntu + 14.04.3 (3.13.0-63-generic). The same display connected on the same + displayport did work fine. + + --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: olivier2403 F pulseaudio - /dev/snd/controlC2: olivier2403 F pulseaudio - /dev/snd/controlC1: olivier2403 F pulseaudio - /dev/snd/seq:timidity 1672 F timidity + USERPID ACCESS COMMAND + /dev/snd/controlC0: olivier2403 F pulseaudio + /dev/snd/controlC2: olivier2403 F pulseaudio + /dev/snd/controlC1: olivier2403 F pulseaudio + /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: - 0 radeondrmfb - 1 radeondrmfb + 0 radeondrmfb + 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied - No PulseAudio daemon running, or not running as session daemon. + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-3.19.0-30-generic N/A - linux-backports-modules-3.19.0-30-generic N/A - linux-firmware 1.143.3 + linux-restricted-modules-3.19.0-30-generic N/A + linux-backports-modules-3.19.0-30-generic N/A + linux-firmware 1.143.3 RfKill: - + Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: - + _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. -- 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/1499491 Title: 1002:67b1 Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. I plugged the R9 290 into a Asus M2NPV-VM based PC running Ubuntu 14.04.3 (3.13.0-63-generic). The same display connected on the same displayport did work fine. --- ApportVersion: 2.17.2-0ubuntu1.5
[Kernel-packages] [Bug 1501993] Re: drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]()
Cut from Description. ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481525/+files/WifiSyslog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481523/+files/UdevDb.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481524/+files/UdevLog.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481522/+files/RfKill.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481521/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481520/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481518/+files/ProcCpuinfo.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481519/+files/ProcEnviron.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481517/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481516/+files/Lspci.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481515/+files/JournalErrors.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481514/+files/IwConfig.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481513/+files/Dependencies.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481512/+files/CurrentDmesg.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481511/+files/CRDA.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4481510/+files/AlsaInfo.txt ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4483862/+files/kern.log ** Description changed: - Hi there -- - I'm seeing a kernel hang when I 'dock' my laptop into my docking station; this happens with 4.2, specifically with: linux-image-extra-4.2.0-11-generic linux-image-extra-4.2.0-12-generic + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501993/+attachment/4483862/+files/kern.log - Oct 1 21:38:33 mart6985-laptop kernel: [ 876.317186] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up - Oct 1 21:38:34 mart6985-laptop kernel: [ 877.156378] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up - Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995466] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up - Oct 1 21:38:35 mart6985-laptop kernel: [ 877.995698] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to train DP, aborting - Oct 1 21:38:36 mart6985-laptop kernel: [ 878.825806] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up - Oct 1 21:38:37 mart6985-laptop kernel: [ 879.664854] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up - Oct 1 21:38:38 mart6985-laptop kernel: [ 880.503908] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up - Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821042] ACPI Error: Index value 0x0083 overflows field width 0x7 (20150619/exfldio-341) - Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821046] ACPI Error: Method parse/execution failed [\NEVT] (Node 88040e0c7258), AE_AML_REGISTER_LIMIT (20150619/pspa - rse-536) - Oct 1 21:38:38 mart6985-laptop kernel: [ 880.821050] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV._Q66] (Node 88040e0c4b90), AE_AML_REGISTER_ - LIMIT (20150619/psparse-536) - Oct 1 21:38:38 mart6985-laptop kernel: [ 881.343010] [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up - Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998373] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) - Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998374] [ cut here ] - Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998386] WARNING: CPU: 1 PID: 1038 at /build/linux-X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_c - rtc_state+0x2c5/0x440 [i915]() - Oct 1 21:38:39 mart6985-laptop kernel: [ 881.998387] pipe state doesn't match! - Oct 1
[Kernel-packages] [Bug 1491494] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2015-10-04 15:15 EDT--- State: Assigned by: bellivea on 04 October 2015 10:07:01 Any updates? -- 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/1491494 Title: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile Status in linux package in Ubuntu: Triaged Bug description: -- Problem Description -- The failure related to the BELL-3 (2 port-Async EIA-232 adapter). Ubuntu always hit exception when the adapter is not present. See my test scenarios below. Test #1: Boot Ubuntu with BELL-3 adapter === - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on the LPAR. => Ubuntu boot fine this time. Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile === - I powered down the Ubuntu partition and removed the BELL-3 adapter from LPAR profile then powered on the LPAR. => Ubuntu hit the exception. Elapsed time since release of system processors: 0 mins 9 secs error: no suitable video mode found. OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2) Detected machine type: 0101 Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7 memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0b42 alloc_top: 1000 alloc_top_hi : 1000 rmo_top : 1000 ram_top : 1000 instantiating rtas at 0x0ecb... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0b43 -> 0x0b4316b1 Device tree struct 0x0b44 -> 0x0b47 Calling quiesce... returning from prom_init -> smp_release_cpus() spinning_secondaries = 15 <- smp_release_cpus() <- setup_system() [0.661510] /build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through [4.658302] device-mapper: table: 252:0: multipath: error getting device [4.691990] device-mapper: table: 252:0: multipath: error getting device [4.934034] device-mapper: table: 252:0: multipath: error getting device [4.951977] device-mapper: table: 252:0: multipath: error getting device * Discovering and coalescing multipaths... [ OK ] Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd * Starting AppArmor profiles[ OK ] Loading the saved-state of the serial devices... [5.109665] Unable to handle kernel paging request for data at address 0xd803 [5.109677] Faulting instruction address: 0xc060fec4 [5.109685] Oops: Kernel access of bad area, sig: 11 [#1] [5.109691] SMP NR_CPUS=2048 NUMA pSeries [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) mlx4_core(OE) mlx_compat(OE) [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G OE 3.19.0-23-generic #24~14.04.1-Ubuntu [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: c000f0528000 [5.109777] NIP: c060fec4 LR: c0617498 CTR: c060fe20 [5.109785] REGS: c000f052b6b0 TRAP: 0300 Tainted: G OE (3.19.0-23-generic) [5.109793] MSR: 80009033CR: 84002022 XER: [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 SOFTE: 1 GPR00: c0617498 c000f052b930 c144c700 00bf GPR04: d803 00bf c000f399 0141 GPR08: c0611d20 c13539e0 d800 c1351ba8 GPR12: c060fe20 ce830900 GPR16: GPR20: 007d 0040
[Kernel-packages] [Bug 1502646] [NEW] linux: 4.2.0-14.16 -proposed tracker
Public bug reported: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Sunday, 04. October 2015 15:46 UTC kernel-phase-changed:Sunday, 04. October 2015 15:46 UTC kernel-phase:Prepare ** Affects: kernel-development-workflow Importance: Medium Status: Invalid ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Wily) Importance: Undecided Status: Invalid ** Tags: block-proposed kernel-release-tracking-bug wily ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Tags added: wily ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: kernel-development-workflow Status: In Progress => Invalid ** No longer affects: kernel-development-workflow/promote-to-release ** No longer affects: kernel-development-workflow/promote-to-proposed ** No longer affects: kernel-development-workflow/prepare-package-signed ** No longer affects: kernel-development-workflow/prepare-package-meta ** No longer affects: kernel-development-workflow/prepare-package ** No longer affects: kernel-development-workflow/automated-testing -- 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/1502646 Title: linux: 4.2.0-14.16 -proposed tracker Status in Kernel Development Workflow: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Invalid Bug description: This bug is for tracking the 4.2.0-14.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Sunday, 04. October 2015 15:46 UTC kernel-phase-changed:Sunday, 04. October 2015 15:46 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1502646/+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 1499491] Re: 1002:67b1 Display connected on DisplayPort turns black during boot and never returns
Christopher, 1) Yes, I have removed the Radeon HD 6670. 2) I have just tried with fglrx and fglrx-updates : The displays is up when in console mode (tty[1-6]). The displays turns black when switching to Xorg (tty7). -- 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/1499491 Title: 1002:67b1 Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. I plugged the R9 290 into a Asus M2NPV-VM based PC running Ubuntu 14.04.3 (3.13.0-63-generic). The same display connected on the same displayport did work fine. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+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 1502654] [NEW] Keyboard layout changes randomly in ubuntu for no reason
Public bug reported: Keyboard layout changes randomly at any time for no reason. We can change the settings of the keyboard layout manually by clicking on the settings button on the right top corner and then we can select the input source and change the particular layout. But many times it happens where we are using a particular input source and it suddenly changes randomly for no reason. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Rohan Jadhav (rohanjadhav316) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Rohan Jadhav (rohanjadhav316) -- 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/1502654 Title: Keyboard layout changes randomly in ubuntu for no reason Status in linux package in Ubuntu: New Bug description: Keyboard layout changes randomly at any time for no reason. We can change the settings of the keyboard layout manually by clicking on the settings button on the right top corner and then we can select the input source and change the particular layout. But many times it happens where we are using a particular input source and it suddenly changes randomly for no reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502654/+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 1502654] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1502654 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502654 Title: Keyboard layout changes randomly in ubuntu for no reason Status in linux package in Ubuntu: Incomplete Bug description: Keyboard layout changes randomly at any time for no reason. We can change the settings of the keyboard layout manually by clicking on the settings button on the right top corner and then we can select the input source and change the particular layout. But many times it happens where we are using a particular input source and it suddenly changes randomly for no reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502654/+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 1502658] [NEW] unable to read xattr id index table
Public bug reported: when we are updating the vmware tool for linux software it wil instal after that we get bugs(error) ** 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/1502658 Title: unable to read xattr id index table Status in linux package in Ubuntu: New Bug description: when we are updating the vmware tool for linux software it wil instal after that we get bugs(error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502658/+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 1493814] Re: [Acer Travelmate B115-M] Synaptic touchpad
Done! Subscribed > http://vger.kernel.org/vger-lists.html#linux-input Mail sent to linux-input at vger dot kernel dot org Waiting at > http://www.spinics.net/lists/linux-input/maillist.html Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1493814 Title: [Acer Travelmate B115-M] Synaptic touchpad Status in linux package in Ubuntu: Triaged Bug description: Touchpad has issues working. WORKAROUND: Set in BIOS Touchpad option from Advanced to Basic. --- ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuari 1911 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=6a63f422-0d53-4459-873d-c925133fdbec InstallationDate: Installed on 2014-09-16 (357 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer TravelMate B115-M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=681882b9-fe81-482e-a240-d2ee75144228 ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.19.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd04/11/2014:svnAcer:pnTravelMateB115-M:pvrV1.04:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: TravelMate B115-M dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493814/+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 1502055] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1502055/+attachment/4483757/+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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ppiwonsk 1929 F pulseaudio /dev/snd/controlC1: ppiwonsk 1929 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-03 (122 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA TECRA Z40-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 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.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.1A dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z40-B dmi.product.version: PT45GE-06S03C0V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1502055] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1502055/+attachment/4483754/+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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ppiwonsk 1929 F pulseaudio /dev/snd/controlC1: ppiwonsk 1929 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-03 (122 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA TECRA Z40-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 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.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.1A dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z40-B dmi.product.version: PT45GE-06S03C0V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1502055] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1502055/+attachment/4483755/+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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ppiwonsk 1929 F pulseaudio /dev/snd/controlC1: ppiwonsk 1929 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-03 (122 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA TECRA Z40-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 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.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.1A dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z40-B dmi.product.version: PT45GE-06S03C0V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1287635] Re: [Broadcom BCM43142, BCM4313] STA wireless driver failed to activate on 12.04.4
** Package changed: linux-lts-saucy (Ubuntu) => linux-lts-trusty (Ubuntu) -- 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/1287635 Title: [Broadcom BCM43142, BCM4313] STA wireless driver failed to activate on 12.04.4 Status in bcmwl package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Failed to finish driver activation correctly, installing broadcom wireless driver by using Addtional Drivers (Jockey) cannot be finished, because wl seems not correctly built. To verify this issu, execute the same steps in bug 1279690 . Also tired out the patch in bug 1173761 ,and following steps in comment #55 and #58 [0], still not fixing the problem. Affected devices: BCM43142 [14e4:4365], BCM4313 [14e4:4727] [0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173761/comments/58 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.2 ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Mar 4 04:27:30 2014 InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash 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/1287635/+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 1502055] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1502055/+attachment/4483752/+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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ppiwonsk 1929 F pulseaudio /dev/snd/controlC1: ppiwonsk 1929 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-03 (122 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA TECRA Z40-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 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.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.1A dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z40-B dmi.product.version: PT45GE-06S03C0V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1502055] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1502055/+attachment/4483750/+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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ppiwonsk 1929 F pulseaudio /dev/snd/controlC1: ppiwonsk 1929 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-03 (122 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA TECRA Z40-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 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.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.1A dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z40-B dmi.product.version: PT45GE-06S03C0V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1296598] Re: Cardreader O2 Micro, Inc. Device [1217:8520] (rev 01) could not read some of MMC cards
** No longer affects: linux-lts-saucy (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-saucy in Ubuntu. https://bugs.launchpad.net/bugs/1296598 Title: Cardreader O2 Micro, Inc. Device [1217:8520] (rev 01) could not read some of MMC cards Status in linux-lts-trusty package in Ubuntu: New Bug description: Dell Latitude E6540 (CID 201306-13679) on updated 12.04.4 (3.11.0-18-generic #32~precise1-Ubuntu) Steps to reproduce this bug: insert mmc Expected result: Ubuntu will mount the device for you and ready to use (read/write) Actula result: system has no response and dmesg shows: mmc0: Got data interrupt 0x0200 even though no data operation was in progress. More information: 1. this is related to this bug LP: #1239938 2. dmesg message: Mar 24 05:15:23 201306-13679 kernel: [ 108.619703] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. Mar 24 05:15:27 201306-13679 kernel: [ 111.904666] mmc0: Card removed during transfer! Mar 24 05:15:27 201306-13679 kernel: [ 111.904678] mmc0: Resetting controller. Mar 24 05:15:27 201306-13679 kernel: [ 111.905014] mmc0: error -123 whilst initialising MMC card Mar 24 05:15:29 201306-13679 kernel: [ 114.113827] mmc0: Got data interrupt 0x0200 even though no data operation was in progress. Mar 24 05:15:31 201306-13679 kernel: [ 115.730270] mmc0: Card removed during transfer! Mar 24 05:15:31 201306-13679 kernel: [ 115.730283] mmc0: Resetting controller. Mar 24 05:15:31 201306-13679 kernel: [ 115.730444] mmc0: error -123 whilst initialising MMC card Mar 24 05:15:42 201306-13679 kernel: [ 126.882583] mmc0: new MMC card at address 0001 Mar 24 05:15:42 201306-13679 kernel: [ 126.925463] mmcblk0: mmc0:0001 AF MM 490 MiB Mar 24 05:15:42 201306-13679 kernel: [ 126.928036] mmcblk0: p1 Mar 24 05:15:42 201306-13679 kernel: [ 127.432248] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Mar 24 05:16:04 201306-13679 kernel: [ 148.906923] mmc0: card 0001 removed Mar 24 05:16:10 201306-13679 kernel: [ 154.758342] mmc0: new high speed MMC card at address 0001 Mar 24 05:16:10 201306-13679 kernel: [ 154.758669] mmcblk0: mmc0:0001 MMC 242 MiB Mar 24 05:16:10 201306-13679 kernel: [ 154.759956] mmcblk0: p1 Mar 24 05:16:10 201306-13679 kernel: [ 154.968389] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Mar 24 05:16:26 201306-13679 kernel: [ 171.277790] mmc0: card 0001 removed Mar 24 05:16:32 201306-13679 kernel: [ 177.194030] mmc0: new high speed SD card at address b368 Mar 24 05:16:32 201306-13679 kernel: [ 177.194352] mmcblk0: mmc0:b368 SDC 1.87 GiB Mar 24 05:16:32 201306-13679 kernel: [ 177.196338] mmcblk0: p1 Mar 24 05:16:32 201306-13679 kernel: [ 177.346471] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Mar 24 05:16:41 201306-13679 kernel: [ 186.054356] mmc0: card b368 removed Mar 24 05:16:46 201306-13679 kernel: [ 190.973354] mmc0: new high speed SDHC card at address Mar 24 05:16:46 201306-13679 kernel: [ 190.973667] mmcblk0: mmc0: SU04G 3.69 GiB Mar 24 05:16:46 201306-13679 kernel: [ 190.983080] mmcblk0: p1 Mar 24 05:16:46 201306-13679 kernel: [ 191.098084] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Mar 24 05:17:01 201306-13679 CRON[2227]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 24 05:17:04 201306-13679 kernel: [ 208.745328] mmc0: card removed these message could be reproduced by the following steps: a. insert mmc card A which could not work normally. b. insert mmc card B which could work normally. c. insert SD card and SDHC card could work normally. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.11.0-18-generic 3.11.0-18.32~precise1 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-18-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1743 F pulseaudio /dev/snd/controlC0: ubuntu 1743 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf7c34000 irq 46' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 21 Simple ctrls : 3 Card1.Amixer.info: Card
[Kernel-packages] [Bug 1502055] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1502055/+attachment/4483761/+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/1502055 Title: Crypt password screen not responding Status in linux package in Ubuntu: Incomplete Bug description: Hi, During booting of system when the password screen for a encrypted device is presented there is no response. The screen is not accepting any input. I can switch to another screen using ctrl+alt+F# key and see blinking cursor. Switching back to ctrl+alt+F7 is showing message and all entered keys on screen. Rebooting by ctrl+alt+del or power button causes that the system boots to a text version of that screen where I can enter the password and system boots to OS. Not sure what could be gathered during this event to assist in identifying the problem since I have no possibility to get any logs and decrypt the disk :( Regards, Peter Just to add when the password screen is "hung" and I switch to different screen and back to F7 I see this message: starting version 219 The same is visible when second boot is going. However this time I'm pushed to text based version where no problem is visible --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ppiwonsk 1929 F pulseaudio /dev/snd/controlC1: ppiwonsk 1929 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-03 (122 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA TECRA Z40-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 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.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.1A dmi.board.asset.tag: 00 dmi.board.name: TECRA Z40-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z40-B dmi.product.version: PT45GE-06S03C0V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502055/+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 1292563] Re: nvidia driver fails to initialize on Haswell without upstream kernel patch
** No longer affects: linux-lts-saucy (Ubuntu) ** No longer affects: linux-lts-saucy (Ubuntu Precise) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-saucy in Ubuntu. https://bugs.launchpad.net/bugs/1292563 Title: nvidia driver fails to initialize on Haswell without upstream kernel patch Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Invalid Status in linux source package in Saucy: Won't Fix Status in linux-lts-saucy source package in Saucy: Invalid Bug description: I have a Haswell-based Optimus laptop. Trying to initialize the NVIDIA driver fails: [ 58.885456] [drm] Initialized nvidia-drm 0.0.0 20130102 for :03:00.0 on minor 1 [ 58.885462] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 334.23 Sun Mar 9 21:06:05 PDT 2014 [ 58.886183] vgaarb: this pci device is not a vga device [ 58.887550] nvidia :03:00.0: irq 69 for MSI/MSI-X [ 58.894206] NVRM: failed to copy vbios to system memory. [ 58.896770] NVRM: RmInitAdapter failed! (0x30:0x:720) [ 58.896777] NVRM: rm_init_adapter failed for device bearing minor number 0 [ 58.896796] NVRM: nvidia_frontend_open: minor 0, module->open() failed, error -5 This is fixed by cherry-picking the following kernel commit: commit 11b88ee275ec8590a373396888c2460ee89364d6 Author: Rafael J. WysockiDate: Mon Sep 9 23:07:47 2013 +0200 ACPI / bind: Prefer device objects with _STA to those without it As reported at https://bugzilla.kernel.org/show_bug.cgi?id=60829, there still are cases in which do_find_child() doesn't choose the ACPI device object it is "expected" to choose if there are more such objects matching one PCI device present. This particular problem may be worked around by making do_find_child() return device obejcts witn _STA whose result indicates that the device is enabled before device objects without _STA if there's more than one device object to choose from. This change doesn't affect the case in which there's only one matching ACPI device object per PCI device. References: https://bugzilla.kernel.org/show_bug.cgi?id=60829 Reported-by: Peter Wu Tested-by: Felix Lisczyk Signed-off-by: Rafael J. Wysocki drivers/acpi/glue.c | 35 --- 1 file changed, 24 insertions(+), 11 deletions(-) Ubuntu 13.10 is also affected, while the 14.04 beta works since it includes the above commit. # lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 # apt-cache policy linux-image-3.11.0-18-generic linux-image-3.11.0-18-generic: Installed: 3.11.0-18.32~precise1 Candidate: 3.11.0-18.32~precise1 Version table: *** 3.11.0-18.32~precise1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292563/+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