[Kernel-packages] [Bug 1140716]
*** Bug 75163 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: Confirmed Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp
[Kernel-packages] [Bug 986724] Re: [Samsung NP900X3B-A01US] Lid state changes not detected
For those affected by this bug, please consider the solution posted on
https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061- it might be
what you need.
--
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/986724
Title:
[Samsung NP900X3B-A01US] Lid state changes not detected
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Neither lid open nor lid close events are detected.
Running 'cat /proc/acpi/button/lid/LID0/state' always returns 'state: open'.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
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: adam 1893 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0269,144dc0cd,00100202
HDA:80862805,80860101,0010'
Controls : 22
Simple ctrls : 10
Date: Sat Apr 21 19:53:30 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3B/900X4B
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=0b0abe89-812f-48c8-98ad-18dbf49290f8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-03-28 (24 days ago)
dmi.bios.date: 03/20/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P05AAH
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 900X3B/900X4B
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvrP05AAH:bd03/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3B/900X4B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn900X3B/900X4B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 900X3B/900X4B
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/986724/+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 1247723] Re: [Samsung NP900X3C-A02US] Lid state changes not detected
For those affected by this bug, please consider the solution posted on https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061- it might be what you need. -- 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/1247723 Title: [Samsung NP900X3C-A02US] Lid state changes not detected Status in “linux” package in Ubuntu: Expired Bug description: Neither lid open nor lid close events are detected on Samsung 900X3C laptop. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: boot/vmlinuz-3.11.0-12-generic] ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sahak 1482 F pulseaudio Date: Sun Nov 3 23:11:48 2013 InstallationDate: Installed on 2013-10-26 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=366ff628-3319-488f-b6f2-7b1872de5733 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Nov 3 23:05:26 samsung kernel: [ 5958.261114] perf samples too long (2517 2500), lowering kernel.perf_event_max_sample_rate to 5 dmi.bios.date: 02/08/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P06AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP06AAC:bd02/08/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247723/+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 1260610] Re: CVE-2013-2929
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1260610 Title: CVE-2013-2929 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package
[Kernel-packages] [Bug 1282243] Re: linux: 3.13.0-11.31 -proposed tracker
All builds are complete, packages in this bug are available in -proposed. ** Changed in: kernel-development-workflow/prepare-package Status: In Progress = Fix Released ** Changed in: kernel-development-workflow/package-testing Status: New = Confirmed ** Description changed: This bug is for tracking the 3.13.0-11.31 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:Wednesday, 19. February 2014 19:49 UTC - kernel-phase-changed:Wednesday, 19. February 2014 19:49 UTC - kernel-phase:Prepare + kernel-Package-testing-start:Thursday, 20. February 2014 09:00 UTC + kernel-phase:Testing + kernel-phase-changed:Thursday, 20. February 2014 09:00 UTC + kernel-Prepare-package-end:Thursday, 20. February 2014 09:00 UTC -- 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/1282243 Title: linux: 3.13.0-11.31 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: Confirmed 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-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-11.31 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:Wednesday, 19. February 2014 19:49 UTC kernel-Package-testing-start:Thursday, 20. February 2014 09:00 UTC kernel-phase:Testing kernel-phase-changed:Thursday, 20. February 2014 09:00 UTC kernel-Prepare-package-end:Thursday, 20. February 2014 09:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1282243/+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 1282243] Re: linux: 3.13.0-11.31 -proposed tracker
This bug was fixed in the package linux - 3.13.0-11.31 --- linux (3.13.0-11.31) trusty; urgency=low [ Colin Ian King ] * [config] Set IPMI suppoort default to y [ Tim Gardner ] * [Config] CONFIG_USER_NS=y for ppc64el * [Config] CONFIG_RESOURCE_COUNTERS=y for ppc64el * Release Tracking Bug - LP: #1282243 -- Tim Gardner tim.gard...@canonical.com Wed, 19 Feb 2014 12:04:43 -0500 ** Changed in: linux (Ubuntu Trusty) Status: New = 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/1282243 Title: linux: 3.13.0-11.31 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: In Progress 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-release series: New Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.13.0-11.31 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:Wednesday, 19. February 2014 19:49 UTC kernel-Package-testing-start:Thursday, 20. February 2014 09:00 UTC kernel-Prepare-package-end:Thursday, 20. February 2014 09:00 UTC kernel-phase:PPA Testing kernel-phase-changed:Thursday, 20. February 2014 10:00 UTC ppa-package-testing-start:Thursday, 20. February 2014 10:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1282243/+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 1282243] Re: linux: 3.13.0-11.31 -proposed tracker
** Changed in: kernel-development-workflow/package-testing Status: Confirmed = In Progress ** Description changed: This bug is for tracking the 3.13.0-11.31 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:Wednesday, 19. February 2014 19:49 UTC kernel-Package-testing-start:Thursday, 20. February 2014 09:00 UTC - kernel-phase:Testing - kernel-phase-changed:Thursday, 20. February 2014 09:00 UTC kernel-Prepare-package-end:Thursday, 20. February 2014 09:00 UTC + kernel-phase:PPA Testing + kernel-phase-changed:Thursday, 20. February 2014 10:00 UTC + ppa-package-testing-start:Thursday, 20. February 2014 10:00 UTC -- 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/1282243 Title: linux: 3.13.0-11.31 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: In Progress 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-release series: New Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.13.0-11.31 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:Wednesday, 19. February 2014 19:49 UTC kernel-Package-testing-start:Thursday, 20. February 2014 09:00 UTC kernel-Prepare-package-end:Thursday, 20. February 2014 09:00 UTC kernel-phase:PPA Testing kernel-phase-changed:Thursday, 20. February 2014 10:00 UTC ppa-package-testing-start:Thursday, 20. February 2014 10:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1282243/+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 1260613] Re: CVE-2013-2930
** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1260613 Title: CVE-2013-2930 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The perf_trace_event_perm function in kernel/trace/trace_event_perf.c in the Linux kernel before 3.12.2 does not properly restrict access to the perf subsystem, which allows local users to enable function tracing via a crafted application. Break-Fix:
[Kernel-packages] [Bug 1229981] Re: CVE-2013-4345
** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1229981 Title: CVE-2013-4345 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: Off-by-one error in the get_prng_bytes function in crypto/ansi_cprng.c in the Linux kernel through 3.11.4 makes it easier for context- dependent attackers to defeat cryptographic protection
[Kernel-packages] [Bug 1252422] Re: CVE-2013-4579
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1252422 Title: CVE-2013-4579 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The ath9k_htc_set_bssid_mask function in drivers/net/wireless/ath/ath9k/htc_drv_main.c in the Linux kernel through 3.12 uses a BSSID masking approach to determine the set of MAC
[Kernel-packages] [Bug 1282512] [NEW] Unsure
Public bug reported: Please check ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-10-generic 3.13.0-10.30 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: videotron 2734 F pulseaudio /dev/snd/controlC0: videotron 2734 F pulseaudio Date: Wed Feb 19 22:59:30 2014 DuplicateSignature: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:31] EIP: 0060:location EFLAGS: 0246 CPU: 1 Failure: oops HibernationDevice: RESUME=UUID=241563ea-626c-4979-a469-f97344eef17f InstallationDate: Installed on 2014-01-11 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: LENOVO 1450A7U ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9864d147-5614-4e11-9b8b-55e2160b47c8 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: kerneloops-daemon 0.12+git20090217-3ubuntu4 SourcePackage: linux StagingDrivers: rts5139 Title: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:31] UpgradeStatus: Upgraded to trusty on 2014-01-18 (33 days ago) dmi.bios.date: 05/12/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 52CN11WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr52CN11WW:bd05/12/2011:svnLENOVO:pn1450A7U:pvrLenovoB575:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 1450A7U dmi.product.version: Lenovo B575 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops staging trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282512 Title: Unsure Status in “linux” package in Ubuntu: New Bug description: Please check ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-10-generic 3.13.0-10.30 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: videotron 2734 F pulseaudio /dev/snd/controlC0: videotron 2734 F pulseaudio Date: Wed Feb 19 22:59:30 2014 DuplicateSignature: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:31] EIP: 0060:location EFLAGS: 0246 CPU: 1 Failure: oops HibernationDevice: RESUME=UUID=241563ea-626c-4979-a469-f97344eef17f InstallationDate: Installed on 2014-01-11 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: LENOVO 1450A7U ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9864d147-5614-4e11-9b8b-55e2160b47c8 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: kerneloops-daemon 0.12+git20090217-3ubuntu4 SourcePackage: linux StagingDrivers: rts5139 Title: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:31] UpgradeStatus: Upgraded to trusty on 2014-01-18 (33 days ago) dmi.bios.date: 05/12/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 52CN11WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr52CN11WW:bd05/12/2011:svnLENOVO:pn1450A7U:pvrLenovoB575:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 1450A7U dmi.product.version: Lenovo B575 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282512/+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 1281897] Re: linux-armadaxp: 3.5.0-1628.37 -proposed tracker
** Description changed: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 04:13 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 04:13 UTC kernel-stable-master-bug:1281828 + kernel-stable-Certification-testing-end:Thursday, 20. February 2014 11:03 UTC + kernel-stable-Security-signoff-end:Thursday, 20. February 2014 11:03 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1281897 Title: linux-armadaxp: 3.5.0-1628.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Quantal: In Progress Bug description: This bug is for tracking the 3.5.0-1628.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 04:13 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 04:13 UTC kernel-stable-master-bug:1281828 kernel-stable-Certification-testing-end:Thursday, 20. February 2014 11:03 UTC kernel-stable-Security-signoff-end:Thursday, 20. February 2014 11:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1281897/+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 1281965] Re: linux-armadaxp: 3.2.0-1631.43 -proposed tracker
** Summary changed: - linux-armadaxp: version to be filled -proposed tracker + linux-armadaxp: 3.2.0-1631.43 -proposed tracker ** Changed in: kernel-sru-workflow Assignee: (unassigned) = Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) = Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) = Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/upload-to-ppa Assignee: (unassigned) = Ike Panhc (ikepanhc) ** Changed in: kernel-sru-workflow/verification-testing Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) = Ike Panhc (ikepanhc) ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = In Progress ** Changed in: linux-armadaxp (Ubuntu Precise) Assignee: (unassigned) = Ike Panhc (ikepanhc) ** Description changed: - This bug is for tracking the version to be filled upload package. This - bug will contain status and testing results related to that upload. + This bug is for tracking the 3.2.0-1631.43 upload package. This bug will + contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 08:41 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 08:41 UTC kernel-stable-master-bug:1281800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1281965 Title: linux-armadaxp: 3.2.0-1631.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1631.43 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 08:41 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 08:41 UTC kernel-stable-master-bug:1281800 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1281965/+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 1281897] Re: linux-armadaxp: 3.5.0-1628.37 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Assignee: Canonical Hardware Enablement ARM Kernel (canonical-hwe-arm-kernel) = Ike Panhc (ikepanhc) ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: New = In Progress ** Changed in: linux-armadaxp (Ubuntu Quantal) Assignee: (unassigned) = Ike Panhc (ikepanhc) ** Description changed: - This bug is for tracking the version to be filled upload package. This - bug will contain status and testing results related to that upload. + This bug is for tracking the 3.5.0-1628.37 upload package. This bug will + contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 04:13 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 04:13 UTC kernel-stable-master-bug:1281828 kernel-stable-Certification-testing-end:Thursday, 20. February 2014 11:03 UTC kernel-stable-Security-signoff-end:Thursday, 20. February 2014 11:03 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1281897 Title: linux-armadaxp: 3.5.0-1628.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Quantal: In Progress Bug description: This bug is for tracking the 3.5.0-1628.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 04:13 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 04:13 UTC kernel-stable-master-bug:1281828 kernel-stable-Certification-testing-end:Thursday, 20. February 2014 11:03 UTC kernel-stable-Security-signoff-end:Thursday, 20. February 2014 11:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1281897/+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 1261564] Re: CVE-2013-4587
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1261564 Title: CVE-2013-4587 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description:
[Kernel-packages] [Bug 1254900] Re: CVE-2013-4592
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1254900 Title: CVE-2013-4592 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty:
[Kernel-packages] [Bug 1261566] Re: CVE-2013-6367
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1261566 Title: CVE-2013-6367 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The
[Kernel-packages] [Bug 1266399] Re: ext4-fs error messages pop up on command line
Haven't been observing the ext4 errors in the latest ubuntu_alpha2 build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1266399 Title: ext4-fs error messages pop up on command line Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Trusty: Incomplete Bug description: Description: === Adhoc ext4-fs errors seen on the command line: No particular pattern observed, pops up adhocly. EXT4-fs error (device sda): mb_free_blocks:1433: group 5, block 196603:freeing already freed block (bit 32763); block bitmap corrupt. EXT4-fs error (device sda): ext4_mb_generate_buddy:756: group 5, 3442 clusters in bitmap, 3444 in gd; block bitmap corrupt. Environment: Host: Power8 Guest : ubuntu hosted on Power8 Command line to spawn the ubuntu guest: qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=6c:ae:8b:69:16:11 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-ppc64el.img.qcow2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266399/+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 1261568] Re: CVE-2013-6368
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1261568 Title: CVE-2013-6368 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The KVM subsystem in the Linux kernel through 3.12.5 allows local users to gain privileges or cause a denial of service (system crash) via a VAPIC synchronization operation involving a page-end address. Break-Fix: -
[Kernel-packages] [Bug 1265544]
I notice that the bug hasn't been updated in a while, a patch that fixes the issue exists and can be integrated in the same way as bug 71049 (quirk-based bpp clamping bypass). Can this patch be reviewed integrated so that we can consider the issue fixed with this laptop and move on ? -- 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/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Triaged Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1265544/+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 1281965] Re: linux-armadaxp: 3.2.0-1631.43 -proposed tracker
** Description changed: This bug is for tracking the 3.2.0-1631.43 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 08:41 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 08:41 UTC kernel-stable-master-bug:1281800 + kernel-stable-Certification-testing-end:Thursday, 20. February 2014 12:04 UTC + kernel-stable-Security-signoff-end:Thursday, 20. February 2014 12:04 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1281965 Title: linux-armadaxp: 3.2.0-1631.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-armadaxp” source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1631.43 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Wednesday, 19. February 2014 08:41 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 19. February 2014 08:41 UTC kernel-stable-master-bug:1281800 kernel-stable-Certification-testing-end:Thursday, 20. February 2014 12:04 UTC kernel-stable-Security-signoff-end:Thursday, 20. February 2014 12:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1281965/+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 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))
Continue to see it ubuntu_alpha2 build: root@anasuya:~/ltp-full-20140115/testcases/kernel/syscalls/sigaltstack# uname -a Linux anasuya 3.13.0-10-generic #30-Ubuntu SMP Tue Feb 18 23:06:18 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux root@anasuya:~/ltp-full-20140115/testcases/kernel/syscalls/sigaltstack# root@anasuya:~/ltp-full-20140115/testcases/kernel/syscalls/sigaltstack# ./sigaltstack02 sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 -- 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/1267062 Title: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12)) Status in “eglibc” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: 9.3.189.114 (root/.pasroot) (Host Machine) Run the follwoing command to go to the guest victim machine from (/var/lib/libvirt/images/jagan/new_ubuntu_alpha1) qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr- vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg- ppc64el.img.qcow2 after this command you will get the screen number. example: QEMU 1.6.0 monitor - type 'help' for more information (qemu) char device redirected to /dev/pts/16 (label serial0) Then open another host session and execute the below command # screen /dev/pts/16 (qemu) Here the screen number is /dev/pts/16 --Then you will get a blank screen so press ENTER key. The guest machine login: ubuntu/passw0rd Then do ---sudo -i Environment: === Host: Power8 Guest : ubuntu hosted on Power8 The issue: == sigaltstack system call unable send proper return value. How to run : --cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack -- ./sigaltstack02 == Getting the below error sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 = FAIL test_start tag=sigaltstack02 stime=1386653793 cmdline=sigaltstack02 contacts= analysis=exit test_output sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 execution_status initiation_status=ok duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 test_end sigaltstack() should fail and set errno to ENOMEM when the size of alternate stack area is less than MINSIGSTKSZ. But here its sigaltstack() is returning 0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1267062/+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 1267910] Re: ping -R does not work to and from a ubuntu VM image
Ubuntu_alpah2 Guest: 192.168.122.250 Host :9.3.189.114 Continue to see the same issue: [root@localhost ~]# ping -R 192.168.122.250 PING 192.168.122.250 (192.168.122.250) 56(124) bytes of data. root@anasuya:/opt/ltp# ping -R 9.3.189.114 PING 9.3.189.114 (9.3.189.114) 56(124) bytes of data. Ping Data: root@anasuya:/opt/ltp# ping 9.3.189.114 PING 9.3.189.114 (9.3.189.114) 56(84) bytes of data. 64 bytes from 9.3.189.114: icmp_seq=1 ttl=64 time=0.150 ms 64 bytes from 9.3.189.114: icmp_seq=2 ttl=64 time=0.112 ms 64 bytes from 9.3.189.114: icmp_seq=3 ttl=64 time=0.135 ms ^C --- 9.3.189.114 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.112/0.132/0.150/0.018 ms root@anasuya:/opt/ltp# [root@localhost ~]# ping 192.168.122.250 PING 192.168.122.250 (192.168.122.250) 56(84) bytes of data. 64 bytes from 192.168.122.250: icmp_seq=1 ttl=64 time=0.166 ms ^C --- 192.168.122.250 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.166/0.166/0.166/0.000 ms [root@localhost ~]# uname -a root@anasuya:/opt/ltp# uname -a Linux anasuya 3.13.0-10-generic #30-Ubuntu SMP Tue Feb 18 23:06:18 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux root@anasuya:/opt/ltp# -- 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/1267910 Title: ping -R does not work to and from a ubuntu VM image Status in “linux” package in Ubuntu: Incomplete Bug description: Description: === The ping command with the -R option does not work to and from a Ubuntu guest. The command hangs and does not return. The following is the snapshot. [root@localhost test]# ping -R 192.168.122.182 PING 192.168.122.182 (192.168.122.182) 56(124) bytes of data. ^C --- 192.168.122.182 ping statistics --- 17 packets transmitted, 0 received, 100% packet loss, time 16006ms [root@localhost test]# root@ubuntu:/usr/lib/mysql-testsuite# ping -R 9.3.189.114 PING 9.3.189.114 (9.3.189.114) 56(124) bytes of data. ^C --- 9.3.189.114 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2003ms root@ubuntu:/usr/lib/mysql-testsuite# In the above snapshot 192.168.122.82 is the IP of the guest which is running with the ubuntu image. PING 9.3.189.114 (9.3.189.114) 56(124) bytes of data. ^C --- 9.3.189.114 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2003ms Environment: === Guest running ubuntu on a Power8 host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267910/+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 1281176] Re: 8086:2a02 [Dell Vostro 1310] no brightness control on (x)ubuntu 13.10
** Description changed:
- When I press the appropriate keys on keyboard (which ones specifically?)
- the slider appears on the upper right corner of the screen but the
- brightness doesn't change.
+ When I press the appropriate keys on keyboard (Fn+up/Fn+down) the slider
+ appears on the upper right corner of the screen but the brightness
+ doesn't change.
Problem is I have not intel_backlight on /sys/class/backlight folder but
just acpi_video0 or dell_backlight (if I set acpi_backlight=vendor on
grub). Since I don't have intel_backlight folder I can't apply many of
the workaround found here and there.
WORKAROUND: /sys/class/backlight$ for i in /sys/class/backlight/*; do
echo -e \n $i; cat $i/{brightness,max_brightness,actual_brightness};
done
/sys/class/backlight/dell_backlight
1
7
1
If I increase the backlight the files are correctly updated:
/sys/class/backlight/dell_backlight
7
7
7
acpi_listen works just on new mainline kernel 3.13.2 (tried bot generic and
lowlatency) on stock kernel there isn't output at all:
video/brightnessup BRTUP 0086 K
- video/brightnessup BRTUP 0086 K
- video/brightnessup BRTUP 0086 K
- video/brightnessdown BRTDN 0087 K
- video/brightnessdown BRTDN 0087 K
video/brightnessdown BRTDN 0087 K
Now I'm using xrandr to change the brightness:
xrandr --output LVDS1 --brightness 0.5
but since xrandr is a software overlay my battery life is horrible, I'm
stuck on 100% brightness. Beside this, sometimes the brightness slider
appears spontaneously without pressing any keys but again with no
effect.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.25
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: effe 1526 F pulseaudio
CurrentDmesg:
[ 102.704995] ERROR @wl_dev_intvar_get : error (-1)
[ 102.705003] ERROR @wl_cfg80211_get_tx_power : error (-1)
Date: Mon Feb 17 13:27:10 2014
HibernationDevice: RESUME=UUID=d0ee674f-0ea7-47e1-ba6f-1a849ba35941
InstallationDate: Installed on 2014-02-10 (6 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
MachineType: Dell Inc. Vostro1310
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic
root=UUID=44ccbe21-7e45-468c-b942-1773a32943b0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-15-generic N/A
linux-backports-modules-3.11.0-15-generic N/A
linux-firmware 1.116.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0K866H
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1310:pvrNull:rvnDellInc.:rn0K866H:rvr:cvnDellInc.:ct8:cvrN/A:
dmi.product.name: Vostro1310
dmi.product.version: Null
dmi.sys.vendor: Dell Inc.
--
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/1281176
Title:
8086:2a02 [Dell Vostro 1310] no brightness control on (x)ubuntu 13.10
Status in “linux” package in Ubuntu:
Triaged
Bug description:
When I press the appropriate keys on keyboard (Fn+up/Fn+down) the
slider appears on the upper right corner of the screen but the
brightness doesn't change.
Problem is I have not intel_backlight on /sys/class/backlight folder
but just acpi_video0 or dell_backlight (if I set acpi_backlight=vendor
on grub). Since I don't have intel_backlight folder I can't apply many
of the workaround found here and there.
WORKAROUND: /sys/class/backlight$ for i in /sys/class/backlight/*; do
echo -e \n $i; cat $i/{brightness,max_brightness,actual_brightness};
done
/sys/class/backlight/dell_backlight
1
7
1
If I increase the backlight the files are correctly updated:
/sys/class/backlight/dell_backlight
7
7
7
acpi_listen works just on new mainline kernel 3.13.2 (tried bot generic and
lowlatency) on stock kernel there isn't output at all:
video/brightnessup BRTUP 0086 K
video/brightnessdown BRTDN 0087 K
Now I'm using xrandr to change the brightness:
xrandr --output LVDS1 --brightness 0.5
but since xrandr is a software overlay my battery life is horrible,
I'm stuck on 100% brightness. Beside this, sometimes the brightness
slider appears spontaneously without pressing any keys but again with
no effect.
[Kernel-packages] [Bug 1261570] Re: CVE-2013-6376
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1261570 Title: CVE-2013-6376 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode.
[Kernel-packages] [Bug 1256080] Re: CVE-2013-6378
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1256080 Title: CVE-2013-6378 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1281729] Re: 8086:4238 [Lenovo ThinkPad T430s] iwlwifi using 802.11n associates with access point but network is unreachable
Behaviour has not changed after BIOS update. Right after I wrote comment #4, I lost the network, but cycling wifi via nm-applet brought it back. Things seemed to otherwise work yesterday, but this morning after resume from suspend it was back to the same: associated with my AP, but pages in browser do not load. I then ping the AP and get unreachable. $ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date G7ET98WW (2.58 ) 12/16/2013 # ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.10 icmp_seq=1 Destination Host Unreachable ^C --- 192.168.1.1 ping statistics --- 2 packets transmitted, 0 received, +1 errors, 100% packet loss, time 1001ms # iwconfig eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. wlan0 IEEE 802.11abgn ESSID: hidden Mode:Managed Frequency:2.437 GHz Access Point: hidden Bit Rate=78 Mb/s Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=70/70 Signal level=-34 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:26 Invalid misc:52 Missed beacon:0 # dmesg |tail [41713.948053] iwlwifi :03:00.0: L1 Enabled; Disabling L0S [41713.954762] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1 [41714.098900] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [41720.587581] wlan0: authenticate with hidden [41720.599843] wlan0: send auth to hidden (try 1/3) [41720.604907] wlan0: authenticated [41720.608100] wlan0: associate with hidden (try 1/3) [41720.611883] wlan0: RX AssocResp from hidden (capab=0x1411 status=0 aid=5) [41720.622822] wlan0: associated [41720.622892] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready -- 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/1281729 Title: 8086:4238 [Lenovo ThinkPad T430s] iwlwifi using 802.11n associates with access point but network is unreachable Status in “linux” package in Ubuntu: Incomplete Bug description: While the above bug appears to connect and then slow down eventually failing with packet loss, my problem is almost the opposite. If I can connect, it seems to work fine indefinitely, but initial connections (after suspend, or right after a reboot) only occasionally works. Sometimes, if I wait long enough the connection starts working after several minutes, sometimes it works if I turn off wireless and turn it back on, but often it just never works. According to dmesg, iwlwifi is associating with the access point just fine, but if I ping the ap, I get netowrk unreachable. WORKAROUND: 11n_disable=1 After associating, dmesg report: # dmesg |tail [101704.467324] iwlwifi :03:00.0: L1 Enabled; Disabling L0S [101704.474053] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1 [101704.621429] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101704.717787] wlan0: authenticate with xx:xx:xx:xx:xx:xx [101704.780532] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) [101704.793246] wlan0: authenticated [101704.797390] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3) [101704.798226] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x1011 status=0 aid=1) [101704.802300] wlan0: associated [101704.802347] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready But network is unreachable. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.25 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jdrogers 2276 F pulseaudio Date: Tue Feb 18 12:12:57 2014 HibernationDevice: RESUME=UUID=12dd9e3a-ab8c-468f-a7bc-f3c05e4bcddc InstallationDate: Installed on 2014-01-01 (47 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 2352CTO MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=b9c20532-4cfc-4833-830a-3d4500621c0e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET29WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 2352CTO dmi.board.vendor: LENOVO dmi.board.version: Not
[Kernel-packages] [Bug 1256083] Re: CVE-2013-6380
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1256083 Title: CVE-2013-6380 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Released Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid
[Kernel-packages] [Bug 1267075] Re: CVE-2013-7263
** Changed in: linux-ec2 (Ubuntu Lucid) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Lucid) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1267075 Title: CVE-2013-7263 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in
[Kernel-packages] [Bug 1267079] Re: CVE-2013-7265
** Changed in: linux-ec2 (Ubuntu Lucid) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Lucid) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1267079 Title: CVE-2013-7265 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in
[Kernel-packages] [Bug 1282586] [NEW] package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 N: Unable to locate package pkgname ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-10.30-lowlatency 3.13.3 Uname: Linux 3.13.0-10-lowlatency i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackmaxphoto 1838 F pulseaudio Date: Thu Feb 20 07:55:44 2014 DuplicateSignature: package:linux-image-3.13.0-11-lowlatency:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=9ff18643-77cc-4832-ad73-cf0faf20ad66 InstallationDate: Installed on 2014-01-30 (20 days ago) InstallationMedia: Ubuntu-Studio 14.04 Trusty Tahr - Alpha i386 (20140129) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: VIA Technologies, Inc. P4M266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-10-lowlatency root=UUID=cae5b763-046c-409b-b908-fff26ed08b4b 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: grub-pc 2.02~beta2-6 RfKill: SourcePackage: linux SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: P4M266-8235 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/20/2003:svnVIATechnologies,Inc.:pnP4M266-8235:pvr:rvn:rnP4M266-8235:rvr:cvn:ct3:cvr: dmi.product.name: P4M266-8235 dmi.sys.vendor: VIA Technologies, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282586 Title: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in “linux” package in Ubuntu: New Bug description: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 N: Unable to locate package pkgname ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-10.30-lowlatency 3.13.3 Uname: Linux 3.13.0-10-lowlatency i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackmaxphoto 1838 F pulseaudio Date: Thu Feb 20 07:55:44 2014 DuplicateSignature: package:linux-image-3.13.0-11-lowlatency:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=9ff18643-77cc-4832-ad73-cf0faf20ad66 InstallationDate: Installed on 2014-01-30 (20 days ago) InstallationMedia: Ubuntu-Studio 14.04 Trusty Tahr - Alpha i386 (20140129) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: VIA Technologies, Inc. P4M266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-10-lowlatency root=UUID=cae5b763-046c-409b-b908-fff26ed08b4b 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: grub-pc 2.02~beta2-6 RfKill: SourcePackage: linux SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: P4M266-8235 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/20/2003:svnVIATechnologies,Inc.:pnP4M266-8235:pvr:rvn:rnP4M266-8235:rvr:cvn:ct3:cvr: dmi.product.name: P4M266-8235 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282586/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1276705] Re: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
I can not test this kernel, it was only build for i386. The server is installed with amd64 :( Because of timezone difference we can only test one kernel per day, to speed up the bisect, I've done one by myself, the result is the following: $ git bisect log # bad: [6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae] Linux 3.13-rc1 # good: [5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52] Linux 3.12 git bisect start 'v3.13-rc1' 'v3.12' '--' 'drivers/scsi' # good: [53151bbb83f11b358ac94eddd81347c581dc51ea] [SCSI] lpfc 8.3.43: Fixed not processing task management IOCB response status git bisect good 53151bbb83f11b358ac94eddd81347c581dc51ea # good: [323f6226a816f0b01514d25fba5529e0e68636c3] Merge tag 'fcoe-3.13' into for-linus git bisect good 323f6226a816f0b01514d25fba5529e0e68636c3 [Above this point, I didn't build kernel. It was the result from your kernel. Bellow the result are from kernel compiled by myself] # bad: [2f466d33f5f60542d3d82c0477de5863b22c94b9] Merge tag 'pci-v3.13-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci git bisect bad 2f466d33f5f60542d3d82c0477de5863b22c94b9 # bad: [0910c0bdf7c291a41bc21e40a97389c9d4c1960d] Merge branch 'for-3.13/core' of git://git.kernel.dk/linux-block git bisect bad 0910c0bdf7c291a41bc21e40a97389c9d4c1960d # good: [0324e74534241f3f00910ec04ef67de1fe1542f4] Merge tag 'driver-core-3.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core git bisect good 0324e74534241f3f00910ec04ef67de1fe1542f4 # good: [e37459b8e2c7db6735e39e019e448b76e5e77647] Merge branch 'blk-mq/core' into for-3.13/core git bisect good e37459b8e2c7db6735e39e019e448b76e5e77647 # bad: [8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587] Merge branch 'for-linus-dma-masks' of git://git.linaro.org/people/rmk/linux-arm git bisect bad 8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587 # good: [7d35496dd98229cdf923238367fd3b3833fbde52] ARM: 7796/1: scsi: Use dma_max_pfn(dev) helper for bounce_limit calculations git bisect good 7d35496dd98229cdf923238367fd3b3833fbde52 # first bad commit: [8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587] Merge branch 'for-linus-dma-masks' of git://git.linaro.org/people/rmk/linux-arm From my bisect, the commit which introduced the error is 8ceafbfa91ffbdbb2afaea5c24ccb519ffb8b587. For information, to build the kernel I did the following: git remote add ubuntu-trusty git://kernel.ubuntu.com/ubuntu/ubuntu- trusty.git git checkout ubuntu-trusty/master -- debian git checkout ubuntu-trusty/master -- debian.master fakeroot debian/rules clean defaultconfigs fakeroot debian/rules binary-generic skipmodule=true Build area was cleaned after each build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276705 Title: Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR) Status in “linux” package in Ubuntu: Confirmed Bug description: We have recently upgraded an Dell R300 server to Trusty (was running fine in precise), and after upgrade it fail to boot. It is an issue with the SAS controller during the initilisation. It fail to detect the disk, we have the following error in console log: [ 36.539955] scsi4: error handler thread failed to spawn, error = -12 [ 36.552694] mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem After this error, initramfs drop to a shell complaining that rootfs is not found. No disk is seen at all (cat /proc/partition only show sr0 - cdrom drive). We have this issue with two different server (both R300, both Dell SAS 6/iR controller and same hardware). We don't have this issue with another Dell server (R310, Dell PERC H200). We also tester with old kernel (generic, 3.2.0-58.88), it is working. Those server need a greater rootdelay (probably #579572), so we have rootdelay=45. If we remove rootdelay=45, then disk are correctly recognized ! (but few second too late, initramfs dropped to a shell. Pressing control-D resume normal boot) So the issue is that with the (mandatory) rootdelay greater that 30 (default value I think), the disk are not detected due to the error shown above. This is a regression since those server worked in precise (and work with precise old kernel). System information * Dell R300 with Dell SAS 6/iR controller * Ubuntu Trusty Tahr (14.04) * Running arch: x86_64 * Kernel version: 3.13.0-7-generic (dpkg version : 3.13.0-7.25) * Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-7-generic root=UUID=174e14b5-46fc-479b-9f94-05cb33c75ac9 ro rootdelay=45 console=tty0 console=ttyS1,57600 quiet * uname -a: Linux frtls-perf01 3.13.0-7-generic #25-Ubuntu SMP Tue Feb 4 10:19:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Attached files: * console output when error occure. * dmesg when system boot (no rootdelay, need to press control-d during initramfs boot) * lspci -vnn Tell me if you need more
[Kernel-packages] [Bug 1282586] Re: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- 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/1282586 Title: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in “linux” package in Ubuntu: New Bug description: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 N: Unable to locate package pkgname ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-10.30-lowlatency 3.13.3 Uname: Linux 3.13.0-10-lowlatency i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackmaxphoto 1838 F pulseaudio Date: Thu Feb 20 07:55:44 2014 DuplicateSignature: package:linux-image-3.13.0-11-lowlatency:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=9ff18643-77cc-4832-ad73-cf0faf20ad66 InstallationDate: Installed on 2014-01-30 (20 days ago) InstallationMedia: Ubuntu-Studio 14.04 Trusty Tahr - Alpha i386 (20140129) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: VIA Technologies, Inc. P4M266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-10-lowlatency root=UUID=cae5b763-046c-409b-b908-fff26ed08b4b 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: grub-pc 2.02~beta2-6 RfKill: SourcePackage: linux SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: P4M266-8235 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/20/2003:svnVIATechnologies,Inc.:pnP4M266-8235:pvr:rvn:rnP4M266-8235:rvr:cvn:ct3:cvr: dmi.product.name: P4M266-8235 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282586/+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 1282586] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282586 Title: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in “linux” package in Ubuntu: Confirmed Bug description: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 N: Unable to locate package pkgname ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-10.30-lowlatency 3.13.3 Uname: Linux 3.13.0-10-lowlatency i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackmaxphoto 1838 F pulseaudio Date: Thu Feb 20 07:55:44 2014 DuplicateSignature: package:linux-image-3.13.0-11-lowlatency:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=9ff18643-77cc-4832-ad73-cf0faf20ad66 InstallationDate: Installed on 2014-01-30 (20 days ago) InstallationMedia: Ubuntu-Studio 14.04 Trusty Tahr - Alpha i386 (20140129) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: VIA Technologies, Inc. P4M266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-10-lowlatency root=UUID=cae5b763-046c-409b-b908-fff26ed08b4b 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: grub-pc 2.02~beta2-6 RfKill: SourcePackage: linux SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: package linux-image-3.13.0-11-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: P4M266-8235 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/20/2003:svnVIATechnologies,Inc.:pnP4M266-8235:pvr:rvn:rnP4M266-8235:rvr:cvn:ct3:cvr: dmi.product.name: P4M266-8235 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282586/+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 1281198] [NEW] Mouse Primary Button Will Not Switch to Right Button
You have been subscribed to a public bug: After doing a partial distribution upgrade on Trusty Tahr, the mouse buttons worked inconsistently. The system is set for the right mouse button to be the primary. However, from the Launcher and desktop only the left mouse button launched applications or displayed the desktop menu. The right mouse button was primary once int Settings, but going to Settings, Mouse and Touchpad and then switching the buttons back and forth did not resolves the issue. Setting the primary mouse button to Right worked fine prior to the upgrade. The mouse and keyboard are Logitech wireless M185 (mouse) and K270 (keyboard). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.210 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Feb 17 12:06:25 2014 InstallationDate: Installed on 2013-12-08 (71 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-01-25 (23 days ago) VarLogDistupgradeTermlog: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty -- Mouse Primary Button Will Not Switch to Right Button https://bugs.launchpad.net/bugs/1281198 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1273836] [NEW] Ubuntu 14.04 installation hangs with Pango WARNING
You have been subscribed to a public bug: Downloaded Ubuntu 14.04 Alpha Gnome Desktop iso from omgubuntu. Tried installing on a Dell laptop and an Compaq Qube mini desktop. Doesn't even get to the screen where you choose Try or Install Ubuntu. It hangs at the message: (process:186): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin' Both of these computers have had Ubuntu installed before. The Qube had 10.04 for several years, and I was most happy with it. I only decided to upgrade as it's no longer supported. I wish I hadn't bothered as it's been nothing but trouble ever since. I liked 10.04, but Unity is horrible, I've tried 11, 12, 13 and now 14, and I'm now considering moving away from Ubuntu. I've downgraded to 12.10, which is also no longer supported, but remains the most recent version that runs successfully. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 14.04 installation hangs with Pango WARNING https://bugs.launchpad.net/bugs/1273836 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1281797] Re: linux: 2.6.32-57.119 -proposed tracker
Hardware Certification won't be testing this kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = Invalid -- 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/1281797 Title: linux: 2.6.32-57.119 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-57.119 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 18. February 2014 21:31 UTC kernel-stable-Prepare-package-end:Wednesday, 19. February 2014 07:43 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 19. February 2014 07:43 UTC ppa-package-testing-start:Wednesday, 19. February 2014 08:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 19. February 2014 10:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Verification-testing-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Certification-testing-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Security-signoff-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Regression-testing-start:Wednesday, 19. February 2014 11:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1281797/+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 1267082] Re: CVE-2013-7267
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1267082 Title: CVE-2013-7267 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The
[Kernel-packages] [Bug 1162073] Re: [NP900X4C-A04US] System freeze on high memory usage
I experience this as well, latest Ubuntu. When data goes to swap, the entire system freezes. ** Changed in: linux (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1162073 Title: [NP900X4C-A04US] System freeze on high memory usage Status in “linux” package in Ubuntu: Confirmed Bug description: When I use MATLAB and all 8GB of RAM are full, system freezes and only a hard restart can get it working. I have found that the same bug is around since 2007 in the bug report at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356, but it was not fixed. Since Christopher M. Penalver insisted for re-reporting the bug and none have done it yet, I decided to report it. I have tested it with the newest kernel http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.9-rc4-raring/ and it still persists. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-26-generic 3.5.0-26.42 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ivan 2469 F pulseaudio Date: Sat Mar 30 00:49:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4def1db0-01fa-4505-8eb6-97442bc58e4a InstallationDate: Installed on 2013-02-28 (29 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=4936fe74-689d-4768-951a-d793b24ad3cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-26-generic N/A linux-backports-modules-3.5.0-26-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04AAC:bd08/08/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1162073/+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 1266120] [NEW] System freezes when Suspending or Hibernating (WIFI driver glitch?)
You have been subscribed to a public bug: Hello, My system freezes everytime I try to run #pm-suspend or #pm- hibernate. Generally, I am forced to perform a hard shutdown of my system to get it working again. However, if I remove my USB WI-FI adaptor before hand, all is well. I'm currently using a Netgear WNA 1100 (http://wikidevi.com/wiki/Netgear_WNA1100), which is connected to a USB 3.0 PCI Hub, A sebrent CP4-TU (which, I believe is a rebranded Fresco Logic FL1100 device, as I have to use FL1100 drivers on Windows), but have tried plugging the device directly into one of my computer's built- in ports with the same results. I'm currently running Ubuntu 13.10, x64 desktop edition. I've tested this device using the 3.11.0-14, and the 3.11.0-15 kernels. Please let me know if there's any more information I can provide to help resolve this issue. It may be worth noting that this bug might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251684 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- System freezes when Suspending or Hibernating (WIFI driver glitch?) https://bugs.launchpad.net/bugs/1266120 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1273836] Re: Ubuntu 14.04 installation hangs with Pango WARNING
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** 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/1273836 Title: Ubuntu 14.04 installation hangs with Pango WARNING Status in “linux” package in Ubuntu: Incomplete Bug description: Downloaded Ubuntu 14.04 Alpha Gnome Desktop iso from omgubuntu. Tried installing on a Dell laptop and an Compaq Qube mini desktop. Doesn't even get to the screen where you choose Try or Install Ubuntu. It hangs at the message: (process:186): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin' Both of these computers have had Ubuntu installed before. The Qube had 10.04 for several years, and I was most happy with it. I only decided to upgrade as it's no longer supported. I wish I hadn't bothered as it's been nothing but trouble ever since. I liked 10.04, but Unity is horrible, I've tried 11, 12, 13 and now 14, and I'm now considering moving away from Ubuntu. I've downgraded to 12.10, which is also no longer supported, but remains the most recent version that runs successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273836/+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 1273836] Re: Ubuntu 14.04 installation hangs with Pango WARNING
The package is linux. ** Description changed: Downloaded Ubuntu 14.04 Alpha Gnome Desktop iso from omgubuntu. - Tried installing on a Dell laptop and an Compaq Qube mini desktop. Doesn't even get to the screen where you choose Try or Install Ubuntu, hangs at the message: + + Tried installing on a Dell laptop and an Compaq Qube mini desktop. Doesn't even get to the screen where you choose Try or Install Ubuntu. It hangs at the message: (process:186): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin' - Both of these computers have had Ubuntu installed before. The Qube had 10.04 for several years, and I was most happy with it. I only decided to upgrade as it's no longer supported. - I wish I hadn't bothered as it's been nothing but trouble ever since. I liked 10.04, but Unity is horrible, I've tried 11, 12, 13 and now 14, and I'm now considering moving away from Ubuntu. - I've downgraded to 12.10, which is also no longer supported, but the most recent version which will run successfully. + + Both of these computers have had Ubuntu installed before. The Qube had + 10.04 for several years, and I was most happy with it. I only decided + to upgrade as it's no longer supported. + + I wish I hadn't bothered as it's been nothing but trouble ever since. I + liked 10.04, but Unity is horrible, I've tried 11, 12, 13 and now 14, + and I'm now considering moving away from Ubuntu. + + I've downgraded to 12.10, which is also no longer supported, but remains + the most recent version that runs successfully. ** Package changed: ubuntu = linux (Ubuntu) ** Tags added: kernel-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1273836 Title: Ubuntu 14.04 installation hangs with Pango WARNING Status in “linux” package in Ubuntu: Incomplete Bug description: Downloaded Ubuntu 14.04 Alpha Gnome Desktop iso from omgubuntu. Tried installing on a Dell laptop and an Compaq Qube mini desktop. Doesn't even get to the screen where you choose Try or Install Ubuntu. It hangs at the message: (process:186): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin' Both of these computers have had Ubuntu installed before. The Qube had 10.04 for several years, and I was most happy with it. I only decided to upgrade as it's no longer supported. I wish I hadn't bothered as it's been nothing but trouble ever since. I liked 10.04, but Unity is horrible, I've tried 11, 12, 13 and now 14, and I'm now considering moving away from Ubuntu. I've downgraded to 12.10, which is also no longer supported, but remains the most recent version that runs successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273836/+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 1281198] Re: Mouse Primary Button Will Not Switch to Right Button
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Package changed: ubuntu = linux (Ubuntu) ** Tags added: kernel-input ** 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/1281198 Title: Mouse Primary Button Will Not Switch to Right Button Status in “linux” package in Ubuntu: Incomplete Bug description: After doing a partial distribution upgrade on Trusty Tahr, the mouse buttons worked inconsistently. The system is set for the right mouse button to be the primary. However, from the Launcher and desktop only the left mouse button launched applications or displayed the desktop menu. The right mouse button was primary once int Settings, but going to Settings, Mouse and Touchpad and then switching the buttons back and forth did not resolves the issue. Setting the primary mouse button to Right worked fine prior to the upgrade. The mouse and keyboard are Logitech wireless M185 (mouse) and K270 (keyboard). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.210 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Feb 17 12:06:25 2014 InstallationDate: Installed on 2013-12-08 (71 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-01-25 (23 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1281198/+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 1266120] Re: System freezes when Suspending or Hibernating (WIFI driver glitch?)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug. Please run the following command which will attach necessary information: apport-collect BUGNUMBER if you are using Karmic Koala (9.10) or newer, or apport-collect -p linux-image-`uname -r` BUGNUMBER if you are using Hardy Heron (8.04) Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python- launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to Change Non-Private data as it will be adding information to your bug report. If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options): First run the following commands: 1) uname -a uname-a.log 2) dmesg dmesg.log 3) sudo lspci -vvnn lspci-vvnn.log 4) cat /proc/version_signature version.log then attach the files separately to the bug report (not pasted into comments or tar/zip-ed). For your reference, the full description of procedures for kernel- related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance! ** Package changed: 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/1266120 Title: System freezes when Suspending or Hibernating (WIFI driver glitch?) Status in “linux” package in Ubuntu: Incomplete Bug description: Hello, My system freezes everytime I try to run #pm-suspend or #pm- hibernate. Generally, I am forced to perform a hard shutdown of my system to get it working again. However, if I remove my USB WI-FI adaptor before hand, all is well. I'm currently using a Netgear WNA 1100 (http://wikidevi.com/wiki/Netgear_WNA1100), which is connected to a USB 3.0 PCI Hub, A sebrent CP4-TU (which, I believe is a rebranded Fresco Logic FL1100 device, as I have to use FL1100 drivers on Windows), but have tried plugging the device directly into one of my computer's built-in ports with the same results. I'm currently running Ubuntu 13.10, x64 desktop edition. I've tested this device using the 3.11.0-14, and the 3.11.0-15 kernels. Please let me know if there's any more information I can provide to help resolve this issue. It may be worth noting that this bug might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266120/+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 1267085] Re: CVE-2013-7269
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1267085 Title: CVE-2013-7269 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: The
[Kernel-packages] [Bug 1281797] Re: linux: 2.6.32-57.119 -proposed tracker
** Description changed: This bug is for tracking the 2.6.32-57.119 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 18. February 2014 21:31 UTC kernel-stable-Prepare-package-end:Wednesday, 19. February 2014 07:43 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 19. February 2014 07:43 UTC ppa-package-testing-start:Wednesday, 19. February 2014 08:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 19. February 2014 10:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Verification-testing-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Certification-testing-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Security-signoff-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Regression-testing-start:Wednesday, 19. February 2014 11:01 UTC + kernel-stable-Certification-testing-end:Thursday, 20. February 2014 15:00 UTC -- 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/1281797 Title: linux: 2.6.32-57.119 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-57.119 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 18. February 2014 21:31 UTC kernel-stable-Prepare-package-end:Wednesday, 19. February 2014 07:43 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 19. February 2014 07:43 UTC ppa-package-testing-start:Wednesday, 19. February 2014 08:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 19. February 2014 10:00 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Verification-testing-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Certification-testing-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Security-signoff-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Regression-testing-start:Wednesday, 19. February 2014 11:01 UTC kernel-stable-Certification-testing-end:Thursday, 20. February 2014 15:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1281797/+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 1162073] Re: [NP900X4C-A04US] System freeze on high memory usage
I am quite sure that this problem is related to my RAID configuration. I'm waiting for the next LTS to remove the RAID to try to fix this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1162073 Title: [NP900X4C-A04US] System freeze on high memory usage Status in “linux” package in Ubuntu: Confirmed Bug description: When I use MATLAB and all 8GB of RAM are full, system freezes and only a hard restart can get it working. I have found that the same bug is around since 2007 in the bug report at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356, but it was not fixed. Since Christopher M. Penalver insisted for re-reporting the bug and none have done it yet, I decided to report it. I have tested it with the newest kernel http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.9-rc4-raring/ and it still persists. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-26-generic 3.5.0-26.42 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ivan 2469 F pulseaudio Date: Sat Mar 30 00:49:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4def1db0-01fa-4505-8eb6-97442bc58e4a InstallationDate: Installed on 2013-02-28 (29 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=4936fe74-689d-4768-951a-d793b24ad3cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-26-generic N/A linux-backports-modules-3.5.0-26-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04AAC:bd08/08/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1162073/+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 1282624] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282624 Title: [ASUSTeK COMPUTER INC. 1025C] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: [ASUSTeK COMPUTER INC. 1025C] suspend/resume failure ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-10-generic 3.13.0-10.30 ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubun 1964 F mixer_applet2 xubun 2082 F pulseaudio Date: Thu Feb 20 18:51:55 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=90ef389c-39ce-49cb-bcc5-b2105ee9c5d7 InstallationDate: Installed on 2014-01-14 (37 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140113) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK COMPUTER INC. 1025C ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 psbdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-10-generic root=UUID=fb60c42b-dc1f-45cf-8546-11e1f50058f5 ro quiet splash 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-10-generic N/A linux-backports-modules-3.13.0-10-generic N/A linux-firmware 1.125 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. 1025C] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1025C.0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1025C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1025C.0801:bd03/08/2012:svnASUSTeKCOMPUTERINC.:pn1025C:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x: dmi.product.name: 1025C dmi.product.version: x.x dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282624/+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 1245081] Re: macbook keyboard layout maps the tilde key to something else
According to this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1025041
According to an upstream bug report, the ANSI/ISO detection of the
keyboard is incorrect.
there's a walk-around:
echo 0 /sys/module/hid_apple/parameters/iso_layout
I can confirm that this fixes the problem on macbook air 6,2 (2013) with
ubuntu 13.10.
** Bug watch added: Red Hat Bugzilla #1025041
https://bugzilla.redhat.com/show_bug.cgi?id=1025041
--
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/1245081
Title:
macbook keyboard layout maps the tilde key to something else
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
1. install ubuntu on Macbook Air 6,2
2. press the key with the tilde ('~') written on it.
3. see that is prints '§' instead.
This is particularly annoying since the way to switch between windows uses
the tilde.
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kms1491 F pulseaudio
/dev/snd/controlC1: kms1491 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=9e7b2d0e-6a44-4ad7-9725-f9a3f5f39c33
InstallationDate: Installed on 2013-10-25 (1 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64+mac
(20131016.1)
MachineType: Apple Inc. MacBookAir6,2
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux 3.11.0.12.13
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic
root=UUID=079cbe6b-6488-4e57-85d3-c3e3e2fcbe40 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
RelatedPackageVersions:
linux-restricted-modules-3.11.0-12-generic N/A
linux-backports-modules-3.11.0-12-generic N/A
linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/12/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0099.B01.1307121317
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B01.1307121317:bd07/12/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.name: MacBookAir6,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/1245081/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Hey Jason! Thanks! Could you please re-assign this bug, then, to Samantha or Rod? And Samantha/Rod, could you please update the status (in-progress) when you're working on it? That helps those of us here watching/waiting for this work to complete :-) Thanks! Dustin -- 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: In Progress Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1271519] Re: Restore old recvmsg behavior after CVE-2013-7266 fix is applied
** Changed in: linux-armadaxp (Ubuntu Precise) Status: Confirmed = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1271519 Title: Restore old recvmsg behavior after CVE-2013-7266 fix is applied Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-ti-omap4” source package in Precise: Confirmed Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Confirmed Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Confirmed Bug description: After commit f3d3342602f8bcbf37d7c46641cb9bca7618eb1c (net: rework recvmsg handler msg_name and msg_namelen logic), which fixes CVE-2013-7266 to CVE-2013-7271, we end up with a bug in the af_rose. Upstream commit f81152e35001e91997ec74a7b4e040e6ab0acccf restores the old behaviour in net/rose/af_rose.c and should get applied to all the series that got these CVEs fixed. break-fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c break-fix: f3d3342602f8bcbf37d7c46641cb9bca7618eb1c f81152e35001e91997ec74a7b4e040e6ab0acccf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271519/+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 1269053] Re: IBM Domino 'bindsock' cannot bind to ports 1024 since recent kernel 3.5.0-45.68
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1269053 Title: IBM Domino 'bindsock' cannot bind to ports 1024 since recent kernel 3.5.0-45.68 Status in “linux” package in Ubuntu: Fix Released Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Confirmed Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Bug description: Something has changed in Ubuntu's Kernel 3.5.0-45 32 64-bit Intel, has prevented IBM Domino's /opt/ibm/domino/notes/latest/linux/bindsock binary that runs as root (setuid) to get ports lower than 1024 for it's LDAP, SMTP, IMAP, POP3, and HTTP processes. The IBM Domino Application Server's parent process /opt/ibm/domino/notes/latest/linux/server runs as a Service Account or a normal non-admin user, that launches bindsockand others like http, ldap In the Live Domino Console we're seeing the Application Server report: Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege. Another thing in the Live Domino Console, which is unusual is: Error_CmdToDo_INVAL... might be an IBM thang. A number of us have to hold back the kernel now and there's lots of scratching going on. http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=485F5F092833BCBE85257C33006AC7A3 It does seem to be limited to IBM Domino's bindsock binary and other things are just fine, such as Nginx. I have attached some files within the zip ibm-domino-bindsock_strace.zip bindsock_binary_strace.txt This is just running strace against the binary that isn't running in any process. domino-server-pid1052_strace-f.txt The IBM Domino Application Server (/opt/ibm/domino/notes/latest/linux/server) is running as PID 1052 so this is what I applied strace -f to and towards the end, I told server to start the http process (l http) which would then try launch bindsock (I hope). Hopeully this first attempt at strace provides some good info for you kind folks :-) Many thanks MR ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-45-generic 3.5.0-45.68~precise1 ProcVersionSignature: Ubuntu 3.5.0-45.68~precise1-generic 3.5.7.26 Uname: Linux 3.5.0-45-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
[Kernel-packages] [Bug 1279081] Re: linux freezes with threadirqs parameter when rt73usb is loaded
It would be good to know if when using the threadirqs parameter is a regression. If that is the case, we can bisect to identify the commit that introduced this. Can you test the following kernels with the threadirqs parameter enabled and post back if any do not exhibit the bug: v3.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/ v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/ v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ You don't have to test every kernel, just up until the kernel that first has this bug. If 3.2 has the bug, no need to test the rest. Thanks 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/1279081 Title: linux freezes with threadirqs parameter when rt73usb is loaded Status in “linux” package in Ubuntu: Confirmed Bug description: While my usb wifi device is connected, the kernel will freeze while booting. I can boot into recovery mode, but freeze happens as soon as I enable networking. I can boot and login fine without the device attached. As soon as I plug it in, the system freezes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-lowlatency 3.13.0.8.12 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zequence 2598 F pulseaudio /dev/snd/controlC2: zequence 2598 F pulseaudio /dev/snd/controlC0: zequence 2598 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: GNOME Date: Tue Feb 11 22:02:39 2014 HibernationDevice: RESUME=UUID=ede81b37-17df-4f30-a234-1f1fb7f003ad MachineType: Gigabyte Technology Co., Ltd. 965P-DS4 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=7e51aea4-9325-401e-b318-bbf42e368c45 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-11 (123 days ago) dmi.bios.date: 06/25/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: 965P-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965P-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279081/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Hey Dustin - I reassigned to David since I'm not sure who will be testing it. David/Samantha/Rod - please reassign to whoever is doing the test! ** Changed in: maas Status: Triaged = In Progress ** Changed in: maas Assignee: Jason Hobbs (jason-hobbs) = David Duffey (david-duffey) -- 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: In Progress Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1275116] Re: lowlatency-flavour crashes and locks up alot
It would be good to know if when using the threadirqs parameter is a regression. If that is the case, we can bisect to identify the commit that introduced this. Can you test the following kernels with the threadirqs parameter enabled and post back if any do not exhibit the bug: v3.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/ v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/ v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ You don't have to test every kernel, just up until the kernel that first has this bug. If 3.2 has the bug, no need to test the rest. Thanks 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/1275116 Title: lowlatency-flavour crashes and locks up alot Status in “linux” package in Ubuntu: Confirmed Status in “linux-lowlatency” package in Ubuntu: Confirmed Bug description: The 3.11 flavour that where upgraded to 3.13 today crashed 10 times this morning. I have the crashdums, but I figured that it might have been solved in 3.13. Unfortunatly it seems like it is not. I will add crashdumps when I get crashes that do not just lockup the machine but currently I have only seem complete lockups with 3.13 So the essense is : 3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text. 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sgh2176 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 31 23:38:10 2014 InstallationDate: Installed on 2013-12-24 (38 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) MachineType: LENOVO 2356GCG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+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 1274987] Re: can't boot with new lowlatency kernel
It would be good to know if when using the threadirqs parameter is a regression. If that is the case, we can bisect to identify the commit that introduced this. Can you test the following kernels with the threadirqs parameter enabled and post back if any do not exhibit the bug: v3.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/ v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/ v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ You don't have to test every kernel, just up until the kernel that first has this bug. If 3.2 has the bug, no need to test the rest. Thanks 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/1274987 Title: can't boot with new lowlatency kernel Status in “linux” package in Ubuntu: Confirmed Bug description: with the new 3.13.0-6-lowlatency i cant boot. it choose and shows up plymouth (or some text, if i disable plymout) next the computer hungs up completely. no SysRq. only a hard turn off. the same generic kernel works without problems ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-lowlatency 3.13.0-6.23 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabi 2400 F pulseaudio /dev/snd/controlC1: fabi 2400 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 31 16:59:44 2014 HibernationDevice: RESUME=UUID=1db62c66-60db-4cfe-bde9-72d501cc14cc InstallationDate: Installed on 2013-12-12 (50 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. OptiPlex 760 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=5293cdc9-6817-4800-8809-b1d291d3a7e0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0F373D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/21/2012:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0F373D:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274987/+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 1274752] Re: Hyper-V Submissions for 14.04
** Description changed: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html + + === + Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c + Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c ** Description changed: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html === + b) Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c + c) + Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 ** Tags added: kernel-bug-break-fix ** Description changed: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html === + a) b) Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 + d) + e) + Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 + f) -- 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/1274752 Title: Hyper-V Submissions for 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html === a) b) Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: -
[Kernel-packages] [Bug 1275116] Re: lowlatency-flavour crashes and locks up alot
Trying -- 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/1275116 Title: lowlatency-flavour crashes and locks up alot Status in “linux” package in Ubuntu: Confirmed Status in “linux-lowlatency” package in Ubuntu: Confirmed Bug description: The 3.11 flavour that where upgraded to 3.13 today crashed 10 times this morning. I have the crashdums, but I figured that it might have been solved in 3.13. Unfortunatly it seems like it is not. I will add crashdumps when I get crashes that do not just lockup the machine but currently I have only seem complete lockups with 3.13 So the essense is : 3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text. 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sgh2176 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 31 23:38:10 2014 InstallationDate: Installed on 2013-12-24 (38 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) MachineType: LENOVO 2356GCG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+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 1269777] Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only Filesystem
Hi,
[Crucial M500 - a hope? - NO]
---
after returning the Samsung and found this thread in the lenovo forum:
http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/W510-SSD-My-
Story/m-p/1402387
my hope was the Crucial M500 should be compatible to the W510:
http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=AC617B31A5CA7304
Unfortunately, I encounterd the very same problems like with the other SSD's.
The ata port hard resets and the SSD goes into read-only state after a certain
amount of time.
More or less stable I could get things running with turning PCIe
powermanagement off in the BIOS an using libata.force=noncq as kernel
boot parameters. Nevertheless the system freezes from time to time.
I will open a new bug report for this drive as soon as the
[Contacting Lenovo support]
---
The lenovo support stated, that only very special SSDs from Intel with a
capacity of 160GB are compatible with this device.
So no help from lenovo.
[FURTHER TESTING]
-
Since the fact, that an older drive, the Samsung 830 is running fine in
a laptop (Lenovo X201, i7) with the same laptop, I tested all drives
(Samsung 840 EVO, PRO and the Crucial M500 480) in the X201. Same
problem there. So it IS DEFINITELY an incompatibility with the drive and
the machine / chipset / kernel.
Within the next weeks, I will try an older Crucial M4 256GB in the W510.
This is an older drive model like the Samsung 830 and probably will work.
[OPINION]
---
Comming across certain threads, this problem is very common an occurs here and
there with certain chipsets.
I don't think it is a problem of the linux kernel, but probably could be fixed?
I will post my results about the Crucial M4 and the problems with the
Crucial M500 and link here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-
Only Filesystem
Status in “linux” package in Ubuntu:
Opinion
Bug description:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:
1. System
--
- Ubuntu 14 04 LTS (acutal development branch)
- linux-image-generic v. 3.13.x, mainline kernel 3.13.x (first testing the
standard kernel), last 3.12 mainline kernel
- lvm with trim support (batched discard)
- tlp (currently disabled for testing purpose)
2. Hardware:
---
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the
problem disapears)
- nvidia graphics
BIOS (defaults F9) and:
- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management
AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF
- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power
management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power
management OFF
3. Problem descripton
---
The SSD randomly freezes with the following errors:
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
ata1.00: irq_stat 0x0800, interface fatal error
ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Probably affect other Thinkpad models too:
-
http://www.sevenforums.com/bsod-help-support/309288-bsod-after-few-minutes-5-55-minutes-samsung-ssd-840-evo.html
- [GERMAN]
http://thinkpad-forum.de/threads/168841-Freezes-nach-Einbau-einer-neuen-SSD?p=1698795#post1698795
-
http://www.howtoeverything.net/linux/hardware/ubuntu-freeze-issue-after-ssd-upgrade
4. Troubleshooting so far
4.1. Kernel boot parameters:
libata.force=1:3.0G,2:1,5G libata.force=noncq
- not working. DRDY, hard restting link.
4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no
additional kernel boot parameters.
System ran with standard generic kernel 3.13.x for over 12 hours usage
without any problems.
I did some suspend/ resume cycles: no problems.
5. Further testing:
Testing scenarios will be applied in the follwowing structure (if necessary)
5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters
5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with
[Kernel-packages] [Bug 1274752] Re: Hyper-V Submissions for 14.04
** Description changed: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html + http://www.gossamer-threads.com/lists/linux/kernel/1869534 + === a) b) Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 f) ** Description changed: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html http://www.gossamer-threads.com/lists/linux/kernel/1869534 === a) b) - Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c + Break-Fix: - e28bab4828354583bb66ac09021ca69b341a7db4 Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 f) -- 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/1274752 Title: Hyper-V Submissions for 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html http://www.gossamer-threads.com/lists/linux/kernel/1869534 === a) b) Break-Fix: - e28bab4828354583bb66ac09021ca69b341a7db4 Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 f) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274752/+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 1282687] [NEW] kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x0000000000cca200 ***
Public bug reported: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kerneloops-daemon 0.12+git20090217-3ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Date: Thu Feb 20 18:13:36 2014 ExecutablePath: /usr/sbin/kerneloops InstallationDate: Installed on 2014-01-25 (26 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: /usr/sbin/kerneloops ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 6 SourcePackage: kerneloops Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: kerneloops (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1282687 Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Status in “kerneloops” package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kerneloops-daemon 0.12+git20090217-3ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Date: Thu Feb 20 18:13:36 2014 ExecutablePath: /usr/sbin/kerneloops InstallationDate: Installed on 2014-01-25 (26 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: /usr/sbin/kerneloops ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 6 SourcePackage: kerneloops Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1282687/+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 1275116] Re: lowlatency-flavour crashes and locks up alot
3.2 kernel failed ** Attachment added: netconsole.log https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1275116/+attachment/3988477/+files/netconsole.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/1275116 Title: lowlatency-flavour crashes and locks up alot Status in “linux” package in Ubuntu: Confirmed Status in “linux-lowlatency” package in Ubuntu: Confirmed Bug description: The 3.11 flavour that where upgraded to 3.13 today crashed 10 times this morning. I have the crashdums, but I figured that it might have been solved in 3.13. Unfortunatly it seems like it is not. I will add crashdumps when I get crashes that do not just lockup the machine but currently I have only seem complete lockups with 3.13 So the essense is : 3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text. 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sgh2176 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 31 23:38:10 2014 InstallationDate: Installed on 2013-12-24 (38 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) MachineType: LENOVO 2356GCG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+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 1275116] Re: lowlatency-flavour crashes and locks up alot
Log ** Attachment added: netconsole3.2.log https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1275116/+attachment/3988478/+files/netconsole3.2.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/1275116 Title: lowlatency-flavour crashes and locks up alot Status in “linux” package in Ubuntu: Confirmed Status in “linux-lowlatency” package in Ubuntu: Confirmed Bug description: The 3.11 flavour that where upgraded to 3.13 today crashed 10 times this morning. I have the crashdums, but I figured that it might have been solved in 3.13. Unfortunatly it seems like it is not. I will add crashdumps when I get crashes that do not just lockup the machine but currently I have only seem complete lockups with 3.13 So the essense is : 3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text. 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sgh2176 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 31 23:38:10 2014 InstallationDate: Installed on 2013-12-24 (38 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) MachineType: LENOVO 2356GCG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+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 1275116] Re: lowlatency-flavour crashes and locks up alot
http://pastebin.com/TJ2f83ai -- 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/1275116 Title: lowlatency-flavour crashes and locks up alot Status in “linux” package in Ubuntu: Confirmed Status in “linux-lowlatency” package in Ubuntu: Confirmed Bug description: The 3.11 flavour that where upgraded to 3.13 today crashed 10 times this morning. I have the crashdums, but I figured that it might have been solved in 3.13. Unfortunatly it seems like it is not. I will add crashdumps when I get crashes that do not just lockup the machine but currently I have only seem complete lockups with 3.13 So the essense is : 3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text. 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sgh2176 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 31 23:38:10 2014 InstallationDate: Installed on 2013-12-24 (38 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) MachineType: LENOVO 2356GCG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+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 1282687] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1282687/+attachment/3988494/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1282687 Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Status in “kerneloops” package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kerneloops-daemon 0.12+git20090217-3ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Date: Thu Feb 20 18:13:36 2014 ExecutablePath: /usr/sbin/kerneloops InstallationDate: Installed on 2014-01-25 (26 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: /usr/sbin/kerneloops ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 6 SourcePackage: kerneloops Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1282687/+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 1282687] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1282687/+attachment/3988495/+files/ThreadStacktrace.txt ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1282687/+attachment/3988468/+files/CoreDump.gz ** Changed in: kerneloops (Ubuntu) Importance: Undecided = Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1282687 Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Status in “kerneloops” package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kerneloops-daemon 0.12+git20090217-3ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Date: Thu Feb 20 18:13:36 2014 ExecutablePath: /usr/sbin/kerneloops InstallationDate: Installed on 2014-01-25 (26 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: /usr/sbin/kerneloops ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 6 SourcePackage: kerneloops Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1282687/+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 1282687] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1282687/+attachment/3988493/+files/Stacktrace.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1282687 Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Status in “kerneloops” package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kerneloops-daemon 0.12+git20090217-3ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** Date: Thu Feb 20 18:13:36 2014 ExecutablePath: /usr/sbin/kerneloops InstallationDate: Installed on 2014-01-25 (26 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: /usr/sbin/kerneloops ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 6 SourcePackage: kerneloops Title: kerneloops assert failure: *** Error in `/usr/sbin/kerneloops': double free or corruption (!prev): 0x00cca200 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1282687/+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 1282693] [NEW] hyper-v: Time synchronization related patch
Public bug reported: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New = Triaged -- 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/1282693 Title: hyper-v: Time synchronization related patch Status in “linux” package in Ubuntu: Triaged Bug description: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693/+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 1282695] [NEW] hyper-v: enable large receive side buffers for performance
Public bug reported: c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New = Triaged -- 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/1282695 Title: hyper-v: enable large receive side buffers for performance Status in “linux” package in Ubuntu: Triaged Bug description: c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695/+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 1282700] [NEW] hyper-v: file copy host to guest support
Public bug reported: f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New = Triaged -- 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/1282700 Title: hyper-v: file copy host to guest support Status in “linux” package in Ubuntu: Triaged Bug description: f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700/+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 1274752] Re: Hyper-V Submissions for 14.04
** Description changed: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ + (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693) + b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 + + (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694) c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 + (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695) + d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ + (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696) + e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 + + (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699) f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html http://www.gossamer-threads.com/lists/linux/kernel/1869534 + + (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700) === a) b) Break-Fix: - e28bab4828354583bb66ac09021ca69b341a7db4 Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 f) -- 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/1274752 Title: Hyper-V Submissions for 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693) b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694) c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695) d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696) e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699) f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html http://www.gossamer-threads.com/lists/linux/kernel/1869534 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700) === a) b) Break-Fix: - e28bab4828354583bb66ac09021ca69b341a7db4 Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 f) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274752/+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 1282696] [NEW] hyper-v: screen corruption on resume
Public bug reported: d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New = Triaged -- 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/1282696 Title: hyper-v: screen corruption on resume Status in “linux” package in Ubuntu: Triaged Bug description: d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696/+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 1282699] [NEW] hyper-v: keyboard driver does not support E1 key variants
Public bug reported: e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New = Triaged -- 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/1282699 Title: hyper-v: keyboard driver does not support E1 key variants Status in “linux” package in Ubuntu: Triaged Bug description: e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699/+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 1282032] [NEW] /usr/share/initramfs-tools/hooks/touch failed with return 1. update-initramfs: failed for /boot/initrd.img-3.11.0-17-generic with 1. run-parts: /etc/kernel/postin
You have been subscribed to a public bug: dpkg: error processing linux-image-extra-3.11.0-17-generic (--configure): probleme de dependențe - se lasă neconfigurat dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depinde de linux-image-3.11.0-17-generic; dar: Pachetul linux-image-3.11.0-17-generic nu este configurat încă. linux-image-generic depinde de linux-image-extra-3.11.0-17-generic; dar: Pachetul linux-image-extra-3.11.0-17-generic nu este configurat încă. dpkg: error processing linux-image-generic (--configure): probleme de dependențe - se lasă neconfigurat dpkg: dependency problems prevent configuration of linux-generic: linux-generic depinde de linux-image-generic (= 3.11.0.17.18); dar: Pachetul linux-image-generic nu este configNu a fost scris niciun raport apport deoarece mesajul de eroare indică o eroare survenită în urma unei erori precedente. Nu a fost scris niciun raport apport deoarece mesajul de eroare indică o eroare survenită în urma unei erori precedente. Nu există un raport apport deoarece limita MaxReports a fost deja atinsă urat încă. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CrashDB: ubuntu Date: Wed Feb 19 12:41:32 2014 InstallationDate: Installed on 2014-02-12 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hutu Nelu (hutunelu) Status: New ** Tags: amd64 apport-bug dist-upgrade saucy -- /usr/share/initramfs-tools/hooks/touch failed with return 1. update-initramfs: failed for /boot/initrd.img-3.11.0-17-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.11.0-17-generic.postinst line 1010. dpkg: error processing linux-image-3.11.0-17-generic (--configure): subprocesul script post-installation instalat a returnat starea de eroare la ieșire 2 dpkg: dependency problems prevent configuration of linux-image-extra-3.11.0-17-generic: linux-image-extra-3.11.0-17-generic depinde de linux-image-3.11.0-17-generic; dar: Pachetul linux-image-3.11.0-17-generic nu este configurat încă. https://bugs.launchpad.net/bugs/1282032 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1282694] [NEW] hyper-v: ensure kdump works correctly with multiple vCPUs
Public bug reported: b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New = Triaged -- 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/1282694 Title: hyper-v: ensure kdump works correctly with multiple vCPUs Status in “linux” package in Ubuntu: Triaged Bug description: b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694/+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 1282700] Re: hyper-v: file copy host to guest support
Latest V7 version seems to be: http://www.gossamer- threads.com/lists/linux/kernel/1869534 This is looking likely to be accepted this time round. Waiting on that from upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282700 Title: hyper-v: file copy host to guest support Status in “linux” package in Ubuntu: Triaged Bug description: f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700/+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 1282032] Re: /usr/share/initramfs-tools/hooks/touch failed with return 1. update-initramfs: failed for /boot/initrd.img-3.11.0-17-generic with 1. run-parts: /etc/kernel/postinst
** Package changed: ubuntu-release-upgrader (Ubuntu) = linux (Ubuntu) -- 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/1282032 Title: /usr/share/initramfs-tools/hooks/touch failed with return 1. update- initramfs: failed for /boot/initrd.img-3.11.0-17-generic with 1. run- parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info /linux-image-3.11.0-17-generic.postinst line 1010. dpkg: error processing linux-image-3.11.0-17-generic (--configure): subprocesul script post-installation instalat a returnat starea de eroare la ieșire 2 dpkg: dependency problems prevent configuration of linux- image-extra-3.11.0-17-generic: linux-image-extra-3.11.0-17-generic depinde de linux-image-3.11.0-17-generic; dar: Pachetul linux- image-3.11.0-17-generic nu este configurat încă. Status in “linux” package in Ubuntu: New Bug description: dpkg: error processing linux-image-extra-3.11.0-17-generic (--configure): probleme de dependențe - se lasă neconfigurat dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depinde de linux-image-3.11.0-17-generic; dar: Pachetul linux-image-3.11.0-17-generic nu este configurat încă. linux-image-generic depinde de linux-image-extra-3.11.0-17-generic; dar: Pachetul linux-image-extra-3.11.0-17-generic nu este configurat încă. dpkg: error processing linux-image-generic (--configure): probleme de dependențe - se lasă neconfigurat dpkg: dependency problems prevent configuration of linux-generic: linux-generic depinde de linux-image-generic (= 3.11.0.17.18); dar: Pachetul linux-image-generic nu este configNu a fost scris niciun raport apport deoarece mesajul de eroare indică o eroare survenită în urma unei erori precedente. Nu a fost scris niciun raport apport deoarece mesajul de eroare indică o eroare survenită în urma unei erori precedente. Nu există un raport apport deoarece limita MaxReports a fost deja atinsă urat încă. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CrashDB: ubuntu Date: Wed Feb 19 12:41:32 2014 InstallationDate: Installed on 2014-02-12 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282032/+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 1282695] Re: hyper-v: enable large receive side buffers for performance
commit b679ef73edc251f6d200a7dd2396e9fef9e36fc3 Author: Haiyang Zhang haiya...@microsoft.com Date: Mon Jan 27 15:03:42 2014 -0800 hyperv: Add support for physically discontinuous receive buffer -- 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/1282695 Title: hyper-v: enable large receive side buffers for performance Status in “linux” package in Ubuntu: Triaged Bug description: c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695/+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 1282696] Re: hyper-v: screen corruption on resume
This fix seems very dirty and unlikely to make it into mainline. Waiting on upstream commentary on this approach. -- 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/1282696 Title: hyper-v: screen corruption on resume Status in “linux” package in Ubuntu: Triaged Bug description: d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696/+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 1282694] Re: hyper-v: ensure kdump works correctly with multiple vCPUs
commit e28bab4828354583bb66ac09021ca69b341a7db4 Author: K. Y. Srinivasan k...@microsoft.com Date: Wed Jan 15 17:12:58 2014 -0800 Drivers: hv: vmbus: Specify the target CPU that should receive notification commit 269f979467cf49f2ea8132316c1f00f8c9678f7c Author: K. Y. Srinivasan k...@microsoft.com Date: Thu Jan 16 11:59:58 2014 -0800 Drivers: hv: vmbus: Don't timeout during the initial connection with host -- 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/1282694 Title: hyper-v: ensure kdump works correctly with multiple vCPUs Status in “linux” package in Ubuntu: Triaged Bug description: b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694/+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 1282699] Re: hyper-v: keyboard driver does not support E1 key variants
commit c3c4d99485ea51cd354ed3cd955a8310703456b6 Author: K. Y. Srinivasan k...@microsoft.com Date: Sun Jan 12 11:09:14 2014 -0800 Input: hyperv-keyboard - pass through 0xE1 prefix -- 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/1282699 Title: hyper-v: keyboard driver does not support E1 key variants Status in “linux” package in Ubuntu: Triaged Bug description: e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699/+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 1274752] Re: Hyper-V Submissions for 14.04
** Tags removed: kernel-bug-break-fix -- 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/1274752 Title: Hyper-V Submissions for 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693) b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694) c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695) d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696) e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699) f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html http://www.gossamer-threads.com/lists/linux/kernel/1869534 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700) === a) b) Break-Fix: - e28bab4828354583bb66ac09021ca69b341a7db4 Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 f) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274752/+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 1274752] Re: Hyper-V Submissions for 14.04
I have opened a bug for each of these as below: a) Time synchronization related patch (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693) b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694) c) Patch to use large receive side buffers. Will improve Linux VM networking performance: (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695) d) Patch to fix screen corruption during suspend/resume of virtual machine (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696) e) Patch to address Keyboard driver bug (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699) f) Patch for File copy from host to guest feature (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700) -- 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/1274752 Title: Hyper-V Submissions for 14.04 Status in “linux” package in Ubuntu: Confirmed Bug description: There are a few bug fixes and features that need to be added for Hyper-V: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693) b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694) c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695) d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696) e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699) f) Patch for File copy from host to guest feature http://www.spinics.net/lists/kernel/msg1673437.html http://www.gossamer-threads.com/lists/linux/kernel/1869534 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282700) === a) b) Break-Fix: - e28bab4828354583bb66ac09021ca69b341a7db4 Break-Fix: - 269f979467cf49f2ea8132316c1f00f8c9678f7c c) Break-Fix: - b679ef73edc251f6d200a7dd2396e9fef9e36fc3 d) e) Break-Fix: - c3c4d99485ea51cd354ed3cd955a8310703456b6 f) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274752/+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 1282693] Re: hyper-v: Time synchronization related patch
The patch for this seems to be in limbo upstream still. -- 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/1282693 Title: hyper-v: Time synchronization related patch Status in “linux” package in Ubuntu: Triaged Bug description: a) Time synchronization related patch https://groups.google.com/forum/#!msg/linux.kernel/Km5qsxXZHNc/4QhvWVq0nQsJ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282693/+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 1282695] Re: hyper-v: enable large receive side buffers for performance
** Changed in: linux (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282695 Title: hyper-v: enable large receive side buffers for performance Status in “linux” package in Ubuntu: Fix Committed Bug description: c) Patch to use large receive side buffers. Will improve Linux VM networking performance: http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/drivers/hv/channel.c?id=b679ef73edc251f6d200a7dd2396e9fef9e36fc3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282695/+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 1282032] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1282032 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/1282032 Title: /usr/share/initramfs-tools/hooks/touch failed with return 1. update- initramfs: failed for /boot/initrd.img-3.11.0-17-generic with 1. run- parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info /linux-image-3.11.0-17-generic.postinst line 1010. dpkg: error processing linux-image-3.11.0-17-generic (--configure): subprocesul script post-installation instalat a returnat starea de eroare la ieșire 2 dpkg: dependency problems prevent configuration of linux- image-extra-3.11.0-17-generic: linux-image-extra-3.11.0-17-generic depinde de linux-image-3.11.0-17-generic; dar: Pachetul linux- image-3.11.0-17-generic nu este configurat încă. Status in “linux” package in Ubuntu: Incomplete Bug description: dpkg: error processing linux-image-extra-3.11.0-17-generic (--configure): probleme de dependențe - se lasă neconfigurat dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depinde de linux-image-3.11.0-17-generic; dar: Pachetul linux-image-3.11.0-17-generic nu este configurat încă. linux-image-generic depinde de linux-image-extra-3.11.0-17-generic; dar: Pachetul linux-image-extra-3.11.0-17-generic nu este configurat încă. dpkg: error processing linux-image-generic (--configure): probleme de dependențe - se lasă neconfigurat dpkg: dependency problems prevent configuration of linux-generic: linux-generic depinde de linux-image-generic (= 3.11.0.17.18); dar: Pachetul linux-image-generic nu este configNu a fost scris niciun raport apport deoarece mesajul de eroare indică o eroare survenită în urma unei erori precedente. Nu a fost scris niciun raport apport deoarece mesajul de eroare indică o eroare survenită în urma unei erori precedente. Nu există un raport apport deoarece limita MaxReports a fost deja atinsă urat încă. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CrashDB: ubuntu Date: Wed Feb 19 12:41:32 2014 InstallationDate: Installed on 2014-02-12 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282032/+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 1282694] Re: hyper-v: ensure kdump works correctly with multiple vCPUs
** Changed in: linux (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282694 Title: hyper-v: ensure kdump works correctly with multiple vCPUs Status in “linux” package in Ubuntu: Fix Committed Bug description: b) Patches to ensure that kdump works correctly when multiple vCPUs are assigned to the virtual machine: https://lkml.org/lkml/2014/1/16/431 https://lkml.org/lkml/2014/1/15/793 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282694/+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 1282699] Re: hyper-v: keyboard driver does not support E1 key variants
** Changed in: linux (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282699 Title: hyper-v: keyboard driver does not support E1 key variants Status in “linux” package in Ubuntu: Fix Committed Bug description: e) Patch to address Keyboard driver bug https://lkml.org/lkml/2014/1/11/194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282699/+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 1282712] [NEW] SMT disabled leads to panics on ppc64el
Public bug reported: We are getting panics with SMT disabled, fixed by the patch below: http://patchwork.ozlabs.org/patch/322094/ ** Affects: linux (Ubuntu) Importance: Critical Assignee: Andy Whitcroft (apw) Status: Fix Committed ** Changed in: linux (Ubuntu) Status: New = In Progress ** Changed in: linux (Ubuntu) Importance: Undecided = Critical ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Andy Whitcroft (apw) ** Changed in: linux (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282712 Title: SMT disabled leads to panics on ppc64el Status in “linux” package in Ubuntu: Fix Committed Bug description: We are getting panics with SMT disabled, fixed by the patch below: http://patchwork.ozlabs.org/patch/322094/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282712/+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 1282495] Re: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31]
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1282495 Title: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] Status in “linux” package in Ubuntu: Confirmed Bug description: Unsure ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-10-generic 3.13.0-10.30 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: videotron 2720 F pulseaudio /dev/snd/controlC0: videotron 2720 F pulseaudio Date: Wed Feb 19 22:51:39 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] EIP: 0060:location EFLAGS: 0282 CPU: 0 Failure: oops HibernationDevice: RESUME=UUID=241563ea-626c-4979-a469-f97344eef17f InstallationDate: Installed on 2014-01-11 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: LENOVO 1450A7U ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9864d147-5614-4e11-9b8b-55e2160b47c8 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: kerneloops-daemon 0.12+git20090217-3ubuntu4 SourcePackage: linux StagingDrivers: rts5139 Title: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] UpgradeStatus: Upgraded to trusty on 2014-01-18 (33 days ago) dmi.bios.date: 05/12/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 52CN11WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr52CN11WW:bd05/12/2011:svnLENOVO:pn1450A7U:pvrLenovoB575:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 1450A7U dmi.product.version: Lenovo B575 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282495/+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 1282495] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1282495 Title: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] Status in “linux” package in Ubuntu: Confirmed Bug description: Unsure ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-10-generic 3.13.0-10.30 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: videotron 2720 F pulseaudio /dev/snd/controlC0: videotron 2720 F pulseaudio Date: Wed Feb 19 22:51:39 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] EIP: 0060:location EFLAGS: 0282 CPU: 0 Failure: oops HibernationDevice: RESUME=UUID=241563ea-626c-4979-a469-f97344eef17f InstallationDate: Installed on 2014-01-11 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: LENOVO 1450A7U ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9864d147-5614-4e11-9b8b-55e2160b47c8 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: kerneloops-daemon 0.12+git20090217-3ubuntu4 SourcePackage: linux StagingDrivers: rts5139 Title: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] UpgradeStatus: Upgraded to trusty on 2014-01-18 (33 days ago) dmi.bios.date: 05/12/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 52CN11WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr52CN11WW:bd05/12/2011:svnLENOVO:pn1450A7U:pvrLenovoB575:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 1450A7U dmi.product.version: Lenovo B575 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282495/+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 1282495] Re: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31]
** Tags removed: need-duplicate-check -- 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/1282495 Title: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] Status in “linux” package in Ubuntu: Confirmed Bug description: Unsure ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-10-generic 3.13.0-10.30 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: videotron 2720 F pulseaudio /dev/snd/controlC0: videotron 2720 F pulseaudio Date: Wed Feb 19 22:51:39 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] EIP: 0060:location EFLAGS: 0282 CPU: 0 Failure: oops HibernationDevice: RESUME=UUID=241563ea-626c-4979-a469-f97344eef17f InstallationDate: Installed on 2014-01-11 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: LENOVO 1450A7U ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9864d147-5614-4e11-9b8b-55e2160b47c8 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: kerneloops-daemon 0.12+git20090217-3ubuntu4 SourcePackage: linux StagingDrivers: rts5139 Title: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31] UpgradeStatus: Upgraded to trusty on 2014-01-18 (33 days ago) dmi.bios.date: 05/12/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 52CN11WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr52CN11WW:bd05/12/2011:svnLENOVO:pn1450A7U:pvrLenovoB575:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 1450A7U dmi.product.version: Lenovo B575 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282495/+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 1280693] Re: [LENOVO 20AQCTO1WW] hibernate/resume failure
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1280693 Title: [LENOVO 20AQCTO1WW] hibernate/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: This should have hibernate resume, since it is hardware certified: http://www.ubuntu.com/certification/hardware/201308-14073/ Note, I have an SSD instead of the HDD. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.28 [modified: boot/vmlinuz-3.13.0-8-generic] ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1479 F pulseaudio sol1878 F pulseaudio /dev/snd/controlC0: lightdm1479 F pulseaudio sol1878 F pulseaudio Date: Sat Feb 15 17:28:38 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=027c0786-cb7e-48db-84dd-75553c948299 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140214) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 20AQCTO1WW ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=3275897d-69f9-492b-a5bc-82e88c59ad0b 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-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 SourcePackage: linux Title: [LENOVO 20AQCTO1WW] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280693/+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 1280467] Re: ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = 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/1280467 Title: ACPI Warning: 0x1828-0x182f SystemIO conflicts with Region Status in “linux” package in Ubuntu: Confirmed Bug description: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Still also appears in kernel 3.13.3 3.14-rc2: [ 19.459136] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 19.470228] ACPI Warning: 0x1828-0x182f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251) [ 19.470234] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.470238] ACPI Warning: 0x1c30-0x1c3f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251) [ 19.470241] ACPI Warning: 0x1c30-0x1c3f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251) [ 19.470244] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.470245] ACPI Warning: 0x1c00-0x1c2f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251) [ 19.470248] ACPI Warning: 0x1c00-0x1c2f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251) [ 19.470250] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 19.470251] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 19.474422] [drm] Initialized drm 1.1.0 20060810 --- ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Alpha amd64 (20140214) Package: linux (not installed) Tags: trusty Uname: Linux 3.14.0-031400rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280467/+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 1275116] Re: lowlatency-flavour crashes and locks up alot
v3.12-trusty/ seems to work for me. So to me it seem to have broken between 3.12 and 3.13. For sure it did break since where saucy where around christmas, because I ran that with it's lowlatency until then. I'll try v3.13-rc1-trusty to check. -- 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/1275116 Title: lowlatency-flavour crashes and locks up alot Status in “linux” package in Ubuntu: Confirmed Status in “linux-lowlatency” package in Ubuntu: Confirmed Bug description: The 3.11 flavour that where upgraded to 3.13 today crashed 10 times this morning. I have the crashdums, but I figured that it might have been solved in 3.13. Unfortunatly it seems like it is not. I will add crashdumps when I get crashes that do not just lockup the machine but currently I have only seem complete lockups with 3.13 So the essense is : 3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text. 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-6-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sgh2176 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 31 23:38:10 2014 InstallationDate: Installed on 2013-12-24 (38 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224) MachineType: LENOVO 2356GCG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-6-generic N/A linux-backports-modules-3.13.0-6-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+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 1280642] Re: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31]
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1280642 Title: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31] Status in “linux” package in Ubuntu: Incomplete Bug description: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31] ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.28 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.13.2-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1380 F pulseaudio dinesh 2037 F pulseaudio Date: Sat Feb 15 09:18:15 2014 DuplicateSignature: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31] EIP: 0060:location EFLAGS: 0202 CPU: 1 Failure: oops HibernationDevice: RESUME=UUID=4cc2dadc-c747-43d9-8938-ea8bf907df2b InstallationDate: Installed on 2013-11-05 (102 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Hewlett-Packard HP Compaq 6710s (GP167PA#ACJ) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=2bc9b372-0240-46b3-bf0d-d43bef7fdcdc ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DDU Ver. F.06 dmi.board.name: 30C0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.26 dmi.chassis.asset.tag: CNU7240WZS dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DDUVer.F.06:bd04/14/2007:svnHewlett-Packard:pnHPCompaq6710s(GP167PA#ACJ):pvrF.06:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.26:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6710s (GP167PA#ACJ) dmi.product.version: F.06 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280642/+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 1280599] Re: [Dell Inc. Latitude D630] suspend/resume failure
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1280599 Title: [Dell Inc. Latitude D630] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: kernel oops on resume from Suspend (GUI) of laptop ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.28 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan2515 F pulseaudio Date: Sat Feb 15 14:23:14 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (907 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) InterpreterPath: /usr/bin/python3.3 MachineType: Dell Inc. Latitude D630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro quiet splash crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 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-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 SourcePackage: linux Title: [Dell Inc. Latitude D630] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2013-10-25 (113 days ago) UserGroups: dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280599/+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 1281032] Re: Left click randomly stop working
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1281032 Title: Left click randomly stop working Status in “linux” package in Ubuntu: Incomplete Bug description: I'm experiencing a strange issue while everything was working fine with my mouse. Now the left click (but the right click is still working) and the trackpad randomly stop to work if I go to the console (CTRL+ALT+F1) they are reworking. Ubuntu 3.11.0-15.25-generic 3.11.10 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) Subsystem: Dell Device [1028:04b6] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c ? 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 3000-3fff Memory behind bridge: f000-f10f Prefetchable memory behind bridge: c000-d1ff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Intel Corporation Device [8086:2010] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00318 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 64ns, L1 1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 256ns, L1 4us ClockPM- Surprise- LLActRep- BwNot+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled+ Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis- ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -3.5dB
[Kernel-packages] [Bug 1280816] Re: CPU racing
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1280816 Title: CPU racing Status in “linux” package in Ubuntu: Incomplete Bug description: I am really a noob at the whole linux thing but I will try to help as much as i can. i noticed there was a problem because my cpu would race and get more and more cpu usage in the IRQx process until it would lock up. That's when i found the bug page and reported. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.25 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 09:13:59 2014 HibernationDevice: RESUME=UUID=fcf3dde0-a589-4358-a19e-79ea8b86a064 InstallationDate: Installed on 2014-02-08 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Gateway GT5676 MarkForUpload: True ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7B3G1P04 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Not Available dmi.board.vendor: Gateway dmi.board.version: Not Available dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7B3G1P04:bd02/18/2008:svnGateway:pnGT5676:pvr7B3G1P04:rvnGateway:rnNotAvailable:rvrNotAvailable:cvnGateway:ct3:cvr1.0: dmi.product.name: GT5676 dmi.product.version: 7B3G1P04 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280816/+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 1280839] Re: Touchpad / Trackpoint does not work on fresh install of 13.10 on Toshiba Portege Z10t-A
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** 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/1280839 Title: Touchpad / Trackpoint does not work on fresh install of 13.10 on Toshiba Portege Z10t-A Status in “linux” package in Ubuntu: Incomplete Bug description: Touchpad/Trackpoint on dock not working It appears as an i8042 device on /dev/input/event5, which emits data when using input-events and using device Xorg finds it, it's listed in xinput as USB Device, but using the device in X does not work - only action is to display the cursor. The touchscreen and USB mice work fine Thanks ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.25 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam3357 F pulseaudio Date: Sun Feb 16 17:33:49 2014 HibernationDevice: RESUME=UUID=e8bf960c-f79e-43fe-b0c9-51d757c3a9f5 InstallationDate: Installed on 2014-02-14 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: TOSHIBA PORTEGE Z10T-A MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=935a33ad-be6d-41ec-b92e-3ebdf5bef53a ro persistent quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.80 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z10T-A 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:bvrVersion1.80:bd07/16/2013:svnTOSHIBA:pnPORTEGEZ10T-A:pvrPT131E-00700JEN:rvnTOSHIBA:rnPORTEGEZ10T-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z10T-A dmi.product.version: PT131E-00700JEN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280839/+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
