** Tags added: jammy regression-release
** Tags removed: regression-release
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-signed (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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/2049689
Title:
linux-image-5.15.0-94-generic breaks partprobe
** Changed in: fatrace (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.launchpad.net/bugs/1861053
Title:
no fatrace output in focal
Status in fatrace package in
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
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,
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:
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
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
** No longer affects: systemd (Ubuntu)
--
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/1645631
Title:
Sending files fails because obex not loaded
Status in bluez package in Ubuntu:
** Changed in: dkms (Ubuntu Trusty)
Assignee: Martin Pitt (pitti) => (unassigned)
** No longer affects: dkms (Ubuntu Wily)
** Changed in: dkms (Ubuntu Trusty)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages,
I also see this with exfat, so it rather seems to be related to fuse (as
both ntfs-3g and exfat use fuse). Curiously I do not see this when
running the tests on my laptop or on the Scalingstack cloud infra, just
when I run them in QEMU.
--
You received this bug notification because you are a
> Curiously I do not see this when running the tests on my laptop
And of course in the minute I write this it does happen again (I ran the
test maybe 20 times today, and only just now it happened):
[11359.569157] INFO: task systemd-udevd:341 blocked for more than 120 seconds.
[11359.569163]
The version of bcmwl 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.
** Changed in: bcmwl (Ubuntu Precise)
Status: New => Won't Fix
--
You
The version of bcmwl 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.
** Changed in: bcmwl (Ubuntu Precise)
Status: Fix Committed => Won't Fix
The version of bcmwl 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.
** Also affects: bcmwl (Ubuntu Precise)
Importance: Undecided
Status:
The version of bcmwl 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 a member of Kernel
> http://kernel.ubuntu.com/~jsalisbury/lp1626436/yakkety-proposed-
patched
This is a GOOD kernel as well -- booting is almost as fast as with 4.4,
and the load doesn't explode under sbuild either.
I'm a bit confused now, I thought we already tried the two patches in
isolation -- but I think
> I noticed the comment does not have the download link. It is:
> http://kernel.ubuntu.com/~jsalisbury/lp1626436/mailine-with-two-commits/
Bazinga! Perhaps unexpectedly, this is a GOOD kernel -- boot speed is
comparable with 4.4, there is no high load after booting any more, and
shutdown is fast
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1642192
Title:
i386 4.9 in -proposed fails to boot in cloud instances
Public bug reported:
I noticed a forever-looping test of linuxinfo on i386 this morning. This
test upgrades the kernel to 4.9 in -proposed; as soon as that reboots,
the VM never comes back. nova console-log shows:
[1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3)
[
ah, just 4 sounds fine indeed. I did test 4.9-rc5 yesterday already (see
comment #57), just not sure if that includes "the" the two commits.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5/
This still shows unchanged behaviour: slow boot and shutdown, and high
load after boot. So unfortunately it didn't magically fix itself :(
--
You received this bug notification because you are a member of Kernel
Packages, which is
Is there something which could help to cut down the bisect? I had a
theory in comment 12 about the plethora of cgroup related uevents.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/e257ef55ce51d7ec399193ee85acda8b8759d930
Still GOOD.
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/1626436
Title:
[4.8
>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/58f8b094e96f12e899bf767fc658c165908065d4
GOOD
--
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/1626436
Title:
[4.8 regression] boot has
>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/1acd010152138644f63d743e165161edc780fc32
GOOD
--
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/1626436
Title:
[4.8 regression] boot has
>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/a0d3c7c5c07cfbe00ab89438ddf82482f5a99422
Still GOOD.
I'm becoming a bit nervous, but I just re-tested 4.7rc1 again and it's
still bad.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I propose to close this. This is clearly fixed with 4.4 on the host, and
rolling that out is covered by bug 1602577.
It can be closed for auto-package-testing either way as our arm64 nova
compute nodes now run 4.4.23.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
**
>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/07b75260ebc2c789724c594d7eaf0194fa47b3be
GOOD
--
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/1626436
Title:
[4.8 regression] boot has
> The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1626436/0efacbbaee1e94e9942da0912f5b46ffd45a74bd
This is a GOOD kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/4a5219edcdae52bfb5eea0dfc2a7bd575961dad7
I do see the files now. Sorry for the delay, travel/sprint and all.
This is a GOOD kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
The verification of the Stable Release Update for makedumpfile 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
The verification of the Stable Release Update for makedumpfile 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
The verification of the Stable Release Update for makedumpfile 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
>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/4a5219edcdae52bfb5eea0dfc2a7bd575961dad7
this is empty
--
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/1626436
Title:
[4.8 regression]
> I built the another test kernel, up to the same commit:
a7fd20d1c476af4563e66865213474a2f9f473a4
This is GOOD.
--
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/1626436
Title:
[4.8
> In the meantime, it might be worthwhile to test v4.9-rc2. It's available from:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc2/
Still slow boot/high load, i. e. BAD.
> I built the another test kernel, up to the same commit:
> 7afd16f882887c9adc69cd1794f5e5723217
That's GOOD.
> I built the first test kernel, up to the following commit:
> 7afd16f882887c9adc69cd1794f5e5723217
Like Florian, the result isn't unambiguous. It for sure boots much
faster than 4.7/4.8 (~ 3s kernel + 5s userspace), but still much slower
than 4.4. But this could be attributed to the #1 issue
Thanks Florian and Joseph! With the two patches it's definitively a lot
better! Boot times without NM and lightdm:
4.4: 1.5s
4.8.0-22 (zesty): 16.8s
4.8.0-26 (Joseph's kernel): 8.4s
So still quite far from what we used to have, but already twice as fast
as the current y/z kernel.
--
You
Second run: Nothing useful at all in "nova console-log" (just the normal
boot up to "login:"), test output tail is
07:32:01 DEBUG| [stdout] nice PASSED
07:32:11 DEBUG| [stdout] null PASSED
07:32:21 DEBUG| [stdout] opcode PASSED
07:32:31 DEBUG| [stdout] open PASSED
07:32:41 DEBUG| [stdout]
The tests (both yakkety and zesty) are still looping, I'm afraid. I
didn't see the "BUG soft lockup" in the one instance I was watching.
There were no obvious kernel call traces in dmesg, and the test output
tail is just:
06:27:14 DEBUG| [stdout]
Killed
DEBUG - Leave sh
ERROR - The command
> 4.7-rc1: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.7-rc1-yakkety/
bad
Thanks Joseph for taking this!
--
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/1626436
Title:
[4.8
> 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
good
> 4.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
good
> 4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
bad
--
You received this bug notification because you are a member of
Hello Chris, or anyone else affected,
Accepted makedumpfile into yakkety-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.0-2ubuntu1.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Description changed:
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
** 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/1635171
Title:
IPv6 Privacy Extensions do not work
Status in linux package in
Indeed we did get a "proper" timeout now \o/
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-yakkety/yakkety/amd64/l/linux/20161018_180219_53396@/log.gz
So closing this one, and using bug 1634519 for the new timeout.
** Changed in: linux
It's better now -- in my local QEMU test the last output is now
14:46:41 DEBUG| [stdout] Test icebp [Ok]
14:46:41 DEBUG| [stdout] Test int 3 trap [Ok]
14:46:41 DEBUG| [stdout] selftests: breakpoint_test [PASS]
and since then (1 hour) it's hung. But now I still can log into ttyS0.
dmesg is almost
The local QEMU run also doesn't time out cleanly:
qqemu-system-x86_64: /build/qemu-3KpUoe/qemu-2.6.1+dfsg/hw/char/serial.c:231:
serial_xmit: Assertion `!(s->lsr & UART_LSR_TEMT)' failed.
autopkgtest [16:03:27]: ERROR: timed out on command "[...]" (kind: test)
autopkgtest [16:03:28]: test
Public bug reported:
Following up to bug 1632252, tests still hang (but not due to the
suspend issue any more). In a local QEMU run:
$ autopkgtest --testname ubuntu-regression-suite linux -- qemu --ram-size=4096
-o /var/cache/martin /srv/vm/autopkgtest-yakkety-amd64.img
[...]
14:46:41 DEBUG|
With the QEMU runner this gets further, but it fails for me with
14:33:01 DEBUG| Running 'git clone
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety
linux'
14:33:01 ERROR| [stderr] Cloning into 'linux'...
autopkgtest [16:02:54]: ERROR: timed out on command "..." (kind:
I am able to reproduce this locally by using the "ssh" runner on a
manually started QEMU instance, instead of the "qemu" runner directly;
so this is much easier to investigate.
First this needs a small new feature in autopkgtest's ssh runner:
After the hang, even SysRq doesn't work (I tried "sync" with Ctrl+A b s
-- Ctrl+A b is the QEMU console key combo for sending SysRq, see Ctrl-A
?)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Confirmed with 4.8.0-040800.201610022031 from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.8/
--
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/1626436
Title:
[4.8 regression] boot
It is still happening. I was running journalctl -f on the testbed while
it ran, and was able to copy the last 9000 lines of scrollback from
tmux.
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632252/+attachment/4762321/+files/journal.txt
--
You
> The udev event is going to fire before the pool is imported.
So how does a pool get imported, what triggers that if it's not block
devices appearing? Whatever does that import, couldn't that start
zed.service then instead of the udev rule?
--
You received this bug notification because you are
Hello John, 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.5 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
The current linux autopkgtests in yakkety are caught in an eternal
"temporary failure" retry loop. They stopped timing out, but in the
middle of the tests they kill sshd.
Tail of test output:
09:01:00 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done
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
This could potentially be related to changes with cgroups -- creating
them did not cause any uevent in 4.4, but with 4.8 they do:
sudo systemctl stop systemd-timesyncd
udevadm monitor -k # in another terminal
sudo systemctl start systemd-timesyncd
KERNEL[393.260769] add
For the record, I tried Joseph's test bisect kernel in bug 1627108, and
this does not fix it, so this is not a duplicate of bug 1627108:
4.4.0-9136 (previous yakkety): 2.849s (kernel) + 4.639s (userspace)
4.8.0-19 (current yakkety): 5.145s (kernel) + 11.825s (userspace)
4.7.0-040700rc3 (from
FTR, I tested #29 which works for Omer, but not for me, so bug 1626436
is not a 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/1627108
Title:
X1Carbon comes to a crawl during
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Tags added: kernel-4.8
--
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/1626466
Title:
[Yakkety] suspend fail and reboot while
Great news! until that happens, is there any harm in leaving 4.8 or
4.4.23 running on the current compute nodes?
--
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/1602577
Title:
[arm64]
Still confirmed with yesterday's 4.8.0-19.21.
--
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/1626436
Title:
[4.8 regression] boot has become very slow
Status in linux package in
I didn't find a simpler reproducer on the CLI, and the systemd test now
does not call rmmod any more, so there's no handle on this any more.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which
I filed bug 1626436 which is similar; I wanted to try
http://kernel.ubuntu.com/~jsalisbury/lp1627108 but that is empty?
--
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/1627108
Title:
My lxd-armhf1 node that is supposedly running on 4.4.23-040423-generic
(on the compute host) has worked fine for the last 13 hours.
--
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/1602577
** 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/1630245
Title:
after starting ubuntu 16.10 -- no keyboard, no mouse
Status in
@Joseph: I don't know what is running on the compute hosts, I don't have
access to those. I suppose that Junien used the kernel you offered in
comment #26, though?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> I believe the zed systemd unit should at the very least be modified
not to start inside containers
That can be done with ConditionVirtualization=!container
> (b) there were an /etc/default/zed which enabled one to disable zed
altogether.
Please don't do that. /etc/default files should never
Both of my instances have been working happily for three days now. SHIP
IT! :-)
Many thanks to the kernel team and Junien!
--
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/1602577
Title:
For the record, I now use two arm64 xenial (4.4) instances on a host
with kernel 4.8, and things are looking really good. See latest posts to
bug 1602577.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
My two arm64 instances had been idle for 16 hours, and after that fully
busy with running tests for about 5 hours. So from my POV, the 4.8
kernel does not have the RCU hang (bug 1531768) any more, or at least
much less noticeable. And apparently the host has survived about 24
hours as well now. I
My two instances have been up and idle for 1:30 hours by now. They don't
have any actual lxd workload due to bug 1628946 (juju deploy currently
fails), but the original hang bug actually happened on idle boxes. Thus,
so far so good :-)
I'll check again tomorrow.
--
You received this bug
> it seems the issue is not 100% solved, but is much much much less
probable.
I confirm this in bug 1626436 -- boot time is a bit faster and load now
"only" ~ 35 instead of ~ 250, but it's still a huge regression compared
to 4.4.
--
You received this bug notification because you are a member of
Unduplicating. This still happens with 4.8.0-17 from the PPA, both the
slow boots and the high load times. It got a fair bit better, though
(load of ~ 35 instead of ~ 250), but still a huge regression compared to
4.4.
** This bug is no longer a duplicate of bug 1626564
4.8 regression: SLAB is
This bug also trivially reproduces in local QEMU, so can easily be
tested locally as well. So thankfully this doesn't seem to be some
Scalingstack quirk.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I confirm that 4.8.0-17 in the PPA boots on Scalingstack instances
again. 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/1627052
Title:
4.8.0-16.17: genirq: Flags mismatch
This seems to break instance boots on scalingstack i386 and amd64
completely. I get thousands of these messages in console-log, and it
never actually boots up. This breaks all autopkgtesting.
** Changed in: linux (Ubuntu Yakkety)
Importance: Medium => Critical
--
You received this bug
*** This bug is a duplicate of bug 1626564 ***
https://bugs.launchpad.net/bugs/1626564
As far as I understand Andy, bug 1626564 is the root cause, thus duping.
** This bug has been marked a duplicate of bug 1626564
4.8 regression: SLAB is being used instead of SLUB
--
You received this
md (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages,
** Also affects: systemd (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/1626737
Title:
[4.8.0-14/ppc64el regression] rmmod
For the record, Andy already has/knows the fix for this.
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1626436
Public bug reported:
Since upgrading to 4.8.0-14, the "storage" autopkgtest of systemd is
broken. This uses scsi_debug to get a test hard drive, which is reset
between the test through unloading/reloading the module. This has worked
fine so far (and still works on amd64/i386), but now regularly
Changing tasks as this is somewhere between unity-settings-daemon and
polkit.
** Package changed: linux (Ubuntu) => unity-settings-daemon (Ubuntu)
** Changed in: unity-settings-daemon (Ubuntu)
Status: Incomplete => Triaged
** Package changed: systemd (Ubuntu) => policykit-1 (Ubuntu)
**
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
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.
** 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.
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 the output?
I don't get this on my ThinkPad X230, I have the opposite problem
(brightness
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 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
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
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
> 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
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)
> 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.
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:
[
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.
1 - 100 of 531 matches
Mail list logo
