[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I am getting this error and cannot even boot Ubuntu 22.04.1 from a live
USB. I am using an HP Elite Dragonfly G2 with 16GB of RAM. I get an
error: out of memory message then a kernel panic. Please fix this, I
would very much like to try running Ubuntu but I have to run Fedora 36
instead due to the fact that I can't even boot Ubuntu because of this
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
*
[Kernel-packages] [Bug 1885574] Re: Lenovo Ideapad S740 touchscreen is not working
I have a Lenovo Ideapad S740-15IRH and the touchscreen does not work in linux on any distro even with the latest kernel 5.14.14. Is it possible to fix this? ** Changed in: linux (Ubuntu) Status: Expired => 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/1885574 Title: Lenovo Ideapad S740 touchscreen is not working Status in linux package in Ubuntu: Confirmed Bug description: 5.4.0-39-lowlatency on Ubuntu 20.04 LTS Computer is lenovo ideapad s740 I tried to sudo usbhid-dump -es and touch the screen but no output. I've opened a ticket with lenovo: https://forums.lenovo.com/t5/Lenovo- IdeaPad-1xx-3xx-5xx-7xx-Edge-LaVie-Z-Flex- Notebooks/Ideapad-s740-touchscreen-not-working/m-p/5023332 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Same issue with the brightness keys on the HP Elite Dragonfly G2, even on kernel 5.13. Seems like a firmware bug, but may have something to do with the HP WMI keycode driver. Really annoying and not at all good for such an expensive product. This needs to be fixed, it affects most of HP's new business laptops. Could someone describe how to do the power reset please? -- 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/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Invalid Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694561] Re: kernel panic attempting to boot kernel 4.12-rc3
I am unable to run apport-collect running 4.12-rc3, because I cannot actually boot my computer (an immediate kernel panic occurs, as evidenced by adding the output from earlyprintk=efi), so I'm marking this bug as confirmed. Please also see relevant discussion about this issue on the Linux Kernel mailing list: http://lkml.iu.edu/hypermail/linux/kernel/1705.3/04549.html ** 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/1694561 Title: kernel panic attempting to boot kernel 4.12-rc3 Status in linux package in Ubuntu: Confirmed Bug description: I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In short, I am completely unable to boot kernel 4.12-rc3, even though I could boot from 4.12-rc2 perfectly fine. The loading screen does not appear at all, instead GRUB remains stuck on "Loading initial ramdisk ...". Please help. I don't know how to identify what is wrong because I am completely unable to boot the OS to begin with. Needless to say, this is a major problem. Here is my hardware: H/W path Device Class Description system HP Spectre x360 Convertible (N5R94UA) /0bus802D /0/0 memory 64KiB BIOS /0/10 memory 32KiB L1 cache /0/11 memory 32KiB L1 cache /0/12 memory 256KiB L2 cache /0/13 memory 4MiB L3 cache /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GH /0/16 memory 8GiB System Memory /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz /0/100bridge Broadwell-U Host Bridge -OPI /0/100/2 displayBroadwell-U Integrated Graphics /0/100/3 multimedia Broadwell-U Audio Controller /0/100/14 busWildcat Point-LP USB xHCI Controller /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/1 input USB Receiver /0/100/14/0/3 multimedia HP Truevision Full HD /0/100/14/0/4 input Touchscreen /0/100/14/0/5 input ITE Device(8350) /0/100/14/0/7 communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/16 communication Wildcat Point-LP MEI Controller #1 /0/100/1c bridge Wildcat Point-LP PCI Express Root Port /0/100/1c/0 genericRTS5227 PCI Express Card Reader /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port /0/100/1c.2/0 wlo1 networkWireless 7265 /0/100/1f bridge Wildcat Point-LP LPC Controller /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI /0/100/1f.3 busWildcat Point-LP SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume /0/1/0.0.0/2 /dev/sda2 volume 99MiB Windows FAT volume /0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition /0/1/0.0.0/4 /dev/sda4 volume 15EiB Windows FAT volume /0/1/0.0.0/5 /dev/sda5 volume 838MiB Windows NTFS volume /0/1/0.0.0/6 /dev/sda6 volume 146GiB Windows NTFS volume /0/1/0.0.0/7 /dev/sda7 volume 89GiB EXT4 volume /0/1/0.0.0/8 /dev/sda8 volume 8099MiB Linux swap volume /1power PK03056XL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694561] Re: kernel panic attempting to boot kernel 4.12-rc3
It appears a kernel panic is happening immediately while attempting to boot 4.12-rc3, it doesn't happen on 4.12-rc2. Adding earlyprintk=efi to the grub command line options, I get the following message (which explains why the bootloader stops at 'loading initial ramdisk...'): This was meticulously copied from a photo of a GRUB screen, this change is undoubtedly the culprit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/arch/x86/mm/pat.c?id=v4.12-rc3=v4.12-rc2 (direct commit at) https://github.com/torvalds/linux/commit/cbed27cdf0e3f7ea3b2259e86b9e34df02be3fe4 [0.00] Kernel panic - not syncing: x86/PAT: PAT enabled, but not supported by secondary CPU [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.12.0-041200rc3-generic #201705282131 [0.00] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [0.00] Call Trace: [0.00] dump_stack+0x63/0x8d [0.00] panic+0xe4/0x22d [0.00] pat_init+0x13d/0x140 [0.00] generic_set_all+0x1ab/0x300 [0.00] mtrr_bp_init+0x1e5/0x227 [0.00] setup_arch+0x53a/0xca8 [0.00] ? printk+0x52/0x6e [0.00] ? early_idt_handler_array+0x120/0x120 [0.00] start_kernel+0xb7/0x46c [0.00] ? early_idt_handler_array+0x120/0x120 [0.00] x86_64_start_reservations+0x29/0x2b [0.00] x86_64_start_kernel+0x154/0x177 [0.00] secondary_startup_64+0x9f/0x9f [0.00] ---[ end Kernel panic - not syncing: x86/PAT: PAT enabled, but not supported by secondary CPU [0.00] This change causes a kernel panic on my Intel 5500U processor, I literally cannot boot my computer. This commit results in a serious regression for multicore Intel CPUs, 4.12-rc3 and drm-tip result in an immediate kernel panic attempting to boot. This is unacceptable. -- 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/1694561 Title: kernel panic attempting to boot kernel 4.12-rc3 Status in linux package in Ubuntu: New Bug description: I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In short, I am completely unable to boot kernel 4.12-rc3, even though I could boot from 4.12-rc2 perfectly fine. The loading screen does not appear at all, instead GRUB remains stuck on "Loading initial ramdisk ...". Please help. I don't know how to identify what is wrong because I am completely unable to boot the OS to begin with. Needless to say, this is a major problem. Here is my hardware: H/W path Device Class Description system HP Spectre x360 Convertible (N5R94UA) /0bus802D /0/0 memory 64KiB BIOS /0/10 memory 32KiB L1 cache /0/11 memory 32KiB L1 cache /0/12 memory 256KiB L2 cache /0/13 memory 4MiB L3 cache /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GH /0/16 memory 8GiB System Memory /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz /0/100bridge Broadwell-U Host Bridge -OPI /0/100/2 displayBroadwell-U Integrated Graphics /0/100/3 multimedia Broadwell-U Audio Controller /0/100/14 busWildcat Point-LP USB xHCI Controller /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/1 input USB Receiver /0/100/14/0/3 multimedia HP Truevision Full HD /0/100/14/0/4 input Touchscreen /0/100/14/0/5 input ITE Device(8350) /0/100/14/0/7 communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/16 communication Wildcat Point-LP MEI Controller #1 /0/100/1c bridge Wildcat Point-LP PCI Express Root Port /0/100/1c/0 genericRTS5227 PCI Express Card Reader /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port /0/100/1c.2/0 wlo1 networkWireless 7265 /0/100/1f bridge Wildcat Point-LP LPC Controller /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI /0/100/1f.3 busWildcat Point-LP SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS
[Kernel-packages] [Bug 1694561] [NEW] kernel panic attempting to boot kernel 4.12-rc3
Public bug reported: I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In short, I am completely unable to boot kernel 4.12-rc3, even though I could boot from 4.12-rc2 perfectly fine. The loading screen does not appear at all, instead GRUB remains stuck on "Loading initial ramdisk ...". Please help. I don't know how to identify what is wrong because I am completely unable to boot the OS to begin with. Needless to say, this is a major problem. Here is my hardware: H/W path Device Class Description system HP Spectre x360 Convertible (N5R94UA) /0bus802D /0/0 memory 64KiB BIOS /0/10 memory 32KiB L1 cache /0/11 memory 32KiB L1 cache /0/12 memory 256KiB L2 cache /0/13 memory 4MiB L3 cache /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GH /0/16 memory 8GiB System Memory /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz /0/100bridge Broadwell-U Host Bridge -OPI /0/100/2 displayBroadwell-U Integrated Graphics /0/100/3 multimedia Broadwell-U Audio Controller /0/100/14 busWildcat Point-LP USB xHCI Controller /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/1 input USB Receiver /0/100/14/0/3 multimedia HP Truevision Full HD /0/100/14/0/4 input Touchscreen /0/100/14/0/5 input ITE Device(8350) /0/100/14/0/7 communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/16 communication Wildcat Point-LP MEI Controller #1 /0/100/1c bridge Wildcat Point-LP PCI Express Root Port /0/100/1c/0 genericRTS5227 PCI Express Card Reader /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port /0/100/1c.2/0 wlo1 networkWireless 7265 /0/100/1f bridge Wildcat Point-LP LPC Controller /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI /0/100/1f.3 busWildcat Point-LP SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume /0/1/0.0.0/2 /dev/sda2 volume 99MiB Windows FAT volume /0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition /0/1/0.0.0/4 /dev/sda4 volume 15EiB Windows FAT volume /0/1/0.0.0/5 /dev/sda5 volume 838MiB Windows NTFS volume /0/1/0.0.0/6 /dev/sda6 volume 146GiB Windows NTFS volume /0/1/0.0.0/7 /dev/sda7 volume 89GiB EXT4 volume /0/1/0.0.0/8 /dev/sda8 volume 8099MiB Linux swap volume /1power PK03056XL ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-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/1694561 Title: kernel panic attempting to boot kernel 4.12-rc3 Status in linux package in Ubuntu: New Bug description: I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In short, I am completely unable to boot kernel 4.12-rc3, even though I could boot from 4.12-rc2 perfectly fine. The loading screen does not appear at all, instead GRUB remains stuck on "Loading initial ramdisk ...". Please help. I don't know how to identify what is wrong because I am completely unable to boot the OS to begin with. Needless to say, this is a major problem. Here is my hardware: H/W path Device Class Description system HP Spectre x360 Convertible (N5R94UA) /0bus802D /0/0 memory 64KiB BIOS /0/10 memory 32KiB L1 cache /0/11 memory 32KiB L1 cache /0/12 memory 256KiB L2 cache /0/13 memory 4MiB L3 cache /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GH /0/16 memory 8GiB System Memory /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz
[Kernel-packages] [Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
This was fixed in 4.12-rc2! ** 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. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption Status in linux package in Ubuntu: Fix Released Bug description: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ? kmem_cache_alloc_trace+0x181/0x190 [9.574993] fuse_fill_super+0x3b3/0x6a0 [9.574995] ? vsnprintf+0x24b/0x4d0 [9.574997] ? snprintf+0x45/0x70 [9.574998] mount_bdev+0x178/0x1b0 [9.575000] ? mount_bdev+0x178/0x1b0 [9.575001] ? fuse_get_root_inode+0x70/0x70 [9.575003] fuse_mount_blk+0x15/0x20 [9.575005] mount_fs+0x38/0x140 [9.575008] vfs_kern_mount+0x67/0x110 [9.575009] do_mount+0x1e1/0xca0 [9.575011] ? __check_object_size+0xb3/0x190 [9.575013] ? _copy_from_user+0x21/0x70 [9.575015] ? kmem_cache_alloc_trace+0x142/0x190 [9.575016] SyS_mount+0x83/0xd0 [9.575019] entry_SYSCALL_64_fastpath+0x1e/0xa9 [9.575020] RIP: 0033:0x7f2025679faa [9.575021] RSP: 002b:7fffa89e0358 EFLAGS: 0246 ORIG_RAX: 00a5 [9.575023] RAX: ffda RBX: RCX: 7f2025679faa [9.575024] RDX:
[Kernel-packages] [Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
Seems this was resolved in 4.12-rc2, mounting ntfs-3g volumes is fine,
doesn't generate a kernel warning! It was fixed in fs/fuse/inode.c at
https://github.com/torvalds/linux/commit/69c8ebf83213e6165b13d94ec599b861467ee2dc
with
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 5a1b58f..65c8837 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -975,8 +975,15 @@ static int fuse_bdi_init(struct fuse_conn *fc, struct
super_block *sb)
int err;
char *suffix = "";
- if (sb->s_bdev)
+ if (sb->s_bdev) {
suffix = "-fuseblk";
+ /*
+* sb->s_bdi points to blkdev's bdi however we want to redirect
+* it to our private bdi...
+*/
+ bdi_put(sb->s_bdi);
+ sb->s_bdi = _backing_dev_info;
+ }
err = super_setup_bdi_name(sb, "%u:%u%s", MAJOR(fc->dev),
MINOR(fc->dev), suffix);
if (err)
** No longer affects: fuse (Ubuntu)
** No longer affects: ntfs-3g (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/1692143
Title:
fs changes in kernel 4.12 break mount of ntfs-3g, possible data
corruption
Status in linux package in Ubuntu:
Fix Released
Bug description:
Mounting any ntfs partition or ntfs-formatted external drive in kernel
4.12 results in a critical kernel warning. Possible data corruption
could happen, as the drive must be forcibly unmounted. The kernel
warning appears in the syslog literally every single time, this is a
very reproducible bug. The same warning/stack trace all pointing to
the function super_setup_bdi_name in /linux/fs/super.c:1281 along with
related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu
16.10. and Ubuntu 17.04. Here I will only include the information
relevant to my installation of 16.04.2 LTS. This seems rather
critical, as ntfs is one of the only suitable formats supported by
(and shareable between) Windows and Linux, and I worry that possible
data corruption could be happening.
[9.574893] [ cut here ]
[9.574898] WARNING: CPU: 0 PID: 608 at
/home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0
[9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal
intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul
snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi
mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567
aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd
snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c
snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm
snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev
videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d
videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel
hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d
hid_sensor_trigger
[9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common
hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me
soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless
snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core
i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap
acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4
hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915
rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt
fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid
sdhci hid
[9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted
4.12.0-041200rc1-generic #201705131731
[9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS
F.45 04/21/2017
[9.574974] task: 9cef7d14c380 task.stack: aff881488000
[9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0
[9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283
[9.574978] RAX: RBX: 9cef7b3d2400 RCX:
0002
[9.574979] RDX: 0001 RSI: fe01 RDI:
ad7d81bb
[9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09:
[9.574981] R10: f28cc8f45c00 R11: R12:
9cef7d277000
[9.574982] R13: ae2d914c R14: aff88148bce0 R15:
9cef7b2c3200
[9.574983] FS: 7f2025fa8700() GS:9cef8ec0()
knlGS:
[9.574984] CS: 0010 DS: ES: CR0: 80050033
[9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4:
003406f0
[9.574986] Call Trace:
[9.574990]
[Kernel-packages] [Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
Okay, so the warning is clearly being generated by the WARN_ON function in fs/super.c. I realize I could disable the warning, but that sounds like a bad idea. One question though, why would we be verifying if sb->s_bdi is equal to the address of some "struct backing_dev_info noop_backing_dev_info" from either the files /include/linux/backing-dev.h or /mm/backing-dev.c (Found references to definition of this struct in these two file using the power of grep -rl) in fs/super.c on line 1281, when we reassign it anyway to a local variable bdi right after? In other words, IS there something going wrong here, or is this warning insignificant and should be removed? 1281: WARN_ON(sb->s_bdi != _backing_dev_info); 1282: sb->s_bdi = bdi; Also see bug report I filed about this problem at https://bugzilla.kernel.org/show_bug.cgi?id=195809 ** Bug watch added: Linux Kernel Bug Tracker #195809 https://bugzilla.kernel.org/show_bug.cgi?id=195809 -- 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/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption Status in fuse package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in ntfs-3g package in Ubuntu: New Bug description: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ?
[Kernel-packages] [Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879845/+files/dmesg.log -- 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/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption Status in fuse package in Ubuntu: New Status in linux package in Ubuntu: New Status in ntfs-3g package in Ubuntu: New Bug description: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ? kmem_cache_alloc_trace+0x181/0x190 [9.574993] fuse_fill_super+0x3b3/0x6a0 [9.574995] ? vsnprintf+0x24b/0x4d0 [9.574997] ? snprintf+0x45/0x70 [9.574998] mount_bdev+0x178/0x1b0 [9.575000] ? mount_bdev+0x178/0x1b0 [9.575001] ? fuse_get_root_inode+0x70/0x70 [9.575003] fuse_mount_blk+0x15/0x20 [9.575005] mount_fs+0x38/0x140 [9.575008] vfs_kern_mount+0x67/0x110 [9.575009] do_mount+0x1e1/0xca0 [9.575011] ? __check_object_size+0xb3/0x190 [9.575013] ? _copy_from_user+0x21/0x70 [9.575015] ? kmem_cache_alloc_trace+0x142/0x190 [9.575016] SyS_mount+0x83/0xd0 [9.575019] entry_SYSCALL_64_fastpath+0x1e/0xa9 [9.575020] RIP: 0033:0x7f2025679faa [9.575021] RSP: 002b:7fffa89e0358 EFLAGS: 0246 ORIG_RAX: 00a5 [
[Kernel-packages] [Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879846/+files/lspci-vvnn.log -- 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/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption Status in fuse package in Ubuntu: New Status in linux package in Ubuntu: New Status in ntfs-3g package in Ubuntu: New Bug description: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ? kmem_cache_alloc_trace+0x181/0x190 [9.574993] fuse_fill_super+0x3b3/0x6a0 [9.574995] ? vsnprintf+0x24b/0x4d0 [9.574997] ? snprintf+0x45/0x70 [9.574998] mount_bdev+0x178/0x1b0 [9.575000] ? mount_bdev+0x178/0x1b0 [9.575001] ? fuse_get_root_inode+0x70/0x70 [9.575003] fuse_mount_blk+0x15/0x20 [9.575005] mount_fs+0x38/0x140 [9.575008] vfs_kern_mount+0x67/0x110 [9.575009] do_mount+0x1e1/0xca0 [9.575011] ? __check_object_size+0xb3/0x190 [9.575013] ? _copy_from_user+0x21/0x70 [9.575015] ? kmem_cache_alloc_trace+0x142/0x190 [9.575016] SyS_mount+0x83/0xd0 [9.575019] entry_SYSCALL_64_fastpath+0x1e/0xa9 [9.575020] RIP: 0033:0x7f2025679faa [9.575021] RSP: 002b:7fffa89e0358 EFLAGS: 0246 ORIG_RAX:
[Kernel-packages] [Bug 1692143] [NEW] fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
Public bug reported: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ? kmem_cache_alloc_trace+0x181/0x190 [9.574993] fuse_fill_super+0x3b3/0x6a0 [9.574995] ? vsnprintf+0x24b/0x4d0 [9.574997] ? snprintf+0x45/0x70 [9.574998] mount_bdev+0x178/0x1b0 [9.575000] ? mount_bdev+0x178/0x1b0 [9.575001] ? fuse_get_root_inode+0x70/0x70 [9.575003] fuse_mount_blk+0x15/0x20 [9.575005] mount_fs+0x38/0x140 [9.575008] vfs_kern_mount+0x67/0x110 [9.575009] do_mount+0x1e1/0xca0 [9.575011] ? __check_object_size+0xb3/0x190 [9.575013] ? _copy_from_user+0x21/0x70 [9.575015] ? kmem_cache_alloc_trace+0x142/0x190 [9.575016] SyS_mount+0x83/0xd0 [9.575019] entry_SYSCALL_64_fastpath+0x1e/0xa9 [9.575020] RIP: 0033:0x7f2025679faa [9.575021] RSP: 002b:7fffa89e0358 EFLAGS: 0246 ORIG_RAX: 00a5 [9.575023] RAX: ffda RBX: RCX: 7f2025679faa [9.575024] RDX: 5633569a95a0 RSI: 5633569a8430 RDI: 5633569a8760 [9.575025] RBP: 7fffa89df0f0 R08: 5633569a8620 R09: 0028 [9.575026] R10: 000e R11: 0246 R12: 5633569a8430 [9.575026] R13: 5633560b287f R14: 7fffa89df238 R15: 0001 [9.575028] Code: a0 65 48 33 0c 25 28 00 00 00 75 2a 48 83 c4 58 5b 41 5a 41 5c 41 5d 41 5e 5d c3 48 89 df 89 45 84 e8 f6 10 f9 ff 8b 45 84 eb d2 <0f> ff eb c6 b8 f4 ff ff ff eb c7 e8 01 d5 e3 ff 90 0f 1f
[Kernel-packages] [Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879847/+files/uname-a.log -- 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/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption Status in fuse package in Ubuntu: New Status in linux package in Ubuntu: New Status in ntfs-3g package in Ubuntu: New Bug description: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ? kmem_cache_alloc_trace+0x181/0x190 [9.574993] fuse_fill_super+0x3b3/0x6a0 [9.574995] ? vsnprintf+0x24b/0x4d0 [9.574997] ? snprintf+0x45/0x70 [9.574998] mount_bdev+0x178/0x1b0 [9.575000] ? mount_bdev+0x178/0x1b0 [9.575001] ? fuse_get_root_inode+0x70/0x70 [9.575003] fuse_mount_blk+0x15/0x20 [9.575005] mount_fs+0x38/0x140 [9.575008] vfs_kern_mount+0x67/0x110 [9.575009] do_mount+0x1e1/0xca0 [9.575011] ? __check_object_size+0xb3/0x190 [9.575013] ? _copy_from_user+0x21/0x70 [9.575015] ? kmem_cache_alloc_trace+0x142/0x190 [9.575016] SyS_mount+0x83/0xd0 [9.575019] entry_SYSCALL_64_fastpath+0x1e/0xa9 [9.575020] RIP: 0033:0x7f2025679faa [9.575021] RSP: 002b:7fffa89e0358 EFLAGS: 0246 ORIG_RAX: 00a5
[Kernel-packages] [Bug 1692143] Re: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879867/+files/version.log ** Also affects: ntfs-3g (Ubuntu) Importance: Undecided Status: New ** Also affects: fuse (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/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption Status in fuse package in Ubuntu: New Status in linux package in Ubuntu: New Status in ntfs-3g package in Ubuntu: New Bug description: Mounting any ntfs partition or ntfs-formatted external drive in kernel 4.12 results in a critical kernel warning. Possible data corruption could happen, as the drive must be forcibly unmounted. The kernel warning appears in the syslog literally every single time, this is a very reproducible bug. The same warning/stack trace all pointing to the function super_setup_bdi_name in /linux/fs/super.c:1281 along with related calls to fuse functions appears in Ubuntu 16.04 LTS, Ubuntu 16.10. and Ubuntu 17.04. Here I will only include the information relevant to my installation of 16.04.2 LTS. This seems rather critical, as ntfs is one of the only suitable formats supported by (and shareable between) Windows and Linux, and I worry that possible data corruption could be happening. [9.574893] [ cut here ] [9.574898] WARNING: CPU: 0 PID: 608 at /home/kernel/COD/linux/fs/super.c:1281 super_setup_bdi_name+0xcf/0xe0 [9.574899] Modules linked in: hp_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass crct10dif_pclmul snd_soc_rt298 crc32_pclmul ghash_clmulni_intel pcbc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_intel snd_hda_codec snd_soc_rt286 snd_hda_core snd_soc_ssm4567 aesni_intel snd_soc_rl6347a snd_hwdep iwlwifi aes_x86_64 crypto_simd snd_soc_core rtsx_pci_ms cfg80211 glue_helper memstick snd_compress elan_i2c snd_pcm_dmaengine ac97_bus cryptd intel_cstate intel_rapl_perf snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq uvcvideo joydev videobuf2_vmalloc input_leds videobuf2_memops btusb hid_sensor_incl_3d videobuf2_v4l2 hid_sensor_rotation btrtl videobuf2_core btbcm btintel hid_sensor_gyro_3d hid_sensor_accel_3d videodev hid_sensor_magn_3d hid_sensor_trigger [9.574937] bluetooth industrialio_triggered_buffer hid_sensor_iio_common hid_multitouch media lpc_ich ecdh_generic snd_seq_device snd_timer snd mei_me soundcore shpchp mei hp_accel lis3lv02d snd_soc_sst_acpi dw_dmac hp_wireless snd_soc_sst_match input_polldev 8250_dw spi_pxa2xx_platform dw_dmac_core i2c_designware_platform mac_hid i2c_designware_core intel_vbtn sparse_keymap acpi_als acpi_pad kfifo_buf industrialio parport_pc ppdev lp parport autofs4 hid_logitech_hidpp hid_sensor_custom hid_sensor_hub hid_logitech_dj usbhid i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm psmouse libahci rtsx_pci wmi video sdhci_acpi i2c_hid sdhci hid [9.574972] CPU: 0 PID: 608 Comm: mount.ntfs-3g Not tainted 4.12.0-041200rc1-generic #201705131731 [9.574972] Hardware name: HP HP Spectre x360 Convertible /802D, BIOS F.45 04/21/2017 [9.574974] task: 9cef7d14c380 task.stack: aff881488000 [9.574976] RIP: 0010:super_setup_bdi_name+0xcf/0xe0 [9.574977] RSP: 0018:aff88148bc50 EFLAGS: 00010283 [9.574978] RAX: RBX: 9cef7b3d2400 RCX: 0002 [9.574979] RDX: 0001 RSI: fe01 RDI: ad7d81bb [9.574980] RBP: aff88148bcd0 R08: 9cef8233c6f8 R09: [9.574981] R10: f28cc8f45c00 R11: R12: 9cef7d277000 [9.574982] R13: ae2d914c R14: aff88148bce0 R15: 9cef7b2c3200 [9.574983] FS: 7f2025fa8700() GS:9cef8ec0() knlGS: [9.574984] CS: 0010 DS: ES: CR0: 80050033 [9.574985] CR2: 5617f917e058 CR3: 00024258e000 CR4: 003406f0 [9.574986] Call Trace: [9.574990] ? kmem_cache_alloc_trace+0x181/0x190 [9.574993] fuse_fill_super+0x3b3/0x6a0 [9.574995] ? vsnprintf+0x24b/0x4d0 [9.574997] ? snprintf+0x45/0x70 [9.574998] mount_bdev+0x178/0x1b0 [9.575000] ? mount_bdev+0x178/0x1b0 [9.575001] ? fuse_get_root_inode+0x70/0x70 [9.575003] fuse_mount_blk+0x15/0x20 [9.575005] mount_fs+0x38/0x140 [9.575008] vfs_kern_mount+0x67/0x110 [9.575009] do_mount+0x1e1/0xca0 [9.575011] ? __check_object_size+0xb3/0x190 [9.575013] ? _copy_from_user+0x21/0x70 [9.575015] ? kmem_cache_alloc_trace+0x142/0x190 [9.575016] SyS_mount+0x83/0xd0 [9.575019]
[Kernel-packages] [Bug 1677175] Re: network-manager 1.2.6 won't connect to vpn and displays false connected message
** No longer affects: linux (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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-19 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: network-manager 1.2.2-0ubuntu0.16.04.4 PackageArchitecture: amd64 Tags: xenial Uname: Linux 4.9.16 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1677175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677175] Re: network-manager 1.2.6 won't connect to vpn and displays false connected message
apport information ** Tags added: apport-collected xenial ** Description changed: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-03-19 (10 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + Package: network-manager 1.2.2-0ubuntu0.16.04.4 + PackageArchitecture: amd64 + Tags: xenial + Uname: Linux 4.9.16 x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850127/+files/Dependencies.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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-19 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: network-manager 1.2.2-0ubuntu0.16.04.4 PackageArchitecture: amd64 Tags: xenial Uname: Linux 4.9.16 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677175] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850129/+files/ProcEnviron.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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-19 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: network-manager 1.2.2-0ubuntu0.16.04.4 PackageArchitecture: amd64 Tags: xenial Uname: Linux 4.9.16 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677175] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850128/+files/JournalErrors.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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-19 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: network-manager 1.2.2-0ubuntu0.16.04.4 PackageArchitecture: amd64 Tags: xenial Uname: Linux 4.9.16 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677175] [NEW] network-manager 1.2.6 won't connect to vpn and displays false connected message
Public bug reported: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager openvpn vpn ** Also affects: network-manager (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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
Yes, this problem most definitely occurs with the Yakkety proposed kernel, I tried using the most recent build of 16.10 that comes with 4.8, and the graphical problems persist. -- 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/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Bug description: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics Here is my system configuration: H/W path Device Class Description system HP Spectre x360 Convertible (N5R94UA#ABA) /0bus802D /0/0 memory 64KiB BIOS /0/10 memory 32KiB L1 cache /0/11 memory 32KiB L1 cache /0/12 memory 256KiB L2 cache /0/13 memory 4MiB L3 cache /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz /0/16 memory 8GiB System Memory /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz (0.6 ns) /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz (0.6 ns) /0/100bridge Broadwell-U Host Bridge -OPI /0/100/2 displayBroadwell-U Integrated Graphics /0/100/3 multimedia Broadwell-U Audio Controller /0/100/14 busWildcat Point-LP USB xHCI Controller /0/100/14/0usb2 busxHCI Host Controller /0/100/14/1usb1 busxHCI Host Controller /0/100/14/1/1 input USB Receiver /0/100/14/1/3 multimedia HP Truevision Full HD /0/100/14/1/4 input Touchscreen /0/100/14/1/5 input ITE Device(8350) /0/100/14/1/7 communication Bluetooth wireless interface /0/100/16 communication Wildcat Point-LP MEI Controller #1 /0/100/1b multimedia Wildcat Point-LP High Definition Audio Controller /0/100/1c bridge Wildcat Point-LP PCI Express Root Port #2 /0/100/1c/0 genericRTS5227 PCI Express Card Reader /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port #3 /0/100/1c.2/0 wlo1 networkWireless 7265 /0/100/1f bridge Wildcat Point-LP LPC Controller /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI Mode] /0/100/1f.3 busWildcat Point-LP SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume /0/1/0.0.0/2 /dev/sda2 volume 98MiB Windows FAT volume /0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition /0/1/0.0.0/4 /dev/sda4 volume 15EiB Windows FAT volume /0/1/0.0.0/5 /dev/sda5 volume 807MiB Windows NTFS volume /0/1/0.0.0/6 /dev/sda6 volume 97GiB Windows NTFS volume /0/1/0.0.0/7 /dev/sda7 volume 89GiB EXT4 volume /0/1/0.0.0/8 /dev/sda8 volume 8098MiB Linux swap volume /1power PK03056XL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
All kernels after 4.7.4 have this exact same issue with Broadwell integrated graphics, including the official 4.8 release and the previous rc builds. -- 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/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U Status in linux package in Ubuntu: Incomplete Bug description: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics Here is my system configuration: H/W path Device Class Description system HP Spectre x360 Convertible (N5R94UA#ABA) /0bus802D /0/0 memory 64KiB BIOS /0/10 memory 32KiB L1 cache /0/11 memory 32KiB L1 cache /0/12 memory 256KiB L2 cache /0/13 memory 4MiB L3 cache /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz /0/16 memory 8GiB System Memory /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz (0.6 ns) /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz (0.6 ns) /0/100bridge Broadwell-U Host Bridge -OPI /0/100/2 displayBroadwell-U Integrated Graphics /0/100/3 multimedia Broadwell-U Audio Controller /0/100/14 busWildcat Point-LP USB xHCI Controller /0/100/14/0usb2 busxHCI Host Controller /0/100/14/1usb1 busxHCI Host Controller /0/100/14/1/1 input USB Receiver /0/100/14/1/3 multimedia HP Truevision Full HD /0/100/14/1/4 input Touchscreen /0/100/14/1/5 input ITE Device(8350) /0/100/14/1/7 communication Bluetooth wireless interface /0/100/16 communication Wildcat Point-LP MEI Controller #1 /0/100/1b multimedia Wildcat Point-LP High Definition Audio Controller /0/100/1c bridge Wildcat Point-LP PCI Express Root Port #2 /0/100/1c/0 genericRTS5227 PCI Express Card Reader /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port #3 /0/100/1c.2/0 wlo1 networkWireless 7265 /0/100/1f bridge Wildcat Point-LP LPC Controller /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI Mode] /0/100/1f.3 busWildcat Point-LP SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume /0/1/0.0.0/2 /dev/sda2 volume 98MiB Windows FAT volume /0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition /0/1/0.0.0/4 /dev/sda4 volume 15EiB Windows FAT volume /0/1/0.0.0/5 /dev/sda5 volume 807MiB Windows NTFS volume /0/1/0.0.0/6 /dev/sda6 volume 97GiB Windows NTFS volume /0/1/0.0.0/7 /dev/sda7 volume 89GiB EXT4 volume /0/1/0.0.0/8 /dev/sda8 volume 8098MiB Linux swap volume /1power PK03056XL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
** Description changed: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. + + I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel + Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics ** Description changed: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics + + Here is my system configuration: + + H/W path Device Class Description + + system HP Spectre x360 Convertible (N5R94UA#AB + /0bus802D + /0/0 memory 64KiB BIOS + /0/10 memory 32KiB L1 cache + /0/11 memory 32KiB L1 cache + /0/12 memory 256KiB L2 cache + /0/13 memory 4MiB L3 cache + /0/14 processor Intel(R) Core(TM) i7-5500U CPU @ 2.40GH + /0/16 memory 8GiB System Memory + /0/16/0 memory 4GiB Row of chips Synchronous 1600 MHz + /0/16/1 memory 4GiB Row of chips Synchronous 1600 MHz + /0/100bridge Broadwell-U Host Bridge -OPI + /0/100/2 displayBroadwell-U Integrated Graphics + /0/100/3 multimedia Broadwell-U Audio Controller + /0/100/14 busWildcat Point-LP USB xHCI Controller + /0/100/14/0usb2 busxHCI Host Controller + /0/100/14/1usb1 busxHCI Host Controller + /0/100/14/1/1 input USB Receiver + /0/100/14/1/3 multimedia HP Truevision Full HD + /0/100/14/1/4 input Touchscreen + /0/100/14/1/5 input ITE Device(8350) + /0/100/14/1/7 communication Bluetooth wireless interface + /0/100/16 communication Wildcat Point-LP MEI Controller #1 + /0/100/1b multimedia Wildcat Point-LP High Definition Audio + /0/100/1c bridge Wildcat Point-LP PCI Express Root Port + /0/100/1c/0 genericRTS5227 PCI Express Card Reader + /0/100/1c.2 bridge Wildcat Point-LP PCI Express Root Port + /0/100/1c.2/0 wlo1 networkWireless 7265 + /0/100/1f bridge Wildcat Point-LP LPC Controller + /0/100/1f.2 storageWildcat Point-LP SATA Controller [AHCI + /0/100/1f.3 busWildcat Point-LP SMBus Controller + /0/1 scsi0 storage + /0/1/0.0.0 /dev/sda disk 512GB SAMSUNG MZNTE512 + /0/1/0.0.0/1 /dev/sda1 volume 449MiB Windows NTFS volume + /0/1/0.0.0/2 /dev/sda2 volume 98MiB Windows FAT volume + /0/1/0.0.0/3 /dev/sda3 volume 15MiB reserved partition + /0/1/0.0.0/4 /dev/sda4 volume 15EiB Windows FAT volume + /0/1/0.0.0/5 /dev/sda5 volume 807MiB Windows NTFS volume + /0/1/0.0.0/6 /dev/sda6 volume 97GiB Windows NTFS volume + /0/1/0.0.0/7 /dev/sda7 volume 89GiB EXT4 volume + /0/1/0.0.0/8 /dev/sda8 volume 8098MiB Linux swap volume + /1
[Kernel-packages] [Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
I was unable to use apport-collect but I believe the information I have provided is sufficient. I am running Ubuntu 16.04.1 LTS with kernel v4.7.5-generic on a x64 HP Spectre x360 with Broadwell GT2 5500 integrated graphics. ** 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/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U Status in linux package in Ubuntu: Confirmed Bug description: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627408] [NEW] Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U
Public bug reported: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. ** 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/1627408 Title: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U Status in linux package in Ubuntu: New Bug description: I would like to report a severe graphics regression, involving frequent rainbow-glitching and flickering on a x64 computer with Intel Broadwell 5500U processor w/ integrated graphics. This issue was not present on kernel v4.7.4, which I will continue to use. Due to unfortunate issues with Broadwell integrated graphics support, virtually every kernel build in the 4.8 release chain as well as the newest v4.7.5 kernel have this issue. Dramatic multicolored patches and glitched areas appear frequently when using my computer with these kernels installed. The behavior is very similar to that of the Broadwell graphics issues present in kernel version 4.6.x. Please fix this issue, I don't understand why NEWER kernels are actually causing significant graphical problems with older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
