** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
- Removing the non-existent 'co
** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
Removing the non-existent 'co
** Changed in: linux (Ubuntu)
Importance: Medium => High
--
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/1879987
Title:
kernel get stuck at boot if specified 'console=ttyS* ' doesn't e
from dmesg (took from virsh dump)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=ttyS4
..
[1.053683] Warning: unable to open an initial console.
--
You received this bug notification because you are a member of Kerne
I don't know yet if related, but I also observed the following:
syslog:May 21 17:25:27 ubuntu kernel: [0.00] random: get_random_bytes
called from start_kernel+0x99/0x4fd with crng_init=0
syslog:May 21 17:25:27 ubuntu kernel: [1.902484] random: lvm: uninitialized
urandom read (4 bytes
I observed the random kernel spew on my reproducer but I also want to
add that it was also noticed on my VMware impacted contact who brought
this up to my attention at the first place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Related public bugs found here and there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
https://github.com/systemd/systemd/issues/15783
https://github.com/systemd/systemd/issues/15656
** Bug watch added: Debian Bug tracker #960355
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96
** Summary changed:
- kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist.
+ machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification becaus
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Guilherme G
it and problem persisted.
- Eric
--
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/1879987
Title:
machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
Status
** Tags removed: sts-sponsor-mfo
** Tags added: sts-sponsor-mfo-and-slashd
--
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/1869465
Title:
Kdump-Tools: Makedumpfile Failed, Falling Back To
27;
makedumpfile (1:1.6.7-2)
# arch/arm64.c
84 #define PMD_SECTION_MASK((1UL << 40) - 1)
- Eric
--
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/1869465
Title:
Kdump-
Disregard my last comment (#15) ...
I was confused for a second between :
#define PHYS_MASK ((1UL << PHYS_MASK_SHIFT) - 1)
#define PMD_SECTION_MASK((1UL << 40) - 1)
so PMD_SECTION_MASK fix is not found in debian yet.
I'll sponsor the debdiff over the
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch which his little
current friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch to match his current
little friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch to match his current
little friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu Groovy)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Groovy)
Assigne
I have a Dell XPS 15 9570 with the same issue. This includes the slider
in the top panel menu, in system settings and when using the keyboard
shortcuts. When using the keyboard shortcuts, the OSD shows and the bar
moves but the screen brightness is not changed.
System:Host: rex Kernel: 5.4.0-1
mited.
I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE
kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly:
eric@eric-8700K:~$ zpool status
pool: storagepool1
state: ONLINE
scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17
I encountered this recently under Ubuntu 16.04.5 with Linux
4.15.0-65-lowlatency with an AMD A8-3870k APU. In the most recent case
the machine was fine for nearly a week until I was reading a large
amount of data off a usb stick. By moving my mouse receiver to a USB 3.0
port I was able to make the
Would it be worth it to include the changes into Ubuntu generic kernel
and derivative Ubuntu kernels as well ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848739
Title:
[linux-
In Openstack Newton (linux-kvm) with Centos 7 (latest cloud-image) with
cloud-init 19.3, the delay is observed. I think this is due to the
version that Centos ships with for python (2.7.5).
The problem is at the init-local stage. https://github.com/canonical
/cloud-init/pull/103
here is the att
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux package in Ubuntu:
Incom
ere current state
is "unused" unless I missed something. IMHO they should produce
consistent behaviour if 'unused' no ?
- Eric
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
It then might be a problem with "/dev/loop-control" device node. Which
dynamically find or allocate a free device, but also add and remove loop
devices from the running system.
# drivers/block/loop.c
2090 static void loop_remove(struct loop_device *lo)
2091 {
2092 del_gendisk(lo-
Agreed with your comment #11
will start a discussion with the linux-block maintainer.
--
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/1856871
Title:
i/o error if next unused loop device
We see this in 4.19.y when using scsi_mod.use_blk_mq=y . Marcus, are
you using blk-mq?
Jump in on this thread, or I can cc you if you send me an email:
https://lore.kernel.org/linux-block/20190925200138.ga20...@redhat.com/
-Eric
--
You received this bug notification because you are a member
Ok so in fact the inconsistency is due to "parted" that will try to
probe devices iff the given block device return informations from
stat(), regardless if the block device is available or not.
Seems like the only trigger/criteria is the stat() return. Since the
loop device stat doesn't clear/rese
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to smarter and not only based is detection only on
stat() ?
Let's circle back on Jan 2020.
** Also
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to be smarter and not only based is detection on stat()
to assume if its a legit device or not to be
/bugs/1860182
Title:
zpool scrub malfunction after kernel upgrade
Status in zfs-linux package in Ubuntu:
Triaged
Bug description:
I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE
kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly:
eric@eric-8700K:~$ zpool s
I reproduced the behaviour using 5.5 upstream kernel by:
1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device
trace_pipe reveal the following:
"umount-1850 [000] 471.727511: loop_release_xfer <-__loop_clr_fd"
As cascardo menti
I reproduced the behaviour using 5.5 upstream kernel by:
1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device
trace_pipe reveal the following:
"umount-1850 [000] 471.727511: loop_release_xfer <-__loop_clr_fd"
As cascardo mentione
Public bug reported:
I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE kernel
(5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly:
eric@eric-8700K:~$ zpool status
pool: storagepool1
state: ONLINE
scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24
Title:
zpool scrub malfunction after kernel upgrade
Status in zfs-linux package in Ubuntu:
Triaged
Bug description:
I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE
kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly:
eric@eric-8700K:~$ zpool status
-26-generic #28~18.04.1-Ubuntu) and it ran properly:
eric@eric-8700K:~$ zpool status
pool: storagepool1
state: ONLINE
scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020
config:
NAME STATE READ WRITE CKSUM
progress, despite saying 100.00% done. It did not calcualte a
time estimate, saying the rate was slow, however, it did complete after
3h36 (so fast than it used to on kernel 4.15).
eric@eric-8700K:~$ zpool status
pool: storagepool1
state: ONLINE
scan: scrub repaired 0B in 3h36m with 0 errors on Sat
Ok, I got a question for all the interested folks out there;
What is we were to have a test case that run init-local and fails if
random gets imported?
I'm looking at how this could be done, but that test could link to this bug and
have people realise that they need to be careful about the rand
testing phase of bionic-proposed in a couple of weeks.
- Eric
** Tags added: sts
--
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/1832138
Title:
Login screen never appears on vmwgfx using
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in wh
kernel-team archive ML:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101489.html
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland,
Todd, The fix will land in the next kernel cycle.
--
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/1832138
Title:
Login screen never appears on vmwgfx using bionic kernel 4.15
Status in l
Just got the 2 required ACK from kernel team for the patch I have submitted.
Everything looks good for the patch to be part of the next kernel cycle as
described in previous comment.
- Eric
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
The testing phase where the kernel will land in bionic-proposed pocket is due
around :
08-Jul - 19-Jul Bug verification & Regression testing
This is where I'll need you guys to test the proposed kernel and confirm
it still work as expected for you.
- Eric
--
You received this bug not
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1832138
Title:
Login screen never appears on vmwgfx usi
Signature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: eric 1809 F pulseaudio
/dev/snd/controlC0: eric 1809 F..
COMMAND
/dev/snd/controlC1: eric 1809 F pulseaudio
/dev/snd/controlC0: eric 1809 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 19 20:50:52 2018
HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691
InstallationDate: Installed on 2017
cVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: eric 1809 F pulseaudio
/dev/snd/controlC0: eric
this bug also affects dell inspiron-13-7352
i had a problem where i needed to update my bios, but this bug kept me
from being able to make any bios changes until i installed the older
kernel. obviously a bug with the kernel that came with 17.10.
** Tags added: dell-inspiron-13-7352
--
You recei
tu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: eric 1809 F pulseaudio
/dev/snd/controlC0: eric 1809 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 19 20:50:52 2018
HibernationDevice: RESUME=UUID=8b3
supposed to be manipulated by the driver. And we can safely assume that most
current kernel model drivers do keep this updated.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
*
https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718
** Description changed:
- Environment: The guest VM is using a canonical ubuntu image, and the
- eth0 is a virtio-net adaptor, running on DPDK.
+ It has been brought to my attention the following :
+
+
For qemu and upstream DPDK, support is present for the
VIRTIO_NET_F_STATUS capability, and as such should not experience the
"UNKNOWN" operstate issue; jvosburgh checked qemu and don't see this
issue when running it, but haven't set up DPDK to verify it's behavior.
The opencontrail vrouter source
ael S. Tsirkin
Signed-off-by: David S. Miller
---
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
*
signed) => Eric Desrochers (slashd)
--
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/1761534
Title:
"ip a" command on a guest VM shows UNKNOWN status
Status in linux package in Ub
Patch has been submitted to the Ubuntu kernel team ML
Subject:
[PATCH][SRU][B,A,X,T] virtio-net: Fix operstate for virtio when no
VIRTIO_NET_F_STATUS
- Eric
** Description changed:
- It has been brought to my attention the following :
+ It has been brought to our attention the following bug
** Description changed:
+
+ [Impact]
+
+ "ip a" command on a guest VM shows UNKNOWN status.
+
+ [Test Case]
+
+ * Environment : Running a guest VM with a virtio-net adaptor interface,
running on DPDK.
+ * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example:
+
+ 2: eth
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu.
https://bugs.launchpad.net/bugs/1721988
Title:
Ubuntu 17.10 full disk
** 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/1771301
Title:
Setting ipv6.disable=1 prevents both IPv
The patch has received 2 ACKs from Ubuntu kernel team and has been
applied to cosmic master-next branch and unstable master branch 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/173
** Description changed:
[Impact]
It has been brought to my attention that VMware Guest[1] randomly crashes
after moving the VMs from a VMware "5.5" env to VMware 6.5 env.
Notes:
* The crashes wasn't present in VMware 5.5 (with the same VMs). Only started
to happens with Vmware 6.5
*
APPLIED: [PATCH][XBC] UBUNTU: [Debian] hyper-v -- Ensure that hv-kvp-
daemon.service starts before walinuxagent.service
to xenial/master-next and bionic/master-next
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
>From Peter's description of the problem I guessed that it was wireshark
setting promiscuous state on the virtual usbmon interface that caused
the keyboard to go back to working state, which I knew should also be
possible via tcpdump -i usbmon3 where usbmon3 is the interface that
corresponds to the
The trusty-proposed package ^ :
# apt-get changelog linux-image-3.13.0-158-generic
...
* BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
(LP: #1780470)
- VSOCK: sock_put wasn't safe to call in interrupt context
- VSOCK: Fix lockdep issue.
- VSOCK: Detac
r this same impacted user for
about 4 weeks without crashes or unwanted situation on VMware < & > 6.5.
- Eric
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, whi
** Changed in: debian-installer (Ubuntu Trusty)
Status: New => In Progress
** Changed in: debian-installer (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: debian-installer (Ubuntu Trusty)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received th
Sponsored for Trusty.
The 4.4.0-134 is indeed containing the required commits mentioned above
:
$ git log ...
67f5d9c sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC
4a76ed3 sfc: make TSO version a per-queue parameter
$ git describe --contains 67f5d9c
Ubuntu-lts-4.4.0-134.160_14.04.1~320
FTBFS on Trusty amd64 arch in investigation
[Build #15318223] amd64 build of debian-installer 20101020ubuntu318.44 in
ubuntu trusty PROPOSED
--
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/
According to SRU it may be related to :
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1708245
cyphermox will need to be involve.
--
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/178315
Are you guys still experiencing the issue ?
--
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/1540045
Title:
BUG: Bad rss-counter state mm:88010af5cb00 idx:1 val:512
Status in linux pa
The kernel in -proposed (4.15.0-23-generic) doesn't solve the problem.
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Shame on me! I think I've missed an `apt update`. Indeed kernel
4.15.0-24-generic is there an DOES solve the problem. Sorry.
--
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/1752772
Title:
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because
** Description changed:
+ [Impact]
+
+ When booting with ipv6.disable=1, vxlan tunnels will fail to initialize
+ with the error "vxlan: Cannot bind port 4789, err=-97" which is
+ EAFNOSUPPORT.
+
+ Expected result is that vxlan tunnels work when ipv6 is disabled.
+
+ # Tested on :
+ Description:
> https://people.canonical.com/~khfeng/lp1752772-r8169-intx/
It works for me.
--
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/1752772
Title:
r8169 ethernet card don't work after returnin
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eric 6073 F pulseaudio
/dev/snd/seq:timidity 1500 F timidity
Date: Thu Sep 6 09:48:42 2018
ErrorMessage: package linux-image-extra-4.4.0-131-generic is not ready for
configuration
ic 4.4.0-131.157
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eric 6073 F pulseaudio
/dev/sn
** Tags added: sts
--
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/1791758
Title:
ldisc crash on reopened tty
Status in linux package in Ubuntu:
Confirmed
Bug description:
The follo
** Changed in: linux (Ubuntu)
Milestone: trusty-updates => None
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
The following Oops was discovered by user:
[684766.39] BUG: unable to handle kernel paging reque
And original commit adding the infrastructure linked to this thread ;)
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=3a9b76fd0db9f0d426533f96a68a62a58753a51e
Then the official helper was added in
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git
** Tags removed: verification-needed-artful verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty
verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
48741/
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Trusty)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Tags: trusty
--
You received this bug notification because you are a member of Kernel
signed) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Summary changed:
- BUG: scheduling while atomic (v3.13 + VMware 6.0 and late)
+ BUG: scheduling while atomic (Kernel : Ubuntu-3.13 + VMware: 6.0 and late)
--
You received this bug
** Description changed:
[Impact]
It has been brought to my attention that VMware Guest[1] randomly crashes
after moving the VMs from a VMware "5.5" env to VMware 6.5 env.
The crashes started after the above move (5.5->6.5).
Notes:
* The crashes wasn't present in VMware 5.5 (with t
I built a test kernel[1] (3.13.0-153.203+hf185584v20180706b4)on my PPA
containing the 3 fixes as suggested by the VMware author[2].
If you are affected by this problem, feel free to use it for testing and
update this bug with any feedbacks.
[1] - PPA
sudo add-apt-repository ppa:slashd/sf185584
Microsoft Azure didn't come back to us yet about comment #3.
I will gladly resume the work on this LP once we got some updates, for
now I have marked it as "incomplete" as he cannot be verified outside
Microsoft.
Regards,
Eric
** Changed in: linux (Ubuntu)
Status: Triage
Microsoft Azure didn't come back to us yet about comment #3.
I will gladly resume the work on this LP once we get some updates. For
now I've set the bug to "incomplete" as it can only be tested internally
by Microsoft.
Regards,
Eric
--
You received this bug notificati
I currently have a user who run the test kernel (ppa:slashd/sf185584) on
both of his environment (Vmware 5.5 and VMware 6.5), to see if it fixes
the situation on 6.5 with v3.13 guests and to make sure everything still
looks good on VMware 5.5 (to avoid potential regression on version <
6.5)
--
Yo
This user will run the test kernel for several weeks to have a good
sample.
** Tags added: sts
** Description changed:
[Impact]
It has been brought to my attention that VMware Guest[1] randomly crashes
after moving the VMs from a VMware "5.5" env to VMware 6.5 env.
-
- The crashes started
** Description changed:
[Impact]
It has been brought to my attention that VMware Guest[1] randomly crashes
after moving the VMs from a VMware "5.5" env to VMware 6.5 env.
Notes:
* The crashes wasn't present in VMware 5.5 (with the same VMs). Only started
to happens with Vmware 6.5
*
Feedback from an affected user (3 weeks after he start installing a
test kernel with the potential candidate fixes :
"
..we are running the test kernel on 13 VMs, 10 on the new environment (VMware
6.5) and 3 on the old (VMware 5.5). We have experienced no hangs for those VMs
in the new environm
Zesty and Artful is not needed, as both release are no longer supported
version.
Xenial & Bionic testing as you did will suffice for 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/bugs/173
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kern
** Description changed:
This is a request to make a change in the hv-kvp-daemon systemd service
which is part of the linux-cloud-tools-common package to ensure the hv-
kvp-daemon service starts before the walinuxagent service. The default
dependencies make hv-kvp-daemon wait until the whol
** Description changed:
This is a request to make a change in the hv-kvp-daemon systemd service
which is part of the linux-cloud-tools-common package to ensure the hv-
kvp-daemon service starts before the walinuxagent service. The default
dependencies make hv-kvp-daemon wait until the whol
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You rece
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => He
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html
@builddeps@ will be replaced by the package's Build-Depends:, Build-
Depends-Indep:, and build-essential. This is useful if you have many
build dependencies which are only necessary for running the test suite
and you don't want
After a discussion with vorlon, his proposal is to blacklist the
"special" kernels so they're ignored for autopkgtests.
--
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/1723223
Title:
linu
101 - 200 of 859 matches
Mail list logo
