-0ubuntu2
$ dpkg -S /usr/include/x86_64-linux-gnu/asm/fcntl.h
linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug
-linux-gnu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-pa
Yes, sorry. I just hit send on the bug report tool without noticing /boot
was full.
On Thu, May 10, 2018, 10:11 AM Joseph Salisbury, <
joseph.salisb...@canonical.com> wrote:
> You may need to run the following from a terminal:
>
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770178/+attachment/5136746/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I came in this morning, and the bug reporter tool was complaining about
this.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-124-generic 4.4.0-124.148
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic
Public bug reported:
Online Norton Help and Support by PC Planet
PCPlanet's Certified Technicians can help you scan, detect, and remove all
types of viruses and malware in your computer. Our techies have years of
experience and the expertise in providing support for antivirus and fixing
Public bug reported:
Previous
- IOMMU was enabled under Ubuntu 16.04 LTS Kernel 4.4 - No Issues
Current
- After upgrading to 18.04 with kernel 4.15 systems crashes with IOMMU enabled
- Disabling IOMMU within the BIOS allow booting with 4.15 kernel
- Enabling IOMMU and switching to 4.4
I've just rebooted five times without any lock ups.
I'll leave it running, and see what happens.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
Hard lockup during boot
@tyhicks, I don't have an Artful test system, but I confirmed on Xenial
(4.4.0-116-generic) that `apparmor=0` is a workaround, without the
`noibpb` option and with intel-microcode version
3.20180312.0~ubuntu16.04.1.
--
You received this bug notification because you are a member of Kernel
Still not working on 4.16.0-rc6. Is there actually development going on
concering this 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/1728244
Title:
Touchpad stops working after
I'm afraid that 4.4.0-117-generic #141 - Ubuntu SMP Tue Mar 13 11:58:07
doesn't cure the problem for me. I still get the Watchdog Hard Lockups.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
That one, 47a0... , failed.
Unfortunately, that is the last one that I can test for you until next
week, as I have to go away for a few days.
I hope that someone else can help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Linux golf 4.4.0-110-generic #133~lp1745349Commit49bb7a3cbf5 SMP Tue Mar
6 16:37:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux doesn't seem to have
the problem,.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
That one (e233e...) failed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-112-generic
Status in linux package in Ubuntu:
That one, Linux golf 4.4.0-110-generic
#133~lp1745349Commit7de295e2a47849 SMP Tue Mar 6 13:00:57 UTC 20 x86_64
x86_64 x86_64 GNU/Linux doesn't appear to have the problem.
It has been running for a lot longer than it usually does.
--
You received this bug notification because you are a member of
I'm definitely running from your 110 kernel, and it exhibits the
Watchdog Hard Lockup problem, when running without noipbp.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
uname -a shows:-
Linux golf 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
so I obviously haven't implemented your kernel correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I hope this is helpful additional data. I run Ubuntu 16.04 on a Dell XPS
15 9560. I've been using a bluetooth mouse almost daily for over a month
with no problems. I left the computer on, but didn't use it for several
days. I then closed the lid (causing a suspend state), later opened the
lid to a
I'm afraid that I am not an expert at Ubuntu. I think that I have
installed your test kernel correctly, but I don't know how to prove it.
I used sudo dpkg -i *.deb .
If I have installed it correctly, then it doesn't cure the problem. It
runs fine with noibpb, but fails in the same way if I try to
asm/fcntl.h
linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+subscriptions
--
Mailing list: ht
Does not work on 4.16.0-041600rc1-lowlatency on my YEPO 737S. I never
had it working a bit, whichever kernel i booted. `dmesg` output is
attached.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5062564/+files/dmesg.txt
--
You
Correction - 4.4.0-116-generic does not solve the problem.
The server was up for over an hour before hanging. As it doesn't usually
have a console, I can't be certain of the cause of the hang. However, a
subsequent reboot, with a console, involving rebuilding a 10TB RAID 5
array, showed exactly
4.4.0-116-generic does appear to solve the problem on my Asus Prime
Z270K.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745349
Title:
Hard lockup during boot with
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743041
Title:
Updating Lubuntu on netbook corrupts
I've just tested 4.15-rc9 generic from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.15-rc9/. It works 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/1743041
Title:
Updating
I tested the latest upstream kernel (v4.15-rc8) and the bug still
exists.
** Tags removed: bot-comment
** 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
OK, I'll do that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743041
Title:
Updating Lubuntu on netbook corrupts screen
Status in linux package in Ubuntu:
Incomplete
Bug
@tomreyn
My corrent config to get stability
C6 disabled in BIOS
ALSR disabled
kernel >= 4.14.4 with CONFIG_RCU_NOCB_CPU
rcu_nocbs=0-15 processor.max_cstate=1 in GRUB_CMDLINE_LINUX
I got lockups still with ASLR disabled and rcu_nocbs with the custom
built kernel, once I added C6 disabled in bios
Can't run apport-collect as bug renders system inoperable.
** 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/1743041
CurrentDesktop: KDE
Date: Wed Jan 10 18:18:52 2018
InstallationDate: Installed on 2012-01-06 (2196 days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
IwConfig:
lono wireless extensions.
mike no wireless extensions.
IwConfig:
lono wireless extensions.
mike no wireless extensions.
docker0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic
root=/dev/mapper/VastDesk-RootOS ro
01-06 (2196 days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
IwConfig:
lo no wireless extensions.
mike no wireless extensions.
docker0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
ProcFB:
CurrentDesktop: KDE
Date: Wed Jan 10 18:18:52 2018
InstallationDate: Installed on 2012-01-06 (2196 days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
IwConfig:
lono wireless extensions.
mike no wireless extensions.
docker0 n
(20111011)
IwConfig:
lono wireless extensions.
mike no wireless extensions.
docker0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic
root=/dev/mapper/VastDesk-RootOS r
days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
IwConfig:
lono wireless extensions.
mike no wireless extensions.
docker0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
ProcFB: 0 VESA VGA
ProcKer
Workaround:
grep -q 'LLMNR=no' /etc/systemd/resolved.conf || \
echo 'LLMNR=no' | sudo tee -a /etc/systemd/resolved.conf
sudo service systemd-networkd restart
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Interesting; the first thing I tried when triaging this was to edit
/etc/nsswitch.conf as follows:
# hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts: files dns
... to eliminate the possibility that it was multicast DNS causing the
slowdown. But it appears I'm
Just to be clear my mainline kernel is configured with
CONFIG_RCU_NOCB_CPU to yes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected
Well I've now hit 3 weeks of uptime with C6 disabled in the BIOS and
GRUB_CMDLINE_LINUX_DEFAULT="rcu_nocbs=0-15 processor.max_cstate=1"
and 4.14.6 built from the mainline kernel repo. At this point I'm
satisfied that for me at least my Ryzen is now stable.
--
You received this bug notification
I can confirm that #294 works on a Lenovo G50-80.
However I did have some hiccups. Basically the I did the 4 steps, but the first
time did not work.
It didn't update the boot entries, neither installed the new kernel.
What I did was to boot in the oldest kernel that I had installed: Linux
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
(compared to Xenial)
Status in
** Description changed:
When testing MAAS on Bionic, we noticed sluggish performance that we
could not immediately explain.
After comparing the results from a run of the test suite on Xenial to a
run on Bionic, we determined that the slowdowns had to do with DNS
lookups. In
I just tested with the Xenial kernel and Bionic userspace and observed
that the bug still occurs, so marked Invalid for 'linux'.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
Note: I doubt this bug is in the kernel itself; I initially attempted to
file it under glibc at first, but for some reason the `linux` package
was selected.
I also added `systemd` in case the difference in behavior can be
explained by the addition of resolved.
Note that these tests were run on
Public bug reported:
When testing MAAS on Bionic, we noticed sluggish performance that we
could not immediately explain.
After comparing the results from a run of the test suite on Xenial to a
run on Bionic, we determined that the slowdowns had to do with DNS
lookups. In particular, if MAAS
nu/asm/fcntl.h
# Package: linux-libc-dev
# Version: 4.13.0-19.22
Regards, Mike
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-pa
well another lock up. I've now disabled C6 in the bios and added
max_cstates=1 to the boot parameters
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X freeze -
Well another watchdog failure with 4.14.5
I also updated to AGESA 1.0.0.6B when I rebooted to 4.14.5.
Just building a 4.14.6 to try again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
After 5 days uptime with my custom ubuntu kernel build I got a different
crash with a reboot vs the watchdog error. I'm now running a mainline
kernel 4.14.3 with ASLR disabled and rcu_nocbs=0-15 and have restarted
my no crash counter.
--
You received this bug notification because you are a
Public bug reported:
Intel NUC's from Axiomtek with Intel Corporation Wireless 7260 (rev bb)
chipsets. We have this running on almost 200 of these devices.
Ubuntu 16.04.3 as well as Ubuntu 14.04.5
"loaded firmware version 17.608620.0 op_mode iwlmvm"
linux-firmware trusty: 1.127.24
Well I've hit 48 hours uptime since booting to my custom build kernel
(Linux ganymede 4.13.0-17-generic #20+ryzen SMP Sun Dec 3 20:18:51 MST
2017 x86_64 x86_64 x86_64 GNU/Linux) with rcu_nocbs=0-15 in my boot
command and disabled ASLR. That's about double my previous uptime
record, I'll report
Yep I did :) 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/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Status in Linux:
Unknown
Status in
Cool Thanks for the confirmation Franck I've rebuilt 4.13.0-17 with
instructions from here https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
(Probably similarly to Mario). I'm going to test it with this first
(since don't really want to reboot again). But might get stuff ready
with a 4.14.3
@franckc did you have to rebuild your kernel? I tried the kernel
options without that and still had failures. I've just rebuilt with
CONFIG_RCU_NOCB_CPU to see if now the rcu_nocbs=0-15 resolves my lockups
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
System froze and needed to be power-cycled.
ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might
i'm using the fix from git hub on 16.04 all up to date.
https://github.com/pvaret/rtl8192cu-fixes
Tried and work on kernels 4.4 , 4.8 and 4.11 .
I haven't tested it on 4.9 and 4.14
It's ALREADY fixed, some one just needs to review it's not malware and
then do a copy paste -_-
Why it's not
** Description changed:
+ EDIT: Some one fixed it in github, still works in at least in linux 4.4-4.11
+ https://github.com/pvaret/rtl8192cu-fixes
+ EDIT:
+
I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan.
The adapter works fine under Windows and I have no problems
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Summary changed:
- Slow speed and dropped connections with Realtek RTL8192CU-based wifi
+ [patch included]Slow speed and dropped connections with Realtek
RTL8192CU-based wifi
--
You received this bug notification because you
Public bug reported:
I've had this happen twice on kernel upgrades, most recently when linux-
image-extra-4.4.0-95-generic failed to download due to an iffy
connection. Because linux-image-4.4.0-95-generic did successfully
download, its setup (run-parts: executing /etc/kernel/postinst.d/zz-
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948119/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948115/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948120/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I used this command in a terminal as directed:
apport-collect 1716304
and now the post seems to be corrupted.
This is a new install so I have no prior history with the problem. And,
I am not able to test a different kernel on that computer.
Mike
On 09/11/2017 07:14 AM, Joseph Salisbury wrote
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948121/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948111/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948109/+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/1716438
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948117/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948113/+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/1716438
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948118/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948112/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948114/+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/1716438
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1716438/+attachment/4948116/+files/ProcCpuinfoMinimal.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/1716438/+attachment/4948110/+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
** Tags added: apport-collected
** Description changed:
I've had this happen twice on kernel upgrades, most recently when linux-
image-extra-4.4.0-95-generic failed to download due to an iffy
connection. Because linux-image-4.4.0-95-generic did successfully
download,
/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
SS COMMAND
/dev/snd/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Rele
/dev/snd/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(
/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
/dev/snd/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(
/dev/snd/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(
PID ACCESS COMMAND
/dev/snd/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Rele
/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: mike 1919 F pulseaudio
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
+ InstallationDate: Installed on 2017-08-10 (32 days ago
ND
/dev/snd/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(
ND
/dev/snd/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Rele
/controlC0: mike 1919 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=b0812cb2-ade6-42dc-8db3-1fdb1305c3bf
InstallationDate: Installed on 2017-08-10 (32 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Public bug reported:
I've had this happen twice on kernel upgrades, most recently when linux-
image-extra-4.4.0-95-generic failed to download due to an iffy
connection. Because linux-image-4.4.0-95-generic did successfully
download, its setup (run-parts: executing /etc/kernel/postinst.d/zz-
Public bug reported:
With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP,
and GDMSESSION are set to Lubuntu. A more appropriate and useful value
would be LXDE. This is not a problem with Lubuntu-Openbox.
Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE
(Openbox
Looks to me like the patch is in Ubuntu kernel.
http://kernel.ubuntu.com/git/kernel-
ppa/mirror/linux.git/tree/drivers/mfd/intel-lpss-pci.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http://kernel.ubuntu.com/git/kernel-
ppa/mirror/linux.git/tree/drivers/mfd/intel-lpss-pci.c
Looks like the source is now 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/1710392
The title of the email might be better to include the directory path to
the file, and a brief description.
Use the body of the email to mention Lenovo.
I assume you already got that feedback...
--
You received this bug notification because you are a member of Kernel
Packages, which is
Please do use my email or name, etc.
B
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1700657
Title:
Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
Status in Linux:
I changed it to confirmed, although I am the reporter.
I found the patch is missing in the ubuntu kernel source:
https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git
/mainline-crack/tree/drivers/mfd/intel-lpss-pci.c
--
You received this bug notification because you are a
The bug exists upstream in 4.13-rc4
** 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.
Sorry, to answer the first question, the latest kernels do boot on the
machine, the trackpad isn't recognized and doesn't respond to anything
at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
No.
The laptop is a 2017 model. The source file in question simply doesn't
have an array element that describes/identifies the trackpad. My
assumption is that the driver maintainer simply hasn't seen a device
with this ID before.
I would be happy to test the latest kernel, but I don;'t see the
I searched the WWW for any kind of solution to the trackpad not being
recognized. There are several months of similar questions, but no
resolution. Until this patch was made public/known.
Further discussion here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700657
--
You received
Public bug reported:
There's just a 1 line patch required, to add an initializer to array of
structs scanned to match up the device ID with driver.
The PR is here:
https://github.com/torvalds/linux/pull/444#discussion_r131229815
I've applied the patch and created and booted from a custom
@kaihengfeng
Can you please assure this gets in the queue to get merged into master?
The file in question hasn't been changed since early July, so not
merged. It would be awesome to not have to build custom kernels all the
time the kernel needs to be updated.
--
You received this bug
@CoolStar nothing to do.
https://github.com/torvalds/linux/pull/444
@Hoeze made the PR already.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1700657
Title:
Touchpad not detected in
401 - 500 of 1096 matches
Mail list logo
