[Kernel-packages] [Bug 657922] Re: No audio in Ubuntu guest on OS X host using CoreAudio and version 3.2.x

2013-12-06 Thread Bug Watch Updater
** Changed in: virtualbox
   Status: New = Unknown

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/657922

Title:
  No audio in Ubuntu guest on OS X host using CoreAudio and version
  3.2.x

Status in Virtualbox:
  Unknown
Status in “linux” package in Ubuntu:
  Incomplete
Status in “virtualbox-ose” package in Ubuntu:
  New

Bug description:
  Binary package hint: virtualbox-ose

  Since the rewrite of the CoreAudio driver for version 3.2.0, I have no
  sound in my Ubuntu guests (10.04, 10.10 amd64 or i386) on Mac OS X
  host (10.6.4). When the vm is running, the Audio section of the vm
  settings in virtualbox is greyed-out. This is the case whether using
  ICH AC97 or Soundblaster. The most recent kernel for which I have
  audio is 2.6.35-19, and I notice that a number of patches were
  reverted post -19.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: virtualbox-ose-guest-utils 3.2.8-dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-22.33-virtual 2.6.35.4
  Uname: Linux 2.6.35-22-virtual x86_64
  Architecture: amd64
  Date: Sun Oct 10 17:06:16 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.utf8
  SourcePackage: virtualbox-ose

To manage notifications about this bug go to:
https://bugs.launchpad.net/virtualbox/+bug/657922/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258191] Re: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6: bcmwl kernel module failed to build

2013-12-06 Thread Daniel van Vugt
*** This bug is a duplicate of bug 994255 ***
https://bugs.launchpad.net/bugs/994255

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 994255, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 994255
   bcmwl-kernel-source / broadcom-sta failed to build [fatal error: 
asm/system.h: No such file or directory]

-- 
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/1258191

Title:
  bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6: bcmwl kernel module
  failed to build

Status in “bcmwl” package in Ubuntu:
  New

Bug description:
  Cannot activate Broadcom STA Wireless

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  DKMSKernelVersion: 3.8.0-34-generic
  Date: Thu Dec  5 23:17:39 2013
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MarkForUpload: True
  PackageVersion: 5.100.82.38+bdcom-0ubuntu6
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6: 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/1258191/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Kernel-packages] [Bug 1132156] Re: Realktek r8169 driver unrelaible with r8101/02

2013-12-06 Thread Chris B
Unfortunately I will not have access to the machine in question until the
end of this month.

I suggest the bug be closed for now to conserve everybody's time. When I
re-test, I will open it again if necessary.

Chris


On 6 December 2013 01:46, Christopher M. Penalver 
christopher.m.penal...@gmail.com wrote:

 Chris B, this bug was reported a while ago and there hasn't been any
 activity in it recently. We were wondering if this is still an issue? If
 so, could you please test for this with the latest development release
 of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
 /daily-live/current/ .

 If it remains an issue, could you please just make a comment to this.

 Also, could you please test the latest upstream kernel available (not the
 daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It
 will allow additional upstream developers to examine the issue. Once you've
 tested the upstream kernel, please comment on which kernel version
 specifically you tested. If this bug is fixed in the mainline kernel,
 please add the following tags:
 kernel-fixed-upstream
 kernel-fixed-upstream-VERSION-NUMBER

 where VERSION-NUMBER is the version number of the kernel you tested. For
 example:
 kernel-fixed-upstream-v3.13-rc2

 This can be done by clicking on the yellow circle with a black pencil icon
 next to the word Tags located at the bottom of the bug description. As
 well, please remove the tag:
 needs-upstream-testing

 If the mainline kernel does not fix this bug, please add the following
 tags:
 kernel-bug-exists-upstream
 kernel-bug-exists-upstream-VERSION-NUMBER

 As well, please remove the tag:
 needs-upstream-testing

 Once testing of the upstream kernel is complete, please mark this bug's
 Status as Confirmed. Please let us know your results. Thank you for your
 understanding.

 ** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1132156

 Title:
   Realktek r8169 driver unrelaible with r8101/02

 Status in “linux” package in Ubuntu:
   Incomplete

 Bug description:
   Support for the realtek r8101 Ethernet interfac is handled by r8169
 driver on Ubuntu Precise. However, the link is very unreliable and fails to
 connect most of the time. Speed negotiates down to 10Mbit/sec usually, half
 duplex, even when using the workaround 'sudo ethtool -s eth0 autoneg off'
   There seems a problem with the link speed negotiation?
   Won't connect at higher speeds at all.
   It's not possible to use the r8101 driver previously available as this
 is supplied by Realtek only for 2.4/2.6 kernels. It won't compile under
 3.2.x

   ProblemType: Bug
   DistroRelease: Ubuntu 12.04
   Package: linux-image-3.2.0-38-generic-pae 3.2.0-38.61
   ProcVersionSignature: Ubuntu 3.2.0-38.61-generic-pae 3.2.37
   Uname: Linux 3.2.0-38-generic-pae i686
   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
   AplayDevices:
 List of PLAYBACK Hardware Devices 
card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1
 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
   ApportVersion: 2.0.1-0ubuntu17.1
   Architecture: i386
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  oliver 2844 F pulseaudio
/dev/snd/controlC1:  oliver 2844 F pulseaudio
   Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe938000 irq 44'
  Mixer name : 'Realtek ALC662 rev1'
  Components : 'HDA:10ec0662,10ec0662,00100101'
  Controls  : 20
  Simple ctrls  : 11
   Card1.Amixer.info:
Card hw:1 'U0xeb1a0x2776'/'USB Device 0xeb1a:0x2776 at
 usb-:00:1d.7-7, high speed'
  Mixer name : 'USB Mixer'
  Components : 'USBeb1a:2776'
  Controls  : 2
  Simple ctrls  : 1
   Card1.Amixer.values:
Simple mixer control 'Mic',0
  Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
  Capture channels: Mono
  Limits: Capture 0 - 63
  Mono: Capture 61 [97%] [61.00dB] [off]
   Date: Sat Feb 23 16:27:14 2013
   HibernationDevice: RESUME=UUID=76935e71-c474-4de4-b9d4-9fb12d8b1d34
   MachineType: czc czc
   MarkForUpload: True
   ProcFB: 0 inteldrmfb
   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic-pae
 root=UUID=309c2426-7a29-4c52-a7bc-b41ed2a25184 ro quiet splash vt.handoff=7
   RelatedPackageVersions:
linux-restricted-modules-3.2.0-38-generic-pae N/A
linux-backports-modules-3.2.0-38-generic-pae  N/A
linux-firmware1.79.1
   RfKill:
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
   SourcePackage: linux
   UpgradeStatus: Upgraded to precise on 2012-06-17 (251 days ago)
   dmi.bios.date: 05/18/2009
   dmi.bios.vendor: American Megatrends Inc.
   dmi.bios.version: 080015
   dmi.board.asset.tag: To Be Filled By O.E.M.
   dmi.board.name: czc
   

[Kernel-packages] [Bug 1207812] Re: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu

2013-12-06 Thread Phil Culmer
This is possibly an iOS problem. Apple have added a procedure to require
user interaction before connecting to linux computers, apparently due to
a confirmed exploit with using a linux based system disguised as a
charger, which can install arbitrary software on the iPhone, and make
calls without user interaction. Whilst not likely to be a common
problem, the fact that it could be done with something like a gumstix in
a charger case means that it is a real one.

There's a report on the exploit at
http://www.macobserver.com/tmo/article/researchers-to-show-how-to-hack-
iphone-with-usb-charger

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1207812

Title:
  [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When plugging in an iPhone with iOS 7 - Currently BETA 4 I receive the 
following message on Ubuntu 13.04 :
  The Device Nick's iPhone is locked. Enter the passcode on the device and 
click Try again.

  The iPhone reporting Trust the currently connected computer? Trust/Don't 
Trust.
  This then happens in a continous loop when clicking Trust.

  ---
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nrawlins   2068 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb
  InstallationDate: Installed on 2013-08-15 (3 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Sony Corporation VGN-SR29XN_S
  MarkForUpload: True
  Package: linux 3.8.0.27.45
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  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: American Megatrends Inc.
  dmi.bios.version: R1130Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR29XN_S
  dmi.product.version: C6017UKK
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207812/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1172065] Re: 12.04.2 incorrect file name signed efi amd6.deb

2013-12-06 Thread Ralic
I have a few more details to share.

Mounting the iso under windows 8 displays the same incorrect filename,
as does burning the iso to physical media under windows 7.

So to me, it would appear that anyone unlucky enough to use the 
ubuntu-12.04.3-desktop-amd64.iso under windows 7/8, whether it be to:
a.) physically burn it to disc;
b.) mount it virtually;
c.) create a USB boot system from it
would be unable to successfully install ubuntu 12.04.3 LTS on an UEFI booted 
system.

During installation of grub, the installer throws the error 'grub-efi-
amd64-signed' package failed to install into /target/. Without the GRUB
boot loader, the installed system will not boot.

Because the .deb file is misnamed, the following is reported in syslog during 
installation:
Dec  4 17:41:36 ubuntu ubiquity: E: Unable to locate package 
grub-efi-amd64-signed

Workarounds:
===
If you are creating a bootable USB on Windows 7/8, rename the misnamed file 
after the USB has been written so that the installer does not error out during 
installation.

Alternatively, since the file is not misnamed in linux, using the iso to
burn a USB boot system from within linux will also likely work.

From what I can gather so far, Boot-Repair seems to be the current mechanism 
used to resolve problems that result from this, since Boot-Repair first 
removes grub and then re-installs it.
WARNING: (For those of you that may have arrived here from a Google search) 
Boot-Repair downloads the grub packages from the Internet, so be sure to have a 
fully functioning Internet connection if you use this method. If Boot-Repair 
doesn't find an Internet connection, you will be warned that your system may be 
left in an unbootable state. Heed this warning, because while apt will happily 
remove grub without one, it cannot download and re-install grub without a 
connection to the Internet.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1172065

Title:
  12.04.2 incorrect file name signed efi amd6.deb

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  download ISO has wrong nameamd6 should be amd64.
  In /pool/main/g/grub2-signed

  grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd6.deb
  seems like it should be 
  grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd64.deb

  See Also 
  http://ubuntuforums.org/showthread.php?t=2138041

  Just downloaded the ISO and it still has wrong name.
  Compared to Raring and Raring has correct name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172065/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1002429] Re: [MSI MS-7522] Ubuntu 12.04 hangs on shutdown and restart

2013-12-06 Thread Logan Page
Christopher, Unfortunetly I cannot comment on this issue anymore as I no
longer have the machine on which I experienced this problem. If needed I
can test the lastest development release on my new machine, however the
architecture is completely different.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1002429

Title:
  [MSI MS-7522] Ubuntu 12.04 hangs on shutdown and restart

Status in The Linux Kernel:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  WORKAROUND: Type in a terminal:
  sudo nano /etc/default/grub

  find the line:
  GRUB_CMDLINE_LINUX_DEFAULT=quiet splash

  and change it to:
  GRUB_CMDLINE_LINUX_DEFAULT=reboot=pci quiet splash

  save then perform via the Terminal:
  sudo update-grub

  and reboot the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  logan  2339 F pulseaudio
   /dev/snd/controlC0:  logan  2339 F pulseaudio
   /dev/snd/pcmC0D0p:   logan  2339 F...m pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb8f8000 irq 55'
     Mixer name : 'Realtek ALC892'
     Components : 'HDA:10ec0892,14627522,00100302'
     Controls  : 43
     Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfb9bc000 irq 56'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 6
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Mon May 21 20:30:36 2012
  HibernationDevice: RESUME=UUID=f0a86fb1-4678-4451-86e9-b6840a262f44
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: MSI MS-7522
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=ff1edde8-c3c4-4d9e-a97d-572a5a4402b9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-05-17 (4 days ago)
  dmi.bios.date: 07/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD65 (MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 4.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: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.1:bd07/28/2010:svnMSI:pnMS-7522:pvr4.0:rvnMSI:rnX58A-GD65(MS-7522):rvr4.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr4.0:
  dmi.product.name: MS-7522
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1002429/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Kernel-packages] [Bug 1252266] Re: Corrupted low memory after resume from suspend after updating to saucy

2013-12-06 Thread benpicco
 I built the next test kernel, up to the following commit:
 5f0e5afa0de4522abb3ea7d1369039b94e740ec5
 
 The test kernel can be downloaded from:
 http://kernel.ubuntu.com/~jsalisbury/lp1252266

Suspends, corrupts memory

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1252266

Title:
  Corrupted low memory after resume from suspend after updating to saucy

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to saucy and Linux 3.11 my Gigabyte 965P-DS3 board no longer 
properly resumes from suspend.
  The desktop still works fine after resume, but the ethernet interface won't 
come up again.
  dmesg after resume warns about corrupted low memory:

  [40560.864036] [ cut here ]
  [40560.864044] WARNING: CPU: 0 PID: 24687 at 
/build/buildd/linux-3.11.0/arch/x86/kernel/check.c:140 
check_for_bios_corruption+0x10f/0x120()
  [40560.864046] Memory corruption detected in low memory
  [40560.864048] Modules linked in: pci_stub vboxpci(OF) vboxnetadp(OF) 
vboxnetflt(OF) vboxdrv(OF) cuse ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) 
nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_conntrack(F) 
nf_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) 
bridge(F) stp(F) llc(F) ip6table_filter(F) ip6_tables(F) iptable_filter(F) 
ip_tables(F) ebtable_nat(F) ebtables(F) x_tables(F) joydev(F) xpad ff_memless 
hid_generic usbhid hid rfcomm bnep bluetooth binfmt_misc(F) kvm_intel(F) kvm(F) 
gpio_ich ppdev(F) ir_lirc_codec lirc_dev ir_sanyo_decoder ir_mce_kbd_decoder 
ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder 
e4000 rtl2832 usb_storage(F) snd_usb_audio snd_usbmidi_lib uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dvb_usb_rtl28xxu 
rtl2830 dvb_usb_v2 dvb_core rc_core snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) 
snd_seq_midi_event(F) microcode(F) pcspkr serio_raw(F) snd_rawmidi(F) 
snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) lpc_ich soundcore(F) 
nvidia(POF) parport_pc(F) drm mac_hid it87 hwmon_vid coretemp lp(F) parport(F) 
pata_acpi sky2 pata_jmicron ahci(F) libahci(F)
  [40560.864148] CPU: 0 PID: 24687 Comm: kworker/0:1 Tainted: PF   W  O 
3.11.0-13-generic #20-Ubuntu
  [40560.864151] Hardware name: Gigabyte Technology Co., Ltd. 
965P-DS3/965P-DS3, BIOS F14d 12/18/2008
  [40560.864155] Workqueue: events check_corruption
  [40560.864158]  0009 880064be9d30 816e54ba 
880064be9d78
  [40560.864162]  880064be9d68 81061dbd  
8801
  [40560.864166]  81ea73b0 0001 8800 
