[Kernel-packages] [Bug 1118657] Re: Lenovo m490/k4350/b580/L530/k29 - ACPI Warnings for \_SB_.PCI0.LPCB.H_EC.LED_
** Changed in: hwe-next
Status: Incomplete = Triaged
** Changed in: hwe-next
Importance: High = Medium
** Changed in: linux (Ubuntu)
Importance: High = 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/1118657
Title:
Lenovo m490/k4350/b580/L530/k29 - ACPI Warnings for
\_SB_.PCI0.LPCB.H_EC.LED_
Status in HWE Next Project:
Triaged
Status in “linux” package in Ubuntu:
Triaged
Status in “linux” source package in Precise:
Confirmed
Status in “linux” source package in Quantal:
Confirmed
Bug description:
Suspend and hibernate stress test got failed with following errors in logs:
s3: HIGH Kernel message: [10512.177806] ACPI Warning: For
\_SB_.PCI0.LPCB.H_EC.LED_: Excess arguments - needs 1, found 2
(20110623/nspredef-326)
s4: HIGH Kernel message: [11728.328110] ACPI Warning: For
\_SB_.PCI0.LPCB.H_EC.LED_: Excess arguments - needs 1, found 2
(20110623/nspredef-326)
Steps:
1. Log into desktop
2. Run s3/s4 stress test for 30 times
Expected results:
Suspend and hibernate stress got passed without any error
Actual results:
s3/s4 got failures in log file
Diagnosis:
This warning is generated by the ACPI LED method expects 1 argument, but the
kernel driver thinkpad_acpi.c function led_set_status will evaluate the ACPI
LED method with two arguments (let and led_status):
Method (LED, 1, NotSerialized)
{
If (H8DR)
{
Store (Arg0, MLED)
}
Else
{
And (RBEC (0x0B), 0xFD, Local0)
Or (Local0, Arg0, Local0)
WBEC (0x0B, Local0)
}
}
and I also checked with lenovo thiinkpad x220, x200, seems it accepts two
arguments in ACPI LED method:
Method (LED, 2, NotSerialized)
{
Or (Arg0, Arg1, Local0)
If (\H8DR)
{
Store (Local0, HLCL)
}
Else
{
\WBEC (0x0C, Local0)
}
}
It seems the spec change, if yes, we might need the spec.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1118657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234905] Re: [Lenovo E535] High Failures reported Initial brightness and AMD MMCONFIG
The same root cause with bug#1243493,
please refer to,
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1243493/comments/2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1234905
Title:
[Lenovo E535] High Failures reported Initial brightness and AMD
MMCONFIG
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The following High Failures were produced during an fwts run on a
Lenovo E535 laptop:
High failures: 2
klog: HIGH Kernel message: [0.567391] [Firmware Bug]: ACPI: No _BQC
method, cannot determine initial brightness
klog: HIGH Kernel message: [0.668681] pnp 00:07: [Firmware Bug]: [mem
0x-0x disabled] covers only part of AMD MMCONFIG area
[mem 0xf800-0xfbff]; adding more reservations
---
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 1: Generic [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1831 F pulseaudio
/dev/snd/controlC0: ubuntu 1831 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xe8444000 irq 53'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 7
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xe844 irq 16'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa5106,0012'
Controls : 22
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=021fd550-dfce-44fa-86dc-30cde2d89701
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64
(20130820.1)
MachineType: LENOVO 3260S08
MarkForUpload: True
NonfreeKernelModules: fglrx wl
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=89049656-49ed-4ffc-a4cb-8f3051d497aa ro quiet splash initcall_debug
vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/31/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: HHET31WW (1.06 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3260S08
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrHHET31WW(1.06):bd05/31/2012:svnLENOVO:pn3260S08:pvrThinkPadEdgeE535:rvnLENOVO:rn3260S08:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3260S08
dmi.product.version: ThinkPad Edge E535
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1162372] Re: [SAMSUNG NP-R425-JS04] suspend/resume failure
I'm still affected by this bug, using Ubuntu 13.10 ** Changed in: linux (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1162372 Title: [SAMSUNG NP-R425-JS04] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: All the information is an automated report, but I have to add that with 13.04 this samsung r425 cannot wakeup after sleep - the screen remains black. ProblemType: KernelOops DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-15-generic 3.8.0-15.25 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: db 2184 F pulseaudio /dev/snd/controlC0: db 2184 F pulseaudio Date: Sat Mar 30 23:15:37 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=eebedcf7-36dc-4197-941b-b2583c990bc5 InstallationDate: Installed on 2013-03-30 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130326) InterpreterPath: /usr/bin/python3.3 MachineType: SAMSUNG ELECTRONICS CO., LTD. R425/R525 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=007b6c15-af6d-45c0-b709-953c25a2a95e 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.8.0-15-generic N/A linux-backports-modules-3.8.0-15-generic N/A linux-firmware1.104 SourcePackage: linux Title: [SAMSUNG ELECTRONICS CO., LTD. R425/R525] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/03/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05NS dmi.board.name: R425/R525 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05NS:bd07/03/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425/R525:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425/R525:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R425/R525 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1162372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1151664] Re: HP Pavilion g7 - FWTS failures when doing cert testing
** Changed in: linux (Ubuntu)
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/1151664
Title:
HP Pavilion g7 - FWTS failures when doing cert testing
Status in “linux” package in Ubuntu:
Fix Released
Bug description:
During cert testing, several FWTS tests returned HIGH or critical
failures. Logs are attached.
This occurred during hibernate, suspend and batch testing.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1599 F pulseaudio
/dev/snd/controlC0: ubuntu 1599 F pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xf0344000 irq 49'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xf034 irq 16'
Mixer name : 'IDT 92HD87B2/4'
Components : 'HDA:111d76d9,103c184b,00100107'
Controls : 18
Simple ctrls : 10
Date: Thu Mar 7 03:18:22 2013
HibernationDevice: RESUME=UUID=09dbe284-769a-4cba-95e3-b0c6e7c8d1f6
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic
root=UUID=12f59f42-f1b9-49fc-af07-88195f43aeee ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 184B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr079F1000501020100:rvnHewlett-Packard:rn184B:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 079F1000501020100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1148649] Re: HP Pavilion G7 - FWTS HIGH errors during suspend/resume and batch testing
** Changed in: linux (Ubuntu) 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/1148649 Title: HP Pavilion G7 - FWTS HIGH errors during suspend/resume and batch testing Status in “linux” package in Ubuntu: Fix Released Bug description: Gonna just start putting them all into a single bug for each machine, otherwise I'll be filing 2 - 4 bugs per machine just about every time I do a certification test ;-) So this is 12.04.2 plus latest SRU kernel for certification. FWTS reported HIGH errors during Hibernate, Suspend and batch testing. I've attached the logs from each. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fwts 0.25.06precise1 ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Mar 6 00:21:36 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fwts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1148649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 77370] Re: Laptop Fan always on after resume from suspend to RAM
1. before suspend, examine and remember all values of /sys/devices/virtual/thermal/cooling_device*/cur_state 2. after suspend, restore all values mentioned above. OR, for simplicity, just set the values of /sys/devices/virtual/thermal/cooling_device*/cur_state periodically. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/77370 Title: Laptop Fan always on after resume from suspend to RAM Status in “acpi” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Won't Fix Status in “linux-source-2.6.17” package in Ubuntu: Won't Fix Bug description: Binary package hint: initramfs-tools After doing a suspend to RAM, the fan is always on on my laptop, even if temperatures are low (where the fan would normally be off before going to sleep mode for the first time). I removed the /usr/share/initramfs-tools/hooks/thermal script and now everything works fine (fan behaviour is not anymore affected by the suspend to RAM). It seems like this script does a wrong initialization of something which is not needed on my PC. My laptop is a Toshiba satellite A100-308 with dual core centrino. I have a basic standard ACPI support, toshiba_acpi and omnibook kernel modules do not work with my hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/77370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 911210] Re: Kernel freeze on Acer Aspire 1510 since Maverick
Karl-Felix Glatzer, the next step is to fully commit bisect from Lucid to Maverick, 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/911210 Title: Kernel freeze on Acer Aspire 1510 since Maverick Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: On every boot all Kernels newer than 2.6.33-02063306 completely freeze on my Acer Aspire 1510 notebook. When the kernel freezes the fan gets louder and i can't switch ttys anymore nor use the magic sysrq combinations for a safe reboot so i have to hard reset the laptop by pressing the power key for a while. This happens regardless of the installed ubuntu version. At the moment i have a dual boot of lucid and precise and the bug is still present with the 3.2 linux kernel on precise although it works fine when i boot it with the current lucid kernel. I've made a picture of the freeze using the 3.2 linux kernel booting it with the --debug and without the quiet and splash kernel parameters. I'll upload it as soon as possible. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-37-generic 2.6.32-37.81 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 Uname: Linux 2.6.32-37-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: k1ll 1583 F pulseaudio CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden Card0.Amixer.info: Card hw:0 'nForce3'/'NVidia nForce3 with ALC250 at irq 22' Mixer name : 'Realtek ALC250 rev 2' Components : 'AC97a:414c4752' Controls : 33 Simple ctrls : 21 Date: Tue Jan 3 12:50:59 2012 HibernationDevice: RESUME=UUID=39897aa7-39bf-45f3-8dbe-732bf198cbbf InstallationMedia: Ubuntu 10.04.2 LTS Lucid Lynx - Release i386 (20110211.1) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0483:0321 SGS Thomson Microelectronics Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer,Inc. Aspire 1510 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-37-generic root=UUID=c0efd683-5f06-4a82-80e1-b23fdf8806c5 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux dmi.bios.date: 05/10/04 dmi.bios.vendor: Acer dmi.bios.version: 3A29 dmi.board.name: Aspire 1510 dmi.board.vendor: Acer,Inc. dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag XXX dmi.chassis.type: 1 dmi.chassis.vendor: Acer,Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr3A29:bd05/10/04:svnAcer,Inc.:pnAspire1510:pvrAspire1510:rvnAcer,Inc.:rnAspire1510:rvrRev.A:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 1510 dmi.product.version: Aspire 1510 dmi.sys.vendor: Acer,Inc. --- ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0483:0321 STMicroelectronics Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer,Inc. Aspire 1510 MarkForUpload: True Package: linux 3.12.0.2.4 PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic root=UUID=1605d023-943a-4512-8b73-3c32fc059a68 ro quiet splash ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 RfKill: Tags: trusty Uname: Linux 3.12.0-2-generic i686 UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1055506] Re: Failed to boot after upgrade to 12.04.1
** Tags removed: kernel-bug-exists-upstream-v3.6-rc7 ** Tags added: kernel-bug-exists-upstream-v3.12 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1055506 Title: Failed to boot after upgrade to 12.04.1 Status in The Linux Kernel: Won't Fix Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading (with do-release-upgrade) the OS to Ubuntu 12.04.1 LTS, the system failed to boot. It failed to find any disks. Boot process ended with the (initramfs) prompt. Output attached. Tried the following option with the new kernel (3.2.0-31-generic): noapic -- failed nolapic -- failed acpi=ht -- failed WORKAROUND: Add to boot options: acpi=off Falling back to old kernel (2.6.32-43-server) the system booted fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-31-generic 3.2.0-31.50 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 AcpiTables: AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Sep 24 09:08 seq crw-rw---T 1 root audio 116, 33 Sep 24 09:08 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 24 09:31:18 2012 HibernationDevice: RESUME=UUID=eaff9f20-4df4-40db-a79b-fe4b1a9d48ec InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release amd64 (20100427) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: CheckPoint P-20-00 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic root=UUID=3cb24138-2b7c-4dae-9de8-10ffda57c140 ro console=ttyS0,115200n8 acpi=off RelatedPackageVersions: linux-restricted-modules-3.2.0-31-generic N/A linux-backports-modules-3.2.0-31-generic N/A linux-firmware1.79.1 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-09-21 (2 days ago) dmi.bios.date: 03/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Bridgeport dmi.board.vendor: Intel dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Intel dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/26/2008:svnCheckPoint:pnP-20-00:pvrToBeFilledByO.E.M.:rvnIntel:rnBridgeport:rvrTobefilledbyO.E.M.:cvnIntel:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: P-20-00 dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: CheckPoint To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1055506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1055506] Re: Failed to boot after upgrade to 12.04.1
J Bauer, it wouldn't hurt to have a commit bisect done from 2.6.32-43-server to 3.2.0.31-generic in order to identify the offending commit following https://wiki.ubuntu.com/Kernel/KernelBisection . Despite this, it looks like the upstream consensus is this issue is BIOS driven, and they would prefer a fix there versus a quirk. Any information on the BIOS front? ** Changed in: linux (Ubuntu) Status: Incomplete = Triaged ** Summary changed: - Failed to boot after upgrade to 12.04.1 + [Checkpoint P-20-00] Failed to boot after upgrade to 12.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1055506 Title: [Checkpoint P-20-00] Failed to boot after upgrade to 12.04.1 Status in The Linux Kernel: Won't Fix Status in “linux” package in Ubuntu: Triaged Bug description: After upgrading (with do-release-upgrade) the OS to Ubuntu 12.04.1 LTS, the system failed to boot. It failed to find any disks. Boot process ended with the (initramfs) prompt. Output attached. Tried the following option with the new kernel (3.2.0-31-generic): noapic -- failed nolapic -- failed acpi=ht -- failed WORKAROUND: Add to boot options: acpi=off Falling back to old kernel (2.6.32-43-server) the system booted fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-31-generic 3.2.0-31.50 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 AcpiTables: AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Sep 24 09:08 seq crw-rw---T 1 root audio 116, 33 Sep 24 09:08 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 24 09:31:18 2012 HibernationDevice: RESUME=UUID=eaff9f20-4df4-40db-a79b-fe4b1a9d48ec InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release amd64 (20100427) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: CheckPoint P-20-00 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic root=UUID=3cb24138-2b7c-4dae-9de8-10ffda57c140 ro console=ttyS0,115200n8 acpi=off RelatedPackageVersions: linux-restricted-modules-3.2.0-31-generic N/A linux-backports-modules-3.2.0-31-generic N/A linux-firmware1.79.1 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-09-21 (2 days ago) dmi.bios.date: 03/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Bridgeport dmi.board.vendor: Intel dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Intel dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/26/2008:svnCheckPoint:pnP-20-00:pvrToBeFilledByO.E.M.:rvnIntel:rnBridgeport:rvrTobefilledbyO.E.M.:cvnIntel:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: P-20-00 dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: CheckPoint To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1055506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1212199] Re: 10ec:8168 [MSI P35 Neo] Network not working after resume from suspend
Liam Proven / Laurens Bosscher / Eustaquio Rangel, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report would delay your problem being addressed as quickly as possible. No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212199 Title: 10ec:8168 [MSI P35 Neo] Network not working after resume from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html workaround not working related ? info: https://github.com/torvalds/linux/commit/2a15cd2ff488a9fdb55e5e34060f499853b27c77 I am running Ubuntu 13.10 with the latest updates ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanuel1634 F pulseaudio CurrentDmesg: [ 18.315564] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Aug 14 13:42:10 2013 HibernationDevice: RESUME=UUID=c295bea4-fefe-4d3b-8f12-ee5b580946db InstallationDate: Installed on 2013-05-02 (103 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130502) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7360 MarkForUpload: True ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=86fe6e26-730a-49ee-9ef7-096ce5dedeb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-2-generic N/A linux-backports-modules-3.11.0-2-generic N/A linux-firmware1.113 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7360 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd11/11/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7360:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7360:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7360 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1226172] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
Ron, did this problem not occur in a release prior to Raring?
As well, in mainline testing, please ensure you are not testing the
daily folder (nightly as you called it), but the one at the bottom of
the list, as outlined in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226172/comments/18
.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1226172
Title:
iostat: Cannot open /proc/stat: Cannot allocate memory
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
I receive an intermittent error using iostat -k 5 : Cannot open
/proc/stat: Cannot allocate memory
This can also be simply reproduced by entering: cat /proc/stat, one
to several (~5-10) times.
strace on the cat /proc/stat method:
...exclude typical run-up...
fstat(3, {st_mode=S_IFREG|0644, st_size=1607664, ...}) = 0
mmap(NULL, 1607664, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd755b77000
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
open(/proc/stat, O_RDONLY)= -1 ENOMEM (Cannot allocate memory)
write(2, cat: , 5cat: )= 5
write(2, /proc/stat, 10/proc/stat) = 10
open(/usr/share/locale/locale.alias, O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd755d09000
read(3, # Locale name alias data base.\n#..., 4096) = 2570
read(3, , 4096) = 0
close(3)= 0
munmap(0x7fd755d09000, 4096)= 0
open(/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
...exclude typical throw-error via LC_MESSAGES/libc.mo...
/proc/meminfo detail:
# cat /proc/meminfo
MemTotal: 32947584 kB
MemFree: 302664 kB
Buffers: 154064 kB
Cached: 21284268 kB
SwapCached: 1728840 kB
Active: 12576792 kB
Inactive: 17279896 kB
Active(anon):5097984 kB
Inactive(anon): 3320844 kB
Active(file):7478808 kB
Inactive(file): 13959052 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 187617276 kB
SwapFree: 185330320 kB
Dirty: 148 kB
Writeback: 0 kB
AnonPages: 7048592 kB
Mapped: 104312 kB
Shmem: 604 kB
Slab:1947068 kB
SReclaimable:1523288 kB
SUnreclaim: 423780 kB
KernelStack:8800 kB
PageTables:38260 kB
NFS_Unstable: 0 kB
Bounce:0 kB
WritebackTmp: 0 kB
CommitLimit:204091068 kB
Committed_AS: 15333712 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 163292 kB
VmallocChunk: 34359457992 kB
HardwareCorrupted: 0 kB
AnonHugePages: 38912 kB
HugePages_Total: 0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
DirectMap4k: 333824 kB
DirectMap2M:14313472 kB
DirectMap1G:18874368 kB
This only seems to happens on specific hardware: Intel Server System P4000CP
/ S2600CP Motherboard, booted with kernel option: pci=conf1
This does NOT happen on very similar hardware: Intel Server R2312GZ /
S2600GZ Motherboard
Is there a possible memory, or kernel memory sysctl configurable I'm missing
here?
---
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Aug 23 07:12 seq
crw-rw---T 1 root audio 116, 33 Aug 23 07:12 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=98374fad-7836-4390-b311-614da0ca473c
InstallationDate: Installed on 2013-02-17 (210 days ago)
InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64
(20121017.2)
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 046b:ff10 American Megatrends, Inc. Virtual Keyboard
and Mouse
MachineType: Intel Corporation S2600CP ..
MarkForUpload: True
Package: linux 3.8.0.30.48
PackageArchitecture: amd64
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
[Kernel-packages] [Bug 1242773] Re: Network not working after sleep-mode
** Description changed: After reactivating PC from Sleep-Mode or Hibernate-Mode there is no networkconnection. All network-devices are listed as DEACTIVATED. Re- ACTIVATING doesn't help. Only Soution is to reboot computer. - Only working workaround at this time is to send PC into sleep-mode via - terminal using following code: + WORKAROUND: Perform sleep-mode via terminal: dbus-send --system --print-reply \ - --dest=org.freedesktop.UPower \ - /org/freedesktop/UPower \ - org.freedesktop.UPower.Suspend - - Afterwards everything works fine. + --dest=org.freedesktop.UPower \ + /org/freedesktop/UPower \ + org.freedesktop.UPower.Suspend ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: christoph 3148 F pulseaudio - christoph 11811 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: christoph 3148 F pulseaudio + christoph 11811 F pulseaudio Date: Mon Oct 21 18:14:25 2013 HibernationDevice: RESUME=UUID=f84c65b3-d309-41ff-9e6d-8cb7cdbba15c MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0baeeaae-3cde-4d40-be74-12ddfa54d6ba ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.11.0-12-generic N/A - linux-backports-modules-3.11.0-12-generic N/A - linux-firmware 1.116 + linux-restricted-modules-3.11.0-12-generic N/A + linux-backports-modules-3.11.0-12-generic N/A + linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (2 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. ** Summary changed: - Network not working after sleep-mode + [Dell XPS L502X] Network not working after sleep-mode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1242773 Title: [Dell XPS L502X] Network not working after sleep-mode Status in “linux” package in Ubuntu: Incomplete Bug description: After reactivating PC from Sleep-Mode or Hibernate-Mode there is no networkconnection. All network-devices are listed as DEACTIVATED. Re- ACTIVATING doesn't help. Only Soution is to reboot computer. WORKAROUND: Perform sleep-mode via terminal: dbus-send --system --print-reply \ --dest=org.freedesktop.UPower \ /org/freedesktop/UPower \ org.freedesktop.UPower.Suspend ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christoph 3148 F pulseaudio christoph 11811 F pulseaudio Date: Mon Oct 21 18:14:25 2013 HibernationDevice: RESUME=UUID=f84c65b3-d309-41ff-9e6d-8cb7cdbba15c MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0baeeaae-3cde-4d40-be74-12ddfa54d6ba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (2 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1250321] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1250321/+attachment/3909416/+files/ProcEnviron.txt -- 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/1250321 Title: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Dependencies: DistroRelease: Ubuntu 13.10 LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250321] Re: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX
** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909417/+files/kern.log -- 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/1250321 Title: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Dependencies: DistroRelease: Ubuntu 13.10 LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250321] Re: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX
I'm currently on a live session of an Xubuntu 13.10 64-bit flash drive which I was attempting to install over my Ubuntu 14.04 partition and when it got to the installing grub2 portion it crashed and now I have a log I can provide. ** Tags added: apport-collected ** Description changed: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. + --- + ApportVersion: 2.12.5-0ubuntu2 + Architecture: amd64 + CasperVersion: 1.336ubuntu1 + Dependencies: + + DistroRelease: Ubuntu 13.10 + LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) + MarkForUpload: True + Package: linux-firmware 1.116 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 + Tags: saucy + Uname: Linux 3.11.0-12-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/1250321 Title: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Dependencies: DistroRelease: Ubuntu 13.10 LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250321] Re: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909418/+files/syslog ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909416/+files/ProcEnviron.txt -- 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/1250321 Title: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Dependencies: DistroRelease: Ubuntu 13.10 LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1227678] Re: [Dell Inc. OptiPlex 7010] suspend/resume failure
vroetman, as a potential WORKAROUND, could you instead hibernate via a terminal: sudo pm-hibernate As well, I would test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ before following https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227678/comments/5 . ** Tags added: trusty ** Tags added: raring ** Changed in: linux (Ubuntu) Status: Incomplete = 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/1227678 Title: [Dell Inc. OptiPlex 7010] suspend/resume failure Status in “linux” package in Ubuntu: Triaged Bug description: This has happened multiple times. I suspend when I leave work. When I arrive in the morning the power light shows it is suspended, but when I press a key on the keyboard to wake up, it takes a few seconds, and then the system reboots. I don't know if the system has ever suspended/resumed correctly. I set the system firmware to run pure UEFI with no legacy drivers and I enabled Secure Boot. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-7-generic 3.11.0-7.13 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vic2295 F pulseaudio /dev/snd/controlC2: vic2295 F pulseaudio /dev/snd/controlC0: vic2295 F pulseaudio Date: Thu Sep 19 08:49:11 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=e96f77ca-f3de-400f-a340-7d80e17eddef InstallationDate: Installed on 2013-09-10 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130910) InterpreterPath: /usr/bin/python3.3 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: Dell Inc. OptiPlex 7010 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic.efi.signed root=UUID=75b07d7e-d28b-4b14-93ec-1d43abe9fbb9 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-7-generic N/A linux-backports-modules-3.11.0-7-generic N/A linux-firmware1.114 RfKill: SourcePackage: linux Title: [Dell Inc. OptiPlex 7010] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0GY6Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd06/10/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1245159] Re: [MacBookPro8, 2] Laptop keyboard activity and touchpad movements often interpreted as clicks
Maintainer Process - https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream Mailing list - linux-input -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1245159 Title: [MacBookPro8,2] Laptop keyboard activity and touchpad movements often interpreted as clicks Status in “linux” package in Ubuntu: Triaged Bug description: On a MacBookPro8,2, the track pad often fires off a click even when it is not pressed. This can happen when typing on the keyboard (not touching the trackpad) or when actually using the mouse but not clicking. Such events make it fairly unsafe to use GUI applications that do not have an undo function for each possible action. Nothing seems to make the false clicks more or less likely to happen. WORKAROUND: Use external keyboard and mouse. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 27 12:51:50 2013 InstallationDate: Installed on 2013-10-17 (10 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64+mac (20131016) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=140e28f3-4795-466b-9ea0-3264746c9186 ro quiet splash vt.handoff=7 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) 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. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-17 (10 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64+mac (20131016) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=140e28f3-4795-466b-9ea0-3264746c9186 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) 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/1245159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1220719] Re: NetworkManager not setting proper state after suspend
Angelos Sfakianakis / jradwans, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report would delay your problem being addressed as quickly as possible. No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220719 Title: NetworkManager not setting proper state after suspend Status in “linux” package in Ubuntu: Incomplete Bug description: This issue is being experienced on a Lenovo T430 laptop running 13.10 with the latest updates. It has been happening since roughly the time I upgraded to 13.10, but was not happening with 13.03 and the 3.11 kernel. After resuming from suspend, many times NetworkManager will not list any connections, will not connect to wired networks, and will only show Network Enabled unchecked in the drop-down menu. NetworkManager Status: tcameron@HOSTNAME:~$ nmcli nm status RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running asleep enabled enabledenabled disabled Using nmcli to set the sleep state to false re-enables networking manually. tcameron@HOSTNAME:~$ nmcli nm sleep false RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected enabled enabledenabled enabled tcameron@HOSTNAME:~$ nmcli nm status RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected enabled enabledenabled enabled ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu19 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 4 09:23:13 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-02 (305 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: snipped for privacy MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-08-14 (21 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1220719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250321] Re: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX
Once again it has crashed at the same spot Nov 15 11:13:27 xubuntu ubiquity: Setting up grub-efi-amd64-signed (1.22.1+2.00-19ubuntu2.1) ... Nov 15 11:14:29 xubuntu kernel: [ 1035.084269] CPU: 7 PID: 15508 Comm: efibootmgr Tainted: GF D 3.11.0-12-generic #19-Ubuntu Nov 15 11:14:29 xubuntu kernel: [ 1035.084465] [815b35fe] efivar_entry_get+0x2e/0x70 Nov 15 11:14:29 xubuntu kernel: [ 1035.084474] [815b42bd] efivar_show_raw+0x4d/0x130 Nov 15 11:14:29 xubuntu kernel: [ 1035.084481] [815b4862] efivar_attr_show+0x42/0x60 *ensue crashing frenzy* I'm not sure why the Xubuntu 13.10 ISO induces this crash when installing grub when Ubuntu 13.10/14.04 did not. -- 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/1250321 Title: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Dependencies: DistroRelease: Ubuntu 13.10 LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250321] Re: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX
I don't see any mentions of systemd-udevd or kthreadd in these logs like I took in my screenshots (of which I don't remember seeing issues with efibootmgr) so the bug with Xubuntu may or may not be related to the issue I'm having here, although I would assume there is some sort of connection somehow. I should probably try installing Ubuntu 13.10 and seeing if it does the same thing Xubuntu 13.10 is doing. -- 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/1250321 Title: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Dependencies: DistroRelease: Ubuntu 13.10 LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1164557] Re: [Lenovo ThinkPad R60] Laptop to hot - VID to high
** Tags removed: 3.12.0-2-generic regression-potential ** Tags added: lucid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1164557 Title: [Lenovo ThinkPad R60] Laptop to hot - VID to high Status in “linux” package in Ubuntu: Incomplete Bug description: My laptop goes to very high temperature. First I think it was a fan problem. I adjusted thinkfan to use the disengaged option. Now my fan is at maximum speed if the temperature goes over 67°C. But still it is not possible to run the laptop for a longer time an 100% CPU. It then overheats and stops working. For example just after clamscan starts working the fan is at maximum speed (5600 revolutions) and the temperature goes up over 85°C, the CPU usage is the about 70%. My standard governer is ondemand. By using powersave the temperature will be about 5-10°C decrease. My investigation show me that in my opinion the VID is to high. To verify this I do the following: - rdmsr -p0 [1] 0x0199 for every speed steps - the governer ondemand switches the MSR 0x199 between - 0x0613, which means 1GHz and 1.275V? - 0x081c, which means 1,33GHz and 1.3875V? - 0x0b28, which means 1,83GHz and 1.5375V? by 100% CPU the laptop overheats and stops - set the governer to userspace 1.833GHz - reduce the VID using: wrmsr -p0 [1] 0x0199 0x0b20 the temperature goes not over 65°C by starting load that goes to 100% CPU!. I see that the VID is always set to 0x0b28 when the governor change the speed to the highest speed. I don't know if the governor or an other kernel module set the VID The Sped (FID) is selected by the governor. The FID/VID vor maximum should be set to 0x0b20 instead 0x0B28 and every thing would fine. sudo lshw -C display; uname -a; lsb_release -a *-display description: VGA compatible controller product: Radeon Mobility X1400 vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 0 bus info: pci@:01:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d800-dfff ioport:2000(size=256) memory:ee00-ee00 memory:ee02-ee03 Linux BN591-LINUX 3.2.0-40-generic-pae #64-Ubuntu SMP Mon Mar 25 21:44:41 UTC 2013 i686 i686 i386 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 12.04.2 LTS Release: 12.04 Codename: precise --- ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3165 F pulseaudio CasperVersion: 1.336ubuntu1 CurrentDmesg: [ 71.182993] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 71.185122] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 71.982542] iwl3945 :03:00.0: loaded firmware version 15.32.2.9 [ 72.055058] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 72.055518] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131108) MachineType: LENOVO 9461DXG MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.12.0-2.5-generic 3.12.0 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 Tags: trusty Uname: Linux 3.12.0-2-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7CETD3WW (2.23 ) dmi.board.name: 9461DXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7CETD3WW(2.23):bd08/28/2009:svnLENOVO:pn9461DXG:pvrThinkPadR60:rvnLENOVO:rn9461DXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 9461DXG dmi.product.version: ThinkPad R60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1164557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1006765] Re: 1033:0194 Hot plugging USB3.0 express card Not possible
Roland, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ? Please provide a direct URL to your post once you have made it so that it may be tracked. Thank you for your understanding. ** 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/1006765 Title: 1033:0194 Hot plugging USB3.0 express card Not possible Status in “linux” package in Ubuntu: Triaged Bug description: On my Lenovo T520 hot plugging USB3.0 PCI AKE Express USB 3.0 5Gbps BC618 Express card not possible. Hot plugging USB devices in this Card is also not possible. In kern.log: May 31 09:54:48 roland kernel: [ 1441.460174] hub 3-0:1.0: hub_port_status failed (err = -19) May 31 09:54:48 roland kernel: [ 1441.460244] hub 3-0:1.0: hub_port_status failed (err = -19) May 31 09:54:49 roland kernel: [ 1442.066711] hub 4-0:1.0: hub_port_status failed (err = -19) May 31 09:54:49 roland kernel: [ 1442.066773] hub 4-0:1.0: hub_port_status failed (err = -19) May 31 09:55:02 roland kernel: [ 1455.659879] hub 3-0:1.0: hub_port_status failed (err = -19) May 31 09:55:02 roland kernel: [ 1455.659938] hub 3-0:1.0: hub_port_status failed (err = -19) May 31 09:55:03 roland kernel: [ 1456.250534] hub 4-0:1.0: hub_port_status failed (err = -19) May 31 09:55:03 roland kernel: [ 1456.250595] hub 4-0:1.0: hub_port_status failed (err = -19) May 31 09:55:05 roland kernel: [ 1458.940363] hub 4-0:1.0: hub_port_status failed (err = -19) May 31 09:55:05 roland kernel: [ 1458.940429] hub 4-0:1.0: hub_port_status failed (err = -19) Plugging out the USB3 Express card: no messages in kern.log !! WORKAROUND: Power on with PCI card and USB devices connected. Reconnecting devices after this is not possible. Re-Plugging the drive or other USB products are not recognized. WORKAROUND: sudo echo acpiphp /etc/modules Modify /etc/default/grub to have: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash pciehp_force=1 pciehp_poll_mode=1 and run: sudo update-grub --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roland 2949 F pulseaudio CRDA: country NL: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5330 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5490 - 5710 @ 40), (N/A, 27), DFS Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf272 irq 52' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21cf,0012 HDA:80862805,80860101,0010' Controls : 37 Simple ctrls : 14 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 4243W29 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=e5e65e59-f323-4df0-a813-dc393d2a4970 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic N/A linux-backports-modules-3.2.0-24-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei Tags: precise staging precise staging Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-04-24 (37 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243W29 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: LBNL02200 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1164557] Re: [Lenovo ThinkPad R60] Laptop to hot - VID to high
Rainer, as WORKAROUNDs, in addition to maxing out your fan speed, I was going to suggest using powersave governor setting. At this point, it would be helpful if a powertop was run and the top power consuming processes were identified. Could you please do this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1164557 Title: [Lenovo ThinkPad R60] Laptop to hot - VID to high Status in “linux” package in Ubuntu: Incomplete Bug description: My laptop goes to very high temperature. First I think it was a fan problem. I adjusted thinkfan to use the disengaged option. Now my fan is at maximum speed if the temperature goes over 67°C. But still it is not possible to run the laptop for a longer time an 100% CPU. It then overheats and stops working. For example just after clamscan starts working the fan is at maximum speed (5600 revolutions) and the temperature goes up over 85°C, the CPU usage is the about 70%. My standard governer is ondemand. By using powersave the temperature will be about 5-10°C decrease. My investigation show me that in my opinion the VID is to high. To verify this I do the following: - rdmsr -p0 [1] 0x0199 for every speed steps - the governer ondemand switches the MSR 0x199 between - 0x0613, which means 1GHz and 1.275V? - 0x081c, which means 1,33GHz and 1.3875V? - 0x0b28, which means 1,83GHz and 1.5375V? by 100% CPU the laptop overheats and stops - set the governer to userspace 1.833GHz - reduce the VID using: wrmsr -p0 [1] 0x0199 0x0b20 the temperature goes not over 65°C by starting load that goes to 100% CPU!. I see that the VID is always set to 0x0b28 when the governor change the speed to the highest speed. I don't know if the governor or an other kernel module set the VID The Sped (FID) is selected by the governor. The FID/VID vor maximum should be set to 0x0b20 instead 0x0B28 and every thing would fine. sudo lshw -C display; uname -a; lsb_release -a *-display description: VGA compatible controller product: Radeon Mobility X1400 vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 0 bus info: pci@:01:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d800-dfff ioport:2000(size=256) memory:ee00-ee00 memory:ee02-ee03 Linux BN591-LINUX 3.2.0-40-generic-pae #64-Ubuntu SMP Mon Mar 25 21:44:41 UTC 2013 i686 i686 i386 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 12.04.2 LTS Release: 12.04 Codename: precise --- ApportVersion: 2.12.6-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3165 F pulseaudio CasperVersion: 1.336ubuntu1 CurrentDmesg: [ 71.182993] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 71.185122] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 71.982542] iwl3945 :03:00.0: loaded firmware version 15.32.2.9 [ 72.055058] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 72.055518] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131108) MachineType: LENOVO 9461DXG MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.12.0-2.5-generic 3.12.0 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 Tags: trusty Uname: Linux 3.12.0-2-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7CETD3WW (2.23 ) dmi.board.name: 9461DXG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7CETD3WW(2.23):bd08/28/2009:svnLENOVO:pn9461DXG:pvrThinkPadR60:rvnLENOVO:rn9461DXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 9461DXG dmi.product.version: ThinkPad R60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1164557/+subscriptions --
[Kernel-packages] [Bug 1243647] Re: [Asus 1005HA] Resuming from suspend mode : suspend loop
Fred Saunier, is this partially solved scenario reproducible in the Trusty live environment via http://cdimage.ubuntu.com/daily- live/current/ ? ** 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/1243647 Title: [Asus 1005HA] Resuming from suspend mode : suspend loop Status in “linux” package in Ubuntu: Incomplete Bug description: Using 13.10 on my laptop (Asus EeePC 1005HA), the system goes into suspend mode when I close the lid. When opening the lid and pressing a key, the system wakes up and asks me for my password. This is the expected behavior. However, if the laptop is running on battery, the system will go back into suspend mode, within a few seconds ; it will do so each and every time I wake it up subsequently. If I connect the laptop to its PSU, it is acting as expected when resuming from suspend mode. I did not experience any such problem with 13.04. Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3 --- ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fred 3205 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=f25cda9a-ab3e-4873-9752-74587b66e784 InstallationDate: Installed on 2010-05-26 (1245 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: ASUSTeK Computer INC. 1005HA MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=cdc8fdab-17fe-413b-a9be-4e534a1e2776 ro quiet splash acpi_osi=Linux elevator=deadline vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 04/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1005HA 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.:bvr1601:bd04/18/2011:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1005HA 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/1243647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1097680] Re: CVE-2013-0160
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low -- 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/1097680 Title: CVE-2013-0160 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: 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: Fix Committed Status in “linux” source package in Lucid: In Progress 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: 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: 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 Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: 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-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: 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-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4”
[Kernel-packages] [Bug 1251333] Re: System freezes after suspend to RAM
Graeme Hewson, as per http://www.asus.com/Motherboards/M4A88TDM_EVOUSB3/#support an update is available for your BIOS (1801). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If not, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251333 Title: System freezes after suspend to RAM Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu Saucy with kernel 3.11.0-12 the system was OK, but after upgrading to kernel 3.11.0-13 I started experiencing the problem. After sleeping the system overnight, it would partially wake up but then be unresponsive. The previous time I had the problem I could enter a few letters of my password into LightDM, but then the system became unresponsive to the keyboard and mouse, and didn't respond to pings. Today (with some other Kubuntu upgrades installed in the meantime) there was just a black screen apart from the mouse cursor, and the system was unresponsive to the keyboard and mouse straight away after waking the system with the keyboard. It responded to pings, and I could open a TCP session to it on port 22, but sshd was unresponsive. If I sleep the system for only a short time, it wakes OK. I see messages in syslog about the TSC, so maybe that's the reason for the problem. Possibly related to bug 1241582. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghewson2761 F pulseaudio /dev/snd/controlC0: ghewson2761 F pulseaudio Date: Thu Nov 14 16:34:53 2013 InstallationDate: Installed on 2012-01-02 (682 days ago) InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=74c50ca0-562b-4669-93e3-eb1b729f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-20 (25 days ago) dmi.bios.date: 09/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1143800] Re: CVE-2013-0343
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1143800 Title: CVE-2013-0343 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: New 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-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: 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: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: 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-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal:
[Kernel-packages] [Bug 1251333] Re: System freezes after suspend to RAM
** 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/1251333 Title: System freezes after suspend to RAM Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu Saucy with kernel 3.11.0-12 the system was OK, but after upgrading to kernel 3.11.0-13 I started experiencing the problem. After sleeping the system overnight, it would partially wake up but then be unresponsive. The previous time I had the problem I could enter a few letters of my password into LightDM, but then the system became unresponsive to the keyboard and mouse, and didn't respond to pings. Today (with some other Kubuntu upgrades installed in the meantime) there was just a black screen apart from the mouse cursor, and the system was unresponsive to the keyboard and mouse straight away after waking the system with the keyboard. It responded to pings, and I could open a TCP session to it on port 22, but sshd was unresponsive. If I sleep the system for only a short time, it wakes OK. I see messages in syslog about the TSC, so maybe that's the reason for the problem. Possibly related to bug 1241582. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghewson2761 F pulseaudio /dev/snd/controlC0: ghewson2761 F pulseaudio Date: Thu Nov 14 16:34:53 2013 InstallationDate: Installed on 2012-01-02 (682 days ago) InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=74c50ca0-562b-4669-93e3-eb1b729f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-20 (25 days ago) dmi.bios.date: 09/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1244478] Re: 1814:3290 [HP 650 Notebook PC] Kernel update from 3.2.0-54 to 3.2.0-55 renders Ralink RT3290 Wireless (rt2800pci) unusable
Not Fix Released as per previous comments. ** Changed in: linux (Ubuntu) Status: Fix Released = 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/1244478 Title: 1814:3290 [HP 650 Notebook PC] Kernel update from 3.2.0-54 to 3.2.0-55 renders Ralink RT3290 Wireless (rt2800pci) unusable Status in “linux” package in Ubuntu: Triaged Bug description: On a Notebook HP 650 with Ubuntu 12.04 LTS 64-bit i received updates for kernel 3.2.0-55-generic (exactly 3.2.0-55.85) and starting the notebook with that kernel results in unavailable connection, no wifi. Starting from grub with previous kernel (3.2.0-54.82) solve the issue. WORKAROUND: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244478/comments/31 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giardia2010 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x5260 irq 44' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,103c1858,00100202 HDA:80862806,103c1858,0010' Controls : 25 Simple ctrls : 11 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-osaka-precise-amd64-20121101-2 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=9e6434e2-89cc-47ca-aa26-a2ac6825ff3c InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20121101-11:02 MachineType: Hewlett-Packard HP 650 Notebook PC MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-54-generic root=UUID=98bb0642-ce40-4a4b-956f-8c4f30c60aba ro i915.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50 RelatedPackageVersions: linux-restricted-modules-3.2.0-54-generic N/A linux-backports-modules-3.2.0-54-generic N/A linux-firmware1.79.7 StagingDrivers: mei Tags: precise running-unity staging Uname: Linux 3.2.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/19/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1858 dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd10/19/2012:svnHewlett-Packard:pnHP650NotebookPC:pvr088412005B10002600010:rvnHewlett-Packard:rn1858:rvr65.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 650 Notebook PC dmi.product.version: 088412005B10002600010 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1196155] Re: mei_me resets spamming dmesg
Its happen again [ 111.128181] mei_me :00:03.0: unexpected reset: dev_state = RESETTING [ 117.140090] mei_me :00:03.0: reset: connect/disconnect timeout. [ 117.140111] mei_me :00:03.0: unexpected reset: dev_state = RESETTING [ 123.152100] mei_me :00:03.0: reset: connect/disconnect timeout. [ 123.152119] mei_me :00:03.0: unexpected reset: dev_state = RESETTING christian@t61-ubuntu:~$ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1196155 Title: mei_me resets spamming dmesg Status in “linux” package in Ubuntu: Fix Released Bug description: As you can see from the dmesg attached I'm getting the following every 5-10 seconds: [11332.456035] mei_me :00:03.0: reset: connect/disconnect timeout. [11332.456044] mei_me :00:03.0: unexpected reset: dev_state = RESETTING This was happening with raring but I blacklisted the mei module. With saucy it seems mei is included directly and is no longer loaded as a module. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-1-generic 3.10.0-1.8 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: herb 2330 F pulseaudio /dev/snd/controlC0: herb 2330 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat Jun 29 18:57:30 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=878dad1b-8d2b-4879-8dea-862befaf67b9 InstallationDate: Installed on 2013-01-23 (157 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700p Convertible Minitower MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1-generic root=UUID=bcaf6352-17f6-4fa2-af31-127c04f60e6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.10.0-1-generic N/A linux-backports-modules-3.10.0-1-generic N/A linux-firmware1.110 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-06-29 (0 days ago) dmi.bios.date: 08/14/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v03.03 dmi.board.name: 0A58h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA741121G dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v03.03:bd08/14/2007:svnHewlett-Packard:pnHPCompaqdc7700pConvertibleMinitower:pvr:rvnHewlett-Packard:rn0A58h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc7700p Convertible Minitower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1243825] Re: wont resume when awakened from suspend
Addition: it turned out that removing proprietary video driver was not enough. Some problems disappeared but my laptop still sometimes didn't wake up from sleep. So I tried to upgrade kernel to 3.12 and now it looks like everything is all right again. I hope it will remain that way for a while. So in my case the problems were solved by 1. removing proprietary video drive, 2. upgrading kernel. How to upgrade the kernel: http://ubuntuhandbook.org/index.php/2013/11 /linux-kernel-3-12-released-install-ubuntu-or-linux-mint/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243825 Title: wont resume when awakened from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: I'm on an HP mini running 13.10 32 bit. After I got the update for this 13.10 from 13.04 my computer stopped waking up from suspension. Everything was perfect before the update. If you need more info, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1205284] Re: linux-tools naming is not scalable to multiple source packages
The apt fix for this should be backported to precise, and the linux-lts- saucy HWE kernels have the new linux-tools scheme, so we can actually retain them sanely via autoremove. ** Changed in: apt (Ubuntu Precise) Status: Invalid = In Progress ** Changed in: apt (Ubuntu Precise) Assignee: (unassigned) = Adam Conrad (adconrad) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1205284 Title: linux-tools naming is not scalable to multiple source packages Status in “apt” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux-goldfish” package in Ubuntu: Fix Released Status in “linux-lowlatency” package in Ubuntu: Fix Released Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-meta” package in Ubuntu: Fix Released Status in “linux-meta-goldfish” package in Ubuntu: Fix Released Status in “linux-meta-lowlatency” package in Ubuntu: Fix Released Status in “linux-meta-ppc” package in Ubuntu: Fix Released Status in “linux-ppc” package in Ubuntu: Fix Released Status in “apt” source package in Precise: In Progress Status in “linux” source package in Precise: Fix Committed Status in “linux-goldfish” source package in Precise: Invalid Status in “linux-lowlatency” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-meta” source package in Precise: Invalid Status in “linux-meta-goldfish” source package in Precise: Invalid Status in “linux-meta-lowlatency” source package in Precise: Invalid Status in “linux-meta-ppc” source package in Precise: Invalid Status in “linux-ppc” source package in Precise: Invalid Status in “apt” source package in Saucy: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux-goldfish” source package in Saucy: Fix Released Status in “linux-lowlatency” source package in Saucy: Fix Released Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-meta” source package in Saucy: Fix Released Status in “linux-meta-goldfish” source package in Saucy: Fix Released Status in “linux-meta-lowlatency” source package in Saucy: Fix Released Status in “linux-meta-ppc” source package in Saucy: Fix Released Status in “linux-ppc” source package in Saucy: Fix Released Bug description: The linux tools packages are not currently scalable to multiple source package branches. This is because the packages are actually per architecture (not flavour) in both contents and naming but may differ between source packages which may be at different versions. This prevents us safely emitting linux-tools packages from branches other than master. We have a policy of insulating people from the source package from which a kernel comes. We do this via the linux-thing-flavour package naming, which is consistant regardless of overall package. It therefore makes a lot of sense to extend this to the tools package. Such that we would have the following user consumable packages as below: linux-tools-flavour -- tools to match linux-image-flavour linux-tools-abi-flavour -- tools to match linux-image-abi-flavour In order to allow linux-tools to be still be a valid install target the first of these would additionally Provides: linux-tools to allow simple selection of the appropriate flavour specific package where there is only one, or to help the user make an informed choice where there is more. The first would be the logical choice when wanting to maintain tools installed for all future version of the kernel, mirroring the kernels as installed by the linux-flavour and linux-image-flavour packages and keeping the user up to date in tools. The second would be the appropriate package to request installation when trying to target a specific kernel version and would be used by the wrapper when requesting manual intervention such as when the linux-tools-flavour is not installed. The first of these would be added to the appropriate meta package, the second would come out of the flavour specific packages in the main kernel source package. Further we would then be able to name the actual binary packages as produced by the various source packages to be source package specific. Thus we would have packages as below: linux-tools-abi -- coming out of the master branch linux-grouper-tools-abi -- coming out of the grouper branch These would be hidden from the user via the previously listed meta packages and would not be direct installation candidates. There is also an additional linux-tools-common package which represents the manual pages and the wrappers. These would be only generated and installed from the master branch and all of
[Kernel-packages] [Bug 1205284] Re: linux-tools naming is not scalable to multiple source packages
Hello Andy, or anyone else affected, Accepted apt into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apt/0.8.16~exp12ubuntu10.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1205284 Title: linux-tools naming is not scalable to multiple source packages Status in “apt” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux-goldfish” package in Ubuntu: Fix Released Status in “linux-lowlatency” package in Ubuntu: Fix Released Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-meta” package in Ubuntu: Fix Released Status in “linux-meta-goldfish” package in Ubuntu: Fix Released Status in “linux-meta-lowlatency” package in Ubuntu: Fix Released Status in “linux-meta-ppc” package in Ubuntu: Fix Released Status in “linux-ppc” package in Ubuntu: Fix Released Status in “apt” source package in Precise: Fix Committed Status in “linux” source package in Precise: Fix Committed Status in “linux-goldfish” source package in Precise: Invalid Status in “linux-lowlatency” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-meta” source package in Precise: Invalid Status in “linux-meta-goldfish” source package in Precise: Invalid Status in “linux-meta-lowlatency” source package in Precise: Invalid Status in “linux-meta-ppc” source package in Precise: Invalid Status in “linux-ppc” source package in Precise: Invalid Status in “apt” source package in Saucy: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux-goldfish” source package in Saucy: Fix Released Status in “linux-lowlatency” source package in Saucy: Fix Released Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-meta” source package in Saucy: Fix Released Status in “linux-meta-goldfish” source package in Saucy: Fix Released Status in “linux-meta-lowlatency” source package in Saucy: Fix Released Status in “linux-meta-ppc” source package in Saucy: Fix Released Status in “linux-ppc” source package in Saucy: Fix Released Bug description: The linux tools packages are not currently scalable to multiple source package branches. This is because the packages are actually per architecture (not flavour) in both contents and naming but may differ between source packages which may be at different versions. This prevents us safely emitting linux-tools packages from branches other than master. We have a policy of insulating people from the source package from which a kernel comes. We do this via the linux-thing-flavour package naming, which is consistant regardless of overall package. It therefore makes a lot of sense to extend this to the tools package. Such that we would have the following user consumable packages as below: linux-tools-flavour -- tools to match linux-image-flavour linux-tools-abi-flavour -- tools to match linux-image-abi-flavour In order to allow linux-tools to be still be a valid install target the first of these would additionally Provides: linux-tools to allow simple selection of the appropriate flavour specific package where there is only one, or to help the user make an informed choice where there is more. The first would be the logical choice when wanting to maintain tools installed for all future version of the kernel, mirroring the kernels as installed by the linux-flavour and linux-image-flavour packages and keeping the user up to date in tools. The second would be the appropriate package to request installation when trying to target a specific kernel version and would be used by the wrapper when requesting manual intervention such as when the linux-tools-flavour is not installed. The first of these would be added to the appropriate
[Kernel-packages] [Bug 1236653]
I have compiled Mesa 10 master in /opt/mesa and added a conf file in /etc/ld.so.conf.d. Now glxinfo shows: OpenGL version string: 3.0 Mesa 10.0.0-devel (git-69b425e) OpenGL shading language version string: 1.30 OpenGL context flags: (none) This is the first time I have built mesa. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1236653 Title: Graphics performance reduced after playing games for a little bit Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Saucy. I noticed that everytime I play something like Counter Strike Source, my graphics performance drops down to something like 15fps while normally it is locked at a max FPS of 40fps.. This slowdown happens and also makes my computer generally pretty slow. Thermo maximum has not been tripped (I know, and I actually underclock while playing these games). I'm not sure why this is happening. It only happens on 13.10. I have bumblebee installed. I used both cards to play the game and the same thing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shuhao 2611 F pulseaudio shuhao 4063 F plugin-containe /dev/snd/pcmC0D0p: shuhao 4063 F...m plugin-containe /dev/snd/timer: shuhao 4063 f plugin-containe Date: Mon Oct 7 20:39:17 2013 HibernationDevice: RESUME=UUID=0c4e9477-6a74-48cb-a0e4-37bc3251580e InstallationDate: Installed on 2013-07-08 (91 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: LENOVO 4180J4C MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash i915.modeset=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create secure directory (/run/user/1000/pulse): Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180J4C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4180J4C:pvrThinkPadT420:rvnLENOVO:rn4180J4C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180J4C dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1236653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1236653]
Created attachment 88747 i915_error_state file after causing render ring hang in Google Maps This is the i915_error_state file after updating my system with the https://launchpad.net/~oibaf/+archive/graphics-drivers/ PPA (and restarting X of course) and scrolling around a lot in Google Maps in Google Chrome. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1236653 Title: Graphics performance reduced after playing games for a little bit Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Saucy. I noticed that everytime I play something like Counter Strike Source, my graphics performance drops down to something like 15fps while normally it is locked at a max FPS of 40fps.. This slowdown happens and also makes my computer generally pretty slow. Thermo maximum has not been tripped (I know, and I actually underclock while playing these games). I'm not sure why this is happening. It only happens on 13.10. I have bumblebee installed. I used both cards to play the game and the same thing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shuhao 2611 F pulseaudio shuhao 4063 F plugin-containe /dev/snd/pcmC0D0p: shuhao 4063 F...m plugin-containe /dev/snd/timer: shuhao 4063 f plugin-containe Date: Mon Oct 7 20:39:17 2013 HibernationDevice: RESUME=UUID=0c4e9477-6a74-48cb-a0e4-37bc3251580e InstallationDate: Installed on 2013-07-08 (91 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: LENOVO 4180J4C MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash i915.modeset=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create secure directory (/run/user/1000/pulse): Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180J4C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4180J4C:pvrThinkPadT420:rvnLENOVO:rn4180J4C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180J4C dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1236653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1236653]
Created attachment 88969 i915_error_state Still hang after playing hedgewars for nearly an hour, but it doesn't hang continuously, just one time. Dmesg shows: [ 3929.521951] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring [ 3929.521963] [drm:i915_hangcheck_elapsed] *ERROR* stuck on blitter ring [ 3929.521967] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state I notice that my error message has blitter ring. Is it a different 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/1236653 Title: Graphics performance reduced after playing games for a little bit Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Saucy. I noticed that everytime I play something like Counter Strike Source, my graphics performance drops down to something like 15fps while normally it is locked at a max FPS of 40fps.. This slowdown happens and also makes my computer generally pretty slow. Thermo maximum has not been tripped (I know, and I actually underclock while playing these games). I'm not sure why this is happening. It only happens on 13.10. I have bumblebee installed. I used both cards to play the game and the same thing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shuhao 2611 F pulseaudio shuhao 4063 F plugin-containe /dev/snd/pcmC0D0p: shuhao 4063 F...m plugin-containe /dev/snd/timer: shuhao 4063 f plugin-containe Date: Mon Oct 7 20:39:17 2013 HibernationDevice: RESUME=UUID=0c4e9477-6a74-48cb-a0e4-37bc3251580e InstallationDate: Installed on 2013-07-08 (91 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: LENOVO 4180J4C MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash i915.modeset=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create secure directory (/run/user/1000/pulse): Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180J4C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4180J4C:pvrThinkPadT420:rvnLENOVO:rn4180J4C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180J4C dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1236653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1236653]
(In reply to comment #33) Created attachment 88969 [details] i915_error_state Still hang after playing hedgewars for nearly an hour, but it doesn't hang continuously, just one time. Dmesg shows: [ 3929.521951] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring [ 3929.521963] [drm:i915_hangcheck_elapsed] *ERROR* stuck on blitter ring [ 3929.521967] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state I notice that my error message has blitter ring. Is it a different bug? Yes, IPEHR of 0x0b160001 suggests that your bug is actually: https://bugs.freedesktop.org/show_bug.cgi?id=54226 It is not this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1236653 Title: Graphics performance reduced after playing games for a little bit Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Saucy. I noticed that everytime I play something like Counter Strike Source, my graphics performance drops down to something like 15fps while normally it is locked at a max FPS of 40fps.. This slowdown happens and also makes my computer generally pretty slow. Thermo maximum has not been tripped (I know, and I actually underclock while playing these games). I'm not sure why this is happening. It only happens on 13.10. I have bumblebee installed. I used both cards to play the game and the same thing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shuhao 2611 F pulseaudio shuhao 4063 F plugin-containe /dev/snd/pcmC0D0p: shuhao 4063 F...m plugin-containe /dev/snd/timer: shuhao 4063 f plugin-containe Date: Mon Oct 7 20:39:17 2013 HibernationDevice: RESUME=UUID=0c4e9477-6a74-48cb-a0e4-37bc3251580e InstallationDate: Installed on 2013-07-08 (91 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: LENOVO 4180J4C MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash i915.modeset=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create secure directory (/run/user/1000/pulse): Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180J4C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4180J4C:pvrThinkPadT420:rvnLENOVO:rn4180J4C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180J4C dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1236653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250622] Re: linux: 3.2.0-57.87 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = Sylvain Pineau (sylvain-pineau) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250622 Title: linux: 3.2.0-57.87 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-57.87 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 20:47 UTC kernel-stable-Prepare-package-end:Thursday, 14. November 2013 21:31 UTC kernel-stable-Promote-to-proposed-start:Thursday, 14. November 2013 21:31 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 22:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 14. November 2013 23:02 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 23:02 UTC kernel-stable-Certification-testing-start:Thursday, 14. November 2013 23:02 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 23:02 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 23:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1250622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1236653]
Fixed in Mesa 9.2.3 (out today), the upcoming Mesa 10.0 release, or Mesa master. This fixes the Sandybridge-specific GPU hang where i915_error_state (aka /sys/class/drm/card0/error) lists an IPEHR of 0x79050005. If you experience a GPU hang and your IPEHR is not 0x79050005, that is a different bug. Thanks again for your patience! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1236653 Title: Graphics performance reduced after playing games for a little bit Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Saucy. I noticed that everytime I play something like Counter Strike Source, my graphics performance drops down to something like 15fps while normally it is locked at a max FPS of 40fps.. This slowdown happens and also makes my computer generally pretty slow. Thermo maximum has not been tripped (I know, and I actually underclock while playing these games). I'm not sure why this is happening. It only happens on 13.10. I have bumblebee installed. I used both cards to play the game and the same thing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shuhao 2611 F pulseaudio shuhao 4063 F plugin-containe /dev/snd/pcmC0D0p: shuhao 4063 F...m plugin-containe /dev/snd/timer: shuhao 4063 f plugin-containe Date: Mon Oct 7 20:39:17 2013 HibernationDevice: RESUME=UUID=0c4e9477-6a74-48cb-a0e4-37bc3251580e InstallationDate: Installed on 2013-07-08 (91 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: LENOVO 4180J4C MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash i915.modeset=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create secure directory (/run/user/1000/pulse): Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180J4C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4180J4C:pvrThinkPadT420:rvnLENOVO:rn4180J4C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180J4C dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1236653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1205284] Re: linux-tools naming is not scalable to multiple source packages
** Branch linked: lp:ubuntu/precise-proposed/apt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1205284 Title: linux-tools naming is not scalable to multiple source packages Status in “apt” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux-goldfish” package in Ubuntu: Fix Released Status in “linux-lowlatency” package in Ubuntu: Fix Released Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-meta” package in Ubuntu: Fix Released Status in “linux-meta-goldfish” package in Ubuntu: Fix Released Status in “linux-meta-lowlatency” package in Ubuntu: Fix Released Status in “linux-meta-ppc” package in Ubuntu: Fix Released Status in “linux-ppc” package in Ubuntu: Fix Released Status in “apt” source package in Precise: Fix Committed Status in “linux” source package in Precise: Fix Committed Status in “linux-goldfish” source package in Precise: Invalid Status in “linux-lowlatency” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-meta” source package in Precise: Invalid Status in “linux-meta-goldfish” source package in Precise: Invalid Status in “linux-meta-lowlatency” source package in Precise: Invalid Status in “linux-meta-ppc” source package in Precise: Invalid Status in “linux-ppc” source package in Precise: Invalid Status in “apt” source package in Saucy: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux-goldfish” source package in Saucy: Fix Released Status in “linux-lowlatency” source package in Saucy: Fix Released Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-meta” source package in Saucy: Fix Released Status in “linux-meta-goldfish” source package in Saucy: Fix Released Status in “linux-meta-lowlatency” source package in Saucy: Fix Released Status in “linux-meta-ppc” source package in Saucy: Fix Released Status in “linux-ppc” source package in Saucy: Fix Released Bug description: The linux tools packages are not currently scalable to multiple source package branches. This is because the packages are actually per architecture (not flavour) in both contents and naming but may differ between source packages which may be at different versions. This prevents us safely emitting linux-tools packages from branches other than master. We have a policy of insulating people from the source package from which a kernel comes. We do this via the linux-thing-flavour package naming, which is consistant regardless of overall package. It therefore makes a lot of sense to extend this to the tools package. Such that we would have the following user consumable packages as below: linux-tools-flavour -- tools to match linux-image-flavour linux-tools-abi-flavour -- tools to match linux-image-abi-flavour In order to allow linux-tools to be still be a valid install target the first of these would additionally Provides: linux-tools to allow simple selection of the appropriate flavour specific package where there is only one, or to help the user make an informed choice where there is more. The first would be the logical choice when wanting to maintain tools installed for all future version of the kernel, mirroring the kernels as installed by the linux-flavour and linux-image-flavour packages and keeping the user up to date in tools. The second would be the appropriate package to request installation when trying to target a specific kernel version and would be used by the wrapper when requesting manual intervention such as when the linux-tools-flavour is not installed. The first of these would be added to the appropriate meta package, the second would come out of the flavour specific packages in the main kernel source package. Further we would then be able to name the actual binary packages as produced by the various source packages to be source package specific. Thus we would have packages as below: linux-tools-abi -- coming out of the master branch linux-grouper-tools-abi -- coming out of the grouper branch These would be hidden from the user via the previously listed meta packages and would not be direct installation candidates. There is also an additional linux-tools-common package which represents the manual pages and the wrappers. These would be only generated and installed from the master branch and all of the other flavours would (at least initially) share this package. The actual binaries will be moved over to names similar to below: /usr/lib/srcpkg-tools-abi/binary with symlinks in as below for each flavour pointing to the above: /usr/lib/linux-tools/binary-abi-flavour
[Kernel-packages] [Bug 1236653] Re: Graphics performance reduced after playing games for a little bit
** Changed in: linux Status: In Progress = Fix Released ** Bug watch added: freedesktop.org Bugzilla #71276 https://bugs.freedesktop.org/show_bug.cgi?id=71276 ** Bug watch added: freedesktop.org Bugzilla #54226 https://bugs.freedesktop.org/show_bug.cgi?id=54226 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1236653 Title: Graphics performance reduced after playing games for a little bit Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Saucy. I noticed that everytime I play something like Counter Strike Source, my graphics performance drops down to something like 15fps while normally it is locked at a max FPS of 40fps.. This slowdown happens and also makes my computer generally pretty slow. Thermo maximum has not been tripped (I know, and I actually underclock while playing these games). I'm not sure why this is happening. It only happens on 13.10. I have bumblebee installed. I used both cards to play the game and the same thing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shuhao 2611 F pulseaudio shuhao 4063 F plugin-containe /dev/snd/pcmC0D0p: shuhao 4063 F...m plugin-containe /dev/snd/timer: shuhao 4063 f plugin-containe Date: Mon Oct 7 20:39:17 2013 HibernationDevice: RESUME=UUID=0c4e9477-6a74-48cb-a0e4-37bc3251580e InstallationDate: Installed on 2013-07-08 (91 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: LENOVO 4180J4C MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash i915.modeset=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create secure directory (/run/user/1000/pulse): Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180J4C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4180J4C:pvrThinkPadT420:rvnLENOVO:rn4180J4C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180J4C dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1236653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250622] Re: linux: 3.2.0-57.87 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250622 Title: linux: 3.2.0-57.87 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Precise: New Bug description: This bug is for tracking the 3.2.0-57.87 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 20:47 UTC kernel-stable-Prepare-package-end:Thursday, 14. November 2013 21:31 UTC kernel-stable-Promote-to-proposed-start:Thursday, 14. November 2013 21:31 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 22:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 14. November 2013 23:02 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 23:02 UTC kernel-stable-Certification-testing-start:Thursday, 14. November 2013 23:02 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 23:02 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 23:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1250622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1236653]
Sorry to re-open but I wanted to include one more detail - either a recent update fixed this for me, or a recent change I made to my BIOS settings (changing my fan speed from normal to turbo in my motherboard BIOS) has made me unable to reproduce this hang, even after long periods of scrolling complex maps in Google Maps. I can definitely raise the temperature nearly 10C by doing this, but with the fans on turbo (and this only seems to make it slightly louder) the hang does not occur. Hopefully this will help anyone else with these issues - always try to cool the processor as much as possible! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1236653 Title: Graphics performance reduced after playing games for a little bit Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: I recently upgraded to Saucy. I noticed that everytime I play something like Counter Strike Source, my graphics performance drops down to something like 15fps while normally it is locked at a max FPS of 40fps.. This slowdown happens and also makes my computer generally pretty slow. Thermo maximum has not been tripped (I know, and I actually underclock while playing these games). I'm not sure why this is happening. It only happens on 13.10. I have bumblebee installed. I used both cards to play the game and the same thing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shuhao 2611 F pulseaudio shuhao 4063 F plugin-containe /dev/snd/pcmC0D0p: shuhao 4063 F...m plugin-containe /dev/snd/timer: shuhao 4063 f plugin-containe Date: Mon Oct 7 20:39:17 2013 HibernationDevice: RESUME=UUID=0c4e9477-6a74-48cb-a0e4-37bc3251580e InstallationDate: Installed on 2013-07-08 (91 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: LENOVO 4180J4C MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash i915.modeset=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to create secure directory (/run/user/1000/pulse): Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-25 (12 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180J4C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4180J4C:pvrThinkPadT420:rvnLENOVO:rn4180J4C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180J4C dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1236653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250592] Re: linux: 2.6.32-54.116 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250592 Title: linux: 2.6.32-54.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-54.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 18:50 UTC kernel-stable-Prepare-package-end:Wednesday, 13. November 2013 02:04 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. November 2013 02:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 11:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 14. November 2013 12:02 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Certification-testing-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1250592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1226172] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
I believe it did occur in Quantal, but I am not 100% certain. These
servers had Quantal for a very shot time (~1 day), because we required
kernel features present only in Raring+, for use with Ceph/Rados.
Raring was still 3-4 months from release, but we were pulling Raring
Kernels into Quantal. These servers have been fully Raring based since
its official release.
I have loaded kernellinux-headers-3.12.0-031200-generic (trusty),
the one from the bottom, to ensure we're thorough.
Your original instructions were confusing. On the page you provided,
there is a section titled Mainline Kernel Mapping, and a single link
current which points directly to that Daily kernel. The (fool-proof)
link would be: http://kernel.ubuntu.com/~kernel-ppa/mainline
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1226172
Title:
iostat: Cannot open /proc/stat: Cannot allocate memory
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
I receive an intermittent error using iostat -k 5 : Cannot open
/proc/stat: Cannot allocate memory
This can also be simply reproduced by entering: cat /proc/stat, one
to several (~5-10) times.
strace on the cat /proc/stat method:
...exclude typical run-up...
fstat(3, {st_mode=S_IFREG|0644, st_size=1607664, ...}) = 0
mmap(NULL, 1607664, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd755b77000
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
open(/proc/stat, O_RDONLY)= -1 ENOMEM (Cannot allocate memory)
write(2, cat: , 5cat: )= 5
write(2, /proc/stat, 10/proc/stat) = 10
open(/usr/share/locale/locale.alias, O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd755d09000
read(3, # Locale name alias data base.\n#..., 4096) = 2570
read(3, , 4096) = 0
close(3)= 0
munmap(0x7fd755d09000, 4096)= 0
open(/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
...exclude typical throw-error via LC_MESSAGES/libc.mo...
/proc/meminfo detail:
# cat /proc/meminfo
MemTotal: 32947584 kB
MemFree: 302664 kB
Buffers: 154064 kB
Cached: 21284268 kB
SwapCached: 1728840 kB
Active: 12576792 kB
Inactive: 17279896 kB
Active(anon):5097984 kB
Inactive(anon): 3320844 kB
Active(file):7478808 kB
Inactive(file): 13959052 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 187617276 kB
SwapFree: 185330320 kB
Dirty: 148 kB
Writeback: 0 kB
AnonPages: 7048592 kB
Mapped: 104312 kB
Shmem: 604 kB
Slab:1947068 kB
SReclaimable:1523288 kB
SUnreclaim: 423780 kB
KernelStack:8800 kB
PageTables:38260 kB
NFS_Unstable: 0 kB
Bounce:0 kB
WritebackTmp: 0 kB
CommitLimit:204091068 kB
Committed_AS: 15333712 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 163292 kB
VmallocChunk: 34359457992 kB
HardwareCorrupted: 0 kB
AnonHugePages: 38912 kB
HugePages_Total: 0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
DirectMap4k: 333824 kB
DirectMap2M:14313472 kB
DirectMap1G:18874368 kB
This only seems to happens on specific hardware: Intel Server System P4000CP
/ S2600CP Motherboard, booted with kernel option: pci=conf1
This does NOT happen on very similar hardware: Intel Server R2312GZ /
S2600GZ Motherboard
Is there a possible memory, or kernel memory sysctl configurable I'm missing
here?
---
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Aug 23 07:12 seq
crw-rw---T 1 root audio 116, 33 Aug 23 07:12 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=98374fad-7836-4390-b311-614da0ca473c
InstallationDate: Installed on 2013-02-17 (210 days ago)
InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64
(20121017.2)
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
[Kernel-packages] [Bug 1250592] Re: linux: 2.6.32-54.116 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) = Brendan Donegan (brendan-donegan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250592 Title: linux: 2.6.32-54.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-54.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 18:50 UTC kernel-stable-Prepare-package-end:Wednesday, 13. November 2013 02:04 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. November 2013 02:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 11:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 14. November 2013 12:02 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Certification-testing-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1250592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251676] [NEW] bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1: bcmwl kernel module failed to build
Public bug reported: It Ocurrs when i was installing optimized netbook kernel 3.10.4-netbook_3.10.4_i386 (headers and image). ProblemType: Package DistroRelease: Ubuntu 13.10 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DKMSKernelVersion: 3.10.4-netbook Date: Fri Nov 15 09:56:31 2013 InstallationDate: Installed on 2013-11-14 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True PackageVersion: 6.30.223.141+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1251676 Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: New Bug description: It Ocurrs when i was installing optimized netbook kernel 3.10.4-netbook_3.10.4_i386 (headers and image). ProblemType: Package DistroRelease: Ubuntu 13.10 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DKMSKernelVersion: 3.10.4-netbook Date: Fri Nov 15 09:56:31 2013 InstallationDate: Installed on 2013-11-14 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True PackageVersion: 6.30.223.141+bdcom-0ubuntu1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1251676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251681] [NEW] mei_me resets spamming dmesg again
Public bug reported: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251681 Title: mei_me resets spamming dmesg again Status in “linux” package in Ubuntu: New Bug description: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1158258] Re: CVE-2013-1797
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium -- 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/1158258 Title: CVE-2013-1797 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: 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: Fix Released 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: 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: 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 Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: 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-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: 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-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in
[Kernel-packages] [Bug 1251681] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1251681 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251681 Title: mei_me resets spamming dmesg again Status in “linux” package in Ubuntu: Incomplete Bug description: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251441] Re: Stylus input stops working after resuming from suspend
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 stable 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.11.8-saucy/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: kernel-da-key needs-bisect regression-release ** 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/1251441 Title: Stylus input stops working after resuming from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: I'm filing this bug here as per a suggestion on Ask Ubuntu: http://askubuntu.com/questions/377047/which-package-should-i-file-a -bug-against-for-pen-input I have a Fujitsu LifeBook T900 which accepts touchscreen input via a stylus which comes with the machine. It works fine until I suspend the laptop, such as by closing the lid, then resuming, at which point it immediately stops working. A workaround is to restart the machine if this type of input is desired and the machine was previously suspended since the last time it was booted. Keyboard and touchpad (mouse) still work while the bug is active. This is a fresh install of Ubuntu 13.10; the same machine previously ran 12.04 LTS and did not experience the problem there. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chorton1695 F pulseaudio Date: Thu Nov 14 16:47:51 2013 HibernationDevice: RESUME=UUID=7daf89ba-2a9b-4dcb-b74f-94c6c6712d7c InstallationDate: Installed on 2013-10-22 (23 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: FUJITSU LIFEBOOK T900 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=3afa1e4f-0b09-4e49-b2f4-b6e805900e81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.19 dmi.board.name: FJNB204 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: CP480443-01 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd11/29/2011:svnFUJITSU:pnLIFEBOOKT900:pvr:rvnFUJITSU:rnFJNB204:rvr:cvnCP480443-01:ct10:cvr: dmi.product.name: LIFEBOOK T900 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251684] [NEW] 13.10 shutdown on Acer 3050 laptop doesn't work
Public bug reported: After doing an update to Ubuntu 13.04, the laptop wwould go thru the motions of shutting down but would NOT complete the shutdown. The drive light continues to flicker and the 2 status lights on the front of the laptop remain lit. I tried to correct this issue by installing Ubuntu 13.10 from a DVD over the existing Ubuntu 13.04. This was before I saw all the problems showing up with the release. It installed but had some options that had to be corrected. The machine still will not after getting several updates since. This machine is set up as a dual-boot with Windows Vista. The Windows side shutsdown without any issues. This shutdown problem affects the lptop and not my Zotac desktop machine. It appears to be a problem in the shutdown of laptops and not desktop machines. The only way I can shut it down or reboot the machine is to HARD Shutdown the machine and then press the POWER button to start it back up. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1251684 Title: 13.10 shutdown on Acer 3050 laptop doesn't work Status in “linux” package in Ubuntu: Incomplete Bug description: After doing an update to Ubuntu 13.04, the laptop wwould go thru the motions of shutting down but would NOT complete the shutdown. The drive light continues to flicker and the 2 status lights on the front of the laptop remain lit. I tried to correct this issue by installing Ubuntu 13.10 from a DVD over the existing Ubuntu 13.04. This was before I saw all the problems showing up with the release. It installed but had some options that had to be corrected. The machine still will not after getting several updates since. This machine is set up as a dual-boot with Windows Vista. The Windows side shutsdown without any issues. This shutdown problem affects the lptop and not my Zotac desktop machine. It appears to be a problem in the shutdown of laptops and not desktop machines. The only way I can shut it down or reboot the machine is to HARD Shutdown the machine and then press the POWER button to start it back up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250592] Re: linux: 2.6.32-54.116 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250592 Title: linux: 2.6.32-54.116 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-54.116 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 18:50 UTC kernel-stable-Prepare-package-end:Wednesday, 13. November 2013 02:04 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. November 2013 02:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 11:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 14. November 2013 12:02 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Certification-testing-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 12:02 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 12:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1250592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251684] Re: 13.10 shutdown on Acer 3050 laptop doesn't work
I was intending to rebuild the machine as just an Ubuntu machine but I won't until it can shutdown cleanly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251684 Title: 13.10 shutdown on Acer 3050 laptop doesn't work Status in “linux” package in Ubuntu: Incomplete Bug description: After doing an update to Ubuntu 13.04, the laptop wwould go thru the motions of shutting down but would NOT complete the shutdown. The drive light continues to flicker and the 2 status lights on the front of the laptop remain lit. I tried to correct this issue by installing Ubuntu 13.10 from a DVD over the existing Ubuntu 13.04. This was before I saw all the problems showing up with the release. It installed but had some options that had to be corrected. The machine still will not after getting several updates since. This machine is set up as a dual-boot with Windows Vista. The Windows side shutsdown without any issues. This shutdown problem affects the lptop and not my Zotac desktop machine. It appears to be a problem in the shutdown of laptops and not desktop machines. The only way I can shut it down or reboot the machine is to HARD Shutdown the machine and then press the POWER button to start it back up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251256] Re: Qualcomm Atheros AR9285 Wireless Network Adapter Can't Connect After Screen Locks
Can you post the newer linux-firmware version that resolves the bug? ** Tags added: kernel-da-key -- 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/1251256 Title: Qualcomm Atheros AR9285 Wireless Network Adapter Can't Connect After Screen Locks Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: Wait for the screen to lock, then log back in...voila! You will no longer be able to reconnect to any network connections until you reboot (of which I can't seem to get Ubuntu 12.04.3) to shut down. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-firmware 1.79.7 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Thu Nov 14 08:05:54 2013 Dependencies: InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1251256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251684] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1251684 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251684 Title: 13.10 shutdown on Acer 3050 laptop doesn't work Status in “linux” package in Ubuntu: Incomplete Bug description: After doing an update to Ubuntu 13.04, the laptop wwould go thru the motions of shutting down but would NOT complete the shutdown. The drive light continues to flicker and the 2 status lights on the front of the laptop remain lit. I tried to correct this issue by installing Ubuntu 13.10 from a DVD over the existing Ubuntu 13.04. This was before I saw all the problems showing up with the release. It installed but had some options that had to be corrected. The machine still will not after getting several updates since. This machine is set up as a dual-boot with Windows Vista. The Windows side shutsdown without any issues. This shutdown problem affects the lptop and not my Zotac desktop machine. It appears to be a problem in the shutdown of laptops and not desktop machines. The only way I can shut it down or reboot the machine is to HARD Shutdown the machine and then press the POWER button to start it back up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251500] Re: package linux-image-3.11.0-13-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
You may need to run the following: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package. If that does not resolve your issue, please mark the bug as Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251500 Title: package linux-image-3.11.0-13-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in “linux” package in Ubuntu: Incomplete Bug description: tried to update all software after a fresh install without automatically downloading updates. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tommy 2049 F pulseaudio /dev/snd/controlC0: tommy 2049 F pulseaudio CurrentDmesg: [ 10.546300] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Thu Nov 14 22:05:56 2013 DuplicateSignature: package:linux-image-3.11.0-13-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=5016509f-a2f4-4ec8-8cca-d88b578d9615 InstallationDate: Installed on 2013-11-15 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SX58 MarkForUpload: True ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-12-generic root=UUID=4bd42f7a-715a-45f9-9854-a8b287c02d13 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: grub-pc 2.00-19ubuntu2.1 RfKill: SourcePackage: linux Title: package linux-image-3.11.0-13-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SX58 dmi.board.vendor: Shuttle Inc. dmi.board.version: V10 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Intel dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd04/02/2012:svnShuttleInc.:pnSX58:pvrV10:rvnShuttleInc.:rnSX58:rvrV10:cvnIntel:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SX58 dmi.product.version: V10 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251681] Re: mei_me resets spamming dmesg again
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 stable 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.11.8-saucy/ ** 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/1251681 Title: mei_me resets spamming dmesg again Status in “linux” package in Ubuntu: Incomplete Bug description: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251684] Re: 13.10 shutdown on Acer 3050 laptop doesn't work
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 stable 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.11.8-saucy/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: regression-release saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251684 Title: 13.10 shutdown on Acer 3050 laptop doesn't work Status in “linux” package in Ubuntu: Incomplete Bug description: After doing an update to Ubuntu 13.04, the laptop wwould go thru the motions of shutting down but would NOT complete the shutdown. The drive light continues to flicker and the 2 status lights on the front of the laptop remain lit. I tried to correct this issue by installing Ubuntu 13.10 from a DVD over the existing Ubuntu 13.04. This was before I saw all the problems showing up with the release. It installed but had some options that had to be corrected. The machine still will not after getting several updates since. This machine is set up as a dual-boot with Windows Vista. The Windows side shutsdown without any issues. This shutdown problem affects the lptop and not my Zotac desktop machine. It appears to be a problem in the shutdown of laptops and not desktop machines. The only way I can shut it down or reboot the machine is to HARD Shutdown the machine and then press the POWER button to start it back up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251433] Re: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker
git://kernel.ubuntu.com/ppisati/ubuntu-precise.git ti-omap4 ** Summary changed: - linux-ti-omap4: version to be filled -proposed tracker + linux-ti-omap4: 3.2.0-1441.60 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1251433 Title: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 14. November 2013 21:24 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Thursday, 14. November 2013 21:24 UTC kernel-stable-master-bug:1250622 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1251433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade
Trying bisecting didn't work for me, as (according to the wiki's translation of the output) it spans non-linear tags. My attempt to build from a 3.10 mainline kernel produced an image that suffered from the same issue, but that didn't provide a linux-image-extras package which seems to be necessary for the brightness controls to work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade Status in “linux” package in Ubuntu: Incomplete Bug description: On raring (and precise) the display brightness keys (fn+f4 and fn+f5) on my Dell Inspiron 14z turned the brightness up and down. After a saucy upgrade this no longer happens (I don't see the popup brightness bubble either). The other, similar keys (volume adjustment, etc) still work fine. Changing the values in /sys/class/backlight/intel_backlight/brightness works (temporarily - it gets reset after the screen lock kicks in) I tried following the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting but this appears to be out of date (it references /usr/share/doc/udev/README.keymap.txt which does not exist) Ubuntu kernel version bisect revealed: First bad Ubuntu kernel: 3.11.0-0.2 last good Ubuntu kernel: 3.10.0-6.17 The results of a commit bisect are pending. --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2646 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2011-11-18 (675 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Dell System Inspiron N411Z MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=8bcbab07-7d4f-4c89-b6db-54aeed6ad1c4 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 RelatedPackageVersions: linux-restricted-modules-3.11.0-8-generic N/A linux-backports-modules-3.11.0-8-generic N/A linux-firmware1.114 Tags: saucy Uname: Linux 3.11.0-8-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-21 (2 days ago) UserGroups: adm admin cdrom davfs2 dialout lpadmin plugdev sambashare dmi.bios.date: 09/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0P01VP dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0P01VP:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N411Z dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251433] Re: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1251433 Title: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 14. November 2013 21:24 UTC kernel-stable-master-bug:1250622 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Friday, 15. November 2013 17:05 UTC kernel-stable-Certification-testing-end:Friday, 15. November 2013 17:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1251433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251433] Re: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker
** Description changed: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 14. November 2013 21:24 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Thursday, 14. November 2013 21:24 UTC kernel-stable-master-bug:1250622 + kernel-stable-phase:ReadyToBePackaged + kernel-stable-phase-changed:Friday, 15. November 2013 17:05 UTC + kernel-stable-Certification-testing-end:Friday, 15. November 2013 17:04 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1251433 Title: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 14. November 2013 21:24 UTC kernel-stable-master-bug:1250622 kernel-stable-phase:ReadyToBePackaged kernel-stable-phase-changed:Friday, 15. November 2013 17:05 UTC kernel-stable-Certification-testing-end:Friday, 15. November 2013 17:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1251433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1226172] Re: iostat: Cannot open /proc/stat: Cannot allocate memory
Thanks for the feedback, Ron. I updated that wiki page.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1226172
Title:
iostat: Cannot open /proc/stat: Cannot allocate memory
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
I receive an intermittent error using iostat -k 5 : Cannot open
/proc/stat: Cannot allocate memory
This can also be simply reproduced by entering: cat /proc/stat, one
to several (~5-10) times.
strace on the cat /proc/stat method:
...exclude typical run-up...
fstat(3, {st_mode=S_IFREG|0644, st_size=1607664, ...}) = 0
mmap(NULL, 1607664, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd755b77000
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
open(/proc/stat, O_RDONLY)= -1 ENOMEM (Cannot allocate memory)
write(2, cat: , 5cat: )= 5
write(2, /proc/stat, 10/proc/stat) = 10
open(/usr/share/locale/locale.alias, O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd755d09000
read(3, # Locale name alias data base.\n#..., 4096) = 2570
read(3, , 4096) = 0
close(3)= 0
munmap(0x7fd755d09000, 4096)= 0
open(/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo, O_RDONLY) = -1
ENOENT (No such file or directory)
...exclude typical throw-error via LC_MESSAGES/libc.mo...
/proc/meminfo detail:
# cat /proc/meminfo
MemTotal: 32947584 kB
MemFree: 302664 kB
Buffers: 154064 kB
Cached: 21284268 kB
SwapCached: 1728840 kB
Active: 12576792 kB
Inactive: 17279896 kB
Active(anon):5097984 kB
Inactive(anon): 3320844 kB
Active(file):7478808 kB
Inactive(file): 13959052 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 187617276 kB
SwapFree: 185330320 kB
Dirty: 148 kB
Writeback: 0 kB
AnonPages: 7048592 kB
Mapped: 104312 kB
Shmem: 604 kB
Slab:1947068 kB
SReclaimable:1523288 kB
SUnreclaim: 423780 kB
KernelStack:8800 kB
PageTables:38260 kB
NFS_Unstable: 0 kB
Bounce:0 kB
WritebackTmp: 0 kB
CommitLimit:204091068 kB
Committed_AS: 15333712 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 163292 kB
VmallocChunk: 34359457992 kB
HardwareCorrupted: 0 kB
AnonHugePages: 38912 kB
HugePages_Total: 0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
DirectMap4k: 333824 kB
DirectMap2M:14313472 kB
DirectMap1G:18874368 kB
This only seems to happens on specific hardware: Intel Server System P4000CP
/ S2600CP Motherboard, booted with kernel option: pci=conf1
This does NOT happen on very similar hardware: Intel Server R2312GZ /
S2600GZ Motherboard
Is there a possible memory, or kernel memory sysctl configurable I'm missing
here?
---
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Aug 23 07:12 seq
crw-rw---T 1 root audio 116, 33 Aug 23 07:12 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=98374fad-7836-4390-b311-614da0ca473c
InstallationDate: Installed on 2013-02-17 (210 days ago)
InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64
(20121017.2)
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 046b:ff10 American Megatrends, Inc. Virtual Keyboard
and Mouse
MachineType: Intel Corporation S2600CP ..
MarkForUpload: True
Package: linux 3.8.0.30.48
PackageArchitecture: amd64
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic
root=/dev/mapper/h01vg-root ro pci=conf1 intel_iommu=on
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
RelatedPackageVersions:
[Kernel-packages] [Bug 1242938] Re: 13.10: Kernel panic - not syncing (on system start)
I built the next test kernel, up to the following commit: f084dbb939070281be7c882db63a4a428c51fcf4 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1242938 Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results. 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/1242938 Title: 13.10: Kernel panic - not syncing (on system start) Status in “linux” package in Ubuntu: Confirmed Bug description: If i start ubuntu 13.10 i always get the error (see attached picture). This happens if i start via live-usb stick and after normal update from 13.04 to 13.10 within ubuntu. The same usb-live stick works on another computer without any errors. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 CrashDB: ubuntu Date: Tue Oct 22 00:31:43 2013 InstallationDate: Installed on 2013-08-05 (77 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to saucy on 2013-10-20 (0 days ago) VarLogDistupgradeTermlog: --- ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1845 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=411d36d6-4f07-4f5b-a060-18096ace08de InstallationDate: Installed on 2013-08-05 (79 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release i386 (20130424) MachineType: Medion P8610 MarkForUpload: True Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-31-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.8.0-31-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/28/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: M1.04 dmi.board.name: P8610 dmi.board.vendor: Medion dmi.board.version: REFERENCE dmi.chassis.type: 10 dmi.chassis.vendor: Medion dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrM1.04:bd11/28/2008:svnMedion:pnP8610:pvrREFERENCE:rvnMedion:rnP8610:rvrREFERENCE:cvnMedion:ct10:cvr: dmi.product.name: P8610 dmi.product.version: REFERENCE dmi.sys.vendor: Medion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1107150] Re: B75 Chipset I/O Problems
I built the next test kernel, up to the following commit: 010e646ba2fdfc558048a97da746381c35836280 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1107150 Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1107150 Title: B75 Chipset I/O Problems Status in “linux” package in Ubuntu: Confirmed Bug description: I built a new system and installed Ubuntu 12.10. The system has the following specifications: Samsung 840 Pro 128 GB Gigabyte P75-D3 Intel i7 3770 32 GB Ram Western Digital 1 TB Black (mounted as /home) Western Digital 3 TB Green (mounted as /media/data_drive) The initial Ubuntu 12.10 install took almost 6 hours as transfer rates were very slow. After reboot everything appeared very fast. However when I did an apt-get update the download took 20 seconds and the processing of lists took 19 minutes. I had 12.10 installed on another computer which was working great (older Althon system) so I installed the drive and tested the new machine. It suffered the same performance problems. I installed Windows 7 and performed speeds tests, it reported great results. I installed 12.04 onto the 1 TB drive and it did not suffer the same performance problems. Everything ran great. I then upgraded 12.10 to 13.04 (January 27, 2013) and it too suffered from the performance issue. It appears that a change between 12.04 to 12.10 impacts AHCI based systems specifically running the Intel B75 chipset. I am not certain but I think that either the motherboard is misrepresenting something (that 12.04 ignores but it impacts 12.10) or the kernel is not detecting the system correctly. I created a couple of pastebins with data collected: 12.10 Install: http://pastebin.ubuntu.com/1561660/ 12.04 Live Disk (was checked against installed version and data is mostly the same): http://paste.ubuntu.com/1565140/ I have a thread on the ubuntu forums that may provide additional details: http://ubuntuforums.org/showthread.php?t=2104709 I also started an e-mail thread to the ubuntu-users mailing list: http://ubuntu.5.n6.nabble.com/Seeking-Help-td5010422.html I have done a lot of troubleshooting and I feel that the problem must either be the kernel or the bios misrepresenting information. In either case I am stuck without any idea of where to go next with the debuging and diagnoses path. If any additional information needs to be collected, please let me know and I will work to assist. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bakers 1729 F pulseaudio /dev/snd/controlC0: bakers 1729 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf711 irq 45' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,1458a002,00100302' Controls : 39 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583553,00100100' Controls : 18 Simple ctrls : 3 DistroRelease: Ubuntu 12.04 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic-pae root=UUID=4f30252c-fa56-4d53-be78-117cddab55f4 ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35 RelatedPackageVersions: linux-restricted-modules-3.2.0-36-generic-pae N/A linux-backports-modules-3.2.0-36-generic-pae N/A linux-firmware1.79.1 RfKill: StagingDrivers: mei Tags: precise running-unity staging Uname: Linux 3.2.0-36-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P75-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be
[Kernel-packages] [Bug 1249719] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0000000000000030; IP: [ffffffff811c07c7] touch_atime+0x17/0x140
I started a kernel bisect between v3.11.5 and v3.11.6. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: b340404549c872099aec7554439a1821c0708878 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1249719 Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results. 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/1249719 Title: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 0030; IP: [811c07c7] touch_atime+0x17/0x140 Status in “linux” package in Ubuntu: Confirmed Bug description: Since 3.11.0-13-generic, I've been encountering the following kernel oops. I can trigger it quite reliably by watching full-screen videos on YouTube using google-chrome (Version 31.0.1650.48) for roughly 10 minutes. Once the oops happens, the system remains up, but certain programs (like top) start hanging and a reboot is needed to restore full functionality. I've tried using 3.12.0-999-generic (3.12.0-999.201311080433), but get the same problem there. I don't get the oops when booting into 3.11.0-12-generic, so I suspect the problem was introduced in 3.11.0-13-generic (especially since I see there were some changes made related to the shmat system call). Attached is the oops from dmesg. The EIP location and stack-trace are identical for all the oops I've seen so far. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rick 1421 F pulseaudio /dev/snd/controlC1: rick 1421 F pulseaudio /dev/snd/controlC0: rick 1421 F pulseaudio Date: Sat Nov 9 23:24:33 2013 HibernationDevice: RESUME=UUID=0ad92a6e-2969-424f-b469-faaa9f2ec20f InstallationDate: Installed on 2012-10-19 (387 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cf7d6665-f4a9-4be8-a12d-c72a985ea5eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-19 (22 days ago) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1249880] Re: kernel 3.11.0-13 freezes on qemu+kvm VM start
I built the next test kernel, up to the following commit: a1c008db75b819e29a62ff3fbeffe493bf7ece93 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1249880 Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results. 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/1249880 Title: kernel 3.11.0-13 freezes on qemu+kvm VM start Status in “linux” package in Ubuntu: Confirmed Bug description: I updated my Ubuntu 13.10 workstation with newest kernel 3.11.0-13 and every time I start my Windows7 VM made of qemu+kvm the workstation freezes. I reverted to 3.11.0-12 for the time being. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zm5s-trnc 2084 F pulseaudio Date: Mon Nov 11 11:07:01 2013 HibernationDevice: RESUME=UUID=cff75e59-746a-4d33-b21f-fb68d7dda4cf MachineType: Dell Inc. OptiPlex 390 MarkForUpload: True ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=f845956f-07fb-4b93-b7ae-32e4039cf283 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-17 (24 days ago) dmi.bios.date: 10/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0M5DCD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/26/2011:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 390 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251054] Re: networking didn't return from suspend
Seth Forshee, good news, bluntly restarting NetworkManager allowed me to continue without the reboot: $ sudo service network-manager restart [sudo] password for sarnold: network-manager stop/waiting network-manager start/running, process 6165 I didn't see anything in my logs that suggests what the error is. Is 'linux' still the correct package? Or since restarting NetworkManager 'fixes' the problem, should this be re-assigned towards nm? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251054 Title: networking didn't return from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: Wireless networking did not work when I resumed from suspend. Using the indicator/applet to Enable Networking didn't associate my wireless with the AP. Plugging in an Ethernet cable did not bring back networking. The hardware rfkill switch did not bring back networking. A reboot allowed me to associate as I expected. Thanks ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2966 F pulseaudio Date: Wed Nov 13 15:03:20 2013 HibernationDevice: RESUME=UUID=81b2976f-2830-4449-9dae-e1d44a43fa78 InstallationDate: Installed on 2012-10-18 (391 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: LENOVO 2359CTO MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-06 (7 days ago) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET62WW (2.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO 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:bvrG4ET62WW(2.04):bd09/13/2012:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1212977] Re: saucy/trusty CD images are unbootable, stuck in BusyBox shell
** Attachment added: 20131115_130257.jpg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+attachment/3909619/+files/20131115_130257.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212977 Title: saucy/trusty CD images are unbootable, stuck in BusyBox shell Status in “linux” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Confirmed Status in “casper” source package in Saucy: Invalid Status in “linux” source package in Saucy: Confirmed Status in “udev” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Status in “udev” source package in Trusty: Confirmed Bug description: saucy daily-live images are unbootable on Dell Optiplex 990 and other hardware combinations. I just get a BusyBox shell. All images up to and including raring however work fine. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2083 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=9e3dac8a-8fa4-4da5-b4d2-52b2ee5fd022 InstallationDate: Installed on 2013-06-03 (76 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 990 MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=416f5f80-6d98-4208-a3f5-ef272b12e5c6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 RelatedPackageVersions: linux-restricted-modules-3.8.0-25-generic N/A linux-backports-modules-3.8.0-25-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/10/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0D6H9T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0D6H9T:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251054] Re: networking didn't return from suspend
From what I see in the logs there's not even an attempt to establish a connection after resume, so I think the problem is likely with network- manager. Reassigning. ** Package changed: linux (Ubuntu) = network-manager (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251054 Title: networking didn't return from suspend Status in “network-manager” package in Ubuntu: Confirmed Bug description: Wireless networking did not work when I resumed from suspend. Using the indicator/applet to Enable Networking didn't associate my wireless with the AP. Plugging in an Ethernet cable did not bring back networking. The hardware rfkill switch did not bring back networking. A reboot allowed me to associate as I expected. Thanks ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2966 F pulseaudio Date: Wed Nov 13 15:03:20 2013 HibernationDevice: RESUME=UUID=81b2976f-2830-4449-9dae-e1d44a43fa78 InstallationDate: Installed on 2012-10-18 (391 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: LENOVO 2359CTO MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-06 (7 days ago) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET62WW (2.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO 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:bvrG4ET62WW(2.04):bd09/13/2012:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1251054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1212977] Re: saucy/trusty CD images are unbootable, stuck in BusyBox shell
I think I may have been able to reproduce this today with Trusty. The system dropped to the busybox shell. It looked like there was a timeout waiting to find the root filesystem by uuid. I took a digital picture and will attach to the bug. Daniel, can you also take a digital picture of your system when it drops to the busybox shell? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212977 Title: saucy/trusty CD images are unbootable, stuck in BusyBox shell Status in “linux” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Confirmed Status in “casper” source package in Saucy: Invalid Status in “linux” source package in Saucy: Confirmed Status in “udev” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Status in “udev” source package in Trusty: Confirmed Bug description: saucy daily-live images are unbootable on Dell Optiplex 990 and other hardware combinations. I just get a BusyBox shell. All images up to and including raring however work fine. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2083 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=9e3dac8a-8fa4-4da5-b4d2-52b2ee5fd022 InstallationDate: Installed on 2013-06-03 (76 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 990 MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=416f5f80-6d98-4208-a3f5-ef272b12e5c6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 RelatedPackageVersions: linux-restricted-modules-3.8.0-25-generic N/A linux-backports-modules-3.8.0-25-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/10/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0D6H9T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0D6H9T:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1188355] Re: CVE-2013-2147
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low -- 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/1188355 Title: CVE-2013-2147 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: 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: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: 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: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: 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-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: 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-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in
[Kernel-packages] [Bug 1188351] Re: CVE-2013-2140
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium -- 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/1188351 Title: CVE-2013-2140 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: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-backport-oneiric” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-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: 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: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: 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-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: 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-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status
[Kernel-packages] [Bug 1198296] Re: CVE-2013-2237
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low -- 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/1198296 Title: CVE-2013-2237 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-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: Fix Committed 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: Invalid Status in “linux-lts-backport-natty” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Invalid Status in “linux-lts-backport-natty” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Invalid Status in “linux-lts-backport-natty” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: 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-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Committed Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Invalid Status
[Kernel-packages] [Bug 1220185] Re: CVE-2013-2888
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220185 Title: CVE-2013-2888 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix 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: 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring:
[Kernel-packages] [Bug 1220190] Re: CVE-2013-2889
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220190 Title: CVE-2013-2889 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix 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: 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package
[Kernel-packages] [Bug 1163720] Re: Brightness control broken on XPS13 and 3.8.0-16, 3.8.0-22 and 3.11.0-12
I have prepared a test kernel for saucy and raring that may help Dell XPS13 systems which experience black screen on boot and non-functional backlight controls. (In particular, this case has been reported when UEFI BIOS is enabled on XPS13's). This test kernel is _only_ relevant for XPS13's. See http://zinc.canonical.com/~kamal/xps13-pch-bootparam/ and follow the instructions in the README. (IMPORTANT: In addition to installing the test kernel, you must enable the fix with a boot parameter, as the README explains). Please provide feedback here regarding whether the test kernel and boot parameter helps you XPS13 backlight. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1163720 Title: Brightness control broken on XPS13 and 3.8.0-16, 3.8.0-22 and 3.11.0-12 Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Raring: In Progress Bug description: Since 3.8.0-16, the brightness control doesn’t work anymore. The popup is displayed, so the shortcut keys do work correctly, but it has no effect on the actual brightness of the screen. Switching back to 3.8.0-15 solves the issue. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-16-generic 3.8.0-16.26 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: coucouf1837 F pulseaudio Date: Wed Apr 3 08:29:58 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 HibernationDevice: RESUME=UUID=e49e9eae-f16f-45bb-ad2c-b6da5c0c6f6d InstallationDate: Installed on 2013-03-23 (10 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic root=UUID=3f6858e1-d8f5-44c4-b8e9-5ab8b9639ba7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-16-generic N/A linux-backports-modules-3.8.0-16-generic N/A linux-firmware1.104 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-02 (0 days ago) dmi.bios.date: 01/22/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1163720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1212977] Re: saucy/trusty CD images are unbootable, stuck in BusyBox shell
If you are seeing the same message as me, can you try using the rootdelay boot option? From the GRUB prompt select e. Once there you can add the line rootdelay=90 to the end of the line. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1212977 Title: saucy/trusty CD images are unbootable, stuck in BusyBox shell Status in “linux” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Confirmed Status in “casper” source package in Saucy: Invalid Status in “linux” source package in Saucy: Confirmed Status in “udev” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Status in “udev” source package in Trusty: Confirmed Bug description: saucy daily-live images are unbootable on Dell Optiplex 990 and other hardware combinations. I just get a BusyBox shell. All images up to and including raring however work fine. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2083 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=9e3dac8a-8fa4-4da5-b4d2-52b2ee5fd022 InstallationDate: Installed on 2013-06-03 (76 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 990 MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=416f5f80-6d98-4208-a3f5-ef272b12e5c6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 RelatedPackageVersions: linux-restricted-modules-3.8.0-25-generic N/A linux-backports-modules-3.8.0-25-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/10/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0D6H9T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0D6H9T:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
I built the next test kernel, up to the following commit: 44b7400e6724f9a238f62bbeffd462a449d9a518 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1245938 Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results. 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/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1220196] Re: CVE-2013-2892
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220196 Title: CVE-2013-2892 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix 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: 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status
[Kernel-packages] [Bug 1220200] Re: CVE-2013-2895
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220200 Title: CVE-2013-2895 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New 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: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring:
[Kernel-packages] [Bug 1220198] Re: CVE-2013-2893
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ec2 (Ubuntu Lucid) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Lucid) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220198 Title: CVE-2013-2893 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix 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: 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix
[Kernel-packages] [Bug 1251433] Re: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker
All builds are complete, packages in this bug can be copied to -proposed. ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Description changed: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 14. November 2013 21:24 UTC kernel-stable-master-bug:1250622 - kernel-stable-phase:ReadyToBePackaged - kernel-stable-phase-changed:Friday, 15. November 2013 17:05 UTC kernel-stable-Certification-testing-end:Friday, 15. November 2013 17:04 UTC + kernel-stable-phase:CopyToProposed + kernel-stable-Prepare-package-end:Friday, 15. November 2013 21:04 UTC + kernel-stable-Promote-to-proposed-start:Friday, 15. November 2013 21:04 UTC + kernel-stable-phase-changed:Friday, 15. November 2013 21:04 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1251433 Title: linux-ti-omap4: 3.2.0-1441.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid 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 promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux-ti-omap4” source package in Precise: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 14. November 2013 21:24 UTC kernel-stable-master-bug:1250622 kernel-stable-Certification-testing-end:Friday, 15. November 2013 17:04 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Friday, 15. November 2013 21:04 UTC kernel-stable-Promote-to-proposed-start:Friday, 15. November 2013 21:04 UTC kernel-stable-phase-changed:Friday, 15. November 2013 21:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1251433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1247967] Re: nvidia optimus chipset disabled when running on battery, even in discrete mode
Any suggestion on the next steps? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247967 Title: nvidia optimus chipset disabled when running on battery, even in discrete mode Status in “linux” package in Ubuntu: Confirmed Bug description: It appears that under 3.11.0-13, the Nvidia Optimus GPU is disabled when running on battery even if the chipset is set to discrete mode in the BIOS. When running without AC power under the 3.11 kernel, lspci -v gives the following: http://paste.ubuntu.com/6360607/ With AC power under 3.11, the same command gives: http://paste.ubuntu.com/6360613/ If the system is booted into the 3.11 kernel with AC power connected, it can be removed and the GPU continues to function normally. I have not tested suspend and resume under the 3.11 kernel (with or without AC power). This same configuration worked properly under Raring (13.04). Booting with the 3.8 kernel and the same nvidia module version used in the above 3.11 kernel tests results in the previously experienced (correct, working) behavior. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Nov 4 12:31:48 2013 HibernationDevice: RESUME=UUID=1fbfa69c-fb52-4aee-ad35-9c523aa14974 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) MachineType: LENOVO 2436CTO MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=/dev/mapper/ssd-root ro vga=792 splash nox2apic crashkernel=384M-2G:64M,2G-:128M quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-32-generic N/A linux-backports-modules-3.8.0-32-generic N/A linux-firmware1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) dmi.bios.date: 08/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO 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:bvrG5ET94WW(2.54):bd08/12/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2436CTO dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1220202] Re: CVE-2013-2896
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220202 Title: CVE-2013-2896 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New 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: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in
[Kernel-packages] [Bug 1220205] Re: CVE-2013-2897
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220205 Title: CVE-2013-2897 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal”
[Kernel-packages] [Bug 1220209] Re: CVE-2013-2899
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Low ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Low ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1220209 Title: CVE-2013-2899 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New 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: Fix Released Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in
[Kernel-packages] [Bug 1233753] Re: [HP Envy 15t-1100] saucy images boot to black screen
hmm, the fedora 20 beta boots to X ok. going to retry booting the saucy live image, and see how much of what i'm seeing running local kernels is due to fglrx not compiling for 3.10 and above -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233753 Title: [HP Envy 15t-1100] saucy images boot to black screen Status in “linux” package in Ubuntu: Confirmed Bug description: Downloaded latest saucy images and boots to nothing but a black screen. Get the same behavior with 3.11 mainline kernel package as per bug #1167586 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-31-generic 3.8.0-31.46 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3518 F pulseaudio /dev/snd/controlC0: jbarnett 3518 F pulseaudio Date: Tue Oct 1 09:31:14 2013 HibernationDevice: RESUME=UUID=6a792c43-ea80-4425-961e-ccde894552ed InstallationDate: Installed on 2010-04-19 (1261 days ago) InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) MachineType: Hewlett-Packard HP ENVY 15 Notebook PC MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=639dc488-e095-42a4-8c1f-ffb1a9299e1c ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-26 (157 days ago) dmi.bios.date: 10/12/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.2B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1522 dmi.board.vendor: Hewlett-Packard dmi.board.version: 36.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.2B:bd10/12/2010:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr048F1124192000153:rvnHewlett-Packard:rn1522:rvr36.35:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP ENVY 15 Notebook PC dmi.product.version: 048F1124192000153 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1241769] Re: CVE-2013-4299
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Saucy) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux (Ubuntu Raring) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: New = Fix Committed ** Changed in: linux-lts-raring (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/1241769 Title: CVE-2013-4299 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Fix Committed Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in
[Kernel-packages] [Bug 1250321] Re: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX
Ubuntu 14.04 already has the latest mainline kernel, and Ubuntu 13.04 works perfectly fine with every kernel from 3.8 to 3.12. -- 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/1250321 Title: Ubuntu 13.10 + 14.04 Catastrophic Random Kernel Crashes on Boot with ASUS Sabertooth 990FX Status in “linux-firmware” package in Ubuntu: Confirmed Bug description: System Specs: ASUS Sabertooth 990FX (with the latest BIOS) AMD FX-8120 AMD Radeon HD 7950 240GB Seagate SSD (20GiB / partition) 2TB WD HDD (/home) I have installed Ubuntu 14.04 three times and each met the same fate. The first time you boot into the system after installing it, it works fine. However, after you install your usual programs like Steam, Skype, smplayer, etc. and reboot the system will fail on such a grand catastrophic scale that you can't even boot into recovery mode since that will begin spamming error messages quickly as well. It isn't related to the kernel because I used the same kernel in Ubuntu 13.04. I also had the same problems with Ubuntu 13.10 (I'm not sure if that still applies but I will soon find out). Meanwhile, Ubuntu 13.04 with kernel 3.12 works perfectly. --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Dependencies: DistroRelease: Ubuntu 13.10 LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True Package: linux-firmware 1.116 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1229981] Re: CVE-2013-4345
** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1229981 Title: CVE-2013-4345 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: New Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source
[Kernel-packages] [Bug 1229975] Re: CVE-2013-4343
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium -- 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/1229975 Title: CVE-2013-4343 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix
[Kernel-packages] [Bug 1232691] Re: Automatic suspend / resume behaviour is poor
This behaviour no longer occurs in 13.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232691 Title: Automatic suspend / resume behaviour is poor Status in “linux” package in Ubuntu: Incomplete Bug description: Automatic suspend does not show the suspend message when watching video, for example iPlayer, in full screen mode. This prevents the user from choosing not to suspend and so the suspend occurs automatically. This is extremely annoying when watching a video or TV programme as the user has to go though the resume procedure. The resume procedure itself is rather strange as : 1. after entering the password the screen goes black for a moment 2. the suspend message is not removed automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248700] Re: CVE-2013-4348
** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium -- 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/1248700 Title: CVE-2013-4348 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New 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: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy:
[Kernel-packages] [Bug 1226497] Re: CVE-2013-4350
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-armadaxp (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: linux-lts-saucy (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-saucy (Ubuntu Raring) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (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/1226497 Title: CVE-2013-4350 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: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New 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: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Committed Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package
[Kernel-packages] [Bug 1251681] Re: mei_me resets spamming dmesg again
apport information ** Tags added: apport-collected ** Description changed: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: christian 2000 F pulseaudio + /dev/snd/pcmC0D0p: christian 2000 F...m pulseaudio + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=7d0cbf28-88df-4f70-813b-93288de2cbe1 + InstallationDate: Installed on 2013-03-02 (258 days ago) + InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) + MachineType: LENOVO 8895WFL + MarkForUpload: True + Package: linux 3.11.0.13.14 + PackageArchitecture: amd64 + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=d1e5c18d-297c-4972-b48d-d2cdd6428e19 ro quiet splash + ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 + RelatedPackageVersions: + linux-restricted-modules-3.11.0-13-generic N/A + linux-backports-modules-3.11.0-13-generic N/A + linux-firmware 1.116 + Tags: saucy + Uname: Linux 3.11.0-13-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-09-09 (67 days ago) + UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo vboxusers video + dmi.bios.date: 04/08/2010 + dmi.bios.vendor: LENOVO + dmi.bios.version: 7LETC7WW (2.27 ) + dmi.board.name: 8895WFL + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn8895WFL:pvrThinkPadT61:rvnLENOVO:rn8895WFL:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 8895WFL + dmi.product.version: ThinkPad T61 + dmi.sys.vendor: LENOVO ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1251681/+attachment/3910024/+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/1251681 Title: mei_me resets spamming dmesg again Status in “linux” package in Ubuntu: Confirmed Bug description: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 2000 F pulseaudio /dev/snd/pcmC0D0p: christian 2000 F...m pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=7d0cbf28-88df-4f70-813b-93288de2cbe1 InstallationDate: Installed on 2013-03-02 (258 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MachineType: LENOVO 8895WFL MarkForUpload: True Package: linux 3.11.0.13.14 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=d1e5c18d-297c-4972-b48d-d2cdd6428e19 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-09 (67 days ago) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo vboxusers video dmi.bios.date: 04/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC7WW (2.27 ) dmi.board.name: 8895WFL dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias:
[Kernel-packages] [Bug 1251681] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1251681/+attachment/3910025/+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/1251681 Title: mei_me resets spamming dmesg again Status in “linux” package in Ubuntu: Confirmed Bug description: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 2000 F pulseaudio /dev/snd/pcmC0D0p: christian 2000 F...m pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=7d0cbf28-88df-4f70-813b-93288de2cbe1 InstallationDate: Installed on 2013-03-02 (258 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MachineType: LENOVO 8895WFL MarkForUpload: True Package: linux 3.11.0.13.14 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=d1e5c18d-297c-4972-b48d-d2cdd6428e19 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-09 (67 days ago) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo vboxusers video dmi.bios.date: 04/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC7WW (2.27 ) dmi.board.name: 8895WFL dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn8895WFL:pvrThinkPadT61:rvnLENOVO:rn8895WFL:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 8895WFL dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1251681] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1251681/+attachment/3910028/+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/1251681 Title: mei_me resets spamming dmesg again Status in “linux” package in Ubuntu: Confirmed Bug description: I'm getting this message every 5 seconds [ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout. [ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155 it should be fixed in 3.10.0-2.10 But it seems happening again $ uname -a Linux t61-ubuntu 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 2000 F pulseaudio /dev/snd/pcmC0D0p: christian 2000 F...m pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=7d0cbf28-88df-4f70-813b-93288de2cbe1 InstallationDate: Installed on 2013-03-02 (258 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MachineType: LENOVO 8895WFL MarkForUpload: True Package: linux 3.11.0.13.14 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=d1e5c18d-297c-4972-b48d-d2cdd6428e19 ro quiet splash ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-09-09 (67 days ago) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo vboxusers video dmi.bios.date: 04/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC7WW (2.27 ) dmi.board.name: 8895WFL dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn8895WFL:pvrThinkPadT61:rvnLENOVO:rn8895WFL:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 8895WFL dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
