It seems Serge knows what's going on, so tentatively closing the linux
task.
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/bug
hallyn | stgraber: i was thinking lcx-start-ephemeral used the api more than it
does.
hallyn | stgraber: lcx-start-ephemeral needs to be updated the same way the api
did, for the new overlayfs options
--
You received this bug notification because you are a member of Kernel
Packages, which is su
** No longer affects: 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/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in AppArmor Linux app
Reopening the kernel task here. We've carried the "temporary" udev rule
workaround for three releases now; it seems we all agree that it's wrong
(unconditional "unbreak my kernel rule") and makes things even worse
under memory pressure. Is there any better solution in sight? Thanks!
** Changed in:
systemd 219 is planned in about two weeks which will contain this.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
Hello Mathieu, or anyone else affected,
Accepted grub2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-9ubuntu1.10 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Mathieu, or anyone else affected,
Accepted grub2-signed into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.34.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Mathieu, or anyone else affected,
Accepted shim-signed into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.16~16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
h
Colin, please fix this in yakkety so that the SRU can be released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1587686
Title:
ZFS: Running ztest repeatedly for long periods of tim
** Changed in: libatasmart (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1581594
Title:
constantly shows wrong temperature (99°C
The verification of the Stable Release Update for zfs-linux 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
The verification of the Stable Release Update for zfs-linux 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
The verification of the Stable Release Update for linux-firmware 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 enco
Thanks Colin, great work! I'll deploy this ASAP.
FYI, at least some of the VM hosts in scalingstack got updated to a 4.4
kernel. Not sure how much that changes your investigations.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
lxd-armhf1 (on swirlix01) has run without any lockup since the host
kernel update to 4.4. I created a new lxd-armhf2 yesterday (on
swirlix08) which also survived without any workaround. At the same time
I created a new lxd-armhf3 (on swirlix16) which has locked up pretty
well every < 15 minutes (I
[hloeung@ragnar tmp]$ for i in {01..09} 16; do ssh
swirlix${i}.bos01.scalingstack "uname -a"; done
Linux swirlix01 4.4.0-30-generic #49~14.04.1-Ubuntu SMP Thu Jun 30 22:20:09 UTC
2016 aarch64 aarch64 aarch64 GNU/Linux
Linux swirlix02 4.4.0-30-generic #49~14.04.1-Ubuntu SMP Thu Jun 30 22:20:09 UTC
hloeung | pitti: yeah, I believe work was done to get swirlix01-09 to
4.4
--
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:
[arm64] lockups some time after booting
Status in
> can you try using the following kernel parameters on the VM and see if this
> helps:
> rcu_nocb_poll rcutree.kthread_prio=90 rcuperf.verbose=1
the instance on swirlix16 (on 4.2 kernel) hung again (twice), with the
attached console log. This now has the above kernel parameters, but I'm
afraid it
** Package changed: udev (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/1589997
Title:
The device on /dev/sdx is not created when inserting new devices
Status
Maintaining an ever-growing list of vendors is error-prone and TBH quite
silly. Are there any CPUs where we *don't* want hot-add? If not, why
can't the kernel just default to enabling this, instead of userspace
unconditionally turning this on? But if hot-add is supposed to work
everywhere, then for
Thanks Colin! So this confirms that we really should let the kernel be
in "performance" during boot. But from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/comments/9
it actually sounds like we should leave it to "performance" all the time
at least for processors which are ≤ 5 years
So it seems we should make the "ondemand" init script a no-op if
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver contains
"intel_pstate", since in this case "ondemand" is worse than
"performance"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
So it seems we should make the "ondemand" init script a no-op if
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver contains
"intel_pstate", since in this case "ondemand" is worse than
"performance"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
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/1584124
Title:
revisit /etc/init.d/ondemand
Status
Closing the kernel task, as it's now obvious that we want to keep the
"performance" default there, and only do the "ondemand" thing for older
processors.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
Yo
ew => In Progress
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: sysvinit (Ubuntu Xenial)
Importance: Undecided => Medium
** Summary changed:
- Consid
@dino99: That's fine, the script has
AVAILABLE="/sys/devices/system/cpu/cpu$FIRSTCPU/cpufreq/scaling_available_governors"
[ -f $AVAILABLE ] || exit 0
thus it's a no-op for those cases.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=2558ca88
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=2558ca88
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
> I would be happy to unconditionally turning hot-add on and SRU the
udev rule back to Ubuntu 14.04.
As I (and Kay) said, this is okay for an SRU, but unconditionally
second-guessing/changing the kernel defaults is just wrong and
inefficient too. For yakkety and onwards this *really* should be fix
Public bug reported:
linux' tests have recently started to fail differently in y than they
were failing before:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-yakkety/yakkety/ppc64el/l/linux/20160610_110617%40/log.gz
Cloning into 'autotest-
This happens without any --user-data or any particular interaction, just
by plainly booting a standard image.
--
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:
[arm64] locks
Neither did this trigger on two trusty 4-cpu instances so far.
--
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:
[arm64] locks up some time after booting
Status in Auto Pack
Undecided
Status: New
** Changed in: auto-package-testing
Status: New => Triaged
** Changed in: auto-package-testing
Importance: Undecided => Medium
** Changed in: auto-package-testing
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notif
ing
Assignee: Martin Pitt (pitti) => (unassigned)
** Summary changed:
- [arm64] locks up some time after booting
+ [arm64] locks up some time after booting when idle if tickless (nohz=on) is
used
** Summary changed:
- [arm64] locks up some time after booting when idle if tickless (nohz=
Oh noes! I'm still getting "task * blocked for more than 120 seconds"
hangs even with nohz=off :-( Is there another option which I could try?
** Changed in: auto-package-testing
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packag
** 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/1592585
Title:
radeon.ko not loads automatically after updates
Status in linux pack
> It may be worth trying nohz=off on the host as well
Junien did that on the nova compute host, and no change. Processes in
the instance still freeze.
This is actually also consistent with the observation that this
apparently does not happen with the trusty kernel.
--
You received this bug noti
Hang still occurs with xenial kernel and one instance of
nice -n 19 dd if=/dev/zero of=/dev/null bs=1024 &
I have now rebooted and started four dd's, so that all four CPUs should
remain busy constantly.
--
You received this bug notification because you are a member of Kernel
Packages, which
FTR, running the trusty kernel on xenial userspace does not work:
http://paste.ubuntu.com/17392362/
cking | pitti, syscall 384 on aarch64 is getrandom() and that does not
exist on trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Package changed: udev (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/1593291
Title:
USB 2 vs. 3 device mapping is inconsistent
Status in linux package in U
Further notekeeping:
- 4 dd's (xenial+nohz=off) has survived for half a day, then the instance
crashed on something else.
- trusty and vivid kernels with nohz=off have survived for a full day without
any lockups. lxd on trusty kernel causes a lot of leaked "FREEZED/FREEZING"
containers, but th
Hello Mathieu, or anyone else affected,
Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Mathieu, or anyone else affected,
Accepted grub2-signed into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.66.1 in a few hours,
and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Mathieu, or anyone else affected,
Accepted dkms into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Colin Ian King [2016-06-17 10:50 -]:
> I'm trying to get a reliable reproducer on a similarly sized aarch64
> host. Just so that I'm not missing anything, what is the entire command
> line being used on the host to run the VM?
I can't determine this. I asked Junien on IRC to put it here.
> A
>- trusty and vivid kernels with nohz=off have survived for a full day
without any lockups.
They both hung last night.
So in summary: Neither nohz=off nor older kernels help here. This really
seems to be a matter of luck/what's going on on the host system.
** Summary changed:
- [arm64] lockups
The verification of the Stable Release Update for initramfs-tools 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 enc
Meh, I meant to release grub2{,-signed} for trusty, fat-fingered this. I
removed the copy into -updates, as this is premature.
** Changed in: grub2 (Ubuntu Xenial)
Status: Fix Released => Fix Committed
** Changed in: grub2-signed (Ubuntu Xenial)
Status: Fix Released => Fix Committed
Hello Brian, or anyone else affected,
Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Mathieu, or anyone else affected,
Accepted shim-signed into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.15~14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
h
Hello Mathieu, or anyone else affected,
Accepted shim-signed into precise-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.15~12.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Mathieu, or anyone else affected,
Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04.6 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Mathieu, or anyone else affected,
Accepted grub2-signed into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.34.10 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Mathieu, or anyone else affected,
Accepted grub2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-9ubuntu1.9 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Package changed: udisks2 (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/1603578
Title:
unable to enumerate USB device
Status in linux package in Ubuntu:
** Package changed: systemd (Ubuntu) => bluez (Ubuntu)
** Project changed: systemd => bluez
--
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/1603715
Title:
bluetooth unavailable after rfk
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
The verification of the Stable Release Update for ubuntu-fan 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 encounte
Hello Andy, or anyone else affected,
Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Confirmed. /etc/mtab is dead, dead, dead, and an ill-conceived and
broken concept. Don't ever use it please ☺
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1607920
Title:
zfs servic
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
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/1600124
Title:
Adjust KBL PCI-ID's
Status in libdrm package in Ubuntu:
F
Hello Pedro, or anyone else affected,
Accepted snap-confine into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/snap-
confine/1.0.38-0ubuntu0.16.04.10 in a few hours, and then in the
-proposed repository.
Please help us by testing this new pac
** Summary changed:
- Permanent I/O from kworker since migrated to systemd
+ Permanent I/O from kworker and ecryptfs
** 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.
> The preferred governor with the intel_pstate driver is powersave.
Do you have some references/proof for that? This is contrary to what
kernel developers say, see comment 1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Thanks Doug! Ack, I'll change it to use "powersave" again then.
** Changed in: systemd (Ubuntu)
Status: Fix Released => In Progress
--
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/15
With https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=94a70093 it uses powersave on
intel_pstate again, like in xenial.
> pitti, can we please have a config option to disable "ondemand"?
Indeed, right now it is statically enabled, so it can only be disabled
with "systemctl mask
> I'll make it dynamically enabled
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=19e67c70
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625100
Title:
systemd 231-6 ADT test failure with linux 4.8.0-
** Summary changed:
- systemd 231-6 ADT test failure with linux 4.8.0-11.12
+ systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el,
systemd-tmpfiles crash
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
I tried to reproduce the full boot-and-services test log on
scalingstack, and upon rebooting into the 4.8 kernel I got the attached
kernel oops. This does everytime, though.
** Attachment added: "4.8/ppc64el kernel crash log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625100/+atta
> [kernel oops] This does everytime, though.
This was supposed to mean: This does *not happen* every time.
--
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/1625100
Title:
systemd test fai
FTR, I ran the full boot-and-services test against the current PPA which
has kernel -11.12 and could not reproduce the crash. Could it be that
this was a regression in -10.11 (the test runs in the description) which
got fixed in -11.12 again?
So the only concrete thing here that I can see is the m
** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624844
Title:
Ubuntu 16.04 breaks boot with wrong zpool.cache
Status in zf
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
(Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: In Progress
** Tags: bot-stop-nagging
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Ch
Public bug reported:
With yakkety's recent update from linux 4.4 to 4.8 my brightness keys
stopped working. They are not handled in software via evdev events (on
most platforms you just get a KEY_BRIGHTNESS{UP ../../../:00:02.0
-r--r--r-- 1 root root 4096 Sep 22 09:45 max_brightness
drwxr-xr-x
Public bug reported:
With yakkety's recent update from linux 4.4 to 4.8 booting has become a
lot slower. It's not one service in particular, but without "quiet" and
"splash" you can now easily read every single line instead of that whole
wall of text zipping by. It now takes over 20s instead of ~1
Confirmed with 4.8.0-14.15-generic from yakkety-proposed.
Immediately after boot the system load is also reported as ~ 250, and
then slowly goes down towards zero.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
I do not see this in QEMU (even with -smp 4), only on my laptop. At this
point I'm not sure if it is specific to my ThinkPad X230 or happens for
others too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
This is the first test that boots the root disk without an initrd.
Indeed booting it with debug shows that the kernel detects no hard disks
then (in particular not /dev/sda1), thus the boot fails like that.
With 4.4, or with 4.8 and booting with an initrd it detects the sda hard
drive again:
[
> This only happens on amd64, i386 and ppc64el are fine.
FTR, this is because we run the qemu tests only on amd64. i386 also has
CONFIG_ATA=m 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
Talked to Andy on IRC, and dropping these drivers was not intended. I
agree we should keep the most common ones built in, especially for cloud
instances; there it would really be beneficial to drop initrds
completely (see bug 1592684), as they are just bloat there.
** Changed in: systemd (Ubuntu)
> CONFIG_FAT_DEFAULT_IOCHARSET somehow got changed to utf8 instead of
iso8859-1.
Related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833238
TL;DR: Use this:
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
FAT_DEFAULT_UTF8=y
** Bug watch added: Debian Bug tracker #833238
http://bugs.debian.org
The verification of the Stable Release Update for dkms 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 a reg
http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/ppc64el passed
a few times again, and that tmpfiles crash never reproduced.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Fix Released => Invalid
--
You received th
This was fixed in -14, scsi_debug is back.
** Changed in: linux (Ubuntu)
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.launchpad.net/bugs/1625100
Title:
systemd t
Oh, forgot: for evtest you might need to try with several devices, such
as "ThinkPad Extra Buttons" and the actual keyboard.
--
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/1626651
Title:
This looks like one keypress would cause a massive spew of uevents
and/or evdev events. Can you please run "sudo evtest" and "udevadm
monitor -e", then press a brightness key once, then ^C both and
copy&paste the output?
I don't get this on my ThinkPad X230, I have the opposite problem
(brightnes
** Attachment added: "pitti's x230 acpidump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626429/+attachment/4746382/+files/acpidump-x230.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
So this did break with -10 and -11, but was fixed again in -14.
** Changed in: linux (Ubuntu)
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.launchpad.net/bugs/162642
I just dist-upgraded again, and with 4.8.0-14 my brightness keys work
again (bug 1626429). Under i3 (no unity-settings-daemon), I get a tame
and immediate reaction:
UDEV [38372.886325] change
/devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight)
ACTION=change
DEVPATH=/devices/pci0
201 - 300 of 536 matches
Mail list logo
