[Kernel-packages] [Bug 1220146] Re: Need support for new Ralink Wifi card - Mediatek 7630 [14c3:7630]
I'm new in Linux world, everything what for you very simple is for me is willy hard. I have wifi working but bluetooth work not, visibility I can't turn on, over usb bluetooth working fine. Laptop is asus x552v, for asus-bluetooth in terminal softblocked say no, hardblocked no?! I have Linux Mint 17 installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1220146 Title: Need support for new Ralink Wifi card - Mediatek 7630 [14c3:7630] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Raring: Incomplete Status in “linux” source package in Saucy: Incomplete Status in “linux” package in Fedora: New Bug description: This device is appearing in some OEM machines, but driver is not yet available in mainline. The driver seems to be present in machines with pre-installed OS, but isn't available on the download-and-install versions! To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1220146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350480] Re: [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in
Thanks for the test kernels, Joe. Looks like we've bisected the offending commit down to 1f81b6d22a5980955b01e08cf27fb745dc9b686f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350480 Title: [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Precise: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress Bug description: The latest kernel update in Ubuntu 14.04 LTS (3.13.0-32.57) renders our Intel NUCs unbootable, when we cold boot and have USB devices (keyboard, mouse, USB/Ethernet adapter) connected. The 3.13.0-24.47 kernel does not exhibit this behavior. Our particular NUCs have the i5-3427U processor, which is the D53427RKE board (DC53427HYE kit). These reports seem to be related: http://support.sundtek.com/index.php/topic,1600.0.html http://en.it-usenet.org/thread/19505/17700/ --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1400 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=37e4ff56-b945-4604-a94d-557bdf83e0b2 InstallationDate: Installed on 2014-07-30 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=c0597da2-7d4a-4340-b85a-c7f96d8262d7 ro ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2013 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0017.2013.0425.1251 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87790-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0017.2013.0425.1251:bd04/25/2013:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87790-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter
Confirmed on 14.10 alpha Fix in #23 still working. hci0: Type: BR/EDR Bus: USB BD Address: BC:77:37:D5:9F:89 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:1364783 acl:46087 sco:0 events:89396 errors:0 TX bytes:29127367 acl:132937 sco:0 commands:229 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: HOLD SNIFF PARK Link mode: ACCEPT MASTER Name: 'Dell-System-Vostro-3450-0' Class: 0x7c0100 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Uncategorized HCI Version: 3.0 (0x5) Revision: 0x1b07 LMP Version: 3.0 (0x5) Subversion: 0x0 Manufacturer: Intel Corp. (2) a2dp audio device - Motorola HT820 mouse - Apple A1197 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/424215 Title: Bluetooth mouse usage makes A2DP audio stutter Status in “bluez” package in Ubuntu: Fix Released Bug description: Binary package hint: bluez When I use my Bluetooth A2DP headset (Philips SHB7102) together with my mouse (Lenovo Bluetooth Laser Mouse), I notice this: Whenever I leave the mouse still for a few seconds (it seems to enter some kind of lower-power-mode) and then start to move it, my music most of the time skips for a second. This makes using these two bluetooth devices together quite annoying... The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.) I am running current karmic amd64 (linux 2.6.31-9). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.
Same on Asus X54HY (X54LY) Ubuntu 14.04.1 I: Bus=0011 Vendor=0002 Product=000e Version= N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input11 U: Uniq= H: Handlers=mouse0 event4 B: PROP=1 B: EV=b B: KEY=6420 3 0 0 0 0 B: ABS=26080001103 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1166442 Title: Elantech clickpad/touchpad lacks multitouch features. Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux” package in Arch Linux: New Bug description: Newer versions of the Elantech multitouch trackpad are not fully supported in Linux. These appear in many of the newer Samsung laptops, for example. elantech.c in the kernel needs to be updated to support these models (up to v7 perhaps?) This bug is confirmed to affect a range of samsung laptops running Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current (3.9) upstream kernel. A dkms package was produced in 2011 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64) which may fix certain older laptops affected by this issue, but doesn't fix newer models. == Original Report == Hello, So far I've been having a problem with my Elantech multitouch trackpad in Linux. Basically all i get is right click, left click, and tap to click, along with basic movement. The problem seems to be rooted in improper detection of the trackpad, likely b/c its a new revision or whatnot. Of note is that working elantech trackpads of the past in forums i scouted through show up as "ETPS/2 Elantech Touchpad". Mine just shows up in xinput as "PS/2 Elantech Touchpad". I think this might be a simple fix in the end, just improper detection, I hope. For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on Ubuntu 13.04 thus far, with all combinations of psmouse. -- What's expected: touchpad multitouch support What happened: basic touchpad support Laptop mode: Samsung Series 7 NP780 series Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04 Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and psmouse-alps-dst. No improvements so removed. synclient -l reports "Couldn't find synaptics properties. No synaptics driver loaded?" -- See attached for more info. Ask anything you need! --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gscoppino 2272 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d InstallationDate: Installed on 2013-04-06 (3 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.104 StagingDrivers: rts5139 Tags: raring staging Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03ABU.139.130226.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP780Z5E-S01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 770Z5E/780Z5E/870Z5E/
[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect on paravirtual EC2 instances.
I had a dream... well honestly this idea came to me around then. So I was fishing in the same availability zone to get another case of this (was not sure I could just go back to yours). Then installed a 12.04 (3.2.x) kernel and bingo, same problem. So at least I can stop trying to think of a way the changes between 3.2 and 3.13 may have caused this. And the reason I added the comment about the observation that it may not happen initially but then on a reboot and after that on every reboot was this: I have the feeling that the uptime of the host also is one part of the equation. So this seems: - Intel CPU, the nonstop_tsc of the E5-2650 might be something to look at - A certain uptime of the host - Maybe the tsc/systime related code in the hypervisor Well, it could also be independent of the CPU and only rely on the uptime and it is just pure bad luck that the only hosts we currently find are of a certain type. Only way to prove or bust this would be to find a unaffected guest showing an uptime of those 58 days. Figuring out the involvement of the hypervisor code is nearly impossible as Amazon uses a special version of 3.4.3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-
[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
Hi, additional i did a few "system" upgrades too. (may thats why its working for me) My system : dell poweredge R815 BIOS version 3.2.1 Firmware: 1.96 (Build 01) uname -a Linux hostname 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux now some ethtool infos: ethtool -i 10gbiface driver: ixgbe version: 3.15.1-k firmware-version: 0x546c0001 bus-info: :22:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no If you also have a dell try to upgrade the firmware. p.s. you can write me an email, i have some "helpfull" upgrade - links :-D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: "Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don" If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349028] Re: getitimer returns it_value=0 erroneously
SRU Justification:
Impact:
The CONFIG_CONTEXT_TRACKING_FORCE should be disabled for
various reasons:
1. As described in the Kconfig "this option brings an
overhead that you don't want in production" and also
"Say Y only if you're working on the development of an
architecture backend for the context tracking."
Clearly for production kernel we should disable this.
2. Disabling this option also fixes bug LP:#1349028.
Testcase:
According to the getitimer() man page: "The element
it_value is set to the amount of time remaining on
the timer, or zero if the timer is disabled. Similarly,
it_interval is set to the reset value."
The following perl script should never exit:
use Time::HiRes;
$SIG{VTALRM} = sub { };
Time::HiRes::setitimer(&Time::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
while (1) {
my @t = Time::HiRes::getitimer(&Time::HiRes::ITIMER_VIRTUAL);
exit 0 if $t[0] == 0;
}
With this config change the correct behaviour occurs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349028
Title:
getitimer returns it_value=0 erroneously
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
According to the 'getitimer()' man page: "The element it_value is set
to the amount of time remaining on the timer, or zero if the timer is
disabled. Similarly, it_interval is set to the reset value."
As such the following Perl program should never exit:
use Time::HiRes;
$SIG{VTALRM} = sub { };
Time::HiRes::setitimer(&Time::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
while (1) {
my @t = Time::HiRes::getitimer(&Time::HiRes::ITIMER_VIRTUAL);
exit 0 if $t[0] == 0;
}
and on linux-image 3.11.0-18-generic (and all other systems tested) it
loops forever but 3.13.0-32-generic it exits. Have not bisected
between those kernels, nor am I likely to be able to do so soon.
This Perl program shows the timer countdown:
use Time::HiRes;
my $r = [Time::HiRes::gettimeofday()];
sub display {
my ($desc) = @_;
my @t = Time::HiRes::getitimer(&Time::HiRes::ITIMER_VIRTUAL);
my $i = Time::HiRes::tv_interval($r);
printf "%s: elasped=%.8f; time left=%.6f reset time=%.6f\n", $desc,
$i,@t;
}
$SIG{VTALRM} = sub {
display('VTALRM');
exit;
};
Time::HiRes::setitimer(&Time::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
while (1) {
display('inloop');
}
on other (working) systems it gives:
inloop: elasped=1.65178400; time left=0.001000 reset time=0.401000
inloop: elasped=1.65184200; time left=0.001000 reset time=0.401000
inloop: elasped=1.65186800; time left=0.001000 reset time=0.401000
inloop: elasped=1.65192300; time left=0.001000 reset time=0.401000
inloop: elasped=1.65198100; time left=0.001000 reset time=0.401000
VTALRM: elasped=1.65209800; time left=0.40 reset time=0.401000
(end of file)
but on the 3.13.0-32-generic or later kernel I get:
inloop: elasped=0.54692100; time left=0.33 reset time=0.40
inloop: elasped=0.54692800; time left=0.26 reset time=0.40
inloop: elasped=0.54693500; time left=0.20 reset time=0.40
inloop: elasped=0.54694100; time left=0.13 reset time=0.40
inloop: elasped=0.54694800; time left=0.07 reset time=0.40
inloop: elasped=0.54695500; time left=0.00 reset time=0.40
inloop: elasped=0.54696200; time left=0.004000 reset time=0.40
[...]
VTALRM: elasped=0.55013600; time left=0.397062 reset time=0.40
(end of file)
The reset time also looks dodgy.
Hardware is an Intel Core i7-920 on Asus P6T Deluxe v2 (X58)
motherboard and hasn't changed.
Requested information:
Ubuntu 3.13.0-32.57-generic 3.13.11.4
Description: Ubuntu 14.04.1 LTS
Release: 14.04
# apt-cache policy linux-image-generic
linux-image-generic:
Installed: 3.13.0.32.38
Candidate: 3.13.0.32.38
Version table:
*** 3.13.0.32.38 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
500 http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/
trusty/main amd64 Packages
100 /var/lib/dpkg/status
3.13.0.24.28 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tivrusky 3009 F pulseaudio
/dev/snd/controlC0: tivrusky 3009 F pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=c026abdc-9fee-425c-b5ae-020bf6ea2ad6
IwConfig:
eth0 no wireless extensions.
eth1 no wireless extensions.
lono wireless extensio
[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest
Commit b7dd0e350e0bd4c0fddcc9b8958342700b00b168 (x86/xen: safely map and unmap grant frames when in atomic context) https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350373 Title: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Bug description: Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while expanding the grant table (usually when requested by blkfront, when booting). See an example trace below. This is caused by calling functions that are unsafe in atomic context. The fix (which has been submitted to 3.16) is available here (also attached): https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable /for-linus-3.16&id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168 The fix is applicable to all kernel since 2.6.39 but only appears to trigger with the 3.13 kernel in 14.04. [2.577876] [ cut here ] [2.577896] kernel BUG at /build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239! [2.577910] invalid opcode: [#1] SMP [2.577922] Modules linked in: [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic #46-Ubuntu [2.577946] task: ec058000 ti: ec09 task.ti: ec09 [2.577955] EIP: 0061:[] EFLAGS: 00010002 CPU: 0 [2.577973] EIP is at enter_lazy.part.1+0x3/0x5 [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50 [2.578001] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660 [2.578027] Stack: [2.578032] ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff edc01000 c1a93018 [2.578052] edc00fff c193ce80 edc01000 [2.578076] ed3ef588 ed3ef588 c1b87b70 ec091ad0 edc01000 c1b65310 1000 [2.578096] Call Trace: [2.578111] [] paravirt_enter_lazy_mmu+0x24/0x30 [2.578127] [] apply_to_page_range+0x1a3/0x310 [2.578141] [] arch_gnttab_map_status+0x38/0x60 [2.578152] [] ? map_pte_fn+0x70/0x70 [2.578166] [] gnttab_map_frames_v2+0xb0/0x100 [2.578182] [] gnttab_map+0x95/0x120 [2.578198] [] ? blk_update_request+0x190/0x340 [2.578209] [] get_free_entries+0xd3/0x280 [2.578221] [] gnttab_alloc_grant_references+0x13/0x30 [2.578238] [] do_blkif_request+0x535/0x6f0 [2.578253] [] ? _raw_spin_unlock_irqrestore+0x1c/0x40 [2.578269] [] __blk_run_queue+0x2e/0x40 [2.578280] [] blk_start_queue+0x25/0x40 [2.578291] [] kick_pending_request_queues+0x1e/0x30 [2.578304] [] blkif_interrupt+0x69f/0x740 [2.578318] [] ? xen_set_pte_at+0xbf/0xf0 [2.578335] [] handle_irq_event_percpu+0x35/0x1a0 [2.578351] [] ? radix_tree_lookup+0xa/0x10 [2.578364] [] handle_irq_event+0x31/0x50 [2.578376] [] handle_edge_irq+0x66/0x110 [2.578389] [] __xen_evtchn_do_upcall+0x1c6/0x2c0 [2.578402] [] xen_evtchn_do_upcall+0x20/0x40 [2.578415] [] xen_do_upcall+0x7/0xc [2.578427] [] ? xen_hypercall_xen_version+0x7/0x20 [2.578441] [] ? xen_force_evtchn_callback+0xf/0x20 [2.578454] [] check_events+0x8/0xc [2.578464] [] ? xen_restore_fl_direct_reloc+0x4/0x4 [2.578480] [] ? xen_batched_set_pte+0xb3/0x160 [2.578493] [] xen_set_pte_at+0x28/0xf0 [2.578505] [] ? __raw_callee_save_xen_pte_val+0x6/0x8 [2.578521] [] copy_pte_range+0x258/0x4c0 [2.578534] [] copy_page_range+0x1d7/0x2e0 [2.578549] [] dup_mm+0x28e/0x4f0 [2.578561] [] copy_process.part.33+0xfa6/0x10d0 [2.578574] [] do_fork+0xc1/0x2c0 [2.578591] [] ? SyS_rt_sigprocmask+0x76/0xa0 [2.578604] [] SyS_clone+0x25/0x30 [2.578615] [] sysenter_do_call+0x12/0x28 [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 <0f> 0b 55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5 [2.578745] EIP: [] enter_lazy.part.1+0x3/0x5 SS:ESP 0069:ec091a50 [2.578765] ---[ end trace ab5b5344be71ca3d ]--- [2.578775] Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
Hi Larry/Michael/everyone, I just bought a Lenovo T540p with the same Realtek 8192EE wifi adapter. I tried both the 2.13.9 patched kernel with the firmware and the newest 2.16rc7 kernel. Both have the same problem: My wifi connects OK but it drops intermittently When I try to ping "www.google.com" in the terminal about 7% pakets gets dropped Just to make sure it's not the internet I ping the router address 192.168.1.1 and same problem. So it's definitely the wifi connection unstable. I have a Cisco M10 router. It may be the router so I played around with the router settings a bit and changing it to "wireless N only" mode seems to help lower the timeout rate a bit but still high compare to the windows 7 results (around 1%) Where can I find the debug logs and give you more information? Also, how do I tweak the paramters? When I execute the modinfo command ERROR: modinfo: could not find module rtl8192ee Thanks in advance! Juan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] Re: Hibernate with fwts will cause hwclock command to time out
apport information ** Tags added: apport-collected staging trusty ** Description changed: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 + --- + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: ubuntu 1587 F pulseaudio + ubuntu 2722 F pulseaudio + /dev/snd/controlC0: ubuntu 1587 F pulseaudio + ubuntu 2722 F pulseaudio + CRDA: + country TW: + (2402 - 2472 @ 40), (3, 27) + (5270 - 5330 @ 40), (3, 17), DFS + (5735 - 5815 @ 40), (3, 30) + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 + InstallationDate: Installed on 2014-07-25 (6 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + MachineType: Dell Inc. Inspiron 5547 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-24-generic N/A + linux-backports-modules-3.13.0-24-generic N/A + linux-firmware 1.127 + StagingDrivers: rts5139 + Tags: trusty staging + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/12/2014 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: X18 + dmi.board.name: 08KNCD + dmi.board.vendor: Dell Inc. + dmi.board.version: X01 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: X18 + dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: + dmi.product.name: Inspiron 5547 + dmi.product.version: X18 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166508/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F..
[Kernel-packages] [Bug 1333569] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166509/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166516/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166517/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166515/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166514/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166512/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166510/+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/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166513/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166511/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166522/+files/WifiSyslog.txt ** 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/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166521/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166520/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166518/+files/PulseList.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/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333569] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1333569/+attachment/4166519/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333569 Title: Hibernate with fwts will cause hwclock command to time out Status in Firmware Test Suite: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: This issue was found in bug 1327075 If you hibernate a system with fwts, and run the hwclock command, the hwclock command will complain that it was unable to access /dev/rtc, you have to reboot the system to have it back to normal. ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 03:31:27 AM EDT -0.875913 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory ubuntu@201401-14542:/dev$ ll rtc lrwxrwxrwx 1 root root 4 Jun 23 04:59 rtc -> rtc0 It can be easily reproduced. ubuntu@201401-14542:~$ fwts -v fwts, Version V14.05.00, 2014-05-07 01:57:17 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio /dev/snd/controlC0: ubuntu 1587 F pulseaudio ubuntu 2722 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c009324a-f03b-4149-a917-82aa1d9d2631 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=71694704-97cb-4de1-ae78-cea0afb095b7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1333569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318218] Re: SATA problems on MacBook Pro 11, 1?
Further to my earlier comment, it seems that these settings don't
entirely eliminate SATA errors. I've tried with both "medium_power" and
"min_power" as settings for the link_power_management_policy, and still
get some errors. They're slightly different, and also less regular;
around 10 every 5 minutes as opposed to once a second on
"max_performance". Here's a sample of the errors produced on
"medium_power". I've added some line breaks to make the difference in
timestamps easier to follow.
[367622.113130] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x404 action
0xe frozen
[367622.113134] ata1.00: irq_stat 0x8040, connection status changed
[367622.113136] ata1: SError: { CommWake DevExch }
[367622.113139] ata1.00: failed command: WRITE DMA EXT
[367622.113143] ata1.00: cmd 35/00:08:80:7b:0d/00:00:16:00:00/e0 tag 24 dma
4096 out
[367622.113143] res 50/00:00:77:3f:ff/00:00:0f:00:00/ef Emask 0x10
(ATA bus error)
[367622.113145] ata1.00: status: { DRDY }
[367622.113148] ata1: hard resetting link
[367622.836250] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[367622.836665] ata1.00: unexpected _GTF length (8)
[367622.837097] ata1.00: unexpected _GTF length (8)
[367622.837103] ata1.00: configured for UDMA/33
[367622.837188] ata1: EH complete
[367668.468555] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x404 action
0xe frozen
[367668.468565] ata1.00: irq_stat 0x8040, connection status changed
[367668.468570] ata1: SError: { CommWake DevExch }
[367668.468578] ata1.00: failed command: READ DMA
[367668.468588] ata1.00: cmd c8/00:08:f8:e6:e0/00:00:00:00:00/ee tag 26 dma
4096 in
[367668.468588] res 50/00:00:a7:e1:4a/00:00:1b:00:00/e0 Emask 0x10
(ATA bus error)
[367668.468594] ata1.00: status: { DRDY }
[367668.468601] ata1: hard resetting link
[367669.192455] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[367669.192953] ata1.00: unexpected _GTF length (8)
[367669.193458] ata1.00: unexpected _GTF length (8)
[367669.193462] ata1.00: configured for UDMA/33
[367669.193568] ata1: EH complete
[367676.039388] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x404 action
0xe frozen
[367676.039393] ata1.00: irq_stat 0x8040, connection status changed
[367676.039396] ata1: SError: { CommWake DevExch }
[367676.039401] ata1.00: failed command: WRITE DMA EXT
[367676.039407] ata1.00: cmd 35/00:08:20:f2:fd/00:00:15:00:00/e0 tag 28 dma
4096 out
[367676.039407] res 50/00:00:07:e3:7d/00:00:12:00:00/e0 Emask 0x10
(ATA bus error)
[367676.039410] ata1.00: status: { DRDY }
[367676.039414] ata1: hard resetting link
[367676.762336] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[367676.762813] ata1.00: unexpected _GTF length (8)
[367676.763339] ata1.00: unexpected _GTF length (8)
[367676.763342] ata1.00: configured for UDMA/33
[367676.763497] ata1: EH complete
[368192.378495] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x404 action
0xe frozen
[368192.378505] ata1.00: irq_stat 0x8040, connection status changed
[368192.378510] ata1: SError: { CommWake DevExch }
[368192.378517] ata1.00: failed command: WRITE DMA
[368192.378528] ata1.00: cmd ca/00:80:10:d9:6a/00:00:00:00:00/ee tag 15 dma
65536 out
[368192.378528] res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10
(ATA bus error)
[368192.378533] ata1.00: status: { DRDY }
[368192.378541] ata1: hard resetting link
[368193.101144] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[368193.101540] ata1.00: unexpected _GTF length (8)
[368193.101964] ata1.00: unexpected _GTF length (8)
[368193.101967] ata1.00: configured for UDMA/33
[368193.102043] ata1: EH complete
[368383.548958] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x404 action
0xe frozen
[368383.548963] ata1.00: irq_stat 0x8040, connection status changed
[368383.548966] ata1: SError: { CommWake DevExch }
[368383.548969] ata1.00: failed command: WRITE DMA EXT
[368383.548973] ata1.00: cmd 35/00:98:e0:60:0f/00:00:16:00:00/e0 tag 30 dma
77824 out
[368383.548973] res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10
(ATA bus error)
[368383.548975] ata1.00: status: { DRDY }
[368383.548979] ata1: hard resetting link
[368384.270310] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[368384.270711] ata1.00: unexpected _GTF length (8)
[368384.271160] ata1.00: unexpected _GTF length (8)
[368384.271166] ata1.00: configured for UDMA/33
[368384.271246] ata1: EH complete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318218
Title:
SATA problems on MacBook Pro 11,1?
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
I installed Ubuntu 14.04 next to MacOS following the guide at
https://help.ubuntu.com/community/MacBookPro11-1/Saucy/
Looking into dmesg, I constantlz get entries like
[ 276.380934] ata1: SError: { PHYRdyChg }
[ 276.380943] ata1: hard resetting link
[ 277.103527] ata1: SATA lin
[Kernel-packages] [Bug 1349879] [NEW] powering off an usb3 device causes kernel to resume immediately after suspend
You have been subscribed to a public bug: After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc) the system immediately resumes after suspend. This does not happen, if I umount the device and disconnect it. Usb devices < 3.0 seem not to be affected. How to reproduce: 1) plug an usb3 device to an usb3 port and mount it 2) umount it 3) power it off: udisksctl power-off -b /dev/sdX 4) suspend: (e.g. echo mem > /sys/power/state) result: system suspends and immediately resumes Package: udisks2 (2.1.3-1) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- powering off an usb3 device causes kernel to resume immediately after suspend https://bugs.launchpad.net/bugs/1349879 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1287811] Re: 168c:0036 [Acer Aspire E1-772G] Bluetooth device not detected
Łukasz Rumin, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1287811 Title: 168c:0036 [Acer Aspire E1-772G] Bluetooth device not detected Status in “linux” package in Ubuntu: Incomplete Bug description: In kernel 3.14 bluetooth sees devices, but has problems with sending (transfer failed 0x4f) files and receiving. Bluetooth long turns on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-bluetooth 3.8.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 18:17:00 2014 ExecutablePath: /usr/bin/bluetooth-wizard InstallationDate: Installed on 2014-03-01 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patryk 1903 F pulseaudio /dev/snd/controlC1: patryk 1903 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [6.911363] init: plymouth-upstart-bridge main process (1181) terminated with status 1 [6.911375] init: plymouth-upstart-bridge main process ended, respawning [7.434646] init: anacron main process (1050) killed by TERM signal DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=65a43c27-c6ed-4daf-b102-089fa5e65681 InstallationDate: Installed on 2014-03-01 (82 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) MachineType: Acer Aspire E1-772G Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=a121d353-840a-4d56-979e-6870e7bf3541 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 Tags: trusty Uname: Linux 3.13.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/28/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HW dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd01/28/2014:svnAcer:pnAspireE1-772G:pvrV1.03:rvnAcer:rnEA70_HW:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-772G dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1287811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
Displacer, thank you for your comment. Unfortunately, this bug report is not scoped to you or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in “linux” package in Ubuntu: Incomplete Bug description: In 14.04 after wakeup from suspend, the notebook screen goes blank while the OS and the hardware is awake (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system). Changeing "quiet splash" to "nomodeset" in /etc/default/grub allows the wakeup, but the pc is really slow (can't be used). WORKAROUND: This problem is not happening with the AMD property drivers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lis
[Kernel-packages] [Bug 1349879] Re: powering off an usb3 device causes kernel to resume immediately after suspend
can you please do "dmesg > /tmp/dmesg.txt" after such a resume and attach /tmp/dmesg.txt here? Thanks! ** Package changed: udisks2 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349879 Title: powering off an usb3 device causes kernel to resume immediately after suspend Status in “linux” package in Ubuntu: Incomplete Bug description: After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc) the system immediately resumes after suspend. This does not happen, if I umount the device and disconnect it. Usb devices < 3.0 seem not to be affected. How to reproduce: 1) plug an usb3 device to an usb3 port and mount it 2) umount it 3) power it off: udisksctl power-off -b /dev/sdX 4) suspend: (e.g. echo mem > /sys/power/state) result: system suspends and immediately resumes Package: udisks2 (2.1.3-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1324261] Re: [SABERTOOTH 990FX R2.0] Log filling with errors
Chris Beresford, could you please test http://cdimage.ubuntu.com/daily- live/current/ and advise if this issue is resolved in it? ** 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/1324261 Title: [SABERTOOTH 990FX R2.0] Log filling with errors Status in “linux” package in Ubuntu: Incomplete Bug description: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x001a address=0x1000 flags=0x] repeating more than once per second. shown on dmesg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-26-generic 3.13.0-26.48 ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11 Uname: Linux 3.13.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 28 22:02:41 2014 HibernationDevice: RESUME=UUID=6de7cec2-3aee-4cb5-8059-efae2c2eb6b9 InstallationDate: Installed on 2014-03-31 (57 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140329) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-26-generic N/A linux-backports-modules-3.13.0-26-generic N/A linux-firmware 1.127.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd11/21/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335475] Re: 8086:08b1 (rev 73) [Dell Vostro 5470] WiFi keeps dropping
** Tags added: needs-upstream-testing regression-potential ** Tags added: needs-wifi-debug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1335475 Title: 8086:08b1 (rev 73) [Dell Vostro 5470] WiFi keeps dropping Status in “linux” package in Ubuntu: Incomplete Bug description: Wifi only works if I'm within 2-3 m from the router. Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Wireless-N 7260 [8086:4462] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoltan 1528 F pulseaudio /dev/snd/controlC1: zoltan 1528 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 28 20:20:25 2014 HibernationDevice: RESUME=UUID=37e4a4dd-23aa-4f64-9819-ad9ac81ce00a InstallationDate: Installed on 2014-05-17 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 5470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=UUID=4113e76e-862f-4e4e-88c5-ccb82732ef5a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0G5M5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/06/2013:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0G5M5F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333487] Re: [ASUS ZENBOOK UX32VD] Wifi failure to connect regression.
guysoft, please again see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333487/comments/7 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1333487 Title: [ASUS ZENBOOK UX32VD] Wifi failure to connect regression. Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Trusty: In Progress Bug description: 3.13.0-29-generic works 3.13.0-30 results in the following errors Jun 23 20:53:15 colt kernel: [5.862854] iwlwifi :03:00.0: L1 Disabled; Enabling L0S Jun 23 20:53:15 colt kernel: [5.869441] iwlwifi :03:00.0: Radio type=0x2-0x1-0x0 Jun 23 20:53:15 colt kernel: [5.967202] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Jun 23 20:53:15 colt kernel: [5.967478] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Jun 23 20:53:15 colt kernel: [5.972410] ip6_tables: (C) 2000-2006 Netfilter Core Team Jun 23 20:53:15 colt kernel: [6.644363] Bridge firewalling registered Jun 23 20:53:16 colt kernel: [6.816877] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) Jun 23 20:53:16 colt kernel: [6.865773] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready Jun 23 20:53:18 colt kernel: [9.196680] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:53:18 colt kernel: [9.201356] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:53:18 colt kernel: [9.305248] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 2/3) Jun 23 20:53:18 colt kernel: [9.307338] wlan0: authenticated Jun 23 20:53:18 colt kernel: [9.307545] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:53:21 colt kernel: [ 12.654570] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:53:21 colt kernel: [ 12.656770] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:53:21 colt kernel: [ 12.659369] wlan0: authenticated Jun 23 20:53:21 colt kernel: [ 12.659583] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:53:25 colt kernel: [ 16.446479] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:53:25 colt kernel: [ 16.449055] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:53:25 colt kernel: [ 16.451708] wlan0: authenticated Jun 23 20:53:25 colt kernel: [ 16.451816] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:53:30 colt kernel: [ 20.751118] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:53:30 colt kernel: [ 20.753892] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:53:30 colt kernel: [ 20.756151] wlan0: authenticated Jun 23 20:53:30 colt kernel: [ 20.756311] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:53:46 colt kernel: [ 37.251795] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:53:46 colt kernel: [ 37.254521] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:53:46 colt kernel: [ 37.256537] wlan0: authenticated Jun 23 20:53:46 colt kernel: [ 37.256922] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:53:59 colt kernel: [ 50.574868] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:53:59 colt kernel: [ 50.577201] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:53:59 colt kernel: [ 50.579460] wlan0: authenticated Jun 23 20:53:59 colt kernel: [ 50.579761] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:54:11 colt kernel: [ 62.361021] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:54:11 colt kernel: [ 62.363445] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:54:11 colt kernel: [ 62.366190] wlan0: authenticated Jun 23 20:54:11 colt kernel: [ 62.366336] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:54:24 colt kernel: [ 75.684454] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:54:24 colt kernel: [ 75.686745] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:54:24 colt kernel: [ 75.692039] wlan0: authenticated Jun 23 20:54:24 colt kernel: [ 75.692169] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:54:36 colt kernel: [ 87.367947] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:54:36 colt kernel: [ 87.370284] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) Jun 23 20:54:36 colt kernel: [ 87.372230] wlan0: authenticated Jun 23 20:54:36 colt kernel: [ 87.372356] wlan0: waiting for beacon from 94:0c:6d:fe:2e:d6 Jun 23 20:54:49 colt kernel: [ 100.691218] wlan0: authenticate with 94:0c:6d:fe:2e:d6 Jun 23 20:54:49 colt kernel: [ 100.693585] wlan0: send auth to 94:0c:6d:fe:2e:d6 (try 1/3) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID
[Kernel-packages] [Bug 1331860] Re: [Gigabyte GA-MA770-UD3] wireless lags
dev-rke, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331860/comments/28 regarding this being fixed with an update. 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/1331860 Title: [Gigabyte GA-MA770-UD3] wireless lags Status in “linux” package in Ubuntu: Invalid Bug description: Hi, i already discussed the following issue already in the german forum http://forum.ubuntuusers.de/topic/netzwerk-lags-nach-kernel-update-3-13-14-04-lt/ and in your Official Ubuntu IRC Support Channel, without a solution. System: new Ubuntu: 14.04 LTS new Kernel: 3.13.0-29-generic old Ubuntu: 13.10 old Kernel: 3.11.0-19-generic wireless device: TP-LINK WND4800, Atheros chipset wireless driver: ath9k wireless operating mode: 2.4ghz @ 802.11bgn and 5ghz @ 802.11a+n wireless router: fritz!box 3390 Before upgrading to Ubuntu 14.04 LTS everything worked fine. After upgrading to Ubuntu 14.04 LTS the wireless connection produced sequently lags, when sending a ping to my wireless router. The lag sequence duration is around 5 seconds, the duration to the next lag sequence is around 100 seconds. Each ping get a reply (no requests get lost), but the delay of the reply raises up to 2000 miliseconds. Normally the ping is around 1 or 2 miliseconds. I can reproduce this behavior manually by running 'sudo iwlist wlan1 scan' and keep watching the ping in another terminal window. I also used 'iwevent' to watch on events fired by the wireless interface while the lag is happening: '01:31:13.289166 wlan1Scan request completed' is the only message i get. When booting the 3.11 kernel everything works fine again, no lags occur. If i try to reproduce the behavior with a manual scan as described before, no lags occur, everything keeps working fine. I already tried several configurations using special driver options like "nohwcrypt" and "debug", but dmesg and syslog do not log any failures or warnings. If i downgrade the wireless router to 2.4ghz @ 802.11b+g (54mbit) the new kernel (3.13) has also no failed pings and no massive lags, but this is not a stable solution for me due to many other wireless networks in my environment. So i assume there has been something changed between the kernel 3.11 and 3.13 or the belonging ath9k driver. I thought about the wireless scanning interval of the network manager, but i think changing this would also be just a workaround than a clean solution. Any ideas or recommendations how to solve this or how to collect more relevant information about this issue? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: reiner 3154 F pulseaudio /dev/snd/controlC0: reiner 3154 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=79cac639-2340-43af-8d11-807382480b49 InstallationDate: Installed on 2012-03-17 (824 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=59541979-590e-42ca-a568-79027794148f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-29-generic i686 UpgradeStatus: Upgraded to trusty on 2014-04-21 (59 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin mythtv plugdev sambashare wireshark www-data _MarkForUpload: True dmi.bios.date: 12/29/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: GA-MA770-UD3 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.:bvrFG:bd12/29/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvrx.x:cvnGigab
[Kernel-packages] [Bug 1349923] Re: [Asus SABERTOOTH P67] PC freezes
galen, could you please advise on which section specifically you are stuck on? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349923 Title: [Asus SABERTOOTH P67] PC freezes Status in “linux” package in Ubuntu: Incomplete Bug description: The bug is as follows: The whole system freezes except the mouse. After 5 seconds, the screen turns off as if he put on standby. After 20 to 30 seconds, in most cases, the screen turns back on and it is possible to resume the job. But sometimes, the screen comes back but the rest is still frozen and then the screen turns off again, on again and so on. In this case, a forced reboot is required. However, while the system is frozen, magic keys (reisub) are still functional. I noticed that this bug occurs mainly when I used my pc so active (file transfer, web browsing, video playback, etc). I left my pc on for several days without working on it and according to the system log, the bug has not manifested. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-6-generic 3.16.0-6.11 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lynn 2740 F pulseaudio /dev/snd/controlC1: lynn 2740 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 29 17:11:03 2014 HibernationDevice: #RESUME=UUID=7d6efaa5-21d8-46ff-b013-bdbeeec0e829 IwConfig: tun0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-6-generic root=UUID=09e8d2b6-5539-4289-b78f-b622b738d86e ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH P67 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.:bvr3602:bd11/01/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHP67: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/1349923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318771] Re: x230t dock station usb devices stopped working after resume from suspend
bharath, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** 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/1318771 Title: x230t dock station usb devices stopped working after resume from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: This seems to be very common on this particular kernel. There was not a problem before there are some errors in bus [49466.198717] usb 3-3.4.1: Busted HC? Not enough HCD resources for old configuration. [49466.270037] usb 3-3.4.3.3: reset high-speed USB device number 15 using xhci_hcd [49466.326339] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801a24b8c80 [49466.326341] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801a24b8cc0 [49466.349942] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [49467.006344] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [49467.007356] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [49467.007359] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [49467.009384] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [49467.009387] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [49467.010347] ata1.00: configured for UDMA/133 [49467.026437] sd 0:0:0:0: [sda] Starting disk [49467.047997] PM: resume of devices complete after 2336.954 msecs [49467.056364] PM: Finishing wakeup. [49467.056365] Restarting tasks ... done. [49467.063176] status interrupt: c0 03 [49467.063682] video LNXVIDEO:00: Restoring backlight state [49467.070624] usb 3-3.4.1: USB disconnect, device number 12 [49467.111251] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88001f1ad900 [49467.198552] usb 3-3.4.1: new full-speed USB device number 16 using xhci_hcd [49467.216701] usb 3-3.4.1: New USB device found, idVendor=1532, idProduct=0012 [49467.216711] usb 3-3.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [49467.216715] usb 3-3.4.1: Product: Razer Salmosa [49467.216717] usb 3-3.4.1: Manufacturer: Razer [49467.216940] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [49467.216946] xhci_hcd :00:14.0: Not enough bandwidth [49467.216955] usb 3-3.4.1: can't set config #1, error -12 [49467.217635] usb 3-3.4.2: USB disconnect, device number 13 [49467.241322] mmc0: new high speed SDHC card at address e624 [49467.241445] mmcblk0: mmc0:e624 SU32G 29.7 GiB [49467.252179] mmcblk0: p1 [49467.318914] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88001f1adf80 [49467.318923] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88001f1ad300 [49467.390613] usb 3-3.4.2: new low-speed USB device number 17 using xhci_hcd [49467.434073] usb 3-3.4.2: New USB device found, idVendor=046d, idProduct=c30e [49467.434076] usb 3-3.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [49467.434078] usb 3-3.4.2: Product: HID compliant keyboard [49467.434079] usb 3-3.4.2: Manufacturer: Logitech [49467.434179] usb 3-3.4.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [49467.434183] usb 3-3.4.2: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mastier4325 F pulseaudio /dev/snd/controlC0: mastier4325 F pulseaudio CurrentDesktop: Unity Date: Mon May 12 20:29:01 2014 HibernationDevice: RESUME=UUID=f6738183-910b-49b9-b769-898c55ff5967 InstallationDate: Installed on 2012-10-25 (564 days ago) Installa
[Kernel-packages] [Bug 1350513] Re: Ctrl+Alt+F1 shuts down laptop
Luís de Sousa, thank you for reporting this and helping make Ubuntu better. As per http://www.sony.co.uk/support/en/content/cnt-dwnl/VGN-FW31ZJ/list an update to your BIOS is available (R2060Y0). 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. As well, you don't have to create a new bug report. As well, you don't have to create a new bug report. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Once the BIOS is updated, then please mark this report Status Confirmed. Thank you for your understanding. ** Tags added: bios-outdated-r2060y0 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350513 Title: Ctrl+Alt+F1 shuts down laptop Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 on Sony Vaio VGN-FW31ZJ. Whenever I try to switch to a TTY, say by pressing Ctrl+Alt+F1, the system shuts down. The text user name prompt appears for a split second but quickly everything goes black. I then have to press and hold the On/Off chassis button (as in a regular switch on) and wait for the whole start up process to go through: BIOS, Grub and so on. I have used Ubuntu on this laptop since 8.10 and never had such odd behaviour. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lads 2307 F pulseaudio /dev/snd/controlC1: lads 2307 F pulseaudio /dev/snd/pcmC1D0p: lads 2307 F...m pulseaudio /dev/snd/controlC0: lads 2307 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 30 21:43:05 2014 HibernationDevice: RESUME=UUID=3e528dc8-cff2-4953-946f-e811a25f65d0 InstallationDate: Installed on 2013-01-01 (574 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Sony Corporation VGN-FW31ZJ ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1737b96c-878e-4f49-aa43-80d76ab1a740 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-23 (7 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 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.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW31ZJ:pvrC6015DPB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FW31ZJ dmi.product.version: C6015DPB dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349028] Re: getitimer returns it_value=0 erroneously
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: Incomplete
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Utopic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349028
Title:
getitimer returns it_value=0 erroneously
Status in “linux” package in Ubuntu:
Fix Committed
Status in “linux” source package in Trusty:
Fix Committed
Status in “linux” source package in Utopic:
Fix Committed
Bug description:
According to the 'getitimer()' man page: "The element it_value is set
to the amount of time remaining on the timer, or zero if the timer is
disabled. Similarly, it_interval is set to the reset value."
As such the following Perl program should never exit:
use Time::HiRes;
$SIG{VTALRM} = sub { };
Time::HiRes::setitimer(&Time::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
while (1) {
my @t = Time::HiRes::getitimer(&Time::HiRes::ITIMER_VIRTUAL);
exit 0 if $t[0] == 0;
}
and on linux-image 3.11.0-18-generic (and all other systems tested) it
loops forever but 3.13.0-32-generic it exits. Have not bisected
between those kernels, nor am I likely to be able to do so soon.
This Perl program shows the timer countdown:
use Time::HiRes;
my $r = [Time::HiRes::gettimeofday()];
sub display {
my ($desc) = @_;
my @t = Time::HiRes::getitimer(&Time::HiRes::ITIMER_VIRTUAL);
my $i = Time::HiRes::tv_interval($r);
printf "%s: elasped=%.8f; time left=%.6f reset time=%.6f\n", $desc,
$i,@t;
}
$SIG{VTALRM} = sub {
display('VTALRM');
exit;
};
Time::HiRes::setitimer(&Time::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
while (1) {
display('inloop');
}
on other (working) systems it gives:
inloop: elasped=1.65178400; time left=0.001000 reset time=0.401000
inloop: elasped=1.65184200; time left=0.001000 reset time=0.401000
inloop: elasped=1.65186800; time left=0.001000 reset time=0.401000
inloop: elasped=1.65192300; time left=0.001000 reset time=0.401000
inloop: elasped=1.65198100; time left=0.001000 reset time=0.401000
VTALRM: elasped=1.65209800; time left=0.40 reset time=0.401000
(end of file)
but on the 3.13.0-32-generic or later kernel I get:
inloop: elasped=0.54692100; time left=0.33 reset time=0.40
inloop: elasped=0.54692800; time left=0.26 reset time=0.40
inloop: elasped=0.54693500; time left=0.20 reset time=0.40
inloop: elasped=0.54694100; time left=0.13 reset time=0.40
inloop: elasped=0.54694800; time left=0.07 reset time=0.40
inloop: elasped=0.54695500; time left=0.00 reset time=0.40
inloop: elasped=0.54696200; time left=0.004000 reset time=0.40
[...]
VTALRM: elasped=0.55013600; time left=0.397062 reset time=0.40
(end of file)
The reset time also looks dodgy.
Hardware is an Intel Core i7-920 on Asus P6T Deluxe v2 (X58)
motherboard and hasn't changed.
Requested information:
Ubuntu 3.13.0-32.57-generic 3.13.11.4
Description: Ubuntu 14.04.1 LTS
Release: 14.04
# apt-cache policy linux-image-generic
linux-image-generic:
Installed: 3.13.0.32.38
Candidate: 3.13.0.32.38
Version table:
*** 3.13.0.32.38 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
500 http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/
trusty/main amd64 Packages
100 /var/lib/dpkg/status
3.13.0.24.28 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tivrusky 3009 F pulseaudio
/dev/snd/controlC0: tivrusky 3009 F pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=c026abdc-9fee-425c-b5ae-020bf6ea2ad6
IwConfig:
eth0 no wireless extensions.
eth1 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: root=UUID=3ea7a4cb-eade-4906-b545-5133d8c14080 ro quiet
splash
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
RelatedPackageVersions:
linux-restricted-modules-3.13.0-32-generic N/A
linux-backports-modules-3.13.0-32-generic N
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
Juan/Kelvin, Based on Larry's earlier responses, I think we're going to have to wait until the 3.18 kernel for the new and improved driver. Realtek has apparently made a lot of fixes to its version of the driver, but porting it to the kernel is a lot of work on Larry's part. It sounds like some people have had found the current version of the driver reasonably stable. That hasn't been my experience, but it's hard to know what variables are making the difference. Personally, I bought a cheap USB wifi adapter to use until the Linux driver for this chip is more stable - if you can find a USB adapter with good linux drivers, that may be the best option for you. Juan: the kernel module is r8192ee, not rtl8192ee. - Tim -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350480] Re: [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in
Correct, the offending commit is 1f81b6d22a5980955b01e08cf27fb745dc9b686f. A patched has been proposed in the 3.16 kernel instead of a revert. That patch is undergoing testing now. I've also build a test kernel with this patch at: http://kernel.ubuntu.com/~jsalisbury/kirkland/ However, that is the latest mainline kernel and not a Trusty 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/1350480 Title: [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Precise: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress Bug description: The latest kernel update in Ubuntu 14.04 LTS (3.13.0-32.57) renders our Intel NUCs unbootable, when we cold boot and have USB devices (keyboard, mouse, USB/Ethernet adapter) connected. The 3.13.0-24.47 kernel does not exhibit this behavior. Our particular NUCs have the i5-3427U processor, which is the D53427RKE board (DC53427HYE kit). These reports seem to be related: http://support.sundtek.com/index.php/topic,1600.0.html http://en.it-usenet.org/thread/19505/17700/ --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1400 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=37e4ff56-b945-4604-a94d-557bdf83e0b2 InstallationDate: Installed on 2014-07-30 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=c0597da2-7d4a-4340-b85a-c7f96d8262d7 ro ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2013 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0017.2013.0425.1251 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation dmi.board.version: G87790-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0017.2013.0425.1251:bd04/25/2013:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87790-403:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
The driver is working fairly stable for me, I also have problems with suspend/wakeup but two things usually help me solve that: * It is usually only a problem if I want to re-connect to the same WIFi. If I switch from one to another, it works without a problem in most cases. In case of the portable WiFi hotspot on my phone, it is even enough to just disable and enable it again. No chance to connect without that, works immediately after that. That might help to find the problem here? * If that is not an option, it often helps to (repeatedly) kill the NetworkManager, then it usually works again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349883] Re: dmesg time wildly incorrect on paravirtual EC2 instances.
Of course, after stating that I will look for a instance that is not affected, all of which I start are on the same cpu type and affected. :/ >From further research it sounds like Xen 3.4.3 has a default of running guests in native tsc mode while Xen 4.0 and later have a default of native if the tsc is stable and emulated otherwise. I played around with the local host but could get no difference even if forcing native tsc mode. One thing I noticed then was that while on dom0 I have nonstop_tsc in the /proc/cpuinfo, it does not show up in my PV guest. Somehow we see it on AWS. Locally I am using Xen 4.4 though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. Status in “linux” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 EC2 instances, during startup the dmesg time goes from 0 seconds to thousands of seconds. This causes kernel logs to be recorded for months in the future. This appears to be related to the kernel trusting the TSC clock on Xen servers, as described here: https://forums.aws.amazon.com/thread.jspa?threadID=59753 But I am not sure that is the cause. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jul 29 14:47:54 2014 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 29 14:41 seq crw-rw 1 root audio 116, 33 Jul 29 14:41 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [7562292.301737] init: plymouth-upstart-bridge main process ended, respawning DistroRelease: Ubuntu 14.04 Ec2AMI: ami-00dc1368 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: m1.small Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin ssh sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349923] Re: [Asus SABERTOOTH P67] PC freezes
>From wiki, I understood goal and purpose of the operation, but I don't know where to start and what to do..!? Step by step would be welcome. :) Sorry, I do what I can to help report bugs but I have not had computer training and there, it's high to my level of understanding. ^^ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349923 Title: [Asus SABERTOOTH P67] PC freezes Status in “linux” package in Ubuntu: Incomplete Bug description: The bug is as follows: The whole system freezes except the mouse. After 5 seconds, the screen turns off as if he put on standby. After 20 to 30 seconds, in most cases, the screen turns back on and it is possible to resume the job. But sometimes, the screen comes back but the rest is still frozen and then the screen turns off again, on again and so on. In this case, a forced reboot is required. However, while the system is frozen, magic keys (reisub) are still functional. I noticed that this bug occurs mainly when I used my pc so active (file transfer, web browsing, video playback, etc). I left my pc on for several days without working on it and according to the system log, the bug has not manifested. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-6-generic 3.16.0-6.11 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lynn 2740 F pulseaudio /dev/snd/controlC1: lynn 2740 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 29 17:11:03 2014 HibernationDevice: #RESUME=UUID=7d6efaa5-21d8-46ff-b013-bdbeeec0e829 IwConfig: tun0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-6-generic root=UUID=09e8d2b6-5539-4289-b78f-b622b738d86e ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH P67 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.:bvr3602:bd11/01/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHP67: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/1349923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307473] Re: guest hang due to missing clock interrupt
I confirm, like Jeff Wilson, that I had the same issue with 3.13 and got resolved with 3.14.1. I cannot right now test the kernel suggested in #46. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307473 Title: guest hang due to missing clock interrupt Status in “linux” package in Ubuntu: Confirmed Bug description: I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing: - in case of Windows VMs I'm getting BSOD with error message: "A clock interrupt was not received on a secondary processor within the allocated time interval." - On linux VMs I'm noticing "hrtimer: interrupt took 2992229 ns" messages - On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts QEMU version is: QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3) Full command line: qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc- i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a- 4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb- uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio- disk0,id=virtio-disk0,bootindex=1 -drive file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en- us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio- win-0.1-74.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1331077] Re: [Lenovo ThinkPad Edge E540] suspend/resume failure
I just received this Lenovo ThinkPad E540 today. I replaced the harddisk with an 120 GB SSD and made fresh install of Kubuntu 14.04.1 and discovered this bug here. Fortunately the proposed workaround to disable USB3.0 in the BIOS settings helped to get around this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331077 Title: [Lenovo ThinkPad Edge E540] suspend/resume failure Status in “linux” package in Ubuntu: Triaged Bug description: suspend to RAM failed before it was completed: * fan was still on and * Fn-F1- & Fn-F4-status LEDs were still on (signifying muted speakers and microphone respectively) * nevertheless the general ThinkPad LED (the i's dot) (/proc/acpi/ibm/led 0) behaved like normal: slowly blinking, which normally means "I'm suspended to RAM." * however resume was impossible: wakeup failed through mouse clicks, various keyboard keys and combinations and also the power key, only a hard reset (5s or so holding down the power key) could bring it back to life Adding the kernel cmdline option acpi_sleep=nonvs was of no avail, too. I recently upgraded to a new BIOS v2.07 [1], I think the problem exists since then. Update == I confirmed that this is definitely a BIOS issue. The last working BIOS is v1.61 [2], so the change was introduced by v2.07 [1]. Installing the latest v2.08 [3] does not fix this problem. So this is the changelog for v2.07 [1]: - (Fix) Fixed an issue that system will auto wakeup after shutdown when battery capacity is under 15% on DC only. - (Fix) Fixed an issue related to APS. - (New) Added support for new GPU config. By the way, I could not find a new GPU config option in the BIOS, same old choice vs. , nothing new. [1] http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj10wd.iso http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj10wd.txt [2] http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj09wd.iso http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj09wd.txt [3] http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj11wd.iso http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj11wd.txt ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xx 2499 F pulseaudio /dev/snd/controlC0: xx 2499 F pulseaudio Date: Tue Jun 17 17:16:54 2014 DuplicateSignature: suspend/resume:LENOVO 20C6S00200:J9ET87WW (2.07 ) ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1400281919 Failure: suspend/resume HibernationDevice: RESUME=UUID=2ecc68b9-65e3-4cee-9b2a-d41ff651e4e8 InstallationDate: Installed on 2014-01-06 (161 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 20C6S00200 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed root=/dev/mapper/ubuntuvg-root ro quiet splash "acpi_osi=!Windows 2012" pcie_aspm=force intel_pstate=enable vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.3 SourcePackage: linux Title: [LENOVO 20C6S00200] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-06-12 (5 days ago) UserGroups: dmi.bios.date: 05/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: J9ET87WW (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6S00200 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:bvrJ9ET87WW(2.07):bd05/13/2014:svnLENOVO:pn20C6S00200:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6S00200:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C6S00200 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.la
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
** Also affects: linux (Ubuntu Utopic) Importance: High Status: 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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [] dump_stack+0x45/0x56 19:35:02 [2.547101] [] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [] module_alloc+0x74/0xd0 19:35:02 [2.547132] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [] load_module+0xd3/0x1b70 19:35:02 [2.547154] [] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [] dump_stack+0x45/0x56 19:35:02 [2.547202] [] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [] module_alloc+0x74/0xd0 19:35:02 [2.547220] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [] load_module+0xd3/0x1b70 19:35:02 [2.547235] [] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. DistroRelease: Ubuntu 14.10 Ec2AMI: ami-c571d8d8 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: sa-east-1b Ec2InstanceType: m3.medium Ec2Kernel: aki-5553f448 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux-image-virtual 3.16.0.5.6 PackageArchitecture: amd64 PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
I've got a way to rapidly reproduce the error now. I can do it reliably with a turnaround time of 5-10 minutes. I've reproduced the crash on the new Kernel, so it has now been observed on both 3.13.0-32-generic and 3.15.7-031507-generic. I'll try 3.16 next. I've also discovered this new stack trace at the point of the crash (setup_cluster_bitmap) which happens every time: [97056.916053] NMI backtrace for cpu 1 [97056.916053] CPU: 1 PID: 1107 Comm: kworker/u30:1 Not tainted 3.13.0-32-generic #57-Ubuntu [97056.916053] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/23/2014 [97056.916053] Workqueue: writeback bdi_writeback_workfn (flush-btrfs-1) [97056.916053] task: 8800e8018000 ti: 8800da1ac000 task.ti: 8800da1ac000 [97056.916053] RIP: 0010:[] [] default_send_IPI_mask_sequence_phys+0xbc/0x100 [97056.916053] RSP: 0018:8801efc23c60 EFLAGS: 0046 [97056.916053] RAX: 0400 RBX: b06a RCX: 0001 [97056.916053] RDX: 0001 RSI: 0001 RDI: 0300 [97056.916053] RBP: 8801efc23c98 R08: 81d13780 R09: 0d2e [97056.916053] R10: R11: 8801efc239e6 R12: 81d13780 [97056.916053] R13: 0400 R14: 0086 R15: 0002 [97056.916053] FS: () GS:8801efc2() knlGS: [97056.916053] CS: 0010 DS: ES: CR0: 80050033 [97056.916053] CR2: 7f803f12e000 CR3: 000101cc2000 CR4: 001406e0 [97056.916053] Stack: [97056.916053] 00010008 0001 2710 81c4e1c0 [97056.916053] 81d137a0 81c4e1c0 0001 8801efc23ca8 [97056.916053] 81049217 8801efc23cc0 81044c60 8801efc2e800 [97056.916053] Call Trace: [97056.916053] [97056.916053] [] physflat_send_IPI_all+0x17/0x20 [97056.916053] [] arch_trigger_all_cpu_backtrace+0x70/0xb0 [97056.916053] [] rcu_check_callbacks+0x3fe/0x650 [97056.916053] [] update_process_times+0x47/0x70 [97056.916053] [] tick_sched_handle.isra.17+0x25/0x60 [97056.916053] [] tick_sched_timer+0x41/0x60 [97056.916053] [] __run_hrtimer+0x77/0x1d0 [97056.916053] [] ? tick_sched_handle.isra.17+0x60/0x60 [97056.916053] [] hrtimer_interrupt+0xef/0x230 [97056.916053] [] xen_timer_interrupt+0x2f/0x150 [97056.916053] [] ? xen_clocksource_read+0x20/0x30 [97056.916053] [] ? sched_clock+0x9/0x10 [97056.916053] [] ? sched_clock_local+0x1d/0x80 [97056.916053] [] handle_irq_event_percpu+0x3e/0x1d0 [97056.916053] [] handle_percpu_irq+0x3e/0x60 [97056.916053] [] __xen_evtchn_do_upcall+0x317/0x320 [97056.916053] [] ? __vtime_account_system+0x2e/0x40 [97056.916053] [] ? vtime_account_system+0x3c/0x50 [97056.916053] [] xen_evtchn_do_upcall+0x2b/0x50 [97056.916053] [] xen_hvm_callback_vector+0x6d/0x80 [97056.916053] [97056.916053] [] ? find_next_zero_bit+0x8f/0xf0 [97056.916053] [] setup_cluster_bitmap+0x15a/0x280 [btrfs] [97056.916053] [] btrfs_find_space_cluster+0x244/0x290 [btrfs] [97056.916053] [] find_free_extent+0x4d2/0xc30 [btrfs] [97056.916053] [] btrfs_reserve_extent+0xa8/0x1a0 [btrfs] [97056.916053] [] cow_file_range+0x135/0x430 [btrfs] [97056.916053] [] run_delalloc_range+0x312/0x350 [btrfs] [97056.916053] [] ? find_lock_delalloc_range.constprop.43+0x1b9/0x1f0 [btrfs] [97056.916053] [] __extent_writepage+0x2f4/0x750 [btrfs] [97056.916053] [] ? end_extent_writepage+0x70/0x70 [btrfs] [97056.916053] [] extent_write_cache_pages.isra.30.constprop.50+0x272/0x3d0 [btrfs] [97056.916053] [] extent_writepages+0x4d/0x70 [btrfs] [97056.916053] [] ? btrfs_real_readdir+0x5b0/0x5b0 [btrfs] [97056.916053] [] btrfs_writepages+0x28/0x30 [btrfs] [97056.916053] [] do_writepages+0x1e/0x40 [97056.916053] [] __writeback_single_inode+0x40/0x210 [97056.916053] [] writeback_sb_inodes+0x247/0x3e0 [97056.916053] [] __writeback_inodes_wb+0x9f/0xd0 [97056.916053] [] wb_writeback+0x243/0x2c0 [97056.916053] [] bdi_writeback_workfn+0x1b9/0x430 [97056.916053] [] process_one_work+0x182/0x450 [97056.916053] [] worker_thread+0x121/0x410 [97056.916053] [] ? rescuer_thread+0x430/0x430 [97056.916053] [] kthread+0xd2/0xf0 [97056.916053] [] ? kthread_create_on_node+0x1d0/0x1d0 [97056.916053] [] ret_from_fork+0x7c/0xb0 [97056.916053] [] ? kthread_create_on_node+0x1d0/0x1d0 [97056.916053] Code: 90 8b 0c 25 00 73 5f ff 80 e5 10 75 f2 89 f0 c1 e0 18 89 04 25 10 73 5f ff 41 83 ff 02 44 89 e8 41 0f 45 c7 89 04 25 00 73 5f ff 8a 4c 89 f7 57 9d 0f 1f 44 00 00 48 83 c4 10 5b 41 5c 41 5d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349711 Title: Machine lockup in btrfs-transaction Status in “linux” package in Ubuntu: Incomplete Bug description: This has happened twice now. I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami- 776d9700. # cat /proc/version_signature Ubuntu 3.13.0-32.57-generic 3.13.11.4 Afte
[Kernel-packages] [Bug 1350889] [NEW] kernel crash kvm guest on power8
Public bug reported: subject is extremely vague, I'll give all the information I have here. We've got a number of kvm guests running on a power8 host: $ head -n 5 /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) $ rpm -qf `which qemu-system-ppc64` qemu-system-ppc-1.6.0-2.pkvm2_1.9.2.ppc64 $ uname -r 3.10.23-900.pkvm2_1.1.ppc64 $ ps axw | grep [s]tilson-01 83440 pts/1S+ 0:00 /bin/bash /home/shared/bin/guest-start stilson-01 83459 pts/1Sl+ 4882:24 qemu-system-ppc64 -enable-kvm -M pseries -cpu host -smp cores=2,threads=1 -m 8G -net nic,macaddr=52:54:00:00:43:81 -net tap,script=no,downscript=no,ifname=tap4381 -device spapr-vscsi -drive file=/var/lib/libvirt/images/shared/stilson-01/disk1.img -drive file=/var/lib/libvirt/images/shared/stilson-01/eph0.img -nographic -vga none The ppc64el Ubuntu 14.04 guest was found dead, and showed on console: [708665.375169] Unable to handle kernel paging request for data at address 0x00bf [708665.375321] Faulting instruction address: 0xc04b790c [708665.375388] Oops: Kernel access of bad area, sig: 11 [#1] [708665.375440] SMP NR_CPUS=2048 NUMA pSeries [708665.375513] Modules linked in: 8021q garp mrp ebtable_broute ebtable_filter sunrpc nfnetlink_queue nfnetlink_log nfnetlink btrfs raid6_pq xor ufs msdos xfs libcrc32c veth xt_conntrack ipt_REJECT ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [708665.376496] CPU: 0 PID: 270 Comm: cgmanager Not tainted 3.13.0-32-generic #57-Ubuntu [708665.376644] task: c001fa55be10 ti: c001f8d68000 task.ti: c001f8d68000 [708665.376786] NIP: c04b790c LR: c04b78d8 CTR: c04b7860 [708665.376931] REGS: c001f8d6b680 TRAP: 0300 Not tainted (3.13.0-32-generic) [708665.377084] MSR: 80009033 CR: 42008484 XER: 2000 [708665.377411] CFAR: c000a86c DAR: 00bf DSISR: 4000 SOFTE: 0 GPR00: c04b4710 c001f8d6b900 c164edb8 GPR04: 0800 GPR08: 0003 00bf 00bf c00172a0 GPR12: 22002482 cfe4 fe80 fe90 GPR16: fea0 feb0 fec0 GPR20: 010003df8420 c000b1bfbe00 0400 GPR24: 0001 c15f2ed8 c000b1bfbdc0 GPR28: c16e4c80 c16e4fc4 c78e6600 c001f8d6b9d0 [708665.379401] NIP [c04b790c] .tg_prfill_cpu_rwstat+0xac/0x180 [708665.379517] LR [c04b78d8] .tg_prfill_cpu_rwstat+0x78/0x180 [708665.379643] Call Trace: [708665.379694] [c001f8d6b900] [c00130138e18] 0xc00130138e18 (unreliable) [708665.379854] [c001f8d6ba20] [c04b4710] .blkcg_print_blkgs+0xf0/0x1b0 [708665.380026] [c001f8d6bae0] [c04b7730] .tg_print_cpu_rwstat+0x50/0x80 [708665.380204] [c001f8d6bb70] [c01381ec] .cgroup_seqfile_show+0x9c/0xc0 [708665.380384] [c001f8d6bc00] [c0287e98] .seq_read+0x158/0x570 [708665.380526] [c001f8d6bcf0] [c02560d4] .vfs_read+0xc4/0x1f0 [708665.380679] [c001f8d6bd90] [c0256ef4] .SyS_read+0x64/0xe0 [708665.380811] [c001f8d6be30] [c000a158] syscall_exit+0x0/0x98 [708665.380956] Instruction dump: [708665.381040] 813d 3be100d0 7c6307b4 7f891800 409d00b0 3d420009 392a1ca8 786a1f24 [708665.381268] 7d49502a e93e01c8 7d495214 7d2ad214 <7cead02a> e9090008 e9490010 e9290018 [708665.381505] ---[ end trace 512b8ac8f55926fd ]--- [708665.387710] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: User Name 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Jul 31 14:32:40 2014 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-3.13.0-32-generic root=UUID=44b83b05-4fa2-4d3f-b3af-4c8a4d097f90 ro console=hvc0 earlyprintk RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware
[Kernel-packages] [Bug 1349879] Re: powering off an usb3 device causes kernel to resume immediately after suspend
> can you please do "dmesg > /tmp/dmesg.txt" after such a resume and attach /tmp/dmesg.txt here? Thanks! Rebooted and executed the steps mentioned above. dmesg is attached. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349879/+attachment/4166687/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1349879 Title: powering off an usb3 device causes kernel to resume immediately after suspend Status in “linux” package in Ubuntu: Incomplete Bug description: After powering off an usb3 disk (e.g. udisksctl power-off -b /dev/sdc) the system immediately resumes after suspend. This does not happen, if I umount the device and disconnect it. Usb devices < 3.0 seem not to be affected. How to reproduce: 1) plug an usb3 device to an usb3 port and mount it 2) umount it 3) power it off: udisksctl power-off -b /dev/sdX 4) suspend: (e.g. echo mem > /sys/power/state) result: system suspends and immediately resumes Package: udisks2 (2.1.3-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
Ben, A few questions that would be useful to answer: * It would be useful to correlate Xen hypervisor versions. On each launch with warnings we need to grep 'Xen version' in dmesg. * Can you add the following to kernel cmdline options to get additional debug information: initcall_debug debug ignore_loglevel LOGLEVEL=8 * If you see this problem in an instance, if you reboot does the same problem occur? 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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [] dump_stack+0x45/0x56 19:35:02 [2.547101] [] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [] module_alloc+0x74/0xd0 19:35:02 [2.547132] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [] load_module+0xd3/0x1b70 19:35:02 [2.547154] [] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [] dump_stack+0x45/0x56 19:35:02 [2.547202] [] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [] module_alloc+0x74/0xd0 19:35:02 [2.547220] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [] load_module+0xd3/0x1b70 19:35:02 [2.547235] [] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. DistroRelease: Ubuntu 14.10 Ec2AMI: ami-c571d8d8 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: sa-east-1b Ec2InstanceType: m3.medium Ec2Kernel: aki-5553f448 Ec2Ramdi
[Kernel-packages] [Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
I have a Dell Latitude E7240 with the same problem of erratic mouse "jumps" and clicks, reported in the logs as: psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced. I tried booting with i8042.reset, which did not help. However, the odd thing is that I plugged in a USB mouse and, after having removed it, the 'mouse jumps' behaviour stopped. I've also lost two-finger scrolling. The plugged-in mouse was: input: Microsoft Microsoft® 2.4GHz Transceiver v5.0 as /devices/pci:00/:00:14.0/usb1/1-2/ 1-2:1.0/0003:045E:074F.0003/input/input21 hid-generic 0003:045E:074F.0003: input,hidraw2: USB HID v1.11 Mouse [Microsoft Microsoft® 2.4GHz Transceiver v5.0] on usb-:00:14.0-2/input0 synclient returns: VertTwoFingerScroll = 1 Notice that the mouse wheel scrolling was also very erratic, but it was an old device and it might have been broken. Anyhow, this makes me think the "lost sync" problem might be related to some sort of "multi-touch" situation where one finger on the trackpad is wrongly interpreted as two and odd behaviour follows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad". This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. 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/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro 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: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
Now reproduced on 3.16. I'm out of things to try for now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247056.192053] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[247056.212061] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest
Test kernel at http://kernel.ubuntu.com/~rtg/3.13.0 -9b0a74ddd711e5a6b07b75eb97e985abecdf657d-lp1350373/ ** Patch added: "[PATCH Trusty] x86/xen: safely map and unmap grant frames when in atomic context" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373/+attachment/4166700/+files/0001-x86-xen-safely-map-and-unmap-grant-frames-when-in-at.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350373 Title: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Bug description: Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while expanding the grant table (usually when requested by blkfront, when booting). See an example trace below. This is caused by calling functions that are unsafe in atomic context. The fix (which has been submitted to 3.16) is available here (also attached): https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable /for-linus-3.16&id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168 The fix is applicable to all kernel since 2.6.39 but only appears to trigger with the 3.13 kernel in 14.04. [2.577876] [ cut here ] [2.577896] kernel BUG at /build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239! [2.577910] invalid opcode: [#1] SMP [2.577922] Modules linked in: [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic #46-Ubuntu [2.577946] task: ec058000 ti: ec09 task.ti: ec09 [2.577955] EIP: 0061:[] EFLAGS: 00010002 CPU: 0 [2.577973] EIP is at enter_lazy.part.1+0x3/0x5 [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50 [2.578001] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660 [2.578027] Stack: [2.578032] ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff edc01000 c1a93018 [2.578052] edc00fff c193ce80 edc01000 [2.578076] ed3ef588 ed3ef588 c1b87b70 ec091ad0 edc01000 c1b65310 1000 [2.578096] Call Trace: [2.578111] [] paravirt_enter_lazy_mmu+0x24/0x30 [2.578127] [] apply_to_page_range+0x1a3/0x310 [2.578141] [] arch_gnttab_map_status+0x38/0x60 [2.578152] [] ? map_pte_fn+0x70/0x70 [2.578166] [] gnttab_map_frames_v2+0xb0/0x100 [2.578182] [] gnttab_map+0x95/0x120 [2.578198] [] ? blk_update_request+0x190/0x340 [2.578209] [] get_free_entries+0xd3/0x280 [2.578221] [] gnttab_alloc_grant_references+0x13/0x30 [2.578238] [] do_blkif_request+0x535/0x6f0 [2.578253] [] ? _raw_spin_unlock_irqrestore+0x1c/0x40 [2.578269] [] __blk_run_queue+0x2e/0x40 [2.578280] [] blk_start_queue+0x25/0x40 [2.578291] [] kick_pending_request_queues+0x1e/0x30 [2.578304] [] blkif_interrupt+0x69f/0x740 [2.578318] [] ? xen_set_pte_at+0xbf/0xf0 [2.578335] [] handle_irq_event_percpu+0x35/0x1a0 [2.578351] [] ? radix_tree_lookup+0xa/0x10 [2.578364] [] handle_irq_event+0x31/0x50 [2.578376] [] handle_edge_irq+0x66/0x110 [2.578389] [] __xen_evtchn_do_upcall+0x1c6/0x2c0 [2.578402] [] xen_evtchn_do_upcall+0x20/0x40 [2.578415] [] xen_do_upcall+0x7/0xc [2.578427] [] ? xen_hypercall_xen_version+0x7/0x20 [2.578441] [] ? xen_force_evtchn_callback+0xf/0x20 [2.578454] [] check_events+0x8/0xc [2.578464] [] ? xen_restore_fl_direct_reloc+0x4/0x4 [2.578480] [] ? xen_batched_set_pte+0xb3/0x160 [2.578493] [] xen_set_pte_at+0x28/0xf0 [2.578505] [] ? __raw_callee_save_xen_pte_val+0x6/0x8 [2.578521] [] copy_pte_range+0x258/0x4c0 [2.578534] [] copy_page_range+0x1d7/0x2e0 [2.578549] [] dup_mm+0x28e/0x4f0 [2.578561] [] copy_process.part.33+0xfa6/0x10d0 [2.578574] [] do_fork+0xc1/0x2c0 [2.578591] [] ? SyS_rt_sigprocmask+0x76/0xa0 [2.578604] [] SyS_clone+0x25/0x30 [2.578615] [] sysenter_do_call+0x12/0x28 [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 <0f> 0b 55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5 [2.578745] EIP: [] enter_lazy.part.1+0x3/0x5 SS:ESP 0069:ec091a50 [2.578765] ---[ end trace ab5b5344be71ca3d ]--- [2.578775] Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsub
[Kernel-packages] [Bug 1350889] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1350889 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350889 Title: kernel crash kvm guest on power8 Status in “linux” package in Ubuntu: Incomplete Bug description: subject is extremely vague, I'll give all the information I have here. We've got a number of kvm guests running on a power8 host: $ head -n 5 /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) $ rpm -qf `which qemu-system-ppc64` qemu-system-ppc-1.6.0-2.pkvm2_1.9.2.ppc64 $ uname -r 3.10.23-900.pkvm2_1.1.ppc64 $ ps axw | grep [s]tilson-01 83440 pts/1S+ 0:00 /bin/bash /home/shared/bin/guest-start stilson-01 83459 pts/1Sl+ 4882:24 qemu-system-ppc64 -enable-kvm -M pseries -cpu host -smp cores=2,threads=1 -m 8G -net nic,macaddr=52:54:00:00:43:81 -net tap,script=no,downscript=no,ifname=tap4381 -device spapr-vscsi -drive file=/var/lib/libvirt/images/shared/stilson-01/disk1.img -drive file=/var/lib/libvirt/images/shared/stilson-01/eph0.img -nographic -vga none The ppc64el Ubuntu 14.04 guest was found dead, and showed on console: [708665.375169] Unable to handle kernel paging request for data at address 0x00bf [708665.375321] Faulting instruction address: 0xc04b790c [708665.375388] Oops: Kernel access of bad area, sig: 11 [#1] [708665.375440] SMP NR_CPUS=2048 NUMA pSeries [708665.375513] Modules linked in: 8021q garp mrp ebtable_broute ebtable_filter sunrpc nfnetlink_queue nfnetlink_log nfnetlink btrfs raid6_pq xor ufs msdos xfs libcrc32c veth xt_conntrack ipt_REJECT ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [708665.376496] CPU: 0 PID: 270 Comm: cgmanager Not tainted 3.13.0-32-generic #57-Ubuntu [708665.376644] task: c001fa55be10 ti: c001f8d68000 task.ti: c001f8d68000 [708665.376786] NIP: c04b790c LR: c04b78d8 CTR: c04b7860 [708665.376931] REGS: c001f8d6b680 TRAP: 0300 Not tainted (3.13.0-32-generic) [708665.377084] MSR: 80009033 CR: 42008484 XER: 2000 [708665.377411] CFAR: c000a86c DAR: 00bf DSISR: 4000 SOFTE: 0 GPR00: c04b4710 c001f8d6b900 c164edb8 GPR04: 0800 GPR08: 0003 00bf 00bf c00172a0 GPR12: 22002482 cfe4 fe80 fe90 GPR16: fea0 feb0 fec0 GPR20: 010003df8420 c000b1bfbe00 0400 GPR24: 0001 c15f2ed8 c000b1bfbdc0 GPR28: c16e4c80 c16e4fc4 c78e6600 c001f8d6b9d0 [708665.379401] NIP [c04b790c] .tg_prfill_cpu_rwstat+0xac/0x180 [708665.379517] LR [c04b78d8] .tg_prfill_cpu_rwstat+0x78/0x180 [708665.379643] Call Trace: [708665.379694] [c001f8d6b900] [c00130138e18] 0xc00130138e18 (unreliable) [708665.379854] [c001f8d6ba20] [c04b4710] .blkcg_print_blkgs+0xf0/0x1b0 [708665.380026] [c001f8d6bae0] [c04b7730] .tg_print_cpu_rwstat+0x50/0x80 [708665.380204] [c001f8d6bb70] [c01381ec] .cgroup_seqfile_show+0x9c/0xc0 [708665.380384] [c001f8d6bc00] [c0287e98] .seq_read+0x158/0x570 [708665.380526] [c001f8d6bcf0] [c02560d4] .vfs_read+0xc4/0x1f0 [708665.380679] [c001f8d6bd90] [c0256ef4] .SyS_read+0x64/0xe0 [708665.380811] [c001f8d6be30] [c000a158] syscall_exit+0x0/0x98 [708665.380956] Instruction dump: [708665.381040] 813d 3be100d0 7c6307b4 7f891800 409d00b0 3d420009 392a1ca8 786a1f24 [708665.381268] 7d49502a e93e01c8 7d495214 7d2ad214 <7cead02a> e9090008 e9490010 e9290018 [708665.381505] ---[ end trace 512b8ac8f55926fd ]--- [708665.387710] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: User Name 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic ppc64le AlsaDevices: Error: command ['l
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
This gist contains a stack trace every 10 seconds taken with `echo l >
/proc/sysrq-trigger` whilst the machine was spinning in the kernel but
still responsive.
https://gist.github.com/pwaller/c7dd0f4807459acedcdf
The machine remained responsive for 5-10 minutes before becoming totally
unresponsive to network activity.
The test case just involves copying every sqlite file in a directory
tree containing ~400GB of files of various sizes to new files in the
same directory with `.new` on the end of the filename.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247056.192053] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[247056.212061] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711/+subscriptions
--
M
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1350522 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [] dump_stack+0x45/0x56 19:35:02 [2.547101] [] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [] module_alloc+0x74/0xd0 19:35:02 [2.547132] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [] load_module+0xd3/0x1b70 19:35:02 [2.547154] [] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [] dump_stack+0x45/0x56 19:35:02 [2.547202] [] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [] module_alloc+0x74/0xd0 19:35:02 [2.547220] [] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [] load_module+0xd3/0x1b70 19:35:02 [2.547235] [] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. DistroRelease: Ubuntu 14.10 Ec2AMI: ami-c571d8d8 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: sa-east-1b Ec2InstanceType: m3.medium Ec2Kernel: aki-5553f448 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux-image-virtual 3.
[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep
Christopher, done: #1350910 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep Status in “linux” package in Ubuntu: Incomplete Bug description: In 14.04 after wakeup from suspend, the notebook screen goes blank while the OS and the hardware is awake (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system). Changeing "quiet splash" to "nomodeset" in /etc/default/grub allows the wakeup, but the pc is really slow (can't be used). WORKAROUND: This problem is not happening with the AMD property drivers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 24 12:58:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c660] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218) MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RAF.N93.130403.LEO dmi.board.asset.tag: No Asset Tag dmi.board.name: NP535U4X-S01TH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 535U4C dmi.product.version: P06RAF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 12:54:54 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
** Tags added: kernel-bug-exists-upstream
** 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/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247056.192053] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[247056.212061] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350889] Re: kernel crash kvm guest on power8
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** 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/1350889 Title: kernel crash kvm guest on power8 Status in “linux” package in Ubuntu: Confirmed Bug description: subject is extremely vague, I'll give all the information I have here. We've got a number of kvm guests running on a power8 host: $ head -n 5 /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) $ rpm -qf `which qemu-system-ppc64` qemu-system-ppc-1.6.0-2.pkvm2_1.9.2.ppc64 $ uname -r 3.10.23-900.pkvm2_1.1.ppc64 $ ps axw | grep [s]tilson-01 83440 pts/1S+ 0:00 /bin/bash /home/shared/bin/guest-start stilson-01 83459 pts/1Sl+ 4882:24 qemu-system-ppc64 -enable-kvm -M pseries -cpu host -smp cores=2,threads=1 -m 8G -net nic,macaddr=52:54:00:00:43:81 -net tap,script=no,downscript=no,ifname=tap4381 -device spapr-vscsi -drive file=/var/lib/libvirt/images/shared/stilson-01/disk1.img -drive file=/var/lib/libvirt/images/shared/stilson-01/eph0.img -nographic -vga none The ppc64el Ubuntu 14.04 guest was found dead, and showed on console: [708665.375169] Unable to handle kernel paging request for data at address 0x00bf [708665.375321] Faulting instruction address: 0xc04b790c [708665.375388] Oops: Kernel access of bad area, sig: 11 [#1] [708665.375440] SMP NR_CPUS=2048 NUMA pSeries [708665.375513] Modules linked in: 8021q garp mrp ebtable_broute ebtable_filter sunrpc nfnetlink_queue nfnetlink_log nfnetlink btrfs raid6_pq xor ufs msdos xfs libcrc32c veth xt_conntrack ipt_REJECT ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables dm_crypt [708665.376496] CPU: 0 PID: 270 Comm: cgmanager Not tainted 3.13.0-32-generic #57-Ubuntu [708665.376644] task: c001fa55be10 ti: c001f8d68000 task.ti: c001f8d68000 [708665.376786] NIP: c04b790c LR: c04b78d8 CTR: c04b7860 [708665.376931] REGS: c001f8d6b680 TRAP: 0300 Not tainted (3.13.0-32-generic) [708665.377084] MSR: 80009033 CR: 42008484 XER: 2000 [708665.377411] CFAR: c000a86c DAR: 00bf DSISR: 4000 SOFTE: 0 GPR00: c04b4710 c001f8d6b900 c164edb8 GPR04: 0800 GPR08: 0003 00bf 00bf c00172a0 GPR12: 22002482 cfe4 fe80 fe90 GPR16: fea0 feb0 fec0 GPR20: 010003df8420 c000b1bfbe00 0400 GPR24: 0001 c15f2ed8 c000b1bfbdc0 GPR28: c16e4c80 c16e4fc4 c78e6600 c001f8d6b9d0 [708665.379401] NIP [c04b790c] .tg_prfill_cpu_rwstat+0xac/0x180 [708665.379517] LR [c04b78d8] .tg_prfill_cpu_rwstat+0x78/0x180 [708665.379643] Call Trace: [708665.379694] [c001f8d6b900] [c00130138e18] 0xc00130138e18 (unreliable) [708665.379854] [c001f8d6ba20] [c04b4710] .blkcg_print_blkgs+0xf0/0x1b0 [708665.380026] [c001f8d6bae0] [c04b7730] .tg_print_cpu_rwstat+0x50/0x80 [708665.380204] [c001f8d6bb70] [c01381ec] .cgroup_seqfile_show+0x9c/0xc0 [708665.380384] [c001f8d6bc00] [c0287e98] .seq_read+0x158/0x570 [708665.380526] [c001f8d6bcf0] [c02560d4] .vfs_read+0xc4/0x1f0 [708665.380679] [c001f8d6bd90] [c0256ef4] .SyS_read+0x64/0xe0 [708665.380811] [c001f8d6be30] [c000a158] syscall_exit+0x0/0x98 [708665.380956] Instruction dump: [708665.381040] 813d 3be100d0 7c6307b4 7f891800 409d00b0 3d420009 392a1ca8 786a1f24 [708665.381268] 7d49502a e93e01c8 7d495214 7d2ad214 <7cead02a> e9090008 e9490010 e9290018 [708665.381505] ---[ end trace 512b8ac8f55926fd ]--- [708665.387710] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: User Name 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.2 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or director
[Kernel-packages] [Bug 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards
Bug confirmed for Logitech h540 Device is listed as "USB-Audio - Logitech USB Headset H540" The proposed workaround fixed the issue. -- 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/1002952 Title: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards Status in “alsa-lib” package in Ubuntu: Confirmed Bug description: === Read me first === = Symptom = If you have a USB headset, or other USB device that does not have any S/PDIF output, but yet sometimes there is an extra device called "Digital Output (S/PDIF)" for that device, you're suffering from this bug. This bug is only for USB devices - if you have an invalid digital output for some other type of device, please file a separate bug instead. = Workaround = If you're affected, please try this workaround: first check the output of "aplay -l" (lowercase L), or "arecord -l" if it's an input device, and grab the first of two name in brackets: Example: card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio] here grab the name "Sennheiser USB Headset". Now edit the file /usr/share/alsa/cards/USB-Audio.conf (requires root permissions) Around line 40, you will find a line saying "Logitech USB Headset" 999 Add a new line after this line, so that there is now a new line called "Sennheiser USB Headset" 999 (including quotes, and replace "Sennheiser USB Headset" with whatever your particular card was named.) Save the file and reboot your computer for the changes to take effect. = Already known devices = These card names are already in 12.04: "Blue Snowball" "Logitech USB Headset" "Logitech Web Camera" These card names are on their way into 12.04: "Logitech Speaker Lapdesk N700" "Logitech Wireless Headset" "Plantronics USB Headset" "Sennheiser USB headset" If you have one of the above four, please help out by testing the proposed repository and report back in bug 987163. If your name is not listed above, please add a comment to this bug, including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo - they will be collected for a SRU later on, or at least make it into the next release of Ubuntu. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Might be related to Lorenzo's thought: the random jumping and clicking only happen when the touchpad is treated as touchpad. I haven't had any problem when loading the touchpad driver as a simple mouse (no scrolling, tapping, multitouch, ... for the touchpad): sudo modprobe -r psmouse sudo modprobe psmouse proto=imps I also found that whenever the touchpad started behaving badly (lots of "lost sync" messages), reloading the driver seems to reset it back to be good for a long while: sudo modprobe -r psmouse sudo modprobe psmouse About keyboard input, it might be hardware (pretty common for Dell). I have an E6440 that I can easily reproduce the key repititions by hitting the keys in a certain way (e.g. tapping a key straight down lightly while relaxing my finger). It looks a lot like the "bounce" effect in the old desktop keyboards, perhaps Dell didn't put in good-enough bounce-filtering. I can reproduce the same problem in Windows and FreeDOS. My E7440 also had that problem initially (although not as easy to produce as the E6440), but not after Dell replaced the keyboard (together with the touchpad). One solution for the keyboard repetition is to set the Bounce rate: Universal Access > Typing > Bounce Keys > Acceptance delay. You will have to experiment to find the right rate that work for you without missing intentional repetition (especially when smashing the keys when playing games). What works for my E6440 is to drag the delay all the way to shortest, then move the slider to the right (long) twice using the "right arrow" 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/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in “linux” package in Ubuntu: Incomplete Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad". This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. 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/controlC1: allanc 1852 F pulseaudio /dev/snd/controlC0: allanc 1852 F pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro 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: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- Mailing list: https://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 1261668] Re: Intel 7260 firmware causes crashes, needs updating
*** This bug is a duplicate of bug 1265436 *** https://bugs.launchpad.net/bugs/1265436 On Thu, Jul 31, 2014 at 04:01:48PM -, JaSauders wrote: > There was a lengthy bug report that was just split off to a new report > to centralize around these issues. Perhaps you can read it over and see > if this applies to you. No! I've been trying to be clear in my previous responses to your messages, but let me reiterate: I do _not_ want a centralized bug report. It's better for users to file an individual bug report so we can capture the logs and hardware information from that machine, unless they have the exact same machine and symptoms as the existing bug. We can always dup bugs later if we find out that they really do represent the same problem. In this case the problems are clearly unrelated, since this one is about a firmware crash and the one you point out has nothing to do with firmware crashes. When we start piling unrelated problems onto a single bug report it can quickly become unmanagable. So _please_ do not point people at a single, "central" bug report for 7260 wireless issues. Thanks! -- 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/1261668 Title: Intel 7260 firmware causes crashes, needs updating Status in System76: New Status in “linux-firmware” package in Ubuntu: Triaged Bug description: The firmware we currently ship for the intel 7260 wireless card is buggy, and causing frequent crashes. See http://www.spinics.net/lists/linux-wireless/msg114861.html There is updated firmware available, see http://marc.info/?l=linux- wireless&m=138718659005765&w=2 We should get this updated, as this is becoming a very popular wireless card (System76 are shipping it in their systems) and it's a pain having to reboot every time it crashes... To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1261668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1261668] Re: Intel 7260 firmware causes crashes, needs updating
*** This bug is a duplicate of bug 1265436 *** https://bugs.launchpad.net/bugs/1265436 This wireless card is extremely problematic on any operating system. Users from Windows 7, 8, 8.1, BSD, Arch, Gentoo, Ubuntu have all reported the exact same issue. A quick Google search of this card reveals a world of complaints that makes me truly question why companies are *still* shipping it... System76, Dell, Lenovo, WHY ship a problematic card? I called Intel about my frequent disconnects on my XPS 13 Ubuntu Dev Edition, and Intel confirmed it is a known problem and they are working for a fix. (though they've been working on a fix since this chip came out a year ago with no substantial headway yet, so...). Given the length of time this chip has been out with no actual fix, I'm likely going to be stuck with swapping out my XPS with a non-7260 unit as per Dell, as Dell has no other M.2 form factor wireless cards to swap with, so that's all they could offer. I have tried Intel's latest firmware at the time of this post and can confirm it yielded no difference in results. I still disconnect at random across the 5 wireless networks I tested with different encryption levels. Sometimes it's once every 3 days (no big deal), other times a dozen times in 20 minutes (major deal breaker). It's wildly sporadic. There was a lengthy bug report that was just split off to a new report to centralize around these issues. Perhaps you can read it over and see if this applies to you. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349572 -- 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/1261668 Title: Intel 7260 firmware causes crashes, needs updating Status in System76: New Status in “linux-firmware” package in Ubuntu: Triaged Bug description: The firmware we currently ship for the intel 7260 wireless card is buggy, and causing frequent crashes. See http://www.spinics.net/lists/linux-wireless/msg114861.html There is updated firmware available, see http://marc.info/?l=linux- wireless&m=138718659005765&w=2 We should get this updated, as this is becoming a very popular wireless card (System76 are shipping it in their systems) and it's a pain having to reboot every time it crashes... To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1261668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
>From IRC, an example of a testcase:
1) create around ~300GB of small files (sqlite files for example), put the
files into a list sqlite-files.txt
2) Start the copy:
cat sqlite-files.txt | xargs -n1 -I{} -P2 sudo sh -c 'rm -f {}.new; cat {} >
{}.new; echo {}'
3) When it hangs, identify where it hung as $NUM and resume with the following:
tail -n+$NUM | xargs -n1 -I{} -P2 sudo sh -c 'rm -f {}.new; cat {} > {}.new;
echo {}'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247056.192053] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[247056.212061] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists
[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest
** Changed in: linux (Ubuntu Trusty) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350373 Title: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Bug description: Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while expanding the grant table (usually when requested by blkfront, when booting). See an example trace below. This is caused by calling functions that are unsafe in atomic context. The fix (which has been submitted to 3.16) is available here (also attached): https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable /for-linus-3.16&id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168 The fix is applicable to all kernel since 2.6.39 but only appears to trigger with the 3.13 kernel in 14.04. [2.577876] [ cut here ] [2.577896] kernel BUG at /build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239! [2.577910] invalid opcode: [#1] SMP [2.577922] Modules linked in: [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic #46-Ubuntu [2.577946] task: ec058000 ti: ec09 task.ti: ec09 [2.577955] EIP: 0061:[] EFLAGS: 00010002 CPU: 0 [2.577973] EIP is at enter_lazy.part.1+0x3/0x5 [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50 [2.578001] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660 [2.578027] Stack: [2.578032] ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff edc01000 c1a93018 [2.578052] edc00fff c193ce80 edc01000 [2.578076] ed3ef588 ed3ef588 c1b87b70 ec091ad0 edc01000 c1b65310 1000 [2.578096] Call Trace: [2.578111] [] paravirt_enter_lazy_mmu+0x24/0x30 [2.578127] [] apply_to_page_range+0x1a3/0x310 [2.578141] [] arch_gnttab_map_status+0x38/0x60 [2.578152] [] ? map_pte_fn+0x70/0x70 [2.578166] [] gnttab_map_frames_v2+0xb0/0x100 [2.578182] [] gnttab_map+0x95/0x120 [2.578198] [] ? blk_update_request+0x190/0x340 [2.578209] [] get_free_entries+0xd3/0x280 [2.578221] [] gnttab_alloc_grant_references+0x13/0x30 [2.578238] [] do_blkif_request+0x535/0x6f0 [2.578253] [] ? _raw_spin_unlock_irqrestore+0x1c/0x40 [2.578269] [] __blk_run_queue+0x2e/0x40 [2.578280] [] blk_start_queue+0x25/0x40 [2.578291] [] kick_pending_request_queues+0x1e/0x30 [2.578304] [] blkif_interrupt+0x69f/0x740 [2.578318] [] ? xen_set_pte_at+0xbf/0xf0 [2.578335] [] handle_irq_event_percpu+0x35/0x1a0 [2.578351] [] ? radix_tree_lookup+0xa/0x10 [2.578364] [] handle_irq_event+0x31/0x50 [2.578376] [] handle_edge_irq+0x66/0x110 [2.578389] [] __xen_evtchn_do_upcall+0x1c6/0x2c0 [2.578402] [] xen_evtchn_do_upcall+0x20/0x40 [2.578415] [] xen_do_upcall+0x7/0xc [2.578427] [] ? xen_hypercall_xen_version+0x7/0x20 [2.578441] [] ? xen_force_evtchn_callback+0xf/0x20 [2.578454] [] check_events+0x8/0xc [2.578464] [] ? xen_restore_fl_direct_reloc+0x4/0x4 [2.578480] [] ? xen_batched_set_pte+0xb3/0x160 [2.578493] [] xen_set_pte_at+0x28/0xf0 [2.578505] [] ? __raw_callee_save_xen_pte_val+0x6/0x8 [2.578521] [] copy_pte_range+0x258/0x4c0 [2.578534] [] copy_page_range+0x1d7/0x2e0 [2.578549] [] dup_mm+0x28e/0x4f0 [2.578561] [] copy_process.part.33+0xfa6/0x10d0 [2.578574] [] do_fork+0xc1/0x2c0 [2.578591] [] ? SyS_rt_sigprocmask+0x76/0xa0 [2.578604] [] SyS_clone+0x25/0x30 [2.578615] [] sysenter_do_call+0x12/0x28 [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 <0f> 0b 55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5 [2.578745] EIP: [] enter_lazy.part.1+0x3/0x5 SS:ESP 0069:ec091a50 [2.578765] ---[ end trace ab5b5344be71ca3d ]--- [2.578775] Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
Peter also tested on a single core machine and was able to reproduce the
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/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247056.192053] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[247056.212061] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350943] [NEW] [ASUS All Series] suspend/resume failure
Public bug reported: When I suspen PC it never resumes. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-6-generic 3.16.0-6.11 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 2456 F pulseaudio /dev/snd/controlC2: steve 2456 F pulseaudio /dev/snd/controlC0: steve 2456 F pulseaudio Date: Thu Jul 31 18:49:21 2014 DuplicateSignature: suspend/resume:ASUS All Series:0702 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=7cfe0217-dcf3-47f0-a0f5-dbca0209bd41 InstallationDate: Installed on 2014-07-13 (18 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed root=UUID=6abc1ba3-5b17-404f-a4d7-562829e4d2b5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: SourcePackage: linux Title: [ASUS All Series] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1M-A 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.:bvr0702:bd06/25/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops resume suspend utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350943 Title: [ASUS All Series] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: When I suspen PC it never resumes. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-6-generic 3.16.0-6.11 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 2456 F pulseaudio /dev/snd/controlC2: steve 2456 F pulseaudio /dev/snd/controlC0: steve 2456 F pulseaudio Date: Thu Jul 31 18:49:21 2014 DuplicateSignature: suspend/resume:ASUS All Series:0702 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=7cfe0217-dcf3-47f0-a0f5-dbca0209bd41 InstallationDate: Installed on 2014-07-13 (18 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed root=UUID=6abc1ba3-5b17-404f-a4d7-562829e4d2b5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: SourcePackage: linux Title: [ASUS All Series] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled
[Kernel-packages] [Bug 1350943] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350943 Title: [ASUS All Series] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: When I suspen PC it never resumes. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-6-generic 3.16.0-6.11 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 2456 F pulseaudio /dev/snd/controlC2: steve 2456 F pulseaudio /dev/snd/controlC0: steve 2456 F pulseaudio Date: Thu Jul 31 18:49:21 2014 DuplicateSignature: suspend/resume:ASUS All Series:0702 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=7cfe0217-dcf3-47f0-a0f5-dbca0209bd41 InstallationDate: Installed on 2014-07-13 (18 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed root=UUID=6abc1ba3-5b17-404f-a4d7-562829e4d2b5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: SourcePackage: linux Title: [ASUS All Series] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1M-A 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.:bvr0702:bd06/25/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350943] Re: [ASUS All Series] suspend/resume failure
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350943 Title: [ASUS All Series] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: When I suspen PC it never resumes. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-6-generic 3.16.0-6.11 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 2456 F pulseaudio /dev/snd/controlC2: steve 2456 F pulseaudio /dev/snd/controlC0: steve 2456 F pulseaudio Date: Thu Jul 31 18:49:21 2014 DuplicateSignature: suspend/resume:ASUS All Series:0702 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=7cfe0217-dcf3-47f0-a0f5-dbca0209bd41 InstallationDate: Installed on 2014-07-13 (18 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed root=UUID=6abc1ba3-5b17-404f-a4d7-562829e4d2b5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: SourcePackage: linux Title: [ASUS All Series] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1M-A 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.:bvr0702:bd06/25/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350947] [NEW] apparmor: no working rule to allow making a mount private
Public bug reported:
When the file system is mounted as MS_SHARED by default (such as under
systemd, or when the admin configures it so), things like schroot or LXC
need to make their "guest" mounts private. This currently fails under
utopic:
$ sudo lxc-create -t busybox -n c1
$ sudo mount --make-rshared /
$ sudo strace -fvvs1024 -e mount lxc-start -n c1
[...]
[pid 10749] mount(NULL, "/", NULL, MS_SLAVE, NULL) = -1 EACCES (Permission
denied)
lxc-start: Permission denied - Failed to make / rslave
dmesg says:
audit: type=1400 audit(1406825005.687:551): apparmor="DENIED" operation="mo
unt" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/"
pid=8228 co
mm="lxc-start" flags="rw, slave"
(This happens for all mount points on your system, I'm just showing the
first one)
This will leave a couple of leaked mounts on your system. THis is an
useful rune to clean them up:
$ for i in 1 2 3; do sudo umount `mount|grep lxc|awk '{print $3}'`; done
(needs to be done several times; check with "mount |grep lxc" that it's
clean)
I tried to allow that by adding this to /etc/apparmor.d/abstractions/lxc
/start-container:
mount options=(rw, slave) -> **,
then reload the policy and rety with
$ sudo stop lxc; sudo start lxc; sudo lxc-start -n c1
(and again clean up the mounts with above rune)
I tried some variations of this, like
mount options in (rw, slave, rslave, shared, rshared) -> **,
but none of them worked. The only things that do work are one of
mount,
mount -> **,
but those are too lax to be an effestive security restriction.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-6-generic 3.16.0-6.11
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1665 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 31 18:58:18 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (154 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
MachineType: LENOVO 2324CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed
root=UUID=a2b27321-0b55-44c9-af0d-6c939efa45ce ro quiet splash
init=/lib/systemd/systemd crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-6-generic N/A
linux-backports-modules-3.16.0-6-generic N/A
linux-firmware1.132
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324CTO
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: Confirmed
** Affects: lxc (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: Triaged
** Tags: amd64 apparmor apport-bug systemd-boot third-party-packages utopic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in “linux” package in Ubuntu:
Confirmed
Status in “lxc” package in Ubuntu:
Triaged
Bug description:
When the file system is mounted as MS_SHARED by default (such as under
systemd, or when the admin configures it so), things like schroot or
LXC need to make their "guest" mounts private. This currently fails
under utopic:
$ sudo lxc-create -t busybox -n c1
$ sudo mount --make-rshared /
$ sudo strace -fvvs1024 -e mount lxc-start -n c1
[...]
[pid 10749] mount(NULL, "/", NULL, MS_SLAVE, NULL) = -1 EACCES (Permission
denied)
lxc-start: Permission denied - Failed to make / rslave
dmesg says:
audit: type=1400 audit(1406825005.687:551): apparmor="DENIED" operation="mo
unt" info="failed flags match" error=-13 profile="/usr/bin/lxc-start"
name="/" pid=8228 co
mm="lxc-start" flags="rw, slave"
(This happens for all mount points on your system, I'm just showing
the first one)
This will leave a couple of leaked mounts on your system. THis is an
useful rune to clean them up:
$ for i in 1 2 3; do sudo umount `mount|grep lxc|awk '{print $3}'`;
done
(needs to be done several times; check with "mount |grep lxc" that
it's clean)
I tried to allow that by adding this to
/etc
[Kernel-packages] [Bug 1350947] Re: apparmor: no working rule to allow making a mount private
I tested this on trusty's 3.13.0-32, and the previous utopic 3.15.0-6,
same result. So it's not a regression apparently; although I tried
"mount options=(rw, slave) -> /" some weeks ago and it appeared to work,
but apparently I did something weird back then which made it work, but I
can't remember how any more.
** Tags added: apparmor
** Description changed:
When the file system is mounted as MS_SHARED by default (such as under
systemd, or when the admin configures it so), things like schroot or LXC
need to make their "guest" mounts private. This currently fails under
utopic:
$ sudo lxc-create -t busybox -n c1
$ sudo mount --make-rshared /
$ sudo strace -fvvs1024 -e mount lxc-start -n c1
[...]
[pid 10749] mount(NULL, "/", NULL, MS_SLAVE, NULL) = -1 EACCES (Permission
denied)
lxc-start: Permission denied - Failed to make / rslave
dmesg says:
audit: type=1400 audit(1406825005.687:551): apparmor="DENIED" operation="mo
unt" info="failed flags match" error=-13 profile="/usr/bin/lxc-start"
name="/" pid=8228 co
mm="lxc-start" flags="rw, slave"
+ (This happens for all mount points on your system, I'm just showing the
+ first one)
+
This will leave a couple of leaked mounts on your system. THis is an
useful rune to clean them up:
$ for i in 1 2 3; do sudo umount `mount|grep lxc|awk '{print $3}'`; done
(needs to be done several times; check with "mount |grep lxc" that it's
clean)
+ I tried to allow that by adding this to /etc/apparmor.d/abstractions/lxc
+ /start-container:
- I tried to allow that by adding this to
/etc/apparmor.d/abstractions/lxc/start-container:
-
- mount options=(rw, slave) -> **,
+ mount options=(rw, slave) -> **,
then reload the policy and rety with
$ sudo stop lxc; sudo start lxc; sudo lxc-start -n c1
(and again clean up the mounts with above rune)
I tried some variations of this, like
- mount options in (rw, slave, rslave, shared, rshared) -> **,
+ mount options in (rw, slave, rslave, shared, rshared) -> **,
but none of them worked. The only things that do work are one of
- mount,
- mount -> **,
+ mount,
+ mount -> **,
but those are too lax to be an effestive security restriction.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-6-generic 3.16.0-6.11
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: martin 1665 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: martin 1665 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 31 18:58:18 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (154 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
MachineType: LENOVO 2324CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed
root=UUID=a2b27321-0b55-44c9-af0d-6c939efa45ce ro quiet splash
init=/lib/systemd/systemd crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
- linux-restricted-modules-3.16.0-6-generic N/A
- linux-backports-modules-3.16.0-6-generic N/A
- linux-firmware1.132
+ linux-restricted-modules-3.16.0-6-generic N/A
+ linux-backports-modules-3.16.0-6-generic N/A
+ linux-firmware1.132
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324CTO
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in “linux” package in Ubuntu:
Confirmed
Status in “lxc” package in Ubuntu:
Triaged
Bug description:
When the file system is mounted as MS_SHARED by default (such as under
systemd, or when the admin configures it so), things like schroot or
LXC need to make their "guest" mounts private. This currently fails
under utopic:
$ sudo lxc-create -t busybox -n c1
$ sudo mount --make-rshared /
$ sudo strace -fvvs1024 -e mount lxc-start -n c1
[...]
[pid 10749] mount(NULL, "/", NULL, MS_SLAVE, NULL) = -1 EACCES (P
[Kernel-packages] [Bug 1350947] Re: apparmor: no working rule to allow making a mount private
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** 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/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in “linux” package in Ubuntu:
Confirmed
Status in “lxc” package in Ubuntu:
Triaged
Bug description:
When the file system is mounted as MS_SHARED by default (such as under
systemd, or when the admin configures it so), things like schroot or
LXC need to make their "guest" mounts private. This currently fails
under utopic:
$ sudo lxc-create -t busybox -n c1
$ sudo mount --make-rshared /
$ sudo strace -fvvs1024 -e mount lxc-start -n c1
[...]
[pid 10749] mount(NULL, "/", NULL, MS_SLAVE, NULL) = -1 EACCES (Permission
denied)
lxc-start: Permission denied - Failed to make / rslave
dmesg says:
audit: type=1400 audit(1406825005.687:551): apparmor="DENIED" operation="mo
unt" info="failed flags match" error=-13 profile="/usr/bin/lxc-start"
name="/" pid=8228 co
mm="lxc-start" flags="rw, slave"
(This happens for all mount points on your system, I'm just showing
the first one)
This will leave a couple of leaked mounts on your system. THis is an
useful rune to clean them up:
$ for i in 1 2 3; do sudo umount `mount|grep lxc|awk '{print $3}'`;
done
(needs to be done several times; check with "mount |grep lxc" that
it's clean)
I tried to allow that by adding this to
/etc/apparmor.d/abstractions/lxc/start-container:
mount options=(rw, slave) -> **,
then reload the policy and rety with
$ sudo stop lxc; sudo start lxc; sudo lxc-start -n c1
(and again clean up the mounts with above rune)
I tried some variations of this, like
mount options in (rw, slave, rslave, shared, rshared) -> **,
but none of them worked. The only things that do work are one of
mount,
mount -> **,
but those are too lax to be an effestive security restriction.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-6-generic 3.16.0-6.11
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1665 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 31 18:58:18 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (154 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
MachineType: LENOVO 2324CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed
root=UUID=a2b27321-0b55-44c9-af0d-6c939efa45ce ro quiet splash
init=/lib/systemd/systemd crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-6-generic N/A
linux-backports-modules-3.16.0-6-generic N/A
linux-firmware1.132
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324CTO
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350947/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350947] Re: apparmor: no working rule to allow making a mount private
Adding an LXC task; after we figure out how the rule needs to look
like/fixing the apparmor parser or linux bug, we need to adjust LXC's
apparmor policy. This was originally bug 1325468, but it's easier to
have it in one bug.
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in “linux” package in Ubuntu:
Confirmed
Status in “lxc” package in Ubuntu:
Triaged
Bug description:
When the file system is mounted as MS_SHARED by default (such as under
systemd, or when the admin configures it so), things like schroot or
LXC need to make their "guest" mounts private. This currently fails
under utopic:
$ sudo lxc-create -t busybox -n c1
$ sudo mount --make-rshared /
$ sudo strace -fvvs1024 -e mount lxc-start -n c1
[...]
[pid 10749] mount(NULL, "/", NULL, MS_SLAVE, NULL) = -1 EACCES (Permission
denied)
lxc-start: Permission denied - Failed to make / rslave
dmesg says:
audit: type=1400 audit(1406825005.687:551): apparmor="DENIED" operation="mo
unt" info="failed flags match" error=-13 profile="/usr/bin/lxc-start"
name="/" pid=8228 co
mm="lxc-start" flags="rw, slave"
(This happens for all mount points on your system, I'm just showing
the first one)
This will leave a couple of leaked mounts on your system. THis is an
useful rune to clean them up:
$ for i in 1 2 3; do sudo umount `mount|grep lxc|awk '{print $3}'`;
done
(needs to be done several times; check with "mount |grep lxc" that
it's clean)
I tried to allow that by adding this to
/etc/apparmor.d/abstractions/lxc/start-container:
mount options=(rw, slave) -> **,
then reload the policy and rety with
$ sudo stop lxc; sudo start lxc; sudo lxc-start -n c1
(and again clean up the mounts with above rune)
I tried some variations of this, like
mount options in (rw, slave, rslave, shared, rshared) -> **,
but none of them worked. The only things that do work are one of
mount,
mount -> **,
but those are too lax to be an effestive security restriction.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-6-generic 3.16.0-6.11
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1665 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 31 18:58:18 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (154 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
MachineType: LENOVO 2324CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic.efi.signed
root=UUID=a2b27321-0b55-44c9-af0d-6c939efa45ce ro quiet splash
init=/lib/systemd/systemd crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-6-generic N/A
linux-backports-modules-3.16.0-6-generic N/A
linux-firmware1.132
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET95WW (2.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324CTO
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350947/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 306003] Re: smartctl short test hangs at 90%
I confirm this bug for Ubuntu 14.04 LTS, gnome-disk-utility and an OCZ Vertex 4 SSD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/306003 Title: smartctl short test hangs at 90% Status in “linux” package in Ubuntu: Expired Bug description: It seems that after upgrading to 8.04 smartctl short test seems to hang at 90% (ie it never finishes). The following test hangs at 90%: sudo smartctl -t short /dev/sda Output from smartcrl -a /dev/sda Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. according to this report http://smartmontools.markmail.org/message/afuajgivzxhjjgzd?q=test+90%25 a recent kernel fixed it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/306003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
So at this point it would be good to have a clear idea of how to get into this
state to better understand the issue.
Could you write a detailed description of how you setup your machine/volume,
then others can try to run a similar test here and see if we can reproduce the
same results?
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/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247056.192053] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[247056.212061] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166873/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166879/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166880/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] Re: Could not force DPM to low
apport information ** Tags added: apport-collected trusty ** Description changed: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: imran 4208 F pulseaudio + /dev/snd/controlC0: imran 4208 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 + InstallationDate: Installed on 2014-07-25 (6 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-32-generic N/A + linux-backports-modules-3.13.0-32-generic N/A + linux-firmware 1.132~gd~t + Tags: trusty + Uname: Linux 3.13.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/25/2011 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: F.46 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 3628 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: 18.51 + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: + dmi.product.name: HP Pavilion dv6 Notebook PC + dmi.product.version: Rev 1 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166872/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166881/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166877/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166878/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166875/+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/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166882/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166876/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] Re: Could not force DPM to low
Done, now what? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166887/+files/WifiSyslog.txt ** 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/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166884/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166883/+files/PulseList.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/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166886/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166885/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350519] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1350519/+attachment/4166874/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350519 Title: Could not force DPM to low Status in “linux” package in Ubuntu: Confirmed Bug description: When resuming from suspend state to awake state, by pressing the power button of my laptop i see this message? Jul 30 17:48:03 imran-HP-Pavilion-dv6-Notebook-PC kernel: [10760.470694] [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imran 4208 F pulseaudio /dev/snd/controlC0: imran 4208 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=f64b1ebb-cf58-44da-b46e-bae95a9c8367 InstallationDate: Installed on 2014-07-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.132~gd~t Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.46:bd08/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.51:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350519/+subscriptions -- Mailing list: https://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 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
As far as I know installing the card is a PITA. Otherwise I would have done that already. But, if it isn't too taxing (taking the motherboard out or taking apart the screen would be too taxing), I would love to know. On Thu, Jul 31, 2014 at 11:08 AM, Juan wrote: > I realized that I probably picked the wrong card when ordering my laptop. > I was offered either the Intel Wireless N 7260 or this Realtek card, same > price > I am not so keen with this realtek card anyway because even in windows 7 > my signal only shows 3 bars sometimes as my previous laptop it's 5 bar > all-the-time > Instead of buying a usb dongle and wait for the driver I was considering > to just buy the intel card for $20 and swap it in > Some of you guys may consider this option as the other card is certified > by ubuntu and I assume it has the driver built-in? Can anyone with the > T440/540 with the Intel card confirm that? > > Thanks, > Juan > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1239578 > > Title: > No wireless support for Realtek RTL8192EE [10ec:818b] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1239578/+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/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
I realized that I probably picked the wrong card when ordering my laptop. I was offered either the Intel Wireless N 7260 or this Realtek card, same price I am not so keen with this realtek card anyway because even in windows 7 my signal only shows 3 bars sometimes as my previous laptop it's 5 bar all-the-time Instead of buying a usb dongle and wait for the driver I was considering to just buy the intel card for $20 and swap it in Some of you guys may consider this option as the other card is certified by ubuntu and I assume it has the driver built-in? Can anyone with the T440/540 with the Intel card confirm that? Thanks, Juan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1350513] Re: Ctrl+Alt+F1 shuts down laptop
Dear Christopher, Here's the description at the Sony page for the BIOS R2060Y0 update: If your VAIO hardware supports Intel Virtualization Technology, this setting will be added to the BIOS. The VT setting is disabled by default. Are you sure this is related to the issue reported? Updating the BIOS - especially in a computer that has os Microsoft software at all - is not a step to be taken lightly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1350513 Title: Ctrl+Alt+F1 shuts down laptop Status in “linux” package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 on Sony Vaio VGN-FW31ZJ. Whenever I try to switch to a TTY, say by pressing Ctrl+Alt+F1, the system shuts down. The text user name prompt appears for a split second but quickly everything goes black. I then have to press and hold the On/Off chassis button (as in a regular switch on) and wait for the whole start up process to go through: BIOS, Grub and so on. I have used Ubuntu on this laptop since 8.10 and never had such odd behaviour. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lads 2307 F pulseaudio /dev/snd/controlC1: lads 2307 F pulseaudio /dev/snd/pcmC1D0p: lads 2307 F...m pulseaudio /dev/snd/controlC0: lads 2307 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 30 21:43:05 2014 HibernationDevice: RESUME=UUID=3e528dc8-cff2-4953-946f-e811a25f65d0 InstallationDate: Installed on 2013-01-01 (574 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Sony Corporation VGN-FW31ZJ ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=1737b96c-878e-4f49-aa43-80d76ab1a740 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-23 (7 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 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.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW31ZJ:pvrC6015DPB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FW31ZJ dmi.product.version: C6015DPB dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
Hm, I'm not sure I can give a thorough description since I don't
understand enough about the exact workload myself. It is a fairly
arbitrary workload generated by our users.
In the end, it boils down to creating, reading and writing many
(~20,000) sqlite files of size 16kb - 12GB across many folders and doing
random read/write IO to them. The directory structure is that all 20,000
files live inside a directory of one root directory, like so:
/path/1/file.sqlite
/path/2/file.sqlite
etc.
The 500GB volume has approximately 275GB of such files. When copying
/path/1/file.sqlite to /path/1/file.sqlite.new (and so on) with
`cat` twice in parallel (via xargs -P2 as in #11), the volume eventually
(after multiple hours) hangs. If the copying is resumed from the last
file successfully copied before the hang, the hang onset is very rapid.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: so
[Kernel-packages] [Bug 1349711] Re: Machine lockup in btrfs-transaction
(otherwise unloaded test machines)
On a dual core machine, 100% system CPU usage with zero writes is seen
on one core for 5-10 minutes, spending time in BTRFS threads.
On a single thread machine 100% system CPU is used and I haven't yet
been able to cause it to hang entirely. I do observe almost completely
100% system CPU usage and very low IO rates, 0 IOPS for up to minutes at
a time before it then goes to >1000 IOPs.
The system goes to IOWAIT when there is significant IO traffic, and
otherwise kernel threads are consuming CPU.
However the latter is on a non-prewarmed EBS. So I am not sure if the
behaviour we're seeing is entirely due to cold block storage where we
have no latency/rate guarantees.
Generally, I can't tell if we have hit a bug in the BTRFS free extent
code, or if it is all due to bad EBS performance and a spinlock
somewhere.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349711
Title:
Machine lockup in btrfs-transaction
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This has happened twice now.
I'm on an AWS EC2 m3.large instance with the official Ubuntu AMI ami-
776d9700.
# cat /proc/version_signature
Ubuntu 3.13.0-32.57-generic 3.13.11.4
After running for many days, the machine locked up with the below
messages appearing on the console. The machine would respond to ping
but not SSH or HTTP requests. The machine has one BTRFS volume which
is 87% full and lives on an Logical Volume Manager (LVM) block device
on top of one Amazon Elastic Block Store (EBS) device.
Error messages after first reboot:
[ 77.609490] BTRFS error (device dm-0): block group 10766778368 has wrong
amount of free space
[ 77.613678] BTRFS error (device dm-0): failed to load free space cache for
block group 10766778368
[ 77.643801] BTRFS error (device dm-0): block group 19356712960 has wrong
amount of free space
[ 77.648952] BTRFS error (device dm-0): failed to load free space cache for
block group 19356712960
[ 77.926325] BTRFS error (device dm-0): block group 20430454784 has wrong
amount of free space
[ 77.931078] BTRFS error (device dm-0): failed to load free space cache for
block group 20430454784
[ 78.111437] BTRFS error (device dm-0): block group 21504196608 has wrong
amount of free space
[ 78.116165] BTRFS error (device dm-0): failed to load free space cache for
block group 21504196608
Error messages after second reboot:
[ 45.390221] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 45.413472] BTRFS error (device dm-0): free space inode generation (0) did
not match free space cache generation (70012)
[ 467.423961] BTRFS error (device dm-0): block group 518646661120 has wrong
amount of free space
[ 467.429251] BTRFS error (device dm-0): failed to load free space cache for
block group 518646661120
Error messages on the console after second lock-up follow:
[246736.752053] INFO: rcu_sched self-detected stall on CPU { 0} (t=2220246
jiffies g=35399662 c=35399661 q=0)
[246736.756059] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected
by 1, t=2220247 jiffies, g=35399662, c=35399661, q=0)
[246764.192014] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246764.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246792.192022] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246792.212057] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246820.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246820.212018] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246848.192052] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u30:2:1828]
[246848.212058] BUG: soft lockup - CPU#1 stuck for 23s! [btrfs-transacti:492]
[246876.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246876.212057] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246904.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246904.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246916.772052] INFO: rcu_sched self-detected stall on CPU[246916.776058]
INFO: rcu_sched detected stalls on CPUs/tasks:
[246944.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246944.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[246972.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[246972.212018] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247000.192053] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247000.212058] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:492]
[247028.192054] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u30:2:1828]
[247028.212058] BUG: soft
[Kernel-packages] [Bug 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device
Confirming for Trusty 14.04 x64. but exist one solution: 1) Connect your phone with ubuntu via bluetooth. 2) Go to directory on phone. For example: photos, if you want copy some of your importatnt photos. 3) Select only one file! And choose send by email (right mouse contect menu send). Do not select zip option! 4) After some time your default email program will prepare message with selected photo. 5) Send it and check your email! It works only for one file per email! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device
It also works much quicker when you send file by file to shared folder and disks. For example flash card. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
If Lenovo does not have an access door on the bottom that provides access to the wireless card, I am doubly glad that I chose Toshiba over Lenovo when I recently purchased a new laptop. My decision was based on the bad reviews for the new keyboard and touchpad design. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
I just took it apart and tried it. Easy. On my 540p there are 2 service panels at the bottom 1 for HDD and memory the other smaller one is the wifi card. I already swapped the HDD with SSD by taking apart the larger one. Just make sure you get the Intel 7260 NGW form factor for the half- mini size pci slot. I'll probably even upgrade to the Dual band version for $30, even better! http://www.ebay.com/itm/INTEL-7260NGW-M-2-NGFF-Wireless-N-Card-802-11AN- Bluetooth-4-0-/97326988?pt=US_Internal_Network_Cards&hash=item19e3e08e8c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
