The precise kernel version 3.2.0-56.86 fixes the issue, thanks!
Why no verification-needed flag? Anyway, consider this verification-
done-precise.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
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/1208740
Title:
Large pastes into readline enabled
John, are there any plans to SRU this to Trusty? 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/1308761
Title:
apparmor spams log with warning message
Status in “linux” package
Public bug reported:
I was running an apt-get dist-upgrade when the FS suddenly remounted
to RO. The 2 audit lines are from apt-dater running successively apt-
get update and apt-get dist-upgrade:
[153439.007924] type=1006 audit(1396010484.706:46): pid=16029 uid=0 old
auid=4294967295 new
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1298972/+attachment/4048672/+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: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1298972/+attachment/4048673/+files/ProcCpuinfo.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/1298972/+attachment/4048678/+files/WifiSyslog.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/1298972/+attachment/4048674/+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: UdevLog.txt
https://bugs.launchpad.net/bugs/1298972/+attachment/4048677/+files/UdevLog.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/1298972/+attachment/4048676/+files/UdevDb.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/1298972
** 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/1298972
Title:
stacktrace in ext4:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1298972/+attachment/4048675/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm attaching the dmesg extract as it reads more easily (same content as
what's in the issue description).
** Attachment added: dmesg-extract.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1298972/+attachment/4048521/+files/dmesg-extract.log
--
You received this bug notification
The verification on Precise was done using the linux-image-generic-lts-
trusty kernel.
** Tags removed: verification-needed
** Tags added: verification-done-precise verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
My qemu host keeps crashing every once in a while and this seems to
happen when there is some load and/or network traffic happening in the 2
guests it powers.
This time I was able to capture a crash trace:
Sep 10 16:49:45 ocelot kernel: [204709.569951] general protection
Attaching the libvirt definition of the 2 guests
** Attachment added: fw guest (OpenBSD 5.5 64bit)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367932/+attachment/4200959/+files/fw.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: bck guest (Trusty 64bit)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367932/+attachment/4200960/+files/bck.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On 09/10/2014 06:03 PM, Joseph Salisbury wrote:
id this issue occur in a previous version of Ubuntu, or is this a new
issue?
The problem also happened when the host was running Saucy and the
OpenBSD guest was at version 5.4.
Looking at the trace more closely, I noticed
Hi Chris,
On 09/11/2014 01:16 PM, Chris J Arges wrote:
How often does this occur?
It depends: can be once a week or 3 days in a row. It almost always
happened at night (during backup jobs).
Have you been able to reproduce this issue without pinning your VMs to cpus?
Can you still reproduce
On 09/12/2014 07:33 AM, Christopher M. Penalver wrote:
** Tags added: bios-outdated-0502
I'm not sure about this flag since the outdated BIOS version was 305 and
the 502 one is the latest.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Not any crash since I updated the BIOS to version 502 and after
installing linux-crashdump. It's been 11 days since the last crash so
maybe the BIOS update was the fix. I'll wait some more days and will
remove linux-crashdump just to see if this could have some impact.
--
You received this bug
Hi Russell,
On 09/28/2014 01:43 AM, Russell Smith wrote:
https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.2 contains
ext4 patches related to the code in this stack dump;
ad6599ab3ac98a4474544086e048ce86ec15a4d1 specifically references
incorrect freeing of the function.
I'm
Hi Russell,
On 10/02/2014 06:06 AM, Russell Smith wrote:
I behaved lazily... and have been trying to collect more data before
posting back. Sorry for the delay.
1. I can only reproduce the bug about once a week on 3.13 kernel that is
running on ubuntu 14.04.
2. I was lazy and after
Finally marking as invalid since the BIOS upgrade fixed the problem.
** 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:
A linux bridge always adopts the smallest MTU of the enslaved devices.
When no device are enslaved, it defaults to a MTU of 1500 and refuses to
use a larger one. This is problematic when using bridges enslaving only
virtual NICs (vnetX) like it's common with KVM guests.
On 12/04/2014 01:44 PM, Joseph Salisbury wrote:
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
This is reproducible on 12.04 too.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please
On 12/05/2014 01:20 AM, Andy Whitcroft wrote:
Which is calculated rather simplistically where there are no attached
devices:
int br_min_mtu(const struct net_bridge *br)
{
[...]
if (list_empty(br-port_list))
mtu = ETH_DATA_LEN;
[...]
It is not entirely
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1393317
Title:
Intel 7265 [8086:095b] Wireless
Public bug reported:
I noticed that one of my VM had this dmesg -T output:
[Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
[Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1):
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor
inconsistent: 16446 vs
apport information
** Tags added: apport-collected
** Description changed:
I noticed that one of my VM had this dmesg -T output:
[Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
[Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1):
ext4_mb_generate_buddy:756:
** Attachment added: /proc/version_signature
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/+attachment/4322692/+files/version.log
--
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/1423672/+attachment/4322705/+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: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1423672/+attachment/4322703/+files/ProcCpuinfo.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/1423672/+attachment/4322708/+files/WifiSyslog.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/1423672/+attachment/4322704/+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: UdevLog.txt
https://bugs.launchpad.net/bugs/1423672/+attachment/4322707/+files/UdevLog.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/1423672/+attachment/4322706/+files/UdevDb.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/1423672
It was a one time event. I'll report here if/when this happens again.
** 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.
Same problem here (Trusty+HWE kernel) and adding /dev/log r, to
/etc/apparmor.d/local/usr.sbin.rsyslogd does not help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1425398
On 03/04/2015 05:07 PM, Simon Déziel wrote:
Before loosing anyone's time on this issue, I'll first make sure the
hypervisor's RAM is sane. So I'll get back after some memtest86+ then
I'll look at the 4.0 kernel.
After 15+ hours of memtest86+ (8 full passes), I don't think the RAM is
at fault
On 03/09/2015 04:18 PM, Oliver Brakmann wrote:
Only ever happens on VMs, never on physical machines. All my
virtual disks use Virtio, cache mode 'none' (yeah, I know), I/O mode
'native', with raw LVM volumes as backend.
Exact same setup here. What's wrong with cache mode set to none? This
Users of Trusty should give a try to the HWE kernel (3.16 ATM) that is
officially supported.
For details on how to enable this:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This problem just occurred on *another* VM. Again, right after the
cron.daily run.
--
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/1423672
Title:
ext4 turned read-only following a
This occurred on another VM. I guess I will have to roll our the 4.0-rc2
kernel everywhere.
--
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/1423672
Title:
ext4 turned read-only during
** Summary changed:
- ext4 turned read-only following a cronjob run
+ ext4 turned read-only during logrotate daily run
--
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/1423672
Title:
The first occurrence of this problem goes back to Feb 17th. While I keep
all the VMs up to date on a daily basis, I now have doubts about the
hypervisor's RAM (not ECC by the way). I brought all the VMs offline to
have their FSes checked (all ext4). Several of them needed fixing by
fsck. Since
Works here too, thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1425398
Title:
Apparmor uses
On 05/15/2015 11:55 AM, Pete Cheslock wrote:
I'm still able to recreate this issue with kernel version
3.13.0-52-generic #85-Ubuntu SMP Wed Apr 29 16:44:17 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
The fix landed in the kernel (#86) right after the one you are running
(#85).
--
You received
Things seem to have stabilized recently as the last occurrence I
witnessed was on May 13th.
I searched all my 2014 and 2015 logs for ext4_mb_generate_buddy and
here is what I got:
Nov 24 02:54:03 smb kernel: [842091.081319] EXT4-fs error (device vda1):
ext4_mb_generate_buddy:756: group 1, block
While installing linux-image-extra-virtual will work, it also eats up
~230 MB more of storage:
$ sudo apt-get install --no-install-recommends linux-image-extra-virtual
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete = Confirmed
** Summary changed:
- ext4 turned read-only during logrotate daily run
+ ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor
inconsistent: X vs Y
--
You received this bug notification because you are a
And yet again:
root@rproxy:~# dmesg -T | tail
[Thu Jun 11 15:28:56 2015] type=1400 audit(1434050938.364:24):
apparmor=STATUS operation=profile_replace profile=unconfined name=nc
pid=658 comm=apparmor_parser
[Thu Jun 11 15:28:59 2015] init: plymouth-upstart-bridge main process ended,
respawning
To add one more data point, my Trusty server using the Utopic HWE kernel
also exhibits the problem:
May 21 12:27:28 xeon kernel: [95104.918686] audit: type=1400
audit(1432225648.230:57): apparmor=DENIED operation=sendmsg
info=Failed name lookup - disconnected path error=-13
Oddly enough, I'm still seeing some variation of this error:
May 21 12:27:28 xeon kernel: [95104.918686] audit: type=1400
audit(1432225648.230:57): apparmor=DENIED operation=sendmsg
info=Failed name lookup - disconnected path error=-13
profile=/usr/sbin/rsyslogd name=dev/log pid=3444 comm=logger
** Attachment added: "syslog from 3.13.0-69"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516052/+attachment/4518323/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
When I run the 3.13.0-69 -proposed kernel on Trusty, I'm seeing infinite
amount of ip rules:
$ ip -f inet rule show | head
0: from all lookup local
0: from all lookup local
0: from all lookup local
0: from all lookup local
0: from all lookup
** 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/1516052
Title:
[regression] 3.13.0-69 infinite ip rules
Status in
*** This bug is a duplicate of bug 1514785 ***
https://bugs.launchpad.net/bugs/1514785
So 3.19.0-33 doesn't have the problem.
** This bug has been marked a duplicate of bug 1514785
kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule
table)
--
You received this bug
Indeed, the 3.13 and 3.16 -proposed kernels have the commit I'm
suspecting:
fib_rules: fix fib rule dumps across multiple skbs
The 3.19 -proposed kernel doesn't have it so I'm wondering if it's also
affected.
--
You received this bug notification because you are a member of Kernel
Packages,
It's not HWE specific as the 3.13 branch is also affected. Here's a
recap of the good/bad versions:
3.13.0-68: good
3.13.0-69: bad
3.16.0-51: good
3.16.0-53: bad
3.19.0-32: good
3.19.0-33: good
** Also affects: hwe-next
Importance: Undecided
Status: New
** No longer affects: hwe-next
On 10/13/2015 11:50 AM, Jan Wagner wrote:
> I got also hit with the problem on Debian Jessie VM [virtio] (KVM host
> is Jessie as well).
>
> The following bug might be related:
> https://bugzilla.kernel.org/show_bug.cgi?id=104571
>
> I'm trying now '"cache=none"' for this VM and see how that
Someone on the Strongswan mailing list [1] mentioned that 3.19 was also
affected.
I quickly skimmed the changelog between 3.16.0-38-generic to
3.16.0-39-generic and a possible culprit could be:
* ip_forward: Drop frames with attached skb-sk
Clemens, would you be able to just revert the
Marking as confirmed thanks to Tom's bisection results.
** 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/1467561
Title:
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1522766
Title:
cryptsetup hangs after kernel upgrade
The broken kernels just made it to -security.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1514785
Title:
kernel 3.16.0.52+53 - ip rule repeats all default rules (messing
@idallen, try updating to 3.19.0-39.44 which should have the fix. You
might need to enable the -proposed repository:
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1522766 ***
https://bugs.launchpad.net/bugs/1522766
Luis, the kernel 3.13.0-73.116 fixes the issue, thanks!
** This bug has been marked a duplicate of bug 1522766
cryptsetup hangs after kernel upgrade to 3.13.0-72.115
--
You received this bug
The problem is with the kernel itself and a fix was committed upstream:
https://www.spinics.net/lists/stable/msg110748.html
** Changed in: strongswan (Ubuntu)
Status: New => Invalid
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
It turns out that the "dirname not found" error is a red herring because
it also occurs with previous kernel and doesn't prevent booting.
With the problematic kernel, giving the wrong password doesn't ask to
enter the password so it seems it's not even verified. So whatever the
password used,
Public bug reported:
Early in boot, I see this:
Mounting root file system ... Begin: Running /script/local-top ...
/script/local-top/cryptroot: line 24: dirname not found
Then get prompted to enter the LUKS password. Once I entered the right
password, nothing happens, not even any disk
I can confirm that 3.13.0-71.114 fixes the issue. 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/1514785
Title:
kernel 3.16.0.52+53 - ip rule repeats all default rules (messing
volker, it's in 4.3.0-4.13:
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_4.3.0-4.13/changelog
--
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/1523133
Title:
strongswan
Since I filled the bug report, I installed the vbetool and xserver-xorg-
video-intel packages and I'm no longer seeing the crash (uptime: 7h+).
The graphical performance is also back to what it was on Trusty. I guess
my desktop install was too minimal (--no-install-recommends ubuntu-
desktop).
If
Public bug reported:
My Thinkpad T410 is frequently crashing since I'm running Xenial.
Preceeding a crash, an almost entirely blank screen is displayed for a
few seconds, then the laptop shuts down.
I couldn't identify/correlate the crash with anything special I'm doing,
it just happens after
The graphic performance is really below what the same laptop was capable
with Trusty. Under Xenial, I'm unable to smoothly scroll down/up a
simple HTML page with Firefox.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Louie, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502#22
provides a simple way to reproduce. If you could give it a try that
would be appreciated.
FYI, when my hypervisor was running Trusty (3.13), the problem was
reproducible on fresh VMs with brand new ext4 FSes, so hopefully that
Public bug reported:
Steps to reproduce:
1) Force a time delta
date -s "now - 1 hour"
2) Restart systemd-timesyncd to have it fix the time
systemctl restart systemd-timesyncd
Expected behavior:
The clock should be back in sync.
Actual (problematic) behavior:
The clock stays out of sync
Thanks Václav, your conclusion about older Intel CPU seems to match my
setup since this only happens on a Xeon E3110 (which is in fact a re-
branded Core2 Duo E8400).
Thanks for bisecting this and figure the fix was:
** 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/1423672
Title:
ext4_mb_generate_buddy:756: group N, block bitmap and
I recently reinstalled the affected host to run Xenial so I can no
longer test the proposed fix for the 3.13 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1423672
The fix included in 4.4.0-20-generic works well, 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/1566465
Title:
[regression]: Failed to call clock_adjtime(): Invalid argument
Thanks Chris. So far, no regression with the Trusty kernel:
$ uname -a
Linux xeon 3.13.0-86-generic #130~lp1423672v201604200743 SMP Wed Apr 20
12:44:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Since the issue only happens rarely, more people testing it would be
welcome.
--
You received this
I can confirm this problem was fixed for Xenial on 4.4.0-65.86, thank
you.
--
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/1660832
Title:
unix domain socket cross permission check
** 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/1660832
Title:
unix domain socket cross permission
4.4.0-65.86 from -proposed produces no warning, thanks.
** 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-firmware in Ubuntu.
** Attachment removed: "13882350_308252829517622_547356934184648507_n.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573848/+attachment/4719653/+files/13882350_308252829517622_547356934184648507_n.jpg
** Patch removed: "13882350_308252829517622_547356934184648507_n.jpg"
Chenyuchai, yes,
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424
is the fix. It was integrated in the Trusty kernel 3.13.0-87.133
--
You received this bug notification because you are a member of Kernel
Packages, which is
@thornyon, why did you marked this bug as fix released? As far as I can
see, linux-firmware still doesn't ship kbl_dmc_ver1.bin.
I'd like to benefit from lower power usage that should come with this
firmware.
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
== Regression details ==
Since the rolled out 4.4.0-93, we are getting many ~identical call
traces that look like this:
[ cut here ]
WARNING: CPU: 0 PID: at
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445
skb_warn_bad_offload+0xd1/0x120()
So far those messages were only noticed on 2 of our hypervisor nodes.
I'm attaching the relevant extracts of dmesg on those 2 machines.
** Attachment added: "multiple-dmesg.tgz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713787/+attachment/4940943/+files/multiple-dmesg.tgz
--
You
I'm now seeing similar traces on a wildly different machine that's not
using the bonding module. All machines are KVM hypervisors with
VHOST_NET_ENABLED=1. I'm attaching multiple dmesg extract from 3
machines, 2 PowerEdge R830 and 1 old Core 2 Duo/Xeon.
** Summary changed:
- linux 4.4.0-93
This really looks like https://patchwork.ozlabs.org/patch/799015/ which
fortunately made it into 4.4.0-94.117. I'll give that -proposed kernel a
test run.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1711535 ***
https://bugs.launchpad.net/bugs/1711535
4.4.0-94.117 has solved the problem so I'll mark this as a duplicate of
LP: #1711535 (update to stable kernel 4.4.82).
** This bug has been marked a duplicate of bug 1711535
Xenial update to 4.4.82
Between 4.4.0-124.148 and 4.4.0-127.153, the following commits
references "sit":
- sit: reload iphdr in ipip6_rcv
- ipv6: sit: better validate user provided tunnel names
- ipv6 sit: work around bogus gcc-8 -Wrestrict warning
--
You received this bug notification because you are a
I don't know if that matters but I use fq_codel and have been for a long
while.
# sysctl net.core.default_qdisc
net.core.default_qdisc = fq_codel
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a
Xenial VM with a sit tunnel, I get such messages:
May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with
TOS=0x5
Those are logged quite often:
# grep -cF 'sit: non-ECT' /var/log/syslog
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1772775/+attachment/5143072/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1772775/+attachment/5143076/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1772775/+attachment/5143074/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1772775/+attachment/5143073/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 226 matches
Mail list logo
