-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: matt 2675 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Oct 5 12:06:58 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
InstallationDate: Installed
SS COMMAND
/dev/snd/controlC0: matt 2675 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Oct 5 12:06:58 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
InstallationDate: Installed on 2015-12-01 (308 days ago)
InstallationMedia: Xub
The attached JournalErrors.txt file shows the kernel call trace for the
error that occurs.
** 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.
Built a custom linux 4.8-rc8 kernel and I have not seen this problem
since. This is most likely a kernel bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
happend during update
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-41.61~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-41-generic i686
ApportVersion: 2.14.1-0ubuntu3.21
I can't be sure that we ran into the exact same bug, but Amazon seems to
think we may have. I can't find the beginning of the console log, but
here's a mid-point that shows the hang:
Host Type: Amazon EC2 r3.8xlarge
OS: Ubuntu 14.04.5
Kernel: 3.13.0-93-generic
Networking: Intel Enhanced Neworking
I too have experienced this revival on Ubuntu 16.04.1 LTS
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/445852
Title:
devkit-disks-probe-ata-smart causes HSM Violations on SSD,
Ubuntu 15.10 on a Dell XPS 8900 was freezing several times a day
regardless of which kernel I used. Froze more frequently when I used
dual monitors. Problem disappeared completely when I switched my
graphics driver from Nouveau to Nvidia (clicked on Settings in Software
Updater, selected the
FYI the fix is now in linux 4.7-rc1:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/input/joystick/xpad.c?h=v4.7-rc1=4efc6939a83c54fb3417541be48991afd0290ba3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@njmcphail Thanks for sharing your input over on github. Hopefully
paroj's new fix[1] works better!
I won't be able to test it out until next weekend but I thought I'd
mention its existence here so the ubuntu guys can add it (since they
backported the the regression in #1564901)
[1]:
The regression I mentioned in #7 should be fixed in
https://github.com/paroj/xpad/commit/ef9e5b156c4b0042a75897697a792e7b1c5fde4b
I've not had chance to test this personally yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
There is a proposed (untested) fix here[1] and paroj has asked reporters
to confirm whether they are using wired or wireless and 360 or other.
[1]: https://github.com/paroj/xpad/issues/27#issuecomment-221434837
--
You received this bug notification because you are a member of Kernel
Packages,
Same problem continues with 4.4.0-22.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1572659
Title:
bcmwl driver does not work with kernel 4.4.0-21 when secure boot
enabled
Status in
Similar errors went away for me after updating to the latest BIOS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574044
Title:
ACPI Error: [\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup
It may be worth mentioning that while that patch fixes the bug, it also
introduces this regression: https://github.com/paroj/xpad/issues/27
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
Just to pile on, ran into the same issue in my CS computer lab. causing
multiple systems to lock up. Thank you for the quick fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566726
This bug report goes back to 2012, it is now 2016 and this bug is STILL
happening in kernel 4.2.0-35??? Pleas fix this, I had this happen when
upgrading kernel in Ubuntu 14.04lts and had to load 15.10 on my external
to even use my computer, still cannot get into by internal drive. I
figured a very
Public bug reported:
The Raspberry-Pi form factor compatible UP board from Aaeon now supports
RealSense depth enabled camera (http://www.up-board.org/kickstarter/up-
intel-realsense-technology/) , and Intel has made a significant
contribution to open source by supporting Robot Operating System
Adding another environment to successful reports for
http://kernel.ubuntu.com/~kamal/lp1548587.3/
Release: 15.10
VMWare Fusion: Professional Version 8.1.0 (3272237)
OSX:10.11.3
uname -a: Linux ubuntu 4.2.0-30-generic #35+lp1548587~kamal3 SMP
This may be the same thing we are seeing on OpenStack compute nodes
since upgrade. Hard crash, no output to logs, local console occasionally
shows a kernel panic ending with Fatal Exception in Interrupt, shutting
down CPU's.
We are seeing this reliably across 10 nodes which have been upgraded,
Dan,
This BUG_ON has been demoted to only trigger when DEBUG_VM is set in
upstream:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=97ee4ba7cbd30f1858f0d16911e042737c53f2ef
I'm looking into why there's a one page difference between the E820
tables and SRAT. You're
I'm running Debian stable (Jessie). How can I install apport on the
stable release?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1532592
Title:
General Protection Fault - kswapd
Public bug reported:
I just rebuilt my home server with new hardware, and installed the
latest Debian 8.2 fresh Friday night. Yesterday, a general protection
fault occurred while I was running mkvmerge. I ran mkvmerge several
times before and after this incident, and was unable to reproduce the
I forgot to mention, memory was tested using memtest86 v6.2.0. No
issues found during two passes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1532592
Title:
General Protection Fault
FYI: My use case for hot plugging my x86 system like a drunken sailor
is to evaluate the amount of CPUs required to complete a given task
before I schedule it to run on other potentially CPU bound machines.
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
[cut bullshit] I am working on Dell E6420. I am using Kubuntu 15.10.
I am using intel pstate driver.
CPU is working ok. I close the lid to suspend OS. After some time I open my lid
to wake OS up and CPU is stuck at lowest frequency, approximately (600Mhz) OS
is unsuable,
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528962/+attachment/4539559/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also experiencing this with 14.04 dell XPS 9350 Intel(R) Core(TM)
i7-5500U
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1488719
Title:
dmesg shows "[drm:gen8_irq_handler [i915]]
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532706/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532701/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532710/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532709/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532700/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Three attempts at installing Wily alongside Trusty 14.04.1.
Steps:
dd /dev/zero bs=16M count=128 to ensure all previous partitions and data are
gone.
Boot from Trusty 14.04.1 USB drive, select erase and
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532711/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532702/+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/1519172
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532708/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532704/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532707/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532703/+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/1519172
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532699/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532705/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1519172/+attachment/4532698/+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/1519172
@ Philip Susi - You are very likely onto something here. I'm running a
2006 MacPro (1,1 & 2,1), which is an outlier in that it has 64bit
processors and a 32bit EFI implementation. efibootmgr doesn't work on
this hardware, I'm guessing because it only works in 64bit mode, but
please, I'd love to be
OK thanks Joseph. We'll run a test against the latest 3.19.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1484919
Title:
Kernel oops associated with BIRD/netlink
Status in linux
It takes us a bit of time to spin up an environment large enough to hit
this, so I'm just trying to figure out how many runs we'll need to pin
this down.
What are your thoughts here? How many kernels are we likely to need to
test, and is there a way for us to get good diagnostics out to look for
Isn't the latest Wily kernel more recent than the
4.2.0-040200rc7-generic #201508162030 we tried above (and didn't
exhibit the problem)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Following-up on #16: Obviously, this is _not_ the solution for everyone,
but for my work computer, system stability is far more important that
USB3. I disabled xhci in UEFI (so ehci is used instead) and have not had
any more non-responsive USB ports in close to two weeks.
--
You received this
Chris Halse Rogers: This issue still exists in Wily (as of Nov 18, 2015
with kernel 4.2.0-18-generic.
Kernel log: http://paste.ubuntu.com/13335527/
Note: I've stripped out UFW lines that are cumbersome to read past.
Line 1109 marks the time that I had to hard reset my computer because
every USB
Ever since we started picking up the 3.13.0-65 kernel in the openstack
CI system on 9/29 we've been seeing lots of random failures across 3
branches (juno/kilo/master) with ebtables, details are in:
https://bugs.launchpad.net/nova/+bug/1501558
An example failure:
I accidentally stumbled upon a sort-of solution to my own problem. It
seems that the Xen hypervisor handles USB the way it should be handled,
so if you happen to have VT-d or SVM, installing Xen is an easy fix.
Plus, you'll be able to run VMs natively, which is itself super cool.
I'm off to play
I have an ASRock Z87 Pro4, and I have this exact problem. The boot times
are the same, cycling the PSU fixes the problem for the first boot, and
disabling the USB ports fixes the problem indefinitely. I'll provide
logs if anybody ever gets around to fixing this.
--
You received this bug
#209 did work when I changed my kernel version to 3.19.8
However, my connection fails after 5-10 minutes, and I have to reboot my
computer to get wifi again.
matt@Swordfish-II ~$ dmesg|grep ath10k
[7.952768] ath10k_pci :05:00.0: enabling device ( - 0002)
[7.953122] ath10k_pci
same as #219, using ubuntu 14.04.2 LTS with kernel 4.1.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/1383184
Title:
Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not
ProcVersionSignature: Ubuntu 3.13.0-55.92-lowlatency 3.13.11-ckt20
Uname: Linux 3.13.0-55-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2107 F pulseaudio
/dev/snd/controlC0: matt
PID ACCESS COMMAND
/dev/snd/controlC2: matt 2107 F pulseaudio
/dev/snd/controlC0: matt 2107 F pulseaudio
/dev/snd/controlC1: matt 2107 F pulseaudio
CurrentDesktop: XFCE
Date: Sat Jun 20 15:55:43 2015
HibernationDevice: RESUME=UUID=80bbb18e-6e1e
Public bug reported:
hi just installed this os to my laptop after having many issues with windows
8.1 and the horrible horrible layout etc!!
I have successfully installed ubuntu 15.04 desktop edition. I am absolutely
delighted with the os and credit to all the team from top to bottom in
-3.13.0-55-lowlatency 3.13.0-55.92
ProcVersionSignature: Ubuntu 3.13.0-55.92-lowlatency 3.13.11-ckt20
Uname: Linux 3.13.0-55-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2107 F
-55-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2107 F pulseaudio
/dev/snd/controlC0: matt 2107 F pulseaudio
/dev/snd/controlC1: matt 2107 F
-image-3.13.0-55-lowlatency 3.13.0-55.92
ProcVersionSignature: Ubuntu 3.13.0-55.92-lowlatency 3.13.11-ckt20
Uname: Linux 3.13.0-55-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt
ACCESS COMMAND
/dev/snd/controlC2: matt 2107 F pulseaudio
/dev/snd/controlC0: matt 2107 F pulseaudio
/dev/snd/controlC1: matt 2107 F pulseaudio
CurrentDesktop: XFCE
Date: Sat Jun 20 15:55:43 2015
HibernationDevice: RESUME=UUID=80bbb18e-6e1e-4e36-a10a
-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2107 F pulseaudio
/dev/snd/controlC0: matt 2107 F pulseaudio
/dev/snd/controlC1: matt 2107 F pulseaudio
CurrentDesktop: XFCE
Date: Sat Jun 20 15:55:43 2015
I too am suffering with a Samsung R40 that usually fails to recover from
suspend, even now in Ubuntu 14.04 LTS. Has anybody managed to figure out
why this happens, and what can be done about it? I've submitted about a
dozen crash reports, but I've no idea who's taking any notice. Ok, it's
an
Bios update solved the issue for me. This pages details how to do so:
http://www.thinkwiki.org/wiki/BIOS_Upgrade#On_Debian_and_Ubuntu
I didn't have much luck with the primary method, however the
genisoimage method worked perfectly for me.
--
You received this bug notification because you are a
hi jsmitch -
you'll need to install the package dkms for the package listed in #13
to install. Normally it's installed when you attempt to update the
proprietary driver module, but if you're on a fresh install and haven't
done that, worry not.
The dkms package is located on the Ubuntu install
It's possible, but for your system to see it as an update it'd have to
be a newer version than the one you've installed.
So if the respository is updated with a refresh of the version that
shipped with 14.04.2, and it does an update, that refresh should contain
the fix (according to the info on
I see on 2014-05-13 it says:
This bug was fixed in the package bcmwl - 6.30.223.141+bdcom-0ubuntu3
Why wasn't the updated package, from 9 months ago, included in 14.04.2's
install? That would have fixed the issue easily.
For anyone having this problem, rather than do code editing and
compiling
That's fine. At least if someone reads the bug, they will see this bug
is probably fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1355044
Title:
[MSI A88XM-E35] Ubuntu 14.04.1
Ubuntu 14.04.2 has been released with kernel 3.16:
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Updated_Packages
I assume that if you tested on 14.04.2, it would work properly and so
this bug will be marked as fixed or wfm or whatever launchpad uses for
this case.
@Bib: It may require
So, I used gparted to format the drive with a single ext4 partition,
rebooted the system, mounted it, and the errors came back.
It's not a hardware issue. It's some combination of the OS, chipset,
file system in use, and maybe (?) drive type. I can use the same drive
on a Gigabyte board that uses
** Attachment added: lshw-short.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+attachment/4296304/+files/lshw-short.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I was able to recreate this same problem on an ASrock Z87E-ITX with an
mSATA SSD and both Ubuntu 12.04.5 and 14.04.1. Same series of errors in
dmesg. I did manage to get a full install done - not sure how - but when
the system boots it's prone to frequent lockups (also, occasionally, at
boot, it
** Attachment added: lsusb.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+attachment/4296306/+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/1318218
** Attachment added: lspci.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+attachment/4296305/+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/1318218
Public bug reported:
The following applies to the 3.13 in trusty.
When transferring data at = around 100Mbps, the IOMMU logs errors such as:
AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x001c
address=0x3000 flags=0x0050]
I have locally cherry-picked 7a9810e7bd99:
apport information
** Tags added: apport-collected trusty
** Description changed:
The following applies to the 3.13 in trusty.
When transferring data at = around 100Mbps, the IOMMU logs errors such as:
AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x001c
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275498/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275503/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275510/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275500/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275499/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275505/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275509/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275506/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: AudioDevicesInUse.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275497/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275507/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275501/+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/139
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275508/+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/139
dmesg files attached via the apport-collect utility. This bug is way up
at 3909 - 3930 seconds in them -- there's a lot of suspend/resume junk
after that.
Upstream discussion is at
http://thread.gmane.org/gmane.linux.kernel/1746901. This patch landed
in 3.16 as commit
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275504/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275502/+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/139
Actually forget that, just worked out they are in the extras package
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1383921
Title:
kipmi0 process hangs with ipmitool
Status in linux
The kernel 3.13.0-41-generic which is in proposed does not appear to
have any of the ipmi modules. Are we doing something wrong ?
root@adam:/lib/modules# uname -r
3.13.0-41-generic
root@adam:/lib/modules# modprobe ipmi_si
modprobe: FATAL: Module ipmi_si not found.
root@adam:/lib/modules#
With the kernel 3.13.0-41-generic, I can confirm that we are now able to
run warm and cold resets of the mc via ipmitool correctly. On previous
kernel those commands would cause kipmi to use 100% cpu time and require
the ipmi modules to be unloaded and reloaded before ipmitool would
operate
Hi,
Did an upstream bug get filed for this? I have the same pc model (HP Compaq
dc7800p) and have always seen the same odd behaviour where the pc must first be
put into hibernate before it will be able to resume from suspend to RAM. I have
seen this behaviour in both Ubuntu and Arch linux
Is there any news on this issue ? we have many nodes in our Openstack
cluster starting to suffer from this problem as we have a puppet fact
which runs ipmitool lan print and so triggers the bug often. Could you
also tell us what the workaround was for RHEL as we can't access the
page on RedHat's
Seems fixed for 14.10 which is expected. This will probably be fixed
automatically with 14.04.2 so the developers probably won't touch this
bug. See the link for more details:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355044/comments/33
--
You received this bug notification because
I'm not really familiar with the ubuntu kernel policy but it appears this bug
will be irrelevant with 14.04.2 because it will contain kernel 3.16. This
appears to be the new kernel policy:
- New ubuntu release gets a new kernel (14.10 for example)
- Wait a few months and push that new kernel to
I'm using an ASUS TP500L laptop running 14.04 with an Elantech touchpad.
Xinput lists it as an ETPS/2 Elantech Touchpad initially and Unity
settings shows me the Touchpad area. However, it is entirely
unresponsive to any form of input. I have tried the fix in #137 and it
changes nothing. I have
NothingMuchHereToSay:
Your comment seems accurate. The original fix was modified again to only
enable bapm on MSI after stability issues were reported. See comment 16
and the 2nd link for more details (it's in the comments of the diff).
--
You received this bug notification because you are a
201 - 300 of 379 matches
Mail list logo
