I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is
fixed in 18.10 (cosmic) with 4.18.0-1ubuntu2.
** Also affects: iproute2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: iproute2
This happens in about half of the xenial semaphoreci.com instances as
well:
$ uname -a
Linux semaphore-light-1809b 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12
15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, whi
FTR, I just ran fatrace a lot in a current Ubuntu 20.04 VM to debug
#1885188, and it seems fine.
--
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/1861053
Title:
no fatrace output in focal
Thanks Daniel! PR merged upstream. There are a few other test
deprecation warnings/failures I'm looking into before doing a release.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1696480
I released 0.16.8 upstream and uploaded it to Debian unstable, from
where it should autosync into Ubuntu devel soon.
** Changed in: python-dbusmock (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: python-dbusmock
Status: Fix Committed => Fix Released
--
You received this b
This still works fine with Linux 4.4.0-8, but fails on 4.4.0-10, so it's
a kernel regression.
This can be reproduced much simpler without LXC:
$ mkdir /tmp/lower /tmp/upper /tmp/work /tmp/merged
$ sudo mount -t overlay overlay
-olowerdir=/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/work /tmp/merg
Reproducer is available, not hw specific, so doesn’t need additional
logs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Nice work Seth, 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/1555997
Title:
overlay fs regression: chmod fails with "Operation not permitted" on
chowned files
Status in linu
There is no symptom or error description in your report at all. Dmesg
shows that the btrfs task is hung, but there's still not much to go
with.
** Summary changed:
- Systemd crash
+ task btrfs-transacti:1089 blocked for more than 120 seconds
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, w
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
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/1556433
Title:
Booting is taking too long to start from grub
Status in linux packag
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
--
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/1558275
Title:
wrong/missing permissions for device file /dev/prandom (prng
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
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/1566828
Title:
Suspension does not work, freezes the pc
Status in linux package in
For the record, this "auto-destruct" behaviour with the xenial kernel
happens just by itself: reboot the instance, let it sit there for 15 or
60 minutes, then this kernel spew starts happening and it gets locked
up with losing network/ssh access. There was no actual payload on
these.
--
You rec
The kernel spews out some oopses
(https://launchpadlibrarian.net/234191094/CurrentDmesg.txt) About the
connection error, that is mostly tracked in bug 1502097, so let's devote
this to the kernel error.
** Summary changed:
- package systemd 225-1ubuntu4 failed to install/upgrade: subprocess instal
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
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/1551148
Title:
cfg80211 kernel module crashes
Status in linux package in Ubuntu:
The kernel issue still happens (see
http://autopkgtest.ubuntu.com/packages/u/udisks2/xenial/amd64/), so the
workaround needs to come back.
** Changed in: udisks2 (Ubuntu)
Status: Fix Released => In Progress
** Changed in: udisks2 (Ubuntu)
Milestone: ubuntu-15.01 => ubuntu-16.03
--
Yo
The workaround doesn't work any more, and the test does not actually
depend on ntfs-3g any more, so this must rather be fixed in our base
images.
** Changed in: udisks2 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: udisks2 (Ubuntu)
Milestone: ubuntu-16.03 => None
--
You
I re-tried with the current kernel 4.4.0-8, and merely booting a
pristine cloud image with "nova boot --poll --image ubuntu/ubuntu-
xenial-daily-arm64-server-20160227-uefi1.img --flavor m1.large" and
letting it sit there for some 20 minutes is still auto-destructing:
[2J[01;01H[=3h[2J[01;01H[2J[01
Booting with "debug=y" works better, as then the initramfs debug goes
right on the console, instead of /run/initramfs/initramfs.debug. This
shows that even the initrd starts after the error message, so this must
come from the kernel itself:
Loading Linux 4.4.0-8-generic ...
Loading initial ramdisk
Indeed the code in
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/rtc/hctosys.c
looks like it runs entirely "self-"triggered (late_initcall), not
triggered by an userspace call. This function tries to open the device
which simply isn't present (yet) at that time. So may
https://github.com/seccomp/libseccomp/pull/22 Thanks Andy!
** Changed in: libseccomp (Ubuntu)
Importance: High => Undecided
** Changed in: libseccomp (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: libseccomp (Ubuntu)
Assignee: Andy Whitcroft (apw) => (unassigned)
--
I managed to get the 4x CPU instance into the same locked up state now,
so AFAICS the problem isn't fundamentally different between 4 and 8
cores.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Reducing the number of threads that Go uses seems to help a bit:
$ cat /etc/systemd/system/lxd.service.d/override.conf
[Service]
Environment=GOMAXPROCS=1
(GOMAXPROCS defaults to the number of CPUs). But Stéphane is still able
to lock up LXD pretty fast even with that.
--
You received this bug n
Confirming that 4.4.0-2 works fine on an arm64 box. 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/1533009
Title:
arm64: "unsupported RELA relocation"
Status in Linaro GCC:
Un
** Summary changed:
- lxd and other commands get stuck on arm64 kernel and multiple CPUs
+ [arm64] multithreaded processes get locked up in futexes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Some good news: With bug 1534545 fixed I was now able to upgrade to the
Xenial 4.4 kernel. On the 4x CPU instance two parallel adt-run loops
have now run for about two hours without any dmesg spew. Stéphane has
run "lxc-test-concurrent -j 16 -i 10" twice on the 8x CPU instance
successfully too.
Ba
Darn, I now get the "instance kills itself after some time" on the 4x
CPU as well. nova console-log shows the blurb below and ssh and lxd
ports are dead (so I can't learn anything further from the box than
console-log).
Ubuntu Xenial Xerus (development branch) lxd-armhf2 ttyAMA0
lxd-armhf2 login:
Hello Thiago, or anyone else affected,
Accepted dpdk into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dpdk/2.2.0-0ubuntu8 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Public bug reported:
The kernel has been able to load firmware by itself for several years
now, and as a result the userspace loading of firmware got dropped in
udev three years ago
(https://github.com/systemd/systemd/commit/be2ea723b1d0).
But Ubuntu's kernels still enable CONFIG_FW_LOADER_USER_H
Oh, curious that CONFIG_DELL_RBU depends on the userspace firmware
helper (as a BIOS update sounds like the communication and request goes
from userspace to kernel, not the other way around?).
Anyway, this isn't urgent at all, so if it's not appropriate at that
time, please just close it.
** Chan
This is a syslog from one boot up to the point where I hard-rebooted the
instance because it was completely hanging. The kernel errors still
look by and large like the ones from the original report (in
JournalErrors.txt).
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/
Thanks, reassigning to the kernel then. Please run "apport-collect
1578015" to attach your hardware information. Also, please use "ubuntu-
bug" to file bugs so that this happens automatically in the future.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Yet another
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Changed in: bcmwl (Ubuntu Vivid)
Status: Fix Committed => Won't Fix
--
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Changed in: bcmwl (Ubuntu Vivid)
Status: Fix Committed => Won't Fix
--
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Tags removed: verification-needed
--
You received this bug notification becaus
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
OK, I'll unsubscribe sponsors then. Please re-subscribe once there are
updated patches. Thank you!
--
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/1250109
Title:
Please use dpkg-triggers
Colin Ian King [2016-05-13 11:07 -]:
> Martin, I've going on a hunch, can you try the kernels to see if these
> help:
>
> http://kernel.ubuntu.com/~cking/lp1531768/
I installed that on two out of three lxd hosts. I'll watch the
notification emails of my watchdog and will let you know next wee
Two boxes (lxd-armhf{1,2}) have been running for three days with cking's
kernel, 3 is running the standard xenial kernel. 1 and 3 don't respond
to ssh connections any more; 2 still does, but several processes are in
'D' state:
root47 0.0 0.0 0 0 ?DMay13 0:00 [fsnot
To fix your system locally you can set some custom names for these two
devices, or disable the ifnames schema completely. Please see
/usr/share/doc/udev/README.Debian.gz for details.
Can you please copy&paste the output of
SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id
/sys/class/net/eno1
After installing the 4.6 kernel and rebooting, lxd-bridge.service failed
the same way on two boxes:
May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2112]: Failed to setup lxd-bridge.
May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2129]: RTNETLINK answers: Operation
not supported
May 17 11:27:26 lxd-armh
> I now let one box run with 4.6.0, let's see how long it'll hold up.
Checking again, I got a dozen auto-reboots from the watchdog, and after
disabling the watchdog and inspecting the box after 4 hours I see
exactly the same symptoms.
--
You received this bug notification because you are a membe
I installed the debug kernel on one arm64 box last night, and it has now
run for 12 hours. lxd is still running, no hung processes, and dmesg
shows nothing unusual, i. e. no extra debug messages. Yay heisenbug?
The other box with the standard xenial kernel has locked up as always;
I'll install the
The verification of the Stable Release Update for linux-flo has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
One box completely froze again (ssh does not respond any more),
attaching dmesg. However, I'm not sure that this actually contains what
you were looking for -- there is a lot of the usual chatter from
starting/stopping containers, and then some traces about hung tasks when
trying to flush the file
FTR, I'm also having problems with the wily arm64 kernel on multi-CPU
machines. I filed that as bug 1531768 as the logs here look rather
different to mine. But maybe it's related.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Public bug reported:
I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
want to use for armhf autopkgtesting in LXD). I started with wily as
that has lxd available (it's not yet available in trusty nor the PPA for
arm64).
However, pretty much any LXD task that I do (I haven't
"reboot" also takes too long to be practical (I killed the instance
after waiting for 10 mins, as it didn't even begin to shut down).
--
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/1531768
I take that back. It does survive for much longer, but after some 15
minutes of running I again run into tons of
[ 2424.611668] INFO: task systemd-udevd:1320 blocked for more than 120 seconds.
[ 2424.613514] Tainted: GW 4.2.0-22-generic #27-Ubuntu
[ 2424.615183] "echo 0 > /proc
> Can you collect apport information from the host system as well?
Sorry, I can't. I can create Scalingstack instances, but I have no
access to the host systems. The IS team certainly can, though.
> Do you get the same effects with a single vCPU?
So far that test system is holding up and I haven
FTR, the "networking broken in containers" was an MTU mismatch, worked
around now. Thanks to Andy for figuring this out!
--
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/1531768
Title:
arm
Public bug reported:
(Split out from bug 1531768)
Installing the current xenial kernel on arm64
(http://ports.ubuntu.com/pool/main/l/linux/linux-
image-4.3.0-5-generic_4.3.0-5.16_arm64.deb) regresses the creation of
bridges, which breaks LXC:
lxc fails on lxc-net:
Jan 07 10:03:15 lxd-armhf1w sy
I split out the xenial bridge regression into bug 1534545, so that this
can keep focussing on the "processes become slow and hang after a while"
main aspect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
> BTW, the issue can only be reproduced on Xenial.
Confirmed, from my duplicate bug 1534545. I reproduced that with "ip
link add dev lxcbr0 type bridge", supposedly that also needs to load a
module.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
I did install haveged which indeed seems to help quite a bit. But now
after having used an xlarge (8 CPU) instance for a while, I again get
hanging processes, like
ubuntu2317 0.0 0.0 0 0 pts/0D+ 16:14 0:00 [tail]
I used that tail on /var/log/lxd/lxd.log to see what's going
Another data point: I tried to install 3.19 (the kernel that we have on
the buildds) on the xlarge instance, and lxc list now hangs there as
well.
I haven't yet seem lxc list hang on a large (4 CPUs) instance, but the
whole thing (running tests in containers) is still very slow. TBC on
Monday..
-
lxd-armhf1 (8 CPUs) is again in a state where "lxc list" and even "top"
hang forever. lxd-armhf2 was unfortunately shutdown in the previous
days, so I just booted it again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Retitling. The "unusably slow" part was fixed with installing haveged,
so what remains is that the 8x CPU instance gets into this lockup state
after some time.
On the 4x instance I'm now running adt-run in a loop, so far it's
through ~ 10 iterations. I'll let it run over night and see how it is
ke
> So the easiest fix for this, at a cost of 81kb is to just move ib_iser
from linux-image-extra to linux-image.
It actually appears to me that the easier and less risky (as in
"minimize behaviour change") fix is to just drop /lib/modules-load.d
/open-iscsi.conf ? I mean, the module hasn't been loa
I tried this again yesterday evening, with an up-to-date xenial arm64
image, and lo and behold: Both setting it up and running two parallel
loops with calling adt-run over night, and they went through ~ 500
iterations without a hitch.
So I suppose this was fixed by some newer kernel, the new glibc
Meh, of course this came back. Only not a few minutes after booting any
more, but two days.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
** Summary changed:
- [arm64] locks up a few minutes after booting
+ [arm64] locks up some time after booting
--
You received this
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1311071
Title:
hyper-v: IP Inj
Ah, thanks for the clarification. I now see that hv_set_ifconfig is
shipped in linux-cloud-tools-common, so reassinging to its source
package "linux".
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notificatio
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1311048
Title:
hyper-v: hv_set
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => 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/1311055
Title:
Public bug reported:
bluetooth.service does not install itself. The Debian package has a
workaround for this.
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: Triaged
** Tags: systemd-boot
** Changed in: bluez (Ubuntu)
Assignee
** Description changed:
bluetooth.service does not install itself. The Debian package has a
- workaround for this.
+ workaround for this:
+ http://packages.qa.debian.org/b/bluez/news/20140306T074915Z.html
--
You received this bug notification because you are a member of Kernel
Packages, which
Fixed uploaded to ppa:pitti/systemd.
** Changed in: bluez (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1312032
Title:
[systemd] does n
** Bug watch added: Debian Bug tracker #713877
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
A simple smoke test might be to run something like
sudo dd if=/dev/sda of=/dev/zero &
sudo find / >/dev/null 2>&1 &
sudo grep -r . / >/dev/null &
and run fstrim-all in parallel. You can of course do the original thing
of setting up a schroot and sbuild libreoffice in that (or just "sudo
apt
*** This bug is a duplicate of bug 1252121 ***
https://bugs.launchpad.net/bugs/1252121
** This bug has been marked a duplicate of bug 1252121
missing PrepareForSleep signal after resuming, causing networking to stay
disabled
--
You received this bug notification because you are a member
Trusty fix got uploaded:
https://launchpad.net/ubuntu/+source/bluez/4.101-0ubuntu12
** Also affects: bluez (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Trusty)
Importance: Undecided
Status: Confirmed
** Changed in: bluez (Ubuntu Trusty)
Precise SRU uploaded to queue:
https://launchpad.net/ubuntu/precise/+queue?queue_state=1
Unsubscribing sponsors team, subscribing SRU team.
** Changed in: bluez (Ubuntu Precise)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: kerneloops (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kerneloops in Ubuntu.
https://bugs.launchpad.net/bugs/1289311
Title:
kerneloops is waking up relatively frequ
Can you please give me the output of
apt-cache policy linux-image-`uname -r`
? Thanks!
** Project changed: apport => apport (Ubuntu)
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Anders, please stop walking around Launchpad and changing the status of
random bugs.
** Changed in: ubuntu-cdimage
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
So that actually looks fine. The zoom in/out keys produce proper key
values, and the camera symbol produces KEY_IMAGES, i. e. open your
photos.
Unfortunately these key codes are all > 255, so they can't be used in
X.org (bug 313514). This will get better with Mir, Wayland, or similar
technologies.
Quantal is only a few days away from EOL.
** Changed in: dkms (Ubuntu Quantal)
Status: New => Won't Fix
--
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/1261116
Title:
dkms uninstal
I sponsored the precise SRU. Please set up the bug description according
to https://wiki.ubuntu.com/StableReleaseUpdates#Procedure (add test
case, regression potential).
I strongly suggest to set raring/saucy to WONTFIX, I don't think the
cost/benefit ratio is high enough on these short-lived rele
Sponsored trusty upload from MP.
** Changed in: dkms (Ubuntu Trusty)
Status: New => Fix Committed
--
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/1261116
Title:
dkms uninstall fail
For the record, due to this bug we limited automatic fstrim to Samsung
and Intel drives for now: https://launchpad.net/ubuntu/+source/util-
linux/2.20.1-5.1ubuntu14
I can't say I like that much as it excludes a lot of other "good" SSDs
from being trimmed by default, but better safe than sorry. We
*** This bug is a duplicate of bug 1229591 ***
https://bugs.launchpad.net/bugs/1229591
** This bug has been marked a duplicate of bug 1229591
8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate
evdev events after saucy upgrade
--
You received this bug notificatio
Please do "dmesg > /tmp/dmesg.txt" after you plug in the device, and
attach /tmp/dmesg.txt. Thanks!
** Package changed: udev (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Package
Dave, thanks; so smartctl and hdparm indeed show the same model number,
just wanted to confirm. I whitelisted these in
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/util-
linux/trusty/revision/103
--
You received this bug notification because you are a member of Kernel
Packages, whic
If we have evidence that Ritesh's SSD is the only (or one of very few)
affected models, I'm also not opposed to just blacklisting that. But we
really can't know. At least it's now fairly easy to enable in
/etc/cron.weekly/fstrim on all models, but of course that whole TRIM
business is still way to
Preferably lxcproc should stop using hardcoded names and detect devices
it wants to talk to by their subsystem and properties. If it wants to it
could ship some udev rules to help with identification or creating
symlinks; but symlinks aren't supposed to help programs find devices,
they are mostly a
Joel Ebel [2014-02-10 3:23 -]:
> So this used to (At least as recently as 12.04) stably sit on /dev/lcd0,
> and now, as this bug indicates, it seems to pick randomly between
> /dev/lcd0 and /dev/lcd2. Is the kernel responsible for that?
Yes. It's indeed weird why it wouldn't start enumerating
Public bug reported:
In our quantal to saucy test upgrades, configuring the kernel fails as
follows:
Setting up linux-image-3.11.0-15-generic (3.11.0-15.25) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /e
the i386 and all quantal-saucy-server-* tests fail with the exact same
reason, e. g.
https://jenkins.qa.ubuntu.com/job/upgrade-ubuntu-quantal-saucy-desktop-i386/25/artifact/results/apt-term.log
https://jenkins.qa.ubuntu.com/job/upgrade-ubuntu-quantal-saucy-server-tasks-i386/25/
older tests fail i
This test runs in LXC, but I haven't seen it in any of the upgrades to
trusty yet (which use the same mechanics in terms of LXC and calling do-
release-upgrade, etc.). But still, at this point it could very well be a
flaw in our test machinery as well, so I don't set to "triaged" yet and
don't assi
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1279658
Title:
precise → saucy upgrade fail
This already happens in quantal proper, in the pristine container:
$ sudo /etc/kernel/postinst.d/zz-update-grub 3.5.0-45-generic
/boot/vmlinuz-3.5.0-45-generic
/usr/sbin/grub-probe: error: failed to get canonical path of none.
The installed version of /etc/kernel/postinst.d/zz-update-grub does
1 - 100 of 536 matches
Mail list logo
