Do I have to downgrade my system from Dingo to Cosmic in order to test
this in Cosmic, to keep my bug from being closed?
May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this
I am using a ThinkPad E585, which has a Raven Ridge APU, and the problem
still exists for me in kernel 4.20.15.
`lspci` shows that my USB controllers' device IDs are the ones in the
list of devices for which the fix is applied (15e0,15e1), but I am still
receiving the same error and no USB devices
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1756700/+attachment/5246651/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs
I fail to see how it is not the same issue; I am receiving the same
error that the commit (621faf4f) claims to fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1756700
Title:
Ryze
The kernel boot log is listed as attached file here in case someone is
interested.
** Attachment added: "RV2 Boot Log"
https://bugs.launchpad.net/amd/+bug/1822267/+attachment/5250650/+files/rv2-boot-log.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: a
The original bug report was on PowerKVM (ppc64el qemu). In testing that
it was okay to revert this wholesale in both kmod and kernel, did anyone
test POWER?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
I'm rejecting the kmod upload in the disco queue until the above comment
is addressed, so we don't get into a revert war.
--
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/1795857
Title:
en
What was the host system (ie: what version of qemu)? I want to be sure
this works going back as far as we support (so, trusty hosts).
--
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/1795857
nalog Microphone (priority 150, latency
offset 0 usec, available: unknown)
properties:
I'm going to put it back the way I had it (remove the deb and reinstate
the quirk).
Is there anything else I can test? Or any more DMI info you would like?
Is there som
Here's the whole `sudo dmidecode` output (attached).
** Attachment added: "Output of sudo dmidecode for the LattePanda"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+attachment/5258402/+files/dmidecode.txt
--
You received this bug notification because you are a member of Kern
OK, this second deb seems to solve my problem! The headphone jack state
is detected correctly without the quirk! 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/1824259
Title:
Hea
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
Public bug reported:
Bluetooth devices don't reconnect after sleep. Includes BT audio
receiver and BT Keyboard. One way to repro is to switch BT pairing on
multi-pairing keyboard, then switch back to Ubuntu. The BT connection
state will be very confused, keyboard will not work.
Another way to r
** Description changed:
- Bluetooth devices don't reconnect after sleep. Includes BT audio
- receiver and BT Keyboard. One way to repro is to switch BT pairing on
- multi-pairing keyboard, then switch back to Ubuntu. The BT connection
- state will be very confused, keyboard will not work.
+ Blue
** Description changed:
Bluetooth devices don't reconnect after sleep, or something along those
lines.
- Includes BT audio receiver and BT Keyboard. One way to repro is to
- switch BT pairing on multi-pairing keyboard, then switch back to Ubuntu.
- The BT connection state will be very conf
** Also affects: maas/2.7
Importance: Undecided
Status: New
** Changed in: maas/2.7
Status: New => Fix Committed
** Changed in: maas/2.7
Importance: Undecided => Critical
** Changed in: maas/2.7
Assignee: (unassigned) => Lee Trager (ltrager)
** Changed in: maas/2.7
** Tags added: fecal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status in Linux:
New
Status in linux package in U
Public bug reported:
Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing
CONFIG_NLS_ASCII in the arm64 kernel build options.
This option is enabled on the other kernel builds but somehow was overlooked on
arm64 appears to affect our ability to access logs via journalc
@fginther
I opened this bug report on behalf of @brentk4 from a support ticket.
Please refer to the kernel that referenced in #4.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881
** Changed in: maas
Importance: Undecided => Critical
** Changed in: maas
Assignee: (unassigned) => Lee Trager (ltrager)
--
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/1881821
Tit
** Also affects: maas/2.7
Importance: Undecided
Status: New
** Also affects: maas/2.8
Importance: Critical
Assignee: Lee Trager (ltrager)
Status: Triaged
** Changed in: maas/2.8
Milestone: None => 2.8.0rc1
** Changed in: maas/2.7
Milestone: None => 2.7.2
** Chan
Thanks for the background info, in 2.7 MAAS started modelling the speeds
of interfaces and links, so I expect that 2.6 will not have the same
problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
$ lsinitramfs /boot/initrd.img-5.4.0-14-generic | grep dm-crypt
1 $
https://paste.ubuntu.com/p/bDq66dMjYM/ for the full list
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Tit
$ lsinitramfs /boot/initrd.img-5.4.0-9-generic | grep dm-crypt
usr/lib/modules/5.4.0-9-generic/kernel/drivers/md/dm-crypt.ko
Confirmed it is there for -9
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.la
** Summary changed:
- Failure to boot with LVM + encrypted root disk
+ dm-crypt missing from initiramfs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Title:
dm-crypt missin
*** This bug is a duplicate of bug 1864360 ***
https://bugs.launchpad.net/bugs/1864360
** This bug is no longer a duplicate of bug 1862215
dm-crypt missing from initramfs
** This bug has been marked a duplicate of bug 1864360
cryptsetup-run is transitional package, but removing it also r
*** This bug is a duplicate of bug 1864360 ***
https://bugs.launchpad.net/bugs/1864360
Ah, suspect this is actually an incident of bug 1864360, confirmed I do
not have cryptsetup-initramfs installed, and purged all transitional
packages
** Summary changed:
- dm-crypt missing from initiramfs
I've fixed my problem by applying the kernel suggested in [1]
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/18369
The testcase here doesn't seem to be working (or, rather, failing) for
me, which makes it harder to investigate this. It passes on both sid
and eoan for me:
(sid-amd64)root@nosferatu:~# dpkg -l \*klibc\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Hal
Ah-ha. If loop0 is in use, then the test-case appropriately fails in
both unstable and eoan, which is comforting, as I didn't look forward to
figuring out why this works in Debian (it doesn't).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Are there any plans to correct the Xenial's package?
** Changed in: zfs-linux (Ubuntu Xenial)
Status: Confirmed => Incomplete
--
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/1742
Hello Andreas, or anyone else affected,
Accepted zfs-linux into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.1-1ubuntu14.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
ht
I completely missed the verification ping here in the sea of other
kernel bug mail that I get. Will work with the LP team to get this
verified as quickly as I can, but if you need to make a revert/ship call
before I can, the patches should be pretty harmless even if they don't
fix the bug, so I'd
While there may be arguments for synthesizing UUIDs in various fs
drivers, or creating them in the first place in fs-creation tools, I
agree that if overlayfs has a hard dependency on UUIDs for uniquely
identifying layers, it needs to fill in the gaps where the previous
tools/drivers failed to prov
I didn't mean actually random, and I think clock-based would be entirely
fine, but my paranoia about stacking two things with identical
superblocks might be just paranoia too. I dunno.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Hello manuel, or anyone else affected,
Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Hui, or anyone else affected,
Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello AaronMa, or anyone else affected,
Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Seth, or anyone else affected,
Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
With previous xenial kernels:
XFAIL: nptl/tst-signal6
XFAIL: nptl/tst-thread-exit-clobber
XFAIL: signal/tst-minsigstksz-1
XFAIL: signal/tst-minsigstksz-2
XFAIL: signal/tst-minsigstksz-3
XFAIL: signal/tst-minsigstksz-3a
XFAIL: signal/tst-minsigstksz-4
XFAIL: support/tst-xsigstack
With the kernel i
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
When will be available fix in packages from regular distribution -
applied with apt update/upgrade?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Confirm that solution from #25 works and total_mem=3072 can be removed
from config.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1848790
Title:
USB not working under arm64 on Pi
Hello Timo, or anyone else affected,
Accepted libdrm into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.99-1ubuntu1~18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
The autoremoval part should be fixed if you install from a more recent
image.
--
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/1847927
Title:
Upgrading of 20191010 installed on ZFS wil
20191012 is the only one where this is expected to work, however for
other hilarious reasons, you need to boot in the live session, upgrade
to ubiquity from eoan-proposed (19.10.20), then run the installer.
This should all be in better shape with tonight's images when we spin
them (expected serial
This fix is in the latest eoan kernel on the live repository. Just do
standard update and reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1846016
Title:
Intel Wireless AC 3168
I also experience this issue; you can find my dmesg log (with
usbcore.dyndbg=+p) attached.
** Attachment added: "dmesg.usbcore.dyndbg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+attachment/5314066/+files/dmesg.usbcore.dyndbg.log
--
You received this bug notification be
Easy fix that worked for me (on Mint 19.3): in the Driver Manager, an
older Nvidia driver was selected (390). I manually changed it to 435,
and on reboot I had my 2nd monitor back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
There does appear to be a work around here:
https://wiki.archlinux.org/index.php/HP_Spectre_x360_13-4231ng#Brightness_/_backlight
It requires bc and inotify-tools.
The workaround is for a long running program to listen for changes to
/sys/class/backlight/intel_backlight
calculate the right lumi
An even better script so that all connected displays have their
brightness adjusted
#!/bin/bash
#-
# /usr/local/bin/brightness
# be sure this file is executable
#-
back
Setting total_mem=2048 in /boot/firmware/usercfg.txt allowed me to boot
Pi4 4GB with 19.10 64bit with working USB. Of course I have less RAM
now, but working USB.
Likely the above patch will fix it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Setting total_mem=2048 or 3072 in /boot/firmware/usercfg.txt allowed me
to boot Pi4 4GB with 19.10 64bit with working USB. Of course I have less
RAM now, but working USB.
Likely the above patch will fix it.
--
You received this bug notification because you are a member of Kernel
Packages, which
Hello Christian, or anyone else affected,
Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: verification-needed-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1848848
Title:
Firmware for Radeon RX5700 (navi10) missing / boot failure
Status in linux
@sforshee: Given the severity of this issue, and that it's only adding
new files, I'm inclined to say we fasttrack the release, but I'd also
like to see a follow-up upload that includes the missing files the
drivers reference (if they exist), or patch the drivers to stop
referencing them (if they d
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being 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
Same with the ASUS Zenbook UX333FA on Ubuntu 19.10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status in Linux:
N
Same on dell Latitude E7470, only appeared after upgrading to eoan.
Still present after installing backport-iwlwifi-dkms
Without backport-iwlwifi-dkms iwconfig showed power management on.
After backport it shows no results.
Wifi still functions but crashes randomly.
--
You received this bug no
I can confirm this bug in 18.04. I had the issue a couple of weeks ago,
then everything suddenly worked, and now I have the problem again. I
restarted my pc multiple times, reconnected to my usb-bluetooth adapter,
tried every slot, rebootet bluetooth device, reinstalled headset driver,
but I don't
It turned out that there was a firmware bluetooth issue with my Broadcom
device. I found the issue with `dmesg | grep -i bluetooth ` and I could
fix it by simply downloading the missing firmware from
https://github.com/winterheart/broadcom-bt-firmware - now everything
works.
--
You received this
glibc in eoan building against the supposedly-fixed kernel is hitting
these issues again on i386 testsuites. Did we break it again?
https://launchpad.net/ubuntu/+source/glibc/2.29-0ubuntu3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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
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
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
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
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
Confirmed in production as well, eoan's glibc now builds again on x86.
--
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/1834315
Title:
Revert x86/vdso linker changes from #1830890 as this
Historically, this test had a timeout of 5s. In more modern glibcs, it
uses the default of 20s. It's probably reasonable when SRUing or doing
security updates to bump up that timeout.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
The patch is tested and verified.
--
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/1831846
Title:
[raven] fix screen corruption on modprobe
Status in linux package in Ubuntu:
Incomplete
** Changed in: glibc (Ubuntu Eoan)
Status: Triaged => 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/1836064
Title:
glibc needs an update for linux-5.2 kernel headers
Public bug reported:
This seems to have been fixed in 4.15 (finally), but is still an issue
in the 4.4 kernel used on our builders, and possibly others as well
(needs investigation).
The original Debian bug report linked has more info, as well as the
patchset on lkml at https://lkml.org/lkml/2018
Confirmed that this is fixed in 4.15 as of (at least) 4.15.0-62-generic.
--
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/1844155
Title:
arm64: sigaltstack fails with MINSIGSTKSZ for 32-bi
Public bug reported:
The `perf` profiling tool, and a few other tools, are part of the Linux
project. Ubuntu gets them from a package specific to the running kernel
version, and uses wrapper scripts installed as e.g. /usr/bin/perf to
dispatch to the appropriate version for the running kernel. This
I reported this bug from this container running on an Ubuntu-based host
where I built it. When I tried to run ubuntu-bug in the container on the
host where I actually encountered the problem, it refused to report the
bug due to... a non-Ubuntu kernel!
--
You received this bug notification because
There's not really an applicable Ubuntu kernel to collect logs for; the
problem is only apparent in a container on top of a host that doesn't
run a recognized kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a memb
Public bug reported:
Testing the latest arm64 18.04 mini ISO on a raspberry pi 3, I found the
internal sd card reader was not recognised. This is the main storage on
a pi. Manually extracting the mmc/host/bcm2835 module from the extras
package and insmod'ing it got it working on the d-i installe
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: bionic
** Tags added: arm64
** Tags added: 18.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/176146
Background info on mmc modules in raspberry pi -
https://www.raspberrypi.org/forums/viewtopic.php?f=71&p=1298290#p1298290
--
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/1761468
Title:
De
This is very much a bug in nvidia-graphics-drivers-340. One can debate
if software-properties should or shouldn't purge (though traditionally,
the argument was that silent frontends shouldn't purge because the user
hasn't explicitly asked for that), but if a removed package's unpurged
conffiles ca
Thanks Paolo and Seth for looking into this and the patches. There's a
few things that could be done to make life on the pi better. For
example, are there any plans to add support for the relatively new pi3b+
to bionic? Adding efi stub to the raspi2 kernels would be great. The
upstream and down
Public bug reported:
SRU Justification
Impact: On s390, an incorrect pointer being copied from the kernel to
userspace breaks stack unwinding.
Fix: One-line change from upstream. Only needed for 4.15+.
Test Case: The glibc testsuite contains test cases, which currently fail
with 4.15.
Regressi
I've created a new bug for the raspi2 server image - Bug #1765154
--
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/1566468
Title:
systemd-modules-load.service: Failing due to missing modul
Public bug reported:
Due to the fact that we are no longer guaranteed to produce an initrd
from our postinst, flash-kernel can fail on upgrade when it attempts to
operate (incorrectly, because it's not smart) on the wrong kernel, and
fails to find the initrd we've not yet made.
This is worked aro
Public bug reported:
I went to boot my computer today and it wouldn't boot.
I get an "Unable to handle kernel NULL pointer dereference" message
during the boot process, and, a bit after that, a message from the
kernel watchdog about CPU #0 being stuck. Then the boot process stops
completely.
I w
The drive that was giving me this problem failed. I got a replacement
(which is notionally the same model, with the same USB ID 0781:5581),
and, on kernel 4.15-22, under Xen, the new drive seems to work fine in
USB 3 ports.
However, I also tested with the latest v4.17 kernel from the given link
(4
This also affects the mainline kernel build 4.17.0-041700.201806041953
that I was testing for another bug.
I've attached a photo of the screen with the issue occurring, in that
version.
Booting not under Xen seems to work around the issue, and the system
comes up, but that's not useful for me bec
I updated my BIOS and tested the -24 kernel, as was recommended. It
definitely doesn't work any better. It still has the null dereference
problem, and then it prints a bunch of smp_call_function_too_many errors,
apparently forever.
On Tue, Jun 19, 2018, 08:11 Joseph Salisbury
wrote:
> Can you se
Hello Seth, 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.20 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
root@stilson:~# dpkg -l linux-firmware | grep ^i
ii linux-firmware 1.157.19 allFirmware for Linux kernel
drivers
root@stilson:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin
101 - 200 of 2749 matches
Mail list logo