880064be9dc8
  [40560.864171] Call Trace:
  [40560.864178]  [816e54ba] dump_stack+0x45/0x56
  [40560.864183]  [81061dbd] warn_slowpath_common+0x7d/0xa0
  [40560.864187]  [81061e2c] warn_slowpath_fmt+0x4c/0x50
  [40560.864191]  [8104e5bf] check_for_bios_corruption+0x10f/0x120
  [40560.864195]  [8104e5de] check_corruption+0xe/0x40
  [40560.864200]  [8107d05c] process_one_work+0x17c/0x430
  [40560.864204]  [8107dcac] worker_thread+0x11c/0x3c0
  [40560.864208]  [8107db90] ? manage_workers.isra.24+0x2a0/0x2a0
  [40560.864212]  [810847b0] kthread+0xc0/0xd0
  [40560.864217]  [810846f0] ? kthread_create_on_node+0x120/0x120
  [40560.864221]  [816f51ec] ret_from_fork+0x7c/0xb0
  [40560.864225]  [810846f0] ? kthread_create_on_node+0x120/0x120
  [40560.864228] ---[ end trace a5d0e3f4744a1e9d ]---

  This did not happen with raring/Linux 3.8

  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:  benpicco   3071 F pulseaudio
   /dev/snd/controlC0:  benpicco   3071 F pulseaudio
  Date: Mon Nov 18 14:12:08 2013
  HibernationDevice: RESUME=UUID=81e8d3af-3d5b-4a61-a550-702a919449c5
  InstallationDate: Installed on 2012-02-27 (629 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5b216424-8d68-4640-9d4c-494eb0e00e9d ro quiet splash
  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:
   
  

[Kernel-packages] [Bug 863969] Re: ubuntu 11.10b2 resumes on wrong iMac display port

2013-12-06 Thread Peter T Hayward
One other point relating to the fedora installation on iMac with two
monitors. At boot time the login screen is always on the external
monitor. During login the kde desktop starts up and the display switches
to the internal monitor. I had previously used xrandr to force the
display to be only on the internal monitor (external off). The display
stays on the internal monitor until resume (from suspend), when the
display and desktop then switches back to the external monitor
permanently. Without two monitors it is impossible to use suspend and
resume.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/863969

Title:
  ubuntu 11.10b2 resumes on wrong iMac display port

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My iMac 21.5 (11,2) has ubuntu 11.10b2 installed, dual boot with Osx Lion. 
Ubuntu uses the open source ATI drivers At boot the video is good: on main 
display, correct resolution, reasonable performance. Resuming from sleep the 
system switches to the external video port (nothing connected) and leaves the 
main screen unlit. If I plug second monitor onto the external port I can 
continue after resume. On external screen the X resolution is as if for the 
main screen (1920x1080); incorrect for external screen (should be 1280x1024). I 
have no way to relight the main display, except restart.
  This issue of wrong display port used to affect ubuntu booting on iMac (see 
#542660  #597070) but that problem seems to have been tamed in Oneiric. 
However not being able to resume without a second screen is a problem, 
especially since the higher power consumption in Oneiric (+15w compared with 
OSX) means you would like to sleep when possible. From earlier discussions this 
seems likely to be something fairly complex in KMS code.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.19
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  peter  1558 F pulseaudio
   /dev/snd/controlC0:  peter  1558 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd050 irq 42'
 Mixer name : 'Cirrus Logic CS4206'
 Components : 'HDA:10134206,106b1200,00100301'
 Controls  : 22
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd043 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Sat Oct  1 11:41:07 2011
  HibernationDevice: RESUME=UUID=f6e1b41a-449e-459f-8c41-f8858958eec3
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64+mac (20110816)
  MachineType: Apple Inc. iMac11,2
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=c5afd811-14a5-41cb-a001-99040b12285c ro quiet splash vt.handoff=7
  PulseSinks:
   Error: command ['pacmd', 'list-sinks'] failed with exit code 1: Home 
directory /home/peter not ours.
   No PulseAudio daemon running, or not running as session daemon.
  PulseSources:
   Error: command ['pacmd', 'list-sources'] failed with exit code 1: Home 
directory /home/peter not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM112.88Z.0057.B00.1005031455
  dmi.board.name: Mac-F2238AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2238AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B00.1005031455:bd05/03/10:svnAppleInc.:pniMac11,2:pvr1.0:rvnAppleInc.:rnMac-F2238AC8:rvr:cvnAppleInc.:ct13:cvrMac-F2238AC8:
  dmi.product.name: iMac11,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/863969/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258495] Status changed to Confirmed

2013-12-06 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258495

Title:
  backlight too bright, can't dim it much

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Screen is far too bright, dims only slightly with hotkeys, brightness
  control applet ineffective. Tried more than half a dozen solutions
  (incl. editing the grub which used to work fine with Ubuntu 12.04) but
  none of them worked.

  thindi@thindi-AOA110:~$ ls /sys/class/backlight  backlight
  thindi@thindi-AOA110:~$ grep -r . /proc/acpi  acpi
  grep: /proc/acpi/event: Permission denied
  thindi@thindi-AOA110:~$ sudo acpidump -o acpidump.txt
  thindi@thindi-AOA110:~$ acpixtract acpidump.txt
  Acpi table [DSDT] -  24038 bytes written to DSDT.dat
  Acpi table [SSDT] -   1220 bytes written to SSDT.dat
  thindi@thindi-AOA110:~$ iasl -d DSDT.dat

  Intel ACPI Component Architecture
  AML Disassembler version 20100528 [Dec 19 2012]
  Copyright (c) 2000 - 2010 Intel Corporation
  Supports ACPI Specification Revision 4.0a

  Loading Acpi table from file DSDT.dat
  Acpi table [DSDT] successfully installed and loaded
  Pass 1 parse of [DSDT]
  Pass 2 parse of [DSDT]
  Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
  
...
  Parsing completed
  Disassembly completed, written to DSDT.dsl
  thindi@thindi-AOA110:~$ sudo fwts  fwts
  Test: Gather kernel system information. 
Gather kernel signature.1 info only 
 
Gather kernel system information.   1 info only 
 
Gather kernel boot command line.1 info only 
 
Gather ACPI driver version. 1 info only 
 
  Test: Gather BIOS DMI information.  
Gather BIOS DMI information 1 info only 
 
  Test: Scan kernel log for Oopses.   
Kernel log oops check.  2 passed
 
  Test: Scan kernel log for errors and warnings.  
Kernel log error check. 1 passed
 
  Test: MTRR validation.  
Validate the kernel MTRR IOMEM setup.   1 failed
 
Validate the MTRR setup across all processors.  1 passed
 
Check for AMD MtrrFixDramModEn being cleared by the ..  1 skipped   
 
  Test: General ACPI information check.   
Determine Kernel ACPI version.  1 info only 
 
Determine machine's ACPI version.   1 info only 
 
Determine AML compiler. 1 info only 
 
  Test: Ubuntu UEFI secure boot test. 
   Test aborted..   
 
  Test: Check for UEFI Compatibility Support Module.  
Check for UEFI Compatibility Support Module.1 info only 
 
  Test: Checks firmware has set PCI Express MaxReadReq to a higher value on.. 
Check firmware settings MaxReadReq for PCI Express d..  1 failed
 
  Test: Check PCI host bridge configuration using _CRS.   
Check PCI host bridge configuration using _CRS. 1 skipped   
 
  Test: PCIe ASPM check.  
PCIe ASPM ACPI test.
 
PCIe ASPM registers test.   3 passed, 10 
warnings
  Test: HPET configuration test.  
Check HPET base in kernel log.  
 
Check HPET base in HPET table.  1 passed
 
Check HPET base in DSDT and/or SSDT.
 
Sanity check HPET configuration.
 
  Test: Test DMI/SMBIOS tables for errors.
Find and Check SMBIOS Table Entry Point.6 passed
 
Test DMI/SMBIOS tables for errors.  31 passed, 2 failed 
 
  Test: Check 

[Kernel-packages] [Bug 1002429] Re: [MSI MS-7522] Ubuntu 12.04 hangs on shutdown and restart

2013-12-06 Thread Christopher M. Penalver
Logan Page, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1002429/comments/21
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1002429

Title:
  [MSI MS-7522] Ubuntu 12.04 hangs on shutdown and restart

Status in The Linux Kernel:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  WORKAROUND: Type in a terminal:
  sudo nano /etc/default/grub

  find the line:
  GRUB_CMDLINE_LINUX_DEFAULT=quiet splash

  and change it to:
  GRUB_CMDLINE_LINUX_DEFAULT=reboot=pci quiet splash

  save then perform via the Terminal:
  sudo update-grub

  and reboot the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  logan  2339 F pulseaudio
   /dev/snd/controlC0:  logan  2339 F pulseaudio
   /dev/snd/pcmC0D0p:   logan  2339 F...m pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb8f8000 irq 55'
     Mixer name : 'Realtek ALC892'
     Components : 'HDA:10ec0892,14627522,00100302'
     Controls  : 43
     Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfb9bc000 irq 56'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 6
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Mon May 21 20:30:36 2012
  HibernationDevice: RESUME=UUID=f0a86fb1-4678-4451-86e9-b6840a262f44
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: MSI MS-7522
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=ff1edde8-c3c4-4d9e-a97d-572a5a4402b9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-05-17 (4 days ago)
  dmi.bios.date: 07/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD65 (MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 4.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: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.1:bd07/28/2010:svnMSI:pnMS-7522:pvr4.0:rvnMSI:rnX58A-GD65(MS-7522):rvr4.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr4.0:
  dmi.product.name: MS-7522
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1002429/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1250828] Re: freeze on diskIO without real IO

2013-12-06 Thread jl451
freeze was 15+ seconds
uname -a
Linux Ubunto4ka 3.12.2-031202-generic #201311291538 SMP Fri Nov 29 20:39:07 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12.2-trusty/

Dec  6 16:12:23 Ubunto4ka kernel: [95836.316381] INFO: task mozStorage #8:8285 
blocked for more than 5 seconds.
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316385]   Tainted: PFC O 
3.12.2-031202-generic #201311291538
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316385] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316387] mozStorage #8   D 
81811d80 0  8285   7860 0x
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316390]  880062f21d28 
0002 8801389e2b40 8800371e0f30
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316392]  880062f21fd8 
880062f21fd8 880062f21fd8 00014500
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316394]  880139378000 
88006d025ec0 880062f21d38 8800ba5f8000
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316397] Call Trace:
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316402]  [8174dbb9] 
schedule+0x29/0x70
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316423]  [a009d30c] 
wait_log_commit.isra.21+0x10c/0x130 [btrfs]
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316427]  [8108d2a0] ? 
add_wait_queue+0x60/0x60
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316437]  [a00a2ed2] 
btrfs_sync_log+0x442/0x6d0 [btrfs]
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316440]  [811d6ac0] ? 
dput+0x20/0x90
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316449]  [a0077b9b] 
btrfs_sync_file+0x27b/0x2e0 [btrfs]
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316452]  [811ef2eb] 
vfs_fsync+0x2b/0x40
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316454]  [812c827d] 
ecryptfs_fsync+0x3d/0x50
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316456]  [811ef3cd] 
do_fsync+0x5d/0x90
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316457]  [811ef7b0] 
SyS_fsync+0x10/0x20
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316459]  [817587ff] 
tracesys+0xe1/0xe6
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316461] INFO: task mozStorage #11:7286 
blocked for more than 5 seconds.
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316462]   Tainted: PFC O 
3.12.2-031202-generic #201311291538
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316463] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316464] mozStorage #11  D 
81811d80 0  7286   7860 0x
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316466]  880008ce3d28 
0002 8801389a4000 880037120c60
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316468]  880008ce3fd8 
880008ce3fd8 880008ce3fd8 00014500
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316470]  88013935dec0 
880008a9 880008ce3d38 8800ba5f8000
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316472] Call Trace:
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316474]  [8174dbb9] 
schedule+0x29/0x70
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316483]  [a009d30c] 
wait_log_commit.isra.21+0x10c/0x130 [btrfs]
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316485]  [8108d2a0] ? 
add_wait_queue+0x60/0x60
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316494]  [a00a2ed2] 
btrfs_sync_log+0x442/0x6d0 [btrfs]
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316496]  [811d6ac0] ? 
dput+0x20/0x90
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316505]  [a0077b9b] 
btrfs_sync_file+0x27b/0x2e0 [btrfs]
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316507]  [811ef2eb] 
vfs_fsync+0x2b/0x40
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316509]  [812c827d] 
ecryptfs_fsync+0x3d/0x50
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316510]  [811ef3cd] 
do_fsync+0x5d/0x90
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316512]  [811ef7b0] 
SyS_fsync+0x10/0x20
Dec  6 16:12:23 Ubunto4ka kernel: [95836.316513]  [817587ff] 
tracesys+0xe1/0xe6
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315297] INFO: task Cache I/O:8165 
blocked for more than 5 seconds.
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315300]   Tainted: PFC O 
3.12.2-031202-generic #201311291538
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315301] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315302] Cache I/O   D 
81811d80 0  8165   7860 0x
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315305]  880122501d28 
0002 880037250be0 880138917b40
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315308]  880122501fd8 
880122501fd8 880122501fd8 00014500
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315310]  81c144a0 
8801289e97b0 880122501d38 8800ba5f8000
Dec  6 16:12:28 Ubunto4ka kernel: [95841.315313] Call Trace:
Dec  6 16:12:28 Ubunto4ka kernel: 

[Kernel-packages] [Bug 863969] Re: ubuntu 11.10b2 resumes on wrong iMac display port

2013-12-06 Thread Christopher M. Penalver
Peter T Hayward, if you have a problem in Fedora, it would be best to
file a report on their bug tracker -
http://fedoraproject.org/wiki/How_to_file_a_bug_report

Regarding Ubuntu, it would be helpful if you booted into the live
environment of the latest release that currently boots (ex. Saucy,
Raring, or Quantal if either of the prior two didn't work) and checked
for this via http://releases.ubuntu.com/ .

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/863969

Title:
  ubuntu 11.10b2 resumes on wrong iMac display port

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My iMac 21.5 (11,2) has ubuntu 11.10b2 installed, dual boot with Osx Lion. 
Ubuntu uses the open source ATI drivers At boot the video is good: on main 
display, correct resolution, reasonable performance. Resuming from sleep the 
system switches to the external video port (nothing connected) and leaves the 
main screen unlit. If I plug second monitor onto the external port I can 
continue after resume. On external screen the X resolution is as if for the 
main screen (1920x1080); incorrect for external screen (should be 1280x1024). I 
have no way to relight the main display, except restart.
  This issue of wrong display port used to affect ubuntu booting on iMac (see 
#542660  #597070) but that problem seems to have been tamed in Oneiric. 
However not being able to resume without a second screen is a problem, 
especially since the higher power consumption in Oneiric (+15w compared with 
OSX) means you would like to sleep when possible. From earlier discussions this 
seems likely to be something fairly complex in KMS code.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.19
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  peter  1558 F pulseaudio
   /dev/snd/controlC0:  peter  1558 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd050 irq 42'
 Mixer name : 'Cirrus Logic CS4206'
 Components : 'HDA:10134206,106b1200,00100301'
 Controls  : 22
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd043 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Sat Oct  1 11:41:07 2011
  HibernationDevice: RESUME=UUID=f6e1b41a-449e-459f-8c41-f8858958eec3
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64+mac (20110816)
  MachineType: Apple Inc. iMac11,2
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=c5afd811-14a5-41cb-a001-99040b12285c ro quiet splash vt.handoff=7
  PulseSinks:
   Error: command ['pacmd', 'list-sinks'] failed with exit code 1: Home 
directory /home/peter not ours.
   No PulseAudio daemon running, or not running as session daemon.
  PulseSources:
   Error: command ['pacmd', 'list-sources'] failed with exit code 1: Home 
directory /home/peter not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM112.88Z.0057.B00.1005031455
  dmi.board.name: Mac-F2238AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2238AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM112.88Z.0057.B00.1005031455:bd05/03/10:svnAppleInc.:pniMac11,2:pvr1.0:rvnAppleInc.:rnMac-F2238AC8:rvr:cvnAppleInc.:ct13:cvrMac-F2238AC8:
  dmi.product.name: iMac11,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/863969/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1125452] Re: [Lenovo T530]: Volume Mute key LED is not responding correctly

2013-12-06 Thread Christopher M. Penalver
** Tags added: bios-outdated-2.57

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1125452

Title:
  [Lenovo T530]: Volume Mute key LED is not responding correctly

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed

Bug description:
  Problem description:

  When attempting a hardware mute the volume mute action is applied
  correctly and the volume applet correctly displays that the audio
  output is muted. However, the mute key's LED backlight's
  responsiveness is flaky at best. Pressing the mute key repeatedly may
  or may not result in an mute key LED change. This can quickly get out
  of sync where it's possible for the mute key LED to be lit yet the
  volume is not actually muted.

  Again mute action does actually respond correctly via keypress:

  Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 87
Mono: Playback 63 [72%] [-18.00dB] [on]

  Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 87
Mono: Playback 63 [72%] [-18.00dB] [off]

  
  Software mute does not change status of LED.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-37-generic 3.2.0-37.58
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1621 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf253 irq 46'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,17aa21f6,00100203 
HDA:80862806,80860101,0010'
 Controls  : 41
 Simple ctrls  : 15
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
 Mixer name : 'ThinkPad EC (unknown)'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Thu Feb 14 13:33:49 2013
  HibernationDevice: RESUME=UUID=33af243d-8694-4458-a1eb-5c94d7303d8e
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MachineType: LENOVO 235923U
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic 
root=UUID=212db818-8dcd-4bbd-94a9-0a9ca8d086a3 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-37-generic N/A
   linux-backports-modules-3.2.0-37-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ET37WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 235923U
  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:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn235923U:pvrThinkPadT530:rvnLENOVO:rn235923U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 235923U
  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/1125452/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 760464] Re: WARNING: at /build/buildd/linux-2.6.38/kernel/printk.c:288 do_syslog+0xa4/0x4c0() shown after syslog-ng installation

2013-12-06 Thread Gergely Nagy
** Changed in: syslog-ng (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/760464

Title:
  WARNING: at /build/buildd/linux-2.6.38/kernel/printk.c:288
  do_syslog+0xa4/0x4c0() shown after syslog-ng installation

Status in “linux” package in Ubuntu:
  Triaged
Status in “syslog-ng” package in Ubuntu:
  Fix Released
Status in “linux” source package in Natty:
  Won't Fix
Status in “syslog-ng” source package in Natty:
  Invalid

Bug description:
  Installed syslog-ng; The system log viewer, terminal and firefox
  browser was open and then this bug popped up. It's nature remains
  unknown to me as now. Some messages might be Lithuanian.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: No
  Reproducible: No
  ProcVersionSignature: hostname 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juozas 1514 F pulseaudio
  CRDA: Error: [Errno 2] Toks failas ar aplankas neegzistuoja
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfcffc000 irq 44'
     Mixer name : 'Realtek ALC887'
     Components : 'HDA:10ec0887,1043840b,00100202'
     Controls  : 24
     Simple ctrls  : 14
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfeafc000 irq 16'
     Mixer name : 'Nvidia GPU 0b HDMI/DP'
     Components : 'HDA:10de000b,10de0101,00100100'
     Controls  : 16
     Simple ctrls  : 4
  Date: Thu Apr 14 11:30:59 2011
  Failure: oops
  Frequency: I don't know.
  HibernationDevice: RESUME=UUID=b1a27474-7155-4552-9820-32b1c3fb6ae7
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.

   vboxnet0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=427aaa6f-4f6c-411b-a11e-d671b7557303 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.50
  RfKill:

  SourcePackage: linux
  Title: WARNING: at /build/buildd/linux-2.6.38/kernel/printk.c:288 
do_syslog+0xa4/0x4c0()
  UpgradeStatus: Upgraded to natty on 2011-04-08 (5 days ago)
  dmi.bios.date: 06/01/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0505
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41-M LE
  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.:bvr0505:bd06/01/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41-MLE: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/760464/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

2013-12-06 Thread Stijn Volckaert
not fixed

-- 
You 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 Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnP75-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  

[Kernel-packages] [Bug 1172065] Re: 12.04.2 incorrect file name signed efi amd6.deb

2013-12-06 Thread Fred Palmer
Orginal error was in ISO itself.

Above error seems to be just when written with certain tools that file
name is too long to be converted from ISO correctly.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1172065

Title:
  12.04.2 incorrect file name signed efi amd6.deb

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  download ISO has wrong nameamd6 should be amd64.
  In /pool/main/g/grub2-signed

  grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd6.deb
  seems like it should be 
  grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd64.deb

  See Also 
  http://ubuntuforums.org/showthread.php?t=2138041

  Just downloaded the ISO and it still has wrong name.
  Compared to Raring and Raring has correct name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172065/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1050352] Re: [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects and connects

2013-12-06 Thread Tareeq
I just upgraded from Raring to Saucy (actually a mint user), I also have
the VL80x USB3.0 chipset on my EVGA Z68 FTW motherboard.  In raring the
USB 3.0 was flakey, a usb3.0 device had to be connected at boot time,
for it work, USB 2.0 worked without any issues on that controller.
Since the upgrade I could not USB 2.0 or 3.0 to work on the Via
Contoller (USB 3.0 ports).  It was completly unresponsive.  I came
across this bug, and tried what Christopher suggested.

I installed 3.12-Saucy (http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.12-saucy/).  Since I have installed the 3.12 kernel, the
Via VL80x controller works perfectly.  It even fixed the annoying
softlock cpu0 error I was getting at boot time.

*warning* If you have an nvidia GPU, after installing the kernel, it
could not build the kernel module for the driver, I had to install the
xorg-edgers ppa; https://launchpad.net/~xorg-edgers/+archive/ppa and
install the nvidia 331 driver.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1050352

Title:
  [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects
  and connects

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 12.10 AMD64, kernel 3.5.0-14.16.
  External hard drive Hitachi Touro Desk 3.0 connected to USB 3.0 port.

  Gets disconnected randomly and then connected again. Only happens with
  USB 3.0 connection (xhci).

  WORKAROUND: When plugged to USB 2.0 (ehci) port it works ok.

  Attached is related kernel log portion: there is nothing special there
  except for these lines:

  11-2: Parent hub missing LPM exit latency info.  Power management will be 
impacted.
  usb 11-2: USB disconnect, device number 2
  ---
  AcpiTables: Error: command ['pkexec', 
'/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error 
executing /usr/share/apport/dump_acpi_tables.py: Permission denied
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dmitry 3011 F pulseaudio
   /dev/snd/controlC1:  dmitry 3011 F pulseaudio
   /dev/snd/controlC0:  dmitry 3011 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e3fa02f8-4f15-4f00-9d79-e982d4837b5c
  IwConfig:
   vboxnet0  no wireless extensions.

   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD4
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic 
root=UUID=33c3405d-4b3c-4b5c-a1c3-fd2c7bad1c79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-14-generic N/A
   linux-backports-modules-3.5.0-14-generic  N/A
   linux-firmware1.91
  RfKill:

  Tags:  quantal running-unity
  Uname: Linux 3.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago)
  UserGroups: adm cdrom dialout fuse kvm libvirtd lpadmin plugdev pulse 
pulse-access sambashare sudo vboxusers wireshark
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P55A-UD4
  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.:bvrF14:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1050352/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258573] [NEW] package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 17

2013-12-06 Thread DimkaS
Public bug reported:

Can't tell exactly what had happened. For some reason I happen to have
no initrd after kernel upgrade, so booting with 3.8.0-35 ends with
kernel panic. I've booted with 3.8.0-34 and tried to reinstall -35
image. Aptitude fails with

Running depmod.
update-initramfs: deferring update (hook will be called later)
Failed to symbolic-link /boot/initrd.img-3.8.0-35-generic to initrd.img:File 
exists at /var/lib/dpkg/info/linux-image-extra-3.8.0-35-generic.postinst line 
614.

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: linux-image-extra-3.8.0-35-generic 3.8.0-35.50
ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
Uname: Linux 3.8.0-34-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dimka  2018 F pulseaudio
 /dev/snd/controlC0:  dimka  2018 F pulseaudio
Date: Fri Dec  6 20:27:19 2013
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
HibernationDevice: RESUME=UUID=3c7ce127-77de-4f0d-b5b8-338ced543a4d
InstallationDate: Installed on 2013-11-17 (19 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
MachineType: FUJITSU LIFEBOOK SH561
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=84e8fdde-34c6-4de4-87ee-8510f00ab5b0 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.00-13ubuntu3
SourcePackage: linux
Title: package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.05
dmi.board.name: FJNB227
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd02/15/2011:svnFUJITSU:pnLIFEBOOKSH561:pvr:rvnFUJITSU:rnFJNB227:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK SH561
dmi.sys.vendor: FUJITSU

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 package-from-proposed raring

** Description changed:

  Can't tell exactly what had happened. For some reason I happen to have
- no initrd after kernel upgrade, so buuting with 3.8.0-35 end with kernel
- panic. I've booted with 3.8.0-34 and tried to reinstall -35 image.
- Aptitude fails with
+ no initrd after kernel upgrade, so booting with 3.8.0-35 ends with
+ kernel panic. I've booted with 3.8.0-34 and tried to reinstall -35
+ image. Aptitude fails with
  
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Failed to symbolic-link /boot/initrd.img-3.8.0-35-generic to initrd.img:File 
exists at /var/lib/dpkg/info/linux-image-extra-3.8.0-35-generic.postinst line 
614.
  
  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: linux-image-extra-3.8.0-35-generic 3.8.0-35.50
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  dimka  2018 F pulseaudio
-  /dev/snd/controlC0:  dimka  2018 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  dimka  2018 F pulseaudio
+  /dev/snd/controlC0:  dimka  2018 F pulseaudio
  Date: Fri Dec  6 20:27:19 2013
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
  HibernationDevice: RESUME=UUID=3c7ce127-77de-4f0d-b5b8-338ced543a4d
  InstallationDate: Installed on 2013-11-17 (19 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: FUJITSU LIFEBOOK SH561
  MarkForUpload: True
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=84e8fdde-34c6-4de4-87ee-8510f00ab5b0 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.00-13ubuntu3
  SourcePackage: linux
  Title: package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.05
  dmi.board.name: FJNB227
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 

[Kernel-packages] [Bug 1258573] Re: package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 17

2013-12-06 Thread DimkaS
I've figured out that purging all *-35 files helps. You can then
reinstall them cleanly. Probably not a bug, just local issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258573

Title:
  package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 17

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Can't tell exactly what had happened. For some reason I happen to have
  no initrd after kernel upgrade, so booting with 3.8.0-35 ends with
  kernel panic. I've booted with 3.8.0-34 and tried to reinstall -35
  image. Aptitude fails with

  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Failed to symbolic-link /boot/initrd.img-3.8.0-35-generic to initrd.img:File 
exists at /var/lib/dpkg/info/linux-image-extra-3.8.0-35-generic.postinst line 
614.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: linux-image-extra-3.8.0-35-generic 3.8.0-35.50
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dimka  2018 F pulseaudio
   /dev/snd/controlC0:  dimka  2018 F pulseaudio
  Date: Fri Dec  6 20:27:19 2013
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
  HibernationDevice: RESUME=UUID=3c7ce127-77de-4f0d-b5b8-338ced543a4d
  InstallationDate: Installed on 2013-11-17 (19 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: FUJITSU LIFEBOOK SH561
  MarkForUpload: True
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=84e8fdde-34c6-4de4-87ee-8510f00ab5b0 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.00-13ubuntu3
  SourcePackage: linux
  Title: package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.05
  dmi.board.name: FJNB227
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd02/15/2011:svnFUJITSU:pnLIFEBOOKSH561:pvr:rvnFUJITSU:rnFJNB227:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK SH561
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258573/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258573] Status changed to Confirmed

2013-12-06 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258573

Title:
  package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 17

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Can't tell exactly what had happened. For some reason I happen to have
  no initrd after kernel upgrade, so booting with 3.8.0-35 ends with
  kernel panic. I've booted with 3.8.0-34 and tried to reinstall -35
  image. Aptitude fails with

  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Failed to symbolic-link /boot/initrd.img-3.8.0-35-generic to initrd.img:File 
exists at /var/lib/dpkg/info/linux-image-extra-3.8.0-35-generic.postinst line 
614.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: linux-image-extra-3.8.0-35-generic 3.8.0-35.50
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dimka  2018 F pulseaudio
   /dev/snd/controlC0:  dimka  2018 F pulseaudio
  Date: Fri Dec  6 20:27:19 2013
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
  HibernationDevice: RESUME=UUID=3c7ce127-77de-4f0d-b5b8-338ced543a4d
  InstallationDate: Installed on 2013-11-17 (19 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: FUJITSU LIFEBOOK SH561
  MarkForUpload: True
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=84e8fdde-34c6-4de4-87ee-8510f00ab5b0 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.00-13ubuntu3
  SourcePackage: linux
  Title: package linux-image-extra-3.8.0-35-generic 3.8.0-35.50 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 17
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.05
  dmi.board.name: FJNB227
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd02/15/2011:svnFUJITSU:pnLIFEBOOKSH561:pvr:rvnFUJITSU:rnFJNB227:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK SH561
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258573/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1256094] Re: CVE-2013-6383

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux-armadaxp (Ubuntu Quantal)
   Status: New = Fix Committed

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux (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 Precise)
   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/1256094

Title:
  CVE-2013-6383

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  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:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  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:
  Fix Committed
Status in “linux” source package in Quantal:
  Fix Committed
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
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 Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
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:
  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 

[Kernel-packages] [Bug 1256088] Re: CVE-2013-6381

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (Ubuntu Quantal)
   Status: New = Fix Committed

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux (Ubuntu Quantal)
   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

-- 
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/1256088

Title:
  CVE-2013-6381

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:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  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:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  Fix Committed
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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Saucy:
  New
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  New
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in 

[Kernel-packages] [Bug 1256083] Re: CVE-2013-6380

2013-12-06 Thread John Johansen
** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux (Ubuntu Saucy)
   Status: New = Fix Committed

** Changed in: linux (Ubuntu Trusty)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1256083

Title:
  CVE-2013-6380

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  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:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
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:
  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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
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:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Saucy:
  New
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  New
Status in “linux-lts-backport-natty” source package in Trusty:
  New
Status in “linux-lts-quantal” source package in Trusty:
  Invalid
Status in “linux-lts-raring” source 

[Kernel-packages] [Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise

2013-12-06 Thread Joseph Salisbury
Ok, one more shot.  It looks like PPPOE wasn't enabled for amd64 in
mainline.  I enabled it and rebuilt a test kernel.

Again, its up to the following commit:
6be35c700f742e911ecedd07fcc43d4439922334

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251946

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1251946

Title:
  Network related kernel panic on Atom 64bit system using saucy backport
  stack on precise

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I can't report this through ubuntu-bug as the system is a firewall
  with restricted connectivity and the kernel bug prevents me from using
  the system for more than a couple minutes anyway.

  I recently deployed the saucy kernel on that precise system, after the
  first reboot things looked fine but just a few minutes later, the
  whole system hang. I reproduced this very reliably 3-4 times, then
  hooked up a console cable and extracted the following kernel panic:

  [  124.428031] [ cut here ]
  [  124.432656] Kernel BUG at 81629ce8 [verbose debug info unavailable]
  [  124.439622] invalid opcode:  [#1] SMP 
  [  124.443766] Modules linked in: authenc(F) esp6(F) xfrm6_mode_transport(F) 
ipcomp6(F) xfrm6_tunnel(F) tunnel6(F) xfrm4_mode_tunnel(F) xfrm6_mode_tunnel(F) 
v)
  [  124.577657] CPU: 0 PID: 12800 Comm: samba Tainted: GF   WC   
3.11.0-13-generic #20~precise2-Ubuntu
  [  124.586962] Hardware name:  /D2500CC, BIOS 
CCCDT10N.86A.0039.2013.0425.1625 04/25/2013
  [  124.596268] task: 8800cd711770 ti: 8800bfde2000 task.ti: 
8800bfde2000
  [  124.603752] RIP: 0010:[81629ce8]  [81629ce8] 
pskb_expand_head+0x288/0x2d0
  [  124.612305] RSP: 0018:88012fc03688  EFLAGS: 00010202
  [  124.617621] RAX: 0003 RBX: 8800cd44d000 RCX: 
0020
  [  124.624762] RDX:  RSI: 0050 RDI: 
06c0
  [  124.631900] RBP: 88012fc036c8 R08: 3f2c68050060 R09: 
3f2c68050060
  [  124.639037] R10: bfcb2ffeff3e1602 R11: 20270ff0c0f20726 R12: 
0050
  [  124.646175] R13: 0020 R14: 0001 R15: 
81709280
  [  124.653317] FS:  7f81c5448740() GS:88012fc0() 
knlGS:
  [  124.661407] CS:  0010 DS:  ES:  CR0: 80050033
  [  124.667158] CR2: 0330e780 CR3: bfdc9000 CR4: 
07f0
  [  124.674295] Stack:
  [  124.676318]  e8c00640 000180400040 8801264d6d40 
8800cd44d000
  [  124.683792]  880126ddc000 880126919180 0001 
81709280
  [  124.691262]  88012fc036f8 816caac0 8800cd44d000 
0001
  [  124.698729] Call Trace:
  [  124.701187]  IRQ 
  [  124.703121]  [81709280] ? xfrm6_extract_output+0x50/0x50
  [  124.709525]  [816caac0] xfrm_output_one+0x90/0x230
  [  124.715189]  [816cad26] xfrm_output_resume+0xc6/0x170
  [  124.721112]  [816cade3] xfrm_output2+0x13/0x20
  [  124.726429]  [816cae2f] xfrm_output+0x3f/0x100
  [  124.731747]  [81709299] xfrm6_output_finish+0x19/0x20
  [  124.737669]  [816d5729] ip6_fragment+0x929/0xab0
  [  124.743160]  [81709280] ? xfrm6_extract_output+0x50/0x50
  [  124.749344]  [81708ed0] ? xfrm6_local_rxpmtu+0x70/0x70
  [  124.755356]  [81708fa2] __xfrm6_output+0xd2/0x180
  [  124.760933]  [817092ca] xfrm6_output+0x2a/0x70
  [  124.766250]  [816d4a03] ip6_forward+0x243/0x640
  [  124.771654]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.776971]  [816d5aa8] ip6_rcv_finish+0x88/0x90
  [  124.782460]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.787787]  [a027783d] __ipv6_conntrack_in+0xdd/0x180 
[nf_conntrack_ipv6]
  [  124.795539]  [a0277905] ipv6_conntrack_in+0x25/0x30 
[nf_conntrack_ipv6]
  [  124.803027]  [816660df] nf_iterate+0x8f/0xd0
  [  124.808172]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.813488]  [8166619d] nf_hook_slow+0x7d/0x150
  [  124.818891]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.824210]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.829532]  [a021b3e2] nf_ct_frag6_output+0xf2/0x100 
