[Kernel-packages] [Bug 1218810] Re: video switch hot key will return "super key and p" and no response to switch video mode
Still exist on 12.04.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218810
Title:
video switch hot key will return "super key and p" and no response to
switch video mode
Status in Unity:
New
Status in “linux” package in Ubuntu:
Confirmed
Status in “unity” package in Ubuntu:
New
Status in “linux” source package in Precise:
New
Status in “unity” source package in Precise:
New
Status in “linux” source package in Trusty:
Fix Released
Status in “unity” source package in Trusty:
Fix Released
Bug description:
CID 201209-11735
For some machines, for example, HP laptop "HP 1000" has a hot key on F4 to
perform the shorcut "super + p" to switch video modes.
Use command "sudo showkey -k" to capture the key code of the hot key you will
see the key code of "super key" and "p"
This key combination is expected to change the video mode.
platfrom: HP laptop "HP 1000"
image: 12.04.3
Steps to reproduce:
1. open an terminal,
2. plugin an external monitor
3. press the video switch hotkey, for "HP 1000" it is the F4 key
Expected result:
1. Video mode is changed by the hotkey
2. no character is printed on terminal
Actual result
1. Video mode is not changed.
2. a "p" will be printed on the terminal screen
The other information:
1. A similar bug was reported on LP:#539477 before.
2. The hotkey in 13.04 works
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Fri Aug 30 17:34:56 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1675 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x6360 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,103c1855,00100202
HDA:80862806,80860101,0010'
Controls : 27
Simple ctrls : 10
CurrentDmesg:
[ 45.884915] ISO 9660 Extensions: RRIP_1991A
[ 60.442781] audit_printk_skb: 3 callbacks suppressed
[ 60.442785] type=1400 audit(1378093422.964:31): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5"
name="/usr/share/gvfs/remote-volume-monitors/" pid=1849 comm="mission-control"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 65.385488] r8169 :0e:00.0 eth0: link up
[ 65.385510] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=932733cb-db60-4153-8565-3e3ccb1a6f6d
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
Lsusb:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 05c8:0223 Cheng Uei Precision Industry Co., Ltd
(Foxlink)
MachineType: Hewlett-Packard HP 1000 Notebook PC
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 radeondrmfb
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=770667e1-92a4-4f2e-a434-b9998d55cb30 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/25/2012
dmi.bios.vendor: Insyde
dmi.bios.version: B.50
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1855
dmi.board.vendor: Hewlett-
[Kernel-packages] [Bug 1362447] Re: CVE-2014-5471
CVE-2014-5471 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Description changed: - Placeholder + [unbound recursion in ISOFS - crashes / reboots a kernel due to kernel + stack overflow / corruption] + + Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Lucid) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Utopic) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu T
[Kernel-packages] [Bug 1362447] [NEW] CVE-2014-5471
*** This bug is a security vulnerability *** Public security bug reported: [unbound recursion in ISOFS - crashes / reboots a kernel due to kernel stack overflow / corruption] Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Utopic) Importance: Medium
[Kernel-packages] [Bug 1362168] Re: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362443] [NEW] CVE-2014-3601
*** This bug is a security vulnerability *** Public security bug reported: [kvm: invalid parameter passing in kvm_iommu_map_pages()] Break-Fix: fcd95807fb61e67d602610e7ff7129ed769e9fee 350b8bdd689cd2ab2c67c8a86a0be86cfa0751a7 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Utopic) Importance: Medium
[Kernel-packages] [Bug 1362448] [NEW] CVE-2014-5472
*** This bug is a security vulnerability *** Public security bug reported: [unbound recursion in ISOFS - causes a deadlock in the mount process in "inode_wait"] Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Utopic) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Utopic) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Utopic) Importance: Medium Status: Inval
[Kernel-packages] [Bug 1362443] Re: CVE-2014-3601
CVE-2014-3601 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Description changed: - Placeholder + [kvm: invalid parameter passing in kvm_iommu_map_pages()] + + Break-Fix: fcd95807fb61e67d602610e7ff7129ed769e9fee + 350b8bdd689cd2ab2c67c8a86a0be86cfa0751a7 ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Lucid) Importance: Undecid
[Kernel-packages] [Bug 1362448] Re: CVE-2014-5472
CVE-2014-5472 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Description changed: - Placeholder + [unbound recursion in ISOFS - causes a deadlock in the mount process in + "inode_wait"] + + Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4 ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Lucid) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Utopic) Importance: Undecided => Medium ** Changed in: linux-armadaxp (Ubuntu Trusty) Impo
[Kernel-packages] [Bug 1362168] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188787/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188781/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188784/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188785/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188783/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188779/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188782/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188780/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188786/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] Re: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn
apport information ** Tags added: apport-collected trusty ** Description changed: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks + + + --- + ApportVersion: 2.14.1-0ubuntu3.3 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: massimo1485 F pulseaudio + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 + InstallationDate: Installed on 2014-08-12 (15 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) + MachineType: Sony Corporation VGN-TZ31XN_B + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcEnviron: + LANGUAGE=it + TERM=xterm + PATH=(custom, no user) + LANG=it_IT.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.13.0-35-generic N/A + linux-backports-modules-3.13.0-35-generic N/A + linux-firmware 1.127.5 + Tags: trusty + Uname: Linux 3.13.0-35-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 02/07/2008 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: R0091N7 + dmi.board.asset.tag: N/A + dmi.board.name: VAIO + dmi.board.vendor: Sony Corporation + dmi.board.version: N/A + dmi.chassis.type: 10 + dmi.chassis.vendor: Sony Corporation + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: + dmi.product.name: VGN-TZ31XN_B + dmi.product.version: J002YC52 + dmi.sys.vendor: Sony Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188775/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's stran
[Kernel-packages] [Bug 1362168] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188777/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188776/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362168] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1362168/+attachment/4188778/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Confirmed Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: massimo1485 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f65ecb97-d8c1-4b71-aefb-27ff41a66e50 InstallationDate: Installed on 2014-08-12 (15 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Sony Corporation VGN-TZ31XN_B Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=it TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=cc70f8e1-9c7c-4a7f-87f8-e2dd6a57a27a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0091N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31XN_B:pvrJ002YC52:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-TZ31XN_B dmi.product.version: J002YC52 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349799] Re: CVE-2014-5045
** Changed in: linux (Ubuntu Trusty) Status: New => 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/1349799 Title: CVE-2014-5045 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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: Invalid Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The mountpoint_last function in fs/namei.c in the Linux kernel before 3.15.8 does not properly maintain a certain reference count during attempts to use the umount system call in conjunction with a symlink, which allows local users to cause a denial of service (memory consumption or use-after-free) or possibly have unspecified other impact via the umount program. Break-Fix: 8033426e6bdb2690d302872ac1e1fadaec1a5581 295dc39d941dc2ae53d5c170365af4c9d5c16212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336135] Re: CVE-2014-4667
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1336135 Title: CVE-2014-4667 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The sctp_association_free function in net/sctp/associola.c in the Linux kernel before 3.15.2 does not properly manage a certain backlog value, which allows remote attackers to cause a denial of service (socket outage) via a crafted SCTP packet. Break-Fix: de76e695a5ce19c121ba7e246b45f258be678a75 d3217b15a19a4779c39b212358a5c71d725822ee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349804] Re: CVE-2014-5077
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1349804 Title: CVE-2014-5077 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed Status in “linux” source package in Trusty: New 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The sctp_assoc_update function in net/sctp/associola.c in the Linux kernel through 3.15.8, when SCTP authentication is enabled, allows remote attackers to cause a denial of service (NULL pointer dereference and OOPS) by starting to establish an association between two endpoints immediately after an exchange of INIT and INIT ACK chunks to establish an earlier association between these endpoints in the opposite direction. Break-Fix: - 1be9a950c646c9092fb3618197f7b6bfb50e82aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356318] Re: CVE-2014-5206
** Changed in: linux (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Description changed: - Remounting a read-only bind mount read-only in a user namespace the - MNT_LOCK_READONLY bit would be cleared, allowing an unprivileged user to - the remount a read-only mount read-write. + The do_remount function in fs/namespace.c in the Linux kernel through + 3.16.1 does not maintain the MNT_LOCK_READONLY bit across a remount of a + bind mount, which allows local users to bypass an intended read-only + restriction and defeat certain sandbox protection mechanisms via a + "mount -o remount" command within a user namespace. Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 a6138db815df5ee542d848318e5dae681590fccd Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 07b645589dcda8b7a5249e096fece2a67556f0f4 -- 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/1356318 Title: CVE-2014-5206 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-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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: Invalid 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-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The do_remount function in fs/namespace.c in the Linux kernel through 3.16.1 does not maintain the MNT_LOCK_READONLY bit across a remount of a bind mount, which allows local users to bypass an intended read-only restriction and defeat certain sandbox protection mechanisms via a "mount -o remount" command within a user namespace. Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 a6138db815df5ee542d848318e5dae681590fccd Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 07b645589dcda
[Kernel-packages] [Bug 1356323] Re: CVE-2014-5207
** Changed in: linux (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Description changed: - Mount flags MNT_NOSUID, MNT_NODEV, MNT_NOEXEC, and the atime flags in - addition to MNT_READONLY could be reset by less-privileged users when - remounting filesystems. + fs/namespace.c in the Linux kernel through 3.16.1 does not properly + restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing + MNT_ATIME_MASK during a remount of a bind mount, which allows local + users to gain privileges, interfere with backups and auditing on systems + that had atime enabled, or cause a denial of service (excessive + filesystem updating) on systems that had atime disabled via a "mount -o + remount" command within a user namespace. Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 9566d6742852c527bf5af38af5cbb878dad75705 Break-Fix: 0c55cfc4166d9a0f38de779bd4d75a90afbe7734 ffbc6f0ead47fa5a1dc9642b0331cb75c20a640e -- 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/1356323 Title: CVE-2014-5207 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-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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: Invalid 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-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Released Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: fs/namespace.c in the Linux kernel through 3.16.1 does not properly restrict clearing MNT_NODEV, MNT_NOSUID, and MNT_NOEXEC and changing MNT_ATIME_MASK during a remount of a bind mount, which allows local users to gain privileges, interfere with backups and auditing on systems that had atime enabled, or cause a denial of service (excessive filesystem updating) on systems that had a
[Kernel-packages] [Bug 1339303] Re: CVE-2014-4654
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1339303 Title: CVE-2014-4654 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The snd_ctl_elem_add function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not check authorization for SNDRV_CTL_IOCTL_ELEM_REPLACE commands, which allows local users to remove kernel controls and cause a denial of service (use-after-free and system crash) by leveraging /dev/snd/controlCX access for an ioctl call. Break-Fix: - 82262a46627bebb0febcc26664746c25cef08563 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339304] Re: CVE-2014-4655
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1339304 Title: CVE-2014-4655 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The snd_ctl_elem_add function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not properly maintain the user_ctl_count value, which allows local users to cause a denial of service (integer overflow and limit bypass) by leveraging /dev/snd/controlCX access for a large number of SNDRV_CTL_IOCTL_ELEM_REPLACE ioctl calls. Break-Fix: - 82262a46627bebb0febcc26664746c25cef08563 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339306] Re: CVE-2014-4656
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1339306 Title: CVE-2014-4656 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Multiple integer overflows in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allow local users to cause a denial of service by leveraging /dev/snd/controlCX access, related to (1) index values in the snd_ctl_add function and (2) numid values in the snd_ctl_remove_numid_conflict function. Break-Fix: - ac902c112d90a89e59916f751c2745f4dbdbb4bd Break-Fix: - 883a1d49f0d77d30012f114b2e19fc141beb3e8e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333617] Re: CVE-2014-4171
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1333617 Title: CVE-2014-4171 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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 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: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed 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” source package in Trusty: Fix Committed 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (i_mutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended shmem activity by blocking completion of (1) an MADV_REMOVE madvise call or (2) an FALLOC_FL_PUNCH_HOLE fallocate call. Break-Fix: - f00cdc6df7d7cfcabb5b740911e6788cb0802bdb Break-Fix: - 8e205f779d1443a94b5ae81aa359cb535dd3021e Break-Fix: - b1a366500bd537b50c3aad26dc7df083ec03a448 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages M
[Kernel-packages] [Bug 1334989] Re: CVE-2014-4508
** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => 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/1334989 Title: CVE-2014-4508 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: arch/x86/kernel/entry_32.S in the Linux kernel through 3.15.1 on 32-bit x86 platforms, when syscall auditing is enabled and the sep CPU feature flag is set, allows local users to cause a denial of service (OOPS and system crash) via an invalid syscall number, as demonstrated by number 1000. Break-Fix: - 554086d85e71f30abe46fc014fea31929a7c6a8a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339297] Re: CVE-2014-4653
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1339297 Title: CVE-2014-4653 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not ensure possession of a read/write lock, which allows local users to cause a denial of service (use-after-free) and obtain sensitive information from kernel memory by leveraging /dev/snd/controlCX access. Break-Fix: - fd9f26e4eca5d08a27d12c0933fceef76ed9663d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339294] Re: CVE-2014-4652
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1339294 Title: CVE-2014-4652 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: New Status in “linux-lts-backport-natty” source package in Lucid: New 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: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed 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: New Status in “linux-lts-backport-natty” source package in Trusty: New 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: New Status in “linux-lts-backport-natty” source package in Utopic: New Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Race condition in the tlv handler functionality in the snd_ctl_elem_user_tlv function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allows local users to obtain sensitive information from kernel memory by leveraging /dev/snd/controlCX access. Break-Fix: - 07f4d9d74a04aa7c72c5dae0ef97565f28f17b92 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329103] Re: CVE-2014-4014
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Description changed: The capabilities implementation in the Linux kernel before 3.14.8 does not properly consider that namespaces are inapplicable to inodes, which allows local users to bypass intended chmod restrictions by first creating a user namespace, as demonstrated by setting the setgid bit on a file with group ownership of root. - Break-Fix: - 23adbe12ef7d3d4195e80800ab36b37bee28cd03 + Break-Fix: 1a48e2ac034d47ed843081c4523b63c46b46888b + 23adbe12ef7d3d4195e80800ab36b37bee28cd03 -- 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/1329103 Title: CVE-2014-4014 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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-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” source package in Trusty: Fix Committed 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The capabilities implementation in the Linux kernel before 3.14.8 does not properly consider that namespaces are inapplicable to inodes, which allows local users to bypass intended chmod restrictions by first creating a user namespace, as dem
[Kernel-packages] [Bug 1333612] Re: CVE-2014-4027
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1333612 Title: CVE-2014-4027 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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 Released Status in “linux-lts-raring” source package in Precise: Invalid 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 Committed 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” source package in Trusty: Fix Committed 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 Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The rd_build_device_space function in drivers/target/target_core_rd.c in the Linux kernel before 3.14 does not properly initialize a certain data structure, which allows local users to obtain sensitive information from ramdisk_mcp memory by leveraging access to a SCSI initiator. Break-Fix: c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 4442dc8a92b8f9ad8ee9e7f8438f4c04c03a22dc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1325941] Re: CVE-2014-3917
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => 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/1325941 Title: CVE-2014-3917 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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-lts-trusty” 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-lts-trusty” 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 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-lts-trusty” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed 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-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-trusty” source package in Saucy: Invalid 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-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-lts-trusty” 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-lts-trusty” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: kernel/auditsc.c in the Linux kernel through 3.14.5, when CONFIG_AUDITSYSCALL is enabled with certain syscall rules, allows local users to obtain potentially sensitive single-bit values from kernel memory or cause a denial of service (OOPS) via a large value of a syscall number. Break-Fix: - a3c54931199565930d6d84f4c3456f6440aefd41 To manage notifications about this bug go to: h
[Kernel-packages] [Bug 1333605] Re: CVE-2014-0203
** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => 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/1333605 Title: CVE-2014-0203 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: 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: Invalid 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: 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” 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 Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The __do_follow_link function in fs/namei.c in the Linux kernel before 2.6.33 does not properly handle the last pathname component during use of certain filesystems, which allows local users to cause a denial of service (incorrect free operations and system crash) via an open system call. Break-Fix: - 86acdca1b63e6890540fa19495cfc708beff3d8b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1312987] Re: CVE-2014-0155
** Changed in: linux (Ubuntu Trusty) Status: New => 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/1312987 Title: CVE-2014-0155 Status in “linux” package in Ubuntu: Fix Committed 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: New Status in “linux-lts-backport-natty” package in Ubuntu: New 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: Invalid 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-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-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” source package in Trusty: Fix Committed 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 Status in “linux” source package in Utopic: Fix Committed Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The ioapic_deliver function in virt/kvm/ioapic.c in the Linux kernel through 3.14.1 does not properly validate the kvm_irq_delivery_to_apic return value, which allows guest OS users to cause a denial of service (host OS crash) via a crafted entry in the redirection table of an I/O APIC. NOTE: the affected code was moved to the ioapic_service function before the vulnerability was announced. Break-Fix: 2c2bf01136971c33e3b3fabce23925f372c1017e 5678de3f15010b9022ee45673f33bcfc71d47b60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1312987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 887291] Re: CVE-2011-3638
** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Lucid) Status: New => 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/887291 Title: CVE-2011-3638 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: Invalid Status in “linux-lts-backport-natty” package in Ubuntu: Invalid Status in “linux-lts-backport-oneiric” 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-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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Fix Released 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: 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: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-backport-oneiric” 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 “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: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-backport-oneiric” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Invalid Status in “linux-lts-backport-natty” source package in Raring: Invalid Status in “linux-lts-backport-oneiric” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status in “linux-lts-backport-natty” source package in Saucy: Invalid Status in “linux-lts-backport-oneiric” 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: Invalid Status in “linux-lts-backport-natty” source package in Trusty: Invalid Status in “linux-lts-backport-oneiric” 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Invalid Status in “linux-lts-backport-natty” source package in Utopic: Invalid Status in “linux-lts-backport-oneiric” source package in Utopic: Invalid Status in “linux-lts-quantal” source package in Utopic: Invalid Status in “linux-lts-raring” source package in Utopic: Invalid Status in “linux-lts-saucy” source package in Utopic: Invalid Status in “linux-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: fs/ext4/extents.c in the Linux kernel before 3.0 does not mark a modified extent as dirty in certa
[Kernel-packages] [Bug 1326725] Re: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
Hi, I read the patch on #66, it looks very neat and fair enough. dualshock3nerd, after you applied the patch, you have to do the following steps to build a formal patch 1. git add -u 2. git commit -a -e -s Write the subject and comment for your patch, it will be more clear to add "UBUNTU: SAUCE: " in the subject And you should put "BugLink: https://bugs.launchpad.net/bugs/1326725"; in your comment 3. git format-patch -1 4. the send out the patch which git generate to kernel-t...@lists.ubuntu.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326725 Title: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic Status in “linux” package in Ubuntu: Confirmed Bug description: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: "Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode" After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1/2-1.1.3.1:1.0/input/input22 Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:0268.000E: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:1d.0-1.1.3.1/input0 Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38 Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1" Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358025] Re: package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x31010000_40.dfu', which is also in package bt-dw1705-firmwa
I did: sudo apt-get install -f sudo apt-get clean sudo apt-get update But I got this message when I tried to install again: Preparando para substituir linux-firmware 1.79.1 (usando .../linux-firmware_1.79.16_all.deb) ... Desempacotando substituto linux-firmware ... dpkg: erro processando /var/cache/apt/archives/linux-firmware_1.79.16_all.deb (--unpack): a tentar sobre-escrever '/lib/firmware/ar3k/ramps_0x3101_40.dfu', que também está no pacote bt-dw1705-firmware 0.2 dpkg-deb: erro: subprocesso colar foi finalizado pelo sinal (Pipe quebrado) Erros foram encontrados durante o processamento de: /var/cache/apt/archives/linux-firmware_1.79.16_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1358025 Title: package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: I don't know what do 'cause it's caused when I'm trying to install a automatica atualization. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79.1 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 AptOrdering: linux-firmware: Install linux-firmware: Configure Architecture: amd64 Date: Sun Aug 17 17:50:43 2014 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DpkgTerminalLog: Preparing to replace linux-firmware 1.79.1 (using .../linux-firmware_1.79.16_all.deb) ... Unpacking replacement linux-firmware ... dpkg: error processing /var/cache/apt/archives/linux-firmware_1.79.16_all.deb (--unpack): trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 ErrorMessage: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package bt-dw1705-firmware 0.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1358025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362046] Re: kernel module (sony-laptop)
I did not use Ubuntu previously, I am new using Ubuntu 14.04 as my first Ubuntu in 3 month ago. and this issue become with Ubuntu at the beginning. I tried to install this version (http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.17-rc2-utopic/linux- headers-3.17.0-031700rc2-generic_3.17.0-031700rc2.201408251935_amd64.deb) but I get this error while installing: user@user-pc:~$ sudo dpkg -i linux-headers-3.17.0-031700rc2-generic_3.17.0-031700rc2.201408251935_amd64.deb (Reading database ... 228154 files and directories currently installed.) Preparing to unpack linux-headers-3.17.0-031700rc2-generic_3.17.0-031700rc2.201408251935_amd64.deb ... Unpacking linux-headers-3.17.0-031700rc2-generic (3.17.0-031700rc2.201408251935) over (3.17.0-031700rc2.201408251935) ... dpkg: dependency problems prevent configuration of linux-headers-3.17.0-031700rc2-generic: linux-headers-3.17.0-031700rc2-generic depends on linux-headers-3.17.0-031700rc2; however: Package linux-headers-3.17.0-031700rc2 is not installed. dpkg: error processing package linux-headers-3.17.0-031700rc2-generic (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-3.17.0-031700rc2-generic I tried to install with using `GDebi` and I get this error: user@user-pc:~$ sudo gdebi linux-headers-3.17.0-031700rc2-generic_3.17.0-031700rc2.201408251935_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Building data structures... Done Building data structures... Done This package is uninstallable Dependency is not satisfiable: linux-headers-3.17.0-031700rc2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362046 Title: kernel module (sony-laptop) Status in “linux” package in Ubuntu: Incomplete Bug description: "Laptop Keyboard Backlight not turning off" I had a problem with keyboard backlight that I asked in askUbuntu.com (here http://askubuntu.com/questions/475711/turn-off-keyboard-back-light-sony-vaio-svf1521dcxw) and also I have followed in chat with @Mew (here http://chat.stackexchange.com/transcript/16735) and We tried all solution to fixing my issue and we can not fix that. I found some patch (http://www.absence.it/vaio-acpi/source/patches/) for fixing this problem but then I need to create a custom kernel for myself and it's so hard for me. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kasiya 1906 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-27 (60 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Sony Corporation SVF1521DCXW NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=2aac8bca-f028-4744-a525-08ce1c46ff21 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0220DA dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0220DA:bd11/18/2013:svnSonyCorporation:pnSVF1521DCXW:pvrC10H89HU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVF1521DCXW dmi.product.version: C10H89HU dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1306621] Re: [LENOVO ThinkPad T440s] suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1306621 Title: [LENOVO ThinkPad T440s] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: 1. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2. linux-headers-3.13.0-23-generic: Installed: 3.13.0-23.45 Candidate: 3.13.0-23.45 Version table: *** 3.13.0-23.45 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3. Expected it to hibernate 4. It didn't. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sol2166 F pulseaudio /dev/snd/controlC0: sol2166 F pulseaudio Date: Fri Apr 11 09:53:08 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=027c0786-cb7e-48db-84dd-75553c948299 InstallationDate: Installed on 2014-02-15 (55 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214) InterpreterPath: /usr/bin/python3.4 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-23-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-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [LENOVO 20AQCTO1WW] suspend/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/1306621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305306] Re: 04f2:b3be [Sony VAIO SVP1321M2E] Webcam is distorted
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305306 Title: 04f2:b3be [Sony VAIO SVP1321M2E] Webcam is distorted Status in “linux” package in Ubuntu: Expired Bug description: Hi, My new Vaio Pro 13 has a webcam from Chicony which doesn't work properly. Using Cheese I can se myself for like a second, then the stream ends. In Google Hangouts my image contains static and is distorted (see attachement). Using streamer to take a snapshot the image looks fine in 640x480, but if I want it to take a HD image in 1280x720 I get an error and the output file looks as when in an hangout. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.19.23 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2105 F pulseaudio /dev/snd/controlC1: daniel 2105 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 9 22:52:05 2014 HibernationDevice: RESUME=UUID=a8a44495-3583-451d-99c8-b5be0e8cf0ca InstallationDate: Installed on 2014-04-09 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323) MachineType: Sony Corporation SVP1321M2EB ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1043V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1043V7:bd11/21/2013:svnSonyCorporation:pnSVP1321M2EB:pvrC60C0754:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVP1321M2EB dmi.product.version: C60C0754 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315316] Re: [Lenovo ThinkPad T440s] suspend/resume failing
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315316 Title: [Lenovo ThinkPad T440s] suspend/resume failing Status in “linux” package in Ubuntu: Expired Bug description: Sometimes, the system will appear to go to sleep mode (i.e. the LEDs will start indicating sleep mode). However, it appears to not suspend completely and the system produces a lot of heat while it is in this state which is rather dangerous if you put it in your sleeve and leave it there the system will overheat quickly. The problem exists both with the default Ubuntu and the mainline 3.14 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philipp1945 F pulseaudio /dev/snd/controlC1: philipp1945 F pulseaudio CurrentDesktop: Unity Date: Fri May 2 11:53:25 2014 HibernationDevice: RESUME=UUID=33297c91-85ea-4c06-a780-c68f69e46042 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20ARS0BH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=108e8269-9378-4695-84ff-e001a54e9e97 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARS0BH00 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:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20ARS0BH00:pvrThinkPadT440s:rvnLENOVO:rn20ARS0BH00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARS0BH00 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/1315316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1361086] Re: No card reader support for Realtek RTL8402 [ff00:5286]
** Changed in: hwe-next/trusty 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/1361086 Title: No card reader support for Realtek RTL8402 [ff00:5286] Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Committed Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: Impact: Realtek RTL8402 [ff00:5286], which is widely used by PC vendors, won't work without this fix. Fix: two patches below coming from upstream, clean cherry-picks. Testcase: we already tested and delivered the fix by dkms in OEM projects, works well. commit 56cb3cc1872923b69fdeeb00362b7da4d6cf5590 Author: Micky Ching Date: Wed Dec 18 10:03:13 2013 +0800 mfd: rtsx: Add support for card reader rtl8402 rtl8402 is much like rtl8411, so just add it to rtl8411.c Signed-off-by: Micky Ching Reviewed-by: Dan Carpenter Signed-off-by: Lee Jones commit 0da14eeba216932db2e4b8805ab58dae72e44a45 Author: Micky Ching Date: Wed Dec 18 10:03:12 2013 +0800 mfd: rtsx: Add set pull control macro and simplify rtl8411 Add set pull control macro to reduce code for setting pull control, and use a common init function to reduce code for rtl8411.c. So this patch is used to just simplify code. Signed-off-by: Micky Ching Reviewed-by: Dan Carpenter Signed-off-by: Lee Jones To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1361086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics
Thanks Andreas. Keeping this open in Mir just a bit longer so we don't lose track of it from the Mir side. When a fix is released to Mesa, we can mark it invalid for Mir. ** Changed in: mir Status: Invalid => 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/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics Status in Mir: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: In Progress Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362388] Re: [Dell Vostro 3446] Wireless key does not work on 14.04
This bug is similar to bug 1342548, could be fixed by adding a kernel parameter: acpi_osi=\"!Windows 2012\" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362388 Title: [Dell Vostro 3446] Wireless key does not work on 14.04 Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201402-14677 Dell Vostro 3446 The wireless key does not work on this system. With wireless key press, keycode 240 could be captured, but the scancode can't output with xev: KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio /dev/snd/controlC0: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Aug 27 22:24:42 2014 HibernationDevice: RESUME=UUID=863c857d-be2d-4f0c-9116-343d3909f4f6 InstallationDate: Installed on 2014-08-27 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3446 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed root=UUID=8954dce5-3f09-451d-9cb3-5bbbed643e9b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 00I010 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd02/24/2014:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn00I010:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1362388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362388] 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/1362388 Title: [Dell Vostro 3446] Wireless key does not work on 14.04 Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201402-14677 Dell Vostro 3446 The wireless key does not work on this system. With wireless key press, keycode 240 could be captured, but the scancode can't output with xev: KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio /dev/snd/controlC0: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Aug 27 22:24:42 2014 HibernationDevice: RESUME=UUID=863c857d-be2d-4f0c-9116-343d3909f4f6 InstallationDate: Installed on 2014-08-27 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3446 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed root=UUID=8954dce5-3f09-451d-9cb3-5bbbed643e9b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 00I010 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd02/24/2014:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn00I010:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1362388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362388] [NEW] [Dell Vostro 3446] Wireless key does not work on 14.04
Public bug reported: CID: 201402-14677 Dell Vostro 3446 The wireless key does not work on this system. With wireless key press, keycode 240 could be captured, but the scancode can't output with xev: KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio /dev/snd/controlC0: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Aug 27 22:24:42 2014 HibernationDevice: RESUME=UUID=863c857d-be2d-4f0c-9116-343d3909f4f6 InstallationDate: Installed on 2014-08-27 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3446 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed root=UUID=8954dce5-3f09-451d-9cb3-5bbbed643e9b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 00I010 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd02/24/2014:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn00I010:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Anthony Wong (anthonywong) Status: New ** Tags: 201402-14677 amd64 apport-bug blocks-hwcert staging taipei-lab trusty ** Also affects: hwe-next Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362388 Title: [Dell Vostro 3446] Wireless key does not work on 14.04 Status in HWE Next Project: New Status in “linux” package in Ubuntu: New Bug description: CID: 201402-14677 Dell Vostro 3446 The wireless key does not work on this system. With wireless key press, keycode 240 could be captured, but the scancode can't output with xev: KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0xbc, subw 0x0, time 66898396, (-365,-277), root:(823,313), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio /dev/snd/controlC0: ubuntu 1597 F pulseaudio ubuntu 4758 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Aug 27 22:24:42 2014 HibernationDevice: RESUME=UUID=863c857d-be2d-4f0c-9116-343d3909f4f6 InstallationDate: Installed on 2014-08-27 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Releas
[Kernel-packages] [Bug 1315948] Re: Ubuntu 14.04 reading CD/R + RW's
Retested on Ubuntu Kernel 3.13.0-35 and this bug is FIXED ** Changed in: linux (Ubuntu) Status: Triaged => 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/1315948 Title: Ubuntu 14.04 reading CD/R + RW's Status in “linux” package in Ubuntu: Fix Released Bug description: when ya put in a disk like a Blank CD/R or RW it reads it but it don't format or write on it at all Ive done tryed both Kernels 3.15* RC3 and 3.13.0.24 latest stable version as i know of and both dont read the CD's --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-29 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) NonfreeKernelModules: fglrx Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 2631 F pulseaudio /dev/snd/controlC0: darkangel 2631 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=74fb025e-334f-4b30-a12d-e87c16b01ec9 InstallationDate: Installed on 2014-04-29 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: eMachines EL1360G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=2c6528f4-334a-4ae9-8c5b-3b49213428bf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1341239] Re: Power button not recognized (no ACPI event produced)
** Tags added: kernel-bug-exists-upstream-3.17-rc1 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1341239 Title: Power button not recognized (no ACPI event produced) Status in “linux” package in Ubuntu: Confirmed Bug description: On a Dell Inspiron 1210 the power-button is not recognized with recent kernel versions. I know it is recognized with the linux- image-3.11.0-23-generic kernel. To reproduce: 1. boot normally with a "bad" kernel version (e.g. 3.13.0-32-generic, as provided in Ubuntu where the kernel is configured with the CONFIG_ACPI_BUTTON=y option) 2. switch to a console and log-in (or alternatively, open a terminal after logging in to a desktop env.) 3. run the "acpi_listen" executable from the terminal 4. press the power button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.56 ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edgimar2872 F pulseaudio CurrentDesktop: GNOME Date: Sun Jul 13 00:38:34 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2013-05-05 (433 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Dell Inc. Inspiron 1210 ProcFB: 0 psbdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=b4a760fe-3e39-4633-95aa-15c49fe5e916 ro mem=896mb reboot=pci quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-06-21 (21 days ago) dmi.bios.date: 05/03/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0X605H dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.asset.tag: ** dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/03/2009:svnDellInc.:pnInspiron1210:pvrA04:rvnDellInc.:rn0X605H:rvrA04:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 1210 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1346096] Re: [drm:init_ring_common] *ERROR* render ring initialization failed
Rebooted selecting 3.16.0-10 kernel and compiz and unity failed like they have been since 3.16.0-7. Failing uname -a: Linux Lenovo2 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Just did apt-get update & apt-get dist-upgrade 27 August. No help on this Lenovo ThinkCentre -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1346096 Title: [drm:init_ring_common] *ERROR* render ring initialization failed Status in “linux” package in Ubuntu: Incomplete Bug description: After last apt-get dist-upgrade my computer can not start with a graphic environment. It start but it's freeze in login screen (cursor blink not blink, it's all screen locked). I only can login into my Ubuntu from Grub > Advanced options > resume. Computer: Toshiba Satellite Pro U400-182 with Intel graphic card (Intel GM45 Chipset). Ubuntu version: Ubuntu 14.10 Utopic Unicorn (development branch) Kernel: Linux 3.16.0-4-generic #9-Ubuntu SMP Mon Jul 14 11:55:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Error in syslog is: Jul 18 11:00:14 lito-Ubuntu kernel: [2.420468] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 (valid? 1) head 0304 tail start 00503000 [expected 00503000] Jul 18 11:00:14 lito-Ubuntu kernel: [2.420478] [drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged Xorg log: [11.900] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [11.901] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000 [11.901] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100 [11.901] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200 [11.901] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [11.901] (II) FBDEV: driver for framebuffer: fbdev [11.901] (II) VESA: driver for VESA chipsets: vesa [11.901] (++) using VT number 7 [11.927] (EE) open /dev/dri/card0: No such file or directory [11.927] (WW) Falling back to old probe method for modesetting [11.927] (EE) open /dev/dri/card0: No such file or directory No errors in dmesg Related intel packages: ii intel-gpu-tools1.7-1amd64tools for debugging the Intel graphics driver ii libdrm-intel1:amd642.4.54-1 amd64Userspace interface to intel-specific kernel DRM ii libdrm-intel1:i386 2.4.54-1 i386 Userspace interface to intel-specific kernel DRM un libva-intel-vaapi-driv (no description available) ii xserver-xorg-video-int 2:2.99.910-0ubun amd64X.Org X server -- Intel i8xx, i9xx display driver Thanks in advance. --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lito 5855 F...m pulseaudio /dev/snd/pcmC0D0p: lito 5855 F...m pulseaudio /dev/snd/controlC0: lito 5855 F pulseaudio /dev/snd/seq:timidity 3621 F timidity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=fca42103-06f9-4fcd-bbca-9e8aba068dad InstallationDate: Installed on 2012-07-10 (740 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA Satellite Pro U400 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-generic root=UUID=3a477584-a099-4e62-879e-855c5aed40c3 ro recovery nomodeset ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-4-generic N/A linux-backports-modules-3.16.0-4-generic N/A linux-firmware1.132 Tags: utopic Uname: Linux 3.16.0-4-generic x86_64 UpgradeStatus: Upgraded to utopic on 2013-10-16 (277 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/26/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V5.00 dmi.board.name: Satellite Pro U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV5.00:bd10/26
[Kernel-packages] [Bug 1346096] Re: [drm:init_ring_common] *ERROR* render ring initialization failed
Just installed 3.16.0-6 .iso and upgraded today to 3.16.0-10. Both kernels are in /boot. If I select 3.16.0-10 boots to desktop, from past investigations that means compiz failed and hence unity failed. If I select 3.16.0-6 boots just fine, 3D and all. Since it's the same install, everything else in utopic is the same, just one kernel boots fine and the other does not. BTW, once in many many tries 3.16.0-10 does boot. That's how a race condition would behave, depending on what code gets past a certain point versus other code. This one runs: Linux Lenovo2 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 01:59:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz BTW, utopic 32 bit runs fine, compiz, unity and all. Lubuntu amd64 runs fine, no surprise, no compiz. Will boot the failing 3.16.0-10 and get it's LSPCI. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1346096 Title: [drm:init_ring_common] *ERROR* render ring initialization failed Status in “linux” package in Ubuntu: Incomplete Bug description: After last apt-get dist-upgrade my computer can not start with a graphic environment. It start but it's freeze in login screen (cursor blink not blink, it's all screen locked). I only can login into my Ubuntu from Grub > Advanced options > resume. Computer: Toshiba Satellite Pro U400-182 with Intel graphic card (Intel GM45 Chipset). Ubuntu version: Ubuntu 14.10 Utopic Unicorn (development branch) Kernel: Linux 3.16.0-4-generic #9-Ubuntu SMP Mon Jul 14 11:55:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Error in syslog is: Jul 18 11:00:14 lito-Ubuntu kernel: [2.420468] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 (valid? 1) head 0304 tail start 00503000 [expected 00503000] Jul 18 11:00:14 lito-Ubuntu kernel: [2.420478] [drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged Xorg log: [11.900] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [11.901] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000 [11.901] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100 [11.901] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200 [11.901] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [11.901] (II) FBDEV: driver for framebuffer: fbdev [11.901] (II) VESA: driver for VESA chipsets: vesa [11.901] (++) using VT number 7 [11.927] (EE) open /dev/dri/card0: No such file or directory [11.927] (WW) Falling back to old probe method for modesetting [11.927] (EE) open /dev/dri/card0: No such file or directory No errors in dmesg Related intel packages: ii intel-gpu-tools1.7-1amd64tools for debugging the Intel graphics driver ii libdrm-intel1:amd642.4.54-1 amd64Userspace interface to intel-specific kernel DRM ii libdrm-intel1:i386 2.4.54-1 i386 Userspace interface to intel-specific kernel DRM un libva-intel-vaapi-driv (no description available) ii xserver-xorg-video-int 2:2.99.910-0ubun amd64X.Org X server -- Intel i8xx, i9xx display driver Thanks in advance. --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lito 5855 F...m pulseaudio /dev/snd/pcmC0D0p: lito 5855 F...m pulseaudio /dev/snd/controlC0: lito 5855 F pulseaudio /dev/snd/seq:timidity 3621 F timidity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=fca42103-06f9-4fcd-bbca-9e8aba068dad InstallationDate: Installed on 2012-07-10 (740 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA Satellite Pro U400 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-generic root=UUID=3a477584-a099-4e62-879e-855c5aed40c3 ro recovery nomodeset ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersi
[Kernel-packages] [Bug 1356229] Re: Asus EeePC 1101HA PowerButton not working
Gašper Sedej, the next step is to fully commit bisect the linux kernel in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? ** 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/1356229 Title: Asus EeePC 1101HA PowerButton not working Status in “linux” package in Ubuntu: Incomplete Bug description: The power button stopped working with Ubuntu 14.04. The main issue is that it's not possible to wake up laptop from suspend (does not react to other keys/laptop lid) I did reaserch - the last working kernel is 3.12.26, from 3.13-rc1 it does not work anymore. I also tested 3.16 but still does not wokr. The problem is probably ACPI call which is connected with modules eeepc-laptop and eeepc-wmi - eeepc-laptop: "older", gets loaded when apci-osi=Linux . Work everything (except now power button) - eeepc-wmi: "newer", no kernel parameter. Very little works. does not work wifi hotkey (Fn+F2), and some others. I was not able to use wlan with -wmi module. I was suggested to do the bisecting, but I do not have time at the moment Also the eeepc-laptop module did not change much from 3.12 to 3.13 There is also forum topic about this http://ubuntuforums.org/showthread.php?t=2219864 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gasper 2382 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 69.002927] perf samples too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [ 163.177532] perf samples too long (5047 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 Date: Wed Aug 13 09:47:13 2014 HibernationDevice: RESUME=UUID=4a418b64-24f3-4f6a-861d-63e4839897ea InstallationDate: Installed on 2014-08-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 001 Device 002: ID 13d3:5108 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer INC. 1101HA ProcFB: 0 psbdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=c687e005-4892-4539-a302-a02f7069067d ro quiet splash acpi_backlight=vendor acpi_osi=Linux mem=1920mb vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0317 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1101HA 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.:bvr0317:bd09/24/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1101HA 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/1356229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1301019] Re: hyper-v: ifdown command not working due to bad ifstate
Hi Mark, It appears that the issue was there on 14.04 and has been fixed in 14.04.1. We can close this item. Thanks, Abhishek -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1301019 Title: hyper-v: ifdown command not working due to bad ifstate Status in “linux” package in Ubuntu: Confirmed Bug description: It appears that ifdown command is not working because “/run/network/ifstate" does not contain eth0=eth0. This in turn causes hyper-v's script hv_set_ifconfig.sh to fail as follows: root@ubuntu:~# ./hv_set_ifconfig.sh /var/lib/hyperv/ifcfg-eth0 ifdown: interface eth0 not configured RTNETLINK answers: File exists Failed to bring up eth0. It appears that something is wrong with your core networking files for trusty. Please could you help fix? Thanks, Abhishek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] 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/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in “linux” package in Ubuntu: Confirmed Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports "Could not grab image" or "ignoring empty buffer". The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] [NEW] uvcvideo doesn't work with USB webcam with linux 3.16
Public bug reported: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports "Could not grab image" or "ignoring empty buffer". The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in “linux” package in Ubuntu: New Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports "Could not grab image" or "ignoring empty buffer". The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.l
[Kernel-packages] [Bug 1297522] Re: Since Trusty /proc/diskstats shows weird values
Ok I found a patch that resolves the issue:
0fec08b4ecfc36fd8a64432343b2964fb86d2675
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1297522
Title:
Since Trusty /proc/diskstats shows weird values
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Trusty:
In Progress
Bug description:
After upgrading some virtual machines (KVM) to Trusty I noticed really
high I/O wait times, e.g. Munin graphs now show up to 200 seconds(!)
read I/O wait time. See attached image. Of course real latency isn't
higher than before, it's only /proc/diskstats that shows totally wrong
numbers...
$ cat /proc/diskstats | awk '$3=="vda" { print $7/$4, $11/$8 }'
1375.44 13825.1
From the documentation for /proc/diskstats field 4 is total number of
reads completed, field 7 is the total time spent reading in
milliseconds, and fields 8 and 11 are the same for writes. So above
numbers are the average read and write latency in milliseconds.
Same weird numbers with iowait. Note the column "await" (average time
in milliseconds for I/O requests):
$ iostat -dx 1 60
Linux 3.13.0-19-generic (munin) 03/25/14_x86_64_(2 CPU)
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 2.3016.75 72.45 24.52 572.79 778.3727.87
1.57 620.00 450.20 1121.83 1.71 16.54
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.00 0.000.000.00 0.00 0.00 0.00
0.000.000.000.00 0.00 0.00
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.00 0.000.000.00 0.00 0.00 0.00
0.000.000.000.00 0.00 0.00
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz
avgqu-sz await r_await w_await svctm %util
vda 0.0052.000.00 25.00 0.00 308.0024.64
0.30 27813.920.00 27813.92 0.48 1.20
I upgraded the host system to Trusty too, however there
/proc/diskstats output is normal as before.
$ uname -r
3.13.0-19-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1297522/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
** Patch removed: "0003-UBUNTU-SAUCE-no-up-ahci_xgene-Fix-the-link-down-in-f.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+attachment/4188528/+files/0003-UBUNTU-SAUCE-no-up-ahci_xgene-Fix-the-link-down-in-f.patch ** Patch added: "0003-UBUNTU-SAUCE-no-up-ahci_xgene-Fix-the-link-down-in-f.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+attachment/4188600/+files/0003-UBUNTU-SAUCE-no-up-ahci_xgene-Fix-the-link-down-in-f.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Triaged Bug description: [IMPACT] The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Fix specific to the xgene ahci driver hardreset function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
** Patch removed: "0002-UBUNTU-SAUCE-no-up-ahci_xgene-Skip-the-PHY-and-clock.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+attachment/4188527/+files/0002-UBUNTU-SAUCE-no-up-ahci_xgene-Skip-the-PHY-and-clock.patch ** Patch added: "0002-UBUNTU-SAUCE-no-up-ahci_xgene-Skip-the-PHY-and-clock.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+attachment/4188599/+files/0002-UBUNTU-SAUCE-no-up-ahci_xgene-Skip-the-PHY-and-clock.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Triaged Bug description: [IMPACT] Some disk types will never be seen after boot, while others can disappear after a reboot. This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Only affects the the xgene ahci driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
** Patch removed: "0001-UBUNTU-SAUCE-no-up-arm64-Fix-the-csr-mask-for-APM-X-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+attachment/4188500/+files/0001-UBUNTU-SAUCE-no-up-arm64-Fix-the-csr-mask-for-APM-X-.patch ** Patch added: "0001-UBUNTU-SAUCE-no-up-arm64-Fix-the-csr-mask-for-APM-X-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+attachment/4188598/+files/0001-UBUNTU-SAUCE-no-up-arm64-Fix-the-csr-mask-for-APM-X-.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Triaged Bug description: [IMPACT] The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. [TEST CASE] Attempt to boot from a disk attached to SATA Host controller 1. [Regression Potential] As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1291459] Re: ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4 card
It turns out that a much deeper fix is necessary, and I have not created
it. My current solution is to blacklist the driver. I plan to replace the card.
Alternatively, you could big the guys at Linux tv.org, the ones who write
the drivers in the first place. Launched doesn't seem to be where they hang
out.
The change I made was in the kernel source code. First you have to get the
ubuntu kernel source. After making the change, you have to recompile the
kernel module and copy it into the correct location. The process is very
technical and requires developer skills. But, it doesn't work as well as I
claimed.
Regards,
Ben Stanley
On 28 August 2014 5:21:08 AM Blowdesign <1291...@bugs.launchpad.net> wrote:
> Hi,
>
> How do fix this issue ?
>
> I've the same error :
>
> 3242.308051] xc2028 0-0061: i2c output error: rc = -95 (should be 64)
> [ 3242.308055] xc2028 0-0061: -95 returned from send
> [ 3242.317961] xc2028 0-0061: Error -22 while loading base firmware
> [ 3242.352112] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id
> .
> [ 3242.364130] cxusb: i2c wr: len=64 is too big!
>
> Where is the file drivers/media/tuners/tuner-xc2028 to change the
> MAX_XFER_SIZE ?
>
> Thanks in advance.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1291459
>
> Title:
> ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4
> card
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291459/+subscriptions
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1291459
Title:
ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4
card
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux-firmware” package in Ubuntu:
Confirmed
Bug description:
Top level symptom:
mythtv-backend fails to listen for client connections.
It stops at: (strace mythbackend)
open("/dev/dvb/adapter1/frontend0", O_RDWR|O_NONBLOCK) = 16
ioctl(16, FE_GET_INFO
me-tv also hangs in a similar manner.
I expected the ioctl call to succeed, and for the top level
applications to function properly. Instead, they hang.
The machine has 3 dvb tuners as follows:
Adapter 0
Mar 12 22:32:53 mythtv kernel: [ 17.428195] input: Budget-CI dvb ir
receiver saa7146 (0) as /devices/pci:00/:00:1e.0/:05
:00.0/rc/rc0/input13
Mar 12 22:32:53 mythtv kernel: [ 17.428251] rc0: Budget-CI dvb ir receiver
saa7146 (0) as /devices/pci:00/:00:1e.0/:05:0
0.0/rc/rc0
Mar 12 22:32:53 mythtv kernel: [ 17.432801] budget_ci dvb :05:00.0:
DVB: registering adapter 0 frontend 0 (Philips TDA10045H DVB
-T)...
Adapter 1
Mar 12 22:32:53 mythtv kernel: [ 17.646727] DVB: registering new adapter
(DViCO FusionHDTV DVB-T Dual Digital 4)
Mar 12 22:32:53 mythtv kernel: [ 17.797366] usb 3-1: DVB: registering
adapter 1 frontend 0 (Zarlink ZL10353 DVB-T)...
Adapter 2
Mar 12 22:32:53 mythtv kernel: [ 17.831769] DVB: registering new adapter
(DViCO FusionHDTV DVB-T Dual Digital 4)
Mar 12 22:32:53 mythtv kernel: [ 17.882250] cxusb: No IR receiver detected
on this device.
Mar 12 22:32:53 mythtv kernel: [ 17.882258] usb 3-2: DVB: registering
adapter 2 frontend 0 (Zarlink ZL10353 DVB-T)...
There appears to be a problem loading the firmware for the xc2028 in
the DViCO FusionHDTV card:
Mar 13 02:07:59 mythtv kernel: [ 37.348226] xc2028 10-0061: Loading
firmware for type=BASE F8MHZ (3), id .
Mar 13 02:07:59 mythtv kernel: [ 37.360226] cxusb: i2c wr: len=64 is too
big!
Mar 13 02:07:59 mythtv kernel: [ 37.360226]
Mar 13 02:07:59 mythtv kernel: [ 37.360230] xc2028 10-0061: i2c output
error: rc = -95 (should be 64)
Mar 13 02:07:59 mythtv kernel: [ 37.360231] xc2028 10-0061: -95 returned
from send
Mar 13 02:07:59 mythtv kernel: [ 37.360234] xc2028 10-0061: Error -22 while
loading base firmware
Mar 13 02:07:59 mythtv kernel: [ 37.412233] xc2028 11-0061: Loading
firmware for type=BASE F8MHZ (3), id .
Mar 13 02:07:59 mythtv kernel: [ 37.424360] cxusb: i2c wr: len=64 is too
big!
Mar 13 02:07:59 mythtv kernel: [ 37.424360]
Mar 13 02:07:59 mythtv kernel: [ 37.424364] xc2028 11-0061: i2c output
error: rc = -95 (should be 64)
Mar 13 02:07:59 mythtv kernel: [ 37.424365] xc2028 11-0061: -95 returned
from send
Mar 13 02:07:59 mythtv kernel: [ 37.424368] xc2028 11-0061: Error -22 while
loading base firmware
Mar 13 02:07:59 mythtv kernel: [ 37.428486] xc2028 10-0061: Loading
firmware for type=BASE F8MHZ (3), id .
Mar 13 02:07:59 mythtv kernel: [ 37.492247] xc2028 11-0061: Loading
firmware for type=BASE F8MHZ (3), id .
The firmware is loaded
[Kernel-packages] [Bug 1359514] Re: pci-xgene-msi: fixed deadlock in irq_set_affinity
** Patch removed: "0001-UBUNTU-SAUCE-no-up-pci-xgene-msi-fixed-deadlock-in-i.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+attachment/4188555/+files/0001-UBUNTU-SAUCE-no-up-pci-xgene-msi-fixed-deadlock-in-i.patch ** Patch added: "0001-UBUNTU-SAUCE-no-up-pci-xgene-msi-fixed-deadlock-in-i.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+attachment/4188597/+files/0001-UBUNTU-SAUCE-no-up-pci-xgene-msi-fixed-deadlock-in-i.patch ** Description changed: + [IMPACT] Issue: CPU affinity is changed while irqbalance is running. - - + Problem explanation: - - - Old code - - + Call xgene_msi_cascade function (CPU x) - - + raw_spin_lock(&desc->lock); (CPU x) - - + Goto generic_handle_irq (CPU x) - - + The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x - - + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt - - - New code - - + Use chained_irq_enter and exit as the standard way to cascade interrupt functions. + + + Problem explanation: + + - Old code + + + Call xgene_msi_cascade function (CPU x) + + + raw_spin_lock(&desc->lock); (CPU x) + + + Goto generic_handle_irq (CPU x) + + + The CPU x doesn't have a chance to exit the xgene_msi_cascade + function to unlock desc->lock before Linux scheduce and call + xgene_msi_set_affinity (irqbalance is caller) in the same CPU x + + + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, + flags) which cause deadlock to CPU x because it disables preempt + + - New code + + + Use chained_irq_enter and exit as the standard way to cascade + interrupt functions. + + [TEST CASE] + Turn off irqbalance + Run a single tcp stream + Randomly change the affinity of the receiving ring: + + @ ethtool -S $INTF | grep rx[0-9].*_pac @ - to detect the rx ring + @ grep $INTF /proc/interrupts@ - to find it's interrupt + @ printf "%x" $(( 2 ** $((RANDOM % 8)) )) > /proc/irq/$IRQ/smp_affinity @ - to change the affinity + + [Regression Potential] + Fix specific to the xgene pci msi code. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359514 Title: pci-xgene-msi: fixed deadlock in irq_set_affinity Status in “linux” package in Ubuntu: Triaged Bug description: [IMPACT] Issue: CPU affinity is changed while irqbalance is running. + Problem explanation: - Old code + Call xgene_msi_cascade function (CPU x) + raw_spin_lock(&desc->lock); (CPU x) + Goto generic_handle_irq (CPU x) + The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt - New code + Use chained_irq_enter and exit as the standard way to cascade interrupt functions. [TEST CASE] Turn off irqbalance Run a single tcp stream Randomly change the affinity of the receiving ring: @ ethtool -S $INTF | grep rx[0-9].*_pac @ - to detect the rx ring @ grep $INTF /proc/interrupts@ - to find it's interrupt @ printf "%x" $(( 2 ** $((RANDOM % 8)) )) > /proc/irq/$IRQ/smp_affinity @ - to change the affinity [Regression Potential] Fix specific to the xgene pci msi code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
** Description changed: + [IMPACT] The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. + + [TEST CASE] + Repeatedly reboot the system. + + [Regression Potential] + Fix specific to the xgene ahci driver hardreset function. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Triaged Bug description: [IMPACT] The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Fix specific to the xgene ahci driver hardreset function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
** Description changed: + [IMPACT] + Some disk types will never be seen after boot, while others can disappear after a reboot. + This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. + + [TEST CASE] + Repeatedly reboot the system. + + [Regression Potential] + Only affects the the xgene ahci driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Triaged Bug description: [IMPACT] Some disk types will never be seen after boot, while others can disappear after a reboot. This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Only affects the the xgene ahci driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
** Description changed: + [IMPACT] The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. + [TEST CASE] + Attempt to boot from a disk attached to SATA Host controller 1. + + [Regression Potential] As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Triaged Bug description: [IMPACT] The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. [TEST CASE] Attempt to boot from a disk attached to SATA Host controller 1. [Regression Potential] As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359514] Re: pci-xgene-msi: fixed deadlock in irq_set_affinity
** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359514 Title: pci-xgene-msi: fixed deadlock in irq_set_affinity Status in “linux” package in Ubuntu: Triaged Bug description: Issue: CPU affinity is changed while irqbalance is running. + Problem explanation: - Old code + Call xgene_msi_cascade function (CPU x) + raw_spin_lock(&desc->lock); (CPU x) + Goto generic_handle_irq (CPU x) + The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt - New code + Use chained_irq_enter and exit as the standard way to cascade interrupt functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359514] Re: pci-xgene-msi: fixed deadlock in irq_set_affinity
[IMPACT] The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x. In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt. Use chained_irq_enter and exit as the standard way to cascade interrupt functions. [TEST CASE] Turn off irqbalance Run a single tcp stream Randomly change the affinity of the receiving ring: @ ethtool -S $INTF | grep rx[0-9].*_pac @ - to detect the rx ring @ grep $INTF /proc/interrupts@ - to find it's interrupt @ printf "%x" $(( 2 ** $((RANDOM % 8)) )) > /proc/irq/$IRQ/smp_affinity @ - to change the affinity [Regression Potential] Fix specific to the xgene pci msi code. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359514 Title: pci-xgene-msi: fixed deadlock in irq_set_affinity Status in “linux” package in Ubuntu: Confirmed Bug description: Issue: CPU affinity is changed while irqbalance is running. + Problem explanation: - Old code + Call xgene_msi_cascade function (CPU x) + raw_spin_lock(&desc->lock); (CPU x) + Goto generic_handle_irq (CPU x) + The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt - New code + Use chained_irq_enter and exit as the standard way to cascade interrupt functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359514] Re: pci-xgene-msi: fixed deadlock in irq_set_affinity
** Patch added: "0001-UBUNTU-SAUCE-no-up-pci-xgene-msi-fixed-deadlock-in-i.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+attachment/4188555/+files/0001-UBUNTU-SAUCE-no-up-pci-xgene-msi-fixed-deadlock-in-i.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359514 Title: pci-xgene-msi: fixed deadlock in irq_set_affinity Status in “linux” package in Ubuntu: Confirmed Bug description: Issue: CPU affinity is changed while irqbalance is running. + Problem explanation: - Old code + Call xgene_msi_cascade function (CPU x) + raw_spin_lock(&desc->lock); (CPU x) + Goto generic_handle_irq (CPU x) + The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt - New code + Use chained_irq_enter and exit as the standard way to cascade interrupt functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Triaged Bug description: The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
Can you also send the patch to the kernel team mailing list: kernel-t...@lists.ubuntu.com ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Triaged Bug description: This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
Can you also send the patch to the kernel team mailing list: kernel-t...@lists.ubuntu.com ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Triaged Bug description: The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Confirmed Bug description: This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Confirmed Bug description: The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
** Patch added: "0003-UBUNTU-SAUCE-no-up-ahci_xgene-Fix-the-link-down-in-f.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+attachment/4188528/+files/0003-UBUNTU-SAUCE-no-up-ahci_xgene-Fix-the-link-down-in-f.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Confirmed Bug description: The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Confirmed Bug description: The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
[IMPACT] The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Fix specific to the xgene ahci driver hardreset function. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Confirmed Bug description: The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
** Patch added: "0002-UBUNTU-SAUCE-no-up-ahci_xgene-Skip-the-PHY-and-clock.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+attachment/4188527/+files/0002-UBUNTU-SAUCE-no-up-ahci_xgene-Skip-the-PHY-and-clock.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Confirmed Bug description: This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
[IMPACT] Some disk types will never be seen after boot, while others can disappear after a reboot. This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. [TEST CASE] Repeatedly reboot the system. [Regression Potential] Only affects the the xgene ahci driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Confirmed Bug description: This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350480] Re: [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in
A patch was sent to stable. However, some of the stable kernel versions fail to build with this patch, 3.2.y and 3.13.y for example. This is because the function 'find_trb_seg' is still called by xhci_cmd_to_noop, which is removed from mainline but still exists in the stable kernels. The patch removes the definition of find_trb_seg, which is what causes the build to fail. I built a trusty test kernel with a modified version of the upstream patch to not remove the find_trb_seg function. If this patch resolves this bug, we can ask the 3.13 upstream stable maintainer to modify the patch similarly as well as ask for an SRU to trusty with the fix. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1350480 Can you give this latest kernel a test and see if it resolves the 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/1350480 Title: [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Precise: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress Bug description: The latest kernel update in Ubuntu 14.04 LTS (3.13.0-32.57) renders our Intel NUCs unbootable, when we cold boot and have USB devices (keyboard, mouse, USB/Ethernet adapter) connected. The 3.13.0-24.47 kernel does not exhibit this behavior. Our particular NUCs have the i5-3427U processor, which is the D53427RKE board (DC53427HYE kit). These reports seem to be related: http://support.sundtek.com/index.php/topic,1600.0.html http://en.it-usenet.org/thread/19505/17700/ --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1400 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=37e4ff56-b945-4604-a94d-557bdf83e0b2 InstallationDate: Installed on 2014-07-30 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=c0597da2-7d4a-4340-b85a-c7f96d8262d7 ro ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2013 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0017.2013.0425.1251 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87790-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0017.2013.0425.1251:bd04/25/2013:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87790-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1350480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1361745] Re: X240 Sierra LTE modem requires cdc_ncm prefer_mbim=Y
Can you see if this is already fixed in the latest upstream 3.13 stable kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.6-trusty/ If the bug still exists in 3.13.11.6, we can perform a reverse bisect to identify the commit that fixes this in 3.17-rc2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1361745 Title: X240 Sierra LTE modem requires cdc_ncm prefer_mbim=Y Status in “linux” package in Ubuntu: Confirmed Bug description: On a Lenovo X240, the Sierra EM7345 LTE modem (1199:a001) requires that the cdc_ncm module be loaded with: prefer_mbim=Y before NetworkManager sees it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jpds 2097 F pulseaudio /dev/snd/controlC0: jpds 2097 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 26 16:06:00 2014 HibernationDevice: RESUME=UUID=6d276746-821e-47c3-b2d9-16b936682dd1 InstallationDate: Installed on 2014-08-26 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20ALCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 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:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ALCTO1WW dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1361745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362313] [NEW] a2dp bluetooth music playback broken after bluetooth device reconnect
Public bug reported: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are "timeout" error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:02:72:CC:E6:D5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:100536 acl:18 sco:0 events:14179 errors:0 TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0 syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: /org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1362313 Title: a2dp bluetooth music playback broken after bluetooth device reconnect Status in “bluez” package in Ubuntu: New Bug description: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are "timeout" error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 dmi.board.vendor
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
Can you also send the patch to the kernel team mailing list: kernel-t...@lists.ubuntu.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Confirmed Bug description: The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1326725] Re: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
It might be worth sending the latest patch to the ubuntu kernel team mailing list: kernel-t...@lists.ubuntu.com And also cc the engineer that resolved bug 1305522 acelan@canonical.com That way the patch can be reviewed and possibly considered for an SRU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326725 Title: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic Status in “linux” package in Ubuntu: Confirmed Bug description: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: "Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode" After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1/2-1.1.3.1:1.0/input/input22 Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:0268.000E: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:1d.0-1.1.3.1/input0 Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38 Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1" Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
** Changed in: linux (Ubuntu) Status: Invalid => 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/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Confirmed Bug description: This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
** Patch added: "0001-UBUNTU-SAUCE-no-up-arm64-Fix-the-csr-mask-for-APM-X-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+attachment/4188500/+files/0001-UBUNTU-SAUCE-no-up-arm64-Fix-the-csr-mask-for-APM-X-.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Confirmed Bug description: The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Confirmed Bug description: The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
[IMPACT] The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. [TEST CASE] Attempt to boot from a disk attached to SATA Host controller 1. [Regression Potential] As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Confirmed Bug description: The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359514] Re: pci-xgene-msi: fixed deadlock in irq_set_affinity
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359514 Title: pci-xgene-msi: fixed deadlock in irq_set_affinity Status in “linux” package in Ubuntu: Confirmed Bug description: Issue: CPU affinity is changed while irqbalance is running. + Problem explanation: - Old code + Call xgene_msi_cascade function (CPU x) + raw_spin_lock(&desc->lock); (CPU x) + Goto generic_handle_irq (CPU x) + The CPU x doesn't have a chance to exit the xgene_msi_cascade function to unlock desc->lock before Linux scheduce and call xgene_msi_set_affinity (irqbalance is caller) in the same CPU x + In irq_set_affinity, call raw_spin_lock_irqsave(&desc->lock, flags) which cause deadlock to CPU x because it disables preempt - New code + Use chained_irq_enter and exit as the standard way to cascade interrupt functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359507] Re: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359507 Title: ahci_xgene: Fix the link down in first attempt for the APM X-Gene SoC AHCI SATA host controller driver Status in “linux” package in Ubuntu: Confirmed Bug description: The link down issue in first attempt happens due to 2 H/W errata below: 1. Due to HW errata, during speed negotiation, sometimes controller is not able to detect ALIGN at GEN3(6Gbps) within 54.6us results in a timeout. This issue can be recovered by issuing a COMRESET again. 2. Due to HW errata, although ALIGH detection is successfull, due to 8b/10b and disparity BERR, sometimes the signature from the drive is not received successfully by the Host controller. Due to this the communication with the host and drive is not established due to locking of CDR(clock and data recovery) circuit. This issue can be recovered by issuing a COMRESET again. This patch fixes the above issues by retrying the COMRESET with a maximum attempts of 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362118] Re: [Apple Inc. MacBookPro8, 2] suspend/resume failure [non-free: wl]
Yes, it was happening in Trusty too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362118 Title: [Apple Inc. MacBookPro8,2] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Incomplete Bug description: Screen remains in blank after resume from suspend. I have to restart the graphical environment from a tty to get an usable desktop. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pulse 12926 F pulseaudio /dev/snd/controlC1: pulse 12926 F pulseaudio Date: Wed Aug 27 09:03:25 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookPro8,2:MBP81.88Z.0047.B27.1201241646 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-10-31 (299 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookPro8,2 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb 1 inteldrmfb ProcKernelCmdLine: \boot\vmlinuz-3.16.0-10-generic ro root=UUID=dc72a6ab-bd38-4a3e-ad02-39353a4c68b3 initrd=boot\initrd.img-3.16.0-10-generic 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.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 SourcePackage: linux Title: [Apple Inc. MacBookPro8,2] suspend/resume failure [non-free: wl] UpgradeStatus: Upgraded to utopic on 2014-08-20 (6 days ago) UserGroups: WifiSyslog: dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,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/1362118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1291459] Re: ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4 card
Hi,
How do fix this issue ?
I've the same error :
3242.308051] xc2028 0-0061: i2c output error: rc = -95 (should be 64)
[ 3242.308055] xc2028 0-0061: -95 returned from send
[ 3242.317961] xc2028 0-0061: Error -22 while loading base firmware
[ 3242.352112] xc2028 1-0061: Loading firmware for type=BASE F8MHZ (3), id
.
[ 3242.364130] cxusb: i2c wr: len=64 is too big!
Where is the file drivers/media/tuners/tuner-xc2028 to change the
MAX_XFER_SIZE ?
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/1291459
Title:
ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4
card
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux-firmware” package in Ubuntu:
Confirmed
Bug description:
Top level symptom:
mythtv-backend fails to listen for client connections.
It stops at: (strace mythbackend)
open("/dev/dvb/adapter1/frontend0", O_RDWR|O_NONBLOCK) = 16
ioctl(16, FE_GET_INFO
me-tv also hangs in a similar manner.
I expected the ioctl call to succeed, and for the top level
applications to function properly. Instead, they hang.
The machine has 3 dvb tuners as follows:
Adapter 0
Mar 12 22:32:53 mythtv kernel: [ 17.428195] input: Budget-CI dvb ir
receiver saa7146 (0) as /devices/pci:00/:00:1e.0/:05
:00.0/rc/rc0/input13
Mar 12 22:32:53 mythtv kernel: [ 17.428251] rc0: Budget-CI dvb ir receiver
saa7146 (0) as /devices/pci:00/:00:1e.0/:05:0
0.0/rc/rc0
Mar 12 22:32:53 mythtv kernel: [ 17.432801] budget_ci dvb :05:00.0:
DVB: registering adapter 0 frontend 0 (Philips TDA10045H DVB
-T)...
Adapter 1
Mar 12 22:32:53 mythtv kernel: [ 17.646727] DVB: registering new adapter
(DViCO FusionHDTV DVB-T Dual Digital 4)
Mar 12 22:32:53 mythtv kernel: [ 17.797366] usb 3-1: DVB: registering
adapter 1 frontend 0 (Zarlink ZL10353 DVB-T)...
Adapter 2
Mar 12 22:32:53 mythtv kernel: [ 17.831769] DVB: registering new adapter
(DViCO FusionHDTV DVB-T Dual Digital 4)
Mar 12 22:32:53 mythtv kernel: [ 17.882250] cxusb: No IR receiver detected
on this device.
Mar 12 22:32:53 mythtv kernel: [ 17.882258] usb 3-2: DVB: registering
adapter 2 frontend 0 (Zarlink ZL10353 DVB-T)...
There appears to be a problem loading the firmware for the xc2028 in
the DViCO FusionHDTV card:
Mar 13 02:07:59 mythtv kernel: [ 37.348226] xc2028 10-0061: Loading
firmware for type=BASE F8MHZ (3), id .
Mar 13 02:07:59 mythtv kernel: [ 37.360226] cxusb: i2c wr: len=64 is too
big!
Mar 13 02:07:59 mythtv kernel: [ 37.360226]
Mar 13 02:07:59 mythtv kernel: [ 37.360230] xc2028 10-0061: i2c output
error: rc = -95 (should be 64)
Mar 13 02:07:59 mythtv kernel: [ 37.360231] xc2028 10-0061: -95 returned
from send
Mar 13 02:07:59 mythtv kernel: [ 37.360234] xc2028 10-0061: Error -22 while
loading base firmware
Mar 13 02:07:59 mythtv kernel: [ 37.412233] xc2028 11-0061: Loading
firmware for type=BASE F8MHZ (3), id .
Mar 13 02:07:59 mythtv kernel: [ 37.424360] cxusb: i2c wr: len=64 is too
big!
Mar 13 02:07:59 mythtv kernel: [ 37.424360]
Mar 13 02:07:59 mythtv kernel: [ 37.424364] xc2028 11-0061: i2c output
error: rc = -95 (should be 64)
Mar 13 02:07:59 mythtv kernel: [ 37.424365] xc2028 11-0061: -95 returned
from send
Mar 13 02:07:59 mythtv kernel: [ 37.424368] xc2028 11-0061: Error -22 while
loading base firmware
Mar 13 02:07:59 mythtv kernel: [ 37.428486] xc2028 10-0061: Loading
firmware for type=BASE F8MHZ (3), id .
Mar 13 02:07:59 mythtv kernel: [ 37.492247] xc2028 11-0061: Loading
firmware for type=BASE F8MHZ (3), id .
The firmware is loaded from the file xc3028-v27.fw:
Mar 13 02:07:42 mythtv kernel: [ 18.108746] xc2028 11-0061: creating new
instance
Mar 13 02:07:42 mythtv kernel: [ 18.108748] xc2028 11-0061: type set to
XCeive xc2028/xc3028 tuner
Mar 13 02:07:42 mythtv kernel: [ 18.108801] xc2028 11-0061: Loading 80
firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7
Mar 13 02:07:42 mythtv kernel: [ 18.109670] dvb-usb: DViCO FusionHDTV DVB-T
Dual Digital 4 successfully initialized and connected.
The firmware file /lib/firmware/xc3028-v27.fw belongs to the
linux-firmware-nonfree 1.14.ubuntu1 package. I have located instructions on the
origin of this file
(http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028#How_to_Obtain_the_Firmware)
and I have verified that the firmware file is identical to the one obtained
by that method.
The DViCO FusionHDTV card has been used for several years in this
machine. This problem only occurred after upgrading to saucy
salamander.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-18-generic 3.11.0-18.32
Pro
[Kernel-packages] [Bug 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359489 Title: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node Status in “linux” package in Ubuntu: Confirmed Bug description: The value of the csr-mask of the SATA PHY clock DTS node has a wrong value resulting a kernel panic as the clock/reset is not proper for the PHY of the SATA host controller 1. This patch fixes the correct csr-mask value of the SATA PHY clock DTS node for the SATA Host controller 1. As the 'ok' is the default status of a device tree node, this patch removes the status of the PHY clock node of SATA Host Controller 1. The status of the clock node is handled from the firmware based on the controller enabled/disabled by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362261] Re: CONFIG_DMA_CMA causes ttm performance problems/hangs
The CONFIG_DMA_CMA parameter was enabled in trusty in Ubuntu-3.13.0-24.46 by commit: a9d615a UBUNTU: Rebase to 2d3c627502f2a9b0a7de06a5a2df2365542a72c9 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Tags added: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362261 Title: CONFIG_DMA_CMA causes ttm performance problems/hangs Status in “linux” package in Ubuntu: Triaged Bug description: The x86_64 kernels have CONFIG_DMA_CMA enabled, this causes extrem hangs of at least the RADEON driver full discussion is here: http://lists.freedesktop.org/archives/dri- devel/2014-August/065842.html ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aschultz 2224 F pulseaudio /dev/snd/controlC1: aschultz 2224 F pulseaudio CurrentDesktop: XFCE Date: Wed Aug 27 18:57:02 2014 HibernationDevice: RESUME=UUID=702fb398-84d9-4e93-9b4b-980323bf2d53 MachineType: Hewlett-Packard HP EliteBook 8560w ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-10-generic root=UUID=9a10044a-a505-4049-b794-a0ab87709daa ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-07-21 (37 days ago) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1357148] Re: linux: 3.13.0-35.62 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-35.62 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:Friday, 15. August 2014 01:10 UTC kernel-phase-changed:Friday, 15. August 2014 01:10 UTC kernel-phase:Prepare kernel-stable-Prepare-package-end:Monday, 18. August 2014 15:07 UTC kernel-stable-Promote-to-proposed-start:Monday, 18. August 2014 15:07 UTC ppa-package-testing-start:Monday, 18. August 2014 15:08 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 19. August 2014 19:02 UTC kernel-stable-Verification-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Certification-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Security-signoff-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Regression-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Monday, 25. August 2014 16:02 UTC kernel-stable-Verification-testing-end:Monday, 25. August 2014 16:02 UTC kernel-stable-Certification-testing-end:Tuesday, 26. August 2014 10:03 UTC + kernel-stable-Regression-testing-end:Wednesday, 27. August 2014 19: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/1357148 Title: linux: 3.13.0-35.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-35.62 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:Friday, 15. August 2014 01:10 UTC kernel-phase-changed:Friday, 15. August 2014 01:10 UTC kernel-phase:Prepare kernel-stable-Prepare-package-end:Monday, 18. August 2014 15:07 UTC kernel-stable-Promote-to-proposed-start:Monday, 18. August 2014 15:07 UTC ppa-package-testing-start:Monday, 18. August 2014 15:08 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 19. August 2014 19:02 UTC kernel-stable-Verification-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Certification-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Security-signoff-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Regression-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Monday, 25. August 2014 16:02 UTC kernel-stable-Verification-testing-end:Monday, 25. August 2014 16:02 UTC kernel-stable-Certification-testing-end:Tuesday, 26. August 2014 10:03 UTC kernel-stable-Regression-testing-end:Wednesday, 27. August 2014 19:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1357148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: In Progress Status in “apparmor-easyprof-ubuntu” package in Ubuntu: In Progress Status in “cups” package in Ubuntu: In Progress Status in “cups-filters” package in Ubuntu: In Progress Status in “isc-dhcp” package in Ubuntu: In Progress Status in “libvirt” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “linux” package in Ubuntu: In Progress Status in “lxc” package in Ubuntu: Triaged Status in “rsyslog” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). Testing: * 14.04 system with backported kernel: TODO * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.10 system (non-Touch) with current apparmor userspace: TODO (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: TODO * apparmor-easyprof-ubuntu QRT touch image tests: TODO * 14.10 system (non-Touch) with updated apparmor userspace capable of supporting abstract, anonymous and fine-grained netlink socket: TODO (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: TODO (runs extensive tests (upstream and distro)) * exploratory manual testing: TODO (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: TODO * lxc: TODO (containers can be created, started, shutdown) * libvirt: TODO (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: TODO * apparmor-easyprof-ubuntu QRT touch image tests: TODO Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernel: * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: TODO (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.10 system with previous kernel lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: TODO (exploratory manual testing, lxc, libvirt, etc) * test-apparmor.py: TODO * lightdm guest session: TODO (login, start browser, logout) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: TODO (includes test-apparmor.py, exploratory manu
[Kernel-packages] [Bug 1360887] Re: ERROR @wl_cfg80211_get_tx_power : error (-1)
Hello, Trying to install the upstream kernel, I got this errors: Error! Bad return status for module build on kernel: 3.17.0-031700rc1-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/make.log for more information. /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/make.log: CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.o /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_alloc_linux_if’: /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c:1354:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup); ^ /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c:1354:8: error: ‘alloc_netdev’ undeclared (first use in this function) dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup); ^ /var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c:1354:8: note: each undeclared identifier is reported only once for each function it appears in make[1]: *** [/var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.o] Erreur 1 make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.141+bdcom/build] Erreur 2 make: quittant le répertoire « /usr/src/linux-headers-3.17.0-031700rc1-generic » -- lsmod | grep b43 b43 427679 0 bcma 56999 1 b43 mac80211 696913 1 b43 ssb67356 1 b43 cfg80211 514757 2 b43,mac80211 -- modinfo b43 filename: /lib/modules/3.17.0-031700rc1-generic/kernel/drivers/net/wireless/b43/b43.ko firmware: b43/ucode9.fw firmware: b43/ucode5.fw firmware: b43/ucode16_mimo.fw firmware: b43/ucode15.fw firmware: b43/ucode14.fw firmware: b43/ucode13.fw firmware: b43/ucode11.fw license:GPL author: Rafał Miłecki author: Gábor Stefanik author: Michael Buesch author: Stefano Brivio author: Martin Langer description:Broadcom B43 wireless driver srcversion: CF7FC0483204057CC3D84EB alias: ssb:v4243id0812rev10* alias: ssb:v4243id0812rev0F* alias: ssb:v4243id0812rev0D* alias: ssb:v4243id0812rev0C* alias: ssb:v4243id0812rev0B* alias: ssb:v4243id0812rev0A* alias: ssb:v4243id0812rev09* alias: ssb:v4243id0812rev07* alias: ssb:v4243id0812rev06* alias: ssb:v4243id0812rev05* alias: bcma:m04BFid0812rev2Acl* alias: bcma:m04BFid0812rev28cl* alias: bcma:m04BFid0812rev1Ecl* alias: bcma:m04BFid0812rev1Dcl* alias: bcma:m04BFid0812rev1Ccl* alias: bcma:m04BFid0812rev18cl* alias: bcma:m04BFid0812rev17cl* alias: bcma:m04BFid0812rev11cl* depends:bcma,ssb,mac80211,cfg80211 intree: Y vermagic: 3.17.0-031700rc1-generic SMP mod_unload modversions signer: Magrathea: Glacier signing key sig_key:0C:00:7B:F9:D9:6D:AB:00:92:97:01:86:6B:49:5C:5B:C8:77:5A:C9 sig_hashalgo: sha512 parm: bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int) parm: fwpostfix:Postfix for the .fw files to load. (string) parm: hwpctl:Enable hardware-side power control (default off) (int) parm: nohwcrypt:Disable hardware encryption. (int) parm: hwtkip:Enable hardware tkip. (int) parm: qos:Enable QOS support (default on) (int) parm: btcoex:Enable Bluetooth coexistence (default on) (int) parm: verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug (int) parm: pio:Use PIO accesses by default: 0=DMA, 1=PIO (int) parm: allhwsupport:Enable support for all hardware (even it if overlaps with the brcmsmac driver) (int) ifconfig -a loLink encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 Packets reçus:16 erreurs:0 :0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 Octets reçus:704 (704.0 B) Octets transmis:704 (704.0 B) - lshw -C network *-network NON-RÉCLAMÉ description: Network controller produit: BCM4360 802.11ac Wireless Network Adapter fabriquant: Broadcom Corporation identifiant matériel: 0 information bus: pci@:04:00.0 version: 03 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_lis
[Kernel-packages] [Bug 1362168] Re: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn
Did this issue occur in a previous version of Ubuntu, or is this a new issue? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 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.17-rc2-utopic/ ** 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/1362168 Title: ubuntu14.04.1 don't read sd card on laptop sony vaio vgn-tz31xn Status in “linux” package in Ubuntu: Incomplete Bug description: I have installed (connnected online) ubuntu 14.04.1 on my sony vaio vgntz31xn: the laptop don't read sd card with internal reader ricoh: It's not a problem hardware, because the reader go perfectly with windows. This is the print of lspci: 09:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 09:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 09:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) I've tried all the patches found in web&forum, but they are all older than 2 years and no one goes on my laptop: someone are these: http://goinggnu.wordpress.com/2009/11/12/read-your-sd-card-with-your- ubuntu-laptop/ http://forum.ubuntu-it.org/viewtopic.php?p=3705425#p3705425 http://sourceforge.net/projects/sdricohcs/ https://lkml.org/lkml/2007/10/1/375 http://ubuntuforums.org/showthread.php?t=766892 http://intr.overt.org/blog/?p=59 http://forum.ubuntu- it.org/viewtopic.php?f=47&t=522361&p=4634264&hilit=sd+ricoh#p4634264 Many of these cases have solved the problem updating the old version, but the newest doesn't work: it's strange. I would some help, if it's possible: I'm not very expert of Ubuntu, but I'm sure to leave windows and I would learn how. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1357148] Re: linux: 3.13.0-35.62 -proposed tracker
** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => 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/1357148 Title: linux: 3.13.0-35.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-35.62 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:Friday, 15. August 2014 01:10 UTC kernel-phase-changed:Friday, 15. August 2014 01:10 UTC kernel-phase:Prepare kernel-stable-Prepare-package-end:Monday, 18. August 2014 15:07 UTC kernel-stable-Promote-to-proposed-start:Monday, 18. August 2014 15:07 UTC ppa-package-testing-start:Monday, 18. August 2014 15:08 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 19. August 2014 19:02 UTC kernel-stable-Verification-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Certification-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Security-signoff-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-Regression-testing-start:Tuesday, 19. August 2014 21:01 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Monday, 25. August 2014 16:02 UTC kernel-stable-Verification-testing-end:Monday, 25. August 2014 16:02 UTC kernel-stable-Certification-testing-end:Tuesday, 26. August 2014 10:03 UTC kernel-stable-Regression-testing-end:Wednesday, 27. August 2014 19:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1357148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
