As per the last comment by Emanuele Cisbani (cisba), I re-installed
4.10.0-37 (the original source of video problems with synaptic.
Then did: sudo apt install --reinstall i915-4.11.6-4.10.0-dkms
And the problem is now fixed. :-)
I also ran the intel Graphics Update which didn't perform any actua
That's awesome sir, thank you for your diligence.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
Status in linux package in Ubun
Public bug reported:
I'm on an Acer Espire with intel microcode running dual boot Xorg 17.10
using Gnome. I'd say it's usually 50/50 that i'm able to suspend and
successfully resume. Same goes for shutting down now, where it will
freeze on the purple Ubuntu screen. When I suspend, the monitor will
apport information
** Tags added: apport-collected
** Description changed:
I'm on an Acer Espire with intel microcode running dual boot Xorg 17.10
using Gnome. I'd say it's usually 50/50 that i'm able to suspend and
successfully resume. Same goes for shutting down now, where it will
free
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1740175/+attachment/5027698/+files/ProcCpuinfoMinimal.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of K
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
** Description changed:
I'm on an Acer Espire with intel microcode running dual boot Xorg 17.10
using Gnome. I'd say it's usually 50/50 that i'm able to suspend and
successfully r
Upgraded to v4.15 kernel; used systemctl suspend today and couldn't
resume ~ the screen and hard drive "suspended", but the hard drive was
still running (with my laptop, a blue light indicates the hard drive is
on).
--
You received this bug notification because you are a member of Kernel
Packages
One observation that i've made: upon powering on, if I attempt to
suspend after little to no activity, ie: quickly going through Chromium,
the system is almost always able to suspend and resume thereafter.
During periods when i'm doing projects that last a couple hours using
Sublime Text, CLion, or
So, 'echo freeze | sudo tee /sys/power/state' seems to work quite
smoothly. Is there any reason NOT to use this from here on out instead
of 'systemctl suspend'. Could quite well solve my issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I did a number of the steps in the link provided for debugging to the
best of my ability (i'm pretty new). Last night I had an issue with
shutdown: after running a stop job on mysql community server the system
froze on 'reboot: Power down'. I just properly turned off the i915
driver and updated gru
I was able to fix the stop job on shut down, but I froze again on
'reboot: Power down' - it looks like the hard drive is turning off but
the screen stays on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
How about now?
CONFIG_IPV6_OPTIMISTIC_DAD is no longer experimental either.
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/4479
Public bug reported:
Feature request: Please enable CONFIG_IPV6_OPTIMISTIC_DAD.
config IPV6_OPTIMISTIC_DAD
bool "IPv6: Enable RFC 4429 Optimistic DAD"
---help---
This is experimental support for optimistic Duplicate
Address Detection. It allows for autoconfigured addresses
to be used
For posterity:
CONFIG_IPV6_ROUTER_PREF appears to be enabled in recent versions.
CONFIG_IPV6_OPTIMISTIC_DAD is bug #1728366.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/447905
Title:
Dan,
It appears that the requests that are being submitted refer to DMA
addresses that exceed the guest physical memory range, and this is why
the requests are being failed. The address seen is outside the E820 map:
[ 0.00] e820: BIOS-provided physical RAM map:
[ 0.00] BIOS-e820: [mem 0x0
Yes, ballooning has been a constant source of problems which is why it
is disabled in Amazon Linux AMI.
We do not currently support DMA to/from guest physical addresses outside
of the E820 map for ENA networking or NVMe storage interfaces. This
effectively means that ballooning needs to be disable
I imagine CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is set for the Ubuntu
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/1668129
Title:
Amazon I3 Instance Buffer I/O error on dev nvme0n1
Wanted to chime-in and say I experience the same thing. Issue doesn't
persist in Ubuntu Gnome flavor on the same hardware.
Did notice some earlier posters mentioned dropbox, have noticed the
latest version will consistently chew up available memory the longer the
machine is on.
--
You received t
I've had this issue on 4 different instances in us-west-2 -- two I still
have running -- can I help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1668129
Title:
Amazon I3 Instance Buff
I don't know that I do -- I'm finding these errors when rsync'ing a
larger database from another machine.
I'm using ubuntu/images/hvm-ssd/ubuntu-
xenial-16.04-amd64-server-20170221 (ami-a58d0dc5)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
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 cod
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
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, ev
** 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.
https://bugs.launchpad.net/bugs/152
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
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
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:
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
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
Stat
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 right
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,
and
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.
https://bugs.launchpad.
Public bug reported:
My touchpad only responds about 10% of the time I use it. It's extremely
intermittent and unreliable. I use a Lenovo Thinkpad T530 with Ubuntu
14.04, kernel version 3.13.0-29. This problem has persisted since the
previous version of Ubuntu, although I didn't make a note of wha
I have display problems with a Dell Vostro 1000 (2.4.1 BIOS, similar
hardware to Inspiron 1501) on Lubuntu 14.04. Vertical lines on boot,
whether with LiveCD (USB stick) or installed on hard drive. No
herringbones or purple screens.
Observations:
1. Nomodeset works (albeit stuck in 1024 x 768) b
Please note the above fix requires kernel 3.13.9 afaik available at
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.9-trusty/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1239578
Ti
Strangely enough, it was my power adapter causing the problem. I don't
know exactly how, but when I unplug it, all is well. Lesson learned:
don't by the cheapest power adapter on Amazon.com :)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificatio
spend and prevented it from
resuming properly.
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: matt 1752 F pulseaudio
/dev/snd/controlC1: matt 1752 F pulseaudio
Date: Tue Apr 1 12:09:35 2014
Executabl
We just experienced the same problem on wolfe-01 today. We were
deploying charms with juju and noticed that juju status did not return
the right output.
The kernel that was running is:
Linux wolfe-01 3.13.0-21-generic #43-Ubuntu SMP Mon Mar 31 22:54:04 UTC
2014 ppc64le ppc64le ppc64le GNU/Linux
** Attachment added: "The /var/log/syslog file from wolfe-01."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4064026/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
otation: Your system might become unstable now and might need to be
restarted.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gdm1394 F pulseaudio
matt
ACCESS COMMAND
/dev/snd/controlC1: gdm1394 F pulseaudio
matt 1868 F pulseaudio
/dev/snd/controlC0: gdm1394 F pulseaudio
matt 1868 F pulseaudio
CurrentDmesg: [ 26.157166] FAT-fs (sdb1): Volume was not properly
Boris, all:
We did a test with disabling the SRAT entirely, but the balloon messages
persisted.
ami-af8d9ac6 (ubuntu/images-milestone/hvm/ubuntu-
trusty-14.04-beta2-amd64-server-20140326)
$ dmesg | grep -i 'srat\|node\|numa\|balloon' |grep -iv inode
[0.00] No NUMA configuration found
[
Not precisely. What toolstack are you using? I can try to reproduce
outside of our control plane with a config file that would work on your
toolstack.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
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 pac
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# ipmito
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 correct
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: r816
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
address=0x
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.
https://bugs.launchpad.net/bugs/
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.
https://bugs.launchpad.net/b
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.
https://bugs.launchpad.net/bug
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.
https://bugs.launchpad.net/bugs/13
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.
https://bugs.launchpad.net
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.
https://bugs.launchpad
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.
https://bugs.launchpad.net/bugs/1399
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.
https://bugs.launchpad.net/b
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.
https://bugs.lau
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.
https://bugs.launchpad.net/bugs/
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 7a9810e7bd99c922d9cedf64dba
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.
https://bugs.launchpad.net/b
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
Hi Stefan,
I looked at this a long time back (circa 2011), and things may have
changed since then. See:
https://forums.aws.amazon.com/thread.jspa?threadID=59753
When I looked at this last, we weren't emulating TSC and the CPUID flags
that advertise invariant TSC came through. This was making the
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 si
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 (every
What's the current status of this bug? I have the Folio 1040 and can't
turn on wireless.
$ uname -r
3.13.0-32-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1303420
Title:
Wire
Still an issue in 14.04/Trusty with Lenovo Yoga 2 Pro.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/363583
Title:
webcam still powered on after closing cheese
Status in One Hundred Pa
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
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 20
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 m
_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 pulseaudio
CurrentDesktop: XFCE
Date:
vicesInUse:
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
HibernationDevice: RESUM
roRelease: Ubuntu 14.04
Package: linux-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 ACC
ency 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 2107 F pulseaudio
04
Package: linux-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/cont
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
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 cl
** 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
** 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.
https://bugs.launchpad.net/bu
** 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
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
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, wh
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 linux-lts-u
@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]:
https://gi
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&id=4efc6939a83c54fb3417541be48991afd0290ba3
--
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
Architecture:
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 lin
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.
https://bugs.
Public bug reported:
I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to
4.4.0-43 and rebooting the system didn't seem to recognize my Wifi or
sound hardware: there was no Wifi icon or ability to connect to a
network, and the only output on the sound menu was "Dummy Output."
Reboot
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+ USER PID ACCESS COMMAND
+ /dev/snd/controlC0: matt 3400 F pulseaudio
+ /dev/snd/controlC1: matt 3400 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+
PID ACCESS COMMAND
/dev/snd/controlC0: matt 3400 F pulseaudio
/dev/snd/controlC1: matt 3400 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423
InstallationDate: Install
dware:
there was no Wifi icon or ability to connect to a network, and the only output
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAN
:
there was no Wifi icon or ability to connect to a network, and the only output
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/s
COMMAND
/dev/snd/controlC0: matt 3400 F pulseaudio
/dev/snd/controlC1: matt 3400 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423
InstallationDate: Install
PID ACCESS COMMAND
/dev/snd/controlC0: matt 3400 F pulseaudio
/dev/snd/controlC1: matt 3400 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423
InstallationDate: Install
und hardware:
there was no Wifi icon or ability to connect to a network, and the only output
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAN
hardware:
there was no Wifi icon or ability to connect to a network, and the only output
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAN
dware:
there was no Wifi icon or ability to connect to a network, and the only output
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAN
201 - 300 of 389 matches
Mail list logo