[nf_defrag_ipv6]
  [  124.836932]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.842255]  [a021a0a8] ipv6_defrag.part.2+0x98/0xe0 
[nf_defrag_ipv6]
  [  124.849577]  [a021a11c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6]
  [  124.856284]  [816660df] nf_iterate+0x8f/0xd0
  [  124.861429]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.866743]  [8166619d] nf_hook_slow+0x7d/0x150
  [  124.872146]  [816d5a20] ? ip6_output+0xb0/0xb0
  [  124.877467]  [816d6213] ipv6_rcv+0x313/0x3f0
  [  124.882609]  [81636cba] 

[Kernel-packages] [Bug 1252426] Re: CVE-2013-6763

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux-armadaxp (Ubuntu Quantal)
   Status: New = Fix Committed

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Fix Committed

** Changed in: linux (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 Precise)
   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/1252426

Title:
  CVE-2013-6763

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Committed
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  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:
  Fix Committed
Status in “linux” source package in Quantal:
  Fix Committed
Status in “linux-armadaxp” source package in Quantal:
  Fix Committed
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
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 Raring:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
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:
  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

[Kernel-packages] [Bug 1237336] Re: linux-image-3.11.0-12-generic doesn't boot

2013-12-06 Thread Joseph Salisbury
Do you see a different error when you have PCMCIA disabled?  Can you
take a digital picture of where the system hangs?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1237336

Title:
  linux-image-3.11.0-12-generic doesn't boot

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  I made a fresh install of Ubuntu Ringtail and Upgraded to Saucy.

  Turns out that the machine won't boot with linux-image-3.11.0-12-generic, but 
*will* boot with the old ringtail kernel
  linux-image-3.8.0-31-generic!

  I created two screenshots, one shows the point where the boot process
  with the Saucy kernel stops (after enabling the swap), and another
  picture of the boot process with the ringtail kernel AFTER
  successfully enabling the swap.

  This bug report was generated on 3.8.0-31, since I can't get 3.11 to
  boot...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guest-vLutlY   1977 F pulseaudio
  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: Wed Oct  9 12:40:08 2013
  InstallationDate: Installed on 2013-10-08 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: Acer Extensa 5230
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=5a5a0960-705c-4925-88fa-bcb05eb87c12 ro 
crashkernel=384M-2G:64M,2G-:128M noquiet nosplash
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-09 (0 days ago)
  WifiSyslog:

  dmi.bios.date: 02/02/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.28
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd02/02/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5230
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1518 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=765ea940-a006-4825-a979-c4ec48d81572
  InstallationDate: Installed on 2013-10-08 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: Acer Extensa 5230
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=5a5a0960-705c-4925-88fa-bcb05eb87c12 ro 
crashkernel=384M-2G:64M,2G-:128M noquiet nosplash
  ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
  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-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-09 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 10/30/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.36
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.36:bd10/30/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5230
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237336/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1251035] Re: kernel stack trace when running openvswitch DEP-8 tests

2013-12-06 Thread Joseph Salisbury
** 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/1251035

Title:
  kernel stack trace when running openvswitch DEP-8 tests

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The DEP-8 test exercises the openvswitch userspace and kernel module
  by setting up to bridges, connecting 7 'hosts' to each bridge,
  patching the bridges together and then running performance and ping
  tests between hosts on different bridges.

  The stack trace occurs on teardown of the bridges/switches.

  [  426.965530] [ cut here ]
  [  426.965538] WARNING: CPU: 2 PID: 16575 at 
/build/buildd/linux-3.12.0/net/core/dev.c:5319 
rollback_registered_many+0x219/0x250()
  [  426.965540] Modules linked in: openvswitch vxlan ip_tunnel(F) gre(F) 
libcrc32c(F) veth(F) hid_generic usbhid hid xt_conntrack(F) ipt_REJECT(F) 
xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) ip6table_filter(F) ip6_tables(F) 
iptable_filter(F) ebtable_nat(F) ebtables(F) dm_crypt(F) ipt_MASQUERADE(F) 
iptable_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) nf_nat_ipv4(F) nf_nat(F) 
nf_conntrack(F) ip_tables(F) x_tables(F) bridge(F) stp(F) llc(F) joydev(F) 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel(F) kvm(F) 
crct10dif_pclmul(F) crc32_pclmul(F) ghash_clmulni_intel(F) aesni_intel(F) 
aes_x86_64(F) lrw(F) gf128mul(F) glue_helper(F) ablk_helper(F) cryptd(F) 
arc4(F) parport_pc(F) iwldvm ppdev(F) snd_hda_codec_hdmi mac80211 
snd_hda_codec_realtek uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core videodev btusb microcode(F) snd_hda_intel snd_hda_codec iwlwifi 
snd_hwdep(F) psmouse(F) thinkpad_acpi snd_pcm(F) serio_raw(F) nvram(F) cfg80211 
snd_seq_midi(F) lpc_ich snd_seq_midi_event(F) snd_rawmidi(F) bnep snd_seq(F) 
rfcomm snd_page_alloc(F) snd_seq_device(F) snd_timer(F) bluetooth snd(F) 
soundcore(F) tpm_tis mac_hid mei_me mei lp(F) parport(F) nls_iso8859_1(F) i915 
i2c_algo_bit drm_kms_helper drm sdhci_pci ahci(F) libahci(F) sdhci e1000e(F) 
ptp(F) pps_core(F) wmi video(F) [last unloaded: ip_tunnel]
  [  426.965609] CPU: 2 PID: 16575 Comm: ip Tainted: GF   W
3.12.0-2-generic #7-Ubuntu
  [  426.965610] Hardware name: LENOVO 2324CTO/2324CTO, BIOS G2ET91WW (2.51 ) 
01/14/2013
  [  426.965612]  0009 8803ba8bd8e8 8170feef 

  [  426.965616]  8803ba8bd920 8106430d 8803d0dd9000 
8803ba8bd918
  [  426.965618]  8803ba8bd988  81cd5f80 
