Public bug reported:
Just upgraded to Ubuntu 24.10 which comes with egl-wayland 1.1.15, now
qmapshack crashes on start:
QSocketNotifier: Can only be used with threads started with QThread
qmapshack: ../src/wayland-eglsurface.c:2562: wlEglDestroySurface: Assertion
`wl_list_empty(&surface->ctx.str
Public bug reported:
The amdgpu driver crashes and shows colored rectangles on the screen -
hangs for a few seconds - and then seems to soft recover, once it
crashed hard with only sysrq to reboot.
With logs like:
[gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32772, for process Xorg pid
132
Might be related? On first attempt in the updater GUI in Ubuntu 23.10
(latest STS stable version), I got
linux-image-nvidia-6.5.0-17-generic: constructing .ko files
./BUILD: 10: make: not found
./BUILD: 11: make: not found
./BUILD: 12: make: not found
./BUILD: 13: make: not found
./BUILD: 14: make
We ran into a similar issue since Ubuntu 22.04.3 moved from linux-6.2.y to
6.5.y for linux-generic-hwe-22.04.
The corresponding dkms package rtl8821ce-dkms-5.5.2.1-0ubuntu11~0.22.04.1
unsurprisingly no longer compiles due to quite a number of kernel API changes.
Btw, we're currently considering
If you want, I can test a specific kernel version for comparision?
--
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/2043561
Title:
rtl8761bu bluetooth dongle bails out or looses device con
I cannot say, as it is as fresh (K)ubuntu installation.
I can only say, that it depends on Linux, no probs with Windows...
--
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/2043561
Title:
r
Public bug reported:
Environment:
Bluetooth dongle connected to integrated Hub -> bluetooth mouse
After a fresh boot into (K)ubuntu, the dongle/mouse works.
Then, after some minutes, the mouse stops working.
Errors:
A) Some times, the bluetooth dongle is gone and I have to re-plug it to make it
I believe with dkms, you need a C compiler and related tools, so that
the nvidia kernel module can be built on your machine during kernel /
driver updates. So that probably means more packages have to be
installed. It might also be a bit more error-prone?
I'm not sure if it could affect secure boo
Another issue with the 6.2.0-25 kernel is in linux-modules-nvidia-525-generic:
Provides: nvidia-dkms-525 (= 525.116.04-0ubuntu0.23.04.1),
nvidia-prebuilt-kernel
But nvidia-driver-525 Depends: nvidia-dkms-525 (>= 525.125.06)
So the "dkms replacement" version provided by the pre-built modules
pack
In lunar / 23.04, there is no linux-objects-nvidia-535-6.2.0-25-generic
package, but the linux-image-6.2.0-25-generic package has been available
for some time. Package upgrades therefore insist on switching to nvidia-
dkms, no matter what I try to do. So I'm still on 6.2.0-24.
Is this just another
I can confirm the issue.
Ubuntu 20.04.6 LTS on DELL PowerEdge R650
-
5.4.0-147-generic -> working
5.15.0-71-generic -> hangs at boot at "Starting Network Name Resolution..."
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Status: Expired => 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/1990156
Title:
Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC
** Also affects: linux-signed-hwe-5.4 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942935
Title:
kernel io hangs d
Hello, same here on Linux Mint 21 based on Ubuntu 22.04
blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0
phys_seg 1 prio class 0
Buffer I/O error on dev sr0, logical block 5, async page read
No CD in the drive, tones of lines at boot or when launching Steam or
Lutris (cer
Uups, wrong tagging. This bug does still affect linux (Ubuntu Focal)
** Also affects: focal (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: focal (Ubuntu)
** No longer affects: focal (Ubuntu Bionic)
** No longer affects: focal (Ubuntu Cosmic)
--
You received this bu
I'm experiencing a similar issue after upgrading from kernel 5.11.0-43
to 5.13.0-30, which in my case seems to be related to the SATA I/O:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-5.13/+bug/1962408
--
You received this bug notification because you are a member of Kernel
Package
The previous kernel 5.11.0-43 boots without any issues, suggesting that
there isn't an actual hardware problem with the drive or the SATA
interface.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://b
** Attachment added: "Second digital photo showing different error messages
during startup"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1962408/+attachment/5564045/+files/kernel_io_bug_2.JPG
--
You received this bug notification because you are a member of Kernel
Pac
Public bug reported:
After upgrading the kernel from kernel 5.11.0-43 to kernel 5.13.0-30 in
Focal, the system stops at different stages of the boot process with
error messages concerning the SATA interface with dev sda (see attached
photos).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
This is caused be mismatch between Kernel and iproute2 version. The kernel v5
offers ipset v7 which causes iproute to not be built with ematch ipset
functionality.
This has been fixed in iproute upstream in - its a one line fix -
Pulling this into iproute2 and rebuilding (After committing it) wo
adding the option "--before no_reset" seems to solve the issue with
kernel 5.11.0-37
esptool --before no_reset --chip esp8266 --port /dev/ttyUSB0 --baud
115200 write_flash 0x firmware.bin
Even if I do not understand the why, this solves the issue for me.
--
You received this bug notificatio
some more information:
- I was able to reproduce the problem on a different computer.
- flashing an ESP32 Devel board which is based on the cp210x instead of the
ch341 works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-
Public bug reported:
the esp8266 development boards like wemos D1 mini have an integrated
usb-uart converter which allows to flash/monitor/debug the esp8266 by
usb cable and a tool called esptool on linux, which is either standalone
(esptool package) or integrated into some IDE (platformio + visi
edentials=/home/florian/.smbcredentials,uid=1000,gid=1000,vers=3.0,noserverino,x-systemd.automount,x-systemd.requires=network-online.target
0 0
Yes, the module cifs is loaded
root@x:/media/FritzBox.NAS# lsmod | sort | grep cifs
cifs 1146880 2
fscache 380928
Public bug reported:
I use "Linux Mint 20.2 x86_64", since the kernel update to version
5.11.0-25, Samba share access no longer works, only when I start my
system with kernel 5.8.0-63 does everything work again.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You r
Thank you for you answer! I updated and will look, if the incident
happens again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu.
https://bugs.launchpad.net/bugs/1924861
Title:
nvidia random crashe
Also happening on 20.04
--
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/1775131
Title:
Ubuntu 18.04 networking issue (connection drops after approx. 15
minutes)
Status in linux package
Follow-up to Comment #36: Although patching upower fixes the issue,
gnome-settings-daemon is still broken, since disabling notifications
won't disable all notifications.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
FYI, here's the corresponding bug in GNOME:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/108
And here's the workaround: https://wrgms.com/disable-mouse-battery-low-
spam-notification/
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #108
https://gitlab
I can confirm that the updated packages fix the issue for me (Groovy on
a ThinkPad T14 w/ Ryzen 7 Pro 4750U). However, the LED on the keyboard
for muting the microphone (on the F4 key) doesn't work for the internal
microphone. It works as expected when another microphone is present and
selected as
Since it is a graphics crash, this is probably relevant, too:
08:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream
Port of PCI Express Switch (rev c5)
09:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL
Downstream Port of PCI Express Switch
0a:00.0 VGA
Public bug reported:
I have had two spontaneous crashes in three days, with this in the
syslog:
Oct 8 09:19:57 alhazen kernel: [ 1532.621173] [ cut here
]
Oct 8 09:19:57 alhazen kernel: [ 1532.621292] WARNING: CPU: 13 PID: 8346 at
drivers/gpu/drm/amd/amdgpu/../display/
Clarification: this bug ist not about wrong battery Level measurements
(Nobody reported that), it's about users being unable to disable
notifications. The notification is shown even when in DND mode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
I bet 500 dollhairs they're being marked as duplicate in two seconds.
--
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/1825636
Title:
Battery drain during sleep. System suspended before ke
Although this kind of bug /may/ seem device dependent, in this instance
it's not.
In this very bug report, the issue hass been confirmed by users of the
following devices:
- Thinkpad L390 (twice)
- Thinkpad X201
- Asus Zenbook UX331UN
- Lenovo X1 Extreme
- Lenovo X1 Extreme Gen2
- Thinkapd X1 C
Hey has the Status been changed from confirmed to incomplete? Ubuntu
-devel is still affected.
** Also affects: linux-signed-hwe (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed-hwe (Ubuntu)
--
You received this bug notification because you are a member of
Is this a native s390x build, or something qemu-user? 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/1886814
Title:
posix_spawn usage in gnu make causes failures on s390x
Status
After running ereything with AMD_DEBUG=nongg, the "Waiting for fences"
seems to be mostly gone, and I now get sdma0 timeouts. So this seems to
be part of the gereral cluster of failures that seem to plague the linux
navi drivers since the beginning.
Jun 22 07:24:43 alhazen kernel: [ 748.740480] [
What happens is that I am doing something and suddenly nothing moves
except the mouse pointer and video calls become audio calls which I can
only leave by switching the computer off. I tend to have obs-studio
25.0.3+dfsg1-2 running. for the last two days I had it running with
AMD_DEBUG=nongg and it
This may or may not be the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875459 but this is
not reliably reproducible, and I don't even have chrome installed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Public bug reported:
un 15 08:30:42 alhazen kernel: [ 1566.155810]
[drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences
timed out!
Jun 15 08:30:47 alhazen kernel: [ 1566.159792]
[drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences
timed out!
Ju
Some background: rechargeable batteries have 1.2V nominal (compared to
1.5V nominal for regular battteries). Any mouse will report levels
around 10%, although the batteries will run for *many* months.
So users of rechargeable batteries will experience notifications about
low levels basically after
Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0
native-path: hidpp_battery_0
model:MX Keys Wireless Keyboard
serial: 408a-9b-b6-52-57
power supply: no
updated: Fr 12 Jun 2020 22:39:07 CEST (8 seconds ago)
has hist
** Changed in: linux (Ubuntu)
Status: New => 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/1881398
Title:
Call trace on insmod
Status in linux package in Ubuntu:
Inval
** Changed in: linux (Ubuntu)
Status: New => 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/1881399
Title:
Kernel trace on loopback
Status in linux package in Ubuntu:
I
Public bug reported:
Sorry for reporting against the wrong package, but launchpad doesn't
behave predictably.
Steps to reproduce:
1. Click "Report a bug" on https://bugs.launchpad.net/bugs/1878899.
2. The "Report a bug" form opens, with "linux" pre-filled as the package.
3. Change the package to
Lauchpad is honestly completly broken.
--
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/1881399
Title:
Kernel trace on loopback
Status in linux package in Ubuntu:
New
Bug description:
Launchpad is broken, I reported this aginst v4l2loopback, not against
linux. I'll try 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/1881398
Title:
Call trace on insmod
Status in
Public bug reported:
Fixed upstream: https://github.com/umlaeute/v4l2loopback/issues/257
Also https://bugs.launchpad.net/bugs/1878899
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, whi
Public bug reported:
Fixed upstream: https://github.com/umlaeute/v4l2loopback/issues/257
See also: https://bugs.launchpad.net/bugs/1878899
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages
Argh, why did Firefox keep the contents of comment #6 in the edit box?
Ignore comment #7, the relevant part is
And I have since retired the AMD A10 system, same behaviour on
[ 6442.968740] CPU: 0 PID: 45180 Comm: v4l_id Tainted: G W OE 5.4.0-33-generic
#37-Ubuntu
[ 6442.968741] Hardware name: Sy
Same, happens on loading the v4l2loopback module:
[ 1039.168432] v4l2loopback driver version 0.12.3 loaded
[ 1039.172977] [ cut here ]
[ 1039.172994] WARNING: CPU: 3 PID: 8520 at
drivers/media/v4l2-core/v4l2-ioctl.c:1064 v4l_querycap+0x8b/0xa0 [videodev]
[ 1039.172995] Mod
Same, happens on loading the v4l2loopback module:
[ 1039.168432] v4l2loopback driver version 0.12.3 loaded
[ 1039.172977] [ cut here ]
[ 1039.172994] WARNING: CPU: 3 PID: 8520 at
drivers/media/v4l2-core/v4l2-ioctl.c:1064 v4l_querycap+0x8b/0xa0 [videodev]
[ 1039.172995] Mod
Bus 008 Device 015: ID 046d:08af Logitech, Inc. QuickCam Easy/Cool
Bus 008 Device 013: ID 046d:0892 Logitech, Inc. OrbiCam
Both used by OBS Studio, which then sent its output to a v4l2loobback
device, module parameters:
/sbin/modprobe v4l2loopback devices=1 video_nr=10 card_label="OBS Cam"
exclus
It's too late now, but there's a typo in the changelog: "shitfs".
--
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/1876645
Title:
Unable to handle kernel pointer dereference in virtual ker
Public bug reported:
[92420.303133] [ cut here ]
[92420.303141] WARNING: CPU: 2 PID: 259541 at
drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev]
[92420.303141] Modules linked in: btrfs xor zstd_compress raid6_pq ufs qnx4
hfsplus hfs minix ntfs ms
Same here +1
--
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/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status in Linux:
New
Status in linux package in Ubuntu:
Public bug reported:
The Intel 8265 / 8275 Wireless in my Lenovo ThinkPad X1 Yoga (Gen 3)
keeps constantly crashing with
Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Creating peer entry for
1c:23:2c:6e:90:09
Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Dialog Token in TPK M1 1
Same behavior here. Middle Mouse Button (button2) not working, starting
xev | grep button
try it multiple times; button event occurs; stop xev and the button
keeps working.\
Environment:
KDE Neon (based on Ubuntu 18.04) with mainline kernel verion
5.1.2-050102-generic
Hardware:
Logitech USB-PS
If someone else has those issues with a USB-C Dock (Thunderbolt 3) I got rid of
the issue by using the latest mainline Kernel:
5.1.0-050100-generic #201905052130 SMP Mon May 6 01:32:59 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
and the following Kernel config settings (/etc/default/grub):
GRUB_CMD
Since I'm also facing this bug I just want to confirm that the error
also occurs on the latest mainline Kernel (5.1) and also on the current
drm-tip kernel version (5.1.0.0994 from https://kernel.ubuntu.com
/~kernel-ppa/mainline/drm-tip/2019-05-05/)
I'm trying to use an additional monitor on my X3
Same bug here on two different laptop.
Fresh install Ubuntu 18.04.2
nvidia-driver-418
4.18.0-18-generic
First $vulkaninfo => OK
Switch on Intel with NVIDIA X Server settings
reboot
Switch to NVIDIA with NVIDIA X Server settings
reboot
$vulkaninfo => VK_ERROR_INITIALIZATION_FAILED
$sudo vulkaninfo
=="add", ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2300 F pulseaudio
Date: Fri Nov 9 14:03:15 2018
ErrorMessage: Paket linux-image-extra-4.4.0-38-generic ist nicht bereit zur
Konfiguration kann nicht konfiguriert werden (momentaner Status
»half-installed
I can also confirm that this problem still exists with a fresh install
of Ubuntu 18.10 with kernel 4.18.0.. I will try the
psmouse.synaptics_intertouch=0 workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23202
There are three issues here: The kernel implementation in 4.17 was
buggy: pkey_set and pkey_get weren't implement in glibc, and the misc
/tst-pkeys has some incorrect test expectations.
** Bug watch added: Sourceware.org Bugzilla
Eric, I believe your mirror is lagging behind ab it?
I just installed 4.15.0-24-generic from -proposed and it fixes the issue for me
(tested 2 suspend cycles – previously it would fail 100% of the time).
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You
Confirming this is still an issue for me after updating my bionic
installation to linux-image-4.15.0-23-generic 4.15.0-23.25, while
https://people.canonical.com/~khfeng/lp1752772-r8169-intx/ worked fine
in recent weeks.
--
You received this bug notification because you are a member of Kernel
Pack
I'm pretty sure this is a duplicate of #1752772 , right? Like Kai-Heng
Feng mentioned above. If so, please mark as duplicate.
--
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/1759644
Title:
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/:
works: v4.17-rc1, v4.17-rc3, v4.17-rc4 (-rc2 not tested, but I assume it
works)
fails: v4.16.7
build for 4.16.8 failed, so I was unable to test that one.
--
You received this bug notification because you are a member of Kernel
Packages, wh
I forgot this yesterday: I accidentally compiled git master HEAD of that
repo first. It worked fine, so something fixed this bug between v4.16.5
and 46dc111dfe47. If required I can try to bisect, but it will take a
while, my CPU is almost 10 years old (takes 1+ hour to compile the
kernel). I guess
I cloned git://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-crack and checked out tag
v4.16.5, applied the 6 patches listed at the top of
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.5/ and the one debug
patch at https://lkml.org/lkml/2018/4/3/136.
journalctl be
Related/Duplicate(?):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772
--
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/1760073
Title:
No network from suspend resume
Status in
I have added a link to the upstream kernel.org bugzilla, I believe it's
the same bug.
** Bug watch added: Linux Kernel Bug Tracker #198973
https://bugzilla.kernel.org/show_bug.cgi?id=198973
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=198973
Importance: Unknown
Since updating to bionic, I notice the same symptoms (network not
working after suspend).
I'm adding this comment to note that this makes my network come up again, I'll
try to add this as a post-suspend script as described above:
$ sudo modprobe -r r8169
$ sudo modprobe r8169
(Suggested in https:
Just as a comment, at least in my case this was fixed by the
"uvcdynctrl" package which installs suitable udev rules to initialize
the missing controls from userspace.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Public bug reported:
When trying to boot into 3.19.0-25, the screen either remains purple or
displays the disk unlock dialog scaled by about a factor of two and in
an inoperable state. The only thing that works is Ctrl-Alt-Del and than
select 3.19.0-22 from the grub menu
ProblemType: Bug
DistroRe
0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2980 F pulseaudio
/dev/snd/pcmC1D0c: florian2980 F...m pulseaudio
/dev/snd/pcmC1D0p: florian2980 F...m pulseaudio
/dev/snd/controlC1: florian2980 F..
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2980 F pulseaudio
/dev/snd/pcmC1D0c: florian2980 F...m pulseaudio
/dev/snd/pcmC1D0p: florian2980 F...m pulseaudio
/dev/snd/controlC1: florian2980 F pulseaudio
Date: Tue May 9 11:27:40 2017
Hi
ge-4.4.0-77-generic 4.4.0-77.98
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2980 F pulseaudio
/de
9
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2980 F pulseaudio
/dev/snd/pcmC1D0c: florian2980 F...m pulseaudio
/dev/snd/pcmC1D0p: florian2980
nux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2980 F pulseaudio
/dev/snd/pcmC1D0c: florian2980 F...m pulseaudio
/dev/snd/pcmC1D0p: florian2980 F...m pu
.04
Package: linux-image-4.4.0-77-generic 4.4.0-77.98
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2
Package: linux-image-4.4.0-77-generic 4.4.0-77.98
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2980 F.
dioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian2980 F pulseaudio
/dev/snd/pcmC1D0c: florian2980 F...m pulseaudio
/dev/snd/pcmC1D0p: florian2980 F...m pulseaudio
/dev/snd/controlC1: florian2980 F pulseaudio
Date: Tue May 9 11:27:40 2017
Hi
Unfortunately I must say I've moved on from using both Ubuntu and the
affected card within the last 10 years. Maybe one of the several other
affected people can provide some feedback.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-li
Seeing exactly the same behavior as described in comment #71, happy to
test any change
--
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/1590590
Title:
Touchpad not recognized on Dell Latit
Yes! By also setting the `device_tree_end`, I'm getting the correct MAC
address now, too. Thanks again @mbirth!
--
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/1652504
Title:
Recent updat
Same for me. Using Ubuntu 16.04.1 LTS on a RasPi3.
Adding the line
fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb
to /usr/share/flash-kernel/bootscript/bootscr.rpi3 helped me, too. Thanks
@mbirth!
Also, I have the same issue with the MAC address. I'm currently using
macchanger to set it
Thanks Joseph!
I now believe I'm seeing two different issues in 4.8 that are not in 4.4 and
slow down my boot, which is very confusing.
- #1: High number of kworkers (fixed in 4.8 using the two patches and bisected
by Doug Smythies already)
- #2: Unknown other issue. I've noticed that when compi
My boot time comparison: (Wall clock time from GRUB to lightdm ready for login)
4.4: 12.28s
4.8.0-26 + Patches (Joseph's kernel): 21.78s
4.8.0-22 (Yakkety): 25.06s
This is with NetworkManager-wait-online.service enabled, which seems to
take ~8s in my case.
The attached file has systemd-analyze (b
Thanks Joseph! I'm seeing the same effect described by Martin.
Boot+lightdm+loading Unity 7 is not as fast as it used to be in 16.04.
I need to compare timings (4.8 patched vs 4.8 vs 4.4) tomorrow to make
sure, but I also feel like it's a little faster now with the patches
applied.
The number of
Well, I guess the other patch is required as well for SLUB (not only SLAB as I
assumed at first):
https://patchwork.kernel.org/patch/9361853/
--
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
My problem is probably the same that Doug Smythies described in bug
1626564 . I used the "echo workqueue:workqueue_queue_work >
/sys/kernel/debug/tracing/set_event" method and had about 1000 work
items enqueued by "memcg_kmem_cache_create_func" all at pretty much the
same time, which correlates nic
This is what I get right after boot and login into Unity 7 (executed in Gnome
Terminal):
$ ps aux | grep kworker | wc -l
1004
Kernel is 4.8.0-22-generic. After a few minutes, only 21 kworkers remain. Load
after 4 minutes is not excessive (1244 sleeping processes), forgot to check
load right aft
Same here, downgrading to 4.4 from Xenial improved the situation (boot
still feels a little slower than Xenial though, maybe because of the
NetworkManager bug). I use a 7 years old desktop computer based on a
Gigabyte motherboard and AMD Phenom II X4 955 CPU, So it's not Thinkpad-
related.
(From G
/dev/snd/controlC0: florian1631 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=eca37581-7b02-477e-8847-5d1fe024f793
InstallationDate: Installed on 2016-03-11 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus"
cur with kernel 3.19, but the black screen of external
monitor problem still happens.
---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian1631 F pulseaudio
CurrentDesktop: Unity
DistroRelease
nchpad.net/bugs/1553659
Title:
Ubuntu 15.10 freezes with linux Kernel 4.2 (with intel chipset)
Status in linux package in Ubuntu:
Incomplete
Bug description:
I started with a brand new pc with a fresh install of ubuntu 14.04. But
graphics were poor :
florian@florian-W9x0LU:~$ lspci | gre
ntu.
https://bugs.launchpad.net/bugs/1553659
Title:
Ubuntu 15.10 freezes with linux Kernel 4.2 (with intel chipset)
Status in linux package in Ubuntu:
Incomplete
Bug description:
I started with a brand new pc with a fresh install of ubuntu 14.04. But
graphics were poor :
florian@florian-W9x0LU:~$ lspci
1 - 100 of 200 matches
Mail list logo
