Thanks, uploading
** Changed in: crash (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1217474
Title:
basic autopkgtest for crash
Public bug reported:
I tried to suspend and the suspend process failed. There was a blinking
cursor but I couldn't get the system to do anything. Hopefully the
attached logs are good.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-21-generic 3.16.0-21.28
notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380143/+subscriptions
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer
Public bug reported:
This seems to be something chromium-ish which died (my tabs were all
He's dead, Jim, but I don't know where the bug lies.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-21-generic 3.16.0-21.28
ProcVersionSignature: Ubuntu 3.16.0-21.28-generic
** 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/1380788
Title:
BUG: Bad page map in process HTMLParserThrea
** Tags added: kernel-unable-to-test-upstream
** 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/1380143
Title:
[Apple
** No longer affects: xserver-xorg-video-intel (Ubuntu Utopic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1447143
Title:
[SKL, i915_bpo] Rotation doesn't work
Status in linux
** Also affects: xserver-xorg-video-intel (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
-udisks-2.0 - do you have this installed? The '@'
in the test-depends means that you should install the binary packages
produced by this source. Sorry for not being precise enough in the
description.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer
** Tags added: bot-stop-nagging
--
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/1478623
Title:
Kernel oops - blk_update_request: I/O error when running udisks2
force_test_removal test
that, no?
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification because you are a member
Cheers Joseph - it's still broken with that kernel I'm afraid.
--
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/1478623
Title:
[4.1.0 regression] Kernel oops - blk_update_request: I/O
think.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification because you are a member of Kernel
Tried that, still fails
fs: forced removal ... [ 103.792793] blk_update_request: I/O error, dev sdb,
sector 0
[ 103.804099] BUG: unable to handle kernel paging request at 1af23000
[ 103.805253] IP: [c1357db4] __percpu_counter_add+0x14/0xa0
[ 103.806244] *pdpt = 15588001 *pde =
and construct one for you, then you
just need to boot into it and install the stuff to run udisks2's
autopkgtest.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer
Public bug reported:
We noticed that the udisks2 autopkgtest is failing on i386 in the
forced removal test, for example
https://jenkins.qa.ubuntu.com/job/wily-adt-
udisks2/ARCH=i386,label=adt/55/console
I reproduced this locally, on this kernel
ubuntu@autopkgtest:~$ uname -a
Linux
/system-services/org.freedesktop.UDisks2.service
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug
I tried broadcom-sta on xenial
> Setting up broadcom-sta-dkms (6.30.223.271-1) ...
> Loading new broadcom-sta-6.30.223.271 DKMS files...
> First Installation: checking all kernels...
> Building for 4.2.0-19-generic and 4.3.0-2-generic
> Building initial module for 4.2.0-19-generic
> Done.
>
>
** Changed in: linux (Ubuntu)
Status: Fix Released => 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/1581132
Title:
[Xenial] net: updates to ethtool and virtio_net for
When building systemd with this kernel:
In file included from ../src/udev/net/ethtool-util.c:22:0:
/usr/include/linux/ethtool.h: In function ‘ethtool_validate_speed’:
/usr/include/linux/ethtool.h:1321:18: error: ‘INT_MAX’ undeclared (first use in
this function)
return speed <= INT_MAX || speed
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1581132
Title:
[Xenial] net: updates to ethtool and
.
This was noted by Iain Lane when building systemd with this kernel:
In file included from ../src/udev/net/ethtool-util.c:22:0:
/usr/include/linux/ethtool.h: In function ‘ethtool_validate_speed’:
/usr/include/linux/ethtool.h:1321:18: error: ‘INT_MAX’ undeclared (first use
in this function)
return
I showed my build logs. If you want me to help, I'm happy to, I just
need better steps.
Are you saying that broadcom-sta doesn't work for anyone? If that's
right, what am I doing wrong?
(I've unsubscribed ubuntu-sponsors since this is on the list and there
is nothing to sponsor ATM, given my
Public bug reported:
Hello,
We just noticed that systemd's autopkgtests have started failing often
on amd64 for all releases, when run in Canonical's scalingstack cloud.
This is nested KVM I think.
TEST RUN: Basic systemd setup
+ /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic
For me it's enough to boot an instance on an affected lgw01 compute
node, install qemu-system-x86, download a cloud image and run "/usr/bin
/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -drive
format=raw,cache=unsafe,file=zesty-server-cloudimg-amd64.img -machine
accel=kvm -enable-kvm
Also this appears to not reproduce every time :(
ubuntu@autopkgtest:/lib/modules$ find -name wl.ko
./4.10.0-19-generic/updates/dkms/wl.ko
./4.8.0-46-generic/updates/dkms/wl.ko
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in
The function says above it
"# Get the most recent kernel on Debian based systems. This keeps
# into account both the version and the ABI. If the current kernel
# is the most recent kernel then the function will print a null string."
so I think that my previous patch is wrong.
--
You received
Here's my take 2, which was forwarded upstream. Could someone
review/test please?
** Patch added: "lp1661843-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1681566/+attachment/4861224/+files/lp1661843-v2.debdiff
--
You received this bug notification
With my patch, tested like so
- boot a yakkety cloud vm
- install bcmwl-kernel-source virtualbox-dkms ubuntu-release-upgrader-core
from yakkety
- install dkms from comment #19
- do-release-upgrade -d
- [...]
- dkms status
ubuntu@autopkgtest:~$ sudo dkms status
bcmwl,
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Invalid
** Also affects: virtualbox (Ubuntu Zesty)
Importance: Undecided
Status: Invalid
** Also affects: dkms (Ubuntu Zesty)
Maybe IS happens to have a box that's not provisioned yet and you can
borrow? Or you can borrow that one for a bit if lgw01 has some spare
capacity? Or they'll upgrade to the current lts-xenial kernel so we
maybe get lucky. :)
--
You received this bug notification because you are a member of
Public bug reported:
The ADT tests started failing with 4.11.0-11.16 on amd64, i386 and
ppc64el: all the arches we run using qemu over OpenStack. The virtual
machines hang completely.
The last lines in the log are:
12:11:18 DEBUG| [stdout] Test icebp [Ok]
12:11:18 DEBUG| [stdout] Test int 3
blacklist if it doesn't hang.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification because you are
(ah, it was already closed)
--
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/1706283
Title:
ADT tests fail since 4.11.0-11.16
Status in linux package in Ubuntu:
Fix Released
Bug
ok, the test completes without hanging. It fails though:
ubuntu-regression-suite FAIL non-zero exit status 253
but that's not what this bug was about, so closing & unblacklisting.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags added: rls-aa-incoming
--
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/1711358
Title:
20170817 - ISO hangs on boot on qemu with splash screen enabled and
qxl graphics driver
Just a heads up - this apparently became much harder for me to reproduce
at will. We're still seeing it in actual workloads but I'm having
trouble recreating manually.
My current strategy is to start stress-ng on a number of machines and
then constantly reboot them, with the idea that this will
OK a few days ago apw pointed me at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.13.8/ which is the mainline kernel that the artful-
proposed one I identified as bad is based on.
I ran 35 instances and rebooted them 30 times - all successful. So I
think that says this kernel is good.
Will
eck candidate kernels. Feel free to
throw some more at me if you want to bisect.
(I think IS took some of the slower machines out of rotation so the
problem might become slightly harder to reproduce - definitely is still
happening though.)
--
Iain Lane [ i...@oranges
s, on lcy01 (the busy
cloud that exhibits this problem).
I started 34 (17 × 2 in two runs - that's all I could squeeze in before
I hit my quota) instances, and they were all good. This isn't definitive
proof, but it looks like that kernel might be good.
Cheers,
--
Iain Lane
't
reproduce the problem - it probably wasn't under enough stress anyway.
> Crossing fingers for jsalisbury's hope that 4.14 might already have a
> fix.
Right now I'm trying to build a new cloud image with this kernel that I
can try.
--
Iain Lane [ i..
20 instances, all good.
Maybe I should try one that we think is 'bad' to confirm that the way
I'm doing this is actually capable of reproducing the issue? If you
think that's sensible, could you recommend me a kernel to try?
--
Iain Lane
Public bug reported:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn and
backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the
** Attachment added: "good run console-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+attachment/5005465/+files/laney-test14.log
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
I tried 28 (then my quota ran out) xenial guests BTW and none of those
failed.
--
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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG:
** Attachment added: "bad run console-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+attachment/5005464/+files/laney-test25.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Oh also see https://bugs.launchpad.net/ubuntu/+source/linux-
hwe/+bug/1713751 which has some superficially similar symptoms (cpu
stuck on shutdown).
** Description changed:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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/1770271
Title:
VegaM support
Status in amd:
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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/1714178
Title:
Triple 4K monitor display
** Tags removed: rls-bb-incoming
--
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/1817738
Title:
Can't change virtual terminal when auto-login is enabled
Status in gdm3 package in
** Also affects: gnome-control-center (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: upower
as if you revert to kernel
5.0 it goes away. So I'll reassign this bug to linux - maybe we can find
out when it was introduced if the kernel team can help us to bisect.
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer
Actually, I'm not certain it is a duplicate of that one - this bug I
think is a regression in eoan due to some change in the kernel between
disco and eoan. Perhaps they are related though.
When I'm back from travelling I'll try to do a little bit of
investigation (but I don't know anything about
** No longer affects: 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/1833916
Title:
USB-C to HDMI converter is not working with thunderbolt port
Status in linux package in
would. I think we just need the dependency. Thanks for
handling this!
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You
awesome, thanks for following up!
--
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/1852122
Title:
ocfs2-tools is causing kernel panics in Ubuntu Focal
(Ubuntu-5.4.0-9.12)
Status in
Public bug reported:
We are in the process of switching ubuntu-drivers to installing linux-
restricted-modules versions of NVidia drivers when it can, but this
fails when Ubiquity invokes ubuntu-drivers, like:
Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
I don't think there's anything to fix in udisks2 here, since it's just
using the filesystems that are available; invalidating the task.
Perhaps you're arguing for exfat-fuse to be removed from the archive?
See comment #3.
** Changed in: udisks2 (Ubuntu)
Status: Incomplete => Invalid
--
please re-add the tag if it's not
--
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/1881699
Title:
No analog output
Status in linux package in Ubuntu:
Confirmed
Status in pulseaudio
there's an updated kernel in that bug, jibel can you test it please to
confirm if this is a dupe or not?
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
w
** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu Focal)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu Focal)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: gnome-session (Ubu
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Groovy)
Importance: Undecided
I don't see the same problem on the Focal ISO - do we need to fix this
in Focal?
** Changed in: alsa-lib (Ubuntu Focal)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
ah I see, OK - I will upload, thanks!
can you update the test case to say that this version of alsa-utils is
needed please? maybe provide a PPA link for people to install it with,
until that is accepted into focal?
** Changed in: alsa-lib (Ubuntu Focal)
Status: Incomplete => Fix Committed
** Also affects: gnome-control-center (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also
The point for me is that we should be trying to avoid taking on
indefinite technical debt (patches that have to be rebased forever).
It's "fine" to include them ahead of any upstream schedule if we need to
for hardware enablement, but we do need to have plans to make this be a
non permanent
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh
New shim-signed is now on the latest images (20201021).
I'm still not clear what happened when enabling Broadcom from the
installer since it all looks fine to me. Perhaps you could try and let
us know what doesn't work with detailed steps to reproduce? (but
hopefully it does work)
--
You
Removing 455 from groovy to groovy-proposed to fix (2).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh groovy
Yeah, fossfreedom, can you tell us what you ticked on the 'install third
party drivers' page?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation -
I think the second part (apt install not showing the prompt on next
boot) is fixed with shim-signed 1.45 as indicated by Andy in comment #8.
But I'm not quite sure about your initial part where the installer
didn't do the same. I can make that happen if I tick to install
proprietary drivers and
laney@dev> ./change-override -S -c main -s hirsute libbpf
Override component to main
libbpf 0.3-2 in hirsute: universe/misc -> main
libbpf-dev 1:0.3-2 in hirsute amd64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute arm64: universe/libdevel/optional/100% -> main
libbpf-dev
Are you saying that the live session worked and then the installed
system did not?
If that's right, we need the contents of /var/log/installer, please, to
see what the installer did.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I've just noticed a few failing with "Synchronous Exception at
0x984FA4A8" instead of the IRQ Exception seen earlier.
--
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/1926955
Title:
> I'll file a ticket with IS for their input...
Canonical staff can see this at rt #130839
--
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/1926955
Title:
[VMs on] arm64 eMAG system
ack alone *may* be possible, we
can check that (the cloud archive doesn't contain edk2 though). It's
also running Launchpad buildds though. I would expect reluctance to do
this from their side due to the risks and, annoying as it is, think we
should plan on identifying & doing the backports. Sor
** Summary changed:
- arm64 eMAG system often failng to reboot with "IRQ Exception at
0x9BC11F38"
+ [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at
0x9BC11F38"
--
You received this bug notification because you are a member of Kernel
Packages, which is
FTR, I just checked with Canonical IS and the affected host systems are
running Xenial.
(We also have some different hardware which is running the same versions
too and doesn't suffer from this bug, so I do suspect it is somehow hw
specific.)
--
You received this bug notification because you
apport information
** Tags added: apport-collected ec2-images impish
** Description changed:
We recently installed some new arm64 Ampere eMAG hardware in the
ScalingStack region which we use to run autopkgtests.
Guests (currently impish VMs on OpenStack) which we spawn often fail to
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494393/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494394/+files/Lspci.txt
--
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/1926955
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494395/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494396/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494398/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494399/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494397/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494400/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I captured the console log when the bug happens, was hoping there would
be something interesting just before the exception starts spamming the
console, but sadly not.
[ OK ] Finished Reboot.
[ OK ] Reached target Reboot.
[ 17.856242] reboot: Restarting system
IRQ Exception at
** Description changed:
We recently installed some new arm64 Ampere eMAG hardware in the
ScalingStack region which we use to run autopkgtests.
Guests (currently impish VMs on OpenStack) which we spawn often fail to
reboot, repeating this over and over:
- IRQ Exception at
Public bug reported:
We recently installed some new arm64 Ampere eMAG hardware in the
ScalingStack region which we use to run autopkgtests.
Guests (currently impish VMs on OpenStack) which we spawn often fail to
reboot, repeating this over and over:
IRQ Exception at 0x9BC11F38
(stand
Would have preferred this to come much earlier, but sounds like
something we need to do ...
Please make sure to keep an eye out for bugs.
I'll accept, thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: rls-ff-incoming
--
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/1873052
Title:
Showing two cursors after login
Status in gnome-shell package in Ubuntu:
Confirmed
** Tags removed: block-proposed block-proposed-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv
94 matches
Mail list logo