8803ba8bd930
  [  426.965621] Call Trace:
  [  426.965627]  [8170feef] dump_stack+0x45/0x56
  [  426.965631]  [8106430d] warn_slowpath_common+0x7d/0xa0
  [  426.965634]  [810643ea] warn_slowpath_null+0x1a/0x20
  [  426.965637]  [81612d09] rollback_registered_many+0x219/0x250
  [  426.965640]  [81612d97] unregister_netdevice_many+0x17/0x70
  [  426.965644]  [81626f0f] rtnl_dellink+0xbf/0x130
  [  426.965647]  [81624259] rtnetlink_rcv_msg+0x99/0x260
  [  426.965651]  [8119b068] ? __kmalloc_node_track_caller+0x58/0x1e0
  [  426.965654]  [81197f11] ? kmem_cache_alloc+0x31/0x140
  [  426.965658]  [81606bae] ? __alloc_skb+0x7e/0x2b0
  [  426.965660]  [816241c0] ? rtnetlink_rcv+0x30/0x30
  [  426.965664]  [81642749] netlink_rcv_skb+0xa9/0xc0
  [  426.965667]  [816241b8] rtnetlink_rcv+0x28/0x30
  [  426.965670]  [81641d9d] netlink_unicast+0xdd/0x190
  [  426.965673]  [8137e06d] ? memcpy_fromiovec+0x4d/0x90
  [  426.965676]  [8164214f] netlink_sendmsg+0x2ff/0x740
  [  426.965679]  [815fe63b] sock_sendmsg+0x8b/0xc0
  [  426.965683]  [8117b278] ? page_add_new_anon_rmap+0xd8/0x170
  [  426.965686]  [815fe32e] ? move_addr_to_kernel.part.14+0x1e/0x60
  [  426.965689]  [815feef1] ? move_addr_to_kernel+0x21/0x30
  [  426.965692]  [815feeb8] ___sys_sendmsg+0x3b8/0x3d0
  [  426.965695]  [8117112c] ? handle_mm_fault+0x36c/0x750
  [  426.965699]  [8171c0bc] ? __do_page_fault+0x21c/0x560
  [  426.965704]  [8110aeac] ? acct_account_cputime+0x1c/0x20
  [  426.965707]  [8109b86b] ? account_user_time+0x8b/0xa0
  [  426.965710]  [815ff5c2] __sys_sendmsg+0x42/0x80
  [  426.965713]  [815ff612] SyS_sendmsg+0x12/0x20
  [  426.965716]  [81720d3f] tracesys+0xe1/0xe6
  [  426.965718] ---[ end trace 82879f5d4f934596 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.12.0.2.4
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jamespage   2869 F pulseaudio
  Date: Wed Nov 13 21:26:50 2013
  EcryptfsInUse: Yes
 

Re: [Kernel-packages] [Bug 1005134] Re: [Compaq Presario CQ60-215DX Notebook PC] 12.04 hangs on shutdown when using 3.2 kernel

2013-12-06 Thread Stephen Helden
ok, I'll do it on Sunday


On Wed, Dec 4, 2013 at 9:52 PM, Christopher M. Penalver 
christopher.m.penal...@gmail.com wrote:

 Stephen Helden, as per
 http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063lc=encc=usdlc=ensw_lang=product=3860070#N870an
  update is available for your BIOS (F.54 A). If you update to this
 following https://help.ubuntu.com/community/BiosUpdate , does it change
 anything? If it doesn't, could you please both specify what happened, and
 provide the output of the following terminal command:
 sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

 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.

 ** Summary changed:

 - 12.04 hangs on shutdown when using 3.2 kernal
 + [Compaq Presario CQ60-215DX Notebook PC] 12.04 hangs on shutdown when
 using 3.2 kernel

 ** Tags removed: needs-full-computer-model
 ** Tags added: bios-outdated-f.54a

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1005134

 Title:
   [Compaq Presario CQ60-215DX Notebook PC] 12.04 hangs on shutdown
   when using 3.2 kernel

 Status in “linux” package in Ubuntu:
   Incomplete

 Bug description:
   I've been having a problem, as my system was hanging when I selected
   Shut-Down option from the Ubuntu dropdown menu.  This problem was
   remediated when the Update manager patched the kernal to a release
   3.4. Now, I was presented  with the latest Update Manager patch and
   when I complied, my Ubuntu image file was impacted, and now my kernal
   release is back to 3.2.0-24-generic-pae, and, of course, I'm hanging
   when I select the shut-down option from the Ubuntu dropdown menu.

   WORKAROUND: sudo shutdown

   ProblemType: Bug
   DistroRelease: Ubuntu 12.04
   Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39
   ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
   Uname: Linux 3.2.0-24-generic-pae i686
   NonfreeKernelModules: nvidia
   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
   ApportVersion: 2.0.1-0ubuntu7
   Architecture: i386
   ArecordDevices:
 List of CAPTURE Hardware Devices 
card 0: NVidia [HDA NVidia], device 0: CONEXANT Analog [CONEXANT Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  shelden2442 F pulseaudio
   Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xc000 irq 20'
  Mixer name : 'Nvidia MCP77/78 HDMI'
  Components : 'HDA:14f15051,103c360a,0010
 HDA:10de0002,10de0101,0010'
  Controls  : 20
  Simple ctrls  : 11
   Date: Sun May 27 07:02:59 2012
   HibernationDevice: RESUME=UUID=2c028562-fdac-4b06-9fc4-f060ecda4675
   InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386
 (20120423)
   MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
   ProcEnviron:
TERM=emacs
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
   ProcFB: 0 VESA VGA
   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae
 root=UUID=1ce261e8-0885-4896-bc5c-a173e2218b82 ro quiet splash vt.handoff=7
   RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic-pae N/A
linux-backports-modules-3.2.0-24-generic-pae  N/A
linux-firmware1.79
   SourcePackage: linux
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 02/17/2009
   dmi.bios.vendor: Hewlett-Packard
   dmi.bios.version: F.35
   dmi.board.name: 303C
   dmi.board.vendor: Wistron
   dmi.board.version: 08.49
   dmi.chassis.type: 10
   dmi.chassis.vendor: Wistron
   dmi.chassis.version: N/A
   dmi.modalias:
 dmi:bvnHewlett-Packard:bvrF.35:bd02/17/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.35:rvnWistron:rn303C:rvr08.49:cvnWistron:ct10:cvrN/A:
   dmi.product.name: Compaq Presario CQ60 Notebook PC
   dmi.product.version: F.35
   dmi.sys.vendor: Hewlett-Packard

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005134/+subscriptions


-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1005134

Title:
  [Compaq Presario CQ60-215DX Notebook PC] 12.04 hangs on shutdown
  when using 3.2 kernel

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I've been having a problem, as my system was hanging when I selected
  Shut-Down option from the Ubuntu dropdown menu.  This problem was
  remediated when the Update manager patched the kernal to a release
  3.4. Now, I was presented  with the latest Update Manager patch and
  when I complied, my 

[Kernel-packages] [Bug 1258313] Re: Kernel crashes with error in fs/buffer.c:1268

2013-12-06 Thread Joseph Salisbury
Can you reproduce this easily?  If so, can you give the v3.11.10 kernel a try:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10-saucy/

** Changed in: linux (Ubuntu)
   Importance: Undecided = High

** Tags added: kernel-da-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258313

Title:
  Kernel crashes with error in fs/buffer.c:1268

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade to 3.11.0-15, the kernel crashes with the following
  message:

  Dec  5 22:05:02 excelsior kernel: [22046.717322] kernel BUG at 
/build/buildd/linux-3.11.0/fs/buffer.c:1268!
  Dec  5 22:05:02 excelsior kernel: [22046.717376] invalid opcode:  [#1] 
SMP 
  Dec  5 22:05:02 excelsior kernel: [22046.717413] Modules linked in: 
parport_pc ppdev rfcomm bnep binfmt_misc dm_crypt x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crc32_pclmul aesni_intel aes_i586 xts 
lrw gf128mul ablk_helper cryptd joydev snd_hda_codec_hdmi snd_hda_codec_idt 
dell_wmi sparse_keymap snd_hda_intel uvcvideo snd_hda_codec videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep videodev rts5139(C) ath3k btusb 
snd_pcm bluetooth dell_laptop dcdbas snd_page_alloc snd_seq_midi 
snd_seq_midi_event arc4 snd_rawmidi microcode ath9k ath9k_common psmouse 
serio_raw ath9k_hw ath snd_seq mac80211 lpc_ich snd_seq_device snd_timer 
cfg80211 intel_rst snd mac_hid mei_me mei soundcore lp parport hid_generic 
usbhid hid radeon i915 ttm ahci i2c_algo_bit drm_kms_helper libahci alx drm 
mdio wmi video [last unloaded: ipmi_msghandler]
  Dec  5 22:05:02 excelsior kernel: [22046.718054] CPU: 2 PID: 9814 Comm: 
firefox Tainted: G C   3.11.0-15-generic #22-Ubuntu
  Dec  5 22:05:02 excelsior kernel: [22046.718120] Hardware name: Dell Inc. 
Inspiron 5423/0YW78J, BIOS A06 09/17/2012
  Dec  5 22:05:02 excelsior kernel: [22046.718176] task: e9e1b380 ti: e975c000 
task.ti: e975c000
  Dec  5 22:05:02 excelsior kernel: [22046.718217] EIP: 0060:[c1625279] 
EFLAGS: 00210046 CPU: 2
  Dec  5 22:05:02 excelsior kernel: [22046.718263] EIP is at 
check_irqs_on.part.11+0x3/0x5
  Dec  5 22:05:02 excelsior kernel: [22046.718300] EAX: 00200096 EBX:  
ECX:  EDX: 04400091
  Dec  5 22:05:02 excelsior kernel: [22046.718345] ESI: f68f0400 EDI: 0010 
EBP: e975d894 ESP: e975d894
  Dec  5 22:05:02 excelsior kernel: [22046.718394]  DS: 007b ES: 007b FS: 00d8 
GS: 00e0 SS: 0068
  Dec  5 22:05:02 excelsior kernel: [22046.718434] CR0: 80050033 CR2: b6dbb4a0 
CR3: 01a56000 CR4: 001407f0
  Dec  5 22:05:02 excelsior kernel: [22046.718481] Stack:
  Dec  5 22:05:02 excelsior kernel: [22046.718498]  e975d8d0 c1194e25  
04400091 f6125e00 f7bd7648 a33ea876 e975d8f4
  Dec  5 22:05:02 excelsior kernel: [22046.718569]  c1084db6 e9e1b3b4 e9e1b3b4 
ee2a2780  1000 0010 e975d93c
  Dec  5 22:05:02 excelsior kernel: [22046.718634]  c119687e 1000  
1406 3c39 f6125e00 f6125e00 01406a33
  Dec  5 22:05:02 excelsior kernel: [22046.718700] Call Trace:
  Dec  5 22:05:02 excelsior kernel: [22046.718726]  [c1194e25] 
__find_get_block+0x1e5/0x1f0
  Dec  5 22:05:02 excelsior kernel: [22046.718770]  [c1084db6] ? 
update_curr+0xa6/0x1d0
  Dec  5 22:05:02 excelsior kernel: [22046.718809]  [c119687e] 
__getblk+0x2e/0x320
  Dec  5 22:05:02 excelsior kernel: [22046.718845]  [c12f1ca8] ? 
cpumask_next_and+0x28/0x40
  Dec  5 22:05:02 excelsior kernel: [22046.718885]  [c1088fc5] ? 
update_sd_lb_stats+0xc5/0x450
  Dec  5 22:05:02 excelsior kernel: [22046.718929]  [c11ede6e] 
__ext4_get_inode_loc+0xde/0x410
  Dec  5 22:05:02 excelsior kernel: [22046.718973]  [c1237900] ? 
start_this_handle+0x80/0x4e0
  Dec  5 22:05:02 excelsior kernel: [22046.719015]  [c11effe9] 
ext4_get_inode_loc+0x19/0x20
  Dec  5 22:05:02 excelsior kernel: [22046.719055]  [c11f17ce] 
ext4_reserve_inode_write+0x1e/0x80
  Dec  5 22:05:02 excelsior kernel: [22046.719099]  [c1237f76] ? 
jbd2__journal_start+0xb6/0x1a0
  Dec  5 22:05:02 excelsior kernel: [22046.719143]  [c11f186e] 
ext4_mark_inode_dirty+0x3e/0x1b0
  Dec  5 22:05:02 excelsior kernel: [22046.719188]  [c1219359] ? 
__ext4_journal_start_sb+0x59/0xc0
  Dec  5 22:05:02 excelsior kernel: [22046.719233]  [c11f4b20] ? 
ext4_dirty_inode+0x40/0x60
  Dec  5 22:05:02 excelsior kernel: [22046.719274]  [c11f4b20] 
ext4_dirty_inode+0x40/0x60
  Dec  5 22:05:02 excelsior kernel: [22046.719312]  [c118f341] 
__mark_inode_dirty+0xf1/0x290
  Dec  5 22:05:02 excelsior kernel: [22046.719353]  [c1180fd0] 
update_time+0x80/0xc0
  Dec  5 22:05:02 excelsior kernel: [22046.719392]  [c118118b] 
file_update_time+0x6b/0xa0
  Dec  5 22:05:02 excelsior kernel: [22046.719436]  [c1119928] 
__generic_file_aio_write+0x218/0x460
  Dec  5 22:05:02 excelsior kernel: [22046.719483]  [c104c036] ? 
kmap_atomic_prot+0x46/0x100
  Dec  5 22:05:02 excelsior kernel: [22046.719526]  [c1119bc4] 

[Kernel-packages] [Bug 1229591] Re: display brightness keys don't generate evdev events after saucy upgrade

2013-12-06 Thread Chris Stratford
Rather bizarrely, I can't get it to work with any of the mainline
kernels.  Even going back to 3.9.11-030911-generic which should work
(since the real 3.10.0-6 works fine) I get no brightness control.

I've also noticed the screen never seems to get turned off.  After a
while it will blank the screen, but the backlight is still on.  This may
be completely unconnected, but thought I'd mention it here just in case
it may be relevant.

-- 
You 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 1258313] Re: Kernel crashes with error in fs/buffer.c:1268

2013-12-06 Thread Joseph Salisbury
Also, does the bug go away if you boot back into v3.11.0-14?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258313

Title:
  Kernel crashes with error in fs/buffer.c:1268

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade to 3.11.0-15, the kernel crashes with the following
  message:

  Dec  5 22:05:02 excelsior kernel: [22046.717322] kernel BUG at 
/build/buildd/linux-3.11.0/fs/buffer.c:1268!
  Dec  5 22:05:02 excelsior kernel: [22046.717376] invalid opcode:  [#1] 
SMP 
  Dec  5 22:05:02 excelsior kernel: [22046.717413] Modules linked in: 
parport_pc ppdev rfcomm bnep binfmt_misc dm_crypt x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crc32_pclmul aesni_intel aes_i586 xts 
lrw gf128mul ablk_helper cryptd joydev snd_hda_codec_hdmi snd_hda_codec_idt 
dell_wmi sparse_keymap snd_hda_intel uvcvideo snd_hda_codec videobuf2_vmalloc 
videobuf2_memops videobuf2_core snd_hwdep videodev rts5139(C) ath3k btusb 
snd_pcm bluetooth dell_laptop dcdbas snd_page_alloc snd_seq_midi 
snd_seq_midi_event arc4 snd_rawmidi microcode ath9k ath9k_common psmouse 
serio_raw ath9k_hw ath snd_seq mac80211 lpc_ich snd_seq_device snd_timer 
cfg80211 intel_rst snd mac_hid mei_me mei soundcore lp parport hid_generic 
usbhid hid radeon i915 ttm ahci i2c_algo_bit drm_kms_helper libahci alx drm 
mdio wmi video [last unloaded: ipmi_msghandler]
  Dec  5 22:05:02 excelsior kernel: [22046.718054] CPU: 2 PID: 9814 Comm: 
firefox Tainted: G C   3.11.0-15-generic #22-Ubuntu
  Dec  5 22:05:02 excelsior kernel: [22046.718120] Hardware name: Dell Inc. 
Inspiron 5423/0YW78J, BIOS A06 09/17/2012
  Dec  5 22:05:02 excelsior kernel: [22046.718176] task: e9e1b380 ti: e975c000 
task.ti: e975c000
  Dec  5 22:05:02 excelsior kernel: [22046.718217] EIP: 0060:[c1625279] 
EFLAGS: 00210046 CPU: 2
  Dec  5 22:05:02 excelsior kernel: [22046.718263] EIP is at 
check_irqs_on.part.11+0x3/0x5
  Dec  5 22:05:02 excelsior kernel: [22046.718300] EAX: 00200096 EBX:  
ECX:  EDX: 04400091
  Dec  5 22:05:02 excelsior kernel: [22046.718345] ESI: f68f0400 EDI: 0010 
EBP: e975d894 ESP: e975d894
  Dec  5 22:05:02 excelsior kernel: [22046.718394]  DS: 007b ES: 007b FS: 00d8 
GS: 00e0 SS: 0068
  Dec  5 22:05:02 excelsior kernel: [22046.718434] CR0: 80050033 CR2: b6dbb4a0 
CR3: 01a56000 CR4: 001407f0
  Dec  5 22:05:02 excelsior kernel: [22046.718481] Stack:
  Dec  5 22:05:02 excelsior kernel: [22046.718498]  e975d8d0 c1194e25  
04400091 f6125e00 f7bd7648 a33ea876 e975d8f4
  Dec  5 22:05:02 excelsior kernel: [22046.718569]  c1084db6 e9e1b3b4 e9e1b3b4 
ee2a2780  1000 0010 e975d93c
  Dec  5 22:05:02 excelsior kernel: [22046.718634]  c119687e 1000  
1406 3c39 f6125e00 f6125e00 01406a33
  Dec  5 22:05:02 excelsior kernel: [22046.718700] Call Trace:
  Dec  5 22:05:02 excelsior kernel: [22046.718726]  [c1194e25] 
__find_get_block+0x1e5/0x1f0
  Dec  5 22:05:02 excelsior kernel: [22046.718770]  [c1084db6] ? 
update_curr+0xa6/0x1d0
  Dec  5 22:05:02 excelsior kernel: [22046.718809]  [c119687e] 
__getblk+0x2e/0x320
  Dec  5 22:05:02 excelsior kernel: [22046.718845]  [c12f1ca8] ? 
cpumask_next_and+0x28/0x40
  Dec  5 22:05:02 excelsior kernel: [22046.718885]  [c1088fc5] ? 
update_sd_lb_stats+0xc5/0x450
  Dec  5 22:05:02 excelsior kernel: [22046.718929]  [c11ede6e] 
__ext4_get_inode_loc+0xde/0x410
  Dec  5 22:05:02 excelsior kernel: [22046.718973]  [c1237900] ? 
start_this_handle+0x80/0x4e0
  Dec  5 22:05:02 excelsior kernel: [22046.719015]  [c11effe9] 
ext4_get_inode_loc+0x19/0x20
  Dec  5 22:05:02 excelsior kernel: [22046.719055]  [c11f17ce] 
ext4_reserve_inode_write+0x1e/0x80
  Dec  5 22:05:02 excelsior kernel: [22046.719099]  [c1237f76] ? 
jbd2__journal_start+0xb6/0x1a0
  Dec  5 22:05:02 excelsior kernel: [22046.719143]  [c11f186e] 
ext4_mark_inode_dirty+0x3e/0x1b0
  Dec  5 22:05:02 excelsior kernel: [22046.719188]  [c1219359] ? 
__ext4_journal_start_sb+0x59/0xc0
  Dec  5 22:05:02 excelsior kernel: [22046.719233]  [c11f4b20] ? 
ext4_dirty_inode+0x40/0x60
  Dec  5 22:05:02 excelsior kernel: [22046.719274]  [c11f4b20] 
ext4_dirty_inode+0x40/0x60
  Dec  5 22:05:02 excelsior kernel: [22046.719312]  [c118f341] 
__mark_inode_dirty+0xf1/0x290
  Dec  5 22:05:02 excelsior kernel: [22046.719353]  [c1180fd0] 
update_time+0x80/0xc0
  Dec  5 22:05:02 excelsior kernel: [22046.719392]  [c118118b] 
file_update_time+0x6b/0xa0
  Dec  5 22:05:02 excelsior kernel: [22046.719436]  [c1119928] 
__generic_file_aio_write+0x218/0x460
  Dec  5 22:05:02 excelsior kernel: [22046.719483]  [c104c036] ? 
kmap_atomic_prot+0x46/0x100
  Dec  5 22:05:02 excelsior kernel: [22046.719526]  [c1119bc4] 
generic_file_aio_write+0x54/0xc0
  Dec  5 22:05:02 excelsior kernel: [22046.719570]  [c11e9c90] 
ext4_file_write+0xd0/0x480
  Dec  5 22:05:02 excelsior kernel: [22046.719618]  [c100f9c4] ? 

[Kernel-packages] [Bug 1172065] Re: 12.04.2 incorrect file name signed efi amd6.deb

2013-12-06 Thread Ralic
Fair enough.
I came across this while troubleshooting a problem that I later discovered to 
be reported by bug 
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1252255 and 
rather than repeat what I have found over there, I earlier posted a link there 
back to this bug.

Hopefully what I have found proves useful to resolving that error for
others, so I'll leave it at that.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1172065

Title:
  12.04.2 incorrect file name signed efi amd6.deb

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  download ISO has wrong nameamd6 should be amd64.
  In /pool/main/g/grub2-signed

  grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd6.deb
  seems like it should be 
  grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd64.deb

  See Also 
  http://ubuntuforums.org/showthread.php?t=2138041

  Just downloaded the ISO and it still has wrong name.
  Compared to Raring and Raring has correct name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172065/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1220185] Re: CVE-2013-2888

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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/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:
  Invalid
Status in “linux” source package in Lucid:
  Fix Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” 

[Kernel-packages] [Bug 1143800] Re: CVE-2013-0343

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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:
  Invalid
Status in “linux” source package in Lucid:
  Fix Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  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:
  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 “linux-ti-omap4” source package in Raring:
  Fix Released
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 in “linux-lts-backport-natty” source package in Saucy:
  Invalid
Status in “linux-lts-backport-oneiric” source package in Saucy:
  Invalid
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” 

[Kernel-packages] [Bug 1099487] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000

2013-12-06 Thread bibon
On a LENOVO IdeaPad U330P

# lspci|grep Net
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1099487

Title:
  iwlwifi: Microcode SW error detected.  Restarting 0x200

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This appears to be related to the older bug #200509 on my Lenovo X230.

  Since Jan 4th, I'm seeing errors like:

  Jan  8 14:33:32 lystena kernel: [10462.742627] iwlwifi :03:00.0:
  Microcode SW error detected.  Restarting 0x200.

  Running:

  $ sudo modprobe -r iwlwifi; sudo modprobe iwlwifi

  ...fixes the issue. Attached appears to be one of the first instances
  of the issue.

  Kernel upgrade I can see in my apt logs:

  Start-Date: 2012-12-01  07:43:21
  Commandline: aptdaemon role='role-commit-packages' sender=':1.1567'
  Install: linux-image-extra-3.5.0-19-generic:amd64 (3.5.0-19.30), 
linux-image-3.5.0-19-generic:amd64 (3.5.0-19.30)
  Upgrade: perl:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), perl-base:amd64 
(5.14.2-13, 5.14.2-13ubuntu0.1), libboost-python1.49.0:amd64 
(1.49.0-3.1ubuntu1, 1.49.0-3.1ubuntu1.1), perl-modules:amd64 (5.14.2-13, 
5.14.2-13ubuntu0.1), libboost-date-time1.49.0:amd64 (1.49.0-3.1ubuntu1, 
1.49.0-3.1ubuntu1.1), linux-image-generic:amd64 (3.5.0.18.21, 3.5.0.19.22), 
libperl5.14:amd64 (5.14.2-13, 5.14.2-13ubuntu0.1), linux-libc-dev:amd64 
(3.5.0-18.29, 3.5.0-19.30)

  -21 kernel was installed on the 18th of December.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099487/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1220190] Re: CVE-2013-2889

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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:
  Invalid
Status in “linux” source package in Lucid:
  Fix Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in 

[Kernel-packages] [Bug 1220196] Re: CVE-2013-2892

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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/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:
  Invalid
Status in “linux” source package in Lucid:
  Fix Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” 

[Kernel-packages] [Bug 1220198] Re: CVE-2013-2893

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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:
  Invalid
Status in “linux” source package in Lucid:
  Fix Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in 

[Kernel-packages] [Bug 1220200] Re: CVE-2013-2895

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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:
  Invalid
Status in “linux” source package in Lucid:
  Invalid
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Invalid
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in Trusty:
  

[Kernel-packages] [Bug 1220202] Re: CVE-2013-2896

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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/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:
  Invalid
Status in “linux” source package in Lucid:
  Invalid
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Invalid
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source 

[Kernel-packages] [Bug 1220209] Re: CVE-2013-2899

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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/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:
  Invalid
Status in “linux” source package in Lucid:
  Invalid
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Invalid
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source 

[Kernel-packages] [Bug 1209124] Re: Support for Intel 7260 bluetooth [8087:07dc]

2013-12-06 Thread kanor
I have an ux301la laptop with this wireless chip and the bluetooth is
not working. Could you help me debugging it? So far I found errors in
dmesg:

kanor@kestrel:~$ dmesg | grep -i blue
[1.718506] Bluetooth: Core ver 2.16
[1.718539] Bluetooth: HCI device and connection manager initialized
[1.718546] Bluetooth: HCI socket layer initialized
[1.718548] Bluetooth: L2CAP socket layer initialized
[1.718556] Bluetooth: SCO socket layer initialized
[1.734118] Bluetooth: hci0: read Intel version: 370710018002030d00
[1.738944] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[3.72] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[3.75] Bluetooth: BNEP filters: protocol multicast
[3.788892] Bluetooth: BNEP socket layer initialized
[3.789654] Bluetooth: RFCOMM TTY layer initialized
[3.789664] Bluetooth: RFCOMM socket layer initialized
[3.789665] Bluetooth: RFCOMM ver 1.11
[3.850669] Bluetooth: hci0 sending Intel patch command (0xfc2f) failed (-19)
[5.854659] Bluetooth: hci0 command 0xfc11 tx timeout
[   13.860301] Bluetooth: hci0 exiting Intel manufacturer mode failed (-110)


kernel is 
kanor@kestrel:~$ uname -a
Linux kestrel 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 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/1209124

Title:
  Support for Intel 7260 bluetooth [8087:07dc]

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Some 7260 modules are found in the newly released systems. It needs
  external firmware to work. Support for this module can be found in
  3.10 and need to be backported to 3.5 and 3.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209124/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1220205] Re: CVE-2013-2897

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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:
  Invalid
Status in “linux” source package in Lucid:
  Fix Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Invalid
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” source package in Saucy:
  Invalid
Status in “linux-fsl-imx51” source package in Saucy:
  Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in 

[Kernel-packages] [Bug 1258631] [NEW] instances fails to register GPT partition entries on virtio devices

2013-12-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When booting via KVM and using the VirtIO interface, GPT partition
entries are not shown properly.

ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print
Model: Virtio Block Device (virtblk)
Disk /dev/vda: 10.7GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   EndSize File system Name
  Flags
127 1049kB  2097kB  1049kB   BIOS boot partition  
bios_grub
128 2097kB  89.1MB  87.0MB  fat32   EFI System  
boot
1  89.1MB  10.7GB  10.6GB   ext4 Linux filesystem

Booting with -hda disk.img
[2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5
[2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[2.644685]  sda: sda1 sda127 sda128
[2.664314] sd 0:0:0:0: [sda] Attached SCSI disk

Booting with -drive if=virtio,file=disk.img or -drive 
if=scsi,file=disk.img:
[2.411933] brd: module loaded
[2.422616] loop: module loaded
[2.442178]  vda: vda1
[2.49] scsi0 : ata_piix
[2.456868] scsi1 : ata_piix

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu6
ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
Uname: Linux 3.12.0-5-generic x86_64
ApportVersion: 2.12.7-0ubuntu1
Architecture: amd64
Date: Fri Dec  6 18:49:57 2013
Ec2AMI: ami-0632
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0548
Ec2Ramdisk: ari-0548
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic 
root=LABEL=cloudimg-rootfs console=ttyS0
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr:
dmi.product.name: OpenStack Nova
dmi.product.version: 2013.1.3
dmi.sys.vendor: OpenStack Foundation

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ec2-images trusty
-- 
instances fails to register GPT partition entries on virtio devices
https://bugs.launchpad.net/bugs/1258631
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-meta in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258332] Re: Please backport patches for MXSLDR

2013-12-06 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided = Medium

** Tags added: kernel-da-key precise

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258332

Title:
  Please backport patches for MXSLDR

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The Freescale i.MX23 and i.MX28 devices need additional quirks in the
  kernel's HID layer to operate correctly. Without these quirks, these
  devices will suffer from software crash of their BootROM and not
  operate correctly. The MXSLDR [1] tool will not work correctly without
  the quirks in place either. The patches for this issue were accepted
  into linux-stable long time ago, but are not present in 12.04.3
  version of Ubuntu. Please backport [2], [3], [4] to resolve this
  issue.

  Thank you!

  [1] http://git.denx.de/?p=mxsldr.git;a=summary
  [2] 
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=23408f95fa92483527de3206ebeb55c37e0f679c
  [3] 
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=2843b673d03421e0e73cf061820d1db328f7c8eb
  [4] 
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=436136cec650d661eb662fcb508a99878606d050

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258332/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258631] Re: instances fails to register GPT partition entries on virtio devices

2013-12-06 Thread Ben Howard
** Package changed: systemd (Ubuntu) = linux-meta (Ubuntu)

-- 
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/1258631

Title:
  instances fails to register GPT partition entries on virtio devices

Status in “linux” package in Ubuntu:
  New

Bug description:
  When booting via KVM and using the VirtIO interface, GPT partition
  entries are not shown properly.

  ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print
  Model: Virtio Block Device (virtblk)
  Disk /dev/vda: 10.7GB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt

  Number  Start   EndSize File system Name  
