[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian

@vorlon, I just found this ticket, and would like to report that my Intel AX211 wifi card no longer connects via 6ghz with the linux-oem-22.04b. It was working fine with the 5.15 kernel. I suspect regulatory compliance to be the issue as all of the 6ghz channels show disabled when running $

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

So where are we on this folks? -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

Alright so that means we either need to push a change to remove noexec from the kernel init code, or we go ahead with noexec, and give people on option to remount with exec should they want sgx functionality. I do think the nosuid flag does still provide some benefit even if we decide not to

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

In case anyone is curious conversation is on-going on the kernel-team mailing list https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

@juliank, is this an aws system? If not there's a good chance that you are using an initramfs to mount the filesystems. That's definited in either /etc/init.d/udev or directly out of the init that lives in the initramfs. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

Here is a workaround for this issue in case anyone finds this in the future. Copy remount_dev.service to /etc/systemd/system sudo chown root:root /etc/systemd/system/remount_dev.service sudo systemctl daemon-reload sudo systemctl enable remount_dev.service Still I think the kernel patch should

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

** Information type changed from Private Security to Public Security ** Summary changed: - dev file system is mounted without nosuid + dev file system is mounted without nosuid or noexec -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

** Description changed: + [ SRU TEMPLATE ] + [ Impact ] + + * nosuid, and noexec bits are not set on /dev + * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. + *

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

Looks like Kees already found this years ago. https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ Looks like it was accepted as commit 28f0c335dd4a1 in 5.17. So I think we should apply this patch and the corresponding set CONFIG_DEVTMPFS_SAFE=y at least for the

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

I was hoping to work around this in /etc/init.d/udev, but it looks like that gets redirected to systemctl via . lib/lsb/init-functions ** Description changed: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

So far I've only tested focal AWS images, but this may likely exist elsewhere as well. ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid

** Also affects: linux (Ubuntu) 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/1991975 Title: dev file system is mounted without nosuid

[Kernel-packages] [Bug 1901470] Re: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead

I'm having a similar issue in Jammy again with an HDMI connected 2k monitor. The issue here being that the monitor works on boot up, but experiences this problem after a few hot plugs. Has someone found a follow-on ticket similar to this? -- You received this bug notification because you are a

[Kernel-packages] [Bug 1901470] Re: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead

** Tags added: indeed jammy -- 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/1901470 Title: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p

[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

** Tags added: indeed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status

[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

What are the chances we can remove the the affected kernels from the archives so more people don't get bit by this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title:

[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog

This is seems to be wider than simply Lenovo machines as my Dell Precision 5540 is hitting this as well. -- 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/1851749 Title: Frequently getting

[Kernel-packages] [Bug 1847786] Re: Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels

** Tags added: indeed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1847786 Title: Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels Status in linux-firmware

[Kernel-packages] [Bug 1847786] [NEW] Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels

Public bug reported: It looks like the hwe kernels need the linux-firmware revved again. update-initramfs: Generating /boot/initrd.img-5.3.0-12-generic W: Possible missing firmware /lib/firmware/i915/icl_guc_32.0.3.bin for module i915 W: Possible missing firmware

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

@oddbjornk @cristofaro Launchpad is not a forum. Each bug is meant to solve one problem. One of you need to create a new bug for the new problem. You are welcome to reference or link this issue in that new bug though so whoever triages it has a reference. -- You received this bug

[Kernel-packages] [Bug 1702961] Re: Intel wifi instability with 4.10 and Intel Device 24fd

I'm going to close out this bug, as I have not experienced this since moving to 18.04. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

Re: [Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

ed; assignee=None; > Launchpad-Bug-Tags: indeed verification-done-artful > verification-done-xenial > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: ballengerm benjamin-redhat-bugs chiluk &

[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44

Yah @jparedes you should probably open a different bug. You are running into something different. I've also verified that this is now fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

@katamo 4.14.xx is not a supported Ubuntu kernel. I'm not sure where you pulled that kernel from, but it is not supportable. At this point all Supported Ubuntu kernels and mainline 4.15+ have this fix. @EVERYONE ELSE If you think you are hitting this issue and are running the latest supported

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

Ran same tests against 4.13.0-38 on artful. Just curious, this only seems to be applied to hwe and hwe-edge kernels for xenial. Is that a change in policy? Even though I haven't attempted it, it appears as if this should be pretty straightforward apply on the 4.4 kernel stream. -- You

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

** Tags removed: verification-needed-artful ** Tags added: verification-done-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/1729674 Title: TB16 dock ethernet corrupts data with

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

Looks like this has been released with 4.15.0-9.10 which is available in bionic. ** Also affects: linux (Ubuntu Bionic) Importance: High Assignee: Kai-Heng Feng (kaihengfeng) Status: In Progress ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Released **

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

@kmously I see that you marked this fix as Fix Committed in Artful, but I do not see it in the master-next branch of artful. I'm moving this back to In progress in artful as this does not appear to have been pushed to master-next for artful yet. Feel free to push it back to Fix Committed when

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Importance: Undecided => 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/1729674

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

@pandasauce ... Fix committed means it's in the git archive, but has completed testing nor been integrated into the archives yet. Also please refrain from repeating things we already know in the thread or otherwise +1'ing or me-tooing. It just wastes developers time that could be spent actually

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

Hasn't completed testing or been integrated into the archives. -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

That patch note makes it sound like there will be a hardware/firmware fix that will hopefully resolve this. If so it is very unlikely that upstream will accept your patch, as the proper fix will really be to upgrade your firmware. A more preferable patch will be to log a big bad warning if you

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

I should also mention that this should probably be pushed to linux- stable as well as mainline as this is a silent data corruption bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

Those changes test as good. @Kai-Heng Feng. In the future you should consider setting LOCALVERSION or using a PPA and setting a +lp1729674 to version string in the changelog. With what you did it's hard to distinguish between your test package and an official package. See

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

I'm sorry I've been unable to test this from my end. Have you been able to make any progress on this? -- 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/1729674 Title: TB16 dock ethernet

Re: [Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

I reviewed your patch, and it appears as if it only turns off receive checksumming. The internets are saying that transmit needs to be turned off as well. Have you checked to see if transmit is affected as well? I will try to do some transmit tests. I'll also "test" your kernel when I get a

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

udevadm info -e as requested. ** Attachment added: "udevadminfo" https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+attachment/5010640/+files/udevadminfo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

I also just went through the process of reproducing this while watching the kern.log. Absolutely 0 messages came out. If you find some verbose debugging you want me to turn on let me know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

Re: [Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

I am not using ipv6. On Tue, Nov 14, 2017 at 9:10 AM, Mario Limonciello wrote: > @Dave: > > I was glancing at r8152 driver and notice that it has some special > handling for ipv6. Is this issue reproducing only in ipv6 for you? >

[Kernel-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Sponsored artful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1674680 Title: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README Status in bluez package in Ubuntu:

[Kernel-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

** Also affects: bluez (Ubuntu Artful) Importance: Low Status: New ** Tags removed: sts-sponsor-chiluk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1674680 Title:

[Kernel-packages] [Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name

@bybeu, please do not post questions like this to ancient bugs. Instead use askubuntu or ubuntuforums. Back to your problem at hand though. You are free to manually add your ssd's to the whitelist. Unfortunately the way you asked your question makes it very unclear what you've done or what

[Kernel-packages] [Bug 1705054] Re: Trusty kexec-tools suffer from upstream code regression. Fix not included.

@slashd beat me to the upload, but it looks good to me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1705054 Title: Trusty kexec-tools suffer from upstream code regression. Fix

[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

** Tags added: indeed -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status

[Kernel-packages] [Bug 1690512] Re: shutdown/restart/suspend freezes laptop on intel graphics

Please try the latest hwe stack by. I'm using kabylake + the hwe stack without issue at the moment. sudo apt install --install-recommends linux-generic-hwe-16.04 xserver- xorg-hwe-16.04 More info is available here. https://wiki.ubuntu.com/Kernel/LTSEnablementStack I'm also closing the

[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work

** Tags added: indeed -- 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/1591669 Title: duplicate touchpad reported and syndaemon/synclient does not work Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1527062] Re: XFS Deadlock on 4.2+

@lordbaco, are you still hitting this? Also please post your entire oops next time, as I can't do much with what you've posted. Also you might want to try moving up to the 4.4 kernel by installing linux-image-lts-xenial on trusty *(I think that's the package name). Marking this as fixed

[Kernel-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned

Just so you know I'm waiting for zesty release before uploading this. I don't want to risk causing issues on the release media. Additionally policy is to only push high priority bug fixes for the few weeks leading up to release. -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned

** Tags added: sts-sponsor-chiluk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1674680 Title: Deprecated rfcomm.conf still mentioned Status in bluez package in Ubuntu: New Status

[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain

@Kai-Heng have you been able to make any progress on this? I think Tim is simply waiting on a git branch or git send-email submission to the kernel-team mailing list. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned

** Also affects: bluez (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Yakkety) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu.

[Kernel-packages] [Bug 1674763] [NEW] Warnings then GPF originating from nouveau under zesty

Public bug reported: unity-settings-[4857]: failed to turn the kbd backlight off: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UPower.KbdBacklight' on object at path /org/freedesktop/UPower/KbdBacklight polkit-gnome-au[7926]: cannot open display: :0

[Kernel-packages] [Bug 1328088] Re: Kernel network namespace performance regression during rcu development on kernels above 3.8

@gnanasekarkas. Not that we know of. -- 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/1328088 Title: Kernel network namespace performance regression during rcu development on kernels

[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain

@Tim, When I checked the backport it was not a clean cherry-pick. As you mentioned earlier there was some prerequisite patches that git pulled in. I did not continue investigating, but I guess there should only be a few. Either way the patches seem nvme @Kai-Heng Feng, please make sure you

[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain

I can confirm Francois experience with my 950 pro. Although I saved one or two watts. It's a bit hard to tell. However my PC states were already reaching PC8 before this patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1639299] Re: acpi_pad consumes 100% of resources

** Also affects: linux (Ubuntu) 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/1639299 Title: acpi_pad consumes 100% of resources Status in

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

@djao, sorry for the slow response. I hit pc8 briefly, but that's with most everything tuned, and running nothing. Lots of applications seem to be pretty power hungry for me. That's going to have to get tackled by each upstream project before we integrate solutions into the distro. @fthx.

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: maas-images Status: New => Invalid -- 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/1639202

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

So apparently this is a feature of the dell-branded usb-c devices. Please see the knowledge base. http://www.dell.com/support/article/us/en/04/SLN301147 I've heard back from our contacts at dell, and the issue you are seeing is apparently resolved via a firmware update. -- You received this

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Another thought is that the pxe firmware of the usb-c device was missed in the rebranding process by dell. This is actually quite likely in my opinion. Either way we need to engage Dell in order to remedy this. -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

, and possibly also the firmware of the usb-c device? Thanks, Dave Chiluk -- 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/1639202 Title: Cannot enlist/commission machines in MAAS 2.1 with usb network

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Alright so the problem at present appears to be that the machine is pxe booting off of a nic with a mac address that is not showing up after the kernel boots. The way the boot works is the bios/efi launches a pxe network stack. This typically makes a dhcp request. The DHCP server responds with

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

One of my collegues informed me that maas 2.1 is meant to use https://images.maas.io/ephemeral-v3/daily/ Instead of the ephemeral-v2 images. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

1. So this indicates to me that the kernel is unable to control the usb device. When you mentioned earlier that you were able to investigate the usb-c device with a 16.04.1 machine, what exact kernel version was that machine running. uname -a output should be sufficient. 2. Can you similarly

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

If the device is not being detected I have a feeling there may be something going wrong with udev. -- 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/1639202 Title: Cannot enlist/commission

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

>From the initramfs shell can you provide me the output for ls -la /sys/class/net/* and cat /sys/class/net/*/address I have a feeling you'll only see lo and enx847beb55c195. Specifially I'm looking for the device name that matches your BOOTIF mac address. However if it's showing up please

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

So from the best I can determine it looks like configure_networking out of scripts/functions of the initramfs is failing to properly bring up the network device. I'm going through the process now to figure out what logic might actually be stopping it from functioning. I'll let you know more when

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

s output and am able to investigate the initramfs. Thanks ** Changed in: maas Status: Incomplete => Invalid ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Dave Chiluk (chiluk)

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

I just checked the maas daily images, and both the 4.4.0-45 xenial and 4.8.0-27 yakkety initrd contain the cdc_ether kernel drivers. I also checked the 20160310 maas image that contains the 4.4.0-11-generic kernel, and it contains the drivers as well. So I now suspect that the initramfs is not

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Please ignore the comment from brad-figg as the above comment originated from a bot. That being said, I've had a bit of an opportunity to research this. Initramfs-tools is responsible for updating the initramfs and including modules in the initramfs. Unfortunately I don't think that adding

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

** 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. https://bugs.launchpad.net/bugs/1639202 Title: Cannot enlist/commission machines in MAAS 2.1 with usb

[Kernel-packages] [Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

I'm adding the kernel to this, as I'm fairly certain the kernel is responsible for what modules are built into the default initramfs'. In this case it looks like cdc_ether and usbnet need to be added into the initramfs in order to solve a case like this. I'm not sure if this should be done in

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels >= 3.12

@evan No, you are seeing a different or new bug. -- 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/1338706 Title: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set

[Kernel-packages] [Bug 1628363] Re: VIA VL812 hub stops working with 4.4.0-40.60

** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1628363] Re: VIA VL812 hub stops working with 4.4.0-40.60

So I just rebooted 4 times with the -40 kernel, and everything seems to be going well. I'm going to chalk this one up to hardware misbehaving. At least until someone else hits this as well. Keep in mind the hub, does not work in usb 3.0 mode. That is not what this bug is about. -- You received

[Kernel-packages] [Bug 1628363] [NEW] VIA VL812 hub stops working with 4.4.0-40.60

Public bug reported: VIA VL812 hub stops working with 4.4.0-40.60. Works fine with 4.4.0-39.59. Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40 (previous boot). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.40.42 ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0

Marking verification-done-trusty, as the user has not replied back to me one way or the other so I'll assume their kernel is no longer getting allocation errors. I definitely don't want this pulled from the sources prematurely. ** Tags removed: verification-needed-trusty ** Tags added:

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

Closing as invalid, as the root cause was clearly the IMEI firmware in my case, and has since been verified. ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

IMEI firmware update definitely appears to be the fix as it is now verified independently. https://bugzilla.kernel.org/show_bug.cgi?id=116591 ** Bug watch added: Linux Kernel Bug Tracker #116591 http://bugzilla.kernel.org/show_bug.cgi?id=116591 -- You received this bug notification because

[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0

Fix submitted to kernel-t...@lists.ubuntu.com. ** Description changed: - [Impact] - * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc.

[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0

Shut the front door bug-bot. ** 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/1616193 Title: 3.13: libvirtd: page

[Kernel-packages] [Bug 1616193] [NEW] 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0

=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Dave Chiluk (chiluk) Status: New ** Tags: sts ** Attachment added: "Additiona

[Kernel-packages] [Bug 1581236] Re: Power state does not drop lower than pc03 for package (Haswell i7-4500U)

I was able to remove the nvidia card from my desktop and check again. Removing the nvidia card and enabling the integrated graphics resulted in my machine reaching pc6. So I'll leave this as expired for the time being. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

Personally I think we should modify MNTTAB in zfs-linux to point to /proc/self/mounts. This may not be completely straightforward *(there are a number of places that point to /etc/mnttab directly, or have logic around it and /proc/mounts), but it should be doable. I like this solution most

[Kernel-packages] [Bug 1607920] [NEW] zfs services fail on firstboot if zfs-utils is integrated into the deployment image

Public bug reported: [Impact] * zfs services fail on firstboot if zfs-utils is integrated into the deployment image. * Output from systemd - sudo systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● zfs-import-scan.service loaded failed failed Import ZFS pools by device scanning ●

[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

** Changed in: linux (Ubuntu Wily) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Vivid) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

Thanks guys, I really think the solution here will be to move onto the lts-xenial kernel as all others lts- kernels will be end of life shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1425803] Re: Driver problem with USB chipset VIA VL812-B2

"VIA Labs, Inc. (one of the largest manufacturers of USB 3.0 hub chipsets on the market) does not make an update program for Apple Mac OS X or Linux/Unix. " Vote with your wallets people. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1425803] Re: Driver problem with USB chipset VIA VL812-B2

@Warren, Has this been resolved yet in upstream? *(I'm asking for selfish reasons as I almost just bought one of these). Also if this still exists on the GenesysLogic 3520 (maybe 3521) hub that would likely require a separate change and as such should be a separate bug. -- You received this

[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

** 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/1378123 Title: unix_socket_abstract.sh triggers an AppArmor WARN Status in linux package in Ubuntu: Confirmed Bug

[Kernel-packages] [Bug 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

In case anyone else hits this on their laptop and would like to disable the auto-suspend, I installed dconf-editor, and changed critical- battery-action to nothing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

Sorry hit post too quickly. Anyhow, so it looks like upgrading the IMEI firmware now allows my amt/vpro capable laptop to reach low-power power pc-states. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

So I recently had to run a certain Microsoft OS while debugging another issue. I ran a number updates during that session. The most important of which was an IMEI firmware update. I can't prove for certain that the IMEI firmware update resolved this issue, but it is the mostly likely

[Kernel-packages] [Bug 1581236] Re: Power state does not drop lower than pc03 for package (Haswell i7-4500U)

@Greg Our Haswell servers aren't seeing this, but one of my desktops is. By chance do you happen to have an nvidia card in that machine? I've been meaning to rip it out of my desktop and try again, but I haven't found the time. Also please run apport-collect and upload the logs to this case.

[Kernel-packages] [Bug 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

fantastically. Shame on me for suspecting our beloved OS. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: upower (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed i

[Kernel-packages] [Bug 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

Here's a log of me pulling power, and plugging it back in. ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Attachment added: "upower.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588944/+attachment/4679103/+files/upower.out -- You received this

[Kernel-packages] [Bug 1580272] Re: i915-bpo crashes on external hdmi input

Running 4.4.0-23-generic, I see the same errors as https://bugs.freedesktop.org/show_bug.cgi?id=89055 I see [ 1248.953987] PM: early resume of devices complete after 6.795 msecs [ 1248.956059] rtc_cmos 00:02: System wakeup disabled by ACPI [ 1249.227488] usb 1-8: reset high-speed USB device

[Kernel-packages] [Bug 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

So as I haven't really messed with power monitoring, I discovered upower --monitor-detail. After having been unplugged for a few minutes the below state change occurred. I'm open to advice on how to continue looking into this. My first guess is to open the upower sources to see where it's

  1   2   3   >