Thanks for looking so quickly. I'm almost certain the problem will go
away without the nvidia driver because the nouveau driver didn't
recognise the hardware when I booted off the USB installer, so reverse
prime won't work and there will be no external monitor, which is a
completely new problem.
/snd/controlC0: rocko 1978 F pulseaudio
/dev/snd/controlC1: rocko 1978 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 20 09:20:33 2021
InstallationDate: Installed on 2021-09-15 (5 days ago)
InstallationMedia: Ubuntu 21.10 "Impish
Just to confirm, Ubuntu's mainline 5.14.5 kernel does boot successfully
on my machine with CONFIG_UBSAN_TRAP not set.
--
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/1942684
Title:
I also can't boot the mainline 5.14-4 or 5.14-5 kernels on a Lenovo S7
(AMD 5800H and NVIDIA GPU) - it goes to a blank screen when trying to
boot graphics and freezes - I can't open a tty and have to hard reset
the system.
It looks like I have the laptop in the same mode as the other posters,
ie
Could this be the problem described here:
https://forums.developer.nvidia.com/t/ryzen-7-gtx-1660ti-blank-screen-
on-external-outputs-in-hybrid-graphics-mode/157800
ie (and this is the case if the external display is connected to the
NVIDIA card):
"Using amdgpu as a display offload source is
: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1400 F pulseaudio
rocko 1829 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 27 16
: Linux 5.2.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1400 F pulseaudio
rocko 1829 F pulseaudio
CurrentDesktop
The patch that satmandu mentioned in
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1830961/comments/16
fixes the v5.2.0 mainline kernel build as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 6057 F pulseaudio
/dev/snd/pcmC0D0p: rocko 6057 F...m pulseaudio
Date: Thu May 23 15:01:44 2019
HibernationDevice:
#
https://askubuntu.com/questions/1013830/slow-boot-d
Yes, the amd64 kernels have now built on kernel.ubuntu.com. But newer
mainline kernels are no longer appearing there - 4.20.4 and 5.0-rc3 are
missing!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Oops, it was either acpi_osi=! or acpi_osi='Windows 2009' that was
causing the problem. I had copied them in to try and get the nvidia card
working after resume, but it turns out they aren't needed for the nvidia
card to work anyway.
Sorry for the noise.
** Changed in: upower (Ubuntu)
I can build the mainline 4.20.3 kernel locally if I set "do_dkms_nvidia
= false" in its 0001-base-packaging.patch.
Why would we even want to build the nvidia driver for recent kernels?
Even the most up-to-date nvidia drivers rarely compile for -rc kernels,
and ubuntu typically has an older
@dholbert: your lockup looks like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904 (and the
upstream bug is https://bugs.freedesktop.org/show_bug.cgi?id=100516).
It's a bug in the Intel graphics drivers that unfortunately is present
in both kernels 4.10 and 4.11, but should be fixed in
I find it absolutely astonishing that a bug that is easy to trigger, can
cause data loss, and requires a hard reboot is treated with a lower
priority than security bugs.
Surely Ubuntu 17.04 should be flagged "not suitable for production
machines" until this issue is fixed?
--
You received this
0.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1490 F pulseaudio
Date: Tue May 2 12:36:11 2017
InstallationDate: Installed on 2017-04-13 (18 days ago)
InstallationMe
Public bug reported:
Log attached.
I've seen the 4.10 kernel crash at least twice (on two different
machines) apparently when trying to handle swap. The system slows down
at first and commands like "ps xa" lock up, then the system completely
locks up (I couldn't even access a terminal via
ase: Ubuntu 17.04
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 149
Just a note that you can also find the 4.8 kernel (image and headers) at
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D, and if you
install the deb files from there, you don't need to enable the yakkety
repos.
--
You received this bug notification because you are a member of Kernel
How is this only medium priority? It causes data loss, which is rather
catastrophic...
This might also be related to
https://bugs.freedesktop.org/show_bug.cgi?id=100516, which unfortunately
isn't going to be fixed until kernel 4.12.
** Bug watch added: freedesktop.org Bugzilla #100516
It has been fixed for me since kernel 4.0, so yes, I think it can be
closed 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/1305335
Title:
Cutting or copying files on btrfs to
: rocko 4715 F pulseaudio
CurrentDesktop: Unity
Date: Sat Sep 24 07:29:44 2016
HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7
InstallationDate: Installed on 2016-07-04 (81 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(
-15-generic 4.8.0-15.16
ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
Uname: Linux 4.8.0-15-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 4715 F pulseaudio
8.0-rc7
Uname: Linux 4.8.0-15-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 4715 F pulseaudio
CurrentDesktop: Unity
Date: Sat Sep 24 07:29:44 2016
HibernationDevice: RESUME=U
So I can confirm that adding the extra modeline works, eg I now have
2560x1440@60 Hz both appearing in xrandr and working on the laptop
monitor using the modeset driver.
(There's a separate bug for the modeset driver whereby if you change the
mode, eg from 1920x1080 to 2560x1440, the new screen
Why isn't this a bug in gcc 6? It doesn't seem right that we have to
patch the kernel makefile to get it to build.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574982
Title:
Cannot
Ok, thanks for the info re dpkg-buildpackage.
xf86DefModeSet.c is created by hw/xfree86/common/modeline2c.awk. If you
run dpkg-buildpackage, you'll find it two places:
$ find -name xf86DefModeSet.c
./build-main/hw/xfree86/common/xf86DefModeSet.c
./build-udeb/hw/xfree86/common/xf86DefModeSet.c
>From https://bugs.freedesktop.org/show_bug.cgi?id=97163#c15, I think
it's just a matter of some modelines missing from the xf86DefaultModes
array in xf86DefModeSet.c, eg I suspect that adding this:
/* 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz */
{MODEPREFIX,
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 4715 F pulseaudio
CurrentDesktop: Unity
Date: Sat Sep 24 07:29:44 2016
HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7
InstallationDate: Installed on 2016-07-04 (81 days ago
I tried 4.8-rc4 and I didn't see the skl_update_other_pipe_wm warning
any more. Unfortunately there are regular video glitches and
suspend/resume is broken, so the 4.8 kernel isn't usable yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Just FYI, I proposed a patch at
https://bugs.freedesktop.org/show_bug.cgi?id=97163. I can't test it
beyond checking it compiles without warnings because when I built my own
xserver xorg-server_1.18.4 and installed it to the default prefix
(/usr/local/bin), X crashed. This was without any changes
Is that the right place? The modesetting driver is incorporated into
xserver now, so the versions it offers to report against are very old.
I reported it anyway (against git) at
https://bugs.freedesktop.org/show_bug.cgi?id=97163, in case it helps.
** Bug watch added: freedesktop.org Bugzilla
Thanks for the info.
So it turns out that the problem is that the modesetting driver is
pruning these modelines because it thinks their vertical refresh is
greater than the max vrefresh.
The function in question is
hw/xfree86/drivers/modesetting/drmmode_display.c#add_gtf_modes(), and it
is
Another Ubuntu Perthian! Excellent! I checked another laptop and the
kernel only listed the native resolution of the screen on that as well,
so perhaps the issue is in xserver/modeset after all. But out of
curiosity, what role is the kernel supposed to take here? It does list
all the modes for my
The output is the same for the 4.7.0 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/1606103
Title:
modeset driver does not detect all screen resolutions
Status in linux package
This is the output for kernel 4.6.4-040604-generic (running back on
Ubuntu 16.04, but I guess that shouldn't make any difference if we're
just reading the kernel info):
/sys/class/drm/card0-eDP-1/modes:3840x2160
(There's a bunch of other modes but they are all for the various
resolutions on the
Does this bug happen for people after a USB drive has spun down and the
computer tries to access it? My USB freezing issue goes away if I
disable UAS for a particular drive. It works fine with UAS until it
spins down but the USB subsystem freezes when it tries to spin it up,
requiring me to reboot
Cool, I see the patch is in 4.0-rc3 now (commit
6d65261a09adaa374c05de807f73a144d783669e).
I applied it to 3.19.1-generic and can confirm it works as advertised.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I don't like the idea of eCryptfs supporting the clone ioctl by default.
It would allow an attacker to discover that the files (the original and
the clone) are the same.
I agree with that reasoning.
In any case, I think that the btrfs clone operation should be disallowed
in ecryptfs as a
As a follow-up to comment #16: generally attempting to clone a file in
a non-ecryptfs folder into a mounted ecryptfs folder appears to succeed
but in fact creates a zero-length invalid target file, but going the
other way (cloning from the mounted ecryptfs folder into the non-
ecryptfs folder)
In case anyone still reads bugzilla.kernel.org, I reported this at
https://bugzilla.kernel.org/show_bug.cgi?id=93691.
** Bug watch added: Linux Kernel Bug Tracker #93691
http://bugzilla.kernel.org/show_bug.cgi?id=93691
--
You received this bug notification because you are a member of Kernel
I think it is still useful for ecryptfs to support the btrfs clone ioctl
for the case where both source and target higher files are in the same
ecryptfs mount, since this saves disk space.
We might be able to handle this in
fs/ecryptfs/file.c#ecryptfs_unlocked_ioctl, which gets passed the btrfs
ecryptfs_unlocked_ioctl gets passed the (higher) target file struct as
the first argument, the command as the second, and the source file
descriptor as the third argument. It looks like the source file
descriptor has already been converted to the lower file if it is
associated with a higher file
I checked the mainline 3.11 kernel and it has the bug (as well as 3.13,
3.18 and 3.19, based on the other comments), so I would say it is not a
regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@whoop: If you mean that the thumbnail file length is correct but the
image file is zero bytes, the reason is that the thumbnail file isn't
copied from the non-ecryptfs folder to the ecryptfs folder. Instead, the
system stores thumbnails in ~/.cache/thumbnails. So it creates a new
thumbnail file
Just to note: in the example commands above, of course, /home needs to
be write-accessible to the current user, or you need to use a command
like su root -c echo test /home/test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
The 3.19 kernel still has the problem.
You can reproduce it by copying a test file from say /home into an
encrypted home directory using --reflink:
echo test /home/test
cp --reflink=always /home/test ~
ls -l ~/test # This shows 0 bytes
This command, however, copies the file correctly,
** Tags added: kernel-bug-exists-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/1305335
Title:
Cutting or copying files on btrfs to ecryptfs results in data loss
Status in
@jondee: those are the intel pstate governors. You should be able to
confirm this using the cpufreq-info command.
If you disable intel pstate and reboot you should get the option of
using the other governors (like ondemand) - see
http://askubuntu.com/questions/501840/ubuntu-14-04-used-too-much-
@Paul Gear: you could try 3.18-rc6 from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.18-rc6-vivid/, it works fine with utopic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1384342
I just experienced the bug in 3.18-rc3.
** Tags added: bug-exists-upstream
** Tags added: kernel-bug-exists-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/1384342
Title:
Re 3.18-rc3, I take it back - I was looking at an old log entry. I did
experience a complete system freeze that required a hard reset, but I
don't think it managed to record the error that caused it in the syslog.
** Tags removed: kernel-bug-exists-upstream
--
You received this bug notification
FYI, the 3.17.2 kernel still has the bug. I haven't tried 3.18-rcX yet.
--
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/1384342
Title:
kernel messages intel_crtc_wait_for_pending_flips
/controlC0: rocko F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 13 10:15:41 2014
HibernationDevice: RESUME=UUID=ca164267-edcd-4d3c-b325-acbd60802e7a
InstallationDate: Installed on 2014-02-08 (246 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64
COMMAND
/dev/snd/controlC0: rocko F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 13 10:15:41 2014
HibernationDevice: RESUME=UUID=ca164267-edcd-4d3c-b325-acbd60802e7a
InstallationDate: Installed on 2014-02-08 (246 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 13 10:15:41 2014
HibernationDevice: RESUME=UUID=ca164267-edcd-4d3c-b325-acbd60802e7a
InstallationDate: Installed on 2014-02-08 (246 days ago)
InstallationMedia
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 13 10:15:41 2014
-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1894 F pulseaudio
CurrentDesktop: Unity
Date: Wed Aug 27 17:26:27 2014
-image-3.16.0-10-generic 3.16.0-10.15
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1894 F
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1894 F pulseaudio
CurrentDesktop: Unity
Date: Wed Aug 27 17:26:27 2014
HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0
InstallationDate: Installed on 2014-08-22 (5 days ago
x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1894 F pulseaudio
CurrentDesktop: Unity
Date: Wed Aug 27 17:26:27 2014
HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0
-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1894 F pulseaudio
CurrentDesktop: Unity
Date: Wed Aug 27 17:26:27 2014
HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa
: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1894 F pulseaudio
CurrentDesktop: Unity
Date: Wed Aug 27 17:26:27 2014
HibernationDevice: RESUME=UUID=e586cc1f-5429
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 1894 F pulseaudio
CurrentDesktop: Unity
Date: Wed Aug 27 17:26:27 2014
HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0
InstallationDate: Installed on 2014-08-22 (5 days ago)
InstallationMedia
Yes, this bug was fixed in the 3.13 kernel, so it works fine in Trusty
(and should do in earlier releases if you install a 3.13 kernel). But I
don't know exactly what fixed it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug is still present in Ubuntu 13.10 using the latest (stable)
3.12-1 kernel from the weekly kernel builds.
** 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
3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 2813 F pulseaudio
Date: Tue Oct 1 10:13:24 2013
InstallationDate: Installed on 2012-08-25 (401 days ago)
InstallationMedia
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 2813 F pulseaudio
Date: Tue Oct 1 10:13:24 2013
InstallationDate: Installed on 2012-08-25 (401 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2)
MachineType
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 2813 F pulseaudio
Date: Tue Oct 1 10:13:24 2013
InstallationDate: Installed on 2012-08-25 (401 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2)
MachineType: Dell Inc
-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 2813 F pulseaudio
Date: Tue Oct 1 10:13:24 2013
InstallationDate: Installed on 2012-08-25 (401 days ago)
InstallationMedia: Ubuntu
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 2813 F pulseaudio
Date: Tue Oct 1 10:13:24 2013
InstallationDate: Installed
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rocko 2813 F pulseaudio
Date: Tue Oct 1 10:13:24 2013
InstallationDate: Installed on 2012-08-25 (401 days ago)
InstallationMedia: Ubuntu 12.10 Quantal
- /dev/snd/controlC0: rocko 2813 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: rocko 2813 F pulseaudio
Date: Tue Oct 1 10:13:24 2013
InstallationDate: Installed on 2012-08-25 (401 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64
I recommend switching back to to use intel pstate by default for the
3.11 kernel in Saucy as the overly-high frequency issue seems to be
resolved now (from what I recall when I was trying out the 3.10 and 3.11
kernels, this issue was caused by particular settings in the kernel
config; changing the
73 matches
Mail list logo