Flags
  127 1049kB  2097kB  1049kB   BIOS boot partition  
bios_grub
  128 2097kB  89.1MB  87.0MB  fat32   EFI System
  boot
  1  89.1MB  10.7GB  10.6GB   ext4 Linux filesystem

  Booting with -hda disk.img
  [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5
  [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [2.644685]  sda: sda1 sda127 sda128
  [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk

  Booting with -drive if=virtio,file=disk.img or -drive 
if=scsi,file=disk.img:
  [2.411933] brd: module loaded
  [2.422616] loop: module loaded
  [2.442178]  vda: vda1
  [2.49] scsi0 : ata_piix
  [2.456868] scsi1 : ata_piix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Fri Dec  6 18:49:57 2013
  Ec2AMI: ami-0632
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0548
  Ec2Ramdisk: ari-0548
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic 
root=LABEL=cloudimg-rootfs console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.1.3
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258495] Re: backlight too bright, can't dim it much

2013-12-06 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.12 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.13-rc3-trusty/


** Changed in: linux (Ubuntu)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258495

Title:
  backlight too bright, can't dim it much

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Screen is far too bright, dims only slightly with hotkeys, brightness
  control applet ineffective. Tried more than half a dozen solutions
  (incl. editing the grub which used to work fine with Ubuntu 12.04) but
  none of them worked.

  thindi@thindi-AOA110:~$ ls /sys/class/backlight  backlight
  thindi@thindi-AOA110:~$ grep -r . /proc/acpi  acpi
  grep: /proc/acpi/event: Permission denied
  thindi@thindi-AOA110:~$ sudo acpidump -o acpidump.txt
  thindi@thindi-AOA110:~$ acpixtract acpidump.txt
  Acpi table [DSDT] -  24038 bytes written to DSDT.dat
  Acpi table [SSDT] -   1220 bytes written to SSDT.dat
  thindi@thindi-AOA110:~$ iasl -d DSDT.dat

  Intel ACPI Component Architecture
  AML Disassembler version 20100528 [Dec 19 2012]
  Copyright (c) 2000 - 2010 Intel Corporation
  Supports ACPI Specification Revision 4.0a

  Loading Acpi table from file DSDT.dat
  Acpi table [DSDT] successfully installed and loaded
  Pass 1 parse of [DSDT]
  Pass 2 parse of [DSDT]
  Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
  
...
  Parsing completed
  Disassembly completed, written to DSDT.dsl
  thindi@thindi-AOA110:~$ sudo fwts  fwts
  Test: Gather kernel system information. 
Gather kernel signature.1 info only 
 
Gather kernel system information.   1 info only 
 
Gather kernel boot command line.1 info only 
 
Gather ACPI driver version. 1 info only 
 
  Test: Gather BIOS DMI information.  
Gather BIOS DMI information 1 info only 
 
  Test: Scan kernel log for Oopses.   
Kernel log oops check.  2 passed
 
  Test: Scan kernel log for errors and warnings.  
Kernel log error check. 1 passed
 
  Test: MTRR validation.  
Validate the kernel MTRR IOMEM setup.   1 failed
 
Validate the MTRR setup across all processors.  1 passed
 
Check for AMD MtrrFixDramModEn being cleared by the ..  1 skipped   
 
  Test: General ACPI information check.   
Determine Kernel ACPI version.  1 info only 
 
Determine machine's ACPI version.   1 info only 
 
Determine AML compiler. 1 info only 
 
  Test: Ubuntu UEFI secure boot test. 
   Test aborted..   
 
  Test: Check for UEFI Compatibility Support Module.  
Check for UEFI Compatibility Support Module.1 info only 
 
  Test: Checks firmware has set PCI Express MaxReadReq to a higher value on.. 
Check firmware settings MaxReadReq for PCI Express d..  1 failed
 
  Test: Check PCI host bridge configuration using _CRS.   
Check PCI host bridge configuration using _CRS. 1 skipped   
 
  Test: PCIe ASPM check.  
PCIe ASPM ACPI test.
 
PCIe ASPM registers test.   3 passed, 10 
warnings
  Test: HPET configuration test. 

[Kernel-packages] [Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa

2013-12-06 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
507ffe4f3840ac24890a8123c702cf1b7fe4d33c

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1251816

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/1251816

Title:
  Boot failure with saucy kernel 3.11 probing eisa

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have an old laptop that I upgraded to saucy and it will only boot the 
earlier 3.8 kernel.  The 3.11, 3 versions tried including the proposed, hangs 
on Platform eisa.0: Probing EISA bus 0 
   
  I also tried the 3.12.0-999 kernel at 
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ and it 
hangs as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-generic 3.11.0.14.15
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cp 1926 F pulseaudio
  CRDA:
   country CO:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 23), DFS
(5735 - 5835 @ 40), (3, 30)
  CurrentDmesg:
   [  114.938323] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
   [  115.026165] XFS (sdb6): Mounting Filesystem
   [  119.437397] XFS (sdb6): Ending clean mount
   [  119.878267] EXT4-fs (sdb1): mounted filesystem with ordered data mode. 
Opts: (null)
  Date: Fri Nov 15 23:18:27 2013
  HibernationDevice: RESUME=UUID=33c5f08a-8efc-4eb2-b6ec-497bb57df899
  Lsusb:
   Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA 
Technology Corp. JM20337 Hi-Speed USB to SATA  PATA Combo Bridge
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: sag168168 Apollo Pro133AX
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=5658ed45-be8e-4c39-b0e3-1944d7a303b0 ro 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to saucy on 2013-11-01 (14 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 10/18/2001
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: 694x686a
  dmi.board.vendor: VIA
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Apollo Pro133AX
  dmi.product.version: 8500V
  dmi.sys.vendor: sag168168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258631] Re: instances fails to register GPT partition entries on virtio devices

2013-12-06 Thread Brad Figg
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258631

Title:
  instances fails to register GPT partition entries on virtio devices

Status in “linux” package in Ubuntu:
  New

Bug description:
  When booting via KVM and using the VirtIO interface, GPT partition
  entries are not shown properly.

  ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print
  Model: Virtio Block Device (virtblk)
  Disk /dev/vda: 10.7GB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt

  Number  Start   EndSize File system Name  
Flags
  127 1049kB  2097kB  1049kB   BIOS boot partition  
bios_grub
  128 2097kB  89.1MB  87.0MB  fat32   EFI System
  boot
  1  89.1MB  10.7GB  10.6GB   ext4 Linux filesystem

  Booting with -hda disk.img
  [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5
  [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [2.644685]  sda: sda1 sda127 sda128
  [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk

  Booting with -drive if=virtio,file=disk.img or -drive 
if=scsi,file=disk.img:
  [2.411933] brd: module loaded
  [2.422616] loop: module loaded
  [2.442178]  vda: vda1
  [2.49] scsi0 : ata_piix
  [2.456868] scsi1 : ata_piix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Fri Dec  6 18:49:57 2013
  Ec2AMI: ami-0632
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0548
  Ec2Ramdisk: ari-0548
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic 
root=LABEL=cloudimg-rootfs console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.1.3
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258631] Re: instances fails to register GPT partition entries on virtio devices

2013-12-06 Thread Joseph Salisbury
Is this issue new in Trusty?  Do you happen to know if this also happens
with the latest mainline kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/

** Changed in: linux (Ubuntu)
   Importance: Undecided = Medium

** Tags added: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258631

Title:
  instances fails to register GPT partition entries on virtio devices

Status in “linux” package in Ubuntu:
  New

Bug description:
  When booting via KVM and using the VirtIO interface, GPT partition
  entries are not shown properly.

  ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print
  Model: Virtio Block Device (virtblk)
  Disk /dev/vda: 10.7GB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt

  Number  Start   EndSize File system Name  
Flags
  127 1049kB  2097kB  1049kB   BIOS boot partition  
bios_grub
  128 2097kB  89.1MB  87.0MB  fat32   EFI System
  boot
  1  89.1MB  10.7GB  10.6GB   ext4 Linux filesystem

  Booting with -hda disk.img
  [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5
  [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [2.644685]  sda: sda1 sda127 sda128
  [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk

  Booting with -drive if=virtio,file=disk.img or -drive 
if=scsi,file=disk.img:
  [2.411933] brd: module loaded
  [2.422616] loop: module loaded
  [2.442178]  vda: vda1
  [2.49] scsi0 : ata_piix
  [2.456868] scsi1 : ata_piix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Fri Dec  6 18:49:57 2013
  Ec2AMI: ami-0632
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0548
  Ec2Ramdisk: ari-0548
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic 
root=LABEL=cloudimg-rootfs console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.1.3
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1252266] Re: Corrupted low memory after resume from suspend after updating to saucy

2013-12-06 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
1e0f7a21b2fffc70f27cc4a454c60321501045b1

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1252266

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/1252266

Title:
  Corrupted low memory after resume from suspend after updating to saucy

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to saucy and Linux 3.11 my Gigabyte 965P-DS3 board no longer 
properly resumes from suspend.
  The desktop still works fine after resume, but the ethernet interface won't 
come up again.
  dmesg after resume warns about corrupted low memory:

  [40560.864036] [ cut here ]
  [40560.864044] WARNING: CPU: 0 PID: 24687 at 
/build/buildd/linux-3.11.0/arch/x86/kernel/check.c:140 
check_for_bios_corruption+0x10f/0x120()
  [40560.864046] Memory corruption detected in low memory
  [40560.864048] Modules linked in: pci_stub vboxpci(OF) vboxnetadp(OF) 
vboxnetflt(OF) vboxdrv(OF) cuse ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) 
nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_conntrack(F) 
nf_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) 
bridge(F) stp(F) llc(F) ip6table_filter(F) ip6_tables(F) iptable_filter(F) 
ip_tables(F) ebtable_nat(F) ebtables(F) x_tables(F) joydev(F) xpad ff_memless 
hid_generic usbhid hid rfcomm bnep bluetooth binfmt_misc(F) kvm_intel(F) kvm(F) 
gpio_ich ppdev(F) ir_lirc_codec lirc_dev ir_sanyo_decoder ir_mce_kbd_decoder 
ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder 
e4000 rtl2832 usb_storage(F) snd_usb_audio snd_usbmidi_lib uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dvb_usb_rtl28xxu 
rtl2830 dvb_usb_v2 dvb_core rc_core snd_hda_codec_realtek snd_hda_intel 
snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) 
snd_seq_midi_event(F) microcode(F) pcspkr serio_raw(F) snd_rawmidi(F) 
snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) lpc_ich soundcore(F) 
nvidia(POF) parport_pc(F) drm mac_hid it87 hwmon_vid coretemp lp(F) parport(F) 
pata_acpi sky2 pata_jmicron ahci(F) libahci(F)
  [40560.864148] CPU: 0 PID: 24687 Comm: kworker/0:1 Tainted: PF   W  O 
3.11.0-13-generic #20-Ubuntu
  [40560.864151] Hardware name: Gigabyte Technology Co., Ltd. 
965P-DS3/965P-DS3, BIOS F14d 12/18/2008
  [40560.864155] Workqueue: events check_corruption
  [40560.864158]  0009 880064be9d30 816e54ba 
880064be9d78
  [40560.864162]  880064be9d68 81061dbd  
8801
  [40560.864166]  81ea73b0 0001 8800 
880064be9dc8
  [40560.864171] Call Trace:
  [40560.864178]  [816e54ba] dump_stack+0x45/0x56
  [40560.864183]  [81061dbd] warn_slowpath_common+0x7d/0xa0
  [40560.864187]  [81061e2c] warn_slowpath_fmt+0x4c/0x50
  [40560.864191]  [8104e5bf] check_for_bios_corruption+0x10f/0x120
  [40560.864195]  [8104e5de] check_corruption+0xe/0x40
  [40560.864200]  [8107d05c] process_one_work+0x17c/0x430
  [40560.864204]  [8107dcac] worker_thread+0x11c/0x3c0
  [40560.864208]  [8107db90] ? manage_workers.isra.24+0x2a0/0x2a0
  [40560.864212]  [810847b0] kthread+0xc0/0xd0
  [40560.864217]  [810846f0] ? kthread_create_on_node+0x120/0x120
  [40560.864221]  [816f51ec] ret_from_fork+0x7c/0xb0
  [40560.864225]  [810846f0] ? kthread_create_on_node+0x120/0x120
  [40560.864228] ---[ end trace a5d0e3f4744a1e9d ]---

  This did not happen with raring/Linux 3.8

  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:  benpicco   3071 F pulseaudio
   /dev/snd/controlC0:  benpicco   3071 F pulseaudio
  Date: Mon Nov 18 14:12:08 2013
  HibernationDevice: RESUME=UUID=81e8d3af-3d5b-4a61-a550-702a919449c5
  InstallationDate: Installed on 2012-02-27 (629 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5b216424-8d68-4640-9d4c-494eb0e00e9d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   

[Kernel-packages] [Bug 1258332] Re: Please backport patches for MXSLDR

2013-12-06 Thread Joseph Salisbury
** 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/1258332

Title:
  Please backport patches for MXSLDR

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  The Freescale i.MX23 and i.MX28 devices need additional quirks in the
  kernel's HID layer to operate correctly. Without these quirks, these
  devices will suffer from software crash of their BootROM and not
  operate correctly. The MXSLDR [1] tool will not work correctly without
  the quirks in place either. The patches for this issue were accepted
  into linux-stable long time ago, but are not present in 12.04.3
  version of Ubuntu. Please backport [2], [3], [4] to resolve this
  issue.

  Thank you!

  [1] http://git.denx.de/?p=mxsldr.git;a=summary
  [2] 
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=23408f95fa92483527de3206ebeb55c37e0f679c
  [3] 
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=2843b673d03421e0e73cf061820d1db328f7c8eb
  [4] 
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=436136cec650d661eb662fcb508a99878606d050

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258332/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

2013-12-06 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
252c3d84ed398b090ac2dace46fc6faa6cfaea99

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 1241769] Re: CVE-2013-4299

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (Ubuntu Quantal)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Invalid
Status in “linux” source package in Lucid:
  Fix Released
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux-armadaxp” source package in Precise:
  Fix Committed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux-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 “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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” 

[Kernel-packages] [Bug 1258631] Status changed to Confirmed

2013-12-06 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258631

Title:
  instances fails to register GPT partition entries on virtio devices

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  When booting via KVM and using the VirtIO interface, GPT partition
  entries are not shown properly.

  ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print
  Model: Virtio Block Device (virtblk)
  Disk /dev/vda: 10.7GB
  Sector size (logical/physical): 512B/512B
  Partition Table: gpt

  Number  Start   EndSize File system Name  
Flags
  127 1049kB  2097kB  1049kB   BIOS boot partition  
bios_grub
  128 2097kB  89.1MB  87.0MB  fat32   EFI System
  boot
  1  89.1MB  10.7GB  10.6GB   ext4 Linux filesystem

  Booting with -hda disk.img
  [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5
  [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [2.644685]  sda: sda1 sda127 sda128
  [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk

  Booting with -drive if=virtio,file=disk.img or -drive 
if=scsi,file=disk.img:
  [2.411933] brd: module loaded
  [2.422616] loop: module loaded
  [2.442178]  vda: vda1
  [2.49] scsi0 : ata_piix
  [2.456868] scsi1 : ata_piix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu6
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  Date: Fri Dec  6 18:49:57 2013
  Ec2AMI: ami-0632
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0548
  Ec2Ramdisk: ari-0548
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic 
root=LABEL=cloudimg-rootfs console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2013.1.3
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa

2013-12-06 Thread Charles Peters II
The kernel has the bug.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1251816

Title:
  Boot failure with saucy kernel 3.11 probing eisa

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have an old laptop that I upgraded to saucy and it will only boot the 
earlier 3.8 kernel.  The 3.11, 3 versions tried including the proposed, hangs 
on Platform eisa.0: Probing EISA bus 0 
   
  I also tried the 3.12.0-999 kernel at 
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ and it 
hangs as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-generic 3.11.0.14.15
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cp 1926 F pulseaudio
  CRDA:
   country CO:
(2402 - 2472 @ 40), (3, 27)
(5170 - 5250 @ 40), (3, 17)
(5250 - 5330 @ 40), (3, 23), DFS
(5735 - 5835 @ 40), (3, 30)
  CurrentDmesg:
   [  114.938323] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
   [  115.026165] XFS (sdb6): Mounting Filesystem
   [  119.437397] XFS (sdb6): Ending clean mount
   [  119.878267] EXT4-fs (sdb1): mounted filesystem with ordered data mode. 
Opts: (null)
  Date: Fri Nov 15 23:18:27 2013
  HibernationDevice: RESUME=UUID=33c5f08a-8efc-4eb2-b6ec-497bb57df899
  Lsusb:
   Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA 
Technology Corp. JM20337 Hi-Speed USB to SATA  PATA Combo Bridge
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: sag168168 Apollo Pro133AX
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=5658ed45-be8e-4c39-b0e3-1944d7a303b0 ro 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to saucy on 2013-11-01 (14 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 10/18/2001
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: 694x686a
  dmi.board.vendor: VIA
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Apollo Pro133AX
  dmi.product.version: 8500V
  dmi.sys.vendor: sag168168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)

2013-12-06 Thread Dave
Problem as of 2013-12-06 Ubuntu 14.04 daily build is still present when trying 
to install on Dell 515 with IDrac6 Enterprise.
http://cdimage.ubuntu.com/ubuntu-server/daily/current/trusty-server-amd64.iso

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1244176

Title:
  Server 13.10 Install Fails with USB Keyboard (Appears to Hang)

Status in “initramfs-tools” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Committed
Status in “initramfs-tools” source package in Saucy:
  Invalid
Status in “linux” source package in Saucy:
  In Progress
Status in “initramfs-tools” source package in Trusty:
  Invalid
Status in “linux” source package in Trusty:
  Fix Committed

Bug description:
  A fresh install of Server 13.10 on old hardware fails when a USB
  keyboard is present. The installation succeeds when a PS/2 keyboard is
  installed.

  The installation appears to hang at the third screen, which is Select
  Language. The screen does not respond to keyboard or mouse events.

  The issue was experienced independently on HP/Compag  dc5850 with
  Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See
  Server 13.10 Install Hangs,
  http://askubuntu.com/questions/364945/server-13-10-install-
  hangs/364949.

  The issue was not present on Server 12.04.3 LTS or 13.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1226497] Re: CVE-2013-4350

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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/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:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source 

[Kernel-packages] [Bug 1258675] [NEW] hardware switch of wireless not working for Centrino Advanced-N 6235

2013-12-06 Thread Martin Konopka
Public bug reported:

I have ubuntu 13.10  64-bit running on a HP ZBook 15. The notebook uses an 
Intel Corporation Centrino Advanced-N 6235 (rev 24) wireless adapter.
 
The wireless networking principally works. The issue is that it is not possible 
to enable or disable it using the hardware button. The only way is the software 
control (clicking on Enable Wi-Fi).

BTW, when I click on Enable Wi-Fi, it indicates the changes status of
the wifi radio by changing the colour of the light on the hardware
button. (This is the correct and expected behaviour. What is wrong is
that I can not change the status by pressing the hardware button.)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-firmware 1.116
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Fri Dec  6 23:04:18 2013
Dependencies:
 
InstallationDate: Installed on 2013-12-04 (2 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

-- 
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/1258675

Title:
  hardware switch of wireless not working for Centrino Advanced-N 6235

Status in “linux-firmware” package in Ubuntu:
  New

Bug description:
  I have ubuntu 13.10  64-bit running on a HP ZBook 15. The notebook uses an 
Intel Corporation Centrino Advanced-N 6235 (rev 24) wireless adapter.
   
  The wireless networking principally works. The issue is that it is not 
possible to enable or disable it using the hardware button. The only way is the 
software control (clicking on Enable Wi-Fi).

  BTW, when I click on Enable Wi-Fi, it indicates the changes status
  of the wifi radio by changing the colour of the light on the hardware
  button. (This is the correct and expected behaviour. What is wrong is
  that I can not change the status by pressing the hardware button.)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-firmware 1.116
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Dec  6 23:04:18 2013
  Dependencies:
   
  InstallationDate: Installed on 2013-12-04 (2 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1258675/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258676] [NEW] Kernel panic on connecting usb drive to ASM1042 usb3 controller

2013-12-06 Thread webmind
Public bug reported:

The kernel panics consistenly when connecting a external USB3 drive to
the pci-express - usb3 controller ASM1042 without providing either the
external drive or the controller with external power.

This system was running very stable before adding this controller.

System was sadly enough unable to write anything to /var/log/kern.log I
have taken pictures of the screen but a lot also scrolls out of view
before you can read it.

lspci entry: 
05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  webmind2860 F pulseaudio
Date: Fri Dec  6 23:24:09 2013
InstallationDate: Installed on 2013-03-01 (280 days ago)
InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1)
MachineType: LENOVO 7470BQ5
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic 
root=UUID=1d5dcb98-da29-4fbe-957f-6f0c15c6a379 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic  N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-27 (40 days ago)
dmi.bios.date: 03/17/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET42WW (2.06 )
dmi.board.name: 7470BQ5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: TP037123
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6DET42WW(2.06):bd03/17/2009:svnLENOVO:pn7470BQ5:pvrThinkPadX200s:rvnLENOVO:rn7470BQ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7470BQ5
dmi.product.version: ThinkPad X200s
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

** Attachment added: Fotos of screens crashes and sysrq dumps
   
https://bugs.launchpad.net/bugs/1258676/+attachment/3924538/+files/screenshots.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/1258676

Title:
  Kernel panic on connecting usb drive to ASM1042 usb3 controller

Status in “linux” package in Ubuntu:
  New

Bug description:
  The kernel panics consistenly when connecting a external USB3 drive to
  the pci-express - usb3 controller ASM1042 without providing either
  the external drive or the controller with external power.

  This system was running very stable before adding this controller.

  System was sadly enough unable to write anything to /var/log/kern.log
  I have taken pictures of the screen but a lot also scrolls out of view
  before you can read it.

  lspci entry: 
  05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-14-generic 3.11.0-14.21
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  webmind2860 F pulseaudio
  Date: Fri Dec  6 23:24:09 2013
  InstallationDate: Installed on 2013-03-01 (280 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MachineType: LENOVO 7470BQ5
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic 
root=UUID=1d5dcb98-da29-4fbe-957f-6f0c15c6a379 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-14-generic N/A
   linux-backports-modules-3.11.0-14-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (40 days ago)
  dmi.bios.date: 03/17/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET42WW (2.06 )
  dmi.board.name: 7470BQ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: TP037123
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET42WW(2.06):bd03/17/2009:svnLENOVO:pn7470BQ5:pvrThinkPadX200s:rvnLENOVO:rn7470BQ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7470BQ5
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258676/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1258676] Re: Kernel panic on connecting usb drive to ASM1042 usb3 controller

2013-12-06 Thread webmind
** Attachment removed: WifiSyslog.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258676/+attachment/3924555/+files/WifiSyslog.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258676/+attachment/3924542/+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/1258676

Title:
  Kernel panic on connecting usb drive to ASM1042 usb3 controller

Status in “linux” package in Ubuntu:
  New

Bug description:
  The kernel panics consistenly when connecting a external USB3 drive to
  the pci-express - usb3 controller ASM1042 without providing either
  the external drive or the controller with external power.

  This system was running very stable before adding this controller.

  System was sadly enough unable to write anything to /var/log/kern.log
  I have taken pictures of the screen but a lot also scrolls out of view
  before you can read it.

  lspci entry: 
  05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-14-generic 3.11.0-14.21
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  webmind2860 F pulseaudio
  Date: Fri Dec  6 23:24:09 2013
  InstallationDate: Installed on 2013-03-01 (280 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MachineType: LENOVO 7470BQ5
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic 
root=UUID=1d5dcb98-da29-4fbe-957f-6f0c15c6a379 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-14-generic N/A
   linux-backports-modules-3.11.0-14-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (40 days ago)
  dmi.bios.date: 03/17/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET42WW (2.06 )
  dmi.board.name: 7470BQ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: TP037123
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET42WW(2.06):bd03/17/2009:svnLENOVO:pn7470BQ5:pvrThinkPadX200s:rvnLENOVO:rn7470BQ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7470BQ5
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258676/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1256646] Re: [ASUS M3N78-VM, Nvidia MCP77/78 HDMI, Digital Out, HDMI] No sound at all

2013-12-06 Thread Raymond
** Also affects: alsa-lib (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1256646

Title:
  [ASUS M3N78-VM, Nvidia MCP77/78 HDMI, Digital Out, HDMI] No sound at
  all

Status in ALSA driver:
  Unknown
Status in “alsa-driver” package in Ubuntu:
  Confirmed
Status in “alsa-lib” package in Ubuntu:
  New

Bug description:
  Sound stopped working on upgrade from 13.4 to 13.10.  Up until then,
  sound via HDMI worked fine.  Now, I get no sound through HDMI.
  Checked the Sound Settings and alsa mixer and everything looks fine.
  If I hook up speakers to the microphone port I get sound.

  I used ubuntu-bug -s audio to report this bug (very nice BTW).  If
  there is any additional information you need or anything you would
  like me to try, I am game for it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  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/controlC0:  ray2389 F pulseaudio
   /dev/snd/controlC1:  ray2389 F pulseaudio
  Date: Sun Dec  1 09:35:49 2013
  InstallationDate: Installed on 2011-10-02 (791 days ago)
  InstallationMedia: Edubuntu 11.04 Natty Narwhal - Release amd64 (20110426)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: Built-in Audio - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ray2389 F pulseaudio
   /dev/snd/controlC1:  ray2389 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [System Product Name, Nvidia MCP77/78 HDMI, Digital Out, HDMI] No 
sound at all
  UpgradeStatus: Upgraded to saucy on 2013-11-03 (27 days ago)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1009
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-VM
  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.:bvr1009:bd04/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM: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/alsa-driver/+bug/1256646/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235136] Re: CVE-2013-4387

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (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/1235136

Title:
  CVE-2013-4387

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:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix Released
Status in “linux-armadaxp” source package in Precise:
  Fix Released
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-fsl-imx51” source package in Precise:
  Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Precise:
  Won't Fix
Status in “linux-lts-quantal” source package in Precise:
  Fix Released
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Committed
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Released
Status in “linux” source package in Quantal:
  Fix Released
Status in “linux-armadaxp” source package in Quantal:
  Fix Released
Status in “linux-ec2” source package in Quantal:
  Invalid
Status in “linux-fsl-imx51” source package in Quantal:
  Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Quantal:
  Won't Fix
Status in “linux-lts-quantal” source package in Quantal:
  Invalid
Status in “linux-lts-raring” source package in Quantal:
  Invalid
Status in “linux-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-mvl-dove” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Fix Released
Status in “linux” 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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source 

[Kernel-packages] [Bug 1258676] Status changed to Confirmed

2013-12-06 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258676

Title:
  Kernel panic on connecting usb drive to ASM1042 usb3 controller

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The kernel panics consistenly when connecting a external USB3 drive to
  the pci-express - usb3 controller ASM1042 without providing either
  the external drive or the controller with external power.

  This system was running very stable before adding this controller.

  System was sadly enough unable to write anything to /var/log/kern.log
  I have taken pictures of the screen but a lot also scrolls out of view
  before you can read it.

  lspci entry: 
  05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host 
Controller

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-14-generic 3.11.0-14.21
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  webmind2860 F pulseaudio
  Date: Fri Dec  6 23:24:09 2013
  InstallationDate: Installed on 2013-03-01 (280 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MachineType: LENOVO 7470BQ5
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic 
root=UUID=1d5dcb98-da29-4fbe-957f-6f0c15c6a379 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-14-generic N/A
   linux-backports-modules-3.11.0-14-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (40 days ago)
  dmi.bios.date: 03/17/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET42WW (2.06 )
  dmi.board.name: 7470BQ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: TP037123
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET42WW(2.06):bd03/17/2009:svnLENOVO:pn7470BQ5:pvrThinkPadX200s:rvnLENOVO:rn7470BQ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7470BQ5
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258676/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1248703] Re: CVE-2013-4470

2013-12-06 Thread John Johansen
** Changed in: linux-armadaxp (Ubuntu Quantal)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1248703

Title:
  CVE-2013-4470

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  Won't Fix
Status in “linux-lts-backport-natty” package in Ubuntu:
  Won't Fix
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Lucid:
  Won't Fix
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Fix 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 Released
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  Fix 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 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:
  Fix Released
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
Status in “linux-lts-backport-natty” source package in Saucy:
  Won't Fix
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Invalid
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  Won't Fix
Status in “linux-lts-backport-natty” source package in Trusty:
  Won't Fix
Status in “linux-lts-quantal” source package in 

[Kernel-packages] [Bug 1258686] [NEW] Faulty laptop battery or AC throws system cache for a loop

2013-12-06 Thread Alan Pater
Public bug reported:

After a random period of time after a fresh boot, the system cache gets
corrupted. This is shown by hdparm -T.

Before system cache corruption:
 Timing cached reads:   1804 MB in  2.00 seconds = 902.88 MB/sec

After system cache corruption:
 Timing cached reads:   258 MB in  2.00 seconds = 129.10 MB/sec

Either the system battery or the AC adaptor is not functioning
correctly, the Dell bios at times indicates that the AC adaptor is not a
valid Dell product, though it is. In any case, the battery does not
charge, but remains at 0%.

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 i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  asp1931 F pulseaudio
Date: Fri Dec  6 18:45:58 2013
HibernationDevice: RESUME=UUID=08003f81-dc4b-4697-adb9-c4f28291be17
InstallationDate: Installed on 2013-12-06 (0 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
MachineType: Dell Inc. Latitude D420
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=ecd26c7d-0cb5-446e-a2ca-e4fefc0c0fd0 ro quiet splash 
processor.ignore_ppc=1 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:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0TJ984
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-bug i386 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/1258686

Title:
  Faulty laptop battery or AC throws system cache for a loop

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After a random period of time after a fresh boot, the system cache
  gets corrupted. This is shown by hdparm -T.

  Before system cache corruption:
   Timing cached reads:   1804 MB in  2.00 seconds = 902.88 MB/sec

  After system cache corruption:
   Timing cached reads:   258 MB in  2.00 seconds = 129.10 MB/sec

  Either the system battery or the AC adaptor is not functioning
  correctly, the Dell bios at times indicates that the AC adaptor is not
  a valid Dell product, though it is. In any case, the battery does not
  charge, but remains at 0%.

  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 i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asp1931 F pulseaudio
  Date: Fri Dec  6 18:45:58 2013
  HibernationDevice: RESUME=UUID=08003f81-dc4b-4697-adb9-c4f28291be17
  InstallationDate: Installed on 2013-12-06 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Dell Inc. Latitude D420
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=ecd26c7d-0cb5-446e-a2ca-e4fefc0c0fd0 ro quiet splash 
processor.ignore_ppc=1 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:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0TJ984
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258686/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1258686] Status changed to Confirmed

2013-12-06 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258686

Title:
  Faulty laptop battery or AC throws system cache for a loop

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After a random period of time after a fresh boot, the system cache
  gets corrupted. This is shown by hdparm -T.

  Before system cache corruption:
   Timing cached reads:   1804 MB in  2.00 seconds = 902.88 MB/sec

  After system cache corruption:
   Timing cached reads:   258 MB in  2.00 seconds = 129.10 MB/sec

  Either the system battery or the AC adaptor is not functioning
  correctly, the Dell bios at times indicates that the AC adaptor is not
  a valid Dell product, though it is. In any case, the battery does not
  charge, but remains at 0%.

  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 i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asp1931 F pulseaudio
  Date: Fri Dec  6 18:45:58 2013
  HibernationDevice: RESUME=UUID=08003f81-dc4b-4697-adb9-c4f28291be17
  InstallationDate: Installed on 2013-12-06 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Dell Inc. Latitude D420
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=ecd26c7d-0cb5-446e-a2ca-e4fefc0c0fd0 ro quiet splash 
processor.ignore_ppc=1 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:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0TJ984
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258686/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 659405] Re: Xorg crashes on suspend

2013-12-06 Thread Bernardo Ramos
I'm running Xubuntu 12.04 on an AVELL notebook model G1711 (avell dot com dot 
br)
I did not install NVidia Driver, running only intel's integrated video 
interface (i5 Haswell).
However, when it suspends due to inactivity timeout or if I ask it to enter in 
suspension (not hibernation) i freezes out.
The only way to use the machine again is by pressing on/off button up to 
shutting the machine off, and then restarting it again.
I upgraded to KERNEL 3.12-SAUCY, have Oracle Java JDK 7 and Oracle VirtualBox 
installed.
Initailly it presented ...done in upper left corner and nothing more.
Once it said also in upper left corner something like Loading  Virtualbox 
kernel blablabla [ok] and froze up.
I tried many distributions and the HW list bellow was produced under openSuse 
13.1.
However my curent Kernel is :
3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
Thanks!


bernardo@G1711:~$ uname -a
Linux G1711 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux
bernardo@G1711:~$ sudo lsusb
[sudo] password for bernardo: 
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 003 Device 002: ID 8087:07da Intel Corp. 
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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
bernardo@G1711:~$ sudo lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 
6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
01:00.0 3D controller: NVIDIA Corporation GK106M [GeForce GTX 765M] (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289 
(rev 01)
04:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0a)
bernardo@G1711:~$

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/659405

Title:
  Xorg crashes on suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  Not every time and perhaps not most of the time, but often enough when
  I put the computer in suspend mode, it apparently makes X crash. When
  I wake up the computer from suspend, my session is gone and and
  replaced by the gdm login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  Uname: Linux 2.6.36-020636rc7-generic i686
  Architecture: i386
  Date: Tue Oct 12 21:37:19 2010
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636rc7-generic
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  Package: xorg 1:7.5+5ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  Tags: lucid
  Uname: Linux 2.6.36-020636rc7-generic i686
  UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev 

[Kernel-packages] [Bug 1246793] Re: Battery charging slows down laptop

2013-12-06 Thread Alan Pater
Looks like you have run into the infamous  CPU frequency issue.

http://www.thinkwiki.org/wiki/Problem_with_CPU_frequency_scaling

Solution is to make sure you are running with high quality AC power.

Workaround is to edit /etc/default/grub

Find the following line and add processor.ignore_ppc=1
so it looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT=quiet splash processor.ignore_ppc=1

then
  sudo update-grub  sudo reboot.

Have a nice day.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1246793

Title:
  Battery charging slows down laptop

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Following up on Bug #962712 which was marked as invalid, instead of
  fixed (gee, thanks...) I'm using Ubuntu 13.10 and this still happening
  pretty badly.

  Steps to reproduce:

  1) Unplug laptop, plug-in second monitor, drain battery until OS warns user 
and asks her to plugin laptop
  2) Plugin laptop

  Expected: Laptop works normally
  Actual: Laptop slows down severely.

  -=-=-

  Drilling down, run `cpufreq-info`

  Expected:
  driver: acpi-cpufreq [...]
  current policy: frequency should be within 800 MHz and 2.80 GHz.

  Actual: 
  driver: acpi-cpufreq [...]
  current policy: frequency should be within 800 MHz and 800 MHz

  -=-=-

  Drilling down, this is known, lingering problem, and is not invalid,
  please triage instead of sweeping under the rug

   * http://ubuntuforums.org/showthread.php?t=1921292
   * 
http://askubuntu.com/questions/186387/laptop-slows-down-while-charging-battery
   * http://bit.ly/17vgUO0
   * ...

  -=-=-

  Thank you for your consideration.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dac514 2414 F pulseaudio
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=b95f5ff9-5665-42f8-8b10-f2ae3ca2411f
  InstallationDate: Installed on 2012-06-12 (505 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 4286CTO
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=59641606-e542-4c74-8a31-08c66bfae100 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  saucy
  Uname: Linux 3.11.0-12-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (23 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1246793/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1256088] Re: CVE-2013-6381

2013-12-06 Thread John Johansen
** Changed in: linux (Ubuntu Trusty)
   Status: New = Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1256088

Title:
  CVE-2013-6381

Status in “linux” package in Ubuntu:
  Fix Committed
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  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:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  Fix Committed
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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
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:
  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:
  New
Status in “linux-lts-backport-natty” source package in Saucy:
  New
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
  New
Status in “linux-lts-backport-natty” source package in Trusty:
  New
Status in “linux-lts-quantal” source package in Trusty:
  Invalid
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid
Status in 

[Kernel-packages] [Bug 1050352] Re: [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects and connects

2013-12-06 Thread Christopher M. Penalver
Tareeq, so your hardware may be tracked, could you please file a new report via 
a terminal:
ubuntu-bug 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/1050352

Title:
  [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects
  and connects

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 12.10 AMD64, kernel 3.5.0-14.16.
  External hard drive Hitachi Touro Desk 3.0 connected to USB 3.0 port.

  Gets disconnected randomly and then connected again. Only happens with
  USB 3.0 connection (xhci).

  WORKAROUND: When plugged to USB 2.0 (ehci) port it works ok.

  Attached is related kernel log portion: there is nothing special there
  except for these lines:

  11-2: Parent hub missing LPM exit latency info.  Power management will be 
impacted.
  usb 11-2: USB disconnect, device number 2
  ---
  AcpiTables: Error: command ['pkexec', 
'/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error 
executing /usr/share/apport/dump_acpi_tables.py: Permission denied
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dmitry 3011 F pulseaudio
   /dev/snd/controlC1:  dmitry 3011 F pulseaudio
   /dev/snd/controlC0:  dmitry 3011 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e3fa02f8-4f15-4f00-9d79-e982d4837b5c
  IwConfig:
   vboxnet0  no wireless extensions.

   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD4
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic 
root=UUID=33c3405d-4b3c-4b5c-a1c3-fd2c7bad1c79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-14-generic N/A
   linux-backports-modules-3.5.0-14-generic  N/A
   linux-firmware1.91
  RfKill:

  Tags:  quantal running-unity
  Uname: Linux 3.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago)
  UserGroups: adm cdrom dialout fuse kvm libvirtd lpadmin plugdev pulse 
pulse-access sambashare sudo vboxusers wireshark
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P55A-UD4
  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.:bvrF14:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1050352/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

2013-12-06 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1229591

Title:
  display brightness keys don't generate evdev events after saucy
  upgrade

Status in “linux” package in Ubuntu:
  Confirmed

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 659405] Re: Xorg crashes on suspend

2013-12-06 Thread Christopher M. Penalver
Bernardo Ramos, so your hardware may be tracked, could you please file a new 
report via a terminal:
ubuntu-bug linux

** Tags added: needs-kernel-logs

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/659405

Title:
  Xorg crashes on suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  Not every time and perhaps not most of the time, but often enough when
  I put the computer in suspend mode, it apparently makes X crash. When
  I wake up the computer from suspend, my session is gone and and
  replaced by the gdm login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  Uname: Linux 2.6.36-020636rc7-generic i686
  Architecture: i386
  Date: Tue Oct 12 21:37:19 2010
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636rc7-generic
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  Package: xorg 1:7.5+5ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  Tags: lucid
  Uname: Linux 2.6.36-020636rc7-generic i686
  UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare 
video
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636rc7-generic

  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  Package: xorg 1:7.5+5ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  Tags: lucid lucid
  Uname: Linux 2.6.36-020636rc7-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare 
video
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636rc7-generic

  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  Package: xorg 1:7.5+5ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags: lucid lucid
  Uname: Linux 2.6.36-020636-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare 
video
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659405/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1256747] Re: [HP Folio 13-1050la Notebook PC] Bluetooth subsystem dies after suspend

2013-12-06 Thread gpothier
The bug does not occur with the kernel compiled as indicated.
Very useful command line, BTW!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1256747

Title:
  [HP Folio 13-1050la Notebook PC] Bluetooth subsystem dies after
  suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After resume from suspend, my bluetooth mouse cannot reconnect. The
  problem does not happen with kernel 3.10.

  WORKAROUND: Disable and re-enable bluetooth from the gnome shell
  bluetooth icon.

  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:  gpothier   2310 F pulseaudio
  Date: Sun Dec  1 23:32:28 2013
  HibernationDevice: RESUME=UUID=281e4254-f100-4193-8e7d-13c4d9785734
  InstallationDate: Installed on 2013-06-04 (180 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 
(20130424)
  MachineType: Hewlett-Packard HP Folio 13 Notebook PCC
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=b26f4d55-88e9-4a68-8456-8a7260aa20a9 ro acpi_backlight=vendor 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: Upgraded to saucy on 2013-10-24 (38 days ago)
  dmi.bios.date: 03/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 17F8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 46.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPCC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Folio 13 Notebook PCC
  dmi.product.version: 068C10204A0320100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258715] [NEW] Waking up from suspension freezes up the system

2013-12-06 Thread Bernardo Ramos
Public bug reported:

I'm running Xubuntu 12.04 on an AVELL notebook model G1711 (avell dot com dot 
br)
 I did not install NVidia Driver, running only intel's integrated video 
interface (i5 Haswell).
 However, when it suspends due to inactivity timeout or if I ask it to enter in 
suspension (not hibernation) i freezes out.
 The only way to use the machine again is by pressing on/off button up to 
shutting the machine off, and then restarting it again.
 I upgraded to KERNEL 3.12-SAUCY, have Oracle Java JDK 7 and Oracle VirtualBox 
installed.
 Initailly it presented ...done in upper left corner and nothing more.
 Once it said also in upper left corner something like Loading Virtualbox 
kernel blablabla [ok] and froze up.
 However my curent Kernel is :
 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
 Thanks!
 
bernardo@G1711:~$ uname -a
 Linux G1711 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
 bernardo@G1711:~$ sudo lsusb
 [sudo] password for bernardo:
 Bus 001 Device 002: ID 8087:8008 Intel Corp.
 Bus 002 Device 002: ID 8087:8000 Intel Corp.
 Bus 003 Device 002: ID 8087:07da Intel Corp.
 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 bernardo@G1711:~$ sudo lspci
 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller (rev 06)
 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 
6-port SATA Controller 1 [AHCI mode] (rev 05)
 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
 01:00.0 3D controller: NVIDIA Corporation GK106M [GeForce GTX 765M] (rev a1)
 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289 
(rev 01)
 04:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0a)
 bernardo@G1711:~$

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-52-generic 3.2.0-52.78
ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
Uname: Linux 3.2.0-52-generic x86_64
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 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bernardo   1815 F pulseaudio
  bernardo   1858 F xfce4-volumed
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7a14000 irq 45'
   Mixer name   : 'Generic  ID 0'
   Components   : 'HDA:,80860101,0010'
   Controls  : 0
   Simple ctrls  : 0
