full computer model name:
FUJITSU LIFEBOOK SH54/K (FMVS54KR)
** Tags removed: needs-full-computer-model
--
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/1189896
Title:
[FUJITSU
I tried lastest mainline build, linux-
image-3.12.0-999-generic_3.12.0-999.201310160446, this issue is still
reproducible.
Linux 3.12.0-999-generic #201310160446 SMP Wed Oct 16 08:48:22 UTC
2013 x86_64 x86_64 x86_64
I don't think this issue is a regression, removing the tag.
** Tags removed:
This issue is no longer reproducible with at least current updated
kernel on precise.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
This laptop freezes once or twice a day. When it freezes, no response to
sysrq keys.
ProblemType: KernelCrash
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-16-generic 4.2.0-16.19
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic
The soft lockup trace is no longer reproducible after updating the
system *and* disable "powertop --auto-tune" *and* disable touchpanel
from BIOS. Closing this for now, but if I can reproducible it firmly
with enabling some options, I will report it again.
** Changed in: linux (Ubuntu)
>From the sticker:
LIFEBOOK SH90/T
FMVS90TB
Specs are as follows for your reference.
http://www.fmworld.net/fmv/sh/1501/spec/
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Description changed:
This laptop freezes once or twice a day. When it freezes, no response to
#146~lp1753662ThreeCommits is better at some level (around 40% failure
rate to 20%).
Failure rate: 187/470 (39.8%), 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2
16:08:24 UTC 2018
Failure rate: 87/222 (39.2%), 4.4.0-120-generic #144-Ubuntu SMP Thu Apr 5
14:11:49 UTC 2018
Failure rate: 138/712
Is there anyone from ubuntu-fan developers willing to satisfy SRU
requirements below?
> Blocked on:
>
> * SRU paperwork
> * Fixes for future stable releases
> * Fix for Bionic
I could try those, but it's not ideal since I have to go through
sponsorship processes and guess the intention of
I run an overnight test with v4.12 just to make sure it really fixed the
issue. It happened sometimes, but way less frequencies. We may need to
test it longer for "good" cases since the patch may not be only one.
Anyway, the current status is:
v4.12-rc1 with i40e 2.1.14 - bad (3 out of 3)
v4.12
With rc3, will test rc2 next.
v4.12-rc1 - bad (3 out of 3)
v4.12-rc3 - mixture result (24 out of 90)
v4.12-rc4 - relatively good (1 out of 70)
v4.12 - relatively good (5 out of 68)
v4.13 - good (0 out of 41)
** Attachment added: "bond_check_xenial_mainline_4.12-rc3_full.log"
With rc2 result. It looks like there is a noticeable difference between
v4.12-rc3 and v4.12-rc4.
@Joseph, can you please start looking into diffs? I'm keeping one
dedicated node just for this testing, so I can run the same script one
by one for more bisections.
v4.12-rc1 - bad (3 of 3)
v4.12-rc2
4.12.0-041200rc3-generic #201803080803 looks good. Please proceed to the
next one. I will test it my tomorrow which would be 12 hours later from
now.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc3 - good (0
Ok, 25% - 30% seems a baseline. I'd like to make sure v4.13 is really 0%
for longer running test, but will do the bisection of v4.12-rc3 and
v4.12-rc4 first.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12-rc4 - relatively
So far 0 of 6 with 4.12.0-041200rc3-generic #201803080803. But I will
keep it running for a while to see if it becomes close to 30% or 0%.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
25f480e89a022d382ddc5badc23b49426e89eabc looks good.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc3 #201803121355 - relatively good (1 of 252 - 0.4%)
25f480e89a022d382ddc5badc23b49426e89eabc
@Joseph,
Will do. Just as a possibility, I could build a kernel on the host if
that's helpful. Because the host is already reserved for this testing
and has hundreds of GBs of memory and many CPU cores. If you have a
pointer how to replicate your build process, that would be great.
--
You
Oh wait,
> I built the next test kernel, up to the following commit:
> d38162e4b5c643733792f32be4ea107c831827b4
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1753662
d38162e4b5c643733792f32be4ea107c831827b4 looks in-between v4.12-rc3 and rc4
which is
The test is still in progress, but so far
d38162e4b5c643733792f32be4ea107c831827b4 looks good (1 of 37). Since I
already downloaded the kernel locally, please go ahead to build the next
one. Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which is
> We may have went wrong somewhere in the bisect. However, just to be sure, I
> built a v4.12-rc4 test kernel. This kernel should be bad and contain the bug.
> If it does not, it may be due to the configs I'm using to build the test
> kernels.
I'm not following since I thought we tested that
d38162e4b5c643733792f32be4ea107c831827b4 looks good.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc1 #201803131457 - relatively good (1 of 93 - 1.1%)
d38162e4b5c643733792f32be4ea107c831827b4
v4.12.0-041200rc3
v4.12-rc4 is good, 1 of 146. Going to test v4.12-rc3.
--
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/1753662
Title:
[i40e] LACP bonding start up race conditions
Status in linux package
The new build of v4.12-rc3 is a good build (2 of 151).
4.12.0-041200rc3-generic #201803151851
v4.12-rc3 - bad (24 of 90 - 26.6%)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/
v4.12-rc3 - relatively good (2 of 151 - 1.3%)
http://kernel.ubuntu.com/~jsalisbury/lp1753662/v4.12-rc3/
So
** Attachment added:
"bond_check_xenial_4.12.0-041200rc3-generic_201803151851.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5081137/+files/bond_check_xenial_4.12.0-041200rc3-generic_201803151851.log
--
You received this bug notification because you are a
0bb230399fd337cc9a838d47a0c9ec3433aa612e seems good. I'm ready for the
next test.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc3 #201803081620 - relatively good (1 of 36 - 2.8%)
171d8b9363725e122b164e6b9ef2acf2f751e387 looks good. The next test is
with 4681ee21d62cfed4364e09ec50ee8e88185dd628.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc1 #201803141333 - relatively good (1 of 217 -
** Attachment added: "bond_check_xenial_4.12.0-041200rc1_201803141835.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5080093/+files/bond_check_xenial_4.12.0-041200rc1_201803141835.log
--
You received this bug notification because you are a member of Kernel
4681ee21d62cfed4364e09ec50ee8e88185dd628 looks good.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc1 #201803141835 - relatively good (1 of 113 - 0.9%)
4681ee21d62cfed4364e09ec50ee8e88185dd628
I run xenial HWE over a night while sleeping, the result was 0/119. The next
test is with:
v4.12.0-041200rc3 #201803081620 - ? 0bb230399fd337cc9a838d47a0c9ec3433aa612e
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
** Attachment added: "bond_check_xenial_hwe_4.13_full.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5073884/+files/bond_check_xenial_hwe_4.13_full.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
400129f0a3ae989c30b37104bbc23b35c9d7a9a4 looks good.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc3 #201803090724 - relatively good (2 of 77 - 2.6%)
400129f0a3ae989c30b37104bbc23b35c9d7a9a4
** Attachment added: "bond_check_xenial_mainline_4.12_full.log.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5071492/+files/bond_check_xenial_mainline_4.12_full.log.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is
For the record,
v4.12-rc1 - bad (3 out of 3)
v4.12 - relatively good (5 out of 68)
v4.13 - good (0 out of 41)
** Attachment added: "bond_check_xenial_mainline_4.13_full.log"
Not reproducible with 4.13-rc1 with 5 reboots.
4.10 - bad
4.11 - bad
4.13-rc1 - good
The next is 4.12.
** Attachment added: "bond_check_xenial_mainline_4.13-rc1.log"
Reproducible with:
v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/
The next is v4.13-rc1.
** Attachment added: "bond_check_xenial_mainline_4.11.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070785/+files/bond_check_xenial_mainline_4.11.log
Thanks, I was running some tests with existing HWE kernels in xenial
repo like linux-image-4.8.0-58-generic, linux-image-4.10.0-42-generic
and linux-image-4.13.0-36-generic. It looks like 4.10 is the last bad
one and 4.13 is the first good one.
Let me double-check with those two:
4.10 Final:
Reproducible with:
4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
The next test will be with:
v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/
** Attachment added: "bond_check_xenial_mainline_4.10.log"
I have let rc4 run for hours.
v4.12-rc1 - bad (3 out of 3)
v4.12-rc4 - relatively good (1 out of 70)
v4.12 - relatively good (5 out of 68)
v4.13 - good (0 out of 41)
I will let rc3 run during my night.
** Attachment added: "bond_check_xenial_mainline_4.12-rc4_full.log"
Correction. I thought v4.12-rc1 had i40e 2.1.7 because of:
https://github.com/torvalds/linux/commit/15990832cd3e7e8904f8dacdabfa33adb9a836d6
But it actually has 2.1.14 from the log output.
So the correct status is:
v4.12-rc1 with i40e 2.1.14 - bad
v4.12 with i40e 2.1.14 - good
--
You received
v4.11 with i40e 1.6.27 - bad
v4.12 with i40e 2.1.14 - good
next: v4.12-rc1 with i40e 2.1.7 - ?
** Attachment added: "bond_check_xenial_mainline_4.12.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070835/+files/bond_check_xenial_mainline_4.12.log
--
You
v4.12-rc1 with i40e 2.1.7 - bad
v4.12 with i40e 2.1.14 - good
I'm running out of time. So more bisections are for tomorrow.
** Attachment added: "bond_check_xenial_mainline_4.12-rc1.log"
The test is still in progress, but so far
171d8b9363725e122b164e6b9ef2acf2f751e387 looks good (0 of 21). Since I
already downloaded the kernel locally, please go ahead to build the next
one. Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which is
The new environment is not fully up yet to test. ETA would be by the end
of this week.
--
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/1753662
Title:
[i40e] LACP bonding start up race
FWIW, kernel trace happens with the kernel in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/comments/77
But I will let it running anyway since I'm not sure if it affects to the
testing or not.
[5.999557] rtc_cmos 00:00: setting system clock to 2018-04-11 15:52:23 UTC
I ran HWE 4.13 just to make sure the result is the same as the previous
host. And as we confirmed before, the issue is not reproducible with HWE
4.13.
[stock xenial]
Failure rate: 117/726 (16.1%), 4.4.0-040400-generic #201803261439 SMP Mon Mar
26 14:43:35 UTC 2018
[HWE 4.13]
Failure rate: 0/407
I ran HWE 4.13 just to make sure the result is the same as the previous
host. And as we confirmed before, the issue is not reproducible with HWE
4.13.
[HWE 4.13]
Failure rate: 0/407 (0.0%), 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14
17:48:43 UTC 2018
> We should first confirm that
FWIW, I tried PCI hot-plugging to try another way for faster iterations without
reboot.
https://paste.ubuntu.com/p/qDVkMcTYPQ/
However, the issue wasn't reproducible with hot-plugging. Rebooting is
the easiest reproduction so far.
--
You received this bug notification because you are a member
4.4 kernel using the Artful configs didn't make much difference.
Failure rate: 117/726 (16.1%), 4.4.0-040400-generic #201803261439 SMP
Mon Mar 26 14:43:35 UTC 2018
I will let stock 4.4 and 4.13 hwe run just to make sure to know the
occurrence rate with this host.
--
You received this bug
Finally got a machine up and running. Will resume testing shortly.
--
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/1753662
Title:
[i40e] LACP bonding start up race conditions
Status in
Just for the record, up-to-date numbers after the weekend.
Failure rate: 167/422 (39.6%), 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2
16:08:24 UTC 2018
Failure rate: 87/222 (39.2%), 4.4.0-120-generic #144-Ubuntu SMP Thu Apr 5
14:11:49 UTC 2018
Failure rate: 117/726 (16.1%),
Ok, we have some numbers with the new host.
Failure rate: 45/112 (40.2%), 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2
16:08:24 UTC 2018
Failure rate: 87/222 (39.2%), 4.4.0-120-generic #144-Ubuntu SMP Thu Apr 5
14:11:49 UTC 2018
Failure rate: 117/726 (16.1%), 4.4.0-040400-generic
Just for the record, I'm using the attached rc.local for testing.
** Attachment added: "rc.local"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5116629/+files/rc.local
--
You received this bug notification because you are a member of Kernel
Packages, which is
4.12-rc4 kernel with Xenial configs looks bad.
[xenial configs]
v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%)
v4.12.0-041200rc3 #201803191316 - relatively bad (21 of 150 - 14.0%)
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6
v4.12.0-041200rc3 #20180324 - relatively bad (60 of 499 -
bscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main;
> status=Triaged; importance=High; assignee=joseph.salisb...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial;
> sourcepackage=linux; compo
ea094f3c830a67f252677aacba5d04ebcf55c4d9 looks bad.
[xenial configs]
v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%)
v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%)
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6
v4.12.0-041200rc3 #20180324 relatively bad (6 of 56 -
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad.
[xenial configs]
v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%)
v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%)
--
You received this bug notification because you are a member of Kernel
Packages, which is
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad.
[xenial configs]
v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%)
v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%)
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6
--
You received this bug notification because you are a
Ok, we see some differences with the three kernels. How do we want to
proceed from here?
v4.12-rc3 - bad (24 of 90 - 26.6%)
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3/
v4.12-rc3 #201803151851 - relatively good (2 of 151 - 1.3%)
I was pretty occupied today, so I'm going to test
55cbdaf6399de16b61d40d49b6c8bb739a877dea now and report back my tomorrow
morning.
[xenial configs]
v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%)
v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%)
55cbdaf6399de16b61d40d49b6c8bb739a877dea looks bad.
[xenial configs]
v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%)
v4.12.0-041200rc3 #201803191316 - relatively bad (21 of 150 - 14.0%)
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6
v4.12.0-041200rc3 #20180324 - relatively bad (60 of
BTW, have we set the baseline of "good" in this bisection with xenial
configs?
> 4.13.0-36(xenial HW) - good (0 of 119 - 0%)
Does HWE kernel man with xenial configs? Or was it built with the source
release config i.e. artful?
--
You received this bug notification because you are a member of
Correction: Does HWE kernel mean it's with xenial configs? Or was it
built with the source release config i.e. artful?
--
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/1753662
Title:
Public bug reported:
When provisioning Ubuntu servers with MAAS at once, some bonding pairs
will have unexpected LACP status such as "Expired". It randomly happens
at each provisioning with the default xenial kernel(4.4), but not
reproducible with HWE kernel(4.13). I'm using Intel X710 cards
** Attachment added: "bond2_status.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070466/+files/bond2_status.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "interfaces.50-cloud-init.cfg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070467/+files/interfaces.50-cloud-init.cfg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "bond1_status.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070465/+files/bond1_status.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This might be related (not exactly the same):
https://sourceforge.net/p/e1000/bugs/524/
One says 1.6.42 fixed his issue.
Looks like Intel has around 10 releases between 1.4.25 and 2.1.14, so it may
not be handy to bisect.
The record of xenial default kernel.
** Attachment added: "bond_check_xenial.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070691/+files/bond_check_xenial.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
For the record of testing.
** Attachment added: "bond_check_xenial_c15e07b02bf0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+attachment/5070633/+files/bond_check_xenial_c15e07b02bf0.log
--
You received this bug notification because you are a member of Kernel
Packages,
The kernel with c15e07b02bf0 didn't make a difference on the race
condition. The issue is still reproducible. Let me know when you need my
testing again with different kernels.
So far, I'm using rc.local below to reboot the same node multiple times.
#!/bin/sh
exec >> /root/bond_check.log
SRU request to D/E/F:
https://lists.ubuntu.com/archives/kernel-team/2019-November/105221.html
--
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/1848481
Title:
cloudimg: no iavf/i40evf
I've filed a follow-up bug of neutron-openvswitch on kernel upgrade:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1851764
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Marking it back to Fix Committed as I got a clarification.
https://lists.ubuntu.com/archives/kernel-team/2019-November/105480.html
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: New => Invalid
**
[disco]
w/o -proposed
multipass@disco:~$ dpkg -L linux-modules-5.0.0-36-generic | egrep 'i40e|iavf'
/lib/modules/5.0.0-36-generic/kernel/drivers/net/ethernet/intel/i40e
/lib/modules/5.0.0-36-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko
multipass@disco:~$ modinfo iavf
modinfo: ERROR:
[eoan]
w/o -proposed
multipass@eoan:~$ dpkg -L linux-modules-5.3.0-23-generic | egrep 'i40e|iavf'
/lib/modules/5.3.0-23-generic/kernel/drivers/net/ethernet/intel/i40e
/lib/modules/5.3.0-23-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko
multipass@eoan:~$ modinfo iavf
modinfo: ERROR:
[bionic]
w/o -proposed
ubuntu@bionic:~$ dpkg -L linux-modules-4.15.0-70-generic | grep i40e
/lib/modules/4.15.0-70-generic/kernel/drivers/net/ethernet/intel/i40e
/lib/modules/4.15.0-70-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko
ubuntu@bionic:~$ modinfo i40evf
modinfo: ERROR: Module
The general protection fault is reproducible with the current 5.3 kernel as
follows by creating 10 SR-IOV enabled VMs with OpenStack and deleting 5 VMs
sequentially. After updating it to the -proposed one as
linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection
fault
The general protection fault is reproducible with the current 5.3 kernel as
follows by creating 10 SR-IOV enabled VMs with OpenStack and deleting 5 VMs
sequentially. After updating it to the -proposed one as
linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection
fault
The general protection fault was reproducible with the current 5.3 kernel as
follows by creating 10 SR-IOV sequentially. After updating it to the -proposed
one as
linux-image-5.3.0-25-generic 5.3.0-25.27, there is no such general protection
fault happened with the same operations. So we can
ntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Nobuto Murata (nobuto)
--
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/18484
Have sent to kernel-t...@lists.ubuntu.com
** Patch added: "0001-UBUNTU-Packaging-include-iavf-i40evf-in-generic.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+attachment/5298618/+files/0001-UBUNTU-Packaging-include-iavf-i40evf-in-generic.patch
--
You received this bug
** No longer affects: livecd-rootfs (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/1848481
Title:
cloudimg: no iavf/i40evf module so no network available with SR-IOV
enabled
Hmm, ixgbevf is in linux-modules-*-generic on bionic instead of modules-
extra. So I'd like i40evf in the same modules-generic set.
linux-modules-4.15.0-65-generic:
/lib/modules/4.15.0-65-generic/kernel/drivers/net/ethernet/intel/ixgbevf/ixgbevf.ko
--
You received this bug notification because
*** This bug is a duplicate of bug 1848481 ***
https://bugs.launchpad.net/bugs/1848481
** Package changed: compiz-plugins-main (Ubuntu) => linux (Ubuntu)
** This bug has been marked a duplicate of bug 1848481
cloudimg: no i40evf module is available so no network with SR-IOV enabled
cloud
** Summary changed:
- cloudimg: no i40evf module is available so no network with SR-IOV enabled
cloud
+ cloudimg: no i40evf module is available so no network available with SR-IOV
enabled cloud
** Summary changed:
- cloudimg: no i40evf module is available so no network available with SR-IOV
Public bug reported:
For example with bionic, i40evf module is in linux-modules-
extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra
seeded:
$ curl -s
http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest
| grep linux-
linux-base
Posted again with a proper subscription instead of guest post:
https://lists.ubuntu.com/archives/kernel-team/2019-October/104898.html
--
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/1848481
** Changed in: linux (Ubuntu Disco)
Assignee: gerald.yang (gerald-yang-tw) => Nobuto Murata (nobuto)
** Changed in: linux (Ubuntu Eoan)
Assignee: gerald.yang (gerald-yang-tw) => Nobuto Murata (nobuto)
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => In
I'm just not sure how it can be merged to focal so raised a question:
https://lists.ubuntu.com/archives/kernel-team/2019-November/105393.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Initially we thought we were hit by
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910201
But it looks like some patches are already in focal GA kernel like
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=d256617be44956fe4f048295a71b31d44d9104d9
--
You received this bug
Hmm, I'm not sure where the difference comes from. With Juju 2.9.16 I
still see mtu=1442 on VM NIC (expected) and mtu=1450 (bigger than
underlying NIC) on fan-252 bridge.
ubuntu@juju-913ba4-k8s-on-openstack-0:~$ brctl show
bridge name bridge id STP enabled interfaces
Let me know what log / log level you want to see to compare. I'm
attaching the machine log of the VM for the time being.
** Attachment added: "machine-0.log"
https://bugs.launchpad.net/juju/+bug/1936842/+attachment/5533786/+files/machine-0.log
--
You received this bug notification because
Public bug reported:
-kvm flavor has CONFIG_NR_CPUS=64 although -generic has
CONFIG_NR_CPUS=8192 these days.
It will be a problem especially when launching a VM on top of a
hypervisor with more than 64 CPU threads available. Then the guest can
only use up to 64 vCPUs even when more vCPUs are
Thank you Stefan for the prompt response. I'm marking this as Invalid
for the time being assuming the value was intended.
** Changed in: linux-kvm (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Also affects: charm-ovn-chassis
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/2009594
Title:
Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
Just to give another data point, I've been running 5.19 from hwe-edge
(instead of hwe) for some time but I realized this suspend issue after
updating hwe-edge from 5.19.0.28.29~22.04.6 to 5.19.0.32.33~22.04.9.
So I went back and tested it as follows. It looks like it's a regression
within 5.19.
** Description changed:
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- After beonding is enabled on switch and server side, the system will
- hang at initialing ubuntu. The kernel loads but around starting the
- Network Services
Random pointers although I'm not sure those are identical to my issue:
https://www.reddit.com/r/archlinux/comments/199am0a/thinkpad_t14_suspend_broken_in_kernel_670/
https://discussion.fedoraproject.org/t/random-resume-after-suspend-issue-on-thinkpad-t14s-amd-gen3-radeon-680m-ryzen-7/103452
--
Public bug reported:
I had a similar issue before:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
However, I haven't seen the issue with later kernels until getting
6.8.0-11.11+1 recently.
* 6.8.0-11 - fails to suspend/resume for the second time although the first
kernel log when trying suspend/resume twice in a row. The machine got
frozen while the power LED is still on in the second suspend and there
is no second "PM: suspend entry (s2idle)" in the kernel log.
** Attachment added: "failed_on_second_suspend.log"
Multiple suspends in a row worked without an external monitor connected,
but after connecting it the machine failed to suspend/resume.
** Attachment added: "failed_on_suspend_after_connecting_monitor.log"
1 - 100 of 101 matches
Mail list logo