Card0.Amixer.values:
 
Card1.Amixer.info:
 Card hw:1 'PCH'/'HDA Intel PCH at 0xf7a1 irq 45'
   Mixer name   : 'VIA VT1802'
   Components   : 'HDA:11068446,15583537,0010'
   Controls  : 32
   Simple ctrls  : 19
Date: Fri Dec  6 23:55:47 2013
HibernationDevice: RESUME=UUID=164435ef-5b54-4926-b6d0-89a6df38eff5
InstallationMedia: Xubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820)
MachineType: Notebook W35xSTQ_370ST
MarkForUpload: True
ProcEnviron:
 LANGUAGE=pt_BR:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: 

[Kernel-packages] [Bug 1257149] Re: linux-ti-omap4: 3.5.0-237.53 -proposed tracker

2013-12-06 Thread John Johansen
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

-- 
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/1257149

Title:
  linux-ti-omap4: 3.5.0-237.53 -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:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “linux-ti-omap4” source package in Quantal:
  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:Tuesday, 03. December 2013 03:14 UTC
  kernel-stable-master-bug:1257035
  kernel-stable-Certification-testing-end:Wednesday, 04. December 2013 16:02 UTC
  kernel-stable-Prepare-package-end:Wednesday, 04. December 2013 22:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 04. December 2013 22:01 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 05. December 2013 20:01 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Thursday, 05. December 2013 21:02 UTC
  kernel-stable-Security-signoff-start:Thursday, 05. December 2013 21:02 UTC
  kernel-stable-Verification-testing-start:Thursday, 05. December 2013 21:02 UTC
  kernel-stable-Regression-testing-start:Thursday, 05. December 2013 21:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1257149/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1256095] Re: CVE-2013-6392

2013-12-06 Thread John Johansen
** Description changed:

- information disclosure
+ The genlock_dev_ioctl function in genlock.c in the Genlock driver for
+ the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC)
+ Android contributions for MSM devices and other products, does not
+ properly initialize a certain data structure, which allows local users
+ to obtain sensitive information from kernel stack memory via a crafted
+ GENLOCK_IOC_EXPORT ioctl call.

-- 
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/1256095

Title:
  CVE-2013-6392

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:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
Status in “linux-lts-quantal” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  New
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  New
Status in “linux-fsl-imx51” source package in Lucid:
  Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” source package in Lucid:
  Invalid
Status in “linux-mvl-dove” source package in Lucid:
  Invalid
Status in “linux-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  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:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
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:
  New
Status in “linux-lts-backport-natty” source package in Quantal:
  New
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:
  New
Status in “linux-lts-backport-natty” source package in Raring:
  New
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:
  New
Status in “linux-lts-backport-natty” source package in Saucy:
  New
Status in “linux-lts-quantal” source package in Saucy:
  Invalid
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-mvl-dove” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  New
Status in “linux” source package in Trusty:
  New
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” source package in Trusty:
  Invalid
Status in “linux-fsl-imx51” source package in Trusty:
  Invalid
Status in “linux-lts-backport-maverick” source package in 

[Kernel-packages] [Bug 1257538] Re: linux-ti-omap4: 3.2.0-1442.61 -proposed tracker

2013-12-06 Thread John Johansen
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

-- 
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/1257538

Title:
  linux-ti-omap4: 3.2.0-1442.61 -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:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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:Wednesday, 04. December 2013 00:24 UTC
  kernel-stable-master-bug:1257370
  kernel-stable-Certification-testing-end:Wednesday, 04. December 2013 17:05 UTC
  kernel-stable-Prepare-package-end:Wednesday, 04. December 2013 22:05 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 04. December 2013 22:05 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 05. December 2013 20:04 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Thursday, 05. December 2013 21:06 UTC
  kernel-stable-Security-signoff-start:Thursday, 05. December 2013 21:06 UTC
  kernel-stable-Verification-testing-start:Thursday, 05. December 2013 21:06 UTC
  kernel-stable-Regression-testing-start:Thursday, 05. December 2013 21:06 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1257538/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 659405] Re: Xorg crashes on suspend

2013-12-06 Thread Bernardo Ramos
It is Done.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258715
I home it may help.
For now, I had to disable suspension due to inactivity, hich is pretty 
unconvenient running on batery charge only.
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/659405

Title:
  Xorg crashes on suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  Not every time and perhaps not most of the time, but often enough when
  I put the computer in suspend mode, it apparently makes X crash. When
  I wake up the computer from suspend, my session is gone and and
  replaced by the gdm login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  Uname: Linux 2.6.36-020636rc7-generic i686
  Architecture: i386
  Date: Tue Oct 12 21:37:19 2010
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636rc7-generic
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  Package: xorg 1:7.5+5ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  Tags: lucid
  Uname: Linux 2.6.36-020636rc7-generic i686
  UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare 
video
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636rc7-generic

  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  Package: xorg 1:7.5+5ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  Tags: lucid lucid
  Uname: Linux 2.6.36-020636rc7-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare 
video
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636rc7-generic

  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100113)
  Package: xorg 1:7.5+5ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags: lucid lucid
  Uname: Linux 2.6.36-020636-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare 
video
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.36-020636-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659405/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258715] Status changed to Confirmed

2013-12-06 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New = Confirmed

** Tags added: trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258715

Title:
  Waking up from suspension freezes up the system

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm running Xubuntu 12.04 on an AVELL notebook model G1711 (avell dot com dot 
br)
   I did not install NVidia Driver, running only intel's integrated video 
interface (i5 Haswell).
   However, when it suspends due to inactivity timeout or if I ask it to enter 
in suspension (not hibernation) i freezes out.
   The only way to use the machine again is by pressing on/off button up to 
shutting the machine off, and then restarting it again.
   I upgraded to KERNEL 3.12-SAUCY, have Oracle Java JDK 7 and Oracle 
VirtualBox installed.
   Initailly it presented ...done in upper left corner and nothing more.
   Once it said also in upper left corner something like Loading Virtualbox 
kernel blablabla [ok] and froze up.
   However my curent Kernel is :
   3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
   Thanks!
   
  bernardo@G1711:~$ uname -a
   Linux G1711 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
   bernardo@G1711:~$ sudo lsusb
   [sudo] password for bernardo:
   Bus 001 Device 002: ID 8087:8008 Intel Corp.
   Bus 002 Device 002: ID 8087:8000 Intel Corp.
   Bus 003 Device 002: ID 8087:07da Intel Corp.
   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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   bernardo@G1711:~$ sudo lspci
   00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller (rev 06)
   00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
   00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
   00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
   00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB xHCI (rev 05)
   00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
   00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB EHCI #2 (rev 05)
   00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
   00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #1 (rev d5)
   00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #3 (rev d5)
   00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #4 (rev d5)
   00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB EHCI #1 (rev 05)
   00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
   00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
   00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
   01:00.0 3D controller: NVIDIA Corporation GK106M [GeForce GTX 765M] (rev a1)
   03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 
24)
   04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289 
(rev 01)
   04:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
   bernardo@G1711:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-52-generic 3.2.0-52.78
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic x86_64
  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 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bernardo   1815 F pulseaudio
bernardo   1858 F xfce4-volumed
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7a14000 irq 45'
 Mixer name : 'Generic  ID 0'
 Components : 'HDA:,80860101,0010'
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 

[Kernel-packages] [Bug 1225571] Re: WARNING: CPU: 0 PID: 1529 at /build/buildd/linux-3.11.0/kernel/softirq.c:159 local_bh_enable+0x60/0x90()

2013-12-06 Thread Dirk Kraft
The patch now ended up in linus' repo
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bc9627e7e918a85e906c1a3f6d01d9b8ef911a96
and is included in 3.13-rc3

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1225571

Title:
  WARNING: CPU: 0 PID: 1529 at
  /build/buildd/linux-3.11.0/kernel/softirq.c:159
  local_bh_enable+0x60/0x90()

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After updating my system from raring to saucy it was crashing during
  boot. After some digging I realised that it is connected to the
  network interfaces. After removing the auto line for the two network
  interfaces in /etc/network/interfaces the system boots successfully.

  If one then tries to bring up the network interface using the
  via_velocity driver (using ifup) the system crashes and the following
  message appears in syslog:

  Sep 15 02:25:24 nas dhclient: Internet Systems Consortium DHCP Client 4.2.4
  Sep 15 02:25:24 nas dhclient: Copyright 2004-2012 Internet Systems Consortium.
  Sep 15 02:25:24 nas dhclient: All rights reserved.
  Sep 15 02:25:24 nas dhclient: For info, please visit 
https://www.isc.org/software/dhcp/
  Sep 15 02:25:24 nas dhclient: 
  Sep 15 02:25:25 nas kernel: [   81.953639] Velocity is AUTO mode
  Sep 15 02:25:25 nas dhclient: Listening on LPF/eth0/00:40:63:f5:15:76
  Sep 15 02:25:25 nas dhclient: Sending on   LPF/eth0/00:40:63:f5:15:76
  Sep 15 02:25:25 nas dhclient: Sending on   Socket/fallback
  Sep 15 02:25:25 nas dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 
interval 3 (xid=0x4ff0e6ad)
  Sep 15 02:25:26 nas kernel: [   83.462216] eth0: Link auto-negotiation speed 
100M bps full duplex
  Sep 15 02:25:28 nas dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 
interval 3 (xid=0x4ff0e6ad)
  Sep 15 02:25:29 nas kernel: [   86.675203] [ cut here 
]
  Sep 15 02:25:29 nas kernel: [   86.675227] WARNING: CPU: 0 PID: 1529 at 
/build/buildd/linux-3.11.0/kernel/softirq.c:159 local_bh_enable+0x60/0x90()
  Sep 15 02:25:29 nas kernel: [   86.675231] Modules linked in: 
snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) 
snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) via_cputemp 
snd_rawmidi(F) snd_seq(F) snd_seq_device(F) snd_timer(F) i2c_viapro psmouse(F) 
serio_raw(F) snd(F) soundcore(F) shpchp mac_hid hwmon_vid lp(F) parport(F) 
binfmt_misc(F) raid10(F) raid1(F) raid0(F) multipath(F) linear(F) dm_crypt(F) 
via_rng raid456(F) async_raid6_recov(F) async_memcpy(F) async_pq(F) 
async_xor(F) async_tx(F) xor(F) raid6_pq(F) pata_acpi padlock_sha padlock_aes 
pata_via via_velocity via_rhine mii(F) ahci(F) libahci(F) crc_ccitt(F)
  Sep 15 02:25:29 nas kernel: [   86.675315] CPU: 0 PID: 1529 Comm: SpiderOak 
Tainted: GF3.11.0-7-generic #13-Ubuntu
  Sep 15 02:25:29 nas kernel: [   86.675320] Hardware name: To Be Filled By 
O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014  12/18/2007
  Sep 15 02:25:29 nas kernel: [   86.675324]    ee803ce8 
c16313c4  ee803d18 c105268e c1805af4
  Sep 15 02:25:29 nas kernel: [   86.675336]   05f9 c1805dc8 
009f c1056b50 c1056b50 c19566c0 efbafb80
  Sep 15 02:25:29 nas kernel: [   86.675347]   ee803d28 c1052752 
0009  ee803d30 c1056b50 ee803d4c
  Sep 15 02:25:29 nas kernel: [   86.675359] Call Trace:
  Sep 15 02:25:29 nas kernel: [   86.675371]  [c16313c4] dump_stack+0x41/0x52
  Sep 15 02:25:29 nas kernel: [   86.675379]  [c105268e] 
warn_slowpath_common+0x7e/0xa0
  Sep 15 02:25:29 nas kernel: [   86.675387]  [c1056b50] ? 
local_bh_enable+0x60/0x90
  Sep 15 02:25:29 nas kernel: [   86.675394]  [c1056b50] ? 
local_bh_enable+0x60/0x90
  Sep 15 02:25:29 nas kernel: [   86.675401]  [c1052752] 
warn_slowpath_null+0x22/0x30
  Sep 15 02:25:29 nas kernel: [   86.675409]  [c1056b50] 
local_bh_enable+0x60/0x90
  Sep 15 02:25:29 nas kernel: [   86.675421]  [c155f1ea] dst_alloc+0x12a/0x140
  Sep 15 02:25:29 nas kernel: [   86.675431]  [c158189d] 
rt_dst_alloc+0x4d/0x60
  Sep 15 02:25:29 nas kernel: [   86.675440]  [c1583fdc] 
ip_route_input_noref+0x2bc/0xa30
  Sep 15 02:25:29 nas kernel: [   86.675448]  [c107c504] ? 
resched_task+0x24/0x70
  Sep 15 02:25:29 nas kernel: [   86.675456]  [c107cfd8] ? 
ttwu_do_wakeup+0x18/0x100
  Sep 15 02:25:29 nas kernel: [   86.675464]  [c1585b4b] 
ip_rcv_finish+0xbb/0x340
  Sep 15 02:25:29 nas kernel: [   86.675471]  [c1586414] ip_rcv+0x254/0x3c0
  Sep 15 02:25:29 nas kernel: [   86.675479]  [c1558217] 
__netif_receive_skb_core+0x557/0x730
  Sep 15 02:25:29 nas kernel: [   86.675487]  [c1558406] 
__netif_receive_skb+0x16/0x60
  Sep 15 02:25:29 nas kernel: [   86.675494]  [c155846f] 
netif_receive_skb+0x1f/0x80
  Sep 15 02:25:29 nas kernel: [   86.675516]  [f845e7ab] 
velocity_rx_srv+0x2ab/0x410 [via_velocity]
  Sep 15 02:25:29 nas kernel: [   

[Kernel-packages] [Bug 1256747] Re: [HP Folio 13-1050la Notebook PC] Bluetooth subsystem dies after suspend

2013-12-06 Thread Christopher M. Penalver
gpothier, please delete the deb files that were previously created and execute:
git checkout c046555966e4a3a75b731e05ece3b1d763ac56ae  cp /boot/config-`uname 
-r` .config  yes '' | make oldconfig  make-kpkg clean  
CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd 
--append-to-version=-custom kernel_image kernel_headers  cd ..  sudo dpkg 
-i *.deb

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1256747

Title:
  [HP Folio 13-1050la Notebook PC] Bluetooth subsystem dies after
  suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After resume from suspend, my bluetooth mouse cannot reconnect. The
  problem does not happen with kernel 3.10.

  WORKAROUND: Disable and re-enable bluetooth from the gnome shell
  bluetooth icon.

  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:  gpothier   2310 F pulseaudio
  Date: Sun Dec  1 23:32:28 2013
  HibernationDevice: RESUME=UUID=281e4254-f100-4193-8e7d-13c4d9785734
  InstallationDate: Installed on 2013-06-04 (180 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 
(20130424)
  MachineType: Hewlett-Packard HP Folio 13 Notebook PCC
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=b26f4d55-88e9-4a68-8456-8a7260aa20a9 ro acpi_backlight=vendor 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: Upgraded to saucy on 2013-10-24 (38 days ago)
  dmi.bios.date: 03/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 17F8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 46.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPCC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Folio 13 Notebook PCC
  dmi.product.version: 068C10204A0320100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258715] Re: Waking up from suspension freezes up the system

2013-12-06 Thread Christopher M. Penalver
** Description changed:

- I'm running Xubuntu 12.04 on an AVELL notebook model G1711 (avell dot com dot 
br)
-  I did not install NVidia Driver, running only intel's integrated video 
interface (i5 Haswell).
-  However, when it suspends due to inactivity timeout or if I ask it to enter 
in suspension (not hibernation) i freezes out.
-  The only way to use the machine again is by pressing on/off button up to 
shutting the machine off, and then restarting it again.
-  I upgraded to KERNEL 3.12-SAUCY, have Oracle Java JDK 7 and Oracle 
VirtualBox installed.
-  Initailly it presented ...done in upper left corner and nothing more.
-  Once it said also in upper left corner something like Loading Virtualbox 
kernel blablabla [ok] and froze up.
-  However my curent Kernel is :
-  3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
-  Thanks!
-  
- bernardo@G1711:~$ uname -a
-  Linux G1711 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
-  bernardo@G1711:~$ sudo lsusb
-  [sudo] password for bernardo:
-  Bus 001 Device 002: ID 8087:8008 Intel Corp.
-  Bus 002 Device 002: ID 8087:8000 Intel Corp.
-  Bus 003 Device 002: ID 8087:07da Intel Corp.
-  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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  bernardo@G1711:~$ sudo lspci
-  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller (rev 06)
-  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
-  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
-  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
-  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB xHCI (rev 05)
-  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
-  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB EHCI #2 (rev 05)
-  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
-  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #1 (rev d5)
-  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #3 (rev d5)
-  00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family 
PCI Express Root Port #4 (rev d5)
-  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 
Family USB EHCI #1 (rev 05)
-  00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
-  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
-  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
-  01:00.0 3D controller: NVIDIA Corporation GK106M [GeForce GTX 765M] (rev a1)
-  03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 
24)
-  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289 
(rev 01)
-  04:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
-  bernardo@G1711:~$
+ I'm running Xubuntu 12.04 on an AVELL notebook model G1711 (avell dot com dot 
br). I did not install NVidia Driver, running only intel's integrated video 
interface (i5 Haswell).  However, when it suspends due to inactivity timeout or 
if I ask it to enter in suspension (not hibernation) i freezes out. The only 
way to use the machine again is by pressing on/off button up to shutting the 
machine off, and then restarting it again.
+ I upgraded to KERNEL 3.12-SAUCY, have Oracle Java JDK 7 and Oracle VirtualBox 
installed.
+ Initially it presented ...done in upper left corner and nothing more. Once 
it said also in upper left corner something like Loading Virtualbox kernel [ok] 
and froze up.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-52-generic 3.2.0-52.78
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic x86_64
  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 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
-Subdevices: 2/2
-Subdevice #0: subdevice #0
-Subdevice #1: subdevice #1
+   List of CAPTURE Hardware Devices 
+  card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
+    Subdevices: 2/2
+    

[Kernel-packages] [Bug 1225571] Re: WARNING: CPU: 0 PID: 1529 at /build/buildd/linux-3.11.0/kernel/softirq.c:159 local_bh_enable+0x60/0x90()

2013-12-06 Thread Christopher M. Penalver
** 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/1225571

Title:
  WARNING: CPU: 0 PID: 1529 at
  /build/buildd/linux-3.11.0/kernel/softirq.c:159
  local_bh_enable+0x60/0x90()

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  After updating my system from raring to saucy it was crashing during
  boot. After some digging I realised that it is connected to the
  network interfaces. After removing the auto line for the two network
  interfaces in /etc/network/interfaces the system boots successfully.

  If one then tries to bring up the network interface using the
  via_velocity driver (using ifup) the system crashes and the following
  message appears in syslog:

  Sep 15 02:25:24 nas dhclient: Internet Systems Consortium DHCP Client 4.2.4
  Sep 15 02:25:24 nas dhclient: Copyright 2004-2012 Internet Systems Consortium.
  Sep 15 02:25:24 nas dhclient: All rights reserved.
  Sep 15 02:25:24 nas dhclient: For info, please visit 
https://www.isc.org/software/dhcp/
  Sep 15 02:25:24 nas dhclient: 
  Sep 15 02:25:25 nas kernel: [   81.953639] Velocity is AUTO mode
  Sep 15 02:25:25 nas dhclient: Listening on LPF/eth0/00:40:63:f5:15:76
  Sep 15 02:25:25 nas dhclient: Sending on   LPF/eth0/00:40:63:f5:15:76
  Sep 15 02:25:25 nas dhclient: Sending on   Socket/fallback
  Sep 15 02:25:25 nas dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 
interval 3 (xid=0x4ff0e6ad)
  Sep 15 02:25:26 nas kernel: [   83.462216] eth0: Link auto-negotiation speed 
100M bps full duplex
  Sep 15 02:25:28 nas dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 
interval 3 (xid=0x4ff0e6ad)
  Sep 15 02:25:29 nas kernel: [   86.675203] [ cut here 
]
  Sep 15 02:25:29 nas kernel: [   86.675227] WARNING: CPU: 0 PID: 1529 at 
/build/buildd/linux-3.11.0/kernel/softirq.c:159 local_bh_enable+0x60/0x90()
  Sep 15 02:25:29 nas kernel: [   86.675231] Modules linked in: 
snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) 
snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) via_cputemp 
snd_rawmidi(F) snd_seq(F) snd_seq_device(F) snd_timer(F) i2c_viapro psmouse(F) 
serio_raw(F) snd(F) soundcore(F) shpchp mac_hid hwmon_vid lp(F) parport(F) 
binfmt_misc(F) raid10(F) raid1(F) raid0(F) multipath(F) linear(F) dm_crypt(F) 
via_rng raid456(F) async_raid6_recov(F) async_memcpy(F) async_pq(F) 
async_xor(F) async_tx(F) xor(F) raid6_pq(F) pata_acpi padlock_sha padlock_aes 
pata_via via_velocity via_rhine mii(F) ahci(F) libahci(F) crc_ccitt(F)
  Sep 15 02:25:29 nas kernel: [   86.675315] CPU: 0 PID: 1529 Comm: SpiderOak 
Tainted: GF3.11.0-7-generic #13-Ubuntu
  Sep 15 02:25:29 nas kernel: [   86.675320] Hardware name: To Be Filled By 
O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080014  12/18/2007
  Sep 15 02:25:29 nas kernel: [   86.675324]    ee803ce8 
c16313c4  ee803d18 c105268e c1805af4
  Sep 15 02:25:29 nas kernel: [   86.675336]   05f9 c1805dc8 
009f c1056b50 c1056b50 c19566c0 efbafb80
  Sep 15 02:25:29 nas kernel: [   86.675347]   ee803d28 c1052752 
0009  ee803d30 c1056b50 ee803d4c
  Sep 15 02:25:29 nas kernel: [   86.675359] Call Trace:
  Sep 15 02:25:29 nas kernel: [   86.675371]  [c16313c4] dump_stack+0x41/0x52
  Sep 15 02:25:29 nas kernel: [   86.675379]  [c105268e] 
warn_slowpath_common+0x7e/0xa0
  Sep 15 02:25:29 nas kernel: [   86.675387]  [c1056b50] ? 
local_bh_enable+0x60/0x90
  Sep 15 02:25:29 nas kernel: [   86.675394]  [c1056b50] ? 
local_bh_enable+0x60/0x90
  Sep 15 02:25:29 nas kernel: [   86.675401]  [c1052752] 
warn_slowpath_null+0x22/0x30
  Sep 15 02:25:29 nas kernel: [   86.675409]  [c1056b50] 
local_bh_enable+0x60/0x90
  Sep 15 02:25:29 nas kernel: [   86.675421]  [c155f1ea] dst_alloc+0x12a/0x140
  Sep 15 02:25:29 nas kernel: [   86.675431]  [c158189d] 
rt_dst_alloc+0x4d/0x60
  Sep 15 02:25:29 nas kernel: [   86.675440]  [c1583fdc] 
ip_route_input_noref+0x2bc/0xa30
  Sep 15 02:25:29 nas kernel: [   86.675448]  [c107c504] ? 
resched_task+0x24/0x70
  Sep 15 02:25:29 nas kernel: [   86.675456]  [c107cfd8] ? 
ttwu_do_wakeup+0x18/0x100
  Sep 15 02:25:29 nas kernel: [   86.675464]  [c1585b4b] 
ip_rcv_finish+0xbb/0x340
  Sep 15 02:25:29 nas kernel: [   86.675471]  [c1586414] ip_rcv+0x254/0x3c0
  Sep 15 02:25:29 nas kernel: [   86.675479]  [c1558217] 
__netif_receive_skb_core+0x557/0x730
  Sep 15 02:25:29 nas kernel: [   86.675487]  [c1558406] 
__netif_receive_skb+0x16/0x60
  Sep 15 02:25:29 nas kernel: [   86.675494]  [c155846f] 
netif_receive_skb+0x1f/0x80
  Sep 15 02:25:29 nas kernel: [   86.675516]  [f845e7ab] 
velocity_rx_srv+0x2ab/0x410 [via_velocity]
  Sep 15 02:25:29 nas kernel: [   86.675525]  [c13dfa19] ? 
__mix_pool_bytes+0x39/0x80
  Sep 15 02:25:29 nas kernel: [   86.675534]  [c1014790] ? 

[Kernel-packages] [Bug 1050352] Re: [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects and connects

2013-12-06 Thread Tareeq
Sure, but should I be booting into the 3.11 ubuntu kernel when I run
that command?  Currently I get an error saying I am running a main line
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/1050352

Title:
  [Gigabyte P55A-UD4] External USB 3.0 hard drive randomly disconnects
  and connects

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 12.10 AMD64, kernel 3.5.0-14.16.
  External hard drive Hitachi Touro Desk 3.0 connected to USB 3.0 port.

  Gets disconnected randomly and then connected again. Only happens with
  USB 3.0 connection (xhci).

  WORKAROUND: When plugged to USB 2.0 (ehci) port it works ok.

  Attached is related kernel log portion: there is nothing special there
  except for these lines:

  11-2: Parent hub missing LPM exit latency info.  Power management will be 
impacted.
  usb 11-2: USB disconnect, device number 2
  ---
  AcpiTables: Error: command ['pkexec', 
'/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error 
executing /usr/share/apport/dump_acpi_tables.py: Permission denied
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dmitry 3011 F pulseaudio
   /dev/snd/controlC1:  dmitry 3011 F pulseaudio
   /dev/snd/controlC0:  dmitry 3011 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e3fa02f8-4f15-4f00-9d79-e982d4837b5c
  IwConfig:
   vboxnet0  no wireless extensions.

   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD4
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic 
root=UUID=33c3405d-4b3c-4b5c-a1c3-fd2c7bad1c79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-14-generic N/A
   linux-backports-modules-3.5.0-14-generic  N/A
   linux-firmware1.91
  RfKill:

  Tags:  quantal running-unity
  Uname: Linux 3.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-09-07 (6 days ago)
  UserGroups: adm cdrom dialout fuse kvm libvirtd lpadmin plugdev pulse 
pulse-access sambashare sudo vboxusers wireshark
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P55A-UD4
  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.:bvrF14:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1050352/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235967] Re: LENOVO JiaYueE1457 suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235967

Title:
   LENOVO JiaYueE1457  suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  开机自动出现这个 错误报告提示

  Boot prompt automatically appears this error report

  http://translate.google.cn/?hl=en#zh-
  
CN/en/%E5%BC%80%E6%9C%BA%E8%87%AA%E5%8A%A8%E5%87%BA%E7%8E%B0%E8%BF%99%E4%B8%AA%20%E9%94%99%E8%AF%AF%E6%8A%A5%E5%91%8A%E6%8F%90%E7%A4%BA

  ProblemType: KernelOops
  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
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fuhaoyun   1542 F pulseaudio
   /dev/snd/controlC0:  fuhaoyun   1542 F pulseaudio
  CurrentDmesg: [   28.630318] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
  Date: Fri Oct  4 21:21:07 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=baec8455-5976-4592-84f4-60086f8caff6
  InstallationDate: Installed on 2013-09-29 (6 days ago)
  InstallationMedia: UbuntuKylin 13.10 Saucy Salamander - Beta amd64 
(20130928)
  InterpreterPath: /usr/bin/python3.3
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO JiaYueE1457
  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-11-generic 
root=UUID=f2272dd7-215a-4906-b3ef-01228e5838a8 ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  SourcePackage: linux
  Title: [LENOVO JiaYueE1457] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/30/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D2KT34AUS
  dmi.board.name: Tilapia CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: INVALID
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrD2KT34AUS:bd07/30/2011:svnLENOVO:pnJiaYueE1457:pvrLenovo:rvnLENOVO:rnTilapiaCRB:rvrINVALID:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: JiaYueE1457
  dmi.product.version: Lenovo
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235967/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235700] Re: [Dell Inc. Latitude E5520] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235700

Title:
  [Dell Inc. Latitude E5520] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  on boot

  ProblemType: KernelOops
  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
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leo2684 F pulseaudio
  Date: Sat Oct  5 10:42:34 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=77df490c-aa38-42ba-b95b-3043b8a22b1a
  InstallationDate: Installed on 2012-10-20 (349 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Dell Inc. Latitude E5520
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=76731a60-f6be-456c-95a2-c89349c0288d ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  Title: [Dell Inc. Latitude E5520] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-09-29 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 07/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0KCT5J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd07/14/2013:svnDellInc.:pnLatitudeE5520:pvr01:rvnDellInc.:rn0KCT5J:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5520
  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/1235700/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1236070] Re: [Hewlett-Packard HP EliteBook 2540p] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1236070

Title:
  [Hewlett-Packard HP EliteBook 2540p] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I do not know

  ProblemType: KernelOops
  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
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chronos2882 F pulseaudio
   /dev/snd/seq:timidity   2445 F timidity
  Date: Sun Oct  6 10:06:04 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=04ed5b63-13e3-45ab-b507-9bc78dc47ec4
  InterpreterPath: /usr/bin/python3.3
  MachineType: Hewlett-Packard HP EliteBook 2540p
  MarkForUpload: True
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=ce687e86-5c13-47e0-8e91-faab1a4e8c5c ro rootfstype=btrfs 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 
drm.vblankoffdelay=1 pcie_aspm=force
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  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
  Title: [Hewlett-Packard HP EliteBook 2540p] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-09-28 (8 days ago)
  UserGroups:
   
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CSU Ver. F.23
  dmi.board.name: 7008
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 38.34
  dmi.chassis.asset.tag: CZC1165484
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CSUVer.F.23:bd03/08/2013:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 2540p
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1236070/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1236208] Re: [LENOVO 4291IR6] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1236208

Title:
  [LENOVO 4291IR6] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  crashed while file copy from cd to hdd

  ProblemType: KernelOops
  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
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anonymous   2604 F pulseaudio
  Date: Mon Oct  7 08:00:29 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2013-05-17 (142 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 4291IR6
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=a586a1ae-b9b1-4359-b3f5-e8dd0756ec57 ro acpi_osi=Linux 
i915.i915_enable_rc6=1 pcie_aspm=force i915.lvds_downclock=1 
i915.i915_enable_fbc=1 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  Title: [LENOVO 4291IR6] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291IR6
  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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291IR6:pvrThinkPadX220:rvnLENOVO:rn4291IR6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291IR6
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1236208/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1258715] Re: Waking up from suspension freezes up the system

2013-12-06 Thread Christopher M. Penalver
Bernardo Ramos, thank you for reporting this and helping make Ubuntu
better. It would appear your laptop is a Clevo W35xSTQ_370ST. Hence, it
would appear that you may have a BIOS update available, as suggested by
the following *unofficial* resource http://repo.palkeo.com/clevo-
mirror/W3xxST/ . If you contact Avell and/or Clevo directly, would they
provide you with a official BIOS to upgrade with?

** Changed in: linux (Ubuntu)
   Importance: Undecided = Medium

** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

** Tags removed: trusty
** Tags added: needs-bios-check needs-upstream-testing regression-potential 
resume suspend

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258715

Title:
  Waking up from suspension freezes up the system

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I'm running Xubuntu 12.04 on an AVELL notebook model G1711 (avell dot com dot 
br). I did not install NVidia Driver, running only intel's integrated video 
interface (i5 Haswell).  However, when it suspends due to inactivity timeout or 
if I ask it to enter in suspension (not hibernation) i freezes out. The only 
way to use the machine again is by pressing on/off button up to shutting the 
machine off, and then restarting it again.
  I upgraded to KERNEL 3.12-SAUCY, have Oracle Java JDK 7 and Oracle VirtualBox 
installed.
  Initially it presented ...done in upper left corner and nothing more. Once 
it said also in upper left corner something like Loading Virtualbox kernel [ok] 
and froze up.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-52-generic 3.2.0-52.78
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic x86_64
  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 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bernardo   1815 F pulseaudio
    bernardo   1858 F xfce4-volumed
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7a14000 irq 45'
     Mixer name : 'Generic  ID 0'
     Components : 'HDA:,80860101,0010'
     Controls  : 0
     Simple ctrls  : 0
  Card0.Amixer.values:

  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7a1 irq 45'
     Mixer name : 'VIA VT1802'
     Components : 'HDA:11068446,15583537,0010'
     Controls  : 32
     Simple ctrls  : 19
  Date: Fri Dec  6 23:55:47 2013
  HibernationDevice: RESUME=UUID=164435ef-5b54-4926-b6d0-89a6df38eff5
  InstallationMedia: Xubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820)
  MachineType: Notebook W35xSTQ_370ST
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=pt_BR:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-52-generic 
root=UUID=0ea5cb5c-40a7-4d61-a147-19e88323e804 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-52-generic N/A
   linux-backports-modules-3.2.0-52-generic  N/A
   linux-firmware1.79.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W35xSTQ_370ST
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/04/2013:svnNotebook:pnW35xSTQ_370ST:pvrNotApplicable:rvnNotebook:rnW35xSTQ_370ST:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W35xSTQ_370ST
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258715/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235671] Re: [LENOVO 7667WHE] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235671

Title:
  [LENOVO 7667WHE] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  111

  ProblemType: KernelOops
  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 i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  conetek1277 F pulseaudio
  Date: Sat Oct  5 16:00:30 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=198b0ceb-7401-47c0-971a-4d55e496d371
  InstallationDate: Installed on 2013-10-02 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 7667WHE
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=813963b9-9b29-4cca-ba14-5f43c900bda4 ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [LENOVO 7667WHE] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-10-03 (1 days ago)
  UserGroups:
   
  dmi.bios.date: 10/09/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETC1WW (2.21 )
  dmi.board.name: 7667WHE
  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:bvr7NETC1WW(2.21):bd10/09/2009:svnLENOVO:pn7667WHE:pvrThinkPadX61s:rvnLENOVO:rn7667WHE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7667WHE
  dmi.product.version: ThinkPad X61s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235671/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235789] Re: [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235789

Title:
  [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  login and the bug message

  ProblemType: KernelOops
  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
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ron1709 F pulseaudio
   /dev/snd/controlC0:  ron1709 F pulseaudio
  Date: Sat Oct  5 17:46:49 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=46c11e5a-143b-4144-8f2d-f234d571bce7
  InstallationDate: Installed on 2013-09-20 (15 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  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-11-generic 
root=UUID=3d3e033d-ebcd-42f9-a650-2c0c6ae9d09f ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-09-21 (13 days ago)
  UserGroups:
   
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr05941124321620100:rvnHewlett-Packard:rn143F:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 05941124321620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235789/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235693] Re: [ASRock Z68M-ITX/HT] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235693

Title:
  [ASRock Z68M-ITX/HT] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  System error msg showed just about booting and seeing the desktop.

  ProblemType: KernelOops
  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
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  frank  1612 F pulseaudio
   /dev/snd/controlC0:  frank  1612 F pulseaudio
  Date: Wed Oct  2 15:17:29 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=abd9b257-a183-46a4-98d7-1a39684e16b6
  InstallationDate: Installed on 2013-09-12 (22 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130909)
  InterpreterPath: /usr/bin/python3.3
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=59c28417-1603-48e5-b719-3a65fdd10255 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  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
  RfKill:
   
  SourcePackage: linux
  Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z68M-ITX/HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/24/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68M-ITX/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235693/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1236183] Re: [Gigabyte Technology Co., Ltd. H61N-USB3] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1236183

Title:
  [Gigabyte Technology Co., Ltd. H61N-USB3] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  The PC not wake up from suspend mode

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-11-generic 3.11.0-11.17 [modified: 
boot/vmlinuz-3.11.0-11-generic]
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stoyan 1695 F pulseaudio
  Date: Mon Oct  7 09:34:18 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=5facfadc-92f6-4e86-82d5-55ec3f85a846
  InstallationDate: Installed on 2013-10-05 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131005)
  InterpreterPath: /usr/bin/python3.3
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H61N-USB3
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  SourcePackage: linux
  Title: [Gigabyte Technology Co., Ltd. H61N-USB3] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: H61N-USB3
  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.:bvrF8:bd05/15/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61N-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61N-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H61N-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1236183/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1236018] Re: [System manufacturer System Product Name] suspend/resume failure [non-free: fglrx]

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1236018

Title:
  [System manufacturer System Product Name] suspend/resume failure [non-
  free: fglrx]

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  

  ProblemType: KernelOops
  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
  NonfreeKernelModules: fglrx
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hunter 2091 F pulseaudio
   /dev/snd/controlC0:  hunter 2091 F pulseaudio
  Date: Sun Oct  6 20:46:47 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=d4acfc9b-4092-4361-9cd6-42db5c012fca
  InstallationDate: Installed on 2013-09-17 (18 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917)
  InterpreterPath: /usr/bin/python3.3
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=91341513-b713-4950-8078-1f285aa05dcc ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [System manufacturer System Product Name] suspend/resume failure 
[non-free: fglrx]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1601
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Rampage III Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1601:bd01/03/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIIExtreme:rvrRev1.xx: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/1236018/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235871] Re: [LENOVO 766313G] late resume failure [non-free: nvidia]

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235871

Title:
  [LENOVO 766313G] late resume failure [non-free: nvidia]

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  happend on startup after login.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-11-generic 3.11.0-11.17
  ProcVersionSignature: Ubuntu 3.11.0-11.4-lowlatency 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.  The resume processing hung very near the end and will have 
appeared to have completed normally.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  markus 2542 F pulseaudio
   /dev/snd/controlC10: markus 2542 F pulseaudio
  Date: Sat Oct  5 14:22:11 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: late resume
  HibernationDevice: RESUME=UUID=c85784a3-80e1-4b3a-af49-682771b3cd3a
  InstallationDate: Installed on 2013-02-25 (222 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  InterpreterPath: /usr/bin/python3.3
  MachineType: LENOVO 766313G
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-lowlatency 
root=UUID=80814815-6eb5-4cae-894b-656f40aeb3a4 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-11-lowlatency N/A
   linux-backports-modules-3.11.0-11-lowlatency  N/A
   linux-firmware1.116
  SourcePackage: linux
  Title: [LENOVO 766313G] late resume failure [non-free: nvidia]
  UpgradeStatus: Upgraded to saucy on 2013-10-04 (1 days ago)
  UserGroups:
   
  dmi.bios.date: 11/14/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC5WW (2.25 )
  dmi.board.name: 766313G
  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:bvr7LETC5WW(2.25):bd11/14/2008:svnLENOVO:pn766313G:pvrThinkPadT61:rvnLENOVO:rn766313G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 766313G
  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/1235871/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235931] Re: [Dell Inc. Latitude E6500] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235931

Title:
  [Dell Inc. Latitude E6500] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Not sure what to say. I don't think I've used suspend yesterday or
  tomorrow, but perhaps somebody smart can understand that error report.

  ProblemType: KernelOops
  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
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wojtek 2461 F pulseaudio
  Date: Sun Oct  6 13:17:09 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2250a990-a3e5-4cd3-8f8c-34f4d13246dd
  InstallationDate: Installed on 2013-09-29 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Dell Inc. Latitude E6500
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash reboot=warm vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  Title: [Dell Inc. Latitude E6500] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0NY667
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd12/06/2011:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235931/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1235750] Re: 046d:0896 [Acer Aspire 5630] Webcam displays green screen only

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235750

Title:
  046d:0896 [Acer Aspire 5630] Webcam displays green screen only

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  On skype options the camera displays green screen only. It is detected
  but doesnt work.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-30-generic 3.8.0-30.44
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stergios   1908 F pulseaudio
  Date: Sat Oct  5 22:04:00 2013
  HibernationDevice: RESUME=UUID=8bf26f59-a7db-4ad3-807f-689b39aaf928
  InstallationDate: Installed on 2013-06-02 (125 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: Acer Aspire 5630
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic 
root=UUID=dea2dfea-657f-4b9c-9a4a-7d7a2ac1b66a ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-30-generic N/A
   linux-backports-modules-3.8.0-30-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.60
  dmi.board.name: Grapevine
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.60:bd08/12/2008:svnAcer:pnAspire5630:pvrV3.60:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5630
  dmi.product.version: V3.60
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235750/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1236005] Re: [FUJITSU SIEMENS LIFEBOOK S7210] suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1236005

Title:
  [FUJITSU SIEMENS LIFEBOOK S7210] suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
   The release of Ubuntu you are using: - 13.10 final beta.
   2) The version of the package you are using, not known
   3) What you expected to happen - No errors appearing on startup
   4) What happened instead - Errors appeared.  No other noticeable side effect.

  ProblemType: KernelOops
  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 i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pete   3145 F pulseaudio
  Date: Sun Oct  6 17:55:41 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=f8fa-8108-49b6-b43b-d8f5d7d31742
  InstallationDate: Installed on 2013-05-05 (154 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MachineType: FUJITSU SIEMENS LIFEBOOK S7210
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=5882ad1e-324c-409a-a049-b3f50a2c8606 ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  Title: [FUJITSU SIEMENS LIFEBOOK S7210] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-10-02 (3 days ago)
  UserGroups:
   
  dmi.bios.date: 05/02/2008
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.08
  dmi.board.name: FJNB1DB
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: S7210
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd05/02/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7210:pvr:rvnFUJITSU:rnFJNB1DB:rvr:cvnFUJITSUSIEMENS:ct10:cvrS7210:
  dmi.product.name: LIFEBOOK S7210
  dmi.sys.vendor: FUJITSU SIEMENS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1236005/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1236597] Re: suspend/resume failure

2013-12-06 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1236597

Title:
  suspend/resume failure

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Automatic bug reporting 'Ubuntu has experienced a problem...'

  Ubuntu 13.10

  ProblemType: KernelOops
  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 i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   7007 F pulseaudio
  CurrentDmesg:
   [  508.608161] audit_printk_skb: 144 callbacks suppressed
   [  508.608169] type=1400 audit(1381177173.536:72): apparmor=STATUS 
operation=profile_replace parent=6623 profile=unconfined 
name=/usr/lib/cups/backend/cups-pdf pid=6627 comm=apparmor_parser
   [  508.608186] type=1400 audit(1381177173.536:73): apparmor=STATUS 
operation=profile_replace parent=6623 profile=unconfined 
name=/usr/sbin/cupsd pid=6627 comm=apparmor_parser
   [  508.609238] type=1400 audit(1381177173.536:74): apparmor=STATUS 
operation=profile_replace parent=6623 profile=unconfined 
name=/usr/sbin/cupsd pid=6627 comm=apparmor_parser
  Date: Mon Oct  7 21:11:54 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=9c6b5294-3e42-4721-a9a3-b4c8e09bcc57
  InstallationDate: Installed on 2013-10-02 (5 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  InterpreterPath: /usr/bin/python3.3
  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 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  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-11-generic 
root=UUID=c9c3c917-7076-4c26-89cd-f8c793e223cd ro 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-11-generic N/A
   linux-backports-modules-3.11.0-11-generic  N/A
   linux-firmware 1.116
  RfKill:
   
  SourcePackage: linux
  Title: suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-10-02 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 06/19/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: nVidia-nForce
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/19/2004:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1236597/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   >